Nevermind … rate limit.
~Barry
On Mar 30, 3:06 pm, bjhess 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.
>
> DirectMessage.find(:all)
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.
DirectMessage.find(:all)
Thanks,
--
Barry
http://iridesco.com
http://bjhess.com
On Mar 30, 2:13 pm,
All,
This is being looked into as I type.
Thanks,
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Mon, Mar 30, 2009 at 12:09 PM, bjhess wrote:
>
> Ditto here.
>
> Note to self, never trust since_id in the Twitter API. This has
> burned me before. It really burned me this time.
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 wrote:
> Ben,
> I can see the same problem. There is now an open issue for this probl
Ben,
I can see the same problem. There is now an open issue for this problem [1].
1. http://code.google.com/p/twitter-api/issues/detail?id=399
Thanks,
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Mon, Mar 30, 2009 at 11:56 AM, Ben Burleson wrote:
>
> I use this URL:
> http://t
Just duplicated the behavior here. The since_id used to work, and
should work afaik... it's probably a transient issue (I hope).
-Chad
On Mon, Mar 30, 2009 at 2:56 PM, Ben Burleson wrote:
>
> I use this URL:
> http://twitter.com/direct_messages.xml?since_id=82528092
>
> The result includes the
