Yeah... It's a bit hard to balance things like this though, I've seen lot's of folks complain about how their Firefox is apparently "broken" because it now suddenly has this empty margin around web-content seemingly wasting space for no reason - and then it turns out that they have deliberately turned this very feature on. And that is even if the feature is completely hidden - I wonder how many more complaints there would be if options like this are made more accessible.

The letterboxing feature has been in Firefox since 2019 - starting from Firefox 67 I think. The preference for it might have been hidden though so maybe it's just relatively unknown feature - I don't know if or how visible LibreWolf makes makes it for the user. But regardless, any modern Firefox variant probably has that capability.

Sounds like you are talking about Firefox's letterboxing feature which you can enable/disable independently from full fingerprinting resistance.

I'm not sure if resistFingerprinting does anything to stop websites from uploading whatever data they can get though, I don't think it does that. And I don't think it could really do that in the first place since the website could just obfuscate the data and browser wouldn't know what is sent.

That's not necessarily a good solution either, because a service could figure out that the source of random fingerprint data likely comes from the same user. Especially if your ip is not changing. It might perhaps be effective if a substantial amount of people were doing it though.

But to generate such random fingerprint is difficult because it consists of many parts and services don't all build fingerprints the aame way. You could easily randomize e.g. canvas data, but the issue is that if you only randomize one data point then that one random data point pretty uniquely identifies you if your other datapoints are stable. So to be effective you would really need to randomize several different datapoints and that may not be such an easy task since websites could build them in all sorts of ways.

Yeah, regular http cache is indeed a thing. However it's more complicated because the web server can tell the browser how the returned content should be cached - if at all. So if, say, reddit servers ask the browser to not cache particular resource (for whatever reason) then it won't be cached. I mean, the browser is free to do as it pleases, but I think in general browsers would do as the server asked and indeed not cache it.

Absolutely not. If anything, public officials would be the one group whose messaging I would understand being scanned so that the people can sort of keep them on check. But again, implementing such possibility that would still weaken security of everyone else as well so of course it should not actually be done.

Yes. I want to have access to both history and bookmarks on all my devices and send specific tabs to other devices. Sync makes these super convenient.

Right, but then you shouldn't be shocked to find out that a feature was removed because nobody seemed to be using it.

If a website has a compatible PWA manifest the there will be an item labelled "install" in the three-dot menu of Firefox in place of usual "add to homescreen" item.

Edit: There's a few other requirements as well for the website to be considered installable as PWA, such as it must have a registered service worker so it can work offline. But regardless, if the website provides all the requirements then it can just be installed straight from the menu.

Unfortunately by sending DNT you are merely suggesting to the server that you wish to not be tracked. There's no requirement for the server to actually care about you at all.

Now, if DNT were actually legally binding though - that would indeed be very cool.

None.

I don't think it's a good idea to take some huge collection of prefs and just apply them blindly.

Instead, make the changes that you actually want to do, so that you actually know what changes you are causing. If you want to put those into your user.js file then feel free, but in my opinion it's just better to change them in about:config directly - that is, unless you need to apply the exact same set of changes to multiple profiles.