@rodhilton perfect. Because the biggest problem with spam is people reading too much of it. And really if your system can't handle massive read loads utilizing things like edge caching then you're probably hosed anyway. What's the betting Twitter tried to get rid of AWS caching with massive scalability and tried to do their own thing that didn't scale? #IsItWebscale ?

Meanwhile wasn't another driver of Twitter's read rate limit to stop crawlers?