First off you should realize that the registrar’s and domain name servers don’t have to be the same. Feel free to use any registrar (ex: namecheap, gandi, etc) and host the domain name server anywhere else.

Secondly, if you want a good API for dynamic updates, I’d recommend looking for something that supports nsupdate, which is bind’s built-in update mechanism. It’s supported almost everywhere, including by let’s encrypt clients like Lego.

https://www.redhat.com/en/blog/red-Hats-decade-of-collaboration-with-government-and-the-open-source-community

When we rolled into Baghdad, we did it using open source. - Major General Nicholas Justice

While that is true, the question is whether that’s a good thing, or not, and for whom.

PCIe absolutely does support disconnecting devices. It is a hot swap bus, that’s how ExpressCard works. But it doesn’t mean that the board/uefi implements it correctly.

chmod -R the directory first?

This doesn’t really explain how the whole protocol works. Are the keys exchanged for example? Are they rotated? If so when and how? From a quick glance at this bit of code this is just RSA? So no forward secrecy?

Where is the crypto documented? I’m immediately dubious of messengers that do not provide LENGTHY documentation about the crypto. Did you roll your own? Are you using libraries? Which ones? Etc… It’s not s good start to see that you have the self signed certs hard-coded in the repo…

https://wiki.debian.org/DebTorrent

https://wiki.debian.org/DebTorrent/SolutionIdeas

SleepAsAnAndroid as well a broad support for generic smart watches

What’s wrong with Debian?

As long as it was encrypted with LUKS headers and not a raw cryptsetup resize is totally capable of resizing partitions/LVs.

What’s your take on… What’s you’re take on?..

Entirely depends if you count HGST as Western Digital or not, because they by far dominate the back blaze reliability scoreboards. IronWolf don’t even come close and are extremely hit or miss depending on capacity.

https://www.backblaze.com/blog/backblaze-drive-stats-for-2023/

No a chroot is indeed not a container/namespace. I’m not sure what you’re getting at here. Flatpak isn’t a chroot and what I suggest you try isn’t either.

Flatpak absolutely does use containers for sandboxing. Bubblewrap is wrapper for Linux namespaces. Containers is just another name for the underlying kernel technology called namespaces. Same goes for Docker, LXC, Podman, systemd-nspawn, Firejail, etc. It’s all just userland frontends for kernel namespaces. man bwrap, you can also use the generic unshare to create them and nsenter to enter those same namespaces. It’s cool technology, it’s very easy to use, a simple flag on your exec or opening of an existing fd is all that is required. I used to work on one of the many userland frontend, even have gotten a couple PRs from Jess Fraz who was one of the core Docker devs. Userns still scares the shit out of me (pretty much every single escape has come from them).

Here’s a fun experiment for you: create a root fs using debootstrap and then enter it using unshare and chroot! Tada! Container!

How can you guarantee that depencies are compatible across versions? That’s a fundamental point I think you are missing.

I’m curious why you would think that containers are bloat? They require virtually no resources and are built into the kernel. A container is literally just a flag that you add when you exec on an executable binary.

I mean sure, but that’s a period of like a couple months every couple of years.

Not sure what you’re on about… Sid and testing are usually pretty damn near bleeding edge.

How do I get rid of it.

Reinstall Debian… Problem solved, and you get rid of snap as a bonus!