The behavior on this group has changed significantly since Ryan finally admitted that Whitelisting no longer exists. I've never seen anyone discuss methods of getting around TOS before, well there was Edward H., and we saw what happened to him. Now there are free flowing discussions of MTurk and other tricks to go way beyond the rate limits. I think this is great. Frankly, Twitter has done a good job of offering free resources to devs, which I thank them for, but there was way too much fear before. Now there are no extra benefits that can be given and withdrawn "on a case by case basis." Boy do I hate that phrase. Of course, they can ban people from this list, but maybe the irony of Twitter blocking free speech on their own forum may restrain that urge in the future.
Personally, I've treated Whitelisting like Social Security. It ain't going to be there when I need it. That has turned out to be a winning strategy. I don't really violate TOS, since I'm not as spammer, but I have never tried building anything that would fail if Twitter didn't give me Whitelisting "after it got into production", which BTW was the most disrespectful thing I've seen from a platform vendor. Everyone should assume that you need to use what is there by default, and always be ready with a workaround if that gets taken away. My gut tells me that things will get worse before they get better. Twitter HQ will be under huge pressure to make money before the IPO, and we are likely to get some of the cuts. The inevitable "they are parasites leeching off of us" will surface. Anyone here old enough to remember Ed Esber? But in the long run, I've never seen a global phenomenon like Twitter, so I'm in it for the next 10 years at least. Then I can retire. Let's keep the discussion open guys. They've already taken away the most important thing you wanted. Now we can build with our eyes open. And don't be afraid to speak up. This is Twitter. Revolutions happen here. Adam Green Twitter API Consultant and Trainer http://140dev.com @140dev -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk