Twitter Search seems to have dropped or lost its ability to parse
shortened URLs, as of Sept. 21, which is the key to surfacing domain
searches within shortened URLs.
Not sure if this is a glitch or an intentional change.
--
Twitter developer documentation and resources: http://dev.twitter.com/d
The method Brian describes is essentially what I have been using for
the past four weeks, tapping the Search API atom feed at intervals
(every three hours), using since_id to pull everything since the last
saved tweet ID.
Since Sept. 21, tweet volumes from this method have dropped 99
percent. The
I suspect this has something to do with the fact that Twitter Search
has essentially stopped parsing shortened URLs, as of Sept. 21 (http://
groups.google.com/group/twitter-development-talk/browse_thread/thread/
9ab5fd225a6250e1#).
So, when Twitter searches for your counturl, it can find only thos
Apologies for the double post, but the above URL is incorrect and
should be:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/d6c3996bc451c0a6#
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twi
