A domain takedown was never able to shut a server down, not even with centralized servers. Most big services are accessible via multiple domains of different countries, and this would just disable one of them. But for the Fediverse that means that they also “disabled” an entire instance with all its users.

This actually shows us that relying on domains can be a problem for the Fediverse! Imo we need to upgrade the federation protocol to be able to handle these things, like propagating a domain change or migrating accounts to other instances.

My server is a DiskStation, so I use HyperBackup to do an encrypted backup of the important data to their Synology C2 service every night.

The thing is, people might not know that they have to look for the Docker setup. Now if they search for “Lemmy on Synology NAS” they land on this guide, telling them to use Docker.

The answer is always yes for hosted services. The data has to be stored somewhere, and it is readable if not explicitly encrypted on your device before being send to the server. Some things like passwords are usually handled differently though, they are not readable by anyone.

That’s one of the reasons why picking an instance is a big deal. You trust that instance with moderation and handling of your data. If you’re not comfortable with any instance then you should look into hosting your own!

Same. Having all their custom software available and just one click away is amazing, and with Docker you can install everything else just like a regular server. It’s the best of both worlds imo.

If you don’t have any restrictions (limited subdomains, service only works on the server root etc.) then it’s really just a personal preference. I usually try paths first, and switch to subdomains if that doesn’t work.