Your browser engine is very easy to identify, it would be useless to lie and it would also cause a lot of breakage.

What do you mean by this? It already reports Linux in the navigator UA, are you talking about the HTTP header? If so, I agree with you and I’m hoping to see a change as it is overkill (although there are reasons against namely passive fping protection in some rare cases).

It causes breakage too, ideally reporting this could influence a change in RFP but there are some blocking issues (things to discuss) at the moment and it is low priority. We could anticipate the change with a patch but we haven’t thought about this yet as we are usually against changing RFP.

I shared this a while ago in the Firefox community --> https://lemmy.ml/post/209597

see y’all there, I updated the lemmy sidebar already :-)

Mull is super nice and its dev does a lot of good open source stuff, recommended!

2mo later I gotta say I’m sorry that I haven’t been able to keep up with lemmy (or even worse with reddit where I haven’t logged in ages) lately, I’ve been pretty busy to the point where even release announcements disappeared.

indeed it does, but most people wouldn’t really care in 2023.

https://librewolf.net/docs/faq/#will-you-provide-an-android-version-of-librewolf

https://librewolf.net/docs/testing/ says:

These tests are not intended to be used as oracles, but rather as a way to check your setup and verify that your changes are applied. You should not read too much into the results unless you are sure you understand them, as explained in this article.

https://blog.pastly.net/posts/2019-01-19-about-to-use-tor/#testing-your-fingerprint

BTW I commented about this in the past, see https://gitlab.com/librewolf-community/browser/windows/-/issues/276#note_1137125815

it’s covered, yes. we enable a built-in list that strips some query params and we also add an extra one that strips more stuff (courtesy of the great https://github.com/DandelionSprout).

btw Firefox also has native query stripping now, so there’s one extra layer of protection! see https://privacytests.org/

one more, we setup a codeberg mirror as well.

oh I forgot: LibreWolf was ported to freebsd too!

your browser finger print will change

it’s about the traffic fingerprint more than anything IMO; for example, to an external observer it would be very obvious that some domains are not being loaded.

it’s worth noting that all Tails users look (looked? IDK if they still ship uBO with TB) the same as they all had uBO included, so Tails had their own user bucket.

Dark Reader can be detected, if not from the injection at very least from the fetching behavior. the creator of the extension states this very clearly on Github:

• https://github.com/darkreader/darkreader/issues/2385#issuecomment-619629021
• https://github.com/darkreader/darkreader/issues/3274

as you already said, extension that alter the traffic fingerprint (eg. ad-blocker or things like LocalCDN) are rather easy to identify. however I wouldn’t go as far as saying that’s an actual issue with the ad-blockers themselves: they do their job, they are just not adequate when you try to fit into a crowd hence when using tor browser; I guess the same can be said about Dark Reader: the extension is doing it’s job, there’s just no way for it to hide.

tldr: extensions can be detected and there’s no way around it. while it doesn’t make them bad in general, maybe don’t use them with TB.

this extension is glorious

I still think enumerating badness (eg. blocking trackers) is not a final solution. it’s nice to have, but it should be only an initial level of protection.

also, strict mode blocks known fping scripts so arguably you don’t need extensions for that, a nice plus :-)

one of the most important changes for privacy that firefox ever made, I hope people realize this. huge win for all the users!

when did you last use it? it hasn’t been that way for me in ages.

also -> https://blog.torproject.org/congestion-contrl-047/

I don’t have the same issue and I update daily as I’m using Nightly, weird.

relevant -> https://lemmy.ml/post/209597

I would also argue that the about config changes he points to are a bit…meh