Rate Limit Status for unauthenticated API requests?

[Jan Krämer]

Hi,

since it seems that the unauthenticated rate limit was switched on,
could you please enable an API comparable to:
http://twitter.com/account/rate_limit_status.xml

It would make planing around that limit much easier. (Especially since
the limit is potentially consumed by twitter badges, if I see things
right...)

Sincerely

- Jan Krämer
@camelus_minimus

[Alex Payne]

We can make that method work for IP-based rate limiting, yes.

--
Alex Payne
http://twitter.com/al3x

[Dossy Shiobara]

Jan Krämer wrote:
> It would make planing around that limit much easier. (Especially since
> the limit is potentially consumed by twitter badges, if I see things
> right...)

LOL, good point - those little web badges on everyone's site ... if you
browse (from the same IP) 100 different pages that each embed a Twitter
badge that causes the browser to make a connection to twitter.com
unauthenticated ... whoops, there goes your rate limit. :-)

This is probably how users' authenticated rate limit gets chewed up,
too: the user authenticates to twitter.com, then goes surfing the web
and the various badges and web dingleberries get the browser to fetch
data from twitter.com, using up their _authenticated_ rate limit for
their user ID.

You hear that giant sucking sound? Yeah.

--
Dossy Shiobara | do...@panoptic.com | http://dossy.org/
Panoptic Computer Network | http://panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)

[Alex Payne]

We should, er, not do that for badges. Quite.

--
Alex Payne
http://twitter.com/al3x