Conversation

Notices

1. Embed this notice
   Cherri (cheri@snug.moe)'s status on Sunday, 18-Feb-2024 00:51:37 JST Cherri

   tbh this spam wave shows how flimsy and scarily open-wild-west to anything the fediverse is.
   It worked while it was small but now uh yeah

   • :blobcathug: likes this.
   • Embed this notice
     Cherri (cheri@snug.moe)'s status on Sunday, 18-Feb-2024 00:51:47 JST Cherri

     in reply to

     like, I don't know if I said I am not happy with activity pub and the way fedi servers are as of now

     :blobcathug: likes this.
   • Embed this notice
     :blobcathug: (jain@blob.cat)'s status on Sunday, 18-Feb-2024 00:56:40 JST :blobcathug:

     in reply to
     @cheri nah, i doubt that this will work since nowdays shared blocklists are already a work of multiple individuals, except i dont think what they do is good...
     what i rather would prefer is better admin tools which could fix such issues tho
   • Embed this notice
     Cherri (cheri@snug.moe)'s status on Sunday, 18-Feb-2024 00:56:41 JST Cherri

     in reply to

     this may be a somewhat controversial opinion but fedi instances should be more vetted.
     Do you know how email has ban lists for servers that don't comply from a technical level or cause spam? maybe fedi should have something similar. There should be a level of responsibility demanded from admins to actually be federating on the fediverse; if one makes a instance with open sign-ups they should be damn sure they can handle it.
     Your instance has spam leaking around at one point? you are banned from federating until you clean up your mess and then claim/prove you took measures for it to not happen again (added more moderation to monitor the instance 24/7 or have manual sign up approvals)
     
     (And I know, this might sound similar to the hated centralized instance block lists but I think this can be 1. decentralized in some way .. maybe simply have multiple lists.. I think email does it that way and 2. purely for the purpose of technical non-compliance or spam and such, not including reasons that could be interpreted from admin to admin).
     
     This kind of vetting is pretty standard in other inter-communicating networks, since one poisoning the well with their node is going to wreck it for everyone.
     
     Not caring about such stuff worked while the fediverse was smaller, now it is going to become more and more of an issue.