Ich bin dem offiziellen GrapheneOS-Konto gerade entfolgt – nicht, weil ich das Projekt nicht schätze. Im Gegenteil: GrapheneOS ist im Bereich mobiler Sicherheit/Privacy weiterhin die beste Option.

Was mich stört, sind die ständigen Seitenhiebe auf /e/OS, CalyxOS und andere Custom-ROMs - auch wenn die Kritik völlig legitim ist. Aber ich folge dem Account, um etwas über GrapheneOS zu lesen, nicht um regelmäßig zu erfahren, was andere in den Sand setzen. Wer ein starkes Projekt hat, sollte es für sich sprechen lassen.

#GrapheneOS #Android #Privacy

/kuk

@kuketzblog LineageOS is by far the most used alternative mobile OS and yet we don't have threads on our timeline about it. That's because LineageOS as an organization isn't misleading people about GrapheneOS and trying to harm us.

/e/ and their supporters are engaging in concerted efforts to mislead people about GrapheneOS and cause personal harm to our team. Each of our threads about it has been made to provide accurate information in response to their inaccurate claims about GrapheneOS.

@GrapheneOS I’m aware of the situation, and I understand why you respond to it.

From my perspective, though, it would be better to put all of this into a dedicated blog post, FAQ, or similar resource people can refer to when needed. That would keep the information available without bringing the same broader conflict back to the main timeline again and again.

Personally, I mainly follow the account for updates about GrapheneOS itself. That is what I value most. The surrounding disputes may deserve a response too, but I think they would be better handled separately from the regular project communication.

I mean this constructively. I appreciate GrapheneOS and the work behind it. I would simply prefer the main account to focus more on GrapheneOS itself.

@kuketzblog @GrapheneOS agree, everytime my feed gets flooded by a post chain with these things I consider to unfollow.
However using just the RSS feed to follow updates doesn't really work for me because I don't want to read through all the internal and small changes. However things like the RCS update and network location I don't want to miss.

@kuketzblog @GrapheneOS and I follow your account because I care and want to see posts about GrapheneOS. If I would want to know thinks about e/OS i would go look for that.

Btw I also don't think e/OS is worth so much of your attention.

@shadowwwind @kuketzblog The level to which people have been misled across platforms about GrapheneOS is extreme. People widely believe and propagate the incorrect claims that it's not a privacy project, not usable by regular people, only useful to people targeted by sophisticated attacks and much more. /e/ and Murena are currently the main source of these claims which has been the case for a while now. Their business model is predicated on convincing people there aren't better options.

@shadowwwind @kuketzblog If someone isn't outraged about providing closer to reasonable privacy and security being portrayed as primarily useful to pedophiles, criminals and spies then they were never our target audience.

Our posts are well received on Bluesky and X. It seems the main issue here is people are using clients poorly displaying threads where each of our posts shows up in their feed separately instead of as a single thread. We can patch in long post support to Mastodon instead.

@shadowwwind @kuketzblog Bluesky doesn't have long posts. We have to format everything we write to fit within Bluesky's character limit including how it weights URLs. Mastodon's standard hard-wired character limit isn't high enough for us to fit more than one of those into a single post. We can only even use 500 characters if we're strictly writing the content for Mastodon. If we patch Mastodon's character limit then we could post the whole thing as a single post but it's not a standard feature.
@GrapheneOS @kuketzblog then like Kuketz suggested, make a blog post, link that. Works on all those platforms