you eca0c9bd61 fix: use packet hash instead of sender_timestamp for channel message dedup ...

Device clocks on MeshCore nodes are wildly inaccurate (off by hours or
epoch-near values like 4). The channel messages endpoint was using
sender_timestamp as part of the deduplication key, which could cause
messages to fail deduplication or incorrectly collide.

Changed dedupe key from sender:timestamp to sender:hash, which is the
correct unique identifier for a transmission.

Also added TIMESTAMP-AUDIT.md documenting all device timestamp usage.

2026-03-21 21:53:38 +00:00

..

meshcore_cracker.min.js

fix: use packet hash instead of sender_timestamp for channel message dedup

2026-03-21 21:53:38 +00:00

meshcore_cracker.min.js.map

fix: use packet hash instead of sender_timestamp for channel message dedup

2026-03-21 21:53:38 +00:00

testbed.html

fix: use packet hash instead of sender_timestamp for channel message dedup

2026-03-21 21:53:38 +00:00