GrapheneOS

Open source privacy and security focused mobile OS with Android app compatibility.

Public Key

npub1235tem4hfn34edqh8hxfja9amty73998f0eagnuu4zm423s9e8ksdg0ht5

NIP-05 Address

GrapheneOS@grapheneos-social.mostr.pub

Profile Code

nprofile1qqs9g69ua6m5ec6ukstnmnyewj7a4j0gjjn5hu75f7w23d64gczunmgpz4mhxue69uhhyetvv9ujuerfw36x7tnsw43q0uc5de

Publishing to

relay.ditto.pub

Author Public Key

npub1235tem4hfn34edqh8hxfja9amty73998f0eagnuu4zm423s9e8ksdg0ht5

Show more details

Last Notes

2026-04-05 22:03:40 UTC

- reply

@nprofile…q9qe GrapheneOS is based in Canada, not France. However, we avoid strongly tying ourselves to Canada and are willing to move elsewhere if there are ever authoritarian laws which prevent us from continuing GrapheneOS in it. Laws which don't impact us directly aren't an issue. We did have multiple public-facing servers in France and had most of our public-facing servers hosted with a French company (OVH). We left those entirely behind.

2026-04-05 21:59:27 UTC

- reply

France is the most anti-encryption, anti-privacy and anti-security country in the EU. They've been doing a gradual crackdown on open source privacy projects including GrapheneOS and Signal with escalating smears and threats. /e/ and Murena are on the side of the police state.

2026-04-05 21:52:18 UTC

- reply

/e/ and Murena have repeatedly claimed GrapheneOS is for drug dealers, pedophiles, terrorists and spies. /e/ and Murena are anti-privacy. They're heavily profiting from marketing products as private but don't believe in it. /e/ is an authoritarian-aligned fake privacy project.

2026-04-05 21:45:59 UTC

- reply

/e/ and Murena have their own privacy invasive behavior in their apps and services. One particularly egregious example is their supposedly private speech-to-text service sending user data to OpenAI without consent instead of doing most locally like Apple:
https://community.e.foundation/t/voice-to-text-feature-using-open-ai/70509

2026-04-05 21:44:51 UTC

- reply

Their marketing heavily focuses on avoiding Google and gives the impression they believe privacy means avoiding one company. Meanwhile, they add a bunch of Google services not present in the Android Open Source Project and give extensive privileged access to Google apps/services.

2026-04-05 21:40:30 UTC

- reply

/e/ and Murena aren't on the same side as GrapheneOS. They're charlatans selling devices with poor privacy and atrocious security to earn money. They've spent years trying to undermine a legitimate privacy project and heavily use the same talking points as police state advocates.

2026-04-05 21:37:14 UTC

- reply

/e/ and Murena are based in France. They've been pushing false narratives about GrapheneOS falsely claiming it isn't usable by regular people and doesn't benefit them for years. Duval has been making the ludicrous claim GrapheneOS is only useful to criminals and spies for years.

2026-04-05 21:33:49 UTC

- reply

Here are several particularly egregious examples:
https://www.leparisien.fr/faits-divers/telephones-proteges-utilises-par-les-narcotrafiquants-rien-nest-inviolable-19-11-2025-3PP34GIBAJGH3EZOVEJVT7OMU4.php
https://www.leparisien.fr/faits-divers/google-pixel-et-grapheneos-la-botte-secrete-des-narcotrafiquants-pour-proteger-leurs-donnees-de-la-police-19-11-2025-NTGPQE4JCNGEHLF7XGIQ3CCA2I.php
https://www.franceinfo.fr/faits-divers/narcotrafic-les-autorites-alertent-sur-l-utilisation-d-un-systeme-d-exploitation-de-telephone-pour-echapper-aux-forces-de-l-ordre_7631510.html
Gaël Duval and Murena participated in these attacks. They even spread harassment content towards our team and shared it with sites attacking us.

2026-04-05 21:24:46 UTC

- reply

Across most of the French corporate and state media covering it, inaccurate claims by the state about the features, distribution and marketing of GrapheneOS were wrongly presented as factual. Most media didn't contact us and none of them showed us what was claimed about us before we could respond.

2026-04-05 21:18:43 UTC

- reply

Recently, France's national law enforcement began fearmongering about GrapheneOS and smearing it with inaccurate claims. France's corporate and state media heavily participated. Many articles and also radio/television coverage misrepresented GrapheneOS as being for criminals.

2026-04-05 21:13:49 UTC

- reply

Despite being done for profit, /e/ receives millions of euros in funding from the EU on an ongoing basis. /e/ and Murena use extraordinarily inaccurate marketing to not only promote their products/services but also to mislead people about GrapheneOS and scare them away from it.

2026-04-05 21:09:56 UTC

- reply

Murena is a for-profit company owned by shareholders including Gaël Duval. /e/ has a non-profit organization which is also led by Gaël Duval. /e/ includes paid services from Murena. /e/ very clearly exists to build products for Murena to sell in order to enrich the shareholders.

2026-04-05 21:06:56 UTC

- reply

It's common for apps and websites to do everything through their own servers. That's best practice to avoid leaking API keys. It's increasingly common for invasive libraries to use hard-wired IPs and/or DNS-over-HTTPS to evade blocking. DNS filtering is increasingly less useful.

2026-04-05 21:04:12 UTC

- reply

Their DNS blocklist can only block domains not used for useful functionality to avoid ruining usability. Meanwhile, the most privacy invasive behavior by apps is rarely ever split out into separate domains. Even for those, apps and websites can trivially evade DNS blocklists.

2026-04-05 21:02:25 UTC

- reply

/e/ and Murena devices are far worse for privacy and security than an iPhone. It's trivial to break into their devices remotely or extract data from them compared to an iPhone. They have weaker privacy protections from apps too. Their main approach to privacy is a DNS blocklist.

2026-04-05 20:56:03 UTC

- reply

/e/ is far weaker in all of these areas compared to the standard Android Open Source Project on secure hardware. It doesn't keep up with standards updates and protections. It adds tons of low security attack surface and privacy invasive services. It's not in the same space as us.

2026-04-05 20:54:05 UTC

- reply

GrapheneOS and iOS are both heavily focused on privacy and security. Both are gradually adding much stronger protections against apps/sites scraping data, coercion users into giving data via alternatives with case-by-case consent and increasingly strong exploit protections.

2026-04-05 20:50:55 UTC

- reply

It's hardly only GrapheneOS focusing on protecting users against exploits. Apple and Google have put a ton of work into it. Apple heavily focuses on privacy and security. That includes protecting against remote exploits, local exploits from compromised apps and data extraction.

2026-04-05 20:43:03 UTC

- reply

For years, Gaël Duval has spearheaded a campaign to misrepresent GrapheneOS as not being usable, not compatible with apps and only useful to a tiny minority of people. He has repeatedly claimed GrapheneOS is for pedophiles, criminals and spies while claiming /e/ is for everyone.

2026-04-05 20:41:48 UTC

- reply

/e/ has far worse privacy and security than the Android Open Source Project. They fail to keep up with important standard privacy and security patches for Android, Linux, firmware, drivers and HALs. They fail to provide current generation Android privacy and security protections.

2026-04-05 20:36:07 UTC

- reply

GrapheneOS exists to protect users from having their privacy invaded by arbitrary individuals, corporations and states. Privacy depends on security. GrapheneOS heavily improves both privacy and security while providing a high level of usability and near perfect app compatibility.

2026-04-05 20:26:43 UTC

- reply

> si la mémoire est pas corrompue, des trucs de sécu vraiment durcis qui pourraient être utiles clairement pour des dirigeants, dans les services secrets ou que sais-je. C'est pas notre but, notre but c'est de partir d'un constat, aujourd'hui nos données personnelles sont pillées en permanence et ça serait pas légal dans la vraie vie avec le courrier ou le téléphone, on veut changer ça. Donc on vous fait un produit qui change ça par défaut pour n'importe quelle personne.

2026-04-05 20:26:39 UTC

- reply

Transcription in French:
> Il y a la surface d'attaque, là pour le coup on est pas des spécialistes de la sécurité, donc je ne pourrais pas te répondre avec précision, mais des discussions que j'ai eu, il semblerait que tout ce qu'on fait, ça réduit la surface d'attaque. Donc oui, probablement ça aide. Par contre, on a pas une approche "sécurité durcie", on développe pas un téléphone pour les pédo(bip) pour qu'ils puissent échapper à la justice. Donc il y a pas des trucs pas possibles pour voir

2026-04-05 20:26:08 UTC

- reply

> with the mail or the telephone, we want to change that. So we are making you a product that changes that by default for anyone.

2026-04-05 20:26:04 UTC

- reply

> we do reduces attack surface. However, we don't have a "hardened security" approach, we aren't developing a phone for pedo(censored) so they can evade justice. So there aren't difficult things to check if the memory is corrupted, really hardened security stuff that could clearly be useful for executives, in the secret service, or whatever. That's not our goal, our goal is to start from an observation: today our personal data is constantly being plundered and that wouldn't be legal in real life

2026-04-05 20:25:41 UTC

Gaël Duval is the founder and president of the /e/ foundation along with the CEO of Murena. Duval and his organizations have consistently taken a stance against protecting users from exploits. In this video, he once again claims protecting against exploits is for only useful pedophiles and spies.
Translation to English:
> There's the attack surface, on that front we're not security specialists here, so I couldn't answer you precisely, but from the discussions I've had, it seems that everything
https://grapheneos.social/system/media_attachments/files/116/353/970/673/759/638/original/9e06eacbb567eab4.mp4

2026-03-30 21:34:57 UTC

- reply

@nprofile…8096 We have bigger fish to fry with legal action.
Debunking this and showing how ridiculous it is should defuse the ability for it to cause harm to us.
It would be a huge pain to take legal action against someone in Europe so it better be worth it. We don't think he's going to cause much harm to us with us debunking it.
We can hopefully get multiple news organization to look into the situation and correct their articles.
It's genuinely ridiculous how much bullshit we deal with...

2026-03-30 20:59:49 UTC

- reply

He was selling devices by misrepresenting his involvement and was going after other companies selling devices with GrapheneOS based on claiming to have created it. He donated a small portion of the sales to GrapheneOS, but the way he earned it money caused substantial harm to us.

2026-03-30 20:52:54 UTC

- reply

We allowed him to make a fork and sell devices with it but he thoroughly misrepresented that as being GrapheneOS behind our backs. He took advantage of the language barrier and our lack of awareness about Dutch media along with us being occupied by the attacks from Copperhead.

2026-03-30 20:50:17 UTC

- reply

Abdoul said he would donate a portion of the money from each device he sold to GrapheneOS but didn't end up providing most of it. Despite that, he later tried to extort us claiming he'd invested money and was owed returns. GrapheneOS isn't a business and has no shareholders.

2026-03-30 19:11:26 UTC

- reply

This isn't limited to tech news sites passing themselves off as credible sources. Here's one of the major Dutch news sites publishing his claims:
https://www.bnr.nl/nieuws/tech-innovatie/10597115/ajaxstopteomvangrijkdatalekuit-2017-in-de-doofpot
We've attached some screenshots of claimed achivements on Abdoul's website at https://aquax.nl/.
https://grapheneos.social/system/media_attachments/files/116/319/707/302/864/367/original/dd4f742ff9a5d54b.png
https://grapheneos.social/system/media_attachments/files/116/319/707/491/975/215/original/e78ddef0b19c5be8.png
https://grapheneos.social/system/media_attachments/files/116/319/707/685/243/124/original/1a0c9f630beca9eb.png

2026-03-30 18:59:22 UTC

- reply

These journalists seriously need to take a close look at Abdoul Rasnab's website where he claims to be responsible for the 2014 celebrity nude leaks involving iCloud and much more. His claims are clearly false. How is the Dutch media getting duped into repeating his stories?

2026-03-30 18:46:49 UTC

- reply

We need help from people in the Netherlands to get Tweakers to investigate their past story where they were duped by Abdoul Rasnab into believing he founded GrapheneOS. They should take it down and issue a formal retraction. Slop farms including Cybernews are unlikely to do much.

2026-03-30 18:45:18 UTC

- reply

We're drawing attention to this because we're concerned about Abdoul Rasnab's fabrications about involvement in GrapheneOS and his supposed hacking achievements being leveraged in state attacks on GrapheneOS. He's making himself a useful idiot for authoritarians slandering us.

2026-03-30 18:43:01 UTC

- reply

Take a look at Abdoul's site and expand the section on data breaches where he claims credit for a bunch of them. We have direct experience with 2 years of him pretending to be supportive while building a business around pretending to be our project. This is simply how he rolls.

2026-03-30 18:36:12 UTC

- reply

Abdoul's site claims he's responsible for major data breaches even including the 2014 celebrity nude photo leaks tied to iCloud. Abdoul has previously duped Dutch podcasts and news sites including Tweakers.net into publishing content claiming he founded GrapheneOS.

2026-03-30 18:14:50 UTC

- reply

We heard from several people who knew Abdoul Rasnab that the reason for his arrest and imprisonment while awaiting trial was him pretending to have committed crimes to impress a woman who turned out to be a police informant. That sounds a lot like what he's doing right now.

2026-03-30 18:12:56 UTC

- reply

Abdoul Rasnab spent a year in prison in Spain which brought an end to his proprietary fork of GrapheneOS pretending to be the original project and his company selling it. We don't know the details. He claims he didn't commit a crime and was found to be innocent. It's possible.

2026-03-30 18:02:38 UTC

- reply

Cybernews has taken AI slop content from Abdoul Rasnab's site claiming credit for hacking a company and published it on their site, which is now being spread by other news sites:
https://cybernews.com/security/ajax-silenced-hacker-2017-data-breach/
This is the state of journalism in 2026. It's why we've posted this thread.

2026-03-30 18:01:49 UTC

- reply

Cybernews is a content farm presenting their coverage of information security as being investigative journalism and security research. We've previously debunked a story from them involving the Pixel 9 which was heavily spread by other news publications:
https://discuss.grapheneos.org/d/16338-highly-misleading-and-inaccurate-article-from-cybernews-about-the-pixel-9

2026-03-30 18:00:04 UTC

- reply

Abdoul Rasnab has created a website filled with AI slop where he claims to have discovered a bunch of severe vulnerabilities and claims credit for hacking multiple companies. He's once again falsely claiming to have founded GrapheneOS on this website:
https://aquax.nl/

2026-03-30 17:49:48 UTC

- reply

Abdoul Rasnab previously tried to extort us by coming up with fabricated stories about us and claiming he would ruin our reputation pushing those in the media. He backed down and he once again stopped wrongly calling himself a founder of the project but now he's back to doing it.

2026-03-30 17:43:38 UTC

- reply

He created a proprietary fork of GrapheneOS and founded a company selling phones with it in Europe. He was allowed to fork GrapheneOS and sell it but absolutely shouldn't have used the same name as the upstream project. He's passing this off as having created/founded GrapheneOS.

2026-03-30 17:40:57 UTC

- reply

Abdoul Rasnab misrepresented himself as creating and founding the project in order to gain an advantage over other companies selling devices with GrapheneOS. He had conflicts with those companies and he did things such as filing DMCA takedowns in our name without authorization.

2026-03-30 17:39:47 UTC

- reply

The person who sold us the grapheneos.com domain with the original rights to the name only charged us around $500 to cover their costs along with wanting a phone running GrapheneOS and accepted an old used one. It's possible they're now a GrapheneOS and supporter.

2026-03-30 17:38:01 UTC

- reply

We ended up having to purchase the grapheneos.com domain including the rights to the name. Run a WHOIS or RDAP check on grapheneos.com and you'll see it was registered in 2014. There was also a name collision with an academic project which renamed themselves.

2026-03-30 17:36:08 UTC

- reply

Back in 2018, we renamed CopperheadOS to the Android Hardening Project as a placeholder and told people we were deciding on a new name. Abdoul Rasnab was one of multiple people who suggested GrapheneOS as a name. He seems to think that somehow made into his project post-rename.

2026-03-30 17:34:01 UTC

- reply

His proprietary fork of GrapheneOS and his company both wrongly reusing the name of the project he forked only existed from around 2018 through 2021. The part that's still ongoing is that he keeps reverting back to promoting himself by claiming to have founded GrapheneOS.

2026-03-30 17:31:11 UTC

- reply

To this day, Abdoul Rasnab misrepresents himself as a founder of GrapheneOS. He even portrays himself as being actively involved in the project. He makes many extraordinarily claims about himself unrelated to GrapheneOS which help to contextualize the claims about GrapheneOS.

2026-03-30 17:24:30 UTC

- reply

He did multiple interviews in Dutch with media in the Netherlands where he misrepresented himself as being the founder and creator of GrapheneOS. He told his customers he was the creator of GrapheneOS and that devices running a fork from him were using the official GrapheneOS.

2026-03-30 17:23:26 UTC

- reply

He took advantage of the fact that we were incredibly busy and under huge pressure from attacks by Copperhead. He acted as if he was supporting us while actually taking advantage of us and pretending he had created the open source project he didn't write 1 line of code in.

2026-03-30 17:22:37 UTC

- reply

He used GrapheneOS as the name for his proprietary fork of GrapheneOS and also named his company founded in the Netherlands GrapheneOS. He didn't have authorization to do this and was misleading us about what he was doing and how he was presenting his involvement in GrapheneOS.

2026-03-30 17:21:30 UTC

- reply

Abdoul Rasnab repeatedly misrepresented himself as a creator or founder of GrapheneOS on LinkedIn and elsewhere. He repeatedly agreed to stop but never followed through. Later, we found out he built his whole business around misrepresenting himself as having created GrapheneOS.

2026-03-30 17:20:24 UTC

- reply

Abdoul Rasnab said he wanted to support us and committed to providing a portion of the sales of devices. We had no formal business deal. He didn't need a commercial license to use GrapheneOS. We thought it was someone being generous, although he didn't end up sending most of it.

2026-03-30 17:17:54 UTC

- reply

From 2018 through around 2021, Abdoul Rasnab sold devices with his own proprietary fork of GrapheneOS. That's 4 years after the project was started. He had no involvement in creating or founding GrapheneOS. He also didn't write absolutely any of the GrapheneOS project's code.

2026-03-30 17:15:30 UTC

- reply

A bunch of companies and individuals have sold devices with GrapheneOS or a fork of it. Many companies making forks of GrapheneOS haven't complied with our open source licenses and our separate rules for usage of our trademarks which we've been actively addressing for years.

2026-03-30 17:11:40 UTC

GrapheneOS is an open source project. Open source means it can be modified and used for any purpose including commercial ones. People making forks of GrapheneOS are supposed to rebrand it and make it clear that it's not the official GrapheneOS but rather a derivative of it.

2026-03-29 16:49:08 UTC

- reply

@nprofile…srdy GrapheneOS is entirely funded by donations. Paying developers is our main expense by far followed by legal fees, auditing and accounting. Our other expenses such as servers are quite small since we're being very efficient including seeking out sponsorships from hosting providers. If every GrapheneOS user donated $20 per year that would be over 8 million dollars per year of donations. We unfortunately don't get that much but don't underestimate how much money we can raise via donations.

2026-03-28 22:59:03 UTC

- reply

@nprofile…5nsj @nprofile…w4aq It will be regular GrapheneOS on Motorola devices. That won't have their apps and services.
They also want to integrate a subset of GrapheneOS features into their own OS which is a separate thing.

2026-03-28 21:14:30 UTC

- reply

@nprofile…w4aq Lenovo is a Chinese company based in Hong Kong.
We're expanding device support to one of the most widely available brands of devices while keeping all of our security standards intact.
It's not our fault that most Android OEMs aren't interested in improving their devices to meet our security requirements with better updates, better hardware/firmware security and adding more of the standardized hardware-based security features.
Why exactly are you angry with us?

2026-03-28 15:38:39 UTC

- reply

There aren't yet devices supporting GrapheneOS directly sold in South America. Brazil in particular has unusually high import duties/taxes which add up to around 100%. This has resulted in us not having a lot of users there but our Motorola partnership will start changing this.

2026-03-28 15:29:12 UTC

- reply

We have a tiny VPS in São Paulo for our ns1 anycast DNS and a second for our website/network services. It probably isn't an issue and those can be removed if necessary. Santiago could be added for both instead but wouldn't work very well as a replacement for having São Paulo.

2026-03-28 15:25:38 UTC

- reply

GrapheneOS has no team members or operations in Brazil. São Paulo in Brazil is by far the biggest network hub within South America. Miami is also a major network hub for South America and is currently where our update server is for South America since it's dramatically cheaper.

2026-03-28 15:08:48 UTC

- reply

It doesn't stop there. It would require keeping data for auditing and providing a token for connecting age verification checks by apps and websites to the data. The law is a privacy disaster and exposes minors to being exploited by leaking their age bracket to apps and websites.

2026-03-28 15:06:06 UTC

Brazil's authoritarian age verification law became active this month. It won't be implemented by GrapheneOS. Complying would require integrating a mandatory process for each user where a third party service checks government identification and confirms a match using the camera.

2026-03-28 13:27:37 UTC

- reply

@nprofile…jq3w CalyxOS has never been a privacy or security hardened OS. It has also always been a downgrade from the privacy and security of the Android Open Source Project in practice. You can read this thread which touches on how CalyxOS was started:
https://grapheneos.social/@GrapheneOS/116302069161337930
They've tried to give people the impression that it will be coming back to life but that doesn't mean it will. They never shipped the 2025-06-05 or later patch level. On 2025-08-05 they said it would be back in 4-6 months.

2026-03-28 12:53:48 UTC

- reply

@nprofile…gnh0 Should we do nothing about the extreme libel, bullying and harassment directed towards our team members? This is happening every day, throughout the day. It takes a huge toll on the project. We could remain silent about it but that's not going to stop or reduce it.

2026-03-28 12:52:12 UTC

- reply

@nprofile…92x8 @nprofile…s4ce That's still going to leak people's birth dates in practice since they'll enable it without considering this. Kids aren't going to want to have content restricted based on their age past their birthday.

2026-03-28 12:47:43 UTC

- reply

@nprofile…jq3w It's not a privacy or security hardened OS. It's a fork of LineageOS which further reduces privacy and security compared to it.
https://eylenburg.github.io/android_comparison.htm
iodéOS officially partnered with Robert Braxman who is a charlatan putting out enormous amounts of inaccurate privacy content filled with fabrications. He sells products/services not providing what he claims. Braxman has been attacking the GrapheneOS project and our team for years. iodéOS is fully supportive of this.

2026-03-27 22:11:26 UTC

- reply

@nprofile…2das You've linked a video where Rossmann pushes blatant fabrications and misrepresentations with the clear aim of directing harassment towards the founder of GrapheneOS and harming GrapheneOS. It's what we're talking about. It was a calculated move on his part after an earlier live stream where he engaged in the bullying and trolling shown in his video towards a developer who had just been swatted due to harassment he supported.

2026-03-27 17:11:11 UTC

- reply

@nprofile…e8we Rossmann was brainwashed by the attacks on GrapheneOS by Copperhead and Henry Fisher (Techlore). He was being hostile towards the founder of the project for many months including actively supporting the attacks with jabs in chat rooms and his content. Rossmann expected us to be super grateful to him for covering GrapheneOS and to make content with him. After the swatting attacks in April 2023, our founder got upset with him in private and Rossmann decided to try to destroy his life.

2026-03-27 16:59:12 UTC

- reply

We're offering forgiveness to people who have engaged in years of libel/harassment towards us if they take down their attacks, debunk it and help repair the harm caused to us. This offer even extends to Henry Fisher and Louis Rossmann. Alternatively, we can address it in court.

2026-03-27 16:52:43 UTC

- reply

No one should believe the false narratives peddled by these people. They've always been in it for personal benefit and have caused immense harm to actual efforts to improve privacy and security. We're willing to forgive people who were duped by their fabrications, just reach out.

2026-03-27 16:51:48 UTC

- reply

Nicolas Merrill burned down Calyx and CalyxOS on his way out. Nick was secretly working on a for-profit company to replace Calyx. He used Calyx resources for his personal benefit and was pushed out. Louis Rossmann is one of 3 co-founders of the company:
https://www.sec.gov/Archives/edgar/data/2009536/000200953624000001/xslFormDX01/primary_doc.xml

2026-03-27 16:49:54 UTC

- reply

Nicolas Merrill took advantage of the situation. He hired a Copperhead employee involved in the takeover to create CalyxOS. CalyxOS heavily used our code and documentation. It was promoted by attacking us and portraying themselves as being above the situation with Copperhead.

2026-03-27 16:44:19 UTC

- reply

Copperhead made the attacks personal and targeted the founder of GrapheneOS with fabricated stories and vile personal attacks. Henry Fisher (Techlore) collaborated with Copperhead to make it into widespread harassment. Others opportunistically took advantage of the situation.

2026-03-27 16:38:04 UTC

- reply

Copperhead published a bunch of press releases and did interviews pushing their false narrative. Many companies including Twitter defaulted to taking the word of a tiny corporation falsely claiming credit for our work over us. We've yet to receive back our stolen Twitter account.

2026-03-27 16:35:12 UTC

- reply

Copperhead heavily edited Wikipedia to push their false narrative. It's why there's a huge article on CopperheadOS presenting it as a separate product when it wasn't one and an inaccurate history in the GrapheneOS article. False narratives about our team are still there too.

2026-03-27 16:33:08 UTC

- reply

Copperhead heavily pushed the false narrative that they created the project and that we created a fork in 2018 which absolutely isn't true. Their claims fell apart in their legal attacks on GrapheneOS and we wiped out their closed source fork by forbidding them using our code.

2026-03-27 16:31:24 UTC

- reply

Copperhead remained entirely dependent on GrapheneOS and had to keep forking our code for each major Android update. Despite depending on GrapheneOS, they waged a war against it trying to destroy the project and attempting to ruin the lives of our team, especially our founder.

2026-03-27 16:27:41 UTC

- reply

GrapheneOS still has the original CopperheadOS repositories on GitHub. Copperhead seized a bunch of the project's infrastructure and accounts. They created a closed source fork of GrapheneOS called CopperheadOS after the split which was not the same CopperheadOS as the original.

2026-03-27 16:25:40 UTC

GrapheneOS started in 2014 and was originally named CopperheadOS. In late 2015, the Copperhead company was founded which was meant to support the project. Copperhead didn't create CopperheadOS and didn't own or control it. Copperhead made a failed takeover attempt on it in 2018.

2026-03-26 19:03:57 UTC

- reply

@nprofile…k5jq Multiple of the /r/privacy mods are hostile towards GrapheneOS themselves and have directly participated in making public attacks on the project with dishonest claims. Reddit should take away the moderation powers from each of the /r/privacy mods on every subreddit they moderate and give moderation control to people who aren't going to abuse it. The largest privacy subreddit banning discussion of GrapheneOS is ridiculous and Reddit should take away all power from these mods themselves.

2026-03-26 19:02:03 UTC

- reply

@nprofile…k5jq Instead, they rewarded the people attacking GrapheneOS by completely banning any discussion of it. It's not permitted to make any post about GrapheneOS or even any comment mentioning it. Even comments indirectly mentioning it to sidestep the rules will be removed if they find them and people get regularly banned for it. They'll check their comment histories and ban them for previously talking about GrapheneOS or participating in our subreddit if they even vaguely allude to GrapheneOS.

2026-03-26 19:01:06 UTC

- reply

@nprofile…k5jq On Reddit, an account blocking you prevents you from replying not only directly to them but to any of the replies to them. Malicious people were using this to cycle through new accounts blocking hundreds of people to prevent replying. They were heavily maliciously attacking GrapheneOS and our team in /r/privacy and elsewhere. /r/privacy mods were not addressing it, so we kept privately complaining t o them. They were never willing to seriously deal with the abuse of their community.

2026-03-26 18:30:34 UTC

- reply

The largest privacy community on Reddit /r/privacy bans any discussion or mentions of GrapheneOS. A bot automatically removes any post mentioning GrapheneOS they'll very actively ban people who evade their filters. The mods of the subreddit misrepresent this as something we want.

2026-03-26 18:30:26 UTC

- reply

Hacker News mods micromanage it enough to repeatedly ask us not to reuse a bit of text across our comments. Meanwhile, they do nothing about disgusting personal attacks and harassment content consistently being spread in threads about GrapheneOS on their heavily moderated site.

2026-03-26 18:30:20 UTC

- reply

Y Combinator has a financial stake in numerous surveillance and exploit development companies. Hacker News is a platform they own and the moderators on it have permitted years of vile harassment towards our team which they'd normally remove if others were targeted.

2026-03-26 18:30:10 UTC

- reply

Every day, dozens of new accounts join our chat rooms to spread the same fabrications about GrapheneOS including via direct messages.
On Hacker News, one of the accounts making personal attacks based on fabrications in most threads about GrapheneOS has been doing it for 8 years.

2026-03-26 18:30:07 UTC

There are at least a dozen people spending at least several hours attacking GrapheneOS across platforms on a daily basis. It's a very strange situation. How do these people have so much time and dedication to keep making posts across platforms attacking us? It's relentless.

2026-03-26 00:46:32 UTC

GmsCompatConfig version 169 released:
https://github.com/GrapheneOS/platform_packages_apps_GmsCompat/releases/tag/config-169
See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.
Forum discussion thread:
https://discuss.grapheneos.org/d/33525-gmscompatconfig-version-169-released
#GrapheneOS #privacy #security #gmscompat

2026-03-25 20:13:15 UTC

- reply

@nprofile…s4ce These laws dictating the information can only be used for gating access based on age is beyond ridiculous. There's no doubt they're aware it's going to be heavily used beyond the permitted use. It cannot be excused as naivety. These same governments often treat birth dates as highly sensitive information usable as a core part of authenticating people's identity. Meanwhile, they're passing laws forcing operating systems and browsers to leak the birth dates of minors to apps and websites.

2026-03-25 20:08:09 UTC

- reply

@nprofile…s4ce The laws being proposed and passed requiring providing age brackets to apps and websites are a horrific invasion of privacy for minors putting their safety at risk. It not only enables targeting minors in harmful ways particularly for the lowest age brackets but also leaks their birth date to apps and websites on the day they move into the next age bracket. One of the biggest lobbyists for these OS level age verification laws is Meta which just lose a court case for exploiting minors.

2026-03-25 07:35:01 UTC

- reply

@nprofile…3wdr @nprofile…pgqq No money is currently changing hands between us and Motorola. We haven't made any decision to have devices sold with GrapheneOS have any premium which would go towards funding GrapheneOS. It's definitely an option but not necessarily the way we're going to go. We may prefer having devices with it preinstalled at no additional cost. Getting additional funding isn't currently a goal of the partnership. We would rather have them assign more developers to work on it than that.

2026-03-25 07:32:04 UTC

- reply

@nprofile…3wdr @nprofile…pgqq We're working with Motorola and Qualcomm to improve their hardware, firmware and drivers to meet our requirements. Our minimum requirements are only the starting point for GrapheneOS support. There will be continued work on improving security.
We're working with Motorola on porting GrapheneOS to those future devices too. That includes includes implementing features including hardware memory tagging, the hardware-based portion of our USB port protection and a lot more.

2026-03-24 09:30:04 UTC

Vanadium version 146.0.7680.164.0 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/146.0.7680.164.0
See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.
Forum discussion thread:
https://discuss.grapheneos.org/d/33474-vanadium-version-146076801640-released
#GrapheneOS #privacy #security #browser

2026-03-24 07:00:32 UTC

- reply

@nprofile…5ldk It's likely we'll support the 2027 variant of the razr ultra.

2026-03-24 05:56:39 UTC

- reply

@nprofile…xsvx Firefox entirely lacks process sandboxing on Android. Firefox rolled out incomplete site isolation providing protection against data being leaked via side channels through not having it in-process. It does not implement sandboxing site isolation required to protect against more than side channels. It doesn't have sandboxing so it can't protect against anything once a remote code execution exploit occurs. It also lacks similar JavaScript VM sandboxing and many other important protections.

2026-03-24 05:56:22 UTC

- reply

@nprofile…xsvx Firefox entirely lacks sandboxing on Android. Firefox has rolled out incomplete site isolation providing protection against data being leaked via side channels through not having it in-process. It does not implement sandboxing site isolation required to protect against more than side channels. It doesn't have sandboxing so it can't protect against anything once a remote code execution exploit occurs. It also lacks similar JavaScript VM sandboxing and many other important protections.

2026-03-24 05:52:39 UTC

- reply

@nprofile…xsvx Firefox entirely lacks sandboxing on Android. Firefox has rolled out incomplete site isolation providing protection against data being leaked via side channels through not having it in-process. It does not implement strict site isolation required to protect against more than side channels. It doesn't have sandboxing on Android so it can't protect against anything once a remote code execution exploit occurs. Complete lack of sandboxing on Android is one aspect of it being far less secure.