I don't think the level of security your are describing should be
at the document level. HTML is an SGML DTD, so there should be no
display/security/editorial definition there. You might have to have a
"filter file"( similar to the UNIX 'filter' file for mail ) to do this.
That way you catch the incoming packet before it even reaches the
>I believe such a feature would have the following benefits.
> 1) Minimal HTML document modification by adult sites. (Only 1
> 2) No modifications to HTTP servers.
> 3) Minimal modifications to existing web browsers.
> 4) Still allowing freedom of speech across the net.
Yet, invariably, it's dependent on who has the password control. It's
not freedom of speech in that manner if I'm not allowed to hear what
your saying, even though you can speak it!
> 5) Providing a secure method for parents to control what
This can also be provided by watching what sites your kids access,
or warning them in the first place NOT to access particular sites. But
that's for a different group... :>
>I welcome your comments to this suggestion, as well as advise on how
>propose this to the WWW community as a whole.
A interesting idea, even if I don't agree with it.
| Scott Bell - Systems Analyst | Nothing happens unless
| Sec. of State/IS Div. | first a dream.
| email@example.com | - Carl Sandberg
| "I speak for myself and no one else" - #include disclaimer.h
| Cbr600f2VolleyballGuitarsMy familyComputersEverything else