Indeed. I tried several other employees. Not all of them exhibited
this behavior, but all of the users that did, were Twitter employees.
If this is some magic, it would be better for it to throw a 404 or
401. I think most developers disregard 404s, but retry on 500.
In my application, retrying on
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
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
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:
http://twitter.com/statuses/user_timeline/kevinweil.json?page=1count=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,
Well this seems to work:
http://twitter.com/statuses/user_timeline/kevinweil.json?count=10page=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=1count=200
yields File not Found in Firefox.
In Safari,
yeah, perhaps some greg pass magic going on on the account behind the
scenes.
On Thu, Jan 14, 2010 at 5:18 PM, Ryan Rosario uclamath...@gmail.com wrote:
count=200 worked for the hundreds of other users, just not this one.
This seems like a bug.
I can't even retrieve his tweets in Tweetie
