esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Hirsch <hirsch.d...@gmail.com>
Subject Re: Twitter API broken?
Date Fri, 04 Dec 2009 10:49:33 GMT
What is strange is that the old REST API is still working  ( I tried
using the old Javascript
http://code.google.com/p/esmeproject/wiki/PureJavascript_messaging_client).

D.

On Fri, Dec 4, 2009 at 11:09 AM, Richard Hirsch <hirsch.dick@gmail.com> wrote:
> I've tried using the Twitter API to send a message and I'm getting a
> strange error:
>
> INFO - Request /twitter/statuses/update.xml took 328 query
> INFO - OK
> INFO - <?xml version="1.0" encoding="UTF-8"?>
> <hash operation="statuses" success="true" ><error>User authentication
> failed</error></hash>
>
> Here is the action I'm using locally to the error (where bob is the
> user and the password is 123456)
>
> http://bob:123456@localhost:8080/twitter/statuses/update.xml
> status=%s
>
> When I use the token instead of the password (like this)
>
> http://bob:Q5PWWXVAJYIPG0EQXMSDPFRGCE2XVTQ0@localhost:8080/twitter/statuses/update.xml
> status=%s
>
> I get this error:
>
> INFO - <?xml version="1.0" encoding="UTF-8"?>
> <hash operation="statuses" success="true" ><error>User authentication
> failed</error></hash>
>
> Anyone else having this problem?
>
> D.
>

Mime
View raw message