3 ms·
Interestingly, I was the one who lobbied Twitter (more specifically Matt Sanford of the search team) to make '$' a valid stop character for searching on summize
by jazzychad 14y ago
Interestingly, I was the one who lobbied Twitter (more specifically Matt Sanford of the search team) to make '$' a valid stop character for searching on summize/twitter search. You've been able to search $TICKER for 2-3 years now. The only thing Twitter has done now is linkified them like hashtags, and they only link to a twitter search of that ticker... so nothing really interesting yet.
I've also linked $TICKER from TweetGrid for as long, except my links go straight to StockTwits: e.g. http://tweetgrid.com/grid?l=0&q1=%24AAPL http://tweetgrid.com/grid?l=0&q1=%24AAPL
- lusr 14y agoMy problem was Twitter's API not having a more intelligent filter API. If you want to use it to filter all tweets with stocks (i.e. "\$\w{1,4}") you can't as far as I could tell. Instead you have to filter on '$' which gets you a ton of noise ("got me some $$$ for 2NITE! yeah!!!!").
- dtsingletary 14y ago... Which you could them pull into a database and filter with your Regex after the API. What does the noise cost you? It's a solvable problem. true, the expanded results may keep you from getting relevant tweets due to rate limiting.
- yo-mf 14y agoBut that is the point, you get rate limited. Of course you can take the data set and clean it in your own database. The problem is how much relevant data you can get before getting cut off.
- wslh 14y agoTwitter has an incredible primitive search. A search for C++ searches for C instead of recognizing the whole term.