Maintaining Konform Browser and some other bits and bobs.

  • 4 Posts
  • 13 Comments
Joined 3 days ago
cake
Cake day: January 18th, 2026

help-circle


  • Sorry, that’s totally off topic (rule 1) and none of your business I’m afraid.

    Feels like you’re meming on some uncharitable stereotype at the expense of myself, QubesOS, and room for more interesting convos in this thread. Comments like this might make other users with less hard skin afraid to post their own setup if stuff like this is all they get back. It leads to less diversity and real talk, more low-effort memes and the sameish sway-with-a-fancy-background-and-fastfetch.

    As this little community grows I think it would be sweet to try not to actively reproduce the bad aspects of Reddit.

    (Yes, I’m a blast at parties)





  • Went low-key public with our internal browser project by sharing here on the feddit. If you’re a dev, packager, Arch Linux user, or already build Firefox from source, this is for you (others can check back at a later date when perhaps there are more builds running and tested). More people using it becomes a shared privacy win. I humbly suggest that this is currently the most privacy-friendly general-purpose GUI browser out there1.

    Announce post

    Sources

    AUR

    1: Biased? I would never!


  • Getting a lot of benefits from it. I’m a happy user!

    If I mostly talk about downsides in order to keep this brief:

    It can work fine to just install and start using out of the box as it is, even for Linux noobs. You can get pretty far without having to dig super deep. But to really customize it you get into things like Salt management (or figuring out an alternative) and building your own templates. This can take a lot of time and effort. Consider it “playing on hard mode”. For me it’s fine since I enjoy these things and you can take it bit by bit. Lots of helpful stuff shared in the community like the repo I linked.

    It’s not 100% jank-free. More niche things like ZFS integration, GPU passthrough and sys-gui qubes take some tweaking or even patching depending on your hardware and use and I have run into bugs with all of those. Chaining Tor and DNS on some IPv6 networks is still not all there but looked like WIP last I checked in.

    Would love if they manage to migrate away from github.com

    That said, things are indeed steadily improving and people generally seem helpful and constructive when I look at the issue tracker1. I think it’s worth giving it another chance now that 4.3 is out.

    1: Example: Didn’t have to report those bugs myself as someone beat me to it. And fixes for most did come in.


  • A tangent but in response to something I see around here recently:

    People who say Wayland is ready for everyone and that X11 is no longer of relevance - that distros and projects like KDE dropping and deprecating it is A Good Thing: How do I replicate this in Wayland without having to loosen security boundaries or lose out on core features? Or at all?

    Not shown in screenshot but sometimes I also run GUI apps or a nested WM (to get the “classic” VM experience with a windowed or fullscreened isolated desktop) in containers. Also obviously need things like remote screen sharing without having to run such apps in dom0 and Input Method integration for non-latin typing. Even with people working on some parts of that already and some ad-hoc early-stage solutions existing, I don’t see it happening this decade… My setup works great for now and I’d hate to have integral parts of it getting fully abandoned or dropped from upstream distros like Fedora or Arch if no drop-in replacements exist. Why the push for deprecation? :/

    Next time you see someone saying that Wayland isn’t ready for them, maybe take their word for it instead of downvoting? Consider how much I had to expose myself just to be able to try to make a point. When we’re in the long tail of remaining use-cases, they get detailed enough that you can’t explain them without getting personal and very profilable.