-
lovetox
,hi
-
lovetox
i have the following case
-
lovetox
<message xmlns="jabber:client" to="MUC_ADDRESS@HERE" type="groupchat" id="testid"> <body>test</body> <replace xmlns="urn:xmpp:message-correct:0" id="testid" /> </message>
-
lovetox
how to react to such a message
-
lovetox
note replace id and message id is the same
-
lovetox
my first thought was, that i ignore the replace element simply and treat the message not as a replace
-
lovetox
or is there a valid case for such thing?
-
Zash
I'd say that you can only replace a previous message.
-
selurvedu
While replacing any message with a unique id is technically possible, and XEP-0308 even states "While it is possible to use this protocol to correct messages older than the most recent received from a full JID, such use is out of scope for this document and support for this SHOULD NOT be assumed without further negotiation", did this "further negotiation" ever happen?
-
lovetox
Zash but it could be a previous message
-
lovetox
nobody is forced to use unique ids
-
lovetox
yeah but obviously if people dont use unique ids lots of stuff will probably break
-
lovetox
so better ignore that
-
Zash
myeah
-
Zash
most recent message with the matching id (and sender) or somesuch
-
MattJ
selurvedu, in that sentence, "further negotiation" means between XMPP entities
-
Zash
presumably using some sort of protocol
-
selurvedu
MattJ, ah, I misunderstood. Does such protocol exist?
-
MattJ
Not that I'm aware of, no