X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=Changes;h=a776e00dab4268e92361bc0b052101451943dc7a;hb=89ce129e42ed35f87e9f98dfd7d7d6c8297383e0;hp=d242d3014f4f94081df4c04e7b67ae918ac6970a;hpb=647730580f6fe6ad14ee8445f0d5d583390cb130;p=spider.git

diff --git a/Changes b/Changes
index d242d301..a776e00d 100644
--- a/Changes
+++ b/Changes
@@ -1,3 +1,47 @@
+01Nov00=======================================================================
+1. put PC11 field 2 check back to m for pc text.
+2. improve 'simple' callsign checking
+3. Added the first cut of the new user/sysop filtering code. This cut works 
+for spots and the syntax is:-
+
+accept/spots [<call>] [input] [<filterno>] things ..
+reject/spots [<call>] [input] [<filterno>] things ..
+
+where things are: 
+  freq 0/30000 | hf | hf/cw | 6m,4m,2m
+  call G,PA,HB9
+  info iota
+  by G,PA,HB9
+  call_dxcc 61,62
+  call_itu 31
+  call_zone 14,15,16
+  by_dxcc 61,62
+  by_itu 31
+  by_zone 14,15,16
+  origin GB7,MB7
+  channel GB7DJK,GB7BAA
+      
+You can simply string these together on one line one after the other and 
+there is an implied 'and', you can also string together with 'or' 'not' (or
+'!') and '(' and ')' - in otherwords an arbitrary expression.
+              
+You can see what you have done with:
+
+show/filter [<call>]
+
+You can clear your work with:
+
+clear/spots [<call>] [input] [<filterno>|all]
+
+Have fun and someone please write the documentation.
+4. Added show/msg_status.pl sysop command (shows some info on what is busy in 
+the message system)
+31Oct00=======================================================================
+1. add 0x8e to the list of characters we clobber (make xterm go into graphics
+mode).
+30Oct00=======================================================================
+1. put in new Filter::it code and tested it. Now all we have to do is write
+the user access routines (oh and the help files!).
 29Oct00=======================================================================
 1. put in echo cancelling measures into the clients. This doesn't mean you
 shouldn't take steps to prevent echoing on node links, but it may help where