jdev - 2020-05-20

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

i want to implement more reporting options for the user

right now i would offer

- Block Contact - Report as Spam

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

or 0161, if thats implemented somewhere

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

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

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

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

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

MattJ: C does afaik

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

Zash: that's great!

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

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

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

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

Have fun with that :)

MattJ: It reports the JID tho, not the message

I think that's fine

ok so i can add that without the server supporting it

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

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.

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

Ge0rG, don't they support RFC 6331 ?

that code makes my eyes bleed.

Zash: apparently not

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

Ah, email on the mailing list about stepping down.