So how is mentioning Vivaldi bad?

I would guess they were probably thinking more about your Zen Browser reference¹, and your comment on Mullvad Browser. Both are misinfo and I would agree it’s good to do a little DD on your own before posting hearsay. Even with the disclaimers it’s contributing to spreading and giving credibility to those claims.

¹: Perhaps the least inspiring major FF fork from a privacy perspective… https://codeberg.org/dialhome-study/browser-network-insights

deleted by creator

The Lemmy community is broadly 50:50 on their support for said calls for the violence.

1. There’s astroturfing. Careful with judging community vibes by obviously votes but also comments.

2. There is more to “The Lemmy community” than what’s on display on .ml.

I also believe nobody here is sending threats.

I wouldn’t be so sure of your tribe. 19 users so far upvoted a comment with among other concerning bits:

if you’re anti this bullshit “law” then you are also pro physically harming poor FOSS “contributors”.

You missed this option:

• Ignore the feature and don’t use it.

systemd is quite modular. For example, if you abhor systemd-resolved (not at unreasonable stance) it’s NBD to disable it.

Recently (<1 year?) I frequently see the notion that software is “tainted” by having been touched by Bad. I find this a bit silly. Especially if it’s from a user who’s not even spending time in the codebase.

Are you keeping at default window size, or resizing? If latter, it is expected. This is a gotcha when using tiling window managers as they often force a window size that may give you off. TB should otherwise start with static fixed window size. Enabling “Letterboxing” feature can help alleviate this somewhat.

On PG: Also been seeing weird vibes and some inexplicable moderation comms and actions when looking closer. Their “recommendations” and “guides” also raise eyebrows. Something is very strange there.

YSAK: If you care about stuff like this, Konform Browser is likely more suitable for you!

It makes these things easier to configure (e.g: There is UI for toggling RS server or setting a custom URL). It makes it easier to selectively enable only security-related stuff (cert revocation lists) while keeping requests for less important features disabled. It requires opt-in to enable the background fetching and has 0 self-initiated/background outgoing connections on first startup. When request to RemoteSettings is blocked by configuration, it reuses locally available data to a larger extent. It is more selective about what to sync and not. It loads ublock origin from local filesystem instead of downloading it from internet at runtime. Etc…

What is particularly annoying is that some of these domains, related to “remote settings”, are essentially hard-coded and cannot be disabled by changing configuration parameters.

This is not entirely true. Relevant prefs for about:config or librewolf.overrides.cfg that are recognized by either browser:

• services.settings.server
• librewolf.services.settings.allowedCollections
• librewolf.services.settings.allowedCollectionsFromDump

For example

Cool. But…, could you name those explicitly?

Thanks for checking out! Not in the readme, because it would be a PITA to keep that up to date over time, especially when rewriting for new context each time. They are already covered in release notes and commit log¹ for the curious. You can also look under patches/kon in the source git repo.

This comes to mind.

Could you please explain why anyone should consider Konform Browser over it?

Am engineer not a salesperson or influencer. I guess that means at this early stage it’s primarily targeting the audience who are able/willing to make sense of and contextualize the given material themselves, or willing to take a leap of faith. The pros/cons vs other browsers is something I hope to leave to other users to talk about and share around. Would be cool to hear your thoughts, for example! Maybe this is relevant for some, though.

Also, pull requests attempting to improve the documentation are very much welcome. Would be great to get more contributors involved and one doesn’t have to be deeply technical to write good docs.

¹: Can click the commit hash for a release under /releases and then xxx commits to list commits for specific release

What an atrocious comment choice.

Update: Readme has been updated to be less out of date and that diff list is now more closely resembling current state of differences. In particular, local full-page translations is supported feature in Konform Browser, unlike the readme previously stated.

It would certainly be nice to be able to pre-download language pair models without selecting to and from and then actually initiating a translation using the model i don’t have yet.

Agreed that would be nice. Closest you get conveniently from inside browser today is to switch temporarily to “Basic Features” preset for model downloads (then maybe restart for good measure) and switch back to “Core Security” preset for actual use.

re: getting uBlock externally, i also see the attraction of that approach but unfortunately Debian’s package was last updated in October (from 1.62 to 1.67) while AMO has a release from January (1.69) :/

I don’t think it will be directly bundled due to the list updates and some users will not want it so it should remain optional. That being said, will already be looking at packaging for NoScript so when that happens I think should be reasonable to do the same with up-to-date uBO.

are there plans to distribute Konform via flathub?

Answered this here.

Officially can’t/won’t due to Github being both unreasonable and a supply-chain risk. Anyone is free to do so independently, however. If done in responsible and reasonable way (don’t introduce breaking patches or leave users hanging weeks without security updates plz) could be supportive of such initiative whether done indepently or via Konform Codeberg.

Oh, thanks for bringing that up - that’s out of date and no longer true so I guess the readme does need an update¹. While you are correct, the offline translations feature wouldn’t actually work when blocking its access to RemoteSettings server. There was also a bug (still present in LW) which prevented locally cached results from being used. As Konform Browser does have a strict policy of not initiating connections to “trusted” servers on its own by default and without explicit user consent, it made more sense to remove it than leaving UI for a completely broken feature until it could be done properly.

Since that was written:

• Bugs fixed in Konform so translations do work fully offline now
• An about:welcome “onboarding” screen was introduced where user has 4 presets to choose from. 3 of them (all but Purely Private 🔒️) allow translations feature and 2 (✳️Basic Functionality and 🦊Just Make It Work) makes it default and enable the automatic downloads of models from Mozilla server like in FF.
• about:translations unhidden and can be used for direct translations of direct input

So in reality I would say offline local translations actually work better in Konform than in FF and other forks.

In the future hoping to improve this further by redistributing the models as packages for separate installation on system. Then you can use them without needing the browser itself to download anything at all. Similarly to how it’s already done for spelling dictionaries and uBlock Origin.

¹: EDIT: Readme has been updated to be less out of date more closely resembling current state of differences.

Care to comment on the actual content of post or the topic of the project rather than aesthetics of the thumbnail icon? It’s a web browser, not a lifestyle brand, and this isn’t c/logodesign 🙄

While that section in readme is not entirely up to date, combining that with release notes should hopefully give decent idea. Let me know if you have remaining questions after returning from those! You could also try it out and see for yourself.

Some day, someone is going to have to explain this one…

There is actually a third visual reference in the logo that may be a bit less obvious.

LibreWolf, on the other hand, works by spoofing a different fingerprint every session.

Is that true? I think it’s not that much of a fundamental difference in strategy as you say. While LW (like MB) does randomization of e.g. WebGL and Canvas fingerprints, in general other fingerprintables are also kept static. From my perspective it’s more a difference in degrees than direction. Have you checked how your font fingerprint persist?

I believe both Mullvad Browser and LibreWolf come with uBlockOrigin pre-installed

Not exactly. LW comes without the addon but is configured to download and install uBlock Origin from addons.mozilla.org the very first thing it does. This is in contrast with Mullvad Browser (which does bundle the addon) and Konform Browser (which will load locally installed system uBO from known path if installed from distribution package manager).

If you’re looking for something to use with actual accounts (like banking), use hardened Firefox (with arkenfox) or a hardened chromium browser.

Konform Browser is intended to support that use-case and also worthy for consideration. Would be curious to hear if you agree or how you think it falls short!

LibreWolf doesn’t work to give you a non-unique fingerprint. Use Mullvad Browser for that (without changing anything other than the safety level).

Konform Browser also provides stronger protection against fingerprinting compared to vanilla FF or LW. Similarly (and in no small part thanks) to Tor Browser and Mullvad Browser.

Identification via enumeration and rendering differences of fonts is a major factor that’s often overlooked. Those three browsers bundle and enforce the same fonts and fontconfig to make that less reliable as fingerprinting method.

This and the links it references are probably relevant:

https://github.com/keepassxreboot/keepassxc/issues/12779

Thanks to you both! Can you explain, like you might to a three-year-old, why this is considered a bug?

Well, you are getting forwarded to an issue tracker for technical discussions. The context is people collaborating on the Firefox codebase. In this space, “bug” might not imply what you think it does. Like, new features still under development and general improvements are also tracked as “bugs” in Bugzilla. That doesn’t mean that anything was considered broken.

With regards to where runtime files and data is stored, the Firefox (and therefore Librewolf) way of doing it is widely considered legacy at this point. They probably wouldn’t build it that way if it was done from scratch today. But it comes from a different era. There is now heritage, legacy, and compatibility making the transition take years. That is normal and expected with a project as widely adopted and integrated as Firefox.

I think there is not much unique to Librewolf here (exception might be the librewolf.overrides.cfg); it’s just inheriting and following upstream.

Old place: .librewolf. New place: Split between ~/.config/librewolf (config) and ~/.local/share/librewolf (data).

Here and now as an existing user who doesn’t really want to care, I would advice sticking with the “old” current location of just ~/.librewolf and not moving things around or reconfiguring yourself. It’s still being relied on by some parts of the browser. Depending on what features and addons you use, things might break if you expect to do a full move already.

See for example https://bugzilla.mozilla.org/show_bug.cgi?id=2005167

Some people feel strongly about “stay the F* out of my home directory, all you apps” and they might tell us this really is a Bug, how crazy it is that it isn’t fixed yet, etc. Their concerns aren’t relevant for a three-year old. Or even most people who just want their browser to work. They might actually help in pushing development forward and the platform getting on with the times. And they find and complain about the edge-cases so that step by step the transition becomes more seamless and complete. But bottom line is that calls for action are targeted at devs and maintainers; not users like yourself (really not meant as gate-keeping but more to point out that there’s a depth and assumption of context here making it take some immersion to make sense of what’s being said and choosing not to partake is fine).

I prefer my devices without any malware at all but you do you I guess.

you’re data is safe with small hackers

wat