Feat/notifications: In-app notification system with placed inboxes#307
Open
St4NNi wants to merge 16 commits into
Open
Feat/notifications: In-app notification system with placed inboxes#307St4NNi wants to merge 16 commits into
St4NNi wants to merge 16 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the backend of the in-app notification system as one shared primitive: mutating operations emit ephemeral post-commit events, routing mints recipient-addressed records, and a durable per-origin FIFO outbox delivers them to a deterministic per-user inbox holder over a dedicated ALPN. Any node serves the REST API by proxying one hop to the holder, so the portal stays topology-blind.
Stacked on #306 (feat/public-access); diff shows only the notification commits.
Changes
GET /api/v1/notificationswith cursor pagination,GET /api/v1/notifications/unread, andPOST /api/v1/notifications/read, each served from any node via holder proxy.docs/design/notifications.md.GitHub Issues