On Tue, 29 Sep 2020 at 11:05, Marvin W <[email protected]> wrote: > I'd like to propose a feature that announces that > a) origin-id, if present, matches the message id field of the original > message > b) message id of the original message (and thereby origin-id if present) > is a random UUID v4 > - If this feature is announced and the sending user's server sees a > message id from that client that is known to have been used before, the > message should cause an error. > - If this feature is announced and any server sees an origin-id from > that client that is known to have been used before, the message should > cause an error. > Motivation of this feature is mostly to get client to do things the > right way. Announcing this feature could also become a dependency for > things like message correction where we want to have a proper way to > reference a message. > > Agreed, with a few minor changes:
* UUIDv4 becomes an "advised to use"; the requirement is uniqueness. I think UUIDv4 is a good thing, and people are unlikely to get anything wrong if they use this method, but I don't think there's any interoperability issue with using something different. * Unconvinced we want to (or even can) rely on global uniqueness from foreign entities; so I'm keen on the first bullet-point in (b) but less sold on the second - having servers allocate a MAM id for inbound foreign messages seems uncomplicated and safer. But overall these are minor quibbles; fundamentally I think this could address all our problems here without creating additional traffic.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
