-
-
Notifications
You must be signed in to change notification settings - Fork 384
browser-recommendation: suggest Firefox ESR instead of Firefox #881
Conversation
Deploy preview for privacytools-io ready! Built with commit 5195f98 |
Mozilla info:
|
2 grammar suggestions, and one clarity-suggestion:
Could also say "in a timely fashion" but I think "promptly" is clear enough. p.s. I am not sure I agree with the idea motivating this pull-request, see my complaints in the https://github.com/privacytoolsIO/privacytools.io/issues/856#issuecomment-486396539 thread-comments. Grammar suggestions should not be interpreted as, me thinking this is ready to push live :-) They are just grammar suggestions ;-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’d like to see the suggestions @five-c-d recommended implemented first, the wording here is kinda strange.
The wording makes sense, just, our American ears require more of a midwestern-diaspora dialect, or something :-) Grammar is not that important in the blurbs, people care about the recommendations themselves more than the verbiage, although, might as well tweak it I guess. real reason to comment was the 'backport' thing, I think it matters
The reason I even brought up grammar-fixes at all, is I think the 'backporting' word is the only thing that needs clarification: the security-fixes in firefoxESR are promptly backported from the stable-rolling-release (or from the alpha-channel-rolling-release more likely), is a very important distinction. FirefoxESR does not add new features (like Waterfox and to some extent TorBrowser and very much so PaleMoon), so the backports are extra-clean extra-well-vetted. Lots of eyeballs have looked over each security-fix-backport, because generally speaking if there is a security-hole in firefoxESR there is also going to be a security-hole in firefox-rolling-release-stable, and for the most part vice versa, the exception being super-new features only found in rolling-release. The same cannot be said of the soft-forks which are more than very-light-ESR-type-soft-forks, because they add features. Prompt security-patches to the Waterfox-specific portions of waterfox might occur, but there are a lot fewer eyeballs on those Waterfox-specific portions. There ARE not any firefoxESR-specific portions, that I'm aware of, because it is just a frozen-in-time v60 flavour of firefox-rolling-release, plus security-fix backports.
This I am not thinking is a good idea. Well, at least, the part about Klar. keep recommending TorBrowser&maybeOrbot APK as now 1A, keep recommending braveBrowser as now 3A, but suggest recommdending firefoxFocus as 2A rather than firefoxKlar which is less-field-tested and FDroid-wedged at present
Currently there are three browsers: 1) TorBrowser the soft-fork-of-ESR-which-is-very-lightly-forked-stable, 2) Firefox stable-channel, and 3) BraveBrowser soft-fork of chromium these days i.e. not muon/electron anymore. So privacyToolsIO is already recommending TorBrowser and BraveBrowser, on whatever platforms they support, including mobile flavors. After this commit is pushed, there will be the difference that 2) will become FirefoxESR the very-light-soft-fork-of-stable. There is no android APK for that, and no iOS either. TorBrowserAlpha on android cannot be a slight soft-fork of FirefoxESR (like TorBrowser on desktop-platforms which benefits from IBM and Canonical and Oracle and so on cooperation on backporting), and moreover, is in alpha. BraveBrowser on android probably functions fine, but I don't like using a chromium-based browser on an AOSP-based LineageOS because that is putting all the security in the google-basket, effectively (even if sans-gApps sans-playStore the OS and the browser are both still soft-forks of google-controlled upstreams). We could keep recommending firefox-rolling-release-stable version (with addons and tweaks and such) for android and ios, where it is fully supported, and recommend firefox-esr on linuxDesktop/osx/win7 systems where it is fully supported. The downside there is that org.mozilla.firefox v66 contains LeanPlum analytics and AdjustSDK, although fairly benign utilization arguably. Rather than firefoxKlar (see notes below on stuck-ness), my recommendation would probably be firefoxFocus, which drops LeanPlum and drops a couple dozen permissions as well (many of them excellent things to drop like 'CAMERA' perm). The main downside to firefoxFocus is it still includes AdjustSDK tracker in the APK -- the code for the SDK is libre-licensed however -- and it also uploads all URLs visited to GoogleSafeBrowsing, to help prevent endpoint-pwn'age (privacyToolsIO website recommends an about:config tweak to disable that though). You can get the firefoxFocus code on github, the firefoxKlar variant is on F-Droid proper,
This is the helpdoc from 2017 explaining that firefoxFocus uses adjustSDK for "install-tracking" to determine whether the enduser installed "due to an advertising campaign of mozilla foundation" or not, and firefoxKlar does not have adjustSDK tracker. 2017 complaints about AdjustSDK == https://www.ghacks.net/2017/02/12/firefox-focus-privacy-scandal , early 2018 complaints about AdjustSDK, https://chefkochblog.wordpress.com/2018/05/25/firefox-focus-the-privacy-browser-which-collects-and-sells-your-data/ , note that the 'event tracking' stuff was removed from both firefoxFocus and firefoxKlar in ~v3.3 but the 'install tracking' stuff does still exist. There was a shift in the firefoxFocus-slash-firefoxKlar implementation a few months ago, it now uses GeckoView, and the F-Droid folks are stuck on firefoxKlar 6.x of August 2018 due to build-related difficulties, upstream is at 8.0.9 nowadays. IzzySoft There is also a firefoxFocus4ios, which has good review-ratings, 18k reviews and 4.8 rating. Like on android, firefoxKlar4ios has lower review-count and lower rating, 4k and 4.7 today. Not sure if the tracker-situation is the same over on the ios flavour, I'm only familiar with android APK tracker-detecting-websites. In particular, it looks like the firefoxFocus for iOS is available on the english-language itunes store, but I'm only finding firefoxKlar for iOS in the german-language portion? https://itunes.apple.com/de/app/klar-by-firefox/id1073435754?l=en&mt=8 So there are some headaches associated with firefoxKlar that don't seem to impact the upstream firefoxFocus (of which firefoxKlar is a soft-fork). My understanding is that firefoxFocus is not really a soft-fork of firefox-stable-rolling-release, it is a project off by itself in most ways (similar to the early days of firefox when it was "a project off by itself mostly-distinct from the huge hulking mozilla-browser"). However the recent upgrade of Focus&Klar to use the GeckoEngine means they are partial-soft-forks now of FirefoxStable APK But I think either firefoxFocus with 1 install-time tracker, if the audience is everyday folks, or firefoxKlar if the audience is hardcore privacy-folks willing to go the extra mile, is important.
I searched a little and did not find any issue-number for DuckDuckGo browser (nor for FirefoxKlar-versus-FirefoxFocus either). I think the only other option is the older DolphinZero browser, maybe? IzzySoft lists it as zero-tracker, but I don't know if it is any good, I've never heard of anybody using it. Not sure it is libre-licensed either. |
@five-c-d "FirefoxKlar-versus-FirefoxFocus": Klar has no trackers, Focus has something (I don't remember what). Klar is really quite barebones – OK for the "quick link" you open from some mail/chat/whatever, but not a "daily driver" with bookmarks etc (this matches Focus as well; the two are mostly identical, just Focus has some telemetry and something other, IIRC).
I haven't tried either. Both were in my repo initially, until Klar was ready and moved to the official F-Droid repo. Later I had to remove Focus as well, as it became too big: it reached 50M+ already due to including Gecko now (initially it was using webview), while my repo allows for ~20M per-app. Oh, Focus also comes with one tracker, Adjust, as you can see here at Appbrain – which makes it implausible to me: you cannot say "my product is focused on privacy", and at the very same time integrate trackers into it. |
Although they are all disabled, Orfox has four trackers :-) because it is/was a fennec-soft-fork. Orbot has zero, and the alpha TorBrowserAndroid has zero ... but it is not well-vetted code yet. BraveBrowser for android has zero trackers, but is soft-glued-to-google in your IzzySoft listings -- and needs a lot of permissions. And is chromium-based so "more risky" in some sense than something not forked from google-upstream. But most importantly I believe it only works with android7+ so older devices cannot use it if they are still running android 4/5/6. FirefoxKlar has no trackers, but FDroid is two major versions behind (the Gecko engine thing that caused you to evict Focus from your custom IzzyRepo), and FirefoxFocus has one tracker, AdjustSDK, and they claim it is used just once at install-time (back in 2017 timeframe both Klar and Focus had the tracker and used it at install-time AND also at runtime for 'event tracking'). I believe if you installed Orbot first, or TorBrowserAlpha first, and then used either of those to install FirefoxFocus, it would blind their install-tracker :-) But for everyday endusers that are only comfy with clicking on playStore and using the playStore app this might not help. Like braveBrowser for android, FirefoxStable APK is a daily-driver type browser, which has two "fairly benign" trackers: AdjustSDK like Focus, and also LeanPub -- see my comments inside the collapse box "suggest recommdending firefoxFocus as 2A rather than firefoxKlar" up above. |
I wouldn't recommend BraveBrowser for privacy reasons (it looks a bit weird to me, as they just replace the ads) unless you are sure it does no tracking etc. Might be good if you want to get money for browsing (and don't care about probably paying for that with your data; not sure about this part, though) – and the "nagging part" might be minimized. But as long as you cannot validate the code, you cannot say what tracking might be in. As for the (minimum) Android version: when at a desktop browser, simply hover your mouse over the app's name and it will tell you.
FirefoxKlar is the German variant of FirefoxFocus (the two share the very same Github repo) – so basically it is a "special build variant" shipping Focus without trackers. So yes, it absolutely makes sense that the German variant is available in German only 🤣 As for being behind in F-Droid: most likely waiting for Fennec, so the Gecko stuff is built. That's a rather complex task I've been told. |
IzzySoft has a comparison of a few dozen browsers... so yes, over there you can hover to see the minimum android-version. But privacyToolsIO has just three browsers: torBrowser which is alpha on android, firefox-or-maybe-firefoxESR if this pull-request is committed, and braveBrowser which is minimum-android7+. I think that android7+ problem, and that alpha-or-4disabledTrackers problem with TBB/Orfox, is reason enough to explicitly recommend either Klar/Focus/Stable flavours of firefox-on-android&ios here in the listings. @Mikaela was originally arguing for FirefoxKlar, and I think that is fine as long as the enduser wants a non-daily-driver browser and is savvy enough to figure out how to get it installed (german itunes repo and outdated fdroid repo and other headaches). FirefoxFocus is a bit less headache to use, and very similar to Klar except for install-tracker via AdjustSDK and (maybe) SafeBrowsing on-by-default, which I think is a good tradeoff. If they need a daily-driver browser on smartphone though, only FirefoxStable with two trackers, and BraveBrowser with zero-detected-trackers-according-to-exodus (not the same as NO tracking of course!) are the only "one-wizard-of-hassle" options. BraveBrowser has the advantage that they proxy SafeBrowsing via their own braveServer to keep google from getting every URL visited, but without leaving the everyday enduser insecure. But yeah, there are a lot of controversial aspects to BraveBrowser -- the advert-swap-thing is off-by-default, which helps, I guess.
I think the client-side portion of braveBrowser is 100% libre, is that NOT true? |
I wonder why nobody say one word about Fennec: Fennec F-Droid (Browse the web) - https://f-droid.org/app/org.mozilla.fennec_fdroid It's F-DROID build of Firefox but removed a lot telemetry and other shit. |
Wording changed.
I didn't remember it exists, the only Firefox with updates outside of F-Droid used to be Nightly. But there probably should be a different issue for mobile recommendations anyway. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems fine, UX-wise, but I'm hesitant to "Approve" without seeing the Firefox discussion finalized, and I'm still not convinced moving our recommendation to ESR is necessarily the best option.
You want to split out the browser-section into a top3 recommendations for desktop, and a separate area which has top3 recommendations for mobile? That is how the OS area already works... and actually, there could be a separate top3 for portable-browsers, I guess, to mirror the LiveCD stuff? I would agree that is logical, but I don't think there are enough web-browsers to fill the listings. At the moment, there is only the one listings-page related to browsers, and it does not have any worthMentioning options. FirefoxStable is on all major platforms, BraveBrowser is on all major platforms, and although TorBrowser is only officially available on desktop-platforms (since it is a soft-fork from firefoxESR which is only on desktops), the TorBrowser listing explicitly links to alpha/unofficial versions of TorBrowser for android and iOS with direct links.
If we change from firefoxStable in the second slot to firefoxESR in the second slot, my expectation is that we need to link to firefoxFocus / firefoxKlar / firefoxStable-for-mobile / or maybe firefoxFennec (there is an fdroid-flavor but not a playStore-flavor except for Nightly-aka-Aurora which is unsuitable for normal endusers) from the ...Android, iOS... portion of the firefoxESR slot. Per the arguments made above, I think firefoxFocus is probably the correct pick since the firefox-in-slot-two is primarily intended for people that could not stomach the somewhat-higher-difficulty of TorBrowser in slot-one. Klar is a little too much hassle, and fennec way too much hassle, to get installed methinks. I'm not against linking to them, but think they should be in WorthMentioning, rather than highlighted in the top3 portion. |
#858 is closed so I guess there is no point keeping this open either. |
I wonder if this could be a compromise suggestion to #856 as with ESR the potentially privacy invasive updates also come more slowly and may in some cases be cancelled before they reach the ESR branch.
Problem: I don't think ESR exists on mobile Android and iOS.
Solution: Having different browser recommendations for those platforms such as Tor Browser (Alpha), Firefox Klar or DuckDuckGo (give me issue number please) and Brave?