Ok, why does this matter? Even if you did support MAR updates, the updates wouldn’t be instant as you would still need to apply LW configs and own updates, no?
Just curious to understand, thanks.
MAR files, short for Mozilla ARchive files
We don’t repackage a built Firefox, we build our own from source with our changes.
MAR updates is just another way we could deliver these updates instead of using our custom Windows updater or using rpm for example.
Thanks for the explanation.
I just wanted to clarify LW does have automatic update and respect that PG criteria. I don’t think the way you do it matters.
So I believe the only valid remaining point would be this:
Ahem…
Maybe we can create a poll to cancel this? This looks like “commercial guides” not about privacy.
This is even more right, that i wanted to explain.
PG should focus on what we do best: privacy!
Not distribution. Not cross-platform. This can be noted in guide separately.
If tool is good, users who want privacy will find and install it themselves.
This requirement is ridiculous. Most of devs of best projects are non-profit hobby ones, so they don’t have money to pay evil corps.
And if Mac requirement is partially explainable, microslop? Seriously?
When shitdows ever was about privacy? Telemetry is privacy? Or maybe AI shit and ads is privacy?
P.S: LibreWolf devs, many thanks for your hard work! Best browser ever!
Not the place. This is a LibreWolf discussion. Start a new Site Development thread.
I’d always understood that LibreWolf was basically the same as Firefox with Arkenfox, have I got that wrong? Are there privacy or security benefits (other than ease of setup) from using LibreWolf over the Firefox and Arkenfox setup?
They do differ, I believe arkenfox is a little more strict in some ways though I forget which.
It used to be similar to arkenfox but not sure how close we are at this point since I add things I stumble upon or when talking with Celenity.
You get some security benefits compared to Firefox, since they refuse to ship some mitigations because of performance loss or because some things become dormant and nobody has looked at them in years.
I backported some build-system changes from release 150 (we are currently on 148), so we can ship STL hardening early for all platforms, compared to Firefox, which currently has it only for macOS and has it planned for Windows in release 150 but nothing yet for Linux.
Also, the recently added per-site WebGL toggle can help reduce the attack surface compared to having to decide between having it on globally or off.
I would have to look, but just by us currently still being on RFP, compared to arkenfox with the default broken FPP RFPTargets, we are more strict.
Thanks so much for the reply, really helpful.
Could I ask one further question…. The only thing that has prevented me from using LW regularly in the past is the way the 1Password extension behaves on MacOS. It logs me out everytime I close the browser and doesn’t seem to play nicely with the desktop app. Is this a know issue and is there a way around it?
off topic: mulvad browser
This is incorrect. Mulvad Browser is FOSS; it is licensed under Mozilla Public License V2 & code is available on Github (though Im not sure if builds are reproducible). The browser does not require MulvadVPN; it can be used with a different VPN, or no VPN at all
Not sure what the issue was/is but it could be related to the macOS release not being signed. Could also be related to Frequently Asked Questions – LibreWolf
I tried adding the symbolic link but still can’t get it working, guess it must be to do with the not being signed. Thanks for the help.
Also, i always wondered, why aren’t you packaged into official repos of Debian/Ubuntu and using extrepo?
I am not against this, but it is a little hard to explain newbies how to use terminal, since they just got used to GUI and app managers…
Since we already have our own repo, which allows us to ship updates much faster, there isn’t much need for it. It would also add additional maintenance we’d have to do. I wouldn’t be against having LibreWolf be packaged in the repos for Debian or Ubuntu, but it would have to be maintained by someone else.
@any1 Are containers redundant/not really necessary in Librewolf?
They serve the same role as they would in Firefox. I personally have never used them, though. You could use them to have multiple separated logins for the same site, for example.
I should have added more context.
The Librewolf FAQ/docs say this:
”Please also notice that dFPI makes containers and containers extensions redundant, unless you want to protect your privacy when visiting the same website multiple times, during the same browsing sessions.”
Is this still the case?
I usually put YouTube in a container. I have no idea if that is useful or helpful or useless but it is one of the more privacy invasive sites I use (don’t use Facebook or Twitter or TikTok etc) so I thought I should put it in a container (thinking it is like an isolated tab jail).
I do often have multiple YouTube tabs open.
Is using containers in this context redundant and unnecessary?
Are you logged into youtube and have it set to keep cookies?
No I am not logged in (I refuse to have a Google account), and have not made any cookie exceptions for YouTube.