No change that I'm aware of, but we push dozens of changes on most business
days, many of which could change the format of a message. If this client
doesn't use a full JSON parser, but instead tries to pick things apart with
Regexp, problems will result. If you are having connection problems, ensure
that you aren't getting rate limited and that you haven't been black-listed.
-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.
On Wed, Jan 20, 2010 at 2:26 AM, Nigel Cannings
nigelcanni...@googlemail.com wrote:
About 4 hours ago, I started getting bizarre JSON errors from
Net::Twitter::Stream - Does anyone know if there has been a change at
the stream end?
