[Standards] XEP-0308: LMC of a previous correction

Ненахов Андрей andrew.nenakhov at redsolution.ru
Sat Nov 17 17:45:40 UTC 2018

I tend to think that title of this XEP is misleading and that any message
should be possible to correct.

Also, I'd rather use the original message ID, because the replaced message
should be stored on original message place in history (with a timestamp of
original message, though possibly amended with correction time). Using id
of last correction would require to fetch all subsequent messages from
archive to get to the original one and it's place in history. This is bad,
especially for clients that could have been offline for some time and would
have to do excessive work digging up message archive.

On Sat, 17 Nov 2018, 21:35 Georg Lukas <georg at op-co.de wrote:

> Hi,
> when correcting a previously corrected message, do you reference the
> original message @id or the message @id of the last correction to that
> message?
> The XEP proclaims:
> | A single message may be corrected multiple times by subsequent edits.
> which kind of leaves this question open, and from a quick survey, at
> least poezio, Conversations and yaxim will reference the last
> correction's message @id and not the original one.
> It would be great to clarify in the XEP business rules.
> Georg
> --
> || http://op-co.de ++  GCS d--(++) s: a C+++ UL+++ !P L+++ !E W+++ N  ++
> || gpg: 0x962FD2DE ||  o? K- w---() O M V? PS+ PE-- Y++ PGP+ t+ 5 R+  ||
> || Ge0rG: euIRCnet ||  X(+++) tv+ b+(++) DI+++ D- G e++++ h- r++ y?   ||
> ++ IRCnet OFTC OPN ||_________________________________________________||
> _______________________________________________
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: Standards-unsubscribe at xmpp.org
> _______________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20181117/e82df5ea/attachment.html>

More information about the Standards mailing list