I am well aware of the Mastodon bitcoin spam issue at the moment, if you are reporting accounts please double check if the account has already been suspended remotely first before reporting it, otherwise it just floods our report inbox with dead accounts that are already suspended.
@Violet oops, that can happen?
@halcy yep. I assume it's just because the suspension hasn't federated properly in time before the post gets reported
@Violet I kind of want to start making just like, a general suite of Admin Tools with a web interface and I guess "autodismiss reports where the remote got bonked" would be one useful thing
@halcy yeah. There's also multiple cases of reports appearing where the account is already listed as "SUSPENDED" next to the unresolved report
@Violet (other ideas: "create reports for all accounts that match some query", where query could be something like "newer than X, from domain Y, username or posts similar to These Three Examples")
@Violet (that last one is something I've been wondering about for a while, specifically: would people be generally okay with a script scanning incoming posts by newish users for anti-spam purposes, essentially doing text embed + compare to known spam posts, and reporting accounts with hits? Would that be accurate enough to be useful for us as admins? Worth doing given that our spam problems are so minor currently that when there is crypto spam it's such an outlier even that everyone talks about it for the rest of the day?)
@noiob @Violet removed in 3.4.0 as far as I know, for reasons of "hasn't flagged a single actual spammer and the dependency is unmaintained": https://github.com/mastodon/mastodon/pull/16011
@noiob @Violet It doesn't anymore, because after the wife guy spammer was gone it basically didn't trigger forever, which is part of the reason why I'm leaning Might Not Be All That Useful, For Now on that last point