so we think we found the issue of why this is effecting dfans over other sites that have it handled after the first big attack. cherubdown was able to make a small change to the spam filter that was not set vs other sites.
Will wait and see how this impacts the results. But should help
the change seems to solve the problem, great, keep up the good work, you're awesome!
there hasnt been another wave yet, so to early to tell, but I have my fingers crossed
so we think we found the issue of why this is effecting dfans over other sites that have it handled after the first big attack. cherubdown was able to make a small change to the spam filter that was not set vs other sites.
Will wait and see how this impacts the results. But should help
for heavens sake's don't deploy one of those terrible capcha systems. some aren't too bad, but others are impossible for even me to get by! heck, maybe even a compromise between what ruksak and the mods are discussing: require users to pass a capcha system for either posting or starting new threads for the first week. That way it doesn't alienate new users that would like to create a new thread and it doesn't annoy long-time users (for long).
Yes, I realize, as thornagol said, you're a bit at the mercy of your platform. But nobody makes progress without some suggestions.
We will never do a normal captcha system. They do not stop bots any more than a good spam system will, no fears there
So Cobalt does allow for role restrictions based on post, and date. However, we try to never use these when at all possible. These have proven to reduce community growth while active. A lot of users sign up to make their first thread asking something. When they cant do this, they get turned off for the most part.
With that said, as bagstone has already stated, our spam filter learns as things are reported, unfortunately, this is the first big korean spam that has hit our sites. This was also not a normal spam bot issue, but a direct attack (as it hit other sites). However the issue has been handled now, and the spam filter should be picking up most of them from here on out.
We also have a another system that is being worked on in our local dev environment that should really help the with the reduction of spam accounts being created, though this wont be deployed out till the new year.
the tl;dr Limiting accounts really does not help, Bots will just post comments instead of threads, and it really does put off new users more than it helps. The better solution is to keep improving the current spam system (which works great on a normal day) to handle big attacks better.
Will wait and see how this impacts the results. But should help
So Cobalt does allow for role restrictions based on post, and date. However, we try to never use these when at all possible. These have proven to reduce community growth while active. A lot of users sign up to make their first thread asking something. When they cant do this, they get turned off for the most part.
With that said, as bagstone has already stated, our spam filter learns as things are reported, unfortunately, this is the first big korean spam that has hit our sites. This was also not a normal spam bot issue, but a direct attack (as it hit other sites). However the issue has been handled now, and the spam filter should be picking up most of them from here on out.
We also have a another system that is being worked on in our local dev environment that should really help the with the reduction of spam accounts being created, though this wont be deployed out till the new year.
the tl;dr Limiting accounts really does not help, Bots will just post comments instead of threads, and it really does put off new users more than it helps. The better solution is to keep improving the current spam system (which works great on a normal day) to handle big attacks better.