2 Commits

Include renames

Author	SHA1	Message	Date
dckcandClaude Opus 5.5	1e6436e089	capsite: social.coop tree at the ActivityPub level (fedi-cache) ... Mastodon is one implementation; the cache speaks the protocol: outbox for backfill, and fedi-cache as a follower actor so Update/Delete are delivered rather than polled for. Its own keypair replaces an access token, so webapp drops out of this one. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-07 11:16:05 -05:00
dckcandClaude Opus 5.5	99ce5b6964	capsite: goal trees for a zotero cache and a social.coop cache ... Both follow the diigo-cache pattern (webapp holds the credential, read-only and minted narrow at the source; the cache serves a public page). Zotero's versioned sync answers diigo's stale-head problem; Mastodon's doesn't announce edits/deletes, so its tree carries that as a design question. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-07 10:21:24 -05:00