[pmwiki-users] Note: blocklist2 word specifications

[Crisses]

On Apr 1, 2006, at 7:08 PM, H. Fox wrote:

>> But there is no way to override locally and allow things that are
>> blocked in the Site.Blocklist is there? In other words if
>> Site.Blocklist blocks 'xxxyyy' then there is no way to allow that  
>> in a
>> field?
>
> Not that I know of.  Maybe there should be a Site.Unblocklist.  :-)

Put a space after "anal" and it will honor it.  It won't work for  
everything, but it will stop "analysis" from being blocked.

"unblock" would be nice, but I worked based on the blocklist.  the  
word speCIALISt is a problem too.  Once I added the drug names to my  
blocklist, I found out how DELIBERATELY clever the pharmaceutical  
industry is.

And now I've ensured my list email won't make it past SpamAssassin &  
etc. ;)

>> Also, is there some way to specify only a complete word block... for
>> instance, block "anal" but not "analysis" (as an example)?
>
> The current script is overzealous about matching.  An update / rewrite
> has been discussed.


 From what I've seen in response to the RFC's, PM is probably moving  
it into the core distribution as an optional plug-in/script.  I would  
be very happy to help out.  I've been reading through the recent  
commentary (oh, only about 4000 messages behind in my list  
reading :P ) , and I suppose I never adequately documented that I  
added in support for whitespace characters into the script.

		"When activated, blocklist.php scans the Main.Blocklist (now  
Site.Blocklist) page looking for strings of the form block:something  
where something is a sequence of characters (including spaces to end- 
of-line) to be excluded from posting."

The spaces were added in because there was one clever guy who kept  
posting "no spam" and wiping out pages on the wiki...so I had to  
support phrases  -- "no spam" is a valid "block:" item.  Maybe I  
should have added in an end-of-word character, but frankly my  
blocklists take up quite enough processing power on my dinky  
webservers :)  Blocking drug names and web domains, with a few IPs  
for the more persistent and creative repeat offenders seemed to have  
been enough.

Any improvements to the processing logic behind-the-scenes would be  
greatly appreciated.

I'm also sorry that the $EnableWhyBlocked broke.  I have not been  
monitoring PmWiki list emails -- and I feel bad that no one contacted  
me.  Life has been hectic.  I'll work on those improvements, and  
maybe the regex support request.

Crisses