> But in late March 2024, Apple quietly tweaked its privacy policy, allowing people to opt out of having the location of their wireless access points collected and shared by Apple — by appending “_nomap” to the end of the Wi-Fi access point’s name (SSID).
I find that incredibly irksome. I'm glad they provide an opt-out mechanism, but strongly dislike that it requires me to give my Wi-Fi network an ugly name. And what if 2 vendors have different opt-out strings such that I can't choose to stay out of, say, Apple and Google's DBs at the same time?
I feel you and agree, but there's a good argument to be made that BSSIDs are "public information".
It's a slippery slope to walk trying to regulate that one. One example: "No public citizen, you are not allowed to monitor our frequencies without paying our corporation a subscription fee."
I understand. I have a ham radio license and I can listen in to all sorts of things sent out into the public airwaves. That's what broadcasting is.
At the same time, I write a blog for other humans to read. I'm annoyed that some companies are likely scraping it to train their LLMs. Beyond my annoyance, I don't know how far I'd want to go toward making it possible for humans to consume it but not AIs. The legal cures for that seem like they'd be worse than the disease.
I am thinking of starting a competing product that uses wifi APs for geo location instead of GPS satellites. I want to be a more customer friendly business than google or apple though, it'll only be opt-in. All you have to do to indicate that you have opted-in is to append "_nomap" to your AP name. /s
If I understand correctly, the research was only possible because they were able to leverage the Google and apple APIs against each other. The lesson I get from this is these companies shouldn't behave like they exist in a vacuum and when exposing data or forcing global configuration (like the AP name) they need to be more careful.