cross-posted from: https://lemmy.dbzer0.com/post/95652

Hey everyone, you may have noticed that some of us have been raising alarms about the amount of spam accounts being created on insufficiently protected instances.

As I wanted to get ahead of this before we’re shoulders deep in spam, I developed a small service which can be used to parse the Lemmy Fediverse Observer and retrieve instances which are suspicious enough to block.

The Overseer provides fully documented REST API which you can use to retrieve the instances in 3 different formats. One with all the info, one with just the names, and one as a csv you can copy-paste into your defederation setting. You can even adjust the level of suspicion you want to have.

Not only that, I also developed a python script which you can edit and run and it will automatically update your defederation list. You can set that baby to run on a daily schedule and it will take care that any new suspicious instances are also caught and any servers that cleared up their spam accounts will be recovered.

I plan to improve this service further. Feel free to send me ideas and PRs.

That’s a cool idea. Thanks for your work!

One question: Let’s say the script defederates an instance and then the admin of that instance cleans up their database and makes sure no new bots can register. Would your script remove them from the blacklist or would I have to manually check if all instances on my blacklist are still “infested” to give them a second chance?

permalink
report
reply
1 point
*

If you run my script in a schedule it should remove them from the defederation list yes

permalink
report
parent
reply
17 points

Thank you for trying to get ahead of the spam influx. Trying to beat the spambots is a thankless task, but thank you anyhouw.

permalink
report
reply
2 points

maybe that’s a dumb question, so sorry for that, but wouldn’t it be easier to just use a whitelist for federation instead of a blocklist?

permalink
report
reply
8 points

Mostly because it would invalidate any single user self hosted instance, which I fin is one of the big draws of the fediverse in general.

permalink
report
parent
reply
14 points

That would lead to having to manually approve every instance by the admins. Mods can’t do that so it would 100% be on them to keep up with all the instances

permalink
report
parent
reply
1 point

undefined> Leaf

I see, yeah that would be close to impossible in the long run… Thanks for the info!

permalink
report
parent
reply
14 points

I feel like the python script is maybe a bit too extreme ? 20 times more users than posts might happen on smaller instances people use mostly to browse the big ones, I feel. I ran it with a suspicion ratio of 100 and it didn’t seem to block any “legit looking communities”. But then again, it is very hard to tell.

Thanks a lot for your work !

permalink
report
reply
14 points

Yes, that’s why I leave the exact number up to each instance admin

permalink
report
parent
reply
6 points

Indeed, thanks a million for giving the community tools at this critical juncture. Very much appreciated!

permalink
report
parent
reply
7 points

I’m loving the innovation in the fediverse, and all the people seeing issues, bringing them up, and people at least attempting to fix.

permalink
report
reply

Technology

!technology@beehaw.org

Create post

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community’s icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

Community stats

  • 2.6K

    Monthly active users

  • 3.4K

    Posts

  • 82K

    Comments