this post was submitted on 08 Apr 2025
54 points (98.2% liked)
Announcements
625 readers
1 users here now
lemmy.zip annoucements
The same rules as the main instance apply here.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I got the Lemmy equivalent of a jump scare. All of this has made me realize that Lemmy is actually quite fragile since a big instance can just vanish.
On the other hand, most content "from" any individual server still exists elsewhere in the network. I was following this thread even while lemmy.zip was down just by reading it from another instance.
While the entrypoint to the network can go down, nothing really goes away, you just have to jump to another server. All you really lose is the post history tied to your account--and the posts still exist, just under your old name.
I think you need Lemmy.zip working for comments from different instances to sync under Lemmy.zip community posts.
Yeah, I hadn't realized that but you're right. I originally come from the old dead kbin.social instance. I just checked an old community and I can see the posts, but new comments there don't propagate to other instances.
I wonder if there's any solution to that. Lemmy admins can move threads between communities, but I don't know if that works across instances. I wonder if a whole community from a dead instance could be moved to another instance by mass-moving all threads.
I think it is more of a limitation of activitypub and DNS. Any work around for this would be cutting out the original server which would likely be a major security risk.
Honestly what it should do is warn users when a instance is down and maybe even lock the community if it is without a local mod for to long. Maybe it could warn after is it down for a hour and then lock after 6 hours.