2 ms·
As someone running a federated server (mastodon); you get more problems with local spam than with foreign spam. Most instances will quickly shut down any spam,
by zaarn 8y ago
As someone running a federated server (mastodon); you get more problems with local spam than with foreign spam.
Most instances will quickly shut down any spam, so it doesn't really fill the federated timeline that much. Local accounts are something you as an administrator need to act on, so they are the annoying ones.
In my experience, instances that allow spam are rare and the get quickly blacklisted by everyone from showing up in the timelines (there is luckily a neat middleground between blocking the instance entirely and not doing that; allow local users to subscribe to that instance, which is my default action for all instances that aren't hosting illegal material for me).
- deleted 8y ago[deleted]
- zbqxu 8y agoIt doesn't look like that might scale at all. In other words, it works because Mastodon is a very small, niche community. Good thing is that the Mastodon instance owners use shared block lists for servers that are currently used to ban free speech instances; that infrastructure could also be used to create a collectively managed list of instances that are full of spam.
- zaarn 8y agoAtm shared block lists are still manual, but I'm hoping they'll become automated in the future...