Forbidden words in the chat?

[Qem]

I've implemented a freephpchat and I'm really loving it.

The problem is we've found that there are a number of words that seem to be forbidden as part of a sentence, unless we type them in caps - and I was wondering if there is a way to work out what those words were so we know to avoid them? Or if there is a work around to enable them, besides typing it in caps or a letter in caps.

kill, php, rsh (discovered with harsh), and.... almost certainly others.

[Alky]

which version of PFC are you using? In my 1.6 installation I've never had any trouble posting any of those character sequences. Just did a test to double make sure, and yeah it posts them without issue.

[Qem]

That's weird. (It's a paid for host as well, not a free one.)

I use php 1.6 - it's not the individual words, but if they are used as part of a sentence it won't work:

It's definitely not the params I'm using - every single chat room, in the demos also experiences the same issues. And while I have a lot of custom commands set up for my chatroom, we noticed the php as a forbidden word fairly early on.


Examples from the demo 2 debug

you can see with the examples, Harsh worked, but "that's totally harsh man", although it recognised it was typed there's no handle response. That's why I thought it was some sort of default behavior.

Code: Select all

handleResponse: getnewmsg-ok-[['7', '19/05/2013', '17:54:53', 'guest', '1ddda23671eca3741943c437fda28047', 'send', 'no response', 1, 0]]
handleResponse: send-ok-
sendRequest: /send no response
sendRequest: /send we kill the casplock
handleResponse: getnewmsg-ok-[['6', '19/05/2013', '17:53:54', 'guest', '1ddda23671eca3741943c437fda28047', 'send', 'we killed the capslock', 1, 0]]
handleResponse: send-ok-
sendRequest: /send we killed the capslock
handleResponse: getnewmsg-ok-[['5', '19/05/2013', '17:53:42', 'guest', '1ddda23671eca3741943c437fda28047', 'send', 'This looks like a job for casplock, don\'t haRsh on my caslock', 1, 0]]
handleResponse: send-ok-
sendRequest: /send This looks like a job for casplock, don't haRsh on my caslock
sendRequest: /send but php in a sentance doesn't work
handleResponse: getnewmsg-ok-[['4', '19/05/2013', '17:50:51', 'guest', '1ddda23671eca3741943c437fda28047', 'send', 'php', 1, 0]]
handleResponse: send-ok-
sendRequest: /send php
sendRequest: /send that's totally harsh man
handleResponse: getnewmsg-ok-[['3', '19/05/2013', '17:50:40', 'guest', '1ddda23671eca3741943c437fda28047', 'send', 'harsh', 1, 0]]
handleResponse: send-ok-
sendRequest: /send harsh
sendRequest: /send hell okill file
handleResponse: getnewmsg-ok-[['2', '19/05/2013', '17:50:22', 'guest', '1ddda23671eca3741943c437fda28047', 'send', 'kill', 1, 0]]
handleResponse: send-ok-
sendRequest: /send kill
handleResponse: getnewmsg-ok-[['1', '19/05/2013', '17:50:21', 'guest', '1ddda23671eca3741943c437fda28047', 'send', 'hello', 1, 0]]
handleResponse: send-ok-
handleResponse: whois2-ok-# <Hash:{'isadmin': '', 'floodtime': '1369011010', 'flood_nbmsg': '1', 'flood_nbchar': '19', 'nick': 'guest', 'nickid': '622845ac38f14bf9af493ebd1e2353faf5b102e1'}>
sendRequest: /send hello
sendRequest: /send hello kill file
handleResponse: who2-ok-# <Hash:{'chan': 'ch_My room', 'chanid': '1ddda23671eca3741943c437fda28047', 'meta': # <Hash:{'users': # <Hash:{'nick': ['guest'], 'nickid': ['622845ac38f14bf9af493ebd1e2353faf5b102e1']}>}>}>
handleResponse: connect-ok-guest
handleResponse: join-ok-['1ddda23671eca3741943c437fda28047', 'My room']
handleResponse: nick-connected-guest
sendRequest: /connect "guest"
sendRequest: /send ok
sendRequest: /send test

So the resulting text displayed is:

‹guest› hello
‹guest› kill
‹guest› harsh
‹guest› php
‹guest› This looks like a job for casplock, don't haRsh on my caslock
‹guest› we killed the capslock
‹guest› no response

But I typed:

hello kill file
hello
kill
hell okill file
harsh
that's totally harsh man
php
but php in a sentance doesn't work
This looks like a job for casplock, don't haRsh on my caslock
we killed the capslock
we kill the casplock
no response

[Alky]

file or database container thingie?

I have never had a problem with those character strings and yeah I tested them in a "sentence". Just thought now that maybe it's got something to do with your container type ... possibly a way to protect a database by knocking out certain words that a malicious chap might use against a dbase?

I've only used the file type containers thingie.