I haven't been doing anything with the REST API recently but I think
there was some kind of event on Streaming last night. I don't have
the data here but it was about 2011-06-27T05:00:00Z if I remember
correctly. I was connected to the sample stream with basic auth if
that matters. It looked like a giant spike in tweet rate and it sent
the Perl AnyEvent::Twitter::Stream library into deep space. It
recovered fairly rapidly, although my machine didn't - I ended up
rebooting. ;-)
--
http://twitter.com/znmeb http://borasky-research.net
A mathematician is a device for turning coffee into theorems. -- Paul
Erdos
Quoting Nicholas Chase nch...@earthlink.net:
On 6/27/2011 6:25 PM, jenny wrote:
To make things more exciting, all new site stream connections started
returning 401s half an hour ago(9:47utc)...
-jenny
Check your access tokens; that's what's been happening to me for the
last several days, and it comes down to the access key and secret
spontaneously changing. (Still waiting to hear on that one...)
Nick
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
