I wasn't thinking of hashbangs, which will ultimately be noise in the history of Twitter. (I could get into a debate about why they weren't that bad, but it's a

I wasn't thinking of hashbangs, which will ultimately be noise in the history of Twitter. (I could get into a debate about why they weren't that bad, but it's all (HTML5) history now, so I'll move on.) I was thinking mostly about the clean, namespaced, REST scheme for their API, which you can see at https://dev.twitter.com/docs/api https://dev.twitter.com/docs/api. And it's not just a separate API, as it corresponds closely to the website URLs too. Generally, Twitter and Digg were the best examples of real-world REST implementations around that time. That people like Oatmeal are making fun of the crazy-long Plus URIs [1] shows it's not just RFC longbeards pontificating about The Right way to build web apps. At least some end-users notice and care about this stuff too. 1. http://techcrunch.com/2012/08/12/google-plus-the-oatmeal/ http://techcrunch.com/2012/08/12/google-plus-the-oatmeal/