| |
In lugnet.announce, Willy Tschager wrote:
> > If you do not ask for a cancel, it is our view that you are in violation
> > of the LUGNET terms of use. It is your choice whether to be in violation or
> > not, because LUGNET does not censor,
I guess I'd probably change the phrasing Larry used here-- Posting profanity IS
a violation of the TOU, no if's about it. This speaks it better:
> > but if you choose to remain in violation,
No two ways about it, you're already in violation. Question is whether or not
you want to make amends by asking to cancel your post. Kinda like a traffic
ticket. You can choose not to pay it, but there's consequences.
Really, I like Dave K's proposal-- by default, detected swears are auto-stripped
and replaced with something else. And members may or may not have the ability to
actually flip off the filter (Ok, I didn't intend the pun initially, but I like
it).
I think in the past the argument was that it was impossible to catch
*everything* since some things are egregiously offensive without even containing
"swear words", and there's more than one way to spell out profanity other than
using the specific letters (ASCII art, interspersed characters, improper but
similar charaters, etc).
But regardless, I think it would probably be a Good Thing, just to catch what it
can (which would probably be the majority of it).
Another option is to have auto-detecting *before* you post something. Hence (for
the sake of less CPU usage), you'd only be adding time when the post was being
added. Effectively, you'd change the post authentication page (or web form) to
alert you to the fact that you were about to post material that is in violation
of the TOS, and gives you a chance to correct it before submitting. That could
also be an easy way to have it alert admins to anyone who went ahead and
submitted profanity anyway, regardless of the warning.
Hm, perhaps the default option would even be to replace your post contents?
Something like:
> Your post appears to contain inappropriate language disallowed by the LUGNET
> TOU. The LUGNET system has autocorrected your text:
>
> > a library with almost 3000 files gives you plenty room for errors (being
> > the maintainer of the mlcad.ini file containing only mini###### parts I know
> > exactly what I'm talkin' about ;-)
>
> [x] Post corrected version
> [ ] Post original version
> [Submit]
DaveE
|
|
Message has 1 Reply:
 | | Re: Bye, bye LUGNET
|
| (...) I was thinking about the 'various ways' that people could get around the built-in filter (if there was one). Then I started thinking that if the filter turns specific words into #%##$, and people know that, so they type S P A C E D words to (...) (20 years ago, 1-Mar-05, to lugnet.general)
|
Message is in Reply To:
29 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
