[Standards] LAST CALL: XEP-0308 (Last Message Correction)

Kevin Smith kevin at kismith.co.uk
Fri Aug 10 12:35:48 UTC 2012

On Fri, Aug 10, 2012 at 1:31 PM, Kevin Smith <kevin at kismith.co.uk> wrote:
> On Fri, Aug 10, 2012 at 1:12 PM, Philipp Hancke
> <fippo at goodadvice.pages.de> wrote:
>>>> "Note well that for tracking purposes this service assigns a new 'id' to
>>>> each message it generates (here using a UUID as defined in RFC 4122)"
>>>> I bet some services do this... making the id at the recipient
>>>> unpredictable.
>>> Oh, and maybe I can replace your messages.
>> or rewrite the chat history after I left... even a same-fulljid requirement
>> doesn't help against that (is there one currently?)
> OK, so I need to add words about not allowing replacement between
> full-JID unavailables (to fix the MUC rejoin) and make sure it's
> explicit that it must be doing  correction only when full-JIDs match.

And also, as Fippo just pointed out to me, never do correction on MUC
join context.

I wonder if we should just not do it unless you have the real JIDs of
the occupants.


More information about the Standards mailing list