XSF Discussion - 2019-10-02


  1. jamescimelZi7qr

    H

  2. !XSF_Martin

    > XMPP has support for threading in RFC 6121 even, but no client does it because it’s unclear how to handle clients which don’t support or don’t want to support threads 🤔[1] 👍[2][*]

  3. !XSF_Martin

    Like this? Asterisk means you (e.g. your other client which supports reactions) reacted.

  4. !XSF_Martin

    I would drop the info who used which reaction for clients not supporting it.

  5. !XSF_Martin

    You can still find out by seeng who send the last reaction and comparing what changed.

  6. !XSF_Martin

    > but how to filter it out for clients that support it 🤔 Maybe two bodys. Reaction body and the legacy citation body. Like OMEMO does.

  7. !XSF_Martin

    But how to get rid of the overhead once it's widespread supported? Make it a 'SHOULD include legacy citation body' in the XEP, support it in the beginning and drop it in clients when you think it's no more necessary?

  8. jonas’

    j.r, also, that makes UX massively worse for clients which deliberately don’t support threads (because threads aren’t everyones cup of tea)

  9. pep.

    “xmpp:council@muc.xmpp.org/?join”, not to pick on Tedd (that appeared in his last email), I'm just curious if that's valid with the “/”

  10. jonas’

    it’s not

  11. jonas’

    methinks

  12. jonas’

    either it is "xmpp:" + jid + "?join", in which case `jid` is not a valid jid (empty resource), or it’s "xmpp:" + jid + "/?join" which has unspecified semantics

  13. Ge0rG

    As the JID part is technically a path in the URI, I wouldn't even categorically deny it being possible

  14. jonas’

    yes, but the semantics in any case aren’t what they are intended to be

  15. Ge0rG

    is it written down somewhere that a bare JID must not have a trailing /

  16. MattJ

    iirc it's written that the resource cannot be empty

  17. MattJ

    and by logical extension there is no valid JID that ends with '/'

  18. Ge0rG

    this is PRECIS land, then

  19. jonas’

    MattJ, correct

  20. Ge0rG

    xmpp: URI handling is badly integrated anyway.

  21. ralphm

    I can confirm the variant with nothing between / and ? is not valid

  22. ralphm

    The relevant production in RFC 5122 is: pathxmpp = [ nodeid "@" ] host [ "/" resid ]

  23. dwd

    is resid limited to minimum 1 character though?

  24. theTedd

    re: "/?join" -- I just copied from one of Dave's mails, so I can claim innocence :D

  25. pep.

    :P

  26. Zash

    dwd: Minimum 1 byte probably

  27. edhelas

    is XEP-0172: User Nickname still used ?

  28. edhelas

    I'm wondering if some modern clients actively uses that one

  29. edhelas

    if not I might remove the +notify in Movim and delete the related column in the db

  30. lskdjf

    edhelas, afaik at least conversations and gajim use it