@GrapheneOS @attilax @LearnToLivePrivate @RustRaven @jmoupah @Yrrussaj @sebsauvage @jolla Hey Graphene OS folks.
First, it's really great that you guys have created a security focused deGoogled Android operating system.
Given the problems of American big tech, I applaud you for creating an alternative.
So full credit where credit is due.
That being said, constantly badmouthing every other non-Apple and non-Google smartphone maker and operating system is not a good look.
And jumping into any thread on Mastodon where there's a mention of another alternative smartphone maker or OS to badmouth them is not a good look.
You say Jolla is no good. SailfishOS is no good. Fairphone is no good. Murena is no good. CalyxOS is no good. Dumbphones are no good.
I'd imagine you'd probably win more people over if you talked more about why people should choose Graphene instead why they shouldn't choose one of the others.
Because right now, there are tradeoffs with every mobile OS.
That includes Graphene.
For example, there are people for whom limiting their exposure to Google and Apple is more important than choosing the most locked down option available.
For such people, needing to buy a Google Pixel phone to run Graphene is a massive negative.
That's even if the Google Pixel is the best hardware from a security perspective.
And in that case, yeah there are other options that may be a better fit for those people.
There's another issue.
There seems to be many Reddit threads and YouTube videos and blogs out there from people who were enthusiastic about Graphene, but have soured on it.
And the funny thing is there's a pattern to it. "Cult-like" and "toxic" seems to be phrases that tend to be used a lot.
I've also noticed a recurring pattern you put for why the other alternatives are bad is because people connected with those businesses or companies badmouth Graphene.
It seems to me like Graphene constantly bags those other projects. When anyone connected with those projects responds, that response is presented by you guys as evidence of bullying and harassment, without that context.
And the recurring line about how people should just stick with iOS or Google Android if they don't choose Graphene? Just shameful. And completely misses the point of why some people are looking for alternative platforms in the first place.
And the more people who choose an alternative OS, the more normal it becomes to do it, which ultimately leads to more people looking at alternatives like Graphene.
#Android #Jolla #SailfishOS #AOSP #Graphene #GrapheneOS #Murena #Calyx #CalyxOS #Linux
@attilax @LearnToLivePrivate @RustRaven @jmoupah @Yrrussaj @sebsauvage @jolla Unlike SailfishOS, AOSP is open source and therefore it's possible to build GrapheneOS on top of it. AOSP has far better privacy and security than SailfishOS which brings the lower security of desktop operating systems to mobile.
Jolla has spent years attacking AOSP-based projects as a whole which includes us. You only think they should not be criticized in response to that because you're against AOSP-based projects.
@GrapheneOS @attilax @LearnToLivePrivate @RustRaven @jmoupah @Yrrussaj @sebsauvage @jolla Hey Graphene OS folks.
First, it's really great that you guys have created a security focused deGoogled Android operating system.
Given the problems of American big tech, I applaud you for creating an alternative.
So full credit where credit is due.
That being said, constantly badmouthing every other non-Apple and non-Google smartphone maker and operating system is not a good look.
And jumping into any thread on Mastodon where there's a mention of another alternative smartphone maker or OS to badmouth them is not a good look.
You say Jolla is no good. SailfishOS is no good. Fairphone is no good. Murena is no good. CalyxOS is no good. Dumbphones are no good.
I'd imagine you'd probably win more people over if you talked more about why people should choose Graphene instead why they shouldn't choose one of the others.
Because right now, there are tradeoffs with every mobile OS.
That includes Graphene.
For example, there are people for whom limiting their exposure to Google and Apple is more important than choosing the most locked down option available.
For such people, needing to buy a Google Pixel phone to run Graphene is a massive negative.
That's even if the Google Pixel is the best hardware from a security perspective.
And in that case, yeah there are other options that may be a better fit for those people.
There's another issue.
There seems to be many Reddit threads and YouTube videos and blogs out there from people who were enthusiastic about Graphene, but have soured on it.
And the funny thing is there's a pattern to it. "Cult-like" and "toxic" seems to be phrases that tend to be used a lot.
I've also noticed a recurring pattern you put for why the other alternatives are bad is because people connected with those businesses or companies badmouth Graphene.
It seems to me like Graphene constantly bags those other projects. When anyone connected with those projects responds, that response is presented by you guys as evidence of bullying and harassment, without that context.
And the recurring line about how people should just stick with iOS or Google Android if they don't choose Graphene? Just shameful. And completely misses the point of why some people are looking for alternative platforms in the first place.
And the more people who choose an alternative OS, the more normal it becomes to do it, which ultimately leads to more people looking at alternatives like Graphene.
#Android #Jolla #SailfishOS #AOSP #Graphene #GrapheneOS #Murena #Calyx #CalyxOS #Linux
so, while there were other things that influenced my decision to resign from #calyx, in the end, the biggest were the on-going outrageous behavior coming out of the engineering department, and a failure of leadership to do anything meaningful about it. although i deeply respect the #calyxos team and the many great folks at the institute, unfortunately, until/unless something is done, i cannot support calyx, and i cannot recommend donating to them right now. (9/9)
so, while there were other things that influenced my decision to resign from #calyx, in the end, the biggest were the on-going outrageous behavior coming out of the engineering department, and a failure of leadership to do anything meaningful about it. although i deeply respect the #calyxos team and the many great folks at the institute, unfortunately, until/unless something is done, i cannot support calyx, and i cannot recommend donating to them right now. (9/9)
none of this even delves into the #calyx engineering director's endless gaslighting, predictable derailing of discussions and decision-making, hoarding of access and information, attempts to delay / sabotage the revival of #calyxos, and apparent eagerness to direct $10,000's of member donations toward goods and services from the warmongering likes of AWS and thales. those would warrant threads of their own. (8/9)
some may think, "i don't mind if #calyx moves my name, email, address, etc to vultr. it's not like it's AWS" - or "this is why i never share any personal info that i can't afford to be leaked anyway". but in my mind, given that calyx has hosted its own services for years - VPN, tor exit nodes, #calyxos release server, etc - i think people have come to expect this and to hold them to a higher standard for data handling and transparency. it's your data. shouldn't you know who has it? (7/9)
when i became aware that the #calyx membership site's dns was changed to point to a cloud provider, i had questions, so i did something controversial: i asked. i wanted to know why, and who was involved, and what considerations were made. i emailed the board and anyone else i thought might know more. and i got a response from someone in leadership saying, among other things, "My reading of the privacy policy is different from yours." (i hadn't even mentioned the privacy policy.) (6/9)
if #calyx were going to have a functional, actually-online datacenter managed by its existing engineering department, it would have happened by now. instead, the infrastructure conversations shift seamlessly from excuse to excuse, with minimal tangible accomplishments in *years*, and the powers that be *just don't care*, despite virtually all calyx workers complaining that the lack of progress - and the technical excuses for it - make no sense. (5/9)
one day in july, after years (or nearly so) of the engineering dept failing to address known problems with the membership server - which is the same story as almost every other #calyx server - finally it "crashed", and they seized on the opportunity to migrate it to ~the cloud~, "temporarily", until calyx has its own new metal to put it on. but without a leadership change, that's never going to happen... (4/9)
This week in #FDroid (TWIF) is live but late to toot:
* Slow updates? There's a reason, or 2️⃣
* Don't be surveilled, engage in our research 🔭
* Using #Calyx#CalyxOS? Read now! 💔
* #DeltaChat hits v2, #ArcaneChat soon™
* #NeoStore finally upgrades to Index-V2
* #NewPipe in your 🚗 ? Maybe...
* #Wesnoth is back 🐴 ⚔️
& 164 more updates
- 4 apps archived
Saturday reading break: https://f-droid.org/2025/08/07/twif.html