Editor Question (Score: 1) by evilviper@pipedot.org on 2015-01-04 22:08 (#2WNK) What's your recommendation to editors on using, or not, the "Ban IP" option for spam posts? Here's as good a place as any... Re: Editor Question (Score: 2, Insightful) by zocalo@pipedot.org on 2015-01-05 07:51 (#2WNR) Or the team could be more proactive on the backend. Many of the bots (or low-rent workers in 3rd world sweatshops, it's hard to tell these days) that stuff forums and submission queues seem to follow a fairly standard template so a few well crafted regexp's combined with a tool like Fail2Ban feeding the IP blacklist might nail a lot of the low hanging fruit before anyone even gets to see it. Re: Editor Question (Score: 1) by bryan@pipedot.org on 2015-01-05 08:15 (#2WNS) I've looked into preemptive bans using existing spam databases (see http://www.stopforumspam.com/usage for an example) that use either a REST API call or a DNS lookup. However, with the current spam load I think the reactive approach is sufficient for now. Re: Editor Question (Score: 2, Interesting) by konomi@pipedot.org on 2015-01-05 12:50 (#2WNW) I've always liked this guide: http://www.landauer.at/preventing-spam-in-form-submissions-without-using-a-captcha/ some people hate these methods though specially if they use javascript my answer to that balance might be to only use these anti spam options on unregistered users. The page is none the less an interesting read.
Re: Editor Question (Score: 2, Insightful) by zocalo@pipedot.org on 2015-01-05 07:51 (#2WNR) Or the team could be more proactive on the backend. Many of the bots (or low-rent workers in 3rd world sweatshops, it's hard to tell these days) that stuff forums and submission queues seem to follow a fairly standard template so a few well crafted regexp's combined with a tool like Fail2Ban feeding the IP blacklist might nail a lot of the low hanging fruit before anyone even gets to see it. Re: Editor Question (Score: 1) by bryan@pipedot.org on 2015-01-05 08:15 (#2WNS) I've looked into preemptive bans using existing spam databases (see http://www.stopforumspam.com/usage for an example) that use either a REST API call or a DNS lookup. However, with the current spam load I think the reactive approach is sufficient for now. Re: Editor Question (Score: 2, Interesting) by konomi@pipedot.org on 2015-01-05 12:50 (#2WNW) I've always liked this guide: http://www.landauer.at/preventing-spam-in-form-submissions-without-using-a-captcha/ some people hate these methods though specially if they use javascript my answer to that balance might be to only use these anti spam options on unregistered users. The page is none the less an interesting read.
Re: Editor Question (Score: 1) by bryan@pipedot.org on 2015-01-05 08:15 (#2WNS) I've looked into preemptive bans using existing spam databases (see http://www.stopforumspam.com/usage for an example) that use either a REST API call or a DNS lookup. However, with the current spam load I think the reactive approach is sufficient for now. Re: Editor Question (Score: 2, Interesting) by konomi@pipedot.org on 2015-01-05 12:50 (#2WNW) I've always liked this guide: http://www.landauer.at/preventing-spam-in-form-submissions-without-using-a-captcha/ some people hate these methods though specially if they use javascript my answer to that balance might be to only use these anti spam options on unregistered users. The page is none the less an interesting read.
Re: Editor Question (Score: 2, Interesting) by konomi@pipedot.org on 2015-01-05 12:50 (#2WNW) I've always liked this guide: http://www.landauer.at/preventing-spam-in-form-submissions-without-using-a-captcha/ some people hate these methods though specially if they use javascript my answer to that balance might be to only use these anti spam options on unregistered users. The page is none the less an interesting read.