What happens to orphaned communities when their host instance dies?
What happens to orphaned communities when their host instance dies?
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?
As of Lemmy 0.18.1, cached copies on other instances do not disappear if the original instance has died.
In theory, it might even be possible to actually clone a cached copy into a new local community. This would require some database hacking, so not recommended unless you're familiar with Lemmy code and SQL.
Not sure how it is on lemmy. But looking at the structure on kbin. I reckon you could (with a little sql magic) convert the existing one to a local magazine without cloning, and then people could subscribe to the new version or existing subs could also hack their sql to change the id to match the new instance and toggle the subscriptions.
On Lemmy though I think images are not cached locally. So you might lose those. Kbin by default will also download images/media locally too.
Not sure this would happen enough to add formal functionality for it though.
It's actually extremely easy to flip a remote community, into being a "local" one.
I actually wondered about that. The way instances share data and store it is all pretty black box to me.
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.
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.
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.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.
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)
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.
Lemmy is instanced. if the host "dies" everthing else dies with it. even the accounts and everything. as far as i understand it. maybe there will be a few cached posts from that instance but im not sure about that.
This is going to make it impossible for any technical help communities to take root. The fact that the whole thing can just go poof completely turns me off from using something like that.
Exactly, this is why things like stack overflow never came into existence.
I get the concern, but long term persistence is probably a rarity. The internet is still young. If anything a federated group of communities that are linked somehow will last far longer than a single server of even a large corporation. For the weeks that Lemmy et al have been growing, how to best develop communities that connect and last has been an ongoing question.
From memory posts are partially archived by Google's cache, so if they're indexed correctly people should still be able to search for something and have it as a result? Unsure if that would work if the whole domain is actually gone though
Not quite. Other instances subscribed to remote instances are sent the information about new posts, comments etc and they store them locally on that instance. So, while there's not be new content (since the main instance is the controller for all incoming content and distributes it back out, it would break the connection for new stuff.
There are manual steps an instance admin could take, to take it over. Probably it would need some agreement as to who takes it on.
I haven't bothered playing with instances yet I just made my account yesterday. I need another account if I leave lemmy.world?
This is a great question that I also would like to understand better.
The modern-day equivalent of "what happens to a dream deferred?"
Just started learning about the fediverse but I suspect everything goes down with the ship. Sort of creates a development opportunity for community driven backup utilities, though. Interesting problems are fun development challenges :)
I've been wondering about this also since I started a new community in the last week and have already invested a fair amount of time into it. I'm hesitant to keep investing time and effort, though, if it can just disappear with no recourse.
I wonder if the activitypub protocol (or, if not the protocol then some other layer) allows for the idea of "community mirrors". The way that the protocol works at the moment, as I understand it, only the host instance has a complete record of a community's posts and comments. But if there was a way for a community to designate one or more other instances as "mirrors" which maintain a complete sync of a community's content (going back all the way to the community's founding), that would lower the exposure to instances going down.
There would need to be a process (both technical and administrative) for a mirror to be designated as the new host instance should the original host disappear.
This would build in additional resilience into the fediverse model, by taking advantage of its distributed nature.