Hacker News Reader

That's a mistake, IMHO. You're pushing a LOT more data over the air by sharing an image versus a URL to a google map. Additionally, Google has partner adverts on those maps that they get revenue from, and if you get enough traffic viewing the maps, you can go to them and get a revshare.

When people start using it to broadcast events like accidents, fires, etc., you're going to want to use URLs, not pics.

View on HN

Problem with sharing URLs is that people would be able to zoom in and see exactly where the messages/echoes come from. Not all of our users would be comfortable with that.

You wouldn't want to share a location with every message, but rather give users the "choice" to share location for any given message they post.

If they've just seen an accident, they'll want to post a URL. If they're at home, not likely.

You might even ask users to "mark" private locations from which location can't be sent, like school, home, or work.

You could also allow the user to vary the accuracy of the position by zooming in/out, to give them control of proximity for their posted locations.

Reply on news.ycombinator.com