As far twitter API goes, it works fine.I implemented in C#. you can see it
here.
http://www.byteblocks.com/post/2009/05/22/Verify-if-two-twitter-users-are-friends.aspx
May be some JS guru can look thru code and suggest some change.
On Tue, Jun 9, 2009 at 6:16 AM, grand_unifier
Put a break point right after you send request to Twitter to get response
and see what is being returned. I have a feeling that you are running into
request rate limit. And the response you are getting back is not getting
translated to your collection objects.
Do you use any third party libraries
This has gone little too far. Somebody just floated an idea and it became a
storm here :-) Guys lets just tweet :-) Somebody mentioned dumb ideas and
things like that. I think there is nothing as dumb or stupid idea. Every
great idea has to start from somewhere and then takes a shape. Just respect
There are two rate limits. One for user account and one for IP address.
Since you mentioned that when you are on a different server, your status is
100. That definitely indicates that your shared server has lot of twitter
API activity going on.
On Tue, Jun 16, 2009 at 8:14 AM, betweeted
API. I don't see a problem with that.
Doug: Presumably the body of the 403 response will contain a suitable
descriptive error message in the usual format?
-Stuart
--
http://stut.net/projects/twitter
2009/6/16 Naveen Kohli naveenko...@gmail.com:
Why would you make decision based
