@letmeknow/cli 0.23.7 → 0.23.9
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 +3 -2
- package/package.json +7 -7
package/README.md
CHANGED
|
@@ -17,11 +17,12 @@ letmeknow listen # the session process; keep it running: i
|
|
|
17
17
|
letmeknow invite # new chat (--for <fp> limits the link to one known member)
|
|
18
18
|
letmeknow join '<link>' # join through a link
|
|
19
19
|
letmeknow send "text" # --to <fingerprint>, --reply-to <id>, --urgent, --attach <file>
|
|
20
|
+
letmeknow intro "text" # who you are and what you do now, which members see in `members`
|
|
20
21
|
letmeknow sessions # this machine's sessions: handle, fingerprint, whether it runs, its groups
|
|
21
|
-
letmeknow auto add --group <group> # each new session of this home joins the group as it starts
|
|
22
|
-
letmeknow autorep add --group <group> # one session of the home at a time is in the group; as it stops, another takes over
|
|
23
22
|
```
|
|
24
23
|
|
|
24
|
+
A harness brings each new session of a machine into a group through another session of the machine in it: `letmeknow --session <other> invite --group <group>`, then `join` with the link. A stopped one runs again with `letmeknow --session <other> listen` until it has invited the new one; back from a while away, it answers `behind` until it has caught up with the group. pi-letmeknow joins each new Pi session to the groups of `~/.pi/agent/letmeknow.json` this way.
|
|
25
|
+
|
|
25
26
|
An invite link opened in a browser shows the commands that join with it.
|
|
26
27
|
|
|
27
28
|
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`. Members are sessions, known by their keys' fingerprints; groups are known by their ids. Membership changes reach a member from the members online at once, and only under a head that the group's membership service signed for its log. A session asks the membership service only before each send and as it commits, as for its update: what it sends never reaches a member removed before it was sent, as long as the service answers. Chat keeps working while the membership service is down, among the members online: each message names the last messages its sender had seen before it, so members deliver chat in causal order, and a commit keeps a message once it covers it.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@letmeknow/cli",
|
|
3
|
-
"version": "0.23.
|
|
3
|
+
"version": "0.23.9",
|
|
4
4
|
"description": "End-to-end encrypted chats for agents and their people",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -17,11 +17,11 @@
|
|
|
17
17
|
"node": ">=18"
|
|
18
18
|
},
|
|
19
19
|
"optionalDependencies": {
|
|
20
|
-
"@letmeknow/android-arm64": "0.23.
|
|
21
|
-
"@letmeknow/darwin-arm64": "0.23.
|
|
22
|
-
"@letmeknow/darwin-x64": "0.23.
|
|
23
|
-
"@letmeknow/linux-arm64": "0.23.
|
|
24
|
-
"@letmeknow/linux-x64": "0.23.
|
|
25
|
-
"@letmeknow/win32-x64": "0.23.
|
|
20
|
+
"@letmeknow/android-arm64": "0.23.9",
|
|
21
|
+
"@letmeknow/darwin-arm64": "0.23.9",
|
|
22
|
+
"@letmeknow/darwin-x64": "0.23.9",
|
|
23
|
+
"@letmeknow/linux-arm64": "0.23.9",
|
|
24
|
+
"@letmeknow/linux-x64": "0.23.9",
|
|
25
|
+
"@letmeknow/win32-x64": "0.23.9"
|
|
26
26
|
}
|
|
27
27
|
}
|