On Sat, 2023-02-25 at 10:50 +0100, Florian Schmaus wrote: > However, it is still unclear to me how changing the RFC 'id' > attribute > specification from "must be unique within the scope of the stream id" > to > "must be globally unique, for example by using UUID" solves much we > discussed in this thread. > > It would just solve the "how to reference a stanza in a 1:1 chat" > problem. But with a questionable backwards interoperability story. > Therefore -- but please consider that I am biased here -- origin-id > feels like the better solution.
Can you explain why you think that origin-id serves *any* purpose other than providing an id that should be globally unique, which would already be covered if it was a requirement in the RFC? Many clients that send an origin-id already put the very same value in it that they also put in the id-attribute. And I even hear voices that this should be mandated in XEP-0359. Also it is my feeling that origin-id is very much questioned as a concept, its only use today seems to be to detect/associate reflections in MUCs that don't do #stable-id and some of those also don't reflect the origin-id, making it even not always suitable for that purpose. Marvin _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
