/e/OS is a complete, fully “deGoogled” mobile ecosystem
/e/OS presents itself as a fully "deGoogled" mobile ecosystem, aiming to reclaim user privacy from tech giants. The Hacker News community fiercely debates its effectiveness, with many questioning whether it truly liberates users or simply swaps one centralized dependency for another. This story ignites a familiar discussion about the practicalities and compromises inherent in pursuing digital sovereignty on modern smartphones.
The Lowdown
/e/OS, developed by the /e/ Foundation, is an open-source mobile operating system built on a "deGoogled" version of Android. Its core mission is to provide users with a privacy-enhanced mobile experience by removing Google apps and services, replacing them with open-source alternatives and its own ecosystem components. The project emphasizes auditable privacy and aims to create a complete mobile environment that protects personal data from surveillance.
Key features and offerings include:
- Replacement of Google services with microG and alternative servers for connectivity checks, NTP, and DNS.
- An ethical search engine, Murena Find, and a curated App Lounge that rates apps based on privacy and tracker presence.
- An "Advanced Privacy" widget allowing users to hide their IP address and geolocation, alongside an always-on ad blocker.
- The Murena Workspace account for cloud storage, email, and online tools, with options for self-hosting.
- Parental control functionalities for content filtering and device location.
- Compatibility with standard Android apps, aiming to ensure digital experience isn't sacrificed for privacy.
- Multiple acquisition options, from purchasing Murena smartphones with /e/OS pre-installed to an easy web installer or manual installation for experienced users.
Ultimately, /e/OS positions itself as a comprehensive solution for individuals seeking to escape digital surveillance and maintain control over their data, offering a balance of privacy, functionality, and accessibility within the Android ecosystem.
The Gossip
Graphene vs. /e/OS: The Great Divide
A dominant theme revolved around comparing /e/OS to GrapheneOS, often with strong opinions. Proponents of GrapheneOS argued it offers superior security and privacy, highlighting its more rigorous approach to sandboxing Google services and device support primarily for Pixel phones. Conversely, /e/OS users emphasized its broader device compatibility, user-friendly interface, and the ease of getting a 'deGoogled' experience for less technical users, even acknowledging that GrapheneOS might be for more extreme security needs. There's a debate about whether /e/OS makes too many compromises, particularly regarding security updates and proprietary blobs, versus GrapheneOS's stricter stance.
Installer's Irony: Browser Compatibility Blues
Many commenters noted the ironic experience of a privacy-focused project requiring users to utilize Chrome, Edge, or Opera for its web installer due to WebUSB compatibility, while displaying a 'browser not supported' message for Firefox. This created a poor first impression, with users expecting a privacy-oriented OS to support privacy-oriented browsers. The discussion included explanations about Firefox's security-driven decision to not support WebUSB and calls for /e/OS to offer better alternative installation methods or a simple device compatibility list.
Murena's Machinations: Replacing One Overlord?
Skepticism was voiced regarding /e/OS's integration with Murena, particularly the Murena Workspace account for cloud services. Critics questioned if this merely replaced Google's centralized control with another, smaller, less-known entity, potentially reintroducing trust concerns. While the project emphasizes open-source and self-hosting options for Murena services, the default integration and perceived necessity of a Murena account led to worries about exchanging one form of digital dependency for another, rather than achieving true independence.
Real-World Roadblocks: App Adoption & Banking Blight
Users shared varied experiences with /e/OS as a daily driver. While many found it stable and functional for everyday use, including navigation and messaging, a significant hurdle remained banking and payment apps. Some reported their banking apps worked fine with microG, while others encountered failures due to security checks that flag modified or 'deGoogled' systems. This highlights the critical dependency on proprietary apps for essential services and the challenges of maintaining full functionality on alternative mobile OSs, despite privacy benefits.
Android's Enduring Embrace: Sustainability of Forks
A more philosophical debate emerged concerning the long-term sustainability of Android forks like /e/OS. Some argued that constantly tweaking a Google-controlled OS (Android) is inherently unsustainable and distracts from efforts to build truly independent mobile platforms. They fear Google could 'pull the plug' on AOSP releases or make changes that render forks unmaintainable. Others countered that AOSP provides a robust base, and building an entirely new OS from scratch is an even greater, perhaps impossible, undertaking given the resources required and the challenge of matching Android's feature set and hardware compatibility.