We published this response to a recent article promoting insecure devices with /e/OS with inaccurate claims, including inaccurate comparisons to GrapheneOS:
The founder of /e/OS has responded with misinformation promoting /e/OS and attacking GrapheneOS.
The founder of /e/OS responded to the post we made on our forum here:
https://mastodon.social/@gael/114874688715085353
Gaël Duval has repeatedly personally targeted the founder of GrapheneOS in response to us posting accurate information responding to misinformation from /e/OS and their supporters.
https://chromereleases.googleblog.com/2025/07/stable-channel-update-for-desktop_15.html
https://chromereleases.googleblog.com/2025/06/chrome-for-android-update_30.html
Patches in Chromium Stable channel updates for Android are often only in the Android tags, not the Windows ones.
The current Android release is 138.0.7204.157, with security patches beyond 138.0.7204.63:
Murena's services are not nearly as private as claimed and not at all on the same level as serious options such as Proton's software suite. Many of their services recently went down from early October 2024 through March 2025:
https://community.e.foundation/t/update-on-murena-io-service-outage/61781
It's somehow a paid service.
Since Oct 6 19:50 CET, most murena.io services have been unreachable. Affected services all murena.io services including drive, calendar, notes and email (@murena.io / @e.email) Over the air (OTA) /e/OS updates App Lounge All other websites including e.foundation, gitlab.e.foundation, community.e.foundation and murena.com remain unaffected. Context The reason behind this outage is related to our storage infrastructure that is getting old while the number of murena.io active users ha...
issues with /e/OS: https://codeberg.org/divested-mobile/divestos-website/raw/commit/c7447de50bc8fadd20a30d4cbf1dcd8cf14805a0/static/misc/e.txt
asb update history: https://web.archive.org/web/20241231003546/https://divestos.org/pages/patch_history
chromium update history: https://web.archive.org/web/20250119212018/https://divestos.org/misc/ch-dates.txt
chromium update summary: https://infosec.exchange/@divested/112815308307602739
@GrapheneOS He is posting the same stuff about you, as you about them. You are both creating long threads, how childish the other one is.
This makes everyone, no matter if they are using Graphene OS, /e/OS or something else, trust both of you less. There are enough people using an insecure OS just because they don't trust you because of this kind of bullshit behavior. Please stop it. It's more damaging than their posts about you.
@jak2k /e/OS is an extraordinarily insecure and non-private OS. If people avoid it and use an iPhone instead, they'll have far better privacy and security.
The information we've provided in this thread and on our forum is accurate and verifiable. We've included a link to a post by Mike Kuketz, a neutral third party privacy/security researcher, where he covers many of the issues with /e/OS. We can include additional third party sources about it.
/e/OS is not safe and SHOULD be avoided.
@GrapheneOS Yes, I know that, but these threads are still destroying trust into you.
(Besides, I don't think Apple offers better privacy. They do a lot more tracking that just a single ID and a single request to Google.)
@jak2k There are better implementations of DNS-based filtering including RethinkDNS.
> Yes, I know that, but these threads are still destroying trust into you.
You're claiming to speak for others and you don't. The vast majority of responses to us posting accurate information correcting inaccurate claims about GrapheneOS and products being marketed by attacking us is support for it. Many people are thankful we provide this information educating people and linking to others doing the same.
@xav @jak2k GrapheneOS is an open source project with 10 developers paid by the non-profit GrapheneOS Foundation. It is not one person's project and not a hobby project. Duval participates in misrepresenting it as such because it serves his interests including encouraging /e/OS supporters to engage in further harassment.
Contrary to your misrepresentation of what's happening, each of our threads about this has been in response to misinformation about GrapheneOS and attacks on our project/team.
@GrapheneOS It's a good reason to not use distribution Chromium packages. Linux distributions often fail to keep up with Chromium releases. I expect that this is due to three factors:
I strongly hope that a Flatpak-based sandbox gets upstreamed to Chromium. This would allow Chromium to be shipped as a distribution-agnostic flatpak, so many distro-specific packages could be retired.
@GrapheneOS To be clear, please do not use this post as an excuse to shame package maintainers. They are doing their best given very limited resources. That said, I myself use proprietary Google Chrome precisely because I can count on it to update promptly.
The proper solution is to make distro-agnostic packaging possible without losing security, and then to make a distro-agnostic package. Snap does not count because many people dislike Snap for legitimate reasons, such as being tied to a store with a proprietary implementation.
Apple and Google both provide support for offline speech-to-text using local models. Users can configure it to be fully offline. The Murena Voice to Text service in /e/OS sends the user's audio to OpenAI which is hidden away in their terms of service: https://community.e.foundation/t/voice-to-text-feature-using-open-ai/70509
GrapheneOS
ippo
Tavi
Jak2k 🏳️🌈
Xav
F4GRX Sébastien