I'd be more worried about how long that flag is going to work. And how long is it going to take us to realize the flag isn't working.

I would still suggest folks to at least go through Librewolf's FAQ and Docs. For example, Librewolf disables DNS over HTTPS by default. See https://librewolf.net/docs/faq/#doh-whats-the-stance-on-doh

If anyone reading this is not configuring their DNS on their routers or on their Linux machines using systemd-resolved or something similar, I suppose they should probably at least configure their browser to use DNS over HTTPS. It should be better than using the default DNS resolver provided by your ISP.

As far as I'm aware, Librewolf's team isn't making significant changes to Firefox's code or "patching out" some spooky telemetry. Librewolf is essentially pre-configuring a bunch of "privacy" and "security" related settings in Firefox for their users. But alternatively any user can configure these things themeselves and make their own choices. Even pre-installing extensions and add-ons on fresh Firefox profiles can be easily done by any user using Firefox policies (which is what Librewolf uses to pre-install Ublock Origin.) But let's say you also want another extension like Bitwarden to be pre-installed on every fresh Firefox profile. Or you don't trust DuckDuckGo and instead want to configure Firefox to use a self-hosted SearXNG instance as your default search engine. Then maintaining your own Firefox policies can help you do all this.

I understand it is far simpler and far more desirable to have "privacy and security" out-of-box without having to configure anything at all. But it is probably not a bad idea to take the time to see what configurations you can make to Firefox yourself, even if you decide to use LibreWolf. You may end up wanting your own configurations in addition to what Librewolf's team decides for you.

some are subcomponents of the main disabled feature. i checked this on my browser which was only modified by GUI, and nothing i saw 'enabled' was actually enabled, but instead a subfeature of what I had disabled.

Xbrowsersync for bookmark syncing. Works across browsers. A real password Manager, like Bitwarden, for passwords.

For sending things to devices I use KDE Connect. I realize it is a fundamentally different application, but it is what I use generally to send / receive links between devices, as well as documents, images etc. It also is good for notification mirroring, and really just integrating Android devices into Windows / Linux computers.

For passwords I used KeePass (and I sync them between devices with SyncThing), but I usually recommend Bitwarden (which is what I used to use). Both are open source, have apps for all platforms, can integrate into your browser if you choose. The main advantage of Bitwarden is that it is open source, all necessary features are free, and you can host the server yourself if you want. It also integrates into some services, notably email aliasing ones, to allow you to generate new emails every time you make a new account.

For bookmarks / history your best bet is the extension everyone else is recommending here!

Oh sure, but browsers are an entirely different beast.

Eventually, they'll take it closed source, now I know what you're thinking "Then one of the forks will just become the dominant one!"

But here's the thing, the browser engine is very complicated just to keep up with. The W3C spec that all engines must follow is thousands of pages long. So all those forks will wither and die once the engine has been cut off from upstream updates.

None of those forks touch the engine as-is

I mean, FOSS doesn't prevent this on its own. We should probably all switch to LW and try to keep an eye that those telemetry settings don't become disabled upstream.

Also of concern would be anyone using Firefox accounts and sync.