When you remote to a repeater and pull the neighbors, it shows the location of the "RemoteTerm" node not the repeater.
The repeater location for this is the red dot but it shows it where I have the local node at.
When you remote to a repeater and pull the neighbors, it shows the location of the "RemoteTerm" node not the repeater.
The repeater location for this is the red dot but it shows it where I have the local node at.
<img width="1652" height="796" alt="Image" src="https://github.com/user-attachments/assets/728a3508-4ea3-46f1-9da7-41f3dd668c50" />
<!-- github-sync-id:4067268751 -->
Oh whoops, yeah we should be showing all that based off the repeater gps, not the RemoteTerm node. I'll patch that and figure out how to manage the sequencing with the fact that we would need to call the telemetry endpoint before calling the neighbor fetch if we want to show accurate distances or map.
Oh whoops, yeah we should be showing all that based off the repeater gps, not the RemoteTerm node. I'll patch that and figure out how to manage the sequencing with the fact that we would need to call the telemetry endpoint before calling the neighbor fetch if we want to show accurate distances or map.
<!-- github-comment-id:4050118157 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When you remote to a repeater and pull the neighbors, it shows the location of the "RemoteTerm" node not the repeater.
The repeater location for this is the red dot but it shows it where I have the local node at.
Oh whoops, yeah we should be showing all that based off the repeater gps, not the RemoteTerm node. I'll patch that and figure out how to manage the sequencing with the fact that we would need to call the telemetry endpoint before calling the neighbor fetch if we want to show accurate distances or map.
Perfect, thank you!