{"version":"2.1.274","anchor":"projectartifact-comment-sync-reworked-to-hash-message-text","canonical_anchor":"projectartifact-comment-sync-reworked-to-hash-message-text","heading":"Edited comments and messages are now detected instead of being treated as already-seen","tier":"internal","area":"Projects","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/projectartifact-comment-sync-reworked-to-hash-message-text","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Edited comments and messages are now detected instead of being treated as already-seen\n\nProject-thread and artifact comment dedup logic now hashes message text so edited or resent content is no longer skipped as already-processed\n\n**What**\n\n- The dedup logic that decides whether a project-thread message notification needs re-processing ('judged' messages) now hashes the message text and stores it alongside the existing id and timestamp used as the dedup key.\n\n- The same text-hashing approach was applied to 'other comments' shared state, and to artifact autoreact logic, using matching helper functions.\n\n- A new `textsForgotten` flag and a `lastText` map track when a comment's or message's content has changed since it was last judged or reacted to.\n\n**Why**\n\nPreviously, dedup was based only on a message's id and timestamp, so if a message or comment was edited but kept the same id and timestamp, it was wrongly treated as already-seen and skipped. Hashing the actual text means edited or resent content is now correctly detected and re-processed.\n\n- Area: Projects\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}