I think you are misunderstanding the intention of the spam prevention sticky. It is not meant to be a be-all-end-all whitepaper on the subject (though I do intend to write something of the sort at some point in the future, this is not the time nor the place); instead, it is meant to be a general overview of common techniques and their effectiveness and offer some simple to implement suggestions for forum owners.
Martin Truckenbrodt wrote:DNSBL check - still the only solution this is catching spambots and human spammers very successfully
My own testing (as well as some testing on phpBB.com) indicated that DNSBL-type solutions (notably, SFS) are not particularly effective in preventing this generation of spam. Please feel free to contact me if you've any empirical data that says otherwise.
Martin Truckenbrodt wrote:
- some general words about user registration and user activation
- User Activation - to get the spammers which are not using real email addresses
- Double Activation - to bring the benefits of User Activation and Admin Activation together
Again, you will note that the spam prevention sticky is not
an all-inclusive guide--it is not meant to be. That being said, admin activation is noted within the article as being tedious and ineffective compared to other solutions--this is entirely true. User activation is, admittedly, omitted. I will rectify that in a future version.
Martin Truckenbrodt wrote:some words about guest posting
Again, the intent of the sticky is to provide information on spam prevention
. Other than "Do not turn it on," I don't see what there is to say.
Martin Truckenbrodt wrote:some words about pruning a spammed user database.
While useful, that is very much outside the scope of a spam prevention sticky.
Martin Truckenbrodt wrote:the StopForumSpam and ATLBL using MODs
This is addressed above.
Martin Truckenbrodt wrote:
Although the UTC-12 check could be done in a better way. Maybe there are some very rare people living in the UTC-12 timezone.
Sorry, but for me it's quite funny that the phpBB community is remembering to this feature just then most of the Visual CAPTCHAs have been broken last time.
It's not silly--simply put, at this point in time, it works. It won't permanently, of course, but it works now. What more can one ask for from a solution?
Martin Truckenbrodt wrote:I'm waiting for spammers which are using Q&A databases to hack or to crack the Q&A CAPTCHAs.
At which time, new spam prevention strategies will be formulated, and the post will be updated
Martin Truckenbrodt wrote:Sorry, but for me it has a bad taste
As I indicated, it seems to me that any "bad taste" is entirely the result of a misunderstanding with regard to the entire objective of the article. Simply, it is a quick overview of spam prevention methods; nothing more, nothing less. It is not meant to be a fully exhaustive list--to be frank, I'm not sure anyone would want to spend the time reading such a list if they were simply searching for a solution to a rather annoying problem
That being said, while I do intend to compile such an exhaustive document in the future, I believe that the spam prevention sticky, in its current iteration, does its job quite well--and quite tastefully.