-
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
-
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?
-
mjk
I also question the ABNF in saying iquerytype and ipair can be empty strings
-
mjk
oh wait, `*` means "one or more" probably
- mjk has to cure their regexitis
-
mjk
nope, not this time. `*` means `0*♾`: https://www.rfc-editor.org/rfc/rfc5234#section-3.6✎ -
mjk
nope, not this time. `*` means `0*∞`: https://www.rfc-editor.org/rfc/rfc5234#section-3.6 ✏
-
lovetox
`xmpp:foo@bar?omemo;sid=abcdef` would be more approriate i think
-
mjk
would need standardization and changing implementations. I'm looking for a way that would work right now :)
-
mjk
on the generation sied✎ -
mjk
on the generation side ✏
-
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
-
mjk
"parsing clients" set is likely == {Conversations}, so that simplifies the task :))
-
lovetox
are you suggesting only Conversations support omemo?
-
lovetox
or do you mean only smartphones need that uri?
-
lovetox
because there are a lot of clients who support omemo
-
Daniel
fwiw i think `xmpp:foo@bar?messgae;omemo-sid-123=abcdef` would not break Conversations
-
mjk
thanks Daniel
-
mjk
lovetox: I mean I'm not aware of any client that parses this kind of URIs✎ -
mjk
lovetox: I mean I'm not aware of any other client that parses this kind of URIs ✏
-
lovetox
i guess the original intent was to communicate it via QR code
-
mjk
yes, that's why I suspect there might be other mobile clients that support it
-
lovetox
so that would only make devices with camera and integrated QR code parser affected
-
mjk
in particular, iOS is a totally blind spot for me
-
moparisthebest
> so that would only make devices with camera and integrated QR code parser affected So only all consumer devices then? ↺
-
moparisthebest
Phones, laptops, tablets
-
lovetox
scanning qr with laptop, is that really a thing?
-
moparisthebest
Yes
-
mjk
and with a Pi!