@admin
I just ran into an issue with the spam protection. When I tried to post a text with the words "become too" it raised an error, telling me that the post is suspected to be spam.
>Spam Suspected, possible IP or post match.
I could narrow it down to "come to" to be the trigger. While the latter might be reasonable the former isn't. Could you please change the regular expression that is responsible for this behaviour?

May be it would clarify the error message if it would be more detailed – something like: "Your IP is part of an IP-range that is often used as the source of spam and/or you used a word combination that is often part of spam messages and therefore your post is not accepted." If this is to long to fit in the configuration a short version could help too: "Post not accepted because IP and/or wording triggered spam protection." … or something in between.
If it makes sense to provide the IP or the relevant trigger might be disputable. OTOH the whole regular expression test might be disputable, because it can easily be bypassed. A simple double space (which is automatically shrinked to a single one) or a Zero Width Space (to be more sophisticated) overcome this hurdle.

BTW, The error message starts with a lot of information that may not be intended for the average user:
#0 error() called at [/home/gurochan/web/bin/templates/themes/spamdb/theme.php:37]
#1 SpamDB::build() called at [/home/gurochan/web/bin/templates/themes/spamdb/theme.php:14]
#2 spamdb_build() called at [/home/gurochan/web/bin/inc/functions.php:487]
#3 rebuildTheme() called at [/home/gurochan/web/bin/inc/functions.php:447]
#4 rebuildThemes() called at [/home/gurochan/web/bin/inc/bans.php:214]
#5 Bans::purge() called at [/home/gurochan/web/bin/inc/functions.php:956]
#6 checkBan() called at [/home/gurochan/web/bin/post.php:383]