Just to say it, this matching of "actual" URL as well as the
shortened, supplied URL has been regarded as a bug by our users; it
confuses them. I would prefer it if it were optional to search so
that I could turn it off... They only want to match the literal
text... We provide means for th
Fantastic, thank you!
On Wed, Jun 9, 2010 at 2:48 PM, Mark McBride wrote:
> We will have this support in the streaming API. Track terms will work
> against tweet text as well as entity text. Currently streaming does
> *not* work as Abraham describes below. We only match against tweet
> text,
We will have this support in the streaming API. Track terms will work
against tweet text as well as entity text. Currently streaming does
*not* work as Abraham describes below. We only match against tweet
text, and don't do any link expansion/contraction.
---Mark
http://twitter.com/mccv
Currently Search (and probably Streaming) returns results that match text in
unshortened URLs not just in the text of the status. I doubt It would change
now especially with t.co coming.
Abraham
-
Abraham Williams | Developer for hire | http://abrah.am
@abraham | http://projects.abrah.
I'm creating a new thread for this because a few others have mentioned it,
and we haven't gotten a response yet. My hunch is that changing those APIs
involve other teams within Twitter, so figuring out a solution could be
challenging.
Here is the issue. We need to be able to get matches on the o
