I’ve noticed some hubub over the role of GPS within Meshtastic; some requests to shut it off, a pinch of disdain for it, admiration by others, and elusions to the less efficient Disaster.Radio project. Simply put, GPS inside Meshtastic is a bit controversial.
Disclaimer: I am not poo-pooing on DR --It’s just not as blessed with as active a development cycle and I hope it finds its stride once again. It still looks like a very purposeful, valuable project, and I fully understand it’s apples/oranges. Maybe in another post we can discuss the differences, but for now let’s stick to GPS.
In this case, I’d like to learn more about the role of GPS in Meshtastic for myself and others; why it’s there, why it’s valuable, how it is utilised, and whether or not a fork that removes it would or wouldn’t make any sense (and the difficulty level of such a project to do so), how it could be perceived as a privacy concern (if at all), and to see if anyone wants to present constructive, logical reasons for or against it in the comments.
So, what’s the dill with GPS?
I recall from videos I viewed while researching Meshtastic before I bought into it that it was used in analytics and calibration, but can we put the subject to rest with a clear explanation for us noobs?
I’m all for asking “evergreen” questions that might be annoying up front for technical people who may feel obligated to answer them, but valuable in the long-term because when it comes up again, this post can be linked to, referenced, and save time on responses surrounding the subject in the future. I hope the makers of Meshtastic don’t hate me for asking.