I've attached hover cards to many places in our UI, but the end-result
is that the user runs into the rate-limit (150 requests per hour) very
quickly while simply broswing around. Once the rate limit is reached
the @anywhere functionality is basically broken, you can't even log
out.
Is there a way around the rate limit without training the user to
avoid hover cards?
Is there a recommended way in @anywhere to detect when the rate limit
is reached and message that to the user?
By the way, this all seems rather dumb. Why do the rate limits apply
to hover cards in the first place? It would seem to me that Twitter
should encourage the use of hover cards where possible.
Thanks,
Arthur van Hoff
Grand Master of Alphabetical Order
The Ellerdale Project
--
You received this message because you are subscribed to the Google Groups "Twitter Anywhere Development" group.
To post to this group, send email to
twitter-de...@googlegroups.com.
To unsubscribe from this group, send email to
twitter-dev-anyw...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/twitter-dev-anywhere?hl=en.