Skip to content

feat(node): optional public contact email for questions about a node - #373

Closed
ralyodio wants to merge 1 commit into
masterfrom
feat/node-contact-email
Closed

ralyodio wants to merge 1 commit into
masterfrom
feat/node-contact-email

Conversation

@ralyodio

Copy link
Copy Markdown
Collaborator

Anthony: "when they setup they should have an option to enter a contact email for questions from users".

A node failing 3 in 4 inference jobs (sergey-234) couldn't be reached: there was no account, payout address, DM identity or email for it anywhere (checked c0mpute.com, the status aggregator and Infernet's providers and pubkey links).

  • Set it: c0mpute contact <email> / --clear (~/.c0mpute/contact; C0MPUTE_CONTACT overrides it). It's published in the capability ad as hardware.contact, the same path as the nickname.
  • At install: install.sh --contact <email>. When a person runs the installer at a terminal it asks once; Enter skips. It never asks in CI or with --no-exec, and it refuses addresses with spaces or odd characters instead of rewriting them.
  • Aggregator: passes contact per node after re-validating it (sanitize_contact: plain local@domain.tld, lowercased, no spaces, quotes, angle brackets or display names).
  • c0mpute.com/nodes: shows it as a mailto link under the node's name, plus a short "add a contact email" section.

It's optional, and public by the operator's choice; nothing is sent to it automatically. Tests cover sanitize_contact (good and hostile inputs) and the aggregator passing and dropping it. The version bump to 0.3.73 comes after #371 (0.3.72) merges.

🤖 Generated with Claude Code

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>
@github-actions

Copy link
Copy Markdown

ThreatCrush Security Scan

14 finding(s)

HIGH/CRITICAL: 2 | MEDIUM: 8 | LOW: 4

Severity Rule Location
HIGH js-ssrf-outbound-request apps/web/public/sw.js:24
HIGH sh-remote-script-execution scripts/install.sh:611
MEDIUM js-unescaped-html-sink apps/web/src/app/blog/[slug]/page.tsx:53
MEDIUM js-unescaped-html-sink apps/web/src/app/layout.tsx:109
MEDIUM sql-template-interpolation apps/web/src/lib/chat/convo-store.ts:116
MEDIUM sql-template-interpolation apps/web/src/lib/chat/convo-store.ts:117
MEDIUM sql-template-interpolation apps/web/src/lib/chat/push.ts:476
MEDIUM js-dynamic-code-execution apps/web/src/lib/router/verify.ts:91
MEDIUM sh-remote-script-execution scripts/dev-setup.sh:25
MEDIUM sh-eval-expansion scripts/dev-setup.sh:35
LOW py-ssrf-outbound-request examples/business-strategist-agent/chat.py:37
LOW py-ssrf-outbound-request examples/business-strategist-agent/train.py:54
LOW secret-generic-credential node/crates/c0mpute-core/src/webhook.rs:1171
LOW py-path-traversal node/crates/c0mpute-core/tests/fixtures/fake-infernet-text:29

Snippets are redacted; ThreatCrush never prints matched credential material.

@ralyodio

Copy link
Copy Markdown
Collaborator Author

Folded into the node DM PR (same branch history, plus c0mpute dm send <node> and dm read).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant