@jobbies Eh? Just use Fedora/Alma/Rocky with BTRFS and Samba/NFS. You can even use an immutable flavour and not have to worry about updates breaking anything.
Hobbies:
#eattherich
Thumb wars
Mad nerd
Quote: “Do you bite your thumb at me, sir?”
@jobbies Eh? Just use Fedora/Alma/Rocky with BTRFS and Samba/NFS. You can even use an immutable flavour and not have to worry about updates breaking anything.
@UnfortunateShort @KarnaSubarna And you’ll want to audit the client code of the fork, including dependencies and make sure it is keeping up to date with official development for security patches. And Signal may try to break the interoperability at some point in the future.
@UnfortunateShort @KarnaSubarna I think you are right about the official client, they really want to own the service so you can only connect to their decentralized service via their centralized servers 🙄 I haven’t done it, but I think you can run your own client, either modifying and building it yourself, or surely one of the existing forks can connect to arbitrary servers? But anyone who wants to use your server will have to also use one of the forks.
@tofu Can’t you just use a rootless podman quadlet? Edit: Oh I see, I think it uses gitlab hooks to find out when there are new images available? You can probably point at latest on an image on a gitlab registry anyway and have a quadlet auto update?