@aburka @unlambda @futzle yes. Futzle's description looks as if not automation is the issue but Mastodon's handling of reposts.
For hypebot it would of course be possible to maintain a central filterlist for people opting out that all hypebot instances refresh periodically. But that still would need people to do that kind of opt-in (for example via a message to a specific Fediverse account to ensure a person can only opt out their own account)
Discussion
Loading...
Post
@tante @aburka @futzle Another possibility would be for the hypebot to set its own blocklist, of a number of prominent known bad instances. User accounts in Mastodon can set their own domain blocklists, if the hypebot did this it would help with the problem described.
Of course, it has all of the problems of maintaining such a blocklist; unfortunately that's become quite a contentions topic. But it probably wouldn't be hard to put together a list of a few of the worst offenders and help reduce the problem.
RE: https://tldr.nettime.org/@hypebot/115576838331029128
@futzle @aburka @unlambda So at least the #nobot thing should help you now with current hypebot versions
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled