9 ms·
/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 re
by Qwertious 6y ago
/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://intangiblesheep.neocities.org/rants/eelo.html
https://web.archive.org/web/20191224031946/https://ewwlo.xyz/evil.html https://web.archive.org/web/20191224031946/https://ewwlo.xyz...
- cookiengineer 6y agoI kinda agree with the sentiment in the articles from an AOSP/lineage/cyanogen perspective. They should definitely embrace the Telegram FOSS fork [1] and OSMAnd~ [2] (which is a superb offline navigation tool btw) and remove all Apps that require the Android 10 firebase hockey-based notifications. [5] and [6] A lot of apps use this for convenience and because it was _required_ since AOSP 10 but there are ways to work around that requirement with a high priority notification. I would additionally recommend to use AppWarden [3] and Blokada [4], because both are amazing additions for an Android device. Firefox for Android, though, is still a nightmare with all the telemetry. The old TOR Browser 9.5 series is based on old Firefox pre-quantum, 10 is based on Firefox post-quantum. The issue with current Firefox and TOR Browser is that Mozilla decided to include the Adjust-, Firebase- and LeanPlum-SDK which introduce now more user tracking than ever before. You'll even sometimes see different A/B UIs based on your browsing behavior (not kidding) and geolocation, and of course this happens more often with Orbot being used as a Proxy. (You can verify this via AppWarden if you don't trust me) [1] https://github.com/Telegram-FOSS-Team/Telegram-FOSS https://github.com/Telegram-FOSS-Team/Telegram-FOSS [2] https://github.com/osmandapp/OsmAnd https://github.com/osmandapp/OsmAnd [3] https://gitlab.com/AuroraOSS/AppWarden/ https://gitlab.com/AuroraOSS/AppWarden/ [4] https://github.com/blokadaorg https://github.com/blokadaorg [5] https://github.com/Telegram-FOSS-Team/Telegram-FOSS/blob/master/Notifications.md https://github.com/Telegram-FOSS-Team/Telegram-FOSS/blob/mas... [6] https://developer.android.com/guide/components/activities/background-starts https://developer.android.com/guide/components/activities/ba...
- dessant 6y agoThose SDKs have indeed no place in Tor Browser, though at least they appear to be disabled. Have you witnessed Tor Browser sending telemetry data to these services on Android? https://gitlab.torproject.org/tpo/applications/fenix/-/issues/40077 https://gitlab.torproject.org/tpo/applications/fenix/-/issue...
- cookiengineer 6y agoThe issue I have with their response is that they argue that it's disabled because it has no API key. I think that's not a real solution because that can change at any time. A request sent is a request sent, relying on the server to block it is the opposite of what TOR initially stood for. I witnessed at least the Leanplum SDK taking action, and I thought I broke the App tbh. After a restart of the phone and clearing all caches via the Settings App I could verify that it happened a second time. But I have no idea whether it was a "chrome://" Page with an externally included JS - or triggered by the underlying SDK directly. In Firefox pre-quantum (pre fenix 9.5), the Extensions Page included Google Analytics for a while, so I was assuming that my installation process of uBlock Origin and uMatrix triggered it somehow down the line. I decided to roll back to TOR 9.5 after it happened the second time on the same day and now I'm building my own Browser (Tholian Stealth) anyways... so I didn't decide to investigate further than a casual look at the codebase where LeanPlum still seems to be littered all over the place. [1] [1] https://gitlab.torproject.org/search?utf8=%E2%9C%93&search=leanplum&group_id=477&project_id=478&scope=&search_code=true&snippets=false&repository_ref=tor-browser-83.0.0b2-10.5-1&nav_source=navbar https://gitlab.torproject.org/search?utf8=%E2%9C%93&search=l...
- dessant 6y agoThanks for the details, I think this should be properly investigated, and if you find any request to telemetry services in Tor Browser, your findings should be made public.
- SubzeroCarnage 6y ago> he issue with current Firefox and TOR Browser is that Mozilla decided to include [...] Those are all completely stubbed out in Tor Browser Android. I helped with some work on that a few years back.
- noTrueScotsman 6y agoThe 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 or use their time otherwise.
- bigbubba 6y agoWhy create a novelty account just for this comment? It's not like you're discussing anything sensitive.
- nuand999 6y agoThose documents are pure FUD from haters. Look at this article: https://www.indidea.org/gael/blog/2020-and-the-minority-spreading-hate-and-fake-news/#more-1379 https://www.indidea.org/gael/blog/2020-and-the-minority-spre...
- ev1 6y agoYou exclusively post e-foundation related articles, don't disclose any affiliation with them, and call them "haters". Questionable.
- greenshackle2 6y agoHN 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
- dllthomas 6y agoHN Guidelines: > 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.
- bigbubba 6y agoHaving now read both, your link does not seem to address any of the claims in the GP's links.