Interesting bit of news for the threadiverse. All three of these are fairly large lemmy instances
I’m not denying that it sucks, but if you’d told anybody this was going to happen a month ago they’d have just laughed at you. Of course they were unprepared. Everbody has more than they can deal with. Adding more mods isn’t as simple as picking some names out of a hat, and this isn’t a thing anyone was preparing for. There currently are no alternative moderation systems, everything is too new and until recently was all way to small for that to be important, and they just have more work then they can deal with trying to suddenly moderate all of the threadiverse.
This was a bad option that sucked, but every option was a bad option that sucked. I’m more concerned with how they deal with things as they normalize over the coming weeks and months than I am with how they’re trying to put out the fires in the short term.
But they chose a nonstandard moderation strategy that limited their ability to scale moderation with users. The default system is that communities are moderated independently of admins (not saying admins don’t form communities or that there’s no overlap between admins and mods) whereas on beehaw only the admins can create communities and therefore are the primary moderators.
Now I’m not saying that there’s anything inherently wrong with the system they’ve chosen but the fact that it is nonstandard and in fact built into the core precept of beehaw means that this was easily foreseen.
Easily forseen if you knew that lemmy was suddenly going to have a hundred times as many users in the space of a couple weeks. That was the thing no one was prepared for though.
A couple of weeks is more than enough time to realize where things were headed and act. lemmy.ml managed to do it.