People like to say even temporarily blocking a spam-embattled instance is wrong, likening the system to email, and that we wouldn’t just block a big email domain for being spammy. Wouldn't we though? Expecting me to just put up with it is an absurd expectation. Be mad at the enormous instance admins who keep open registration. 🤷♂️
@superjosh my only concern with temporary blocking is that the implementation does not handle it as temporary at all, nothing's preserved
I've no reservations about permanently blocking instances that can't or won't get their shit together though 
@elfi Limit vs Suspend have their differences and I err toward limit. But yes, if it becomes a big enough problem, suspend saves me battling spam all day. I work for a living as I assume do most instance admins. Nobody is a prisoner on this instance and if you ask them, you’ll find most are here specifically because it’s invite-only and heavily curated/moderated to cut out the bullshit. If there’s a disagreement, it’s discussed openly. I’m not a dictator. 😂
@superjosh yeee, would be nice if the codebases had options for preserving data in the event of temporary suspensions, but at the end of the day, you aren't expected or obligated to deal with other instance's trashfires for them
