Draft
Conversation
…es and timestamp. This removes the sender's location from the mesh message while preserving TxTracker echo correlation. Coordinates remain in the API payload only.
Contributor
|
@fauxreigner-mb I do like this, give me a bit to review, I've been underwater. Appreciate you working on this! |
Contributor
|
@CSP-Tom This proposal removes coordinates from the channel message altogether and instead uses a unique hash. Lets chat about this :) |
Author
|
@MrAlders0n no worries, appreciate you taking the time to review. There are definitely "better" ways to generate the message hash, either in the |
Collaborator
|
changed to draft until a consensus is reached |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Pings broadcast
@[MapperBot] LAT, LONin a public channel. Power has already been moved to the API payload, but coordinates remained. This is privacy risk since anyone on the channel could read the sender's location in plaintext. Anonymous mode is meant to combat this but still broadcasts the information and must be enabled.Change
Replace the message text with a 6-char hex UID derived from a hash of the coordinates + timestamp, masked to 3 bytes. Coordinates stay in the API payload only. sendPing in connection.dart is simplified to accept the pre-built message string rather than lat/lon.
Why This Fixes It
TxTracker can still confirm an echo is ours via message content matching, but the message itself reveals nothing about the sender's location. ~16.7M options should be sufficiently unique in the listening window and keeps the message short.