Check if you find anything about this in the kernel log (dmesg).

Depends a bit on what the default cloning url will be. If the domain is in control of mozilla, which forwards it to github, then fine, if most people start using the github url, then it is still a vendor lock in, because many people and projects will use it, and that is not so easy to move away.

Update: To the people down-voting my comment, I would love to hear why you either disagree with me, or find that my that my contribution to this discussion is worthless.

The upstream URL of a project or repo is important, because it will be used in other projects, like in build scripts for fetching the sources. If a projects changes that URL in the future, and the old URL is no longer available/functional, all those scripts need to be changed and the old versions of these scripts do not work anymore out of the box.

If the project owns the URL, then can add redirect rules, that might help alleviate some of these issues. I don’t think github allows projects that move away from it to do that. So this is a sort of vendor lock-in. The project needs to maintain the repo on github, because they want to break the internet as little as possible.

Not the drama itself should influence your judgment, but how they will deal with it.

Whenever people work together on something, there will be some drama, but if they are dealing with it, then that should be fine.

Nix and NixOS are big enough, that even if it fails, there are enough other people that will continue it, maybe under a different name.

Even it that causes a hard fork, which I currently think is unlikely, there are may examples where that worked and resolved itself over time, without too much of burden on the users, meaning there are clear migration processes available: owncloud/nextcloud, Gogs/Gitea/Forgejo, redis/valkey, …

Only really nice when not CLA is required and every contributor retains their copyright. Ente doesn’t seem to require a CLA.

Otherwise it allows the owner to just take the changes from their contributors and change the license at a later date.

Or other standard archiving formats like WARC.

There also is https://github.com/ArchiveBox/ArchiveBox which looks a bit similar.

Snap is just one case where Ubuntu is annoying.

It is also a commercial distribution. If you ever used a community distribution like Arch, Gentoo or even Debian, then you will notice that they much more encourage participation. You can contribute your ideas and work without requiring to sign any CLAs.

Because Ubuntu wants to control/own parts of the system, they tend to, rather then contributing to existing solutions, create their own, often subpar, software, that requires CLAs. See upstart vs openrc or later systemd, Mir vs Wayland, which they both later adopted anyway, Unity vs Gnome, snap vs flatpak, microk8 vs k3s, bazar vs git or mercurial, … The NIH syndrom is pretty strong in Ubuntu. And even if Ubuntu came first with some of these solutions, the community had to create the alternative because they where controlling it.

I mod my games on my PC and sync it to my SteamDeck. I also sync the save files back and fourth, to continue playing on different devices. Mostly non-steam games.

I also sync my eBook collection to my eink reader with syncthing.

Everything is also mirrored to my always-on NAS, so syncing always works.

Environment variables isn’t a concept of just docker, but general native app programming. So look into the docs of your language.

I have setup a mail server for my employer, and doing it manually yourself is difficult. I didn’t want to do it for myself as well.

However I looked into mailcow, and tried that privately and it works great so far! However, i would dedicate a separate VPS for just that.

I am hosting bitwarden myself (on a VPS) and I am not that concered about losing my passwords, because every device syncs all passwords locally regulary so that you don’t need internet to access them.

So to loose all your passwords not only do you have to loose your bitwarden server and all the backups, you also have to loose access to all your bitwarden clients synchroniously.