[NathanKP]

This site's usage of browser is ridiculous. Every time you move forward or backwards it adds another history entry, making your back button pretty much useless.

If they want to provide deep linking to a particular map location they should change the URL without writing to the history.

[udev]

First world issues much?

You've been presented with these rare images, that someone probably had to smuggle out of the country, took care to lay them on the map for your convenience, and you sit there dissatisfied with how the back button works.

[coderdude]

Complaining about the presentation of the linked content is sort of a meme here.

Just for fun: https://hn.algolia.com/?query=%22my%20eyes%20hurt%22&sort=by...

[yellowapple]

And for good reason. If you give something to a bunch of programmers, any programming deficiencies will be immediately and more-than-adequately addressed.

[hitekker]

If snarkiness tends to be this predictable, I wonder what kinds of data analysis can be done just using certain recurring phrases.

[vladharbuz]

Giving technical feedback doesn't mean one doesn't appreciate the content.

[nhunzaker]

Seems like they're using window.history.replaceState, which replaces the current history state. This is in contrast to window.history.pushState which adds to the stack.

I can't help but be curious if it's falling back to #hashurls for you (or something else). From my end, they've come up with a clever technique for persisting map state in a sharable way.

[bdcravens]

Not seeing that issue in Chrome/OSX.

[moey]

Browsing on Safari like I never do, I thought it was a weird bug. Thanks for my sanity.