scope: remove public share links #294

New issue

Closed

opened 2026-05-11 18:30:39 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-05-11 18:30:39 +00:00

Owner

Problem

Public share links no longer fit the reduced single-user scope.

Share links make sense for collaboration or multi-user/public workflows. With multi-user removed, they add token routes, acceptance flows, CLI commands, and security review surface without supporting the launch goal.

Solution

Remove event/task share API routes.
Remove /event/share/[token] acceptance route.
Remove share-link generation from the task panel and keymap/help text.
Remove CLI share command, completions, and manpage sections.
Leave old share-link schema cleanup to a later schema-compaction pass if needed.

Acceptance criteria

The app no longer creates public share URLs.
No UI or CLI command exposes sharing.
Existing task/calendar usage is unaffected.

## Problem Public share links no longer fit the reduced single-user scope. Share links make sense for collaboration or multi-user/public workflows. With multi-user removed, they add token routes, acceptance flows, CLI commands, and security review surface without supporting the launch goal. ## Solution - Remove event/task share API routes. - Remove `/event/share/[token]` acceptance route. - Remove share-link generation from the task panel and keymap/help text. - Remove CLI `share` command, completions, and manpage sections. - Leave old share-link schema cleanup to a later schema-compaction pass if needed. ## Acceptance criteria - The app no longer creates public share URLs. - No UI or CLI command exposes sharing. - Existing task/calendar usage is unaffected.

barrettruth added this to the v0.1.0 milestone

2026-05-11 18:30:39 +00:00

barrettruth added the

labels

2026-05-11 18:30:39 +00:00

barrettruth referenced this issue

2026-05-11 18:31:12 +00:00

v0.1.0 roadmap: single-user self-hosted launch #144