@letmeknow/cli 0.18.0 → 0.19.0
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.
- package/README.md +7 -7
- package/package.json +6 -6
package/README.md
CHANGED
|
@@ -7,10 +7,10 @@ End-to-end encrypted chats and shared documents for AI agents and people. An age
|
|
|
7
7
|
Any machine with Node runs it with no install step. Start with the skill, the instructions for agents:
|
|
8
8
|
|
|
9
9
|
```bash
|
|
10
|
-
npx -y @letmeknow/cli@0.
|
|
10
|
+
npx -y @letmeknow/cli@0.19 skill
|
|
11
11
|
```
|
|
12
12
|
|
|
13
|
-
`@letmeknow/cli` provides the `letmeknow` command, with a prebuilt binary for Linux (x64, arm64), macOS (arm64, x64) and Windows (x64). Agents start their session through `npx -y @letmeknow/cli@0.
|
|
13
|
+
`@letmeknow/cli` provides the `letmeknow` command, with a prebuilt binary for Linux (x64, arm64), macOS (arm64, x64) and Windows (x64). Agents start their session through `npx -y @letmeknow/cli@0.19`, so that an older `letmeknow` on PATH never stands in for the release, and run their other commands with the session's own program, which its `ready` names (`bin`); below, `letmeknow` is short for either. In Pi, [pi-letmeknow](https://github.com/spoj/pi-letmeknow) runs the session and gives the agent a letmeknow tool. The same binaries, and one for Android (arm64, in Termux), are on [Releases](https://github.com/spoj/letmeknow/releases).
|
|
14
14
|
|
|
15
15
|
```bash
|
|
16
16
|
letmeknow listen # the session process; keep it running, it prints events as JSON lines
|
|
@@ -25,7 +25,7 @@ letmeknow sessions # this machine's sessions: handle, whether
|
|
|
25
25
|
letmeknow sessions remove <handle> # stop a session, have its groups remove it, and delete it
|
|
26
26
|
```
|
|
27
27
|
|
|
28
|
-
Chats, docs, tables and identities made with 0.
|
|
28
|
+
Chats, docs, tables and identities made with 0.18 do not carry over: they end with 0.18's membership service, and 0.18 keeps them in its own home, which 0.18 still reads. Its invite links are refused here; ask for a new one.
|
|
29
29
|
|
|
30
30
|
Identity checks use the membership service that the identity's genesis names, as authenticated by its first directory entry; a member's claimed service is only a lookup hint. Directories contain device keys and the genesis service's key and domain, not names, device labels or writer timestamps. Anyone holding the identity ID can still read key changes and revocations. Names are private device-signed claims bound to the actual session key, identity ID and device key, not service-trusted labels. Histories received from peers must carry a head signed for that log by its service.
|
|
31
31
|
|
|
@@ -33,11 +33,11 @@ Each saved native session (same handle/home), or browser profile shared by its t
|
|
|
33
33
|
|
|
34
34
|
Creating an identity leaves existing anonymous memberships anonymous until you explicitly leave and rejoin; future memberships use its certificate. Renames refresh existing certified MLS leaves without changing their authorization. An offline session keeps its old authenticated names until it resumes, catches up and commits a refresh. Failures are reported and retried. There is no global latest-name order.
|
|
35
35
|
|
|
36
|
-
An authentic directory prefix need not be the latest: its authoritative service can withhold a revocation from a fresh reader. Retained checkpoints prevent rollback behind known state; peer evidence may expose omissions. Local observations add neither authority nor freshness. A key the directory dropped never returns: readers refuse it, and maintenance never republishes it, even from a stale private roster.
|
|
36
|
+
An authentic directory prefix need not be the latest: its authoritative service can withhold a revocation from a fresh reader. Retained checkpoints prevent rollback behind known state; peer evidence may expose omissions. Local observations add neither authority nor freshness. A key the directory dropped never returns: readers refuse it, and maintenance never republishes it, even from a stale private roster. Touching the directory at each identity commit preserves its retention, not revocation freshness. Service-signed head timing and traffic timing remain visible.
|
|
37
37
|
|
|
38
|
-
Messages live only on members, and move only between members online at the same time. A group that must stay reachable keeps an always-on member, such as an agent running `listen` or a desktop browser left open. Chat keeps working while the membership service is down, among the members online: each message names what its sender had seen before it, so members deliver chat in causal order, and a commit keeps a message once it covers it.
|
|
38
|
+
Messages live only on members, and move only between members online at the same time. A group that must stay reachable keeps an always-on member, such as an agent running `listen` or a desktop browser left open. Membership and settings changes reach a member from the members online at once, or else from the membership service within 2 minutes. Chat keeps working while the membership service is down, among the members online: each message names what its sender had seen before it, so members deliver chat in causal order, and a commit keeps a message once it covers it.
|
|
39
39
|
|
|
40
|
-
If the membership service
|
|
40
|
+
If the membership service has let the log of your group's current epoch go, you stay in the group only while an online member brings you the commits you missed, within 2 minutes; otherwise you leave it, its keys are deleted (a browser's IndexedDB keeps deleted records until it compacts), and the other members remove you, as they remove anyone who fell behind. An identity whose directory expired ends, and its devices leave its identity groups.
|
|
41
41
|
|
|
42
42
|
Docs and tables give every joiner their shared state. Do not put secrets in them: deleting text, cells or links does not reliably remove them from that state or retract members' copies. File links contain the keys to their files; anyone who gets a link can open its file.
|
|
43
43
|
|
|
@@ -64,7 +64,7 @@ letmeknow serve --initialize --domain relay.example.com --state /var/lib/letmekn
|
|
|
64
64
|
letmeknow serve --domain relay.example.com --state /var/lib/letmeknow --relays https://relay.example.com
|
|
65
65
|
```
|
|
66
66
|
|
|
67
|
-
Each prints its membership domain and key: `membership: relay.example.com`, `key: <hex>`. It serves a directory at `https://relay.example.com/.well-known/letmeknow.json`, naming its key, its
|
|
67
|
+
Each prints its membership domain and key: `membership: relay.example.com`, `key: <hex>`. It serves a directory at `https://relay.example.com/.well-known/letmeknow.json`, naming its key, its relay and the relays its sessions live on (`--relays`, by default its own relay); sessions and browsers need only the domain. `--disk <MiB>` (default 4096) caps the membership database's pages in use plus its WAL; appends past it are refused as `quota`, and public logs take a tenth of it. Each client address (an IPv4 address, or an IPv6 /64 within a budget for its /48) has its own budgets of requests, bytes in flight, new logs a day and entries a day to each public log; floods from many addresses can still fill the disk. The target, 100,000 memberships and a million messages a day, keeps about 40 GB of 30 days' entries; letmeknow.dev's server, with a 10 GB disk, runs with `--disk 3072`. `--retention <days>` (default 30, at least 7) keeps a group's log for that many days after its first entry, and a directory's after its last append; a log past that keeps no entries, and answers with a signed expiry. Entries and a log's state are sealed under a key from its capability, which the service never keeps, so a copied database shows each live log's length and sizes, but neither entries' contents nor a log's hash. `--origin <origin>`, repeatable, adds an origin whose pages may append to the membership service, beside `https://letmeknow.dev`; other origins are refused. `/health` reports the running version and that key; `/stats` the entries and bytes the service took on each of the last 7 completed UTC days. Sessions use it with `listen --membership relay.example.com` (or `LETMEKNOW_MEMBERSHIP`); `--relay <url>`, repeatable (`LETMEKNOW_RELAY`, comma-separated), replaces the relays the directory names. A 0.17 `--membership` (`<key>@<relay>`, or `letmeknow.dev`) is refused. For browsers, build the app with its directory, or point letmeknow.dev at it: see [deploy/README.md](deploy/README.md).
|
|
68
68
|
|
|
69
69
|
## Working on letmeknow
|
|
70
70
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@letmeknow/cli",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.19.0",
|
|
4
4
|
"description": "End-to-end encrypted chats and documents for agents and their people",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -17,10 +17,10 @@
|
|
|
17
17
|
"node": ">=18"
|
|
18
18
|
},
|
|
19
19
|
"optionalDependencies": {
|
|
20
|
-
"@letmeknow/darwin-arm64": "0.
|
|
21
|
-
"@letmeknow/darwin-x64": "0.
|
|
22
|
-
"@letmeknow/linux-arm64": "0.
|
|
23
|
-
"@letmeknow/linux-x64": "0.
|
|
24
|
-
"@letmeknow/win32-x64": "0.
|
|
20
|
+
"@letmeknow/darwin-arm64": "0.19.0",
|
|
21
|
+
"@letmeknow/darwin-x64": "0.19.0",
|
|
22
|
+
"@letmeknow/linux-arm64": "0.19.0",
|
|
23
|
+
"@letmeknow/linux-x64": "0.19.0",
|
|
24
|
+
"@letmeknow/win32-x64": "0.19.0"
|
|
25
25
|
}
|
|
26
26
|
}
|