Expose packet_hash to fanout bot kwargs #194

New Issue

2026-10-05T02:02:53+02:00

adam commented

2026-10-05 02:02:53 +02:00

(Thanks again for Remote Term! Claude helped me write this as I'm trying to implement a !packet command for blorkobot)

The fanout bot dispatcher already computes the canonical MeshCore packet hash for community MQTT uploads (app/fanout/community_mqtt.py:_calculate_packet_hash). It would be useful to pass that same hash into the bot kwargs so fanout plugins can use it without re-fetching raw packets and reimplementing the hash.

Proposed change

Move _calculate_packet_hash to a shared module (e.g. app/path_utils.py).
At the broadcast point that builds the data dict consumed by BotModule._run_for_message (app/fanout/bot.py), compute the hash from the raw packet bytes when available and add data["packet_hash"].
Add packet_hash: str | None = None to execute_bot_code and to the supported kwargs in _analyze_bot_signature so bots can declare it explicitly. Bots using **kwargs get it automatically; legacy bots are unaffected.

Use case

A !packet command that links to public MeshCore packet analyzers (analyzer.00id.net, analyzer.letsmesh.net) for the packet that delivered the command. Currently implemented as a workaround that re-fetches via /api/messages + /api/packets/{id} and reimplements _calculate_packet_hash inline — direct kwarg exposure would cut both the duplication and the extra HTTP round-trips.

(Thanks again for Remote Term! Claude helped me write this as I'm trying to implement a `!packet` command for [blorkobot](https://gist.github.com/statico-alt/a0b3e7b11ee66c4cc5ca97444924ea80)) The fanout bot dispatcher already computes the canonical MeshCore packet hash for community MQTT uploads (`app/fanout/community_mqtt.py:_calculate_packet_hash`). It would be useful to pass that same hash into the bot kwargs so fanout plugins can use it without re-fetching raw packets and reimplementing the hash. **Proposed change** - Move `_calculate_packet_hash` to a shared module (e.g. `app/path_utils.py`). - At the broadcast point that builds the `data` dict consumed by `BotModule._run_for_message` (`app/fanout/bot.py`), compute the hash from the raw packet bytes when available and add `data["packet_hash"]`. - Add `packet_hash: str | None = None` to `execute_bot_code` and to the supported kwargs in `_analyze_bot_signature` so bots can declare it explicitly. Bots using `**kwargs` get it automatically; legacy bots are unaffected. **Use case** A `!packet` command that links to public MeshCore packet analyzers (analyzer.00id.net, analyzer.letsmesh.net) for the packet that delivered the command. Currently implemented as a workaround that re-fetches via `/api/messages` + `/api/packets/{id}` and reimplements `_calculate_packet_hash` inline — direct kwarg exposure would cut both the duplication and the extra HTTP round-trips.

adam closed this issue

2026-10-05 02:02:53 +02:00

adam commented

2026-10-05 02:02:54 +02:00

Lemme know if that works for you!

Lemme know if that works for you!

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#194

Expose packet_hash to fanout bot kwargs #194

Expose `packet_hash` to fanout bot kwargs #194