Are you one of those trigger-bloggers? You know, you see something on some web site you think is wrong, or you just don’t like, and you post! post! post! as fast as you can, pointing out the errors of someone else’s way…

The latest I’ve seen is the bit about the podsafe music network and the crazy licensing terms brought up by Boing Boing. Now, Adam Curry responded about the changes they made, and this is good, he says:

This is a great example of how the web works; it started with a post on Boing Boing and was followed by a host of pile-jumpers. Although a personal email would have been preferred, it certainly got my attention.

All good, yes indeed, this is how it should work. I think the problem between public finger-pointing via weblogs and private-griping via email is that you leverage the power of the people when you create a post that others can read and point to and amplify. I’ll write up and send an email because I still have my own feedback on the terms, but there’s a chance it will fall into a black hole and I will never get a response.

Now, I’m not saying we don’t need trigger-bloggers, it helps to keep us all honest and on the level with each other, but weigh the options. Sure, everyone wants an email first but everyone also enjoys a good show…

Most importantly, if you do pull the trigger on someone, and they change their ways because of it, please mention the enlightenment you bestowed upon them and the resulting good times that followed. As of my writing this, I still await the post on Boing Boing mentioning the changes PodShow made.

2 Responses to “Trigger-Bloggers”

  1. The other problem with keeping everything hidden is that nobody learns anything around the edges. Remember a while back, when suddenly the Bobby accessiblity checker’s report pages were coming up higher in Google results than lots of people’s weblogs? I sent them an email explaining how their robots.txt was broken (as I remember it, they were trying to wildcard after a cgi, so that instead of saying “Disallow: check.cgi” which would disallow any URL starting with check.cgi they had “Disallow: check.cgi?*” that only disallowed that exact string), and they fixed it, without me jumping up and down in public, but also without anyone who might have happened to read my jumping up and down saying “oh, crap, I didn’t realize the robots.txt spec didn’t allow wildcards, I’ve got a broken one myself.”

  2. Phil, you are my hero. Keep up the good work.

« | »

buy the button:

Buy The Button