The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#8
|
||||
|
||||
![]()
Hi Michael,
I couldn't get hold of you on MSN Messenger so I've penned down some thoughts/questions here: New code I like the style, comments and fact that it's been called from PHPINCLUDE_START good work ![]() Blacklists What do you think the best way of storing the blacklist(s) and making it editable is? I wonder if a phrase would be a good plan (even if it was managed through a custom part of the admincp rather than the phrase manager). If we wanted to store them as files and be able to write to them via the web interface the files would have to be world or web user writable. It'd be easy to setup a scheduled task to drag down the latest copy of the MT blacklist. Multiple fields What are your thoughts on breaking down the fields passed into the "spam engine"? I'm thinking along the lines of the way that the second version of spamBuster was able to have rules relating to the body text or the subject. Username might be anoter field worth matching against - lots of spammers seem to use the recipe [username][number] like robby34. Perhaps something to worry about later. Are you happy with me going ahead and writing a lower level library that does the spam processing and leaving some of the vBulletin integration (admincp code) to you? Made some changes to the code in the file handling and character substitution PHP Code:
The comments should be replaced out using preg_replace() The main regular expression tests are done using preg_match() which I think in a lot of cases is faster than eregi() Looking at those changes who'd guess I've developed in Perl a fair bit? :ermm: I've not tested this code the line I'm most dubious about is the comment removing code. |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|