Do they get adopted by other instances? Are they still accessible from other instances? Can you still post on them from another instance?
Edit: From my understanding every instance that deals with a community has a cached copy. Will that copy disappear after a certain time, because it can’t phone to home anymore?
If I understand the fediverse correctly, if the instance dies (meaning all the background servers are taken away), everything on that instance is gone; accounts, communities, posts, comments. Since the instance is the host, they are the ones holding the data; if they decide to stop, it’s gone.
However, the creator of the community and its members could create new accounts on another instance to rebuild the community.
Afaik posts and comments are copied locally to federated instances so if the original went down you could still access what was once there from some other instance.
E.g everything (excluding uploaded images/videos) on https://sopuli.xyz/c/technology@beehaw.org would still be there without beehaw.
Hi there! Looks like you linked to a Lemmy community using an URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: !technology@beehaw.org](https://sopuli.xyz/c/technology@beehaw.org)
Once a user on instance A subscribes to a community on instance B, then instance A starts caching posts from the community on B. But to my understanding it doesn’t retroactively fetch all historical posts and comments.
When that’s the case, wouldn’t it be nice to be able to migrate communities, so when an adminndecides to quit an instance, those communities that want to move can arrange that move.
I agree that would be nice. Hopefully it is something that will eventually get added as a possibility, but I don’t know enough about the background workings to say if it is being considered or not.
I think it needs the ability for multiple hosts to opt in to co-hosting a community. It could work as a cache and provide some redundancy if something goes down, temporarily or permanently.
I’m hoping for account linking so you can have multiple synced accounts between instances so if one goes down due to load or permanently you can seamlessly continue without any issue.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !fediverse@lemmy.world
A community to talk about the Fediverse and all it’s related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
Posts must be on topic.
Be respectful of others.
Cite the sources used for graphs and other statistics.
If I understand the fediverse correctly, if the instance dies (meaning all the background servers are taken away), everything on that instance is gone; accounts, communities, posts, comments. Since the instance is the host, they are the ones holding the data; if they decide to stop, it’s gone.
However, the creator of the community and its members could create new accounts on another instance to rebuild the community.
Afaik posts and comments are copied locally to federated instances so if the original went down you could still access what was once there from some other instance.
E.g everything (excluding uploaded images/videos) on https://sopuli.xyz/c/technology@beehaw.org would still be there without beehaw.
Hi there! Looks like you linked to a Lemmy community using an URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: !technology@beehaw.org](https://sopuli.xyz/c/technology@beehaw.org)
Once a user on instance A subscribes to a community on instance B, then instance A starts caching posts from the community on B. But to my understanding it doesn’t retroactively fetch all historical posts and comments.
When that’s the case, wouldn’t it be nice to be able to migrate communities, so when an adminndecides to quit an instance, those communities that want to move can arrange that move.
I agree that would be nice. Hopefully it is something that will eventually get added as a possibility, but I don’t know enough about the background workings to say if it is being considered or not.
I can’t imagine that archiving and instance migration aren’t on the hub roadmap, but they’re probably well beyond the horizon.
Nascent tech rarely prioritizes development for contingencies like it’s own decay/demise.
Bad mojo. 😆
I think it needs the ability for multiple hosts to opt in to co-hosting a community. It could work as a cache and provide some redundancy if something goes down, temporarily or permanently.
The accounts are gone-
But, communities, posts, comments are all replicated. With a single flip of a bit, you can take that cached copy, and turn it into a local community.
Users would need to re-subscribe/follow/etc, but, all of the data would be there.
I’m hoping for account linking so you can have multiple synced accounts between instances so if one goes down due to load or permanently you can seamlessly continue without any issue.