Good time-of-day, Linux users! I hope you will take kindly1 to coming here to tell you about Konform Browser and what it is. And also ask you to try it out in case this is your cup of tea :)

In short, Konform Browser is a web browser with the goal of promoting user freedom and access to the rights of security, privacy and anonymity. It is intended as a general-purpose browser fit both for daily online surfing as well as targeted deployments in secure or untrusted environments. It is fundamentally a patched build and custom configuration of Mozilla FireFox ESR. It started as a fork of LibreWolf and now stands on its own four feet.

Some highlights to give an idea to those familiar with LibreWolf or other FF fork:

  • Security: Konform is based on Firefox ESR instead of Rapid Release. This means a more stable base without missing out on the latest security updates, in exchange for longer time waiting for the newest features from Firefox. It also enables shorter lead times to backport upstream updates.
    • In this sense (and a few others), Konform Browser is closer to IceCat/GNUZilla than it is to Librewolf.
  • Freedom: Konform allows a higher level of customization. It gives the user control and trusts you with that responsibility. Some examples:
    • Allows enabling dark mode and following system theming even when Resist Fingerprinting is enabled
    • Allows installing your own self-built unsigned add-ons
    • “Spoof referer source” user configuration option
  • Privacy and security: Disables all browser features relying on external network connections.
    • “RemoteSettings” is completely disabled2.
    • No cloud “AI” integrations. You can run Konform on a disconnected network and not notice any reduced functionality.
    • All telemetry, metrics, and ads from the browser disabled.
    • OCSP turned off (but we have CRLite).
    • tcpdump and see the difference!

I should add that even if we contrast with LibreWolf above, this is not at all meant as a dig or criticism. I think they have done and continue to do great contributions for the benefit of all of us. That we chose it as upstream and that it’s the easiest to compare with is a testament both to how closely aligned we are and that Konform has a lot to thank Librewolf and the wider Firefox customization community for. Like they built from Librefox and Arkenfox to bring private browsing to a wider audience, so are we but the next to try help widen and deepen the browser ecosystem.

The recommended installation method is building from source but there are also binary packages for x86_64 and arm64 built by Codeberg CI. Currently Linux only, considering Android next and could use some assistance with that.

Doors open for users, testers and contributors. Looking forward to hear what you think and if there’s anything missing!

1: Disclosure: Am dev. This is a rewritten crosspost.

2: This means that local full-page translation is also unavailable even if in principle it should be possible to bundle and run translations fully locally. It’s just the way Mozilla built it. Patches towards allowing users to enable fully offline translations would be very welcome.


Sources: https://codeberg.org/konform-browser

Deb / RPM / Tarball / Container image

See releases for details.

Arch User Repo package

Arch User Repo binary package

Screenshot

  • alecsargent@lemmy.zip
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 days ago

    I tried to install both konform-browser and konform-browser-bin in Arch with yay and it failed to import gpg keys:

    gpg: error reading key: No public key
    
    
     :: PGP keys need importing:
     -> 9511FD9BD64CCF171F0B28A72B6FD58B41A0E262, required by: konform-browser-bin
    :: Import? [Y/n] y
    :: Importing keys with gpg...
    gpg: keyserver receive failed: No data
     -> problem importing keys
    

    I would build from source but I really have an underpowered laptop. Anyway, when this gets fixed I will be sure to give some feedback.

    :)

    • ken@discuss.tchncs.deOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      3 days ago

      Thanks for checking in! Did you try importing the Release PGP Key listed under the release already? ^^ Maybe it’s a bit easy to overlook in the release notes but it’s right above the debian installation. There should be a pinned comment on that on the AUR package pages already.

      If you save key to file on disk:

      $ gpg --import ./konform-cb-ci.pgp
      

      Then it should show up with that Key fingerprint when doing gpg -k after.

      Please let me know still having issues

      • ken@discuss.tchncs.deOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        3 days ago

        Oh and I forgot to mention, we have an Arch repo now with prebuilt bin package too. If you add the repo and pacman -Sy konform-browser-bin, then it will upgrade for you on future pacman -Syu when there are new versions published.

        For trying out such a new project I guess you might still want to do the more manual route in the beginning but if/when you feel it’s earned your trust now you know <3

        • alecsargent@lemmy.zip
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 days ago

          I just installed it from the AUR after importing the keys manually(before it did not work). Everything works as expected on first impression. I will port my configuration (like enlarging those skinny ass scrollbars) and will give you my feedback about it.

          • ken@discuss.tchncs.deOP
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            1 day ago

            You know, I think we should do at least something about those scrollbars1 too. Not sure how close this is to what you prefer but hopefully a more sane default with more traditional fixed-width scrollbars should be part of next release. In general aiming to keep subjective and aesthetic UI tweaking to a minimum but I think the usability argument supports this one at least until anyone voices a different opinion.

            So ty for that suggestion and also thank you for the warm feedback you left on the repo! :3

            1: Not only are they thin; they change the width dynamically when hovered and overlay on top of content. The potential for misclicks is not great.

            • alecsargent@lemmy.zip
              link
              fedilink
              English
              arrow-up
              2
              ·
              24 hours ago

              Good idea, I have the following in my preferences that I took from Dedoimedo:

              defaultPref("widget.non-native-theme.enabled", true);
              defaultPref("widget.non-native-theme.scrollbar.size.override", 20);
              

              And the option “Always show scrollbars” enabled because I have not found the preference to do it through the configuration file.

              I also shared it on mastodon and an ex Firefox subreddit moderator shared with me their enterprise policies for Firefox which included those options. Its fair to say that these are objectively good options.

              The changes that you proposed in the scrollbar branch seems good to me, specially the disabling of the overlay of the bar.

              Cheers!

              • ken@discuss.tchncs.deOP
                link
                fedilink
                English
                arrow-up
                1
                ·
                edit-2
                4 hours ago

                Appreciate the links!

                And the option “Always show scrollbars” enabled because I have not found the preference to do it through the configuration file.

                The labeling makes it less obvious but that maps to widget.gtk.overlay-scrollbars.enabled=false so also part of Konform upcoming update :) In general I find the quickest way to identify the mapping of a UI configuration and the about:config key is to:

                • launch a clean profile
                • open about:config
                • click Show only modified preferences
                • open about:preferences
                • change the thing
                • tab back. what’s new?

                BTW, widget.non-native-theme.enabled is a no-op since the direct GTK integration was removed a while back: https://bugzilla.mozilla.org/show_bug.cgi?id=1726283#c4