Thanks to all for the pointers. I got everything rewritten and working now
thanks to the examples from Joe Chung.
http://nullinfo.wordpress.com/oauth-twitter/
Steve
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterap
-dev] Re: Change in error response objects
Hey Steve,
To expand on Tom's message, Basic Auth is no longer supported on the Twitter
API and you need to update your script to use OAuth. In addition you want to
make sure the URL you are calling is pointing to
http://api.twitter.com/1/sta
-development-talk@googlegroups.com
Subject: Re: [twitter-dev] Re: Change in error response objects
http://dev.twitter.com/announcements
Tom
On 9/3/10 6:35 PM, MrMoxy wrote:
> Raffi,
>
> I have been using the API to tweet twice daily for months, but my
> script suddenly sto
Hey Steve,
To expand on Tom's message, Basic Auth is no longer supported on the
Twitter API and you need to update your script to use OAuth. In
addition you want to make sure the URL you are calling is pointing to
http://api.twitter.com/1/statuses/update.xml - all API requests should
go through ht
http://dev.twitter.com/announcements
Tom
On 9/3/10 6:35 PM, MrMoxy wrote:
> Raffi,
>
> I have been using the API to tweet twice daily for months, but my
> script suddenly stopped working yesterday morning. I am posting to
> this page using a curl connection
>
> http://twitter.com/statuses/upda
Raffi Krikorian wrote:
> it is designed so that we can send multiple error codes back, but in
> practice, right now, we only send one.
>
> On Sun, Aug 29, 2010 at 4:25 PM, Dewald Pretorius wrote:
>
> > Raffi,
> >
> > Will the new error construct always be:
> >
> > [errors][code]
> > [errors][mes
it is designed so that we can send multiple error codes back, but in
practice, right now, we only send one.
On Sun, Aug 29, 2010 at 4:25 PM, Dewald Pretorius wrote:
> Raffi,
>
> Will the new error construct always be:
>
> [errors][code]
> [errors][message]
>
> Or can it be sometimes:
>
> [errors
