#1132 Last Message Correction support in MUC archives
What steps will reproduce the problem?
1. One user sends a message in a MUC.
2. They then correct it.
3. Another user joins the MUC.
What is the expected output?
The second user sees the corrected message.
What do you see instead?
What version of the product are you using? On what operating system?
Prosody trunk f1a46eef9df1, on ArchLinuxARM.
Please provide any additional information below.
Integration between LMC and MUC is undefined, but receiving two messages when one has been corrected is bad UX.
The MUC service should check that the user is the exact same (based on the bare JID, or if it’s easier based on whether they haven’t left the room), and not accept the correction otherwise.
One stretch goal, once LMC are tracked server-side, would be to also strip them out if the user isn’t correcting a known message, to prevent clients which failed to implement the security consideration from being phished.