The <nsfw> Element
html5doctor.com
html5doctor.com
YES, I've been thinking about this kind of thing for a while. But <nsfw> doesn't seem like enough.
What if an entire page or website is nsfw? Maybe some kind of header information would be more appropriate. Or inside the root element (<html nsfw>). How about specific ratings? <nsfw rated:"urn:mpaa:R">
There are still plenty of problems--kids getting around the browser settings--but it's 10x stronger[citation needed] than "what's your birth date?".
Why not just let the kids look at the damn porn?
If they can't see boobs on the Internet, then they are going to see them in a context that results in the creation of children. It's almost like we're programmed to reproduce, or something...
I work in a rather open office environment now. Our management has no problem if employees blow off some steam by surfing to a site that might not be work related as long as its not excessive (just like they don't punish people for going to the break room to get a candy bar from a machine, or going outside to smoke).
However, click the wrong link and end up with porn (or something otherwise seriously inappropriate for a typical work environment) and you get noticed very, very quickly.
Define porn.
Travel to another country.
Define porn.
In the US, periodicals don't post pictures of naked men/women (at least not the defined "naughty bits"). The ones that do are considered pornographic and require the purchaser to be a certain age.
In Europe, nude women in periodicals is not unusual.
In Muslim countries ... well, if you can figure all of the nuances of the most restrictive Muslim countries, I owe you a beer.
Moving depictions of sex off into a .xxx domain would not be very hard. Just because something isn't perfect, doesn't mean it's not a good idea.
(Not for potential censoring so much as avoiding potential workplace problems)