Oops, that's a bug with how we're using Angular. Thanks for pointing it out!

Yes, typical single-page application bug where you need to handle it by itself.

Take also into account the possibility of having many tabs opened with different navigation paths.

Usually I associate sites that break the back button as untrustworthy (Spam, Porn, Porn Spam, Malware). Not a great first impression considering, you know bitcoin, money and all of the fraud that has been associated with it to this point.

Not only that but the back button shenanigans seems to actually have caused the HN favicon in MobileSafari new tab screen to be replaced with their bitcoin logo!

Ha, I'll have to try that. Does it use our icon even if you just navigate to HN directly?

Could call that a feature ;P

I would just bake the static pages as html and serve with nginx or cache on CDN. It seems like overkill to cause all pages to render with JavaScript.