Federated view rev-2 alignment: group cards, browse header, save-a-copy, tab chip, open invites #464
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Cordy/Cairn#464
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Approved mockup:
federated-user-view-mockup-rev2.html(2026-09-10). Build scope:Inside-federation view (biggest gap): breadcrumb → title row (network glyph + server + product chip + reachability chip via /api/v1/ocm/check) → policy + contact subtitle → two group cards with header strips ("Shared with you" / "You shared"), per-row actions (Browse / Download / End share as quiet-danger link), empty groups show a quiet row, unreachable federations grey the inbound card under one amber line.
Remote browse: header card (icon + name + "lives on {server}" badge + reachability chip + right-aligned "Save a copy to Personal…" and "End share" buttons), breadcrumb line, rows with size + per-type actions.
Save a copy (new backend, TDD):
POST /api/v1/ocm/save/{id}{path} fetches one remote file through the share's grant and writes it into the user's Personal tree (collision → suffixed name), audited. v1 is single-file (browse rows + file-share header); folder-recursive save deferred to a follow-up.Requests refinements: relative timestamps (min/h, then date), Withdraw as quiet-danger link in the sub-line, ended-by-owner cards with danger accent + Dismiss (new
dismissdecide verb removing the ended ledger row, TDD).Tabs: pending count as a chip, not "(1)". Shares tab: federation name regular weight (mono reserved for paths/addresses). Contacts: generated key in the dashed keyblock; open-invites line (count + earliest expiry) from the existing GET /api/v1/ocm/invites.
Deferred (noted, not in this pass): remote-file Preview; folder-recursive save; invite revoke (needs API).
House rules: karpathy-guidelines, Superpowers TDD for the two backend pieces, house one-shots on a branch.
Shipped in v0.6.148 (PR #465, dismiss decision TDD red witnessed), live on both dogfoods. One simplification vs the issue text: no new save endpoint — the existing client-side save flow (fetch → files POST) already existed from #117 and is reused for the browse header button (file shares) and per-file rows. Deferred, tracked here for the beta: folder-recursive save-a-copy (needs a server-side walking job), remote-file Preview, per-row file sizes in browse (RemoteEntry carries no size; needs propstat parsing in ListRemote), invite revoke (needs API). Nikola verifies against
federated-user-view-mockup-rev2.html.