Twitter’s WWDC 2008 uptime strategy
It appears that part of Twitter’s strategy to mitigate downtime during WWDC 2008 this year is to push tracking, and therefore traffic and constant refreshing, of the event over to third-party search service, Summize. I’ve noticed before that Summize will often not return the most recent tweets associated with a search. So, it may be less than real time.
However, it could also be that Twitter is working closely with the Summize team and will allow unthrottled access to the API during the event while throttling everyone else back… and it just might work.
What do you think?
Update 06.09.2008 11:00am: It’s about an hour away from the WWDC keynote, and Twitter has removed access to archives, direct messages, and the public timeline. They’ve dropped their API request limit to 10 per hour, from 70.