matrix-org / matrix-org/matrix-spec
Message edits should clear reactions (emoji) to that message - replies should store the timestamp of the referred message
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
I couldn't find a similar issue so I'm opening a new one.
I only realized today that you can
1) send a message "I like flowers"
2) get lots of thumbs-up or otherwise reactions
3) edit your message to say "I hate flowers"
4) now you have fooled a lot of people into agreeing per emoji (or disagreeing, depending on how you edit-troll them) with a message they never reacted to.
Yes, it says "Edited" on the message, but it is never clear at what point in the edit process a reaction was sent.
Likewise with quotes that reference the message ID.
Expected / desired behavior:
Everytime a message is modified, the emoji reaction status gets re-set to "no reactions" - in this way, users can be sure that the reaction they see was issued towards the message they can read.
Bonus: Responses to a message should include the timestamp of the message to which the response was generated, and ideally display *that* version of the message, or at least allow the client to display some disclaimer "this message was edited since the response was generated - click here to see the version at the time of the response"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Matrix specification sections covering message edits, reactions, replies, and message identifiers. Define the normative behavior for clearing reactions and recording the referred message timestamp, including whether historical message versions are required. Done means the behavior is agreed and documented unambiguously in the specification.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100