Remember how LiveJournal, TypePad, and related sites were down the other day? The official line was that “Six Apart has been the victim of a sophisticated distributed denial of service attack.”

It turns out that the DDOS wasn’t aimed at 6A, LJ, or any other part of their network. It was aimed at Blue Security, an anti-spam company, who decided to re-route their web traffic to their blog—a blog hosted on TypePad. So instead of their own site going down, it took out Six Apart’s entire network of millions of bloggers.

Classy move, guys.

I do admire Six Apart’s restraint in not pointing fingers themselves. If it had been my site (though in a way, I suppose it was, since I’ve got an LJ blog, even if I don’t update it very often), I would have been royally pissed off.

Sure, Blue Security didn’t launch the attack—but they did choose where to redirect it. Maybe they thought Six Apart would be able to handle it. Maybe they thought the attackers were targeting them by IP and not domain name. Maybe they were panicked and didn’t think. Maybe they thought things through, but 6A got bitten by the now-all-too-familiar law of unintended consequences. They could easily have pointed their domain name at empty IP space, or to localhost. Redirecting it to a third party was less like deflecting a punch and more like the “Do it to Julia!” moment in 1984, or the classic joke, “I don’t have to outrun the bear, I only have to outrun you.”

(via Spamroll)

Update: Additional articles at Computer Business Review and at Netcraft, and a Slashdot story.

Update 2: According to Blue Security, the DDoS was not targeting their website by name, and the DDoS didn’t attack their blog until after they had already redirected the website. So it looks like it was less a case of them redirecting the attack and more a case of the attackers chasing them.

*Sigh* Must remember to collect all facts before engaging in righteous anger.

Update 3 (May 9): Apparently “all the facts” as reported by Blue Security don’t add up… (via Happy Software Prole)

Molly Holzschlag writes about the Accidental Blogger Effect—what happens when you post something offhand that somehow ends up as a prime search result, leading to that offhand remark taking on a life of its own. I made a comment about how Another One Bites the Dust turned into a 3-year-long thread about Frosty, Heidi and Frank, but it occurs to me that the often-viewed Fallen Angel cover art I posted about last week is the same phenomenon.

It’s hard to believe, but it’s been three years since the first post on this blog. I still think of myself as being kind of new at this, but at this rate, we’ll be in the old guard. Or at least the new old guard. 😉

Topics have shifted around. It started out as a personal blog with Sci-Fi overtones, and slowly took on more of a focus on humor, comics and tech. Posts in the early days were divided 60/40 between me and Katie. These days it’s more 90/10, partly because we’ve both shifted a lot of the personal stuff over to LiveJournal. Strange photos started showing up very early on, making up what are now the Strange World, You Must Be Mistaken, and Signs of the Times categories.

The site started on B2 and moved to WordPress when the project forked.

Even the title is subtly different. It started out as “Ramblings,” with a “K²” icon to the left. After a while, the icon became part of the title, and it’s been known as “K-Squared Ramblings” for most of those three years.

According to the WordPress Dashboard, we now have 912 posts and 961 comments Continue reading

It seems like everything I sign up for these days has a blog attached to it. Slashdot has a journal feature that I’ve never used. K-Squared Ramblings is approaching its third anniversary. I signed up with LiveJournal just to read friends’ journals and ended up with a blog there. Spread Firefox gave me a blog. My Opera gave me a blog. I signed up for info about WordPress.com (reserving a username just in case), and it turns out to be — you guessed it — a hosting service for blogs!

The way things are going, I seriously expect Amazon.com to offer me a blog the next time I order a book.

Making the rounds this week: IO Error’s critique of “nofollow”, the link add-on that was supposed to stop comment spam, but hasn’t even slowed it down. He suggests that it was never intended to: it was simply a sneaky way to lower blogs’ rankings in search engines.

Now, I don’t have a problem with the idea of being able to tack a note onto a link and tell Google not to treat it as an endorsement. But the way it’s been implemented in most blog software—blindly applying it to all links in comments—is overkill. Legitimate, useful, interesting comments should factor into the resource’s ranking, for all the reasons IO Error provides.

Where rel="nofollow" does help with comments is in devaluing the spam that slips through your filters overnight. If a search engine bot happens to crawl your page between the time the comment hits and the time you see it and remove it, nofollow will at least make the spam less effective. Of course, you only need it active for a day or two (depending on how often you check). Once you’ve cleaned the junk out, you want what’s left to get the rank boost it deserves. I’ve been using the No Nofollow plugin to do this since March.

In short, I don’t think that rel="nofollow" is a bad idea in itself. It’s just being used the wrong way.