A good example is https://lemmy.world/c/documentaries
One of their mods, https://lemmy.world/u/sabbah, currently mods 54 communites despite only being on Lemmy for about a month and has never posted on c/documentaries (except for his post asking for people to join his mod team).
The other mod, https://lemmy.world/u/AradFort, has one post to c/documentaries and moderates 18 communities.
Does Lemmy.World have a plan to remove this kind of cancer before we start getting reddit supermods here too?
Edit: This comment shows how this is even more dangerous than I had thought.
Edit2: Official answer from LW admin is here
Final: Was going to create an issue for this on the Lemmy github, but I browsed for awhile and found that it had already been done. If anyone wants to continue the discussion there, here it is - https://github.com/LemmyNet/lemmy/issues/3452
Perhap we need another issue for the problem in the original edit (It being impossible currently to remove a 'founding' mod without destroying either the community of their account)
No, its the entire point of a federated system. If one instance goes down, you can create an account on another instance and continue browsing posts from all other servers still online. No one server has complete control of the system.
@DragonAce Okay, but that was not my point. One can improve usability of a decentralized systems. It does not need to be a bad user experience and waste of time.
How is it a bad user experience? Because you have to make an account on another instance? You can still browse from another instance without logging into it.
How would you suggest they improve the user experience without expecting them to have some sort of centralized login server? Having any sort of centralized user management leads to a single point of attack for anyone looking to exploit the system.