There were a number of threads about this on the mailing list so I
decided it would be better to send a new message announcing the fix,
so my apologies if you missed the announcement.

Thanks for confirming the fix worked for you though.

Best,
Matt


On Thu, Aug 26, 2010 at 6:20 AM, Mark Pavlidis <mark.pavli...@gmail.com> wrote:
> FYI, the fix was deployed yesterday afternoon and I have verified the
> problem has been resolved.
>
> On Aug 25, 2:37 pm, Mark Pavlidis <mark.pavli...@gmail.com> wrote:
>> Hi Matt,
>>
>> Has this fix gone out yet? I'm still seeing the error.
>>
>> Thanks,
>> Mark
>
> --
> 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?hl=en
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
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?hl=en

Reply via email to