Buggy Profanity Filter

Synusoidal Profile Options #1

0

I added a thread recently about the profanity filter and how I believe it should be optional. However, during the beta testing, I've noticed that the filter seems very broken to begin with. Has anyone else been experiencing this?

A lot of times, the filter blocks out words that have absolutely no negative connotations and gives me a message about how my message is against the rules. I remember using the exact sentence "These Hayenas hit hard!", and it was transformed into "These ##### ###!". In other times, I've seen people use the C-word and the F-word, and it's not filtered out.

What gives?

If it's a bug, consider this a bug submission! :P
Ehlynia Profile Options #2

0

Yes.

My wife was talking to her sister who does not like side saddle at all. She said I'm sorry its so ##### ####! for you. When all she typed was 'gamebreaking' as one word by accident.
Synusoidal Profile Options #3

0

Ehlynia on 2012-02-12 01:42:27 UTC
Yes.

My wife was talking to her sister who does not like side saddle at all. She said I'm sorry its so ##### ####! for you. When all she typed was 'gamebreaking' as one word by accident.


Yah, so it's probably just buggy then. I'm going to cross my fingers and hope it's buggy because they're implementing an optional filter.
Markportman Profile Options #4

0

Hard-hitting hyenas are offensive, and should not be discussed.