Spam, spam, spam, spam, spam.... Ad nauseum.


  • user warning: Can't open file: 'cache_filter.MYI' (errno: 145) query: SELECT data, created, headers, expire FROM cache_filter WHERE cid = '1:00fe2b168390872db9f86ce9eae55fe0' in /includes/database.mysql.inc on line 174.
  • user warning: Can't open file: 'cache_filter.MYI' (errno: 145) query: LOCK TABLES cache_filter WRITE in /includes/database.mysql.inc on line 174.
  • user warning: Can't open file: 'cache_filter.MYI' (errno: 145) query: UPDATE cache_filter SET data = '<p>There\'s been a little busy beaver of a spammer lately that\'s been hitting the site, so I\'ve implemented the Drupal spam module to see if that controls it.</p>\n<p>Unfortunately, Canadian law doesn\'t permit the execution of spammers, so I\'ve been forced to take other measures to deal with the problem. At some point, I have to think that most governments will start to realize that these wastes of skin are actually a massive detriment to Internet commerce, amongst other things, and actually start to take real preventative steps. Maybe that\'s wishful thinking.</p>\n<p>All I know is that, speaking as someone who has been using the Internet before Netscape Navigator was even an idea, the spam problem is the single worst thing about the Internet. It\'s frustrating, infuriating, and it continues unabated. There was a time that the British Navy use to put pirates in a gibbet as a warning to others. Seems to me that this might be a good practice for dealing with spammers. Not ladylike, I know, but I\'m past the point of mere irritation.</p>\n<p>Anyways, because of the filters, some legitimate postings might not appear immediately. Don\'t worry, the filter doesn\'t destroy spam, it merely prevents it from being published if it thinks it is spam. Anything not spam will publish as usual and anything marked as spam will be reviewed by me and published if legitimate. Hopefully this works, though I\'m on vacation next week and so won\'t be checking during that time. Other than that, I\'ll just keep on top of it.</p>\n', created = 1369503965, expire = 1369590365, headers = '' WHERE cid = '1:00fe2b168390872db9f86ce9eae55fe0' in /includes/database.mysql.inc on line 174.
  • user warning: Can't open file: 'cache_filter.MYI' (errno: 145) query: SELECT data, created, headers, expire FROM cache_filter WHERE cid = '1:e33e716af34612b3b033739efcec76e7' in /includes/database.mysql.inc on line 174.
  • user warning: Can't open file: 'cache_filter.MYI' (errno: 145) query: LOCK TABLES cache_filter WRITE in /includes/database.mysql.inc on line 174.
  • user warning: Can't open file: 'cache_filter.MYI' (errno: 145) query: UPDATE cache_filter SET data = '<p>Over at the gabyzone, we had to implement a sign in box with numbers so bots can\'t join and post. Helped a lot. And members only to post.</p>\n', created = 1369503965, expire = 1369590365, headers = '' WHERE cid = '1:e33e716af34612b3b033739efcec76e7' in /includes/database.mysql.inc on line 174.
  • user warning: Can't open file: 'cache_filter.MYI' (errno: 145) query: SELECT data, created, headers, expire FROM cache_filter WHERE cid = '1:334756fbd1fe16946114b4e93f00c193' in /includes/database.mysql.inc on line 174.
  • user warning: Can't open file: 'cache_filter.MYI' (errno: 145) query: LOCK TABLES cache_filter WRITE in /includes/database.mysql.inc on line 174.
  • user warning: Can't open file: 'cache_filter.MYI' (errno: 145) query: UPDATE cache_filter SET data = '<p>We\'ll see how this one goes. I\'m trying to avoid CAPTCHA options since they\'re a pain for certain people and are not usually all that effective in the long run. By and large, spammers are looking for big gains and my site isn\'t one of them. However, since there was an opening that they already had scripted, I suppose that they just took it. I\'m curious to see how this module stands up.</p>\n', created = 1369503965, expire = 1369590365, headers = '' WHERE cid = '1:334756fbd1fe16946114b4e93f00c193' in /includes/database.mysql.inc on line 174.
  • user warning: Can't open file: 'cache_filter.MYI' (errno: 145) query: SELECT data, created, headers, expire FROM cache_filter WHERE cid = '1:69af83282d61673f5071f3c55fc4db39' in /includes/database.mysql.inc on line 174.
  • user warning: Can't open file: 'cache_filter.MYI' (errno: 145) query: LOCK TABLES cache_filter WRITE in /includes/database.mysql.inc on line 174.
  • user warning: Can't open file: 'cache_filter.MYI' (errno: 145) query: UPDATE cache_filter SET data = '<p>We all have elements of both genders, why hide them?</p>\n', created = 1369503965, expire = 1369590365, headers = '' WHERE cid = '1:69af83282d61673f5071f3c55fc4db39' in /includes/database.mysql.inc on line 174.

There's been a little busy beaver of a spammer lately that's been hitting the site, so I've implemented the Drupal spam module to see if that controls it.

Unfortunately, Canadian law doesn't permit the execution of spammers, so I've been forced to take other measures to deal with the problem. At some point, I have to think that most governments will start to realize that these wastes of skin are actually a massive detriment to Internet commerce, amongst other things, and actually start to take real preventative steps. Maybe that's wishful thinking.

All I know is that, speaking as someone who has been using the Internet before Netscape Navigator was even an idea, the spam problem is the single worst thing about the Internet. It's frustrating, infuriating, and it continues unabated. There was a time that the British Navy use to put pirates in a gibbet as a warning to others. Seems to me that this might be a good practice for dealing with spammers. Not ladylike, I know, but I'm past the point of mere irritation.

Anyways, because of the filters, some legitimate postings might not appear immediately. Don't worry, the filter doesn't destroy spam, it merely prevents it from being published if it thinks it is spam. Anything not spam will publish as usual and anything marked as spam will be reviewed by me and published if legitimate. Hopefully this works, though I'm on vacation next week and so won't be checking during that time. Other than that, I'll just keep on top of it.

spam

Over at the gabyzone, we had to implement a sign in box with numbers so bots can't join and post. Helped a lot. And members only to post.

That's an option as well

We'll see how this one goes. I'm trying to avoid CAPTCHA options since they're a pain for certain people and are not usually all that effective in the long run. By and large, spammers are looking for big gains and my site isn't one of them. However, since there was an opening that they already had scripted, I suppose that they just took it. I'm curious to see how this module stands up.