Unsatisfactory detection of spam postings (Technics)

by Auge ⌂, Tuesday, December 12, 2017, 09:30 (1935 days ago) @ Micha


I think it would be useful to give moderators access to the blocklists (reading, writing (but not deleting datasets)). That would need a new structure with one row per bad word/IP and (IMHO) an additional column for the user name of the inserting user and (maybe) a datetime field.

Maybe, it will reduce spam but I believe, we should focus on something like honey-pots to reduce spam. A blacklist isn't an effective solution, i.e. ANALysis, AnsPORN, ...

You are right, but (no "yes" without a "but") to insert a honey pot into the registration process doesn't prevent spamming as a non registered visitor.

[edit]Misread your words in the issue. You pointed not only to the registration form but also to the posting form. Sorry[/edit]

I thought about a bayes filter based on this article about it (german language) but the article lost several links including the one to the script sources. :-(

I opened a thread in the SelfHTML-Forum about this issue.

P.S. Do you still review my changes?

Yes, I did (meanwhile). I requested only one further change (set ENGINE=InnoDB into the queries to create the new tables).

Tschö, Auge

Trenne niemals Müll, denn er hat nur eine Silbe!

Complete thread:

 RSS Feed of thread