Congrats!
Meh, I’d not make effort towards backwards compatibility.
Thanks for sharing!
For people who have not dived much into application-level sandboxing (like me), I found this article by the author to be a useful introduction to what this is and why it might be useful. Can’t comment on this vs. alternatives, but it felt like an accessible intro to the problem domain, one possible solution (as implemented by nix-housing), and some limitations.
https://decentstat.es/posts/nix-housing/
They also have the disclaimer in this article that the project nix-housing is “Obligatory: LLM assisted but not vibe-coded.”, which I’m just including so that people who want 0 to do with anything touched by any LLM in any capacity don’t feel like they waste their time looking into this.
I believe in stable systems, for the benefit of myself, or any user that wishes to use my tool.
Any breakage of this tool is wasting time of my users. (I believe this still applies even in the age of AI.)
There is even less LLM code since then, most of the 3000 lines of code here I have manually brought into existence, and the remaining parts, mainly the wayland-security-context, I have heavily audited and compared against the Flatpak version and rewritten.
This looks awesome.
My user on my laptop inevitably has a lot of privileges, but also runs a lot of software.
I like that this allows me to segregate different usecases.