@GrapheneOS @fireborn @larsmb @semitones @thomas @mpldr @j_j Then maybe GrapheneOS has to remain disabled hostile because these companies are, and the solution could be a community spinoff based on GrapheneOS source releases.
Kinda sad though.
@divVerent @fireborn @larsmb @semitones @thomas @mpldr @j_j GrapheneOS is not disabled hostile. A post pushing a bunch of fabrications and spin about us doesn't make that the case. It will certainly result in a worse experience for disabled people going forward due to discouraging contributions in these areas, demotivating our development team and piling on further harm to the project from attacks on it which take away the resources and support we need to even continue without adding more.
@divVerent @fireborn @larsmb @semitones @thomas @mpldr @j_j Do you think what you're doing accelerates our existing work on it? Do you think it's going to motivate our developers and make things happen faster? If you believe any of that, you couldn't be more wrong. This has massively demotivated the team and harm the project in ways that are going to make progress on this slower. You think driving away help from the project is going to speed it up? It's an open source project. You could help.
@GrapheneOS @divVerent @larsmb @semitones @thomas @mpldr @j_j See this thread. https://infosec.exchange/@matchboxbananasynergy/114570624717710963. In short, I was deeply frustrated at the general FOSS messaging seeming to be applied in the posts that I quoted, which reads generally like "we gave you half the car. Go build the rest of it." I've been dealing with this for years, in almost every project I actively use. Starting a conversation with this wasn't productive.
@fireborn @divVerent @larsmb @semitones @thomas @mpldr @j_j GrapheneOS didn't have network location, something many people consider a basic feature, from 2014 through 2024 until near the end of the year. There are many things we need to implement ourselves. Most third party implementations of features usually don't meet our requirements and we either need to make our own or heavily fork them.
Open source TalkBack is in a bad state from Google and we have to deal with that ourselves.