This really showcases how weak the #Lemmy infrastructure is.
If a rogue moderator or admin decides to nuke an entire community of thousands of people’s works & a long history, and scrub the existence of that group so well the name of it is even lost, there are fragments of that group mirrored across hundreds of other nodes. The community & history should be rebuilt in less than 1 hour on a new host (perhaps the host with the 2nd most amount of content).
Just to make sure I understand the problem (because I am also interested in a fix to this) —
A moderator or admin deleted a Lemmy community.
And that deletion causes all posts to the community to not just be deleted from that server, but to also be deleted on every other Lemmy server (that was replicating it)?
Info is still unfolding but the data is apparently not lost. A mod deleted a community and the admins can still see the posts & reactions. But of course the whole public lost visibility on it. The admins are researching how to restore visibility to the public and apparently there are federation issues. Users can enter their profile and see their own posts to that group. They can also still see replies to them in their inbox. But the community gets renamed to deleted@$instance so it’s a mess.
So it turns out the creator of the community deleted the community then deleted his own account.
The data remained in the DB. The fix was for an admin to flip a boolean in the DB somewhere, as I understand it. All nodes that federated with that community need to refederate which for some reason can take hours.
Add comment