I read this discussion carefully and I cannot extract a conclusion...
The question is why a set of API methods are working and others aren't
working properly, returning a 'Incorrect signature' error.
Methods working now:
- posting a tweet (statuses/update). Works fine
- extract user timeline (st
(I'm using exactly the same client library). It does make
> all kinds of sense.
>
> Regular http requests worked fine before, though.
>
> It's probably been mentioned before. If so, I missed it, sorry. :)
>
> On Jul 30, 12:03 pm, Andreu wrote:
>
> > I re
king
> perfectly (I'm using exactly the same client library). It does make
> all kinds of sense.
>
> Regular http requests worked fine before, though.
>
> It's probably been mentioned before. If so, I missed it, sorry. :)
>
> On Jul 30, 12:03 pm, Andreu wrote:
&
The same behaviour for my application. When the app wants to start the oAuth
workflow in order to authenticate and login the user, the server returns a
timeout from https://twitter.com/oauth/authenticate?parameters
On Thu, Aug 6, 2009 at 11:24 PM, Rich wrote:
>
> I can't get oAuth to authenticat
