Receiving censor

[spider_desu]

I noticed that the censor proxy will censor messages as they are sent, and not as they are received. This causes words to appear censored in the logs and it means that people who do not have the censor proxy enabled will still see only *'s when someone with the proxy enabled posts a message.

Is there a way to change this so that things are censored on the receiver's end? This way people can enable or disable the viewing of explicit messages depending on whether or not they wish to read that stuff. Also, it gives a much more accurate chat log, rather than one filled with *'s which could be god knows what.

[spider_desu]

Also, at the same time, can the censor be set to replace one word with another rather than spell the word with *'s? I have phpBB set up and it censors by word replacement and I wish to use the same word replacement list (example: "fuck" become "engage with", "ass" becomes "donkey",...)

[OldWolf]

The overall answer is no, these features do not presently exist, and it's likely they will not be added any time soon. Your welcome to code them yourself and submit them as patches though.

As a suggestion, you could try modifying the existing proxy to work as a post proxie, no idea how difficult this would be though.

[spider_desu]

The overall answer is no, these features do not presently exist, and it's likely they will not be added any time soon. Your welcome to code them yourself and submit them as patches though.

As a suggestion, you could try modifying the existing proxy to work as a post proxie, no idea how difficult this would be though.

From the description on the phpFreeChat website it sounded like post proxies were just processed after the default proxies, but not processed on the receiving end. Or is all receiving done by simply checking the log (which is one of the default proxies)? I'm not quite sure how to code it since I'm not too sure on just how the chat works. I realize that every XXX seconds it pings the chat script, but I don't understand how and from where it gets the data of what has or has not been seen yet.

I'll make the censor a post proxy (if not too difficult) and see what effect that has. As for making it word replacement instead of turning it into stars, I'm sure that won't be too hard to code. I just figured it was worth asking if it had already been done so long as I was asking about the other question.

[OldWolf]

You can't execute php code on the user end... php is server side script. You could write a javascript bit that executes on the users end... but my point was that you could try it as a post proxie to save yourself time.

[spider_desu]

I think my request was misunderstood...

I'm aware that PHP is server-side, but I was suggesting something like the following:

1. CLIENT - User1 makes a post (javascript calls chat.php with post data)
2. SERVER - chat.php records the post in its temporary log
3. CLIENT - User2 pings chat.php (which happens every XX seconds - javascript)
4. SERVER - chat.php reads the temporary log and sees there is new data
<-- insert proxy here
5. SERVER - chat.php sends User2 the new data
6. CLIENT - User2 displays the new post (javascript)

When I say I want it on the "receiving end", I mean I want it filtered after it goes into the temporary post cache (and after User1 has posted it), but before the data is sent to User2. This way, suppose that User3 has his chat filter disabled. The temporary cache stores the messages uncensored, so User3 will see the uncensored version even though User2 has his censored before he receives it.

[OldWolf]

Ah, I see what you're saying. Yea, the only way you are going to achieve that is through your own code unfortunately.

[spider_desu]

Sadness... Could you perhaps explain the process by which it fetches new posts whenever the javascript pings the chat server? That might make it a lot easier for me to code such a proxy. I'm not quite sure where the code is coming from or going to as it is. It would save me a lot of time if I could have that basic premise explained rather than have to read through it and figure out how it works.

[OldWolf]

Unfortunately, I don't know the intimate details of the chat either... I'm not the author of the chat, so I'm not sure how he went about doing it.