jdev - 2020-05-20

  1. lovetox

    does some server implement https://xmpp.org/extensions/attic/xep-0161

  2. lovetox

    i want to implement more reporting options for the user

  3. lovetox

    right now i would offer

  4. lovetox

    - Block Contact - Report as Spam

  5. lovetox

    and on Report as Spam, i would block the contact and send a automatic message to the abuse contact of the server

  6. lovetox

    or 0161, if thats implemented somewhere

  7. MattJ

    lovetox: there are several of these, I personally prefer the latest and simplest: https://xmpp.org/extensions/xep-0377.html

  8. MattJ

    I think there may be a prosody module, can't remember

  9. MattJ

    I think the main issue with this one was that some people didn't like mixing reporting and blocking

  10. MattJ

    The other problem is that I couldn't get a single client developer to implement it

  11. Ge0rG

    I've said time and before that spam *reporting* is not the problem that we need to solve. ✎

  12. Ge0rG

    I've said time and again before that spam *reporting* is not the problem that we need to solve. ✏

  13. Zash

    MattJ: C does afaik

  14. MattJ

    Ge0rG: and I've said time and time again that I disagree :)

  15. MattJ

    Zash: that's great!

  16. Ge0rG

    There is no value in forcing users to jump through hoops just to have yet another line in prosody.log ;)

  17. MattJ

    Just you wait until I feed those logs to my AI and teach it to automatically detect spam before it is sent!

  18. Ge0rG

    MattJ: sure. We can bring up reporting again, _then_.

  19. Ge0rG

    Until that, don't distract me from reading and extracting spam patterns manually from my huge prosody.log

  20. MattJ

    Have fun with that :)

  21. Zash

    MattJ: It reports the JID tho, not the message

  22. MattJ

    I think that's fine

  23. lovetox

    ok so i can add that without the server supporting it

  24. lovetox

    it would just be ignored on a server that does not implement that

  25. Ge0rG

    obscure issues for 300: a yaxim user has asked for help because suddenly yaxim started throwing a "DIGEST-MD5 incorrect-encoding" error. This looks related to an old OpenFire issue (https://discourse.igniterealtime.org/t/saslerror-using-digest-md5-incorrect-encoding/72711) but the user is running jabberd2 and claims not to have changed anything on the server.

  26. Zash

    Hmm https://github.com/jabberd2/jabberd2/search?q=_sasl_err_INCORRECT_ENCODING&type=

  27. Zash

    Ge0rG, don't they support RFC 6331 ?

  28. Ge0rG

    that code makes my eyes bleed.

  29. Ge0rG

    Zash: apparently not

  30. Zash

    > This repository has been archived by the owner. It is now read-only. ... but nothing anywhere else confirms that? weird

  31. Zash

    Ah, email on the mailing list about stepping down.