Parked by Frank on 2026-10-18: no action, this is the note-to-think-later. Nothing was built, nothing was deployed, scripts/signal-relay.py still runs as-is. #5 keeps the plan; this issue keeps the open choices so a future session can act in one pass.
What was settled (facts, so the next pass doesn't re-derive them)
A Telegram bot has no phone number: created by messaging @BotFather, authenticated by a token. The "where does the machine get a number" problem does not exist for a bot.
A Telegram user account still needs a number — the official no-SIM path registers against a blockchain anonymous number bought on Fragment (paid, and buying one takes an existing account): telegram.org/blog/ultimate-privacy-topics-2-0.
signal-cli 0.14.7 on Dankclaw: one registered account, +12062476336 (Frank's mobile, Messages have been last received 46 days ago), register is phone-number-only. Signal's numberless Signal Login is paid and Android-beta with no signal-cli path; Signal usernames hide a number, they don't replace registration.
Bot API reachable from Dankclaw unproxied: bogus token → http=401, total=0.470s (DNS + TLS + path proven, not auth).
A bot cannot initiate a chat: Frank must message it once before its chat_id is knowable.
The bot token is a bearer secret — mode 600 host file, EnvironmentFile, never argv/git/logs (same law a HF token broke on 2026-09-16).
Recorded cost of leaving Signal: Telegram is cloud-stored, not end-to-end like Signal. Alert payloads carry hostnames + service names only.
The three questions to decide later
Destination: DM, or a private group? DM is one less setup step; a group keeps machine traffic out of the human chat list and lets a peer or a future agent join one chat_id.
One bot for the whole fleet, or one per service? One bot + a service name in every message gives attribution with one token to rotate; per-service bots cost a registration each and buy per-chat mute control.
Do we even move, or fix the note-to-self inside Signal? Staying means a second registered signal-cli account (spare physical SIM is the robust door; a VoIP DID risks Signal's range rejections). Moving means a BotFather account Frank may not have at all — that fact alone decides between the two.
What is silently true until one of them is answered
Every alert Alertmanager fires today arrives as a silent note to self — LlmEndpointDown can be red for days with no notification. That is the cost of parking, written down so it is a choice and not an accident.
**Parked by Frank on 2026-10-18: no action, this is the note-to-think-later.** Nothing was built, nothing was deployed, `scripts/signal-relay.py` still runs as-is. #5 keeps the plan; this issue keeps the open choices so a future session can act in one pass.
## What was settled (facts, so the next pass doesn't re-derive them)
- A **Telegram bot has no phone number**: created by messaging `@BotFather`, authenticated by a token. The "where does the machine get a number" problem does not exist for a bot.
- A **Telegram user account still needs a number** — the official no-SIM path registers against a blockchain **anonymous number bought on Fragment** (paid, and buying one takes an existing account): [telegram.org/blog/ultimate-privacy-topics-2-0](https://telegram.org/blog/ultimate-privacy-topics-2-0).
- `signal-cli 0.14.7` on Dankclaw: one registered account, `+12062476336` (Frank's mobile, `Messages have been last received 46 days ago`), `register` is phone-number-only. Signal's numberless **Signal Login** is paid and Android-beta with no signal-cli path; Signal **usernames** hide a number, they don't replace registration.
- Bot API reachable from Dankclaw unproxied: bogus token → `http=401`, `total=0.470s` (DNS + TLS + path proven, not auth).
- A bot **cannot initiate** a chat: Frank must message it once before its `chat_id` is knowable.
- The bot token is a **bearer secret** — mode 600 host file, `EnvironmentFile`, never argv/git/logs (same law a HF token broke on 2026-09-16).
- Recorded cost of leaving Signal: Telegram is **cloud-stored**, not end-to-end like Signal. Alert payloads carry hostnames + service names only.
## The three questions to decide later
1. **Destination: DM, or a private group?** DM is one less setup step; a group keeps machine traffic out of the human chat list and lets a peer or a future agent join one `chat_id`.
2. **One bot for the whole fleet, or one per service?** One bot + a service name in every message gives attribution with one token to rotate; per-service bots cost a registration each and buy per-chat mute control.
3. **Do we even move, or fix the note-to-self inside Signal?** Staying means a second registered signal-cli account (spare physical SIM is the robust door; a VoIP DID risks Signal's range rejections). Moving means a BotFather account Frank may not have at all — that fact alone decides between the two.
## What is silently true until one of them is answered
Every alert Alertmanager fires today arrives as a **silent note to self** — `LlmEndpointDown` can be red for days with no notification. That is the cost of parking, written down so it is a choice and not an accident.
dank
added the human-only label 2026-10-18 16:01:29 -07:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Parked by Frank on 2026-10-18: no action, this is the note-to-think-later. Nothing was built, nothing was deployed,
scripts/signal-relay.pystill runs as-is. #5 keeps the plan; this issue keeps the open choices so a future session can act in one pass.What was settled (facts, so the next pass doesn't re-derive them)
@BotFather, authenticated by a token. The "where does the machine get a number" problem does not exist for a bot.signal-cli 0.14.7on Dankclaw: one registered account,+12062476336(Frank's mobile,Messages have been last received 46 days ago),registeris phone-number-only. Signal's numberless Signal Login is paid and Android-beta with no signal-cli path; Signal usernames hide a number, they don't replace registration.http=401,total=0.470s(DNS + TLS + path proven, not auth).chat_idis knowable.EnvironmentFile, never argv/git/logs (same law a HF token broke on 2026-09-16).The three questions to decide later
chat_id.What is silently true until one of them is answered
Every alert Alertmanager fires today arrives as a silent note to self —
LlmEndpointDowncan be red for days with no notification. That is the cost of parking, written down so it is a choice and not an accident.