1,422 karma · joined May 19, 2020
No, people are correctly pointing out the fact that this is blatantly unfair. You are claiming that 2+2=5 because a judge said so.
If you are concerned about the "consequences" maybe you should start thinking about how open platforms are now legally disadvantaged to closed platforms.
[1] Section 1.1.6: https://developer.apple.com/app-store/review/guidelines/
[1] https://www.theverge.com/2024/6/19/24181214/eu-chat-control
Windows Phone was around during the time that carrying a smartphone on your person at all times was optional, and we didn't have critical government and banking services being delivered exclusively through apps that only work on Google Android and Apple iOS. I suspect that if Windows Phone had survived, and managed to keep even a tiny fraction of the market share, these apps would nonetheless be forced to support it because they would have to account for at least some of their customers using it.
If you're asking what the solution is, I'm not sure, but sticking your head in the sand isn't a great way to handle it. GrapheneOS thinks that suing Google might be the way to go: https://news.ycombinator.com/item?id=41119047
That isn't sufficient. You'll also need to use an OS which provides "acceptable" hardware attestation capabilities (as defined by Google) required to verify that the copy of Chrome is legitimate (otherwise this could be spoofed). In practice that most likely means your options are limited to: Windows 11, macOS with System Integrity Protection enabled, Chrome OS, stock Android with Google services installed as system apps, iOS.
Google's first attempt at bringing attestation to the web, WEI, was shot down by hackers, but it won't be the last. Please continue to fight against this.
I think the idea is that no amount of forking Android is going to produce something different enough to entice developers to port their apps to it, but maybe if an entirely new Linux-based mobile platform kicks off, there's a chance?
If you have to consult `developer.android.com` (a Google-owned domain) to develop for your "totally not Android" platform, it may be difficult to avoid the temptation to do as the documentation recommends and simply embrace proprietary Google services and hardware attestation and whatnot. After all, 99% of users have those things and it's just these several weird forks that don't?
https://discuss.grapheneos.org/d/14344-cellebrite-premium-ju...
> GPS stuff breaks
I haven't experienced things breaking, but it is slightly slower (very slow if indoors) to get a GPS lock, because by default even location requests through Google's API are re-routed to the system service, which uses standard GPS/SUPL/PSDS rather than hoovered-up Wi-Fi SSIDs. You can optionally enable Google's location service if you want faster results.
I trust F-Droid more than $RANDOM_GITHUB_ACCOUNT.
Not really? You can choose whether to upload your recovery key to iCloud or not. The software abstracts over the details of course, but Signal does that too. Unless you're arguing that it's impossible for closed source software to have "true E2EE", which may have some merit, but Discord is proprietary, and something is better than nothing.
[1] https://github.com/cormiertyshawn895/RecordingIndicatorUtili...