Anonymous subscriptions to reports and requests #11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/bug-20-subscriptions"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of BUG-EP1, implements breadboard issue BUG-20 (anonymous subscriptions). Stacked on the BUG-19 branch.
POST /v1/reports/{receipt}/follow subscribes an install to the cluster behind a report (no account, receipt is the capability, follow token returned). DELETE /v1/follows/{token} unsubscribes. One follow per install per cluster, tokens stored hashed only, merges fold followers into the target, ungrouped reports get 409, banned installs get 403. Admin cluster page shows follower count.
Verified: cargo test (all suites green, 6 new tests in tests/follow.rs), cargo clippy with -D warnings clean, cargo fmt clean.
Closes BUG-20
Follow the cluster behind any grouped report with POST /v1/reports/{receipt}/follow (install header required, ban checked, network rate limited) and stop with DELETE /v1/follows/{token}. Follows are one per install per cluster, tokens stored hashed, and merge folds followers into the target. Ungrouped reports get 409 so clients can retry after triage. The admin cluster page shows the follower count.b2859bbc1f098e90cd1f