Are you using twitteroauth library?
Also, the url should be like
http://api.twitter.com/1/statuses/user_timeline/sh...82
Atleast i am using this and it works for me.
On Thu, Feb 10, 2011 at 3:44 PM, nite21 shanebond1...@gmail.com wrote:
hi all
im loading twitter xml data and showing it in
As Paresh mentioned,
Your URL needs to be:
a) pointed to the *api* subdomain
b) versioned -- always *1* at this time
c) specifying a format - usually either *json* or *xml*
And should use:
a) the screen_name parameter instead of an interpolated URI element to
avoid issues with all-integer
On Mon, May 17, 2010 at 11:22:56AM -0700, Jef Poskanzer wrote:
Have you considered keeping basic auth enabled, but only for https?
This would be secure against packet sniffing and would probably use
less resources than OAuth.
The issue with Basic Auth isn't packet sniffing.
The issue with
I agree.
I don't think Basic Auth it's just that insecure and OAuth it's showing many
errors...
On Mon, May 17, 2010 at 8:22 PM, Jef Poskanzer jef.poskan...@gmail.comwrote:
Have you considered keeping basic auth enabled, but only for https?
This would be secure against packet sniffing and
