I am several hundred opossums in a trench coat

  • 1 Post
  • 29 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle





  • There are plenty of legitimate reasons for Google to provide extra support and exceptions to parts of their guidelines to certain parties, including themselves. No one is claiming this is a consequence-neutral decision, and it’s right to not inherently trust these exceptions, but it is not a black and white issue.

    In this case, placing extra barriers around sensitive permissions like MANAGE_EXTERNAL_STORAGE for untrusted parties is perfectly reasonable, but the process they implemented should be competent and appealable to a real support person. What Google should be criticized for (and “heavily fined” by the EU if that were to happen) is their inconsistent and often incorrect baseline review process, as well as their lack of any real support. They are essentially part of a duopoly and should thus be forced to act responsibly.


  • Oh yeah for sure. Google, extremely large companies, and government apps essentially have different streams and access to support than the rest of us mere mortals. They all receive scrutiny, and may have slightly altered guidelines depending on the app, but the most consequential difference is that they have much more ability to access real support. I just don’t think it was an intentional and specific attempt to be anti-competitive, this is better explained by incompetence and the consequences of well-intentioned but poorly implemented policy.


  • I’ve experienced this exact issue with the Google Play Store with some clients and it’s just the worst. This kinda thing happens because Google is essentially half-arsing an Apple-style comprehensive review of apps. For context, Apple offers thorough reviews pointing to exactly how the app violates policy/was rejected, with mostly free one-on-one support with a genuine Apple engineer to discuss or review the validity of the report/how to fix it. They’re restrictive as hell and occasionally make mistakes, but at the end of the road there is a real, extremely competent human able to dedicate time to assist you.

    Google uses a mix of human and automated reviewers that are even more incompetent than Apple’s frontline reviewers. They will reject your app for what often feels like arbitrary reasons, and you’re lucky if their reason amounts to more than a single sentence. Unlike Apple, from that point you have few options. I have yet to find an official way to reach an actually useful human unless you happen to know someone in Google’s Android/Developer Relations team.

    I’m actually certain that the issues facing Nextcloud are not some malicious anti-competitive effort, but yet more sheer and utter incompetence from every enterprise/business facing aspect of Google.


  • Fair use commentary generally requires as little of the actual original work to be used as possible. Summary may be ok, clips/recordings are ok, but they must be minimal. That commentary must also be substantive.

    Reproducing a work in full (thus obviously limiting the commercial viability of the original work - another factor considered) with light commentary over the top probably wouldn’t hold up in court. The commentary just avoids automatic systems in the increasingly poorly moderated internet.


  • I think it would be great if more men read (or just read summaries of) basic feminist texts, especially Judith Butler and people of her ilk. Before I realised I wasn’t a man they helped me. I think the deconstruction of gender that feminism offers serve men just as much as women - it made masculinity feel like less of a prison (nevermind that I ultimately largely moved more feminine).

    I remember reading authors like John Stoltenberg, the aforementioned Judith Butler, and some perspectives of feminism/masculinity in a working class context.










  • It’s important to note that this is them moving in-development branches/features “behind closed doors”, not making Android closed source. Whenever a feature is ready they then merge it publicly. I know this community tends to be filled with purists, many of whom are well informed and reasoned, but I’m actually totally fine with this change. This kind of structure isn’t crazy uncommon, and I imagine it’s mainly an effort to stop tech journalists analysing random in-progress features for an article. Personally, I wouldn’t want to develop code with that kind of pressure.