March 28, 2006
Mike Furir is a big fucking idiot
Some asshole named Mike Furir has been posting comment spam here on le blog for the last few days. Thankfully, the comment filters installed by my lovely and talented blog-host Mr. GAK have ensured that said spam finds its way to the junk bin and does not besmirch your eyes, my dear readers. (All six of you.)
A quick Google confirmed that I'm not the only one getting hit by this shitsmear named Mike Furir. (Hey, that rhymed.) Here are a few other posts on the topic:
- Quixtar Blog: Die Mike Furir
- Jake Ludington: Mike Furir Sucks
- Miss Zoot: I'll join the ranks in wanting Mr. Mike Furir to Die a slow, painful, and hopefully humiliating death.
- It's a Soul Thing: Sock it to me baby!
So, Mike Furir, how's your Google-juice now, ya stupid moron?
Posted by jenv at March 28, 2006 08:25 PM | Filed under: Business and Technology , Misc.Arrr, I be here to serve the more verbose pirates in these seas, not the scalliwags threatening me ship.
I'm not sure what the success rate of Mr. F has been since all the links in the comments include the rel=nofollow attribute, which means Google won't index a thing.
http://googleblog.blogspot.com/2005/01/preventing-comment-spam.html
But god, it's fucking annoying.
Posted by: gak at March 28, 2006 08:56 PMI read the article about the no-follow tags, but I didn't understand it. Does it mean that any comment made will have a tag, or do we, as bloggers have to do it? Damn, I'm so technology illiterate!
Posted by: Maria at March 29, 2006 04:37 PMi doubt there is a person with that name. most likely someone is using that name to test a anu-spamming software they developed. or the tests are over and they are just using the name to continue. i always find it weird when this comment spam doesn't actually lead anywhere that would generate revenue so testing is all i can come up with. or a jerk.
Posted by: tbit at March 30, 2006 11:19 AMheh-heh. shitsmear.
I just went thru a huge spam attack by the celebrated shithead behind Mike Furir on my MT powered blog and managed to reconfigure the comments process by renaming the comments.cgi file to "new_name".cgi and then changing the mt-cfg file to point to that new name.
Apparently this will foil about 95% of spam, because most spammers use the common .cgi file names that .come with the various blogging software to tap into whatever blogs they find on Google or whatever search engine and put them on a white list for their spamming software crawling. Its a fairly simple way to make your comments area relatively secure from this creeps.