Hello folks,
I'm noticing that there is a lack of consistent results when using the tool in the left column "See what is on the local mesh".
Each node I can find returns different results. Not just the order of the nodes, but completely different content. Most nodes on the main status page report the same number of nodes and devices, but when using the "Search the mesh" box at the top of the /a/mesh screen I get wildly different results depending which node I am searching from. This is true both when trying to find nodes, and trying to find services.
Why are the results different from node to node? Do I need to restart Babel to re-create the list of what is available? Does Babel grab a list once and call it done? Looking for some clarity as it's really a problem to tell others to search for a service and nothing shows up even though the service is only a few hops away.
Ed
I'm noticing that there is a lack of consistent results when using the tool in the left column "See what is on the local mesh".
Each node I can find returns different results. Not just the order of the nodes, but completely different content. Most nodes on the main status page report the same number of nodes and devices, but when using the "Search the mesh" box at the top of the /a/mesh screen I get wildly different results depending which node I am searching from. This is true both when trying to find nodes, and trying to find services.
Why are the results different from node to node? Do I need to restart Babel to re-create the list of what is available? Does Babel grab a list once and call it done? Looking for some clarity as it's really a problem to tell others to search for a service and nothing shows up even though the service is only a few hops away.
Ed
I think because 'list of nodes' are ordered in increasing route quality value to other nodes.
Ergo, each node can display different results.
"Do I need to restart Babel to re-create the list of what is available? "
No.
"Does Babel grab a list once and call it done?"
No.
"it's really a problem to tell others to search for a service"
Then, simply share the URL of the resource and have them place the URL in their browser 'location' bat.
Then there will be no need for them to 'search'.
Example: Have folks place this URL in their browser 'location' bar:
http://k7eok-turretcam.local.mesh/
When I place that URL in my browser's 'location' bar, I see an Amcrest camera logn screen.
In the image, note the number to the right of the nodename.
That number will likely be different for each node.
73, Chuck
I think because 'list of nodes' are ordered in increasing route quality value to other nodes.
Ergo, each node can display different results.
True. But what you describe is a different order of listing the various nodes and services. What I'm describing is the total absence of many listings, no matter if close or far to the node. The total content of the list of nodes and services is different even though the main page says the same number of nodes, connected devices, and services.
"Do I need to restart Babel to re-create the list of what is available? "
No.
"Does Babel grab a list once and call it done?"
No.
Then, simply share the URL of the resource and have them place the URL in their browser 'location' bat.
Then there will be no need for them to 'search'.
True. But that sort of defeats the idea that someone can search for themselves in the search area, and in an emergency would slow things down as there would have to be a contact for every person who needs a service to tell them (perhaps again) where the service is.
Anyone else seeing the same inconsistency? Please take a look at your various nodes. Search for the same service from different nodes by character string and let me know if anyone else is seeing this ... I may have to go to Github and make a post there.
Ed