GrapheneOS: Talks shit about Fairphone and their 'ancient' hardware on socials, not considering them as an option at all.

Also GrapheneOS: Partners with Motorola/Lenovo despite more devices in their lineup having relatively mediocre chipsets than not.
@maddy Oh yeah, GrapheneOS, the OS that's fine officially shipping sandboxed proprietary Google Play Services but will not ship a screen reader because it's GPLv3!
@nytpu @maddy wait, the fuck? they don't ship a screen reader? they're OK with being inaccessible???
@senil @nytpu I mean, they don't shut the fuck up about privacy and security, but I never see them spotlight accessibility.

@senil Yep, their social media account has told actual blind people to "just manually download a TTS engine" which is really useful advice when it is literally impossible for someone to interact with the device to get past the initial OOBE.

(They actually do ship TalkBack since that's part of AOSP, but they're missing a TTS engine. Which is like a Linux distro including a desktop environment but no graphics drivers and saying they "have graphics")

@maddy

@nytpu @maddy Ohhhh my godddd that's. Annoying as hell. "We ship the thing that would let you use a TTS system, but we don't actually provide one for you to get started with, if you need one you're on your own."

Surely there's like, some basic TTS engine that could be used for at least the initial OOBE and then post-setup assist the user in installing a more appropriate one if they REALLY don't want to ship a properly featured system.

@nytpu @maddy Truly why does this as a trend keep happening. And I imagine their take is "well just patch it in yourself if you want one from the start" since that attitude is ALSO disappointingly prevalent amongst OSS in general.

Fucking gross.

@senil @nytpu For real. It's incredibly infuriating to see accessibility as a low priority until they just happen to need it themselves.

@maddy @nytpu Even then, I imagine the shitty attitude of "it falls on me to implement this fix" comes up, which leads to no consistent answer for the problem and a ton of split efforts to adding a thing that shouldn't have been a concern from early on 

Ugh.

And folks wonder why people have few choices but to stick to proprietary software, and don't back projects collectively to enable folks who literally have no alternative to use FOSS-alternatives.