On Tue, 18 Sep 2001 19:12, you wrote:
> Es schrieb Joe Menola:
>> I would suggest that the mailing list folks bounce messages containg foul
>> language.
> (here only one example: dump american search
> engines are filtering the pattern "sex" => the country of Sussex, Englend
> can't be found) ...
And Queensland need a new name for their beer, since XXXX (that's how you
write Fourex, for details see The Last Continent by Terry Pratchett) contains
xxx.
> And even worde: Some of us might "read" mails by such a preson by pressing
> the delete button, when they write further mails ...
Or better still, a /dev/null filter. But always the choice to do so or not do
so should be the reciever's.
What happens on the day that Mandrake gets a package that inadvertently
includes an obscenity in its name? The name debugger-0.1-69mdk.noarch.rpm
looks obscene, doesn't it? No? Capitalise letters 3 through 8 and try again.
Goodbye, list traffic?
Woe betide that sysadmin who adds filtering to their proxy. Proxy prohibits
fetching ISO because it contains bad words? Ugh.
I teach my 11yo daughter to detest language that is basically detestable. She
avoids it far more efficiently than a filter could, and comes quickly for
help when an inadvertant porn site ties down her browser and she can't close
it (she likes animals, and it seems that cats in particular have become
associated with illicit affection). If I don't do this, no filter will keep
her from it always and forever, will it?
So, two arguments against it: it's very expensive in many ways, and it
doesn't work anyway.
