This morning I hit 100,000 spammers found and reported! Its a big milestone for me and excited that its been going well as it has. Starting to scale up so should hit half a million spammers before you know it.
Read more »In the last couple days, I’ve scaled up my Twitter Spam Assassin to such large numbers, that I cannot report all the spam that I’m finding anymore. Because I’m not report all the spam I’m finding, the number of spam accounts that stay active spamming people is increasing! I messaged Twitter to help me by …
Read more »Today I discovered that twitter has an api method for looking up 100 different users (unfortunately not supported by Tweepy). I was excited to find this gem, because now the process of vetting accounts I think are spam is a lot easier and faster. So now I run a script that looks up all accounts that …
Read more »As my avid readers would know, the biggest issue i have right now is hitting API call limits. Today to help reduce that problem, I added code to check my db if I’ve already analyzed a twitter account or not. I purposely left this out before because its very possible that an account isn’t spamming when I …
Read more »Today I spent some time to log my errors more in depth by adding traceback (see http://docs.python.org/library/traceback.html). This should be helpful in getting to the bottom on errors when they occur.
Read more »One issue i’ve seen come up time and time again is an error “Not authorized”. Tweepy was giving me this error while pulling from the public timeline. Each time I get this error, my connection to twitter would be severed and would have to reconnect. When I saw this error a lot, i would try …
Read more »I heard word from an official at the Awesome Foundation recently that I was not chosen to receive the grant. But on the up side, apparently some of judges really liked this idea of Twitter Spam Assassin and I was a “finalist”! So close!!! Maybe next time, I def plan on applying again with another idea at …
Read more »