Repository navigation
feat: node contact email + message any node (c0mpute dm send <node>, dm read, TUI inbox) (v0.3.74) - #374
Merged
Conversation
A node failing 3 in 4 inference jobs (sergey-234) could not be reached: no account, payout address, DM identity or email anywhere. Operators can now offer a contact, the way they already offer a nickname: - `c0mpute contact <email>` / `--clear` (~/.c0mpute/contact; C0MPUTE_CONTACT overrides it), published in the capability ad as hardware.contact - install.sh --contact <email>, and when run from a terminal it asks once (Enter skips; never in CI or --no-exec) - the status aggregator passes it per node after re-validating it to a plain address (sanitize_contact: no spaces, quotes, brackets, display names) - c0mpute.com/nodes shows it as a mailto link under the node's name Optional and public by the operator's choice; nothing is sent to it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…pute dm read` and the TUI Anthony: "what about c0mpute dm <node>" / "otherwise just have a dm read function" / "use hqtui". Reaching an operator needed their personal DM identity, which most never create (sergey-234 had none). - Every node gets its own secure-chat identity from a random seed in <config_dir>/node-dm.secret (mode 600, created on first worker start). The worker homes it on itself and publishes its key record every 6 h, so DMs to it land in its spool; it advertises the address as hardware.dm and the status aggregator passes it on (validated). Private nodes do not. - `c0mpute dm send <peer-id | 8-char node id> "..."` resolves the node on c0mpute.com/api/nodes (C0MPUTE_NODES_URL) to that address and sends a normal end-to-end encrypted DM. A node without one says so and shows its contact email when it lists one. - `c0mpute dm read [--json] [--limit N]`: the operator's inbox for the node, no keygen or password (shares the pull code with `dm pull`). - TUI Node tab: a messages row, `m` swaps the Roles panel for Messages, `r` refreshes, a toast on new ones. c0mpute.com/nodes shows the send line. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rst) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThreatCrush Security Scan14 finding(s) HIGH/CRITICAL: 2 | MEDIUM: 8 | LOW: 4
Snippets are redacted; ThreatCrush never prints matched credential material. |
Merged
ralyodio
added a commit
that referenced
this pull request
Nov 15, 2026
Ships #371 (inference: widened offers get bids, ETAs survive restarts, the jobs bridge benches failing workers) and #374 (node contact email, message any node with `c0mpute dm send <node>`, `dm read`, TUI inbox), merged after the v0.3.73 tag (#376). Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Anthony: "when they setup they should have an option to enter a contact email", "what about c0mpute dm ", "otherwise just have a dm read function", "use hqtui". Context: sergey-234's node fails 3 in 4 inference jobs and there was no way to reach its operator: no account, payout address, DM identity or email anywhere. This replaces #373 (the contact email) and adds node DMs on top.
Contact email (optional, public)
c0mpute contact <email>/--clear, stored in~/.c0mpute/contact(C0MPUTE_CONTACToverrides it).install.sh --contact <email>; when a person runs the installer at a terminal it asks once (Enter skips; never in CI or with--no-exec).hardware.contact. The aggregator re-validates it to a plain address and c0mpute.com/nodes shows it as a mailto link.Message any node
<config_dir>/node-dm.secret(32 random bytes, mode 600, created on first worker start). The worker homes it on itself and publishes its key record every 6 h, so DMs land in its spool. It advertiseshardware.dm, which the aggregator passes on (validated). Private nodes don't.c0mpute dm send <peer-id | 8-char node id> "…"resolves the node through c0mpute.com/api/nodes (C0MPUTE_NODES_URL) and sends a normal end-to-end encrypted DM. A node without an address says so and shows its contact email if it lists one.c0mpute dm read [--json] [--limit N]is the operator's inbox for the node: no keygen and no password. It sharespull_allwithdm pull.mswaps Roles for a Messages panel;rrefreshes; a toast when new messages arrive. The demo state shows it (screenshot checked). c0mpute.com/nodes shows the send line for nodes that have an address.Tests:
sanitize_contact(good and hostile inputs), the aggregator passing and dropping contact,node_chat_key(create once, mode 600, stable identity, read never creates),node_target(peer ids and node ids vs addresses, fingerprints and names). TUI: tsc clean, 61/61 tests. The version bump to 0.3.74 lands after #371 (0.3.73).🤖 Generated with Claude Code