4 ms·
This is simply a case of an out-of-date reference blog post (that 2010 #newtwitter article). Quick observation of Twitter.com today will reveal that it's no lo
by bcherry 14y ago
This is simply a case of an out-of-date reference blog post (that 2010 #newtwitter article). Quick observation of Twitter.com today will reveal that it's no longer using the public API (at least from the client). It's fetching the Tweets from the server pre-rendered (via http://twitter.com/i/timeline http://twitter.com/i/timeline). So nothing to see there. Maybe taking a closer look at Twitter for iOS, which does receive promoted Tweets, would provide more information.
- mschonfeld 14y agoWell, the real point of what I was trying to say in the article was that Twitter had publicly stated that they're moving to an API oriented architecture - meaning that the web client is merely just another API client. That, coupled with the non-conforming-UX API key revoking acts recently, made me question the legitimacy of their statements...
- eli 14y agoI don't understand why it matters whether the web client uses a public api? And anyway it's totally reasonable for tge server to access an internal api and prerender the result.