 So, when you block an instance as a mastodon administrator, on account of that instance spewing spam like mad and also none of your users following anybody there, this will NOT resolve any of the >100 reports your users have openend against that instance, despite the reports now being useless. And of course, Mastodon still has no bulk editing of reports, so you die the death of a thousand ~~papercuts~~ report-clicks … or you just add report-resolving to your management script: 2 comments
Why do we already have a script that handles instance blocking for us, you ask? Well. First off, we want to publish the list of blocked instances on our website, with reasons where sensible. Internally, the full list contains a ton of dead instances that don’t make any sense to publish, so we handle it like this. But I’m glad we do, because as it turns out, the Mastodon audit log for instance blocks is utterly useless, so having the true story logged to a git repo is due diligence. #mastoadmin |
Gregory's Server
Also pictured: I did end up closing around 50 reports manually before coming to my senses and automating the whole thing.
I can already tell you that the next step will be an option to close all reports against an instance *while suspending the reported users* when we limit an instance for spam.