apigee + twitter = great match-up; examples of possibilities:
fix for following twitter lists @ http://www.reddit.com/tb/h7032/ (or use
the old interface...)
ease of data access - slides 17+ @ http://goo.gl/HaNdA/ (twitter data
scraped via apigee)
http://twitter.com/#!/aghilmort
--
Twitter
Not to good with this twitter. Will find out tomorrow have more time.
From: aghilmort aghilm...@gmail.com
To: twitter-development-talk@googlegroups.com
Sent: Thursday, 12 May, 2011 18:58:07
Subject: [twitter-dev] Re: New API Console Documentation updates
Wish Google groups had a Like button, because I most definitely like what
y'all have done here.
THANKS!
+100 ;-}
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
We (I work at @apigee) are refreshing the WADL
descriptionhttps://github.com/apigee/wadl-library/blob/master/twitter/api.twitter.com.xml
that
drives the API Console for Twitter in the next few days to make sure that it
is as up-to-date as possible.
And if anyone has feedback about what would
Whoops, I put percent-encoded on text of the web intent link where it wasn't
necessary.
Feedback tweeted @apigee http://twitter.com/intent/tweet?text=@apigee is
the proper way to send it.
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter:
It's great to see progress on this! The real test though will be
whether future reported documentation errors can be fixed immediately
by Twitter staff once verified. Refreshing documentation every 6 - 12
months is something, but far from ideal. Hopefully the recent efforts
by Twitter staff to
