Live data from Hacker News

Google Maps Hacks

simonweckert.com

1–10 of 397 posts

Re: Google Maps Hacks

#5
Why can't the phones determine their proximity to each other and report it to Maps, which would then presumably figure out that they're too close to represent separate vehicles?

Re: Google Maps Hacks

#6
Wow, I never actually stopped to think about the way Google determines traffic but it seems so obvious now. This is a very simple but cool trick, I'd expect to see something like this in an action movie where people need to reroute an important car to a particular street.

Anyone have any idea how often this data is updated? So if the guy runs through a street with a cart and it turns red, when will it show up as clear?

Re: Google Maps Hacks

#8

Why can't the phones determine their proximity to each other and report it to Maps, which would then presumably figure out that they're too close to represent separate vehicles?

Just a guess: there's little economic incentive to perform this attack, and it would also be pretty expensive to perform regularly. So detecting and preventing it has not been a priority up to now. If people started doing it regularly, I'm sure countermeasures would be put in place.

Re: Google Maps Hacks

#9
I'm stunned how fast Google Maps detects traffic jams. I assume all those smartphones are running car navigation and as traffic detection works by trusting the clients I fear there's no chance to avoid this kind of exploit. Nevertheless it would be interesting to know what's the ratio of correct / malicious clients to fool the system. That migt highly depend on whether Google implemented any detection of faulty clients.
Post reply on HN