But the downfall I see is now we have to rely on multiple instances to keep lemmy as a whole running. Whereas with unfederated they are larger scale and probably are more efficient/cost effective with backups. Where as a smaller instance may not be able to make it then we loose lots of data.

I think this would be good if we can migrate data. Say for instance if my instance had to go under for finance reason I can post the “data” files and someone could fork my instance and everything is then recovered. Or maybe even add to existing instance.

This seems majorly flawed. If lemmy.world went down we would then loose a lot information/posts.

Shouldn’t there be a timeout period of some sort, or a way to open a new community of the same name on another instance? Maybe even a backup instance? So say for example

A community on lemmy.ml is created. Let’s call it awesome-community. The moderators of awesome-community set backup of awesome-community to lemmy.world awesome-community. Then all instances on fediverse will see that information and if a user tries to view awesome-community lemmy.ml and it says offline then it redirects to awesome-community on lemmy.world.

I think having redirects for offline communities would be great. Even if you could set a timeout feature so say after 24hrs offline redirect. If not been 24hrs then just show it’s offline.

I would documented everything as I go.

I am a hobbyist running a proxmox server with a docker host for media server, a plex host, a nas host, and home assistant host.

I feel if It were to break It would take me a long time to rebuild.

Where I can’t find it :s

how do i get this?