ToDo: diffs FF125.0.1-FF126 #1842
Comments
some bugzilla tickets
|
|
for the record ... I drink and I know things click me for proof
|
|
@jonaharagon - just going to mention this here, rather than create a new issue or whatever https://discuss.techlore.tech/t/i-want-to-like-mullvad-browser-but/8826/3 So for the last 8 months we (MB/rui/me) have been talking about how (to kill arkenfox and) improve MB (and TB). It's important that MB/TB share the same code, otherwise if it gets too divergent it becomes untenable for all parties (MB being a sponsor and all). TB has also been re-doing the design spec, and a large chunk of this is dispelling/removing the myth that they can prevent anything ever touching the disk (impossible, since the OS controls a lot of that). This leads into discussion on allowing passwords (talked about for over a year) and other measures to allow some disk if the user opts into it. And in fact, after a recent chat, I've come to a conclusion that both MB/TB should start in normal mode - and it was spoken about to some degree in Portugal two weeks ago at the annual tor meetup (I was there), but not in a session and I missed it - or richard simply got around to logging some issues. But anyway, there's a lot of work for this to happen (such as anything touching the disk such as cookies need to be encrypted per session with a memory only key, but not site exceptions .. dealing with service workers, etc). A lot of things to work through - e.g. do we need to encrypt anything on disk if the user opted in? edit: also rui was looking at using profiles, and there is an installable version of MB coming for windows/mac which helps with flicking between profiles - i.e one profile is start in normal mode, the other is PB mode - but I argued against this - it's just an option But FYI: |
|
It has been very clear for some time that if you can't use a browser by default, based on your requirements (and they vary wildly based on your usage, threat model, personal habits, etc.), the added friction will push you to use your other browser more and more. This is why for example with Mullvad VPN, we start from the point of view that your VPN should always be on. And then you can have an escape hatch, using the split tunneling, because unfortunately there are situations where using a VPN will stop you from doing what you need to do online. We are approaching the browser space with Mullvad Browser in a similar way. On one hand we want to improve how well internet works while keeping the privacy focus and model which makes Mullvad and Tor Browsers differents. How it will look like and how it will work is not fixed (and improvements will most probably happens incrementally), because we need to make sure it's technically sound, user friendly and future proof. |
|
thanks rui meanwhile, you can all use ... and MB |
Is that something that could happen soon (next year or so)? Cause MB is not yet packaged on alpine linux and it would probably take some time to get working. |
my best guess is that nothing will happen with AF until at least the next ESR, i.e after 128, so FF141 or something - and given how super stable it is, that's where I would stop (if MB was So worst case scenario you could used ESR141 and be fine for another 2 years from now, or longer if you use stable release channel and as per usual, nothing ever changes that matters - and I could always do an occasional update, maybe - you have lots of options |
FF126 release date: May 14th 2024
FF126 release notes
FF126 for developers
FF126 security advisories
89 diffs ( 48 new, 24 gone, 17 different )
removed, renamed or hidden in v126.0:
changed in v126.0:
08070604ignore
click me for details
==NEW
==REMOVED, RENAMED or HIDDEN
==CHANGED
The text was updated successfully, but these errors were encountered: