notes

5.3 KB

1. # w051 — notes.worldapi.org#4: offline in pure Hybriel — STOPPED at Hybriel gaps
3. **Nothing moved.** notes-offline.js and sw.js stay, and no app file changed (only a new top entry in STATUS.md on Loreana).
4. I measured hl:web's offline realm (`offline = [...]`: generated worker, kept state, durable queue) on a minimal repro with
5. the vendored ff51cf46 in real Chrome. Two things notes needs are missing, so switching now would ship a half-offline notes,
6. which the mission forbids.
8. Repro: `loreana:/media/STORAGE/projects/notes.worldapi.org/.scratch/w051/repro/`. It has one page component at `/` and
9. `/p/:id`, a server-fed `count` that a push updates, and a queued `emit server`. Run it with `node run.mjs` (port 8762,
10. Chrome 8767-8769). Output:
11. ```
12. online /p/1 after 3 bumps: count = 3
13. offline /p/1 reload: count = 3 (kept for this URL)
14. offline / reload: count = 0 (server said 3 before the outage)
15. offline /p/7 (never visited): "Unavailable offline"
16. offline bump, then reload: queued = 1 count = 3
17. server back (fresh, count 0): count = 1 queued = 0 (the queued bump replayed)
18. link with on click { e.preventDefault() }: location = / handler ran: yes
19. ```
20. What works: the queue survives a reload and replays, `__hlQueue` can show offline edits again after a reload, and an inline
21. handler can claim a link.
23. ## Hybriel ticket texts
25. **H1 — hl:web offline: a kept page's state is stored per URL, so a page with several URLs shows stale data offline.**
26. `client.hl stateKey()` = `<component>|<pathname+search>`. `remember()` writes each push under the URL the tab is on at
27. that moment. Repro above: 3 pushes on `/p/1`, then go offline and load `/`: it shows 0, while `/p/1` shows 3. For notes, the
28. list (`notes = notesFor(session)`) is the same at `/` and every `/note/:id`. A user who edits at `/note/A` and then reloads
29. `/` offline sees an old list, and an edit to a stale note becomes a conflict copy.
30. Proposal: keep a need that does not read a route parameter per component, and one that does read it per URL. The graph
31. already knows what each need reads.
33. **H2 — hl:web offline: a param page of a kept component that was never loaded as a document is "Unavailable offline".**
34. `worker.hl navigation()` only answers from `caches.match(path)`. Repro: `/p/7` offline gives 503 "Unavailable offline",
35. although `Page` is kept. For notes: a note created offline (`/note/l…`), or a note opened in-app, cannot be reloaded
36. offline. Today's sw.js serves one kept shell for every `/note/*`.
37. Proposal: for a kept route with parameters, fall back to any kept document of the same route component, and boot it with
38. the URL's parameters and the kept state (H1).
40. **H3 — hl:web offline: kept state, kept documents and the queue belong to no user and cannot be forgotten.**
41. The IndexedDB `hl-offline` store (`state`, `queue`) has no user or session in its keys. The `hl-shell-*` cache keeps SSR
42. documents, and their seed carries the page state, which for notes is the notes themselves. The package exports only
43. `navigate` and `notify*`, so there is no way to drop any of this. Effects for notes:
44. - After a log-out, the notes stay readable in this browser. Today notes-offline.js deletes its copy at log-out, and the
45. gate checks that.
46. - A queue left by user A replays under whichever session opens the next socket.
48. Proposal: key the state and the queue by the session's user, drop that user's state, queue and documents at log-out, or
49. export `forgetOffline()` from hl:web.
51. ## App design for when H1–H3 land (worked out, not built)
52. - `components/notes.hl` (kept):
53. - Server-fed `notes = notesFor(session)`, with the full text of every note.
54. - `__hlQueue`, and `mine` (this tab's edits the server has not acknowledged yet).
55. - `rows` is derived on the client from notes, then `__hlQueue`, then `mine`. The helper functions must live in the
56. component file, because a braced import makes the derivation `srv` and it is never re-derived.
57. - The editor is a `for` over a one-row list keyed by a stable id (the local id if the note has one). It is rebuilt only
58. when a different note is selected.
59. - Statement-form faces `notesPut({owner,id,local,text,base,when})` and `notesDrop(...)` are queued offline. The push
60. `notesChanged(user, list, done)` has an audience of the same user. Use `when`, not `at`: `__hlQueue` rows overwrite `at`.
61. - Catch-up after a reconnect: a value-form `notesPull` (never queued). A null answer means offline, which drives the
62. status line. A CSS-animation tick runs the pull, as tickets/tracker already do.
63. - Server, `notes.hl`: queued saves from one device all carry the same old `base`, so the second one would conflict.
64. - Fix: store `by` (the session tag) and `from` (the base of the last accepted save). A save with the same `by` and `from`
65. is accepted as a continuation, not a conflict.
66. - A losing device's further saves update its existing copy (`copyOf`, `by`, `from`) instead of making a new copy each
67. time.
69. ## Gate
70. The existing gate on the unchanged app:
71. `NOTES_GATE_PORT=8760 NOTES_GATE_IDENT_PORT=8761 NOTES_GATE_CHROME=8767-8769 node tests/browser.mjs` → **50 passed, 0 failed**.
72. No new gate checks, because nothing was built. Afterwards nothing is left running on 8760–8769 (8765/8766 are the
73. creator's services and were already running).
75. ## Open
76. - notes#4 waits for H1–H3. Please file them in project hybriel; I did not post them.
77. - The repro stays in `.scratch/w051/repro/` for the hybriel worker.