[-] [email protected] 1 points 11 months ago

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

[-] [email protected] 1 points 11 months 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.

[-] [email protected] 1 points 11 months ago

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

[-] [email protected] 1 points 11 months ago

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

[-] [email protected] 4 points 11 months ago

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

[-] [email protected] 1 points 11 months 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.

[-] [email protected] 1 points 11 months ago

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

[-] [email protected] 2 points 11 months 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

[-] [email protected] 1 points 1 year ago

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/

1
submitted 1 year ago by [email protected] to c/[email protected]

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 ๐ŸŸ

1
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]

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!

1
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]

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!

1
submitted 2 years ago by [email protected] to c/[email protected]

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 :-)

1
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]

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 :-)

1
submitted 2 years ago by [email protected] to c/[email protected]

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 :-)

1
submitted 2 years ago by [email protected] to c/[email protected]

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.

1
submitted 2 years ago by [email protected] to c/[email protected]

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

1
submitted 2 years ago by [email protected] to c/[email protected]

we back again with a new release, out on some platforms, building on others.

main changes:

  • all upstream fixes from firefox v101.0.
  • settings v6.5, mostly a minor cleanup.
  • multi-language support in the UI for all versions of the browser, all fully rebranded.
  • windows releases and source tarballs are now signed.

enjoy, and as always feedback is appreciated :-)

1
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]

hello, the new release is out on all platforms.

main changes:

  • all upstream fixes from firefox v100.0, happy birthday!
  • easter egg to celebrate v100 :-)
  • settings v6.4, meaning:
    • improved robustness of certificate revocation false positives, in case of corner cases.
    • UI for cookie clearing is now more consistent.
  • updated uBO.
  • patched new theme UI if RFP is enabled.
  • rebased some patches.
  • remapped some more links in the UI.

~~we also have a known issue that causes the main page to display as empty. we worked on a fix and it will be included in the next release.~~

the content of our website has also been updated, including the faq and the addons sections.

peace ๐Ÿ 

[-] [email protected] 0 points 2 years ago* (last edited 2 years ago)

I will start by saying that the author of the article was a tor researcher and dev so this gives some context on the content and me posting this.

which is a very risky thing to do for someone not familiar

may I ask why? I generally agree with the sentiment of the article but I don't have a very strong opinion on this and maybe I'm missing something.

PS I don't think the usual "I will end up in a list of people who use Tor" argument is a valid one.

Preferring JavaScript stay disabled is a better choice, the next best is only allowing JavaScript when needed momentarily.

I disagree with this, it's simply overkill for 99% of the people with arguably no benefit at all. what's there to gain?

2
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]

a great post that was published a few years ago on Matt Traudt's blog with some tips for people using Tor and the Tor Browser.

it also addresses common misconceptions like disabling JS and using fingerprinting tests, which unfortunately I see floating around every other day on the internet.

1
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]

hello, the new release should be out on all platforms. sorry for the delay we had some slowdowns with the settings and then a good portion of our patches needed a rebase. we should have done stuff earlier but personal life got in the way, but well here we are in the end :-)

main changes:

  • based on firefox 99.
  • settings v6.1, which means:
    • removed some settings that became deprecated in v99.
    • general cleanup to remove some redundant prefs.
  • updated librewolf specific UI:
    • we had to fully rebase it.
    • new option to enable firefox sync. requires a restart atm.
    • new option to harden cross origin referrers even further. I noticed it looks slightly broken, it might need a fix during the next few days.
  • updated uBO.
  • remapped a bunch of UI links.
  • fixed more patches.
  • increased security of the build process by checking mozilla's signature on the source code.

again sorry it took 4-5 days rather than the usual 1 to 3 days. enjoy!

[-] [email protected] 1 points 2 years ago

yup, the idea is to ship a de-cluttered and straightforward browser. however we figured there was no reason to completely block users from using Sync, so we made it easier to enable and added the faq entry for those who like the convenience.

it's just another option, like xbrowsersync and manual backups.

view more: next โ€บ

fishonthenet

joined 2 years ago
MODERATOR OF