To be honest, *if* the purpose of the label was only to ensure that browser plugins for content filtering (i.e., Net Nanny) worked reliably to filter out porn, I wouldn't object.

The problem is, as soon as you have something that all adult sites use, the next thing is certain ISPs or cities or whatever will start blocking traffic at the root level, and that does run into free speech issues.

I can remember about a year ago, we discovered that none of our sites were in NetNanny's database. We used the form to submit to have our sites added to the database... but the form was broken. So we emailed customer service. After about 5 days, we got an email back from some brainless person in their email response center telling me how to submit using their form. Several rounds of email exchange between the worthless response center people and I yielded nothing.

It was only after I sent several emails to management people whose addresses I was able to uncover, saying that my next call was to 60 minutes and several other high-profile consumer protection groups, that I got an email from someone that the form had been fixed and our sites added to the database.

It's amazing to me how quick people are to blame the adult industry when half the time we would happily work within the existing framework... but for reasons such as the above, the existing framework is seriously flawed.