XSF Discussion - 2023-04-18


  1. flow

    isn't that just a matter of immutable RFCs? that said, lovetox, feel free to fill an errata for RFC 5122, so this isn't lost in case an rfc5122bis happens. however, it is hard to imagine that an update to rfc5122 will not reference the current XMPP address rfc

  2. mjk

    a more pressing question is how to correctly generate "omemo verification URIs" when `iquerycomp` wants an `iquerytype` before the params. status quo just omits it. what would be an already standardized querytype most appropriate here that's also unlikely to break existing implementations? `xmpp:foo@bar?message;omemo-sid-123=abcdef` maybe?

  3. mjk

    I also question the ABNF in saying iquerytype and ipair can be empty strings

  4. mjk

    oh wait, `*` means "one or more" probably

  5. mjk has to cure their regexitis

  6. mjk

    nope, not this time. `*` means `0*♾`: https://www.rfc-editor.org/rfc/rfc5234#section-3.6

  7. mjk

    nope, not this time. `*` means `0*∞`: https://www.rfc-editor.org/rfc/rfc5234#section-3.6

  8. lovetox

    `xmpp:foo@bar?omemo;sid=abcdef` would be more approriate i think

  9. mjk

    would need standardization and changing implementations. I'm looking for a way that would work right now :)

  10. mjk

    on the generation sied

  11. mjk

    on the generation side

  12. lovetox

    you have a non standard uri, it doesnt really matter in which way you change it, as it adheres to no standard, you can only guess if a parsing client would break or not

  13. mjk

    "parsing clients" set is likely == {Conversations}, so that simplifies the task :))

  14. lovetox

    are you suggesting only Conversations support omemo?

  15. lovetox

    or do you mean only smartphones need that uri?

  16. lovetox

    because there are a lot of clients who support omemo

  17. Daniel

    fwiw i think `xmpp:foo@bar?messgae;omemo-sid-123=abcdef` would not break Conversations

  18. mjk

    thanks Daniel

  19. mjk

    lovetox: I mean I'm not aware of any client that parses this kind of URIs

  20. mjk

    lovetox: I mean I'm not aware of any other client that parses this kind of URIs

  21. lovetox

    i guess the original intent was to communicate it via QR code

  22. mjk

    yes, that's why I suspect there might be other mobile clients that support it

  23. lovetox

    so that would only make devices with camera and integrated QR code parser affected

  24. mjk

    in particular, iOS is a totally blind spot for me

  25. moparisthebest

    > so that would only make devices with camera and integrated QR code parser affected So only all consumer devices then?

  26. moparisthebest

    Phones, laptops, tablets

  27. lovetox

    scanning qr with laptop, is that really a thing?

  28. moparisthebest

    Yes

  29. mjk

    and with a Pi!