fishonthenet

joined 3 years ago
MODERATOR OF
[–] fishonthenet@lemmy.ml 1 points 1 year ago

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

[–] fishonthenet@lemmy.ml 1 points 1 year ago

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.

[–] fishonthenet@lemmy.ml 1 points 1 year ago

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

[–] fishonthenet@lemmy.ml 1 points 1 year ago

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

[–] fishonthenet@lemmy.ml 4 points 1 year ago (1 children)

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

[–] fishonthenet@lemmy.ml 1 points 1 year ago

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.

[–] fishonthenet@lemmy.ml 1 points 1 year ago

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

[–] fishonthenet@lemmy.ml 2 points 1 year ago

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

[–] fishonthenet@lemmy.ml 2 points 2 years ago

hello! since we don't have a paid Apple Developer license there's not really a workaround.

I also wrote a FAQ entry that I'll leave for others since it seems like you already understand the issue --> https://librewolf.net/docs/faq/#why-is-librewolf-marked-as-broken

[–] fishonthenet@lemmy.ml 2 points 2 years ago (1 children)

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/

[–] fishonthenet@lemmy.ml 4 points 2 years ago (1 children)

one more, we setup a codeberg mirror as well.

 

hello! as you might have noticed I haven't been able to post the changelog lately, so I figured I'd write a news thread:

  • as usual we released a new LW version for each FF stable.
  • I just added a bunch of documentation entries, most notably:
    • accessibility and why you might want to disable it, even though we don't by default.
    • how to use KeePassXC when you install both it and LibreWolf as Flatpak.
    • how to install uBO if you're in a country where the addons store is blocked.
    • full list.
  • WebRTC should work a bit better now, you should experience less breakage.
  • we maintained our usual set of patches across each release.
  • this epic contains a bunch of solved issue we have been ironing out during the past few release cycles.
  • in the next release we finally expect to fix the weird new tab issue on linux and the unresponsive window issue on macos; this was possible thanks to a contributor from the community who found a typo in one of our patches :-)
  • there's a known issue with Firefox Sync logins.

if you have any question just ask 🐟

13
submitted 2 years ago* (last edited 2 years ago) by fishonthenet@lemmy.ml to c/librewolf@lemmy.ml
 

hello folks, v107.0 is rolling out on all platforms, if it already hasn't :-)

main changes:

  • rebased to latests firefox;
  • updated patches.

very minimal but enjoy!

 

from that issue:

I'll be stopping providing new LibreWolf builds, and it's possible I'll abandon the port altogether in the near future. So, unless I'll find someone who will take care of the port, it would be better to remove the instructions.

more details inside, and many thanks to the person who provided the port during these months!

 

hello! v106.0.1 is rolling out on all platforms.

some might have already got a v106.0 update, others will be upgraded directly to the newer version as the releases were condensed into one, since they occurred within 48 hrs from each other upstream.

main changes:

  • rebased to latests firefox;
  • updated settings: there have been many minor changes in the past few releses, I suggest looking at the changelog of the past few versions;
  • hide firefox view for now, we will eventually patch it and re-introduce it in a revisited form later on!

enjoy and be safe :-)

9
submitted 2 years ago* (last edited 2 years ago) by fishonthenet@lemmy.ml to c/librewolf@lemmy.ml
 

FYI: if you prefer to use a different instance, mickie created a librewolf community of at https://jeremmy.ml. I will try my best to keep an eye on stuff posted over there too :-)

 

a bit late to the party, but v104 has been released in the past few days, depending on your platform.

the changelog is very small this time, I blame august:

  • all changes from firefox v104;
  • updated some patches that broke;
  • updated settings to v6.9, which is mostly a cleanup.

look I said it wasn't that much..but enjoy it :-)

 

I forgot the changelog for v102 but here's the one for v103 instead.

  • all upstream fixes from FF103
  • updated, fixed and deprecated patches.
    • in particular you might have noticed an issue with uBO disappearing, it's now fixed.
  • add release for OpenSuse Tumbleweed.
  • updated build documentation.
  • updated base macOS SDK to 11+.
  • updated settings to v6.7.
    • as the upstream cookie pref migration is finished you should no longer experience lost cookies.
    • IPv6 is no longer disabled by default.
  • updated some description in the UI.
  • fix printing in flatpak.

an even more detailed issue and merge request overview is available in the meta for v103.

if you want to contribute check our gitlab, follow the labels and the epic for the next release. if you want to report something please use gitlab, follow the guidelines and check known issues.

 

a reminder from our FAQ, for anyone doing it wrong.

 

interesting read from arkenfox's wiki.

view more: next ›