Hi Yusuke,
The host is experimental so we're just looking for feedback about it's
performance right now.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Mon, Feb 14, 2011 at 6:48 AM, Yusuke Yamamoto yus...@mac.com wrote:
Hi Matt,
Are trends.api.twitter.com/* officially supported endpoints?
In other words, should Twitter4J and other libraries connect to
trends.api.twitter.com by default?
Thanks,
--
Yusuke Yamamoto
yus...@mac.com
this email is: [x] bloggable/tweetable [ ] private
follow me on : http://twitter.com/yusukeyamamoto
subscribe me at : http://samuraism.jp/
On Feb 11, 2011, at 10:40 , Matt Harris wrote:
Hi Ian,
For trends you might like to try our trends.api.twitter.com server which
hosts a cached copy of the trends information and is updated whenever the
trends change. It should support your use case and we would be interested in
any feedback you may have about it's performance.
To use it just map the api.twitter.com trends request onto the
trends.api.twitter.com domain name, for example:
http://api.twitter.com/1/trends/available.json
becomes:
http://trends.api.twitter.com/1/trends/available.json
and:
http://api.twitter.com/1/trends/1.json
becomes:
http://trends.api.twitter.com/1/trends/1.json
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
