://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/
>
>
> <http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/>and
> verifying the signature base string and signature you're generating to what
> that emits.
>
&
I'm having a heck of a time getting the users/lookup to work. I keep
getting an "invalid signature" response, however if I try hitting
other urls that require authentication (such as statuses/
home_timeline) I get the proper response.
The only difference that I can see is that the users/lookup req
C2%A0show>
> > method
> > to get the correct user id if necessary.
>
> You will see
> fromhttp://api.twitter.com/users/show.json?screen_name=katie_wallsthat the
> actual user id is 75030777.
>
> Abraham
>
>
>
>
>
> On Sun, Apr 11, 2010 at 12:07, rya
Hey all, I've noticed some very odd and inconsistent behaviour over
the past couple days that has me stumped. When I use the users/show
endpoint using user_id the response produces a 404. When I use
screen_name of that same user everything works fine. Anybody know what
the scoop is?
here are a co
