dborupandClaude Sonnet 5 b3d7efb511 feat: ping-bot reply shows relay path, scope, and area ...

REST-loaded channel history (GetChannelMessages) now resolves the ping
message's relay path to node names ("via RepeaterA → RepeaterB"), bulk-
resolving every referenced pubkey across the page in one query rather
than per-message. Falls back to the raw pubkey when a hop's node isn't
known. Also includes the message's region scope and (via a handler-level
pass, since area resolution needs server config db.go doesn't have)
its resolved area.

The client-side pingBotReply (WebSocket live-push + PSK-channel decrypt
paths) gains scope/area too, since both are already present in that data.
Relay-path names are REST-only for now: the live WS broadcast doesn't
carry a resolved_path, only historical/REST-loaded messages do.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-07-23 14:39:13 +02:00

..

decrypt

feat: CLI tool to decrypt and export hashtag channel messages (#724)

2026-04-12 22:07:41 -07:00

ingestor

Revert "feat: persist ADVERT Feat1/Feat2 capability bytes per node"

2026-07-23 11:35:55 +02:00

migrate

refactor(db): finish #1283 — Option 4: ingestor owns neighbor-graph + schema migrations; server is read-only (fixes #1287) (#1289)

2026-05-19 23:53:41 -07:00

server

feat: ping-bot reply shows relay path, scope, and area

2026-07-23 14:39:13 +02:00