Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)K
Posts
15
Comments
103
Joined
1 mo. ago

  • All info on that site is several years stale and the site itself is unmaintained (last update 2022; git repo permanently archived 2024). Many of the details are not reflecting current state of things and this page is not a good resource for comparing browsers in 2026 (except as inspiration for replicating their methodology1).

    Konform Browser is to my knowledge the only up-to-date webextension-capable browser today with literally 0 phone-home / background connections under defaults, and no telemetry or other superfluous undesired activity ever. (disclaimer: am dev. I'm certain it would be ranking as top if such a ranking was made today. Come @ me ;))

    1: Separately recently published container-based flow for doing this kind of analysis and doing similar comparison. There are some basic results and comparison included in readme but would be cool to see someone take it to the next step, drill deeper, share more exhaustive and educative results, present it in a format more digestible for non-techies (whether using this setup or something different).

  • du

    show them ncdu next time

  • @cm0002@lemy.lol Could you at least cross-post like a normal person or link to OP? Hard to reply like this. (And spare the copy-pasta kthx)

  • 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).

  • Whatever else you do, homelabbing and/or coding on private projects on the side will do you well. Try to go small. Holds at literally any level.

  • Sounds like clients could do a better job in merging cross-posts and making it easier to filter them from the view.

  • Been digging into the Tor Browser codebase recently and as a consequence now lifting over a few goodies in the privacy and security departments from there to Konform Browser

  • Yes! And thanks for trying :)

    As you do, it will help to know if you also tried Firefox (or other derivative) and if results there are same or different from Konform.

  • When someone willing to package and test that shows up ;^^

    In particular, being on flathub means someone with a github account needs to push it up (sorry i'm done there).

    Here is a starting point: https://codeberg.org/konform-browser/flatpak

    Happy to iterate on codeberg with anyone who wants to tackle this

  • Linux @lemmy.world

    Konform Browser v140.7.1-100 released

    codeberg.org /konform-browser/source/releases/tag/140.7.1.100
  • Maybe you already figured this out but I think it's a common gotcha:

    Wireguard AllowedIPs means just that: IP addresses that are allowed to be routed over the tunnel.

    There is nothing that says that you need to have 1-to-1 mapping between that and actual routes. Most of the time it's what you want but there are situations where you want it different. Some people have a wider subnet for AllowedIPs but only add certain routes specifically.

    wg-quick additionally adds corresponding ip routes as a convenience. systemd-networkd did at some point but don't anymore. I'm not sure what NetworkManager's Wireguard plugin is even supposed to be doing there these days. Most of the time what looks broken is actually a result of unclear documentation and a mismatch in assumptions between dev and user.

    It's an understandable source of confusion and the tools don't always help when they try to.

  • Just to be clear, most of these (think about egrep/fgrep for a moment) are deprecated and "shouldn't be used" in scripts for distribution. What's new is that you can't expect everyone else to have them and having dependency on them in shipped software is considered antipattern.

    Nobody gives a shit what aliases and shims you use in your own shell.

    On iptables: By now it's even gone from kernel and the turn tabled with the cli command now actually being a shim calling into its successor nft. IMO nft is much more approachable for beginners to pick up and the rules files become so much more readable and maintainable. If you're already committed to iptables syntax then cool - but with very few exceptions I don't think anyone needs to learn iptables today - just go straight to nft and you'll be happier for it. Similar for ifconfig.

  • ip -br a, even

  • Oh actually I wouldn't know - maybe it's one of those funny crossovers! Will have to remember asking about it next time I meet my Brazilian friend. If it works for you then why not ^^

  • Privacy @lemmy.ml

    Konform Browser v140.7.1-100 released

    codeberg.org /konform-browser/source/releases/tag/140.7.1.100
  • X.Org Server's "Master" Branch Now Closed With Cleaned Up State On "Main"

    Jump
  •  
        
    master( ͡° ͜ʖ ͡°)main
    
    
      
  • still pissed the name is not inspired on a canine/lupine

    I kind of want to keep that subtle but it is there :p

    Follow-up hint: In Japan they sound different than in Norway

    Good to know on the crossposting. And thanks for encouragement! If winds are willing we can also land a patch for this in Tor Browser (and I guess consequentially Mullvad). Only feels fair to try contributing back since we are effectively benefiting from their contributions and if we get reviewing eyes on code in process it's win-win.

  • Linux @programming.dev

    Konform Browser v140.7.1-100 released

    codeberg.org /konform-browser/source/releases/tag/140.7.1.100
  • I think there's quite a lot more to it than sources there already? If you are on Linux there are likely built packages for your distro available. A bit more of the whats and whys are in the readme (though as tends to happen that is not telling the entire story - release notes linked at bottom of OP hopefully help to fill the gaps. Those are written to hopefully be meaningfully digestible by keen non-experts and relevant to (prospective) users).

    I felt the post was getting long enough as it was already with just the release summary but happy to talk more!

    What specifically are you interested in? Fire away!

  • Privacy @lemmy.dbzer0.com

    Konform Browser v140.7.1-100 released

    codeberg.org /konform-browser/source/releases/tag/140.7.1.100
  • The screenshot in the post is from IronFox.

    It's not, though? Let me guess, it's from some tool or page doing static analysis on the APK and reporting results? Please include a link or reference to actual source when reporting in the future.

    So, Firefox contains a library that can be used for reporting telemetry to Mozilla. When you download Firefox from Mozilla, this is enabled and pointing to Mozilla servers. After reading Privacy Notice shouldn't be a surprise.

    When you install one of the fork that disables telemetry (IronFox, LibreWolf, Konform Browser at least do it this way), they will configure the build such that the endpoints are never called. Mozilla are actually reasonable enough that this is supported, documented, and reasonably straightforward for those bothering to build FF from source.

    So yes, when you download IronFox it contains a library that could be used for Mozilla Telemetry. It's just that it's never used to do so (assuming no bugs).

  • Free and Open Source Software @beehaw.org

    dialhome-study/browser-network-insights: they have played us for absolute fools

    codeberg.org /dialhome-study/browser-network-insights/src/branch/main/README.md
  • cybersecurity @infosec.pub

    dialhome-study/browser-network-insights: they have played us for absolute fools

    codeberg.org /dialhome-study/browser-network-insights/src/branch/main/README.md
  • Privacy @lemmy.ml

    dialhome-study/browser-network-insights: they have played us for absolute fools

    codeberg.org /dialhome-study/browser-network-insights/src/branch/main/README.md
  • privacy @lemmy.ca

    dialhome-study/browser-network-insights: they have played us for absolute fools

    codeberg.org /dialhome-study/browser-network-insights/src/branch/main/README.md
  • Linux @lemmy.world

    Konform Browser - Taking privacy, security and freedom to the next level

    codeberg.org /konform-browser
  • Privacy @lemmy.dbzer0.com

    Konform Browser - Taking privacy, security and freedom to the next level

    codeberg.org /konform-browser
  • unixporn @lemmy.world

    LPT: Redmond97-SE theme pack is kicking and now on AUR

    aur.archlinux.org /pkgbase/redmond97se-themes
  • unixporn @lemmy.world

    [Xfce] [Xmonad] Back to root

  • Arch Linux @programming.dev

    Konform Browser - Taking privacy, security and freedom to the next level

    codeberg.org /konform-browser
  • Arch Linux @discuss.tchncs.de

    Konform Browser - Taking privacy, security and freedom to the next level

    codeberg.org /konform-browser