NSFW Thread Titles - NSFW Language

Willowdared · #1 07-04-09, 03:06 PM

I'm glad we all make an effort to use the caution on threads, but should we do the same with thread titles? Most work filters probably pick up words like cocksucker, so if they show up on the main forum page when people visit it could create issues for users who are trying to visit responsibly.

Terminator · #2 07-04-09, 10:19 PM

Currently the only way to filter this would be for us to ban the use of potential not work safe terms from thread titles (oh, what a headache), or censor the word so it doesn't show up (eg: A**hole).

While I understand your position I don't see us changing how we're doing it, unless we're able to find a way around what we're currently doing that isn't one of the above methods.

If I can find a way to do it, I will.

TXCharlie · #3 07-04-09, 10:38 PM

Just an idea... If you enabled HTTPS on the web server, the network traffic would be encrypted. The only way they could intercept it easily would be to put a "screen scraper" program on the PC's, which they probably don't do.

Registered certificates are expensive, but if you generate your own certificate for https, it will pop up annoying warnings about the certificate being invalid on every page, but it still does provide encryption. Other people could still access the site through unencrypted HTTP, and wouldn't get them warnings.

However, whether people would trust their jobs to the encription or not is doubtful. Also, if they click a hard-coded link, it mayfall out of HTTPS and back to HTTP. It would also slow your site down for everyone, because encrypting the pages takes CPU power, and it's more data to transmit back and forth - but I'm assuming that very few people would actually use HTTPS, because of the annoying warnings that would pop up on every page unless you bought a registered certificate.

Terminator · #4 07-04-09, 10:50 PM

^ Yeah, not an option from where I'm sitting.

**Odd** · #5 07-04-09, 11:07 PM

Not so expensive anymore since GoDaddy gives out SSL certificates like candy, something like 25 bucks a year. If it was just an option used by those avoiding getting flagged at work (or logging in from unsecure locations) rather than the default the server load would be minimal. First question I have though is if people getting flagged for naughty words are allowed a https connection.