That may perhaps be the case, and I look forward to reading your thoughts on the matter, but I strongly believe this functionality should not have a history limit of 1. If one were to place a numeric limit on it, it should be more like 10, but that is also totally arbitrary.
In any case, a numeric limit of any value will not make sense in a busy MUC room where your last message might have disappeared into scrollback long ago. I believe Skype does something along the lines of only allowing editing messages within the current chat session (though wether that is a UI or protocol enforcement, who knows?). Perhaps that would be appropriate here. The question then is, who is responsible for enforcing that policy. At the moment, the spec requires no server support, and I think it should stay that way. Regards, Ben Langfeld On Tue, Nov 8, 2011 at 11:02 PM, Dave Cridland <[email protected]> wrote: > On Tue Nov 8 21:34:04 2011, Ben Langfeld wrote: >> >> Because it's more general. "Last" implies that it's not possible to >> modify prior messages, which is not explicitly prohibited by the >> specification, nor should it be. For that reason, "last" is not as >> clear as "previous", and is perhaps even confusing. > > I'm mildly terrified by the notion that *any* previous message can be > corrected. > > I'll try to articulate my phobia tomorrow; in general it just seems Wrong to > allow arbitrary message editing after sending, and I've a nasty feeling > there's some security impact there. > > Dave. > -- > Dave Cridland - mailto:[email protected] - xmpp:[email protected] > - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/ > - http://dave.cridland.net/ > Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade >
