19
Overseer: A Fediverse Chain of Trust (dbzer0.com)
submitted 3 years ago by to c/technology@beehaw.org
17 comments fedilink hide all child comments
 

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

This is my current attempt at preparing to counter the spam waves that will be appearing as the fediverse becomes more and more popular.

It involves the creation of whitelists based on a chain of trust between instances with easy ways to add and remove into it with few overheads.

Let me know what you think and if you're interested, please do register your instance at https://overctrl.dbzer0.com.

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 4 points 3 years ago (5 children)

The problem with blacklists is that it's trivial to make endless domains to spam. The fediverse avoided this by being too small to matter , but as the reddit exodus begins this is about to change

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 3 points 3 years ago (4 children)

    So require paid ssl certificates or something. I just can’t sign on to any system that requires me to establish personal friendships with other instance admins so I can beg them for endorsements. Begging Reddit to improve accessibility didn’t work. I have no interest in a system where my instance now needs to beg other admins for the right to federate. Even email doesn’t work this way.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 3 years ago (2 children)

    So instead of having to "beg for endorsements" you'd rather have to pay to set up a FOSS server?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 3 years ago (1 child)

    Yes. I already have to pay for a VPS, for a domain...nothing wrong with paying for an SSL cert. At least I can pick my vendor.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 3 years ago*

    I'm not sure how'd you accomplish this without requiring an EV cert, which is expensive and time-consuming to get, right? I guess manually maintaining a list of free CAs like Let's Encrypt? Idk, I'd never pay for a cert I'd have to manually update where my LE certs are all automatic.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 3 years ago

    Email does rely on IP reputation as a major component in deciding if something is spam. The system has matured to a point where it works fairly well and transparently ... but the consequence has been you can't reliably send from an IP block unless somebody is very actively handling abuse and working with the reputation services to keep their IP space in the internet's good graces.

    But: I wouldn't want to allowlist based just on one reputation service. I've got some ideas on how to handle spam for my instances involving a few different datapoints. This could be useful as one, if it ends up with enough data.

  • permalink
  • fedilink
  • source
  • parent