Hacker News Reader

They could use the exact same setup they have right now.

They'd just serve the exact same (static) html for every twitter.com/username URL. I don't think it's exactly terrible Javascript hackery to look at the location.href and do an ajax call.

They'd probably support web crawlers with the same system they use now. And many web crawlers these days execute javascript anyway.

View on HN

The system they have now is the #! hack, the crawlers know how to request static versions of the pages. There isn't a similar mechanism for pushState based designs, you just serve up the content pre-rendered for the initial page. So that's probably what they will do to stay indexable. It will also make the first page load snappier (probably)

Reply on news.ycombinator.com