#map
18 messages · Page 1 of 1 (latest)
😬
Are you having any problems?
i sincerely hope you dont siphon that data off the public mqtt server.
Im more concerned its exactly the same as the public one thays used but .eu instead. Very confusing for useers
that too
the retention selection gives my headache too.
Can only asume its from the public mqtt as 90% of them say "official-eu"
Lets see - shows EU, hosted on a cloud provider in the US, no indication who this is and how they are processing Personal data. And apparently abuses public project infrastructure.
Theres also tails data too.
Its also called meshtastic map
This map has trouble and issues all over it.
sorry guys, i will make changes to that, im closing it for now, until i have made some changes, yes it collects data from the official mqtt server, but also a local mqtt server, it was my first project so thx for the feedback i will do some changes:)
map
nothing to say against the project. if you limit the amount and kind of data processed and especially the retention period. For reference: maps are a bit of a touchy subject from past experience. The public MQTT server is not meant for consuming this kind of data. Running this off a private server is ok, as long as you respect the 'dont mqtt' flag in packets.
Ok, i have taken it down for now, you guys pointed out some good things I need to change, the reason I have the trails was because of the hex system, I was thinking like the hexagons can show some sort of coverage, I was migrating to my Eu vps but didn’t come that far before i closed it, that’s why it has the .eu, this was more or less just to get some feedback, thanks again for pointing some stuff out:)