@mudeth @pglpm The grey area is all down to personal choices and how "fascist" your admin is (which goes on to which instance is best for you?)
Defederation is a double-edged sword, because if you defederate constantly for frivolous reasons all you do is isolate your node. This is also why it's the final step in moderation.
The reality is that it's a whole bunch of entirely separate environments and we've walked this path well with email (the granddaddy of federated social networks). The only moderation we can perform outside of our own instance is to defederate, everything else is just typical blocking you can do yourself.
The process here on Mastodon is to decide for yourself what is worth taking action on. If it's not your instance, you report it to the admin of that instance and they decide if they want to take action and what action to take. And if they decide it's acceptable, you decide whether or not this is a personal problem (just block the user or domain on in your user account but leave it federating) or if it's a problem for your whole server (in which case you defederate to protect your users).
Automated action is bad because there's no automated identity verification here and it's an open door to denial of service attacks (harasser generates a bunch of different accounts, uses them all the report a user until that user is auto-suspended).
The backlog problem however is an intrinsic problem to moderation that every platform struggles with. You can automate moderation, but then that gets abused and has countless cases of it taking action on harmless content, and you can farm out moderation but then you get sloppiness.
The fediverse actually helps in moderation because each admin is responsible for a group of users and the rest of the fediverse basically decides whether they're doing their job acceptably via federation and defederation (ie. if you show that you have no issue with open Nazis on your platform, then most other instances aren't going to want to connect to you)