XMPP Service Operators - 2023-09-01

  1. MSavoritias (fae,ve)

    For rtbl raizen@draugr.de Your garden variety racist stuff in the manga room

  2. Menel

    I wonder.. Is a user spamming a question in a room like two days ago or someone doing racist stuff in one room for a universe wide blocklist? Or is it for the room moderators? I thought this blocklist for all rooms is more for the accounts doing harm to all rooms? There are no written rules or even guidelines yet, or are there?

  3. jonas’

    the blocklist operators discussed this

  4. Menel

    What was the conclusion?

  5. jonas’

    in general, the RTBL should only contain cases where it is anticipated (or already happening) that it spreads over the network.

  6. jonas’

    "the RTBL" being that one instance of the RTBL everyone is talking about.

  7. Menel

    (Yes, it is the official standard now 🙂.) Thanks for the info.

  8. MSavoritias (fae,ve)

    jonas’: so cases like this are not blocked from that one instance?

  9. Licaon_Kter

    Current cases were already network wide when actioned upon.

  10. jonas’

    MSavoritias (fae,ve), I don't think so, unless it's in more than one MUC.

  11. MSavoritias (fae,ve)

    Ok. Just wanted to know

  12. jonas’

    MSavoritias (fae,ve), to clarify: this specific RTBL got instantiated to fight network-wide network abuse (less than human abuse). There's definitely room for an RTBL which targets individual doing *human* abuse more than *network* abuse, to protect people affected by that abuse across the network (faster response at the risk of more false-positives (because of less vantage points before actions)).

  13. MSavoritias (fae,ve)

    i agree. and i understand. i am thinking something akin to the badspace 🙂

  14. jonas’

    I would also not be opposed to re-using the existing RTBL infrastructure for that, but I don't run it, so other people have a say in that :)

  15. MSavoritias (fae,ve)

    i have more in mind something like: https://thebad.space

  16. MSavoritias (fae,ve)

    i do think that if we go in that direction (badspace) the blocklists will be for entirely different purposes. and thebadspace blocklist is much more restrictive

  17. MSavoritias (fae,ve)

    but i wouldnt be opposed to also add them to the current RTBL we have. if the others agree 🙂

  18. jonas’

    by "existing RTBL infrastructure" I do not mean the specific endpoint (I wouldn't like to mix them), but the tooling around it as well as potentially the domain name.

  19. MSavoritias (fae,ve)

    ah yeah. i have a question: can you block servers with the rtbl?

  20. jonas’

    I'd assume so

  21. jonas’

    if it's not possible yet, it's a trivial change

  22. MSavoritias (fae,ve)

    nice. thank you

  23. Menel

    The more interesting change would be to be able to subscribe to more then one rtbl. Blocking servers, we can already. It might not be real time. But I don't think it is nessesary to block whole servers in real time.

  24. jonas’

    Menel, also not *too* complex to implement really. I guess that'll happen quickly once there is more than one RTBL

  25. jonas’

    (just like the RTBL client modules evolved rather quickly when the first RTBL hit)

  26. MSavoritias (fae,ve)

    im thinking more of a curated blocklist that you can subscribe.

  27. MattJ

    Yes, domains may be listed in the current RTBL, and implementations should handle it (it's mentioned in https://xmppbl.org/#for-developers )

  28. MattJ

    We've never done so, and I would like to hope we never need to, but it could be necessary (and still isn't actually enough, yet)