Self-echo filter for notify webhook (skip own-node messages) (#22)

2026-09-25 08:51:03 +02:00
parent 3d0e369230
commit d3d1913b83
6 changed files with 88 additions and 3 deletions
@@ -1,5 +1,11 @@
 # Changelog

+## v0.11.2 — 2026-09-25 06:41
+
+- Self-echo filter in the notify webhook: `notifyRx` now skips the POST (with a single debug log line) when an explicit `from` equals our own node number (`myNodeNum`, set from FromRadio myInfo during initial sync) — our own sends must never trigger notifications of ourselves. Injections without `from` still notify; only an explicit `from` matching our node is filtered.
+- Tests: two new specs in the existing `MeshService notify webhook` block — rx text on the notify channel from our own node → no fetch; injected message with `from` = our own node → no fetch (own node number set via a myInfo frame, like the real initial sync). All 52 pre-existing specs stay green (54 total).
+- Docs: README env-var note + AGENTS.md webhook line ("messages from our own node are never notified").
+
 ## v0.11.1 — 2026-09-25 01:49

 - Injected messages now fire the outbound notify webhook too: `injectMessage` calls the same extracted private helper (`notifyRx(channel, text, from?)`) as the bridge RX path (which lost its inline block), with channel 0 — so a synthetic rx record triggers the webhook only when `MESH_NOTIFY_CHANNEL` is set to `0`; no forced semantics change, default stays `3`.