- 已装运
- 2026年8月30日 02:44 UTC
- 作者
- Kamo
- 提交
- e86c161
The NATS payload for MEMBER_REMOVED carries who did the removing, but the NATS→STOMP relay projects every frame through ChatMessageDto — so a field this class does not declare never reaches a browser at all. Subscribers read it as empty, with nothing anywhere reporting a problem. The same trap already caught ATTACHMENT_REVOKED once, which is why that event carries its id twice.