Skip Navigation

Introducing The Lemmy Overseer

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.

Instance Admin | Mod Notes @lemmy.intai.tech

Introducing The Lemmy Overseer

1 0
Lemmy @lemmy.ml

Introducing The Lemmy Overseer

4 0
Technology @beehaw.org

Introducing The Lemmy Overseer

153 49

You're viewing a single thread.

16 comments
  • I added Dockerfiles to make containers of them for those running docker-compose Lemmy instances.

    https://github.com/db0/lemmy-overseer/pull/1

    • Cheers mate, I'm in bed atm so I'll check tomorrow

      • I got the client to run in a container on a cronjob docker run --rm --name overseer-eye -e LEMMY_DOMAIN=discuss.online -e USERNAME=overseer -e PASSWORD=<PASSWORD> lemmy-overseer-eye:latest

        I thought I'd containerize the server too, but it lacks a schema. Or I'm missing something?

16 comments