Determine if we should start capturing ack paths from DMs for recent paths heard in addition to (instead of?) only ever using advert paths #42

Closed
opened 2026-10-05 01:54:43 +02:00 by adam · 1 comment
Owner

We keep a time-based collection of paths; bolting on a "this is super truthy" via ack path feels weird, but maybe we just comingle them? Shorter advert path would then win over longer ack path, but maybe just using shortest recently heard always is reasonable.

We keep a time-based collection of paths; bolting on a "this is super truthy" via ack path feels weird, but maybe we just comingle them? Shorter advert path would then win over longer ack path, but maybe just using shortest recently heard always is reasonable. <!-- github-sync-id:4090131440 -->
adam closed this issue 2026-10-05 01:54:43 +02:00
Author
Owner

Nah. Let's not get weird. Trust adverts, trust manual paths, don't extract paths from packets that aren't meant to be path information. They may not be wrong, but we'd be drifting from MC spec WAY more than we already are.

Nah. Let's not get weird. Trust adverts, trust manual paths, don't extract paths from packets that aren't meant to be path information. They may not be wrong, but we'd be drifting from MC spec WAY more than we already are. <!-- github-comment-id:4078695698 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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