A Disclosure Policy

So in the limelight of the con that PayPerPost was set out to be, the idea to bring balance to the force was to allow opt-in Disclosure Policies. It comes with a very nice policy generator (a good idea for open source types – here’s what someone needs to implement for allowing people to choose the various OSS licenses!), thats rather easy-to-use.

At Step 3 of 6, I did find it a bit odd. “The owner(s) of this blog will never receive compensation in any way from this blog.” Now, how can this be true? This is an option that can never exist, because the moment you start writing quality content, your blog or website starts generating interest, and you’re adding towards your Google Resume. Invariably, you will receive compensation, indirectly even, based on what you come up with.

Step 5 of 6. Wow, conflicts of interest. Of course this blog contains that – someone pays my crust, so there’s no telling why I won’t be writing about working there. But in the open source world, my conflicts of interest also lie in the projects that I favor. Which again, brings me back to the question: how do blogs not contain a conflict of interest? You’re bound to want to write about something that interests you. I do find the 4th option rather interesting, but very tedious to fill out.

Alas, I too now have a disclosure policy. And I apparently just made a menial sum for reviewing this. And I wish it would work, but opt-in items fairly do. Here’s hoping to keep the Web honest… it used to be back in the day (now, I sound ancient).

Technorati Tags: ,


i