![]() |
Re: The Automated Profanity Filter
Quote:
|
Re: The Automated Profanity Filter
Quote:
But who would have turned it off in the first place? I thought it's meant to stay on but we have an option to turn it off individually. |
Re: The Automated Profanity Filter
So we'd see $hit?
Code:
echo '$h!t' | sed 's/!/i/' |
Re: The Automated Profanity Filter
:P
Filter blocks s/i/! out too, I couldn't be bothered to change all of it :P |
Re: The Automated Profanity Filter
I think I found what I had read awhile ago that I based my previous statement on...
Quote:
Quote:
|
Re: The Automated Profanity Filter
Quote:
Quote:
Quote:
Quote:
I'm opposed to censorship as well, and perhaps as fervently, as you are. I would agree that you and I probably do not need to be "treated as children" by default; I'm afraid this does not hold true for every member of this community, however. |
Re: The Automated Profanity Filter
Why can't we simply put a nice, small, checkable box in the user profiles...
Code:
Profanity Filter? Y/N |
Re: The Automated Profanity Filter
Quote:
|
Re: The Automated Profanity Filter
He said "***-bang"?
(UNIX pronunciation applied properly is amusing, in a juvenile way. :D) One (troublesome) detail about at-work filtration; client-side censoring won't help with that, unless done in a sufficiently complex and clever fashion. I can see how to do that, but it really ought to be server-side. Which is harder to add, I think. BTW, Reggie; you really need to turn off that filter; you're gonna get more profanity from people cleverly dodging it than you ever would with it off. ;) |
Re: The Automated Profanity Filter
Client side censoring? That would take more work than anything... When the iTT server sends you the page, all it needs to do is see if you're username wants profanity on or off. Then it sends the page processed just as it should be, the profanity never, ever reaches the client, if they so please.
With **** like that, or **** like sh-it. ;) |
All times are GMT. The time now is 15:13. |
vBulletin® Version 3.8.8