I’m already getting plenty of spam on a discourse install. Based on experience with running a vB forum with over 100K members, I thought I’d give a few thoughts…
- Current spam control is slightly naive. It doesn’t scale very well when you get into thousands of members. Spammers will often have a whole bunch of accounts, and usually have the time and effort to keep on creating new accounts to spam, even if it’s only once per account.
- A hook to stopforumspam.com and akismet need to be built in by default. They don’t catch everything, but at least they reduce the spam. Its easier to deal with 5 spam posts than 500.
- Spammers originate in a few countries - Vietnam, Pakistan, China, India, Nigeria, Morrocco, etc. That said, it’d be nice to be able to block/moderate/approve posts from specific IP’s. Hell, it’d be nice to just be able to ban an ip address. A more advanced ip blocker would allow you to block an ip address range.
- I’m thinking of building GeoIP into my nginx to just block specific countries. To not be too overly heavy handed, I might just block them from posting – but they’ll be able to view posts. This is much, but I’d rather not deal with spam (sorry china). I’ll post my nginx (or apache) config for this when I get it done. This reduced the spam on my vB forum quite significantly.
- A really good method I’ve found to work is just ‘muting’ the offenders. This way they can post all they want but no one ever sees their posts except the administrator. This prevents them from creating new accounts. No one wants to play the cat-and-mouse game.
- One needs to really engage the community to help with flagging – much of the time though, community members would rather email to complain than click the flag button.
Some of this stuff might already be built in – but I just couldn’t find it.