The history of mastodon.social - the one that has been historically run and moderated by the creator has been shown to be and called out multiple times for not moderating well.

Part of that is because it was allowed to get too big and part of that is that because of that they didn’t have enough moderators (especially not ones that were paid).

This led to design decisions for both the web interface and the ‘official’ mastodon app that made moderation (such as one of the report options sending your report into the null) and the general experience (such as removing one of the timelines from the from the ‘official’ app) worse.

The tools for moderators and admins are also somewhat laughable and often display warnings which mastodon.social ironically doesn’t follow or does all too well, depending on whether it’s unhelpful or helpful for them personally to do so.

That’s what I mean, not necessarily individual instance moderation, though as I have shown (not) doing good instance moderation if you’re the developer helps develop tools and designs (which is part of the the problem/solution). But also a community orientated approach and actually paying attention to what folks are saying about an instance and the tools and things that are developed to help out, or as a consequence of any decisions taken or not taken in moderation.