[–] 2 points 8 months ago*

Thanks for the quick rely!

Maybe this is relevant for some

That is very tangible, indeed. And kudos for providing the only browser that aced the 'test'!

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.

Hehe 😜. I do admire your work, but don't get your hopes up 😅.

Anyhow, I will add it to the list of Firefox(-based) browsers worth looking into. To be clear, I'm not a primary consumer of the product category. FWIW, I would install it on my system if I were*.

  • source
  • parent
  • context
  • [–] 7 points 8 months ago (2 children)

    In the now up-to-date README.md we find the following line:

    A couple of privacy-related patches not built elsewhere

    Cool. But..., could you name those explicitly?


    Mullvad Browser is also based on Firefox ESR and is the product of a joint development involving both Mullvad and the Tor Project. Could you please explain why anyone should consider Konform Browser over it?

  • source
  • [–] 1 point 8 months ago

    My priorities:

    • Secure. Unlike popular belief, the fact that the worlds infrastructure basically runs on Linux does not imply that your average Desktop Linux distro enjoys the same level of scrutiny when it comes to its security. Hence, the security-conscious should carefully pick a distro that can handle their threat model. Or, at least harden it to their liking.
    • Stateless. Conventionally, you will be met with a (relatively) minimal system after installation. After which you're expected to configure it to your liking and go smooth sailing afterwards. Occasionally, you might (un)install stuff and/or modify settings; but nothing out of the ordinary, really. While applying some of these changes might seem trivial, they (kinda) lead your system to accumulate cruft. This cruft might seem innocuous, but it's exactly why your system seems so fresh after a reinstall. Foregoing this altogether is referred to as going stateless. This is done by declaring a desired state and 'flushing' all changes that have not been declared. Many other benefits are associated with this, but I digress...

    The above^[So, without even going into release cadence etc.] already dictates the use of NixOS with the impermanence and nix-mineral modules.

  • source
  • view more: ‹ prev next ›