I'm using /e/ for ~2 years and even contributed to it a bit. All listed controversies were basically about "they say degoogled, but not degoogled enough", mostly because LineageOS still has quite a lot of Google code in them. For example you can't remove Google 204 connectivity check... until you implement your own, which /e/ and GrapheneOS did, but LineageOS didn't. GrapheneOS developer is however an arrogant dick, so I've stopped using it and settled with /e/.
The problems of the connectivity check is debatable. It doesn't send any data, just makes a get request
Don't really see how that data could be useful to Google or tied to anyone/any unique device
Using something else makes you stand out significantly on the network you are using, as next to nobody uses something different.
@amolith
You're right about the priorities, which is precisely why I guess neither LineageOS nor /e/ made a big fuss of it. But then you had the wave of people making a whole scandal based on this, humbly described above as "some privacy concerns" π
As for 204, Google gets your IP and User-Agent as minimum, and I agree that people have right not to want to share this with them. And "standing out" assumes you're under DPI, which is a rare threat scenario.
@kravietz @amolith cool, so are you happy with #efoundation ?
@amolith they do have #fairphone with their system preinstalled.
we have 1 #fairphone here. quite alright but also large & a bit heavy
Still like the idea if running 2 sim plus sdcard.
#fairphone itself runs your data, when you order, through many 3rd party services. They are definitely not fair & respectful to the data of the clients. typical #startup mentality π
@kravietz
Thanks.
My #lineageos Rom is unofficial giving headache with updates.
It /e/ is better maintained, this is my thing until #linux on phones kicks off.
Do banking apps run on /e/ ?
@amolith
@kravietz @amolith
Think Fairphone contracted out development of the operating system for the Fairphone 3
Verified boot implementation is a big fail. Uses test signing keys. EDL left open.
https://hub.libranet.de/wiki/and-priv-sec/wiki/verified-boot
(Note theres two sections on FP3 in that)
Think theoretically this could be fixed if old/new devices had keys flashed by EDL.
That would break current /e/ for FP3
Doesnt fill me with much confidence as to the quality of the implementation of the rest of device code/security