Public
- Public
- Network
- Groups
- Featured
- Popular
- People

Terminal interface showing the script "block-instance" being run. It first asks for an instance name, then the block level (block vs limit), and then a multi-select of block reasons, with SPAM being selected. After a couple of other questions, the script reports the instance being added to the block list, and commits the change in the git repo. It then checks for open reports, and asks if all 64 open reports should be closed. Upon confirmation, you see a progress bar tracking the reports being closed one by one.

Download link

Terminal interface showing the script "block-instance" being run. It first asks for an instance name, then the block level (block vs limit), and then a multi-select of block reasons, with SPAM being selected. After a couple of other questions, the script reports the instance being added to the block list, and commits the change in the git repo. It then checks for open reports, and asks if all 64 open reports should be closed. Upon confirmation, you see a progress bar tracking the reports being closed one by one.
https://assets.chaos.social/media_attachments/files/113/436/587/594/148/554/original/c2c7c6fc8126ee2a.png

Notices where this attachment appears

Embed this notice
rixx (rixx@chaos.social)'s status on Thursday, 07-Nov-2024 07:23:25 JST rixx

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:
#mastoadmin

In conversation about 16 days ago from chaos.social permalink