Hi all, I'm hacking on an app that relies heavily on phrase searching, and have gotten very inconsistent results. Most search queries with phrases work as advertised. See: http://search.twitter.com/search?q=&ands=&phrase=%222day+let%27s+dream+with+our+eyes+wide+open!%22&ors=¬s=&tag=&lang=all&from=&to=&ref=&near=&within=15&units=mi&since=&until=&rpp=10 or http://search.twitter.com/search?q=&ands=&phrase="2day+let's+dream+with+our+eyes+wide+open!"&ors=¬s=&tag=&lang=all&from=&to=&ref=&near=&within=15&units=mi&since=&until=&rpp=10
Advertising
Others, however, seem to ignore the fact that I'm looking for a phrase. See: http://search.twitter.com/search?q=%22rabble%2C+rabble%2C+rabble%2C+rabble.%22 or http://search.twitter.com/search?q=%22i+need+new+socks!%22 I thought perhaps there is a minimum length or word requirement for a phrase, but some very short ones seem to work just fine. See: http://search.twitter.com/search?q=%22it%27s+happy+hour%22 Has anybody run into this? Any workarounds (besides further processing the text from the calling application)? Cheers, Robby -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
