This episode has made it clear Lemmy software needs to improve in several ways to be resiliant to the problem. The possible #LemmyBug/enhancements:
â the fix was apparently not just flipping a switchâ it required hacking the db, correct? Shouldnât admins have a simple undelete button?
⥠what if a rogue admin had deleted the community, and perhaps even destroyed the db? In principle it should be possible to rebuild the community on a different node using data from all nodes that have data. Sometimes a whole node goes down. The plug gets pulled when funds run out. We are hosed when that happens.
âą each userâs subscriptions panel should not simply quietly cease to list the deleted community. The community name should remain and have indicators to signal issues (e.g. đ, â ).
⣠msgs users write are stored in their profile & responses are stored in their inbox. But this is poor organization on its own. It only serves to quickly see new msgs/reactions, but users are overly dependent on the serverâs representation of the community to show threads in a coherent way. Clients should have that capability too. I should be able to click âcontextâ on any msg and the client should be able to show me a sequence of msgs regardless of the state of the server host.