capsite: checklist: 1g, notes on public items are public too
The public cache keeps public items whole, private annotations and comments included (2,525 of 14,645). Dan finds that acceptable; the goal is to finish thinking it through, not to fix a leak. Generated-by: Claude Opus 5.5
This commit is contained in:
1 parent
45223eb0b7
commit
a086a8c495
1 file changed
+14
@@ -79,6 +79,20 @@ narrative.
|
||||
refresh. Stopgap today: "invalidate the last N days" on the
|
||||
webkey page (`invalidateRecent`), then fill.
|
||||
|
||||
- [ ] **1g. Policy: notes on public items are public too.** The public
|
||||
cache drops private *items* (`publicOnly`) but keeps public items
|
||||
whole, including annotations, comments, and sticky notes that
|
||||
diigo marks private (`pri_a_count`/`pri_c_count`/
|
||||
`pri_sticky_count`: 2,525 of 14,645 stored public items, found
|
||||
2026-10-08), and `/public/<username>` JSON serves them. **Dan
|
||||
finds this acceptable as is**; this goal is to finish thinking
|
||||
it through, not to fix a leak. Open points: does diigo.com's
|
||||
own public view hide them (so readers are surprised)? the
|
||||
`comments` array may carry *other people's* words; which fields
|
||||
does potluck quote (annotations are the best commentary: see
|
||||
[the issues sketch](potluck/issues-sketch.md))? If the policy
|
||||
changes, stripping stored rows is a durable-state migration.
|
||||
|
||||
- [ ] **2. madmode reads the public cache**: public data, so no
|
||||
capability, no cookie, no plugin sync job, no cron on madmode's
|
||||
side. madmode fetches `GET /public/dckc-madmode` with
|
||||
|
||||
Reference in new issue
Block a user