jdev - 2025-12-24


  1. lovetox

    Did we dicuss, sending a automatic spam report to the remote abuse address?

  2. lovetox

    currently in Gajim if i ban a user, i can chose to moderate all the messages, what if i add a checkbox that if checked, gathers the abuse xmpp adress and sends a automated message to the admin, with the content of one example message and the full jid of the spammer?

  3. lovetox

    would this be considered useful? or would there be a problem with that

  4. lovetox

    message would be sent only on user interaction, e.g. checking the box and confirming

  5. Guus

    lovetox, that's somewhat covered by XEP-0377 (currently under last call)

  6. lovetox

    Moving this to stable without a single example how to report a message as spam is wild

  7. lovetox

    The example with blocking is just not applicable to MUCs where we have the most annoying spam

  8. lovetox

    But i will add my concerns in the last call response then

  9. Link Mauve

    lovetox, stable just means draft, in a way that people will be less critical of.

  10. Link Mauve

    If you have changes to make, that’s totally still possible.

  11. lovetox

    the XEP limits its scope to blocking, and as such its a solution in that scope, but we definitly need more

  12. Guus

    I don't think this XEP intends to be a one-size-fits-all solution - instead, it tries to add an easy-to-use option to a mechanism already in use. I was just latching on to your "didn't we discuss this somewhere" question.

  13. lovetox

    yes i noticed that the title of the XEP does not fit to the introduction

  14. lovetox

    this mislead me

  15. lovetox

    I just write up my comments for the last call

  16. singpolyma

    > the XEP limits its scope to blocking, and as such its a solution in that scope, but we definitly need more it doesn't limit its scope there. but that's the currently only supported case by anyone so it's used in the example. I think with MUC we might be able to do pure reporting ("flag this message") but I haven't had time to write the server module yet

  17. singpolyma

    but yes https://modules.prosody.im/mod_report_forward.html is what I use for this "send to admin" purpose

  18. lovetox

    singpolyma: the scope is clearly reduced to blocking

  19. lovetox

    This specification extends the blocking command to optionally provide an abuse report.

  20. singpolyma

    it defines a new syntax to be used in abuse report contexts and the first use case identified is as part of blocking

  21. lovetox

    No that's not what this says

  22. lovetox

    You clearly think every text can afterwards changed and goals can be extended

  23. lovetox

    But that's not what we vote in a last call for example

  24. lovetox

    Does the specification solve the problem stated in the introduction and requirements?

  25. lovetox

    Yes it does. Does it solve the the problem of a missing base spec which can be applied to multiple contexts where reporting is needed? I would say definitely not. But that is not relevant because it's not a goal on the introduction.

  26. lovetox

    Yes it does. Does it solve the the problem of a missing base spec which can be applied to multiple contexts where reporting is needed? I would say definitely not. But that is not relevant because it's not a goal in the introduction.

  27. singpolyma

    it's always been the goal when discussed and it clearly seems solved by the text of the XEP. but if you think we need to make the wording clearer I'm obviously open to that happeneing

  28. lovetox

    I already sent my feedback to the list

  29. lovetox

    We can only judge the content of the XEP in last call, not what may have been discussed somewhere at some point

  30. singpolyma

    sure. obviously we disagree about what the XEP says as currently written which is enough reason to indicate it can be clarified

  31. lovetox

    Can you point to the sentences in the XEP which give you that interpretation, maybe I missed them

  32. Failed Clown

    How do I get started with jabber development?

  33. Failed Clown

    Any good youtube vids?

  34. lovetox

    singpolyma: or let's move discussion to the list, I'm away for today.

  35. singpolyma

    yeah. I fully agree with you that the current introduction does lend itself to thinking this is just about blocking

  36. singpolyma

    of course that still doesn't prevent reusing in other xeps. we should always reuse an existing namespace where possible, from any xep or even not from a xep. But saying it much more explicitly would make the XEP much better I fully agree

  37. Failed Clown

    Do you guys use Linux?

  38. Failed Clown

    Is it a required for development?

  39. Failed Clown

    Is it required for development?

  40. luca

    Depends on what you develop

  41. Failed Clown

    Jabber apps

  42. luca

    Depends on the jabber app :P

  43. luca

    But I wouldn't say Linux is required as a general principle

    πŸ‘ 1
  44. une

    Is '[' , ']' part of the domainpart, in ipv6 based xmpp server? Prosody service works with "VirtualHost "[my-ipv6]"", xmpp clients don't like connect to my server. I don't understand how it works. Please help. https://datatracker.ietf.org/doc/html/rfc6122#section-2.1 "... note well that reuse of the IP-literal rule from RFC 3986 implies that IPv6 addresses are enclosed in square brackets (i.e., beginning with '[' and ending with ']')".

  45. une

    I generated selfo signed certificate for my ipv6 server, and I added the self generated CA to the system CA store

  46. singpolyma

    probably you don't want to use a raw ip but a domain name of some kind?

  47. une

    probably. If I can make clients work without domain I would save money

  48. Failed Clown

    > Is '[' , ']' part of the domainpart, in ipv6 based xmpp server? Prosody service works with "VirtualHost "[my-ipv6]"", xmpp clients don't like connect to my server. I don't understand how it works. Please help. https://datatracker.ietf.org/doc/html/rfc6122#section-2.1 "... note well that reuse of the IP-literal rule from RFC 3986 implies that IPv6 addresses are enclosed in square brackets (i.e., beginning with '[' and ending with ']')". In XMPP, the domainpart can include an IPv6 address, but it must be enclosed in square brackets. Therefore, '[' and ']' are indeed part of the domainpart when specifying an IPv6 address. IETF hjp.at

  49. une

    πŸ‘

  50. singpolyma

    You can get free DNS name lots of places. Dynamic DNS services etc.

  51. une

    πŸ‘