Well this seems to work:

http://twitter.com/statuses/user_timeline/kevinweil.json?count=10&page=1

On Thu, Jan 14, 2010 at 5:00 PM, Ryan Rosario <uclamath...@gmail.com> wrote:

> http://twitter.com/statuses/user_timeline/kevinweil.json?page=1&count=200
> yields "File not Found" in Firefox.
>
> In Safari, it downloads the 500 web page.
>
> R.
>
> On Jan 14, 4:51 pm, Peter Denton <petermden...@gmail.com> wrote:
> > if you put the URL in the browser it works?
> >
> > On Thu, Jan 14, 2010 at 4:44 PM, Ryan Rosario <uclamath...@gmail.com>
> wrote:
> > > If I remove the "count" parameter from the Curl call, it works, but
> > > with any count parameter, I get a 500.
> >
> > > On Jan 14, 4:39 pm, Ryan Rosario <uclamath...@gmail.com> wrote:
> > > > kevinweil :)
> >
> > > > I logged out of my account and his tweets are publicly viewable.
> >
> > > > On Jan 14, 4:27 pm, Peter Denton <petermden...@gmail.com> wrote:
> >
> > > > > do you have the username? they might be protected, but have given
> you
> > > > > access?
> >
> > > > > On Thu, Jan 14, 2010 at 4:26 PM, Ryan Rosario <
> uclamath...@gmail.com>
> > > wrote:
> > > > > > I am working on a project where I need to extract some tweets
> from my
> > > > > > friends and followers. I follow a couple of employees of Twitter,
> and
> > > > > > for some reason, I cannot retrieve the tweets for one of them. In
> > > > > > Python urllib2, I get a 500 error. In my script, I retry upon a
> 500,
> > > > > > but this profile consistently returns a 500 error.
> >
> > > > > > If I use curl to try to retrieve this user's tweets, I get a 500
> web
> > > > > > page ("Thanks for noticing! We'll get on it" or something like
> that)
> > > > > > instead of a JSON error return.
> >
> > > > > > I can email privately which user I am talking about because I
> don't
> > > > > > want to post it here unless it is ok. Is this is a random
> problem, or
> > > > > > is there extra security on employee profiles? I also experience
> this
> > > > > > problem when trying to list their tweets in Tweetie.
> >
> > > > > > TIA,
> > > > > > Ryan
>

Reply via email to