@dtudury/streamo 0.2.1 → 1.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +1 -2
  2. package/ROADMAP.md +4 -20
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -204,8 +204,7 @@ node --test public/streamo/Repo.test.js # single file
204
204
 
205
205
  ## roadmap
206
206
 
207
- See [ROADMAP.md](./ROADMAP.md) for what's been built, what's next, and what we're
208
- aiming at for 1.0.
207
+ See [ROADMAP.md](./ROADMAP.md) for what's been built and what's next.
209
208
 
210
209
  ## collaboration
211
210
 
package/ROADMAP.md CHANGED
@@ -5,9 +5,9 @@ picture of where the project is and where it's headed.
5
5
 
6
6
  ---
7
7
 
8
- ## where we are (0.2.0)
8
+ ## where we are (1.0.0)
9
9
 
10
- The foundation is solid and working. Here's what's in:
10
+ The foundation is solid, tested, and shipped. Here's what's in:
11
11
 
12
12
  **Core data layer**
13
13
  - `Streamo` — reactive, content-addressed, append-only byte store with a
@@ -54,7 +54,8 @@ The foundation is solid and working. Here's what's in:
54
54
  stream. `public/apps/chat/server.js` is the standalone server — its public key
55
55
  is the room address, its member list is in its own repo, and it has no special
56
56
  authority over anyone's data. Runs in the browser and from the terminal
57
- (`chat-cli.js`).
57
+ (`chat-cli.js`). Message history persists across page reloads via server-side
58
+ archiving — rejoin with the same credentials and your history comes back.
58
59
  - Homepage at `public/index.html`.
59
60
  - `StreamoServer` — reusable class that wraps signer, registry, and all sync
60
61
  methods behind a clean API. `bin/streamo.js` is now a thin CLI parser on top
@@ -67,13 +68,6 @@ The foundation is solid and working. Here's what's in:
67
68
 
68
69
  ## what's next
69
70
 
70
- ### chat persistence ← start here
71
- The chat server (`public/apps/chat/server.js`) uses `StreamoServer` and wires
72
- `archiveSync` — so the member list survives restarts automatically. Individual
73
- message history lives in each participant's own repo; persistence there depends
74
- on participants running with `--data-dir` set. The remaining work is ensuring the
75
- browser chat client also persists across page reloads.
76
-
77
71
  ### presence indicators
78
72
  Who's currently online? The `interest` / `announce` layer is ephemeral by design,
79
73
  so presence is a heartbeat + timeout — announce yourself periodically, time out
@@ -86,16 +80,6 @@ real-world test of the UI layer.
86
80
 
87
81
  ---
88
82
 
89
- ## toward 1.0
90
-
91
- One thing blocking a stable `1.0` claim:
92
-
93
- 1. **Chat persistence** — a chat app that loses history on restart isn't production-ready
94
-
95
- Chat signing is done. Components, keyed list reconciliation, SVG namespaces,
96
- `class` arrays/objects, and the CLI server unification are all done.
97
- Persistence is the last mile.
98
-
99
83
  ---
100
84
 
101
85
  ## known limitations
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@dtudury/streamo",
3
- "version": "0.2.1",
3
+ "version": "1.0.1",
4
4
  "description": "peer-to-peer sync where your data and identity belong to you, not the server",
5
5
  "keywords": ["p2p", "peer-to-peer", "sync", "reactive", "content-addressed", "websocket", "signed", "append-only", "offline-first", "cryptographic", "identity"],
6
6
  "repository": "git@github.com:dtudury/streamo.git",