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.

@kuketzblog /e/ has spent years widely propagating inaccurate claims that GrapheneOS isn't a privacy project, doesn't work on privacy, isn't aimed at regular people, isn't usable, isn't compativle with apps, is difficult to install and much more.

/e/ have repeatedly pushed the false claim that GrapheneOS is primarily useful to criminals and that the userbase largely consists of criminals. They've expanded this to claiming security hardening primarily benefits criminals.

https://grapheneos.social/@GrapheneOS/116353973732143171

@kuketzblog Legitimate privacy projects and organizations would not push the narrative that privacy and security are primarily beneficial to criminals or that the userbase of projects like GrapheneOS and Signal primarily consists of criminals. This isn't a one time incident but rather a consistent narrative from /e/.

/e/ and Murena laid the groundwork for France's national law enforcement and corporate/state media using the same talking points to attack the GrapheneOS project alongside them.

@kuketzblog France's national law enforcement has increasingly gone after apps and devices which are regarded as providing people with privacy and security regardless of the merit to that marketing. In their interviews with the media about GrapheneOS, they made direct reference to past arrests and server takeovers targeting multiple companies and said they would go after us similarly if they could justify it. This is a serious matter and efforts by /e/ and Murena to help them are a big deal.

@kuketzblog Our most important infrastructure for builds and signing has always been on local hardware.

We were concerned about our authoritative DNS, website and other services being hijacked based on direct threats and escalating false narratives of GrapheneOS being for criminals. OVH was previously our main hosting provider and is based in France. OVH directly facilitated those past server takeovers.

We no longer have servers in France or with hosting providers based in France due to this.

@GrapheneOS @kuketzblog I think criticism, while valid, doesn't have its place in a project account. It should probably be in some developer's fedi account, or if that's not possible, in CW in your project account. People sometimes want to read your account to learn about GrapheneOS news, not to learn about other people saying inaccurate stuff about it. By talking a lot about them you're (unintentionally) basically advertising for their content, giving them attention, and I'm not sure that's what you want.

You just can't fix every single article talking about GrapheneOS. But you can recommend reading the official documentation to users confused about them, or even you can get in touch with people writing about it to gently suggest corrections. Inaccurate claims aren't necessarily intentional.
@fun @kuketzblog Our threads about this contain a lot of accurate information about GrapheneOS to address the inaccurate information about it. Most organizations would have a feed filled with marketing fluff with very little substance. We've been focusing on this recently because the attacks on us massively escalated since early March. If we post it elsewhere then it's not going to achieve the goal of widely informing people about the truth to address the inaccurate claims which are being made.
@GrapheneOS @kuketzblog I'm not saying it is inaccurate info.

Who is attacking your developers personally? Where? How? Why?

@fun @kuketzblog Duval has heavily participated in attempts to baselessly portray our founder as insane, delusional, schizophrenic, etc. They mislead people about GrapheneOS and then respond to us addressing it with these personal attacks.

Here's an example where Gaël Duval was linking to harassment content targeting our founder with fabricated stories on a neo-nazi conspiracy site where the content was primarily sourced from Kiwi Farms:

https://archive.is/SWXPJ
https://archive.is/n4yTO

@GrapheneOS @kuketzblog Okay, Duval (and Rossmann/FUTO) are attacking you publicly.

Are individual (previous or not) users attacking your developers personally?
@GrapheneOS @kuketzblog (also, I recommend against linking to archive.is since that website and the whole family of archive.ph websites are involved in a harassment/DDoS campaign: https://arstechnica.com/tech-policy/2026/02/wikipedia-might-blacklist-archive-today-after-site-maintainer-ddosed-a-blog/)

@fun @kuketzblog Which archive site should we use instead that's not going to take down what we archive upon request from the person engaging in attacks on us as archive.org will do?
@GrapheneOS @kuketzblog When did that happen, on what URL, by whom, and why?
@GrapheneOS @kuketzblog I'm asking just because I genuinely want to know how easy it is for someone harassing to do such a thing.

@fun @kuketzblog They take down content upon request as a standard policy. It doesn't work for what we need.

https://help.archive.org/help/how-do-i-request-to-remove-something-from-archive-org/

How do I request to remove something from archive.org? – Internet Archive Help Center

@GrapheneOS @kuketzblog I would archive to archive.org and in addition take screenshots if that's a concern. The advantage w/ screenshots also is that, assuming you just post them here, they will never go down unless your infra does (or you remove them)
Internet Archive: Digital Library of Free & Borrowable Texts, Movies, Music & Wayback Machine

@GrapheneOS @kuketzblog from what I can tell they don't remove unless there's a very good reason to
@GrapheneOS @kuketzblog "because grapheneos archived it to talk about it!!!!!" is I think not good enough of a reason for them to get rid of it