91–100 of 137 posts
There were several privacy problems with this ROM, not sure if they corrected it. https://infosec-handbook.eu/blog/e-foundation-first-look/
Earlier quoted context omitted.
You exclusively post e-foundation related articles, don't disclose any affiliation with them, and call them "haters". Questionable.
HN Guidelines: > Please don't use HN primarily for promotion. It's ok to post your own stuff occasionally, but the primary use of the site should be for curiosity. shadowban plz
> Please don't post insinuations about astroturfing, shilling, brigading, foreign agents and the like. It degrades discussion and is usually mistaken. If you're worried about abuse, email hn@ycombinator.com and we'll look at the data.
Earlier quoted context omitted.
I don't think the graveyard of Android privacy forks is that big? All I can think of is CopperheadOS which died because it was company-backed. You could argue CyanogenMod died, though really it's still well alive in LineageOS. (and CyanogenMod wasn't really privacy-focused) I have a very high respect for all the work that's been done on the various GNU/Linux mobile distributions, but it's still so far away from Andro…
CyanogenMod, as the name suggests, was explicitly a nod to add in features that didn’t exist before. That was indeed a losing battle because Google has far more resources to add features ans beat CyanogenMod. On the other hand, a de googlized and privacy focused platform provides something that Google can never provide. There’s also a change in the environment surrounding all Of this. Thanks to the weaponization of A…
/e/ is mud among the LineageOS community (which is upstream of it), due to several reasons. Sadly I can't find the relevant /r/lineageOS posts . Here's some reading that covers the basic points though: https://intangiblesheep.neocities.org/rants/eelo.html https://web.archive.org/web/20191224031946/https://ewwlo.xyz...
The problem with the article is a semantic one but it should not be overlooked. /e/ “believes” in open source. Less along the lines of “concerns itself with every philosophical checkbox”. IMO you and the author are filling in the blanks as you wish, landing in the realm of no true Scotsman. Freedom to create as one would > flocks of sheep. Personal emotional religion must take a backseat to suggesting folks discuss o…
Earlier quoted context omitted.
Thanks for posting this. I spent some time looking at how "de-Googled" GrapheneOS is. If you define "de-Googled" as meaning the phone makes no connections to Google servers that you do not explicitly acknowledge/permit, then GrapheneOS is still far from "de-Googled". Just to give one example, SUPL. There are also plenty of unGoogled-Chromium patches GrapheneOS doesn't apply. I'm not saying GrapheneOS isn't way better…
You don't have to use Vanadium on GrapheneOS, I use Bromite (mostly for the ad blocking) and there's also an ungoogled chromium available in FDroid.
One of the things that feels a bit problematic here - the webpage is avoiding mention of the fact that this is still Android. In essence, this is still Google's OS and the team has decided to start a fight against Google by taking their opensource and perpetually fight against the main developer by removing their proprietary component. I don't think this is a fight that's sustainable - a giant graveyard of Android pr…
"Since our OS runs on a totally deGoogled Android" Was that added to their site after you wrote your comment?
One of the things that feels a bit problematic here - the webpage is avoiding mention of the fact that this is still Android. In essence, this is still Google's OS and the team has decided to start a fight against Google by taking their opensource and perpetually fight against the main developer by removing their proprietary component. I don't think this is a fight that's sustainable - a giant graveyard of Android pr…
What I seek in a phone is control over my privacy, not necessarily a vegan FOSS system.
What that means is things like:
- Fine-grained control of permissions to apps (e.g. access to rear camera only, access to only city-level accuracy of locations, access to read from only directories I specify)
- For apps that insist on having permissions to things like location and wi-fi scans to use them, the ability to make the app think it got said permissions, but receives fake data. And no, Android's mock location feature doesn't work, because apps can check if the feature is enabled or not
- The ability to fake IMEI, phone number, contact list, installed apps, and other identifying data
- Ability to generate fake IMU, proximity, temperature, barometer, and all other sensor data that could conceivably be used for fingerprinting
Earlier quoted context omitted.
PureOS is trying to use desktop apps instead and fit them to the phone screen ("convergence"). I think it is a viable strategy.
The thing is, there aren't any desktop apps—much less Linux desktop apps—for the types of things I need to do on my phone. On an Android phone, I can buy train tickets (NJTransit), deposit checks (Chase), and have telemedecine appointments with my doctor (MyChart). I don't know if all of these would work in e.foundation, but presumably at least some would run.
Custom AOSP apps can be supported via Anbox on upstream linux.