Post AMSTGHYvwSb0YDL8EK by emacsen@emacsen.net
 (DIR) More posts by emacsen@emacsen.net
 (DIR) Post #AMRyG4ah4a7Fk0aEYi by dansup@mastodon.social
       2022-08-12T11:21:07Z
       
       1 likes, 6 repeats
       
       Spammers are targeting large fediverse instances with SEO spam yet it's the smaller instances that are most affected.🧵 (1/4)
       
 (DIR) Post #AMS5RPKkzULCwGTsaO by betothebop@mastodon.gamedev.place
       2022-08-12T12:22:23Z
       
       0 likes, 0 repeats
       
       @dansup I don't fully understand why account deletion is federated. Is account creation also federated. I'm new to Mastodon.
       
 (DIR) Post #AMS5RPnpFPaqOQ55tY by konni@toot.kartonrad.de
       2022-08-12T12:41:50Z
       
       0 likes, 0 repeats
       
       @betothebop @dansup > account is made> posts illegal content> content spreads to remote servers> hoster catches on and deletes account> post is still on remote instances and possibly boosted to reach more than just the followers' instances> thus, origin instance has to federate the account deletion to every known instance
       
 (DIR) Post #AMSTFhv0SurU0FOFdY by dansup@mastodon.social
       2022-08-12T11:21:17Z
       
       0 likes, 0 repeats
       
       When a spam account is deleted from a large instance like mastodon.social, they federate the account deletion to every known instance. This means your server has to check if that account exists and delete it if so. Account deletion is an expensive process but one that is required. The issue with this is how small servers are subjected to these constant activities from larger servers that are likely more able to deal with this.🧵 (2/4)
       
 (DIR) Post #AMSTFjQwpe0QhbLH3w by dansup@mastodon.social
       2022-08-12T11:21:40Z
       
       0 likes, 0 repeats
       
       Ideally small and large servers wouldn’t be impacted by spammers from remote instances. The onus should really be on each instance to prevent spam registration (and account deletes), that’s easier said than done. Pixelfed is the only fediverse project with an automated spam detection system, and while it prevents about 80% of spam content, it’s not perfect.🧵 (3/4)
       
 (DIR) Post #AMSTFl7sXVwNx2R4cK by dansup@mastodon.social
       2022-08-12T11:21:52Z
       
       0 likes, 0 repeats
       
       I can’t prevent spam on remote instances, but I can improve Pixelfed’s automated spam detection for both small and large instances with an optional anti-spam service I’ve been working on! I look forward to sharing more details soon!🧵 (4/4)
       
 (DIR) Post #AMSTGHYvwSb0YDL8EK by emacsen@emacsen.net
       2022-08-12T13:39:36Z
       
       0 likes, 1 repeats
       
       @dansup I'm writing a generic ActivityPub anti-spam system for all ActivityPub servers and should have a prototype to show in hopefully 2 weeks!I'd be interested in collaborating if you want!
       
 (DIR) Post #AMSpSd8tjPjtwlSGye by suetanvil@mastodon.technology
       2022-08-12T13:12:49Z
       
       0 likes, 0 repeats
       
       @dansup I'm dubious about the cost factor because:1. The whole thing is automated.  The real cost of an instance is admin time and this uses none of that.2. This turns into something on the order of one transaction per instance per deleted account.  That's a drop in the bucket.  And if this *is* a huge resource hit for individual instances, this is an implementation issue or a protocol issue, *not* a social issue.
       
 (DIR) Post #AMTbQJnNUKMJACLulc by james@mstdn.starnix.network
       2022-08-13T06:14:57Z
       
       0 likes, 0 repeats
       
       @emacsen @dansup Oh Great, ActivityPub is turning into email all over again.