Re: Re: Front Paging Profanity

[RMGir]

s/as a default option/as an option/;

and then I'll agree to it.

I don't think profanity adds anything to the site, but I'm not interested in reading it through a filter that might inadvertently alter meaning, unless it's something like this :)
--
Mike

[blakem]

a filter that might inadvertently alter meaning

That reminds me of a story I heard about some javascript that mysteriously failed when run from home, even though the code ran just fine from work. It turned out that the childsafe filters installed at home were transforming the javascript variable 'HashItem' into 'Hash**em'. Doh!

Another interesting case is the origin of the "word" medireview

-Blake

[cecil36]

Seeing the Malkovich filter reminded me of one South Park episode where everything was identified as a Marklar.

As for cussing on PM, I don't see it as a major issue because we're more concerned about the topic of the node rather than the words used to write it. However, considering that some monks here are viewing the site from work as a reference tool, I do believe that several of the more obscene words should not be used in node content. It would be a slap in the face for everyone here if a site visitor got fired or received disciplinary action from a supervisor because of a co-worker viewing something here as being offensive.

[Seumas]

If there is an OPTION you can toggle for this, then I'd support it. As long as the option is disabled by default (ie, swearing isn't filtered by default). If it became a hard rule that swearing was filtered out, I would leave.