plotting MQTT links on map: not useful and degrading performance.

[recrof]

MQTT links especially on global map are doing more harm than good - there should be a way to disable or disallow them.

If there is no way to detect MQTT links, MeshSense should ignore links that are longer than ~300-600 km.

[Soltares]

Hi and thanks for report. The Global MeshSense map is currently under active development and we are trying to find the best solution to this problem. We believe we have filtered out MQTT routes already in f7631be. We have found cases, however, where Meshtastic nodes across the globe can have duplicate Node num as identifiers.

"num":115503498,"user":{"id":"!06e2718a","longName":"stevando","shortName":"stdo","macaddr":"6u6hrmY+","hwModel":"RAK4631"
"num":115503498,"user":{"id":"!06e2718a","longName":"AN/ALQ-3dc0","shortName":"3dc0","macaddr":"98NUVT3A","hwModel":"RAK4631"

This is a tricky problem to solve as trace routes only include a list of node nums. We will likely need to add additional logic to associate node with the MeshSense node that reported them. This adds complexity in the back-end as MeshSense uploaders in the same mesh would add duplicate records for the same node.

Adding the ability to disable rendering routes is a good idea. We also plan on hiding routes when zoomed out significantly, but have them shown currently while we work out the kinks.