A small update... After letting it rest over night, I was able to get /statuses/filter.json to work on my office machine using any set of keys, but attempting to run with any keys on ec2 gets us a 420. Immediately after the 420 in ec2, I can run without issue in the office. I've tried a few of our different hosts in ec2, but they all seem to get a 420 error.
- Josiah -- 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
