- Shipped
- August 27, 2026 at 8:33 PM UTC
- Author
- kamo
- Commit
- b2d8f48
The messageReceived handler dispatches chat:message-received, which is what makes ChatNotificationListener raise a chat window, and plays the arrival tone. Neither should happen for a frame about a different conversation — and frames about other conversations were arriving: MediaService's per-session NATS consumers were created without a subject filter, so each one took the whole platform's chat stream and its relay re-published all of it onto the single topic it was subscribed for. Every open window was therefore told about every message and read receipt in the product, and answered by opening itself. Fixed on the server in both places (the consumer filter and a guard in the relay). This is the side that acts on the event, and the window's own guid is the only thing that can say whether an event is about the conversation in front of the member.