XSF Discussion - 2020-11-11


  1. DebXWoody

    A question for XEP-0384 ( OMEMO ) - Section: 5.3.1 Device list NOTE: as per XEP-0060 §12.20, it is RECOMMENDED for the publisher to specify an ItemID of "current" to ensure that the publication of a new item will overwrite the existing item. Is it a RECOMMENDED or should it be a MUST?

  2. flow

    DebXWoody, well the protocol won't break if you don't follow this, only the pubsub node will accumulate more (unnecessary) items over time. IMHO that does not justify a MUST, not even a SHOULD

  3. flow

    hence RECOMMENDED seems to be sensible in this case

  4. DebXWoody

    flow, "the protocol won't break" I agree. But OMEMO won't work well, I guess. On functional point of view there should be just *one* device list per account. Am I right? The protocol should define the technical way to find a solution of the functional requirement. If the should be *exactly one* device list, the protocol should say this also. ( This is what I think) If it is recommended, how should I manage the different devicelists? Just merge all?

  5. Zash

    The server might have default of 1 max items.

  6. flow

    DebXWoody, there is only one valid device list: the one in the latest item of the pubsub node

  7. flow

    possible that the XEP should spell that out explicitly. it is probably not done since it is a reoccuring design pattern in XMPP

  8. DebXWoody

    Thx, I need to investigate with the user and try to fix the implementation.

  9. jonas’

    flow, FWIW, RECOMMENDED == SHOULD

  10. flow

    right, i always get that wrong

  11. Zash

    So it's probably fine.

  12. Zash

    Ge0rG, re ibr-token, do you happen to know if there's like research or something in that direction saying that captchas are terrible?

  13. Ge0rG

    Zash: I'm sure there is. I only have first-party anecdata.

  14. Zash

    Non-blocking but I think it'd be nice to have that claim backed up by something.

  15. Zash

    Hm, is there a way to express "here's an endpoint with SASL ANONYMOUS you can connect to" with XMPP URIs?

  16. Ge0rG

    Zash: I don't think so, but you might use something like xmpp://domain

  17. Ge0rG

    technically, that'd mean connect by xmpp with no or default username / password

  18. jonas’

    is that true?

  19. Zash

    Yes

  20. Zash

    Same way http://example means to connect there with http

  21. Neustradamus

    Lance has solved a lot of problems today (all tickets have been closed), but how to test it to confirm? - https://github.com/legastero/stanza/

  22. Zash

    Anyone have anything to say about the compliance suite?

  23. Guus

    Can it be purple/

  24. Guus

    Can it be purple?

  25. jonas’

    Guus, <editor-hat>no, we don’t do extra stylesheets for XEPs</editor-hat>

  26. Zash does a diff against the last CS

  27. Ge0rG

    Zash: https://xmpp.org/extensions/xep-0443.html#changes-2020

  28. Zash

    TOO LATE, already voted

  29. Ge0rG

    I'm still in the conference call

  30. Zash

    Dang, forgot to /activity in_a_meeting

  31. Seve

    😂

  32. Zash

    And now it's tooooooo late

  33. marc

    Btw, is there a channel for client and server devs?

  34. MattJ

    jdev on this server

  35. jonas’

    xmpp:jdev@muc.xmpp.org?join

  36. marc

    jonas’: thanks!