Re: Content filtering

["Ryan Russell" <ryanr () sybase com>]

No, it would be terribly useful.  There are a large number of
institutions who could write a one-line access list to block
the port number in question, but won't neccessarily install
an HTTP to parse and filter HTML.  I've got a high school
I help out with networking stuff, and they would LOVE to
be able to block one port and eliminate all the porn.

Of course, all the porn sites are as likely to all go out
and change what port they run on as they are to label
their content.

                    Ryan



----------------------------------
Ahem.

There is already a standard for marking pages as having "objectionable
content" (see the W3C web site for details), and if browser makers and
others wanted to use it, they could.

Wasting another port on this seems less than useful in that light.