Comments on: Comment Spam http://www.hornlo.org/isotropic/2008/08/22/comment-spam/ Where ever you go, there you are. Tue, 25 May 2010 15:16:38 +0000 hourly 1 http://wordpress.org/?v=3.1.3 By: hornlo http://www.hornlo.org/isotropic/2008/08/22/comment-spam/comment-page-1/#comment-451 hornlo Thu, 04 Sep 2008 10:10:35 +0000 http://www.hornlo.org/isotropic/?p=137#comment-451 I've had a lot of search hits for that IP address from the first day I published it. We have plenty of company. I’ve had a lot of search hits for that IP address from the first day I published it. We have plenty of company.

]]> By: Michael Hoppal http://www.hornlo.org/isotropic/2008/08/22/comment-spam/comment-page-1/#comment-450 Michael Hoppal Thu, 04 Sep 2008 03:24:45 +0000 http://www.hornlo.org/isotropic/?p=137#comment-450 I've also been getting a LOT from 200.63.42.136... Actually, 152 spam comments, to be exact. I just got so fed up from it that I made a .htaccess. I think when I looked it up, it said Argentina. Not like I'm going to get any readers from there -- I don't speak Spanish. I googled the address just to know somebody else was suffering with me. Good to know. I’ve also been getting a LOT from 200.63.42.136… Actually, 152 spam comments, to be exact. I just got so fed up from it that I made a .htaccess. I think when I looked it up, it said Argentina. Not like I’m going to get any readers from there — I don’t speak Spanish.

I googled the address just to know somebody else was suffering with me. Good to know.

]]> By: hornlo http://www.hornlo.org/isotropic/2008/08/22/comment-spam/comment-page-1/#comment-446 hornlo Tue, 02 Sep 2008 18:57:13 +0000 http://www.hornlo.org/isotropic/?p=137#comment-446 Looks like 200.63.42.<i>85</i> has now become another source of spam from that network. I've added it to my deny list -- one more from that network and I'll just wildcard it. Also entertaining is that the original post has become a target of the lets-list-20-links type of spam. You'd think they'd know better, but I guess they're trying the 'better living through ignored automation' route. Looks like 200.63.42.85 has now become another source of spam from that network. I’ve added it to my deny list — one more from that network and I’ll just wildcard it.

Also entertaining is that the original post has become a target of the lets-list-20-links type of spam. You’d think they’d know better, but I guess they’re trying the ‘better living through ignored automation’ route.

]]>