Re: Twitter
[email protected] Wed, 19 Sep 2012 08:44:46 -0400
| Newsgroups | gmane.mail.spam.crm114 |
|---|---|
| Message-ID | <[email protected]> |
Chris Babcock <[email protected]> writes: > On Sun, Sep 16, 2012 at 11:44 AM, Chris Babcock <[email protected]> wrote: >> I'm writing a bot to find people to follow on Twitter who post >> relevant material on a given topic. I need to be able to avoid >> spammers, follow bots and Beliebers. What's the best classifier to use >> on short text like a tweet or a Twitter bio? I'm trying to make this >> bot behave more like a human, discovering content by crawling the >> social graph rather than just following a fixed set of hash tags. >> >> Chris >> -- >> "Nothing says, 'I love you,' like 200 feet of parachute cord and a cargo net." >> - Fred, Scooby-Doo! Mystery Incorporated > > I tried correlate on the bios only. It was predictably a failure. Then > I found that I could request an arbitrary number of tweets with the > bio. The default of 30 tweets trained the correlator almost > satisfactorily, but I decided to try hyperspace. > > I'm getting reasonable results with the hyperspace classifier using > TOE, but I'm wondering how it would do with SSTTT. Are there any good > training examples that someone could put up on Pastebin? I tried > Google, but all I got was mailing list articles. The one post > containing code was too complex to serve as a general example. > > Here's my TOE code: > > http://pastebin.com/jCDshUn5 > > I'm probably just one loop away from SSTTT... Less than that, actually. Right now, if I read it correctly out of pastebin, the built-in test in CLASSIFY is thresholding at a pR of 0.0 and you do this test at lines 35 and 51 The difference is to grab the output of the classify in line 35 and 51, and then check it to see whether the pR listed is sufficiently high and in the right direction - if insufficient, then train. It takes about two or three lines in each place, which you can crib from the mailing list articles. Here's the relevant part of one that looks nice: { do your classify here, capture the result as :stats: } match (:: :pR:) [:stats:] /Best match.*: (.*) \nTotal/ { { eval /:@::*:pR: > 0.5:/ #SSTTT { [[[ do your learn here... ]]] } } } (note: we wrap the CLASSIFY in {} so that the built-in FAIL doesn't cause a skip if it fails) - Bill Yerazunis ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/