mirror of
https://github.com/block/buzz.git
synced 2026-11-14 05:12:27 +00:00
The relay accepted forum posts/comments (45001/45003) as channel-scoped writes but only routed kinds 9/40002 through the atomic DM insert/resurface path. Both clients classify all four as human-visible channel messages, so a custom or stale client could post a forum event into a hidden DM: the event rendered but the recipient's hidden_at stayed set and their clients stayed unsubscribed — the original bug through another supported kind. Centralize the resurface trigger on a shared is_human_visible_message_kind predicate (kinds 9/40002/45001/45003, matching the clients' CHANNEL_MESSAGE_EVENT_KINDS) and parameterize the live regression over all four kinds so dropping either forum kind fails the test. Signed-off-by: kenny lopez <klopez4212@gmail.com> Co-authored-by: Mongo <9cfd347903944d5b85aa6c93d2ab67381b978a92a31914bca69998968752a1d7@buzz.block.builderlab.xyz>