dborupandClaude Sonnet 5 3b5bc17180 feat: ping-bot reply reports full reach (deepest hop + breadth), not just first observation ...

GetChannelMessages previously used "first observation wins" for a ping's
botReply -- if the same flood was heard by multiple stations, only
whichever one happened to be scanned first shaped the hop count, SNR, and
relay path. That understates reach: different stations legitimately hear
the same flood at different hop depths depending on which relay leg
reached them.

Now tracks, across every observation of the ping: the DEEPEST (max-hop)
observation's hops/SNR/relay path, and every DISTINCT station that heard
it. The reply shows the deepest leg's path and reports "heard by N
stations" once more than one did (falling back to the single station's
name when there's exactly one, same as before).

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

2026-07-23 15:09:19 +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 reports full reach (deepest hop + breadth), not just first observation

2026-07-23 15:09:19 +02:00