Gregory's Server
first off: screening new signups has helped us a lot.
when we first launched treehouse mastodon, because we have high profile community members, we attracted trolls basically immediately whose goals were to disrupt operations of the instance.
the most notable incident involved a person who signed up for an account and then immediately uploaded multiple pieces of media which were CSAM.
this actually has wound up going very badly for that person, who has had to cancel his podcast several times because his door has gotten kicked in by law enforcement due to this, and other maladaptive behavior.
when folks complain about getting crapflooded -- their complaints are real.
as has recently been highlighted -- in the case of BIPOC, these crapflooding trolls tend to flood users with racial slurs or similar.
in the case of non-BIPOC, these crapflooding trolls tend to use other angles of cheap low-effort insults in their crapfloods.
but crapfloods cause users to have a bad experience, regardless of what the flavor is.
we have built custom tooling to deal with various styles of crapflooding attack, by simply hacking automated mitigations into the mastodon codebase. there are a few feature flags on the treehouse mastodon fork to turn on and off those mitigations.
mitigating crapfloods with automation is essential to ensure a moderation team can scale. otherwise the moderation team will spend a lot of time cleaning up crapfloods.
defederating typical sources of crapfloods is also recommended, but we have dealt with trolls who farm accounts on normal instances that wouldn't typically be defederated.
so you really need automation here.
when folks complain about getting crapflooded -- their complaints are real.
as has recently been highlighted -- in the case of BIPOC, these crapflooding trolls tend to flood users with racial slurs or similar.
in the case of non-BIPOC, these crapflooding trolls tend to use other angles of cheap low-effort insults in their crapfloods.