On Sat, Oct 13, 2012 at 6:46 AM, Gunnar Hellström <[email protected]> wrote: > My conclusions are: > 1. The feature will be allowed. ( deduced from your answer that Kev is asked > do do an update ) > 2. How edits are presented to the receiving user is out of scope, but a > recommendation to make it clearly displayed that there was an edit will be > included. > 3. Edit any previous will be included. It is up to the transmitter to use it > or not. Receivers should be prepared to act on editing any previous.
I have updated 308 in Git. I believe I've addressed all feedback other than allowing editing of any previous - for this I've made a note that the protocol can be used as such, but that signalling is out of scope and so 308 without further negotiation is only for the last message. It's then easy to either add support to 308 later (I think better not), or to add signalling to another XEP that needs or wants it; the doors open, but we're not inviting anyone in just yet. I ended up wanting not to add it to 308 because this thread has made it clear that the security implications are nastier then, and I think there's value in clients being able to implement the simple version (indeed, I'm not sure I want to implement multi-message correction myself any more). /K
