Cordy/Cairn

Fork 0

Remove nav notification dots; federated/peering deliveries notify via the bell #460

New issue

Closed

opened 2026-09-09 22:03:49 +00:00 by Cordy · 1 comment

Cordy commented

2026-09-09 22:03:49 +00:00

Owner

Decision (Nikola, 2026-09-10, on seeing the green dot on "Federated" after the first live OCM share): no notification dots on nav items. Notifications live in the notification bell — receiving a file via OCM or Cairn Peering must produce a bell notification for the recipient, like every other event class.

Scope

Remove:

The Federated nav dot (fed-dot, fedUpdateDot machinery) — supersedes the dot that appeared in the approved mockup; design revised.
The Peering inbox dot (v0.4.3) — same reasoning, same pass.
In-view context indicators stay: the Requests tab count ("Requests (1)") is orientation inside the view, not a notification, and remains.

Add (backend, TDD):

Bell notification on inbound OCM share reaching pending state: "{sender} shared {name} with you from {server}" → links to Federated → Requests.
Bell notification on Peering inbox delivery: "{peer} sent you {name}" → links to the Inbox.
Wire through the existing notifications system (same pattern as the licence bell items, #437). Notifications created server-side at delivery time, so they appear regardless of which client polls.

i18n ×4 for both notification strings.

House rules: karpathy-guidelines (surgical — no redesign of the bell), Superpowers TDD (red on runner for the two backend notification events), house one-shot on a branch.

Decision (Nikola, 2026-09-10, on seeing the green dot on "Federated" after the first live OCM share): **no notification dots on nav items**. Notifications live in the notification bell — receiving a file via OCM or Cairn Peering must produce a bell notification for the recipient, like every other event class. ## Scope **Remove:** - The Federated nav dot (`fed-dot`, `fedUpdateDot` machinery) — supersedes the dot that appeared in the approved mockup; design revised. - The Peering inbox dot (v0.4.3) — same reasoning, same pass. - In-view context indicators stay: the Requests tab count ("Requests (1)") is orientation inside the view, not a notification, and remains. **Add (backend, TDD):** - Bell notification on inbound OCM share reaching pending state: "{sender} shared {name} with you from {server}" → links to Federated → Requests. - Bell notification on Peering inbox delivery: "{peer} sent you {name}" → links to the Inbox. - Wire through the existing notifications system (same pattern as the licence bell items, #437). Notifications created server-side at delivery time, so they appear regardless of which client polls. **i18n ×4** for both notification strings. House rules: karpathy-guidelines (surgical — no redesign of the bell), Superpowers TDD (red on runner for the two backend notification events), house one-shot on a branch.

Cordy added this to the v0.7 — Closed beta (dogfood + hardening) milestone

2026-09-09 22:04:27 +00:00

Cordy referenced this issue from a commit

2026-09-09 22:21:31 +00:00

one-shot: Federated view mockup alignment + bell notifications (#459 #460)

forgejo-actions referenced this issue from a commit

2026-09-09 22:26:28 +00:00

web+api: Federated view per mockup, bell notifications replace the nav dot (#459, #460)

Cordy referenced this issue

2026-09-09 22:28:24 +00:00

web+api: Federated view per mockup, bell notifications replace the nav dot (#459, #460) #461

Cordy referenced this issue from a commit

2026-09-09 22:30:28 +00:00

Merge pull request 'web+api: Federated view per mockup, bell notifications replace the nav dot (#459, #460)' (#461) from fix-459-460 into main

Cordy commented

2026-09-09 22:36:46 +00:00

Author

Owner

Shipped in v0.6.146 (PR #461, TDD red witnessed), live on both dogfoods. fed-dot removed (the old peering inbox dot had already been absorbed by the bell as kind received — nothing else to remove). New derived bell kind ocm-share from the pending ShareIn ledger: appears while a decision is pending, leaves the bell once decided, clicks through to Federated → Requests. Peering items now read "Sent by Cairn peer {p} — in your Inbox" (×4 locales) and click through to the Inbox. Requests tab count kept as in-view orientation.

Shipped in v0.6.146 (PR #461, TDD red witnessed), live on both dogfoods. fed-dot removed (the old peering inbox dot had already been absorbed by the bell as kind `received` — nothing else to remove). New derived bell kind `ocm-share` from the pending ShareIn ledger: appears while a decision is pending, leaves the bell once decided, clicks through to Federated → Requests. Peering items now read "Sent by Cairn peer {p} — in your Inbox" (×4 locales) and click through to the Inbox. Requests tab count kept as in-view orientation.

Cordy closed this issue

2026-09-09 22:37:14 +00:00

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#460

No description provided.

Rows
Columns