fix obadw check on cmd line, new words

[spider.git] / Changes

diff --git a/Changes b/Changes
index 0c941419066c644cb0cc5562c062da3464437f8e..e2ffceb848368f716d14d2e68c7116f577bd0d21 100644 (file)
--- a/Changes
+++ b/Changes
@@ -1,3 +1,24 @@
+01Dec22=======================================================================
+1. Re-add some debugging to see which incoming PC protcol sentences are
+   being dumped because of any bad content (words or calls) if debugging
+   option 'nologchan' is set.
+2. Any line entered by a user is checked for badwords *before* being sent to
+   the command processing system.
+3. All debugging for badwords has the word 'badword' in it. So that one can
+   do a 'grepdbg -1 badword' and one should see who said it and all of what
+   they said. Watchdbg will also work with this.
+4. My latest recommended additions to the badword list includes:
+   RU STOP SPOT DISGRACE CRM CRIM CRUD SUBHUMAN FASCIST DEGENERATE CATTLE CNT
+23Nov22=======================================================================
+1. The BadWord system has been rewritten. This change is pretty radical and
+   needs to be used with care as a word that is entered will be reduced to the
+   minimum sized string needed to match that word. 
+
+   This is effective a sysop command changeable version of the file badw_regex
+   but in a much more sysop friendly form. The (un)set/badword <word>...
+   commands now update the /spider/local_data/badword.new file in real time
+   without having to mess about with editing files and running load/badword.
+   load/badword still works, but you should now never need it.  
 19Nov22=======================================================================
 1. "Fix" Badword detection in spots and announces etc. 
    NOTE: setting $DXCommandmode::maxbadcount to 0 (default 3) will disable