357
The Fennec Android browser is currently behind on Firefox security updates, deemed unsafe by F-droid
(leminal.space)
If, like me, you've relied on Fennec as a more tolerable version of Firefox for Android, you may have gotten some bad news in the latest F-droid update cycle.
Fennec has fallen so far behind on updates that serious security patches implemented by Mozilla in Firefox haven't been applied to the fork, and Fennec is therefore still breachable.
The developer responded two weeks ago that they were "short on time", and there still isn't a new, secure version available. This appears to be due to that recurring weak link in open source development: small teams, confronted by real life demands like time and money?
Ah yes, the toolchain changes appear to be a stumbling stone for the Fennec devs as well. That kind of thing doesn't exactly speed up new releases, I'm sure.
What are your experiences with Mull? Is it generally compatible with Firefox plugins, and are there performance improvements as well as in security?
IMHO as i have it as my daily browser, it can become troublesome with booking websites (flights, tickets, hotels, restaurant orders, shopping). They don't like whatever Mull blocks, and at some point during any booking process you'll be unable to complete it. Sometimes during the payment step, so it can be... Frustrating.
I experience similar, if rarely, with my about:config modifications and muBlock add-on [edit: that was on Fennec, I expect similar on other Fenix forks]. Those things I blame more on the modern web than on any browser :/
I've been using it as my primary browser on Android for years so I don't really have much to compare it to, but I haven't had any issues with extension compatibility. It includes changes from Tor browser and Arkenfox so it's more privacy-focused than on performance.
Mull has defaults that improve privacy at the cost of performance and website compatibility. They maintain a list of changes that you can reverse through about:config. If Mull seems slow for you, consider re-enabling the JavaScript JIT.