splogplosion

Since the
last sploglosion event
also diluted peoples ego searches there is finally some discussion about Google’s ignorance towards this problem: Chris Pirillo demands that Blogger be fixed or turned off I can imagine that it’s harder for him to execute the P(i)rillo Effect.

Sidenote: when will stop the habit of leavng characters out and feel cool about it? (splogplosion -> spam world wide web log exploison)

And, of course, Icerocket suffers as well.

The problem is not new: seven months ago I had to turn of Blogger in BlogsNow. All future rewrites of BlogsNow knew not to trust blogger content. BlogsNow crawls Blogger as much as possible. But not more. That’s why BlogsNow wasn’t hit by the latest boom of junk on Google’s blogging tool. It does help to have very little resources: With BlogsNow I have simply neither room nor bandwidth for spam. Spam would have killed BlogsNow within days, if it wouldn’t be able to defend itself.

Over at Jeff Jarvis there is some discussion as well on the very same topic. Sreven Den Beste comments along the lines that splogs on blogger.com might be beneficial to google. They definitely are. Wether intended or not: Google knows which blogs on blogger get read and which ones not. That alone makes for huge head start for all search efforts.

The concept behind those splogs is threatening not only a few ego searches on PubSub: The internet didn’t work to sell dog food (web/bubble 1.0). Now the internet is trying to sell information (web/bubble 2.0). While this approach is much more promising, all that spam is diluting. And it hurts innovation: Much of BlogsNow constant rewrites go into the upkeep of the status quo against splogs and other malicious symptoms. I would rather add features. And I would rather be able to trust the information out there.

It’s the same with all spam: In order for somebody to make 1 cent somewhere there are damages of hundreds of dollars elsewhere.

Leave a Reply