4 ms·

I'm biased as a maintainer of my own OS, but there are severe issues with /e/OS: https://divestos.org/misc/e.txt https://divestos.org/misc/e.txt And it is hone

by _rdvw 4y ago

I'm biased as a maintainer of my own OS, but there are severe issues with /e/OS: https://divestos.org/misc/e.txt https://divestos.org/misc/e.txt And it is honestly sad to see, because they could be a real viable option and instead choose to largely ignore or hand-wave away these issues.

josephcsible 4y ago
> - Enables Safetynet checks by default which downloads and executes obfuscated proprietary code from Google > - Includes proprietary Google Widevine DRM on nearly all devices While proprietary code, obfuscation, and DRM are all evil, if /e/OS didn't support these things, then a lot of very popular apps wouldn't work on it, which would make it a lot less viable as a platform. Refusing to do those things wouldn't result in any less of those evil technologies. It would just result in less /e/OS adoption.
- npteljes 4y ago
  Linux solves a similar problem sometimes by asking the user if they'd like that feature or not. I'd really appreciate that, of course, while understanding that all these need a lot of extra effort.
- _rdvw 4y ago
  My gripe is more so the outdated/insecure browser/webview, PDF viewer, and Tor daemon.
npteljes 4y ago
Very good list. As a daily user of /e/, I can attest to most of the concerns, which I agree are valid. Advanced Privacy is a major WTF. Using TOR without mentioning it is strange. And so is their all-or-nothing location faker tool. Sounded nice until I wanted to use a navigation app, which too got my fake location. Then I had to disable the faking, making my location available to all applications - quite a headscratcher. CleanAPK is another WTF baked-in dependency. I suppose they are running it themselves, just not in the open, because of copyright and other issues maybe? I don't know, they don't tell me, and why are we left guessing such an important thing on a privacy phone? An update also borked my phone, forcing it into a reboot loop. Granted, it was from 0.something to 1.something, but still, it was the next update in line, I thought the updater could manage it. Aside from these, I'm still a happy user of the system. I appreciate the degoogling effort over the mainline LineageOS. I'd like to have a question about DivestOS. Which device(s) do you regard as the main one(s)? I mean, which do you think will receive the most updates, the longest support, and so on? I'd wager the ones marked "Tested working" are the most healthy?
- _rdvw 4y ago
  Devices marked tested working are ones I have myself. But all devices receive the same monthly updates. If you're buying a device I recommend a Pixel 6/6a with GrapheneOS instead however.

by _rdvw 4y ago

josephcsible 4y ago

> - Enables Safetynet checks by default which downloads and executes obfuscated proprietary code from Google > - Includes proprietary Google Widevine DRM on nearly all devices While proprietary code, obfuscation, and DRM are all evil, if /e/OS didn't support these things, then a lot of very popular apps wouldn't work on it, which would make it a lot less viable as a platform. Refusing to do those things wouldn't result in any less of those evil technologies. It would just result in less /e/OS adoption.

npteljes 4y ago
Linux solves a similar problem sometimes by asking the user if they'd like that feature or not. I'd really appreciate that, of course, while understanding that all these need a lot of extra effort.
_rdvw 4y ago
My gripe is more so the outdated/insecure browser/webview, PDF viewer, and Tor daemon.

npteljes 4y ago

Very good list. As a daily user of /e/, I can attest to most of the concerns, which I agree are valid. Advanced Privacy is a major WTF. Using TOR without mentioning it is strange. And so is their all-or-nothing location faker tool. Sounded nice until I wanted to use a navigation app, which too got my fake location. Then I had to disable the faking, making my location available to all applications - quite a headscratcher. CleanAPK is another WTF baked-in dependency. I suppose they are running it themselves, just not in the open, because of copyright and other issues maybe? I don't know, they don't tell me, and why are we left guessing such an important thing on a privacy phone? An update also borked my phone, forcing it into a reboot loop. Granted, it was from 0.something to 1.something, but still, it was the next update in line, I thought the updater could manage it. Aside from these, I'm still a happy user of the system. I appreciate the degoogling effort over the mainline LineageOS. I'd like to have a question about DivestOS. Which device(s) do you regard as the main one(s)? I mean, which do you think will receive the most updates, the longest support, and so on? I'd wager the ones marked "Tested working" are the most healthy?

_rdvw 4y ago
Devices marked tested working are ones I have myself. But all devices receive the same monthly updates. If you're buying a device I recommend a Pixel 6/6a with GrapheneOS instead however.