Over the past two days, the blog here has been under the effects of a spam storm. Over 200 spam com\u00adments were blocked and ulti\u00admate\u00adly delet\u00aded in that peri\u00adod, the most in all of the his\u00adto\u00adry of the blog. All of these spam com\u00adments were designed to pro\u00admote just one web\u00adsite, a blank page designed to dri\u00adve clicks to a ran\u00addom har\u00advest\u00ading site.<\/p>\n
Its hard to fig\u00adure out whether there was any kind of intel\u00adli\u00adgence to the storm: the spam was quite easy to detect, as there were only two or three dif\u00adfer\u00adent com\u00adment text blocks in use. They all also used much the same pitch to attract clicks to the har\u00advest\u00ading site, a rather come on toward blog own\u00aders to increase their cash\u00adflow return from the blog through the use of a tech\u00adnique that I won\u2019t men\u00adtion by name because I don\u2019t want it to show up in web search\u00ades, which is also why I\u2019m not list\u00ading the har\u00advest\u00ading web\u00adsite, either. It was also pret\u00adty appar\u00adent that at least one of the text blocks was by some\u00adone with a lim\u00adit\u00aded knowl\u00adedge of Eng\u00adlish, whether just by lack of edu\u00adca\u00adtion or if Eng\u00adlish was not their pri\u00adma\u00adry language.<\/p>\n
How\u00adev\u00ader, to cut down on that spam storm, just so that I don\u2019t have to keep clean\u00ading it out of the queue because it always gets caught, I have turned on the require\u00adment that only reg\u00adis\u00adtered mem\u00adbers can com\u00adment. That should\u00adn\u2019t be a prob\u00adlem as the reg\u00adu\u00adlar com\u00admenters are already registered.<\/p>\n","protected":false},"excerpt":{"rendered":"