follow cost

Hi, Luke Francl and I just released follow cost [1] yesterday. We built it with all-unauthenticated calls to the Twitter and Twitter Search API's. Our understanding, based on the docs, was that these calls are not rate limited. Yet to be good stewards, we cache our results pages for 24 hours.

Re: follow cost

Thanks! ~Barry On Oct 14, 10:39 am, Abraham Williams [EMAIL PROTECTED] wrote: http://twitter.com/help/request_whitelisting On Tue, Oct 14, 2008 at 10:12, bjhess [EMAIL PROTECTED] wrote: Hi, Luke Francl and I just released follow cost [1] yesterday.  We built it with all

Re: Change to Twitter API?

I am no longer seeing created_at in the returned user record for http://twitter.com/users/show/id.xml. Naturally, this has broken Follow Cost. :( Thanks, -- Barry http://followcost.com On Dec 10, 7:39 pm, Alex Payne [EMAIL PROTECTED] wrote: Looking into this one further... On Wed, Dec

[twitter-dev] Re: direct_messages since_id parameter doesn't work

Ditto here. Note to self, never trust since_id in the Twitter API. This has burned me before. It really burned me this time. -- Barry http://iridesco.com http://bjhess.com On Mar 30, 2:06 pm, Doug Williams d...@twitter.com wrote: Ben, I can see the same problem. There is now an open issue

[twitter-dev] Re: direct_messages since_id parameter doesn't work

, Doug Williams d...@twitter.com wrote: All, This is being looked into as I type. Thanks, Doug Williams Twitter API Supporthttp://twitter.com/dougw On Mon, Mar 30, 2009 at 12:09 PM, bjhess bjh...@gmail.com wrote: Ditto here. Note to self, never trust since_id in the Twitter API

[twitter-dev] Re: direct_messages since_id parameter doesn't work

Nevermind … rate limit. ~Barry On Mar 30, 3:06 pm, bjhess bjh...@gmail.com wrote: Wondering if you possibly broke some sort of ActiveResource (Rails) compatibility here?  My call, which worked just fine this morning and the past 12 months, now fails with a 400 Bad Request

[twitter-dev] Search problems for from:username searches

We have had some users complain about not being able to find themselves on http://followcost.com. I've dug into the code and it appears the failure is happening on queries to the search API of the form from:username. A couple example queries that return zero results:

[twitter-dev] Re: Upcoming changes to the way status IDs are sequenced

+1 on IDs being increasing. Sequential doesn't matter to me. I don't actually trust passing since_id to Twitter and having them handle the limiting of my result list. I've gotten into trouble when that feature suddenly quit being recognized and my code wasn't defensive enough to double-check

[twitter-dev] Getting 401 when using one access token with OAuth

I'm trying to implement the following in Ruby: http://dev.twitter.com/pages/oauth_single_token Unfortunately I'm receiving 401's from to Twitter usernames, harvest and harvest_test. Both have been set up with an OAuth key and secret. I'm essentially using the identical code to your sample. I

[twitter-dev] Re: Getting 401 when using one access token with OAuth

/twitter-development-talk/browse_thread... regards On May 14, 5:48 pm, bjhess ba...@bjhess.com wrote: I'm trying to implement the following in Ruby: http://dev.twitter.com/pages/oauth_single_token Unfortunately I'm receiving 401's from to Twitter usernames, harvest and harvest_test

[twitter-dev] Re: Getting 401 when using one access token with OAuth

? Assuming all is correct, this part should function. After you've checked your clock and if you're still having issues I'll help you debug this further. Thanks, Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Mon, May 17, 2010 at 7:35 AM, bjhess ba...@bjhess.com