Re:Twitter's garbage problem
by kmavm on Sunday May 16, 2010 @10:24PM
(#1353313)
I've looked into this a bit, albeit more in a spam-filtering context; tweets have very little text for naive Bayes to latch onto. 140 characters would be 20-30 words, tops. That is so few words that it is hard to move the prior very much, unless there are blockbuster words that almost always indicate a bad tweet; as the article suggested, "breakfast", "beer", etc.
[ Parent
| on HN ]
Here's a start. It's a simple ruby app that runs on heroku and proxies your twitter account, dropping uninteresting things. Extremely raw code.
Re:Twitter's garbage problem
by JCThoughtscream on Sunday May 16, 2010 @10:43PM
(#1353353)
Filter by account, then, instead of by post? With a sample body of, say, the ten or twenty of an account's most recent posts.
The article's whole premise was that tweet quality does not correlate well within an account; e.g., some marvelous twitter streams include breakfast tweets.
As I said, I'm fine with a filter that has poor accuracy, as long as it makes twitter marginally better.
Dont many classifiers pick the most interesting n words and only use those to decide? Where n is something like 15.
They usually have a lot more than 15 words to choose from, though.