| Otherwise Occupied |
| About Greg Classes Ride Videos |
|
spam
gregh 2007-06-14 10:12 Blogging spam
On February 14, I noted that after 3 months, Akismet, which I use to filter spam from comments here, had blocked 100 comment spam. The rate was roughly 33 per month. Today, 4 months later, that rate is over 100 per month. The ironic part about this is that the comment spam has increased even as my blogging output has decreased. I had assumed that they would key off changing content, as that would seem to indicate more of a userbase. While they do seem to key off of particular content (anecdotally, this is the page most commonly spammed), they don't seem to care about new content or rate of change at all. I'd suggest that slower turnover is better, because it could potentially indicate a site administrator who's not overly in touch with the blog. However, states from Scoble and Arrington seem to suggest that their substantially more popular and changing blogs are spammed at a much greater frequency, not counted in hundreds per month, but in hundreds per hour or more. Based on the content, I assume it is still largely out to game the search engines by linking all over creation. Right now, I just let Akismet delete it after 24 hours. Akismet has yet to turn up a false positive -- given my low rate of comments, this is not a huge endorsement, however -- and only misses the occasional spam. If my numbers were bigger, I'm sure I'd be much less thrilled. Clearly, something needs to be done about this scourge of bots that allows spammers to operate so freely.
gregh 2007-04-10 08:23 email spam
You know your work is infecting your sensibilities when you open a mail with the above subject headings, worried that it might just be about system with those names and not a spam.
gregh 2007-03-12 13:49 akismet Blogging spam
These people start off with such great feedback, yet they follow-up with all sorts of URLs! "See you...Thanks, its great to receive such positive comments." "This is a cool site! Thanks and wish you better luck! Brilliant but simple idea." ("Simple idea?" *sniff*) "Your site was so interesting and informative I had to call a friend to tell her about it. Great work" (Now, that one I like.) I'm not willing to follow any of the links they've included. Fortunately, Akismet continues to do a great job filtering this stuff out for me.
gregh 2007-01-28 03:02 akismet Blogging Drupal spam
After trying a number of things to combat spam, a little over 3 months ago I installed Akismet, a free-for-non-commercial-use anti-spam service from Automattic, the people behind WordPress.com and WordPress.org. Of course, I don't use WordPress for this site; I use Drupal. No worries. The Automattic folks allow anyone to code to the API, and Markus Petrux of phpMiX.org has written a Drupal Akismet module. As you can see from the counter in the lower right, in just over 3 months, Akismet has caught 100 spam comments. That seems to be a pretty good indicator that my site is not popular enough to be hit. I do run the Bad Behavior module, as well, which catches lots of comment spam before it gets to Akismet, rejecting it for petty little things like bad headers and stuff. My Akismet numbers might be higher, but I like that Referer spam is blocked by Bad Behavior. Before Bad Behavior, the spam was much worse. But even with it, it was pretty bad. I used the old Spam module for Drupal, but it had pretty poor results. Then I shifted to captcha, but spammers got by it even when legit people couldn't. Akismet has been wonderful. Nothing's slipped past, and nothing's been falsely accused of being spam. That's pretty good.
gregh 2006-11-06 15:43 email Law privacy spam
My fellow USF School of Law blogger notes: Spam: This is good to know. Cal. Bus. & Professions Code section 17538.4 requires that spam have an opt-out feature. If you opt out and they continue spamming you, they can be liable for $50 per message up to $25,000 per day. The short answer... isn't particularly short. California Business & Professions Code § 17538.4 was repealed in 2003. It was split up into a number of pieces. The most interesting are Cal. Bus. & Prof. Code §§ 17529.2 and 17529.8. The former restricts the sending of spam from California or to email addresses in California (along with some restrictions on address harvesting):
The latter provides the remedies:
The problem is, 15 U.S.C. § 7707(b):
That would seem to leave Californians with only § 17529.5:
In short, we got a wimpy solution from the federal government that expressly preempted the laboratory that was being provided by the states. It allowed a bunch of folks in Congress to declare victory, when all we've really seen is a huge increase in the amount of spam. (At work, spam blocked by our very expensive filters currently knocks out around 50% of inbound email. Just a remaining trickle is actual spam after that.) Until we can get widespread technical solutions, whether it's Microsoft's newly less-encumbered Sender ID, Yahoo's DomainKeys, the simpler SPF, or something else that's wandering around, things will continue to be ugly. Now that so much spam originates from the bots lingering around the world, trying to take any legal action against spammers is very, very difficult and expensive. The relatively small number of successful cases, given the huge expense of this problem, seems ample evidence of that. |
|