The catch is that you don't ban a user permanently. The risk is too high that innocent users will get in the way. What if an innocent user does get caught in the cross-fire so to speak? There should be a system that will allow users to request removals. This of course requires abuse checks so spammers won't be able to request they be removed from the system. False positive should be very low, because of the checks implemented.Wo1f wrote:Techie-Micheal wrote:Instead, for bulletin board spam, you want to go after the source. Who is the source? The user. The user can be a bot or a human, or both. A human registers, but the bot spams. But once the human is in, what's to stop them from manually spamming? Here comes the problem again of trying to quantify what a human would do and what a bot would do and what either wouldn't do. What I'm proposing is a service that identifies the user, and not their actions. Or rather, the community identifies the user, and the community bans the user.
But then, how do you propose to reliably enforce a "global" ban on a user permanently, without some form of a "mac-like" UID? What about the risks that an innocent potential new member gets automatically mislabeled (because of a signature)? False positives? I imagine you're also talking about a centrally located repository? What about the impact execution-wise, bandwidth-wise, availability-wise etc?
As for availability, the impact on server and client is very low, and bandwidth use is extremely low. Edit: I decided to go ahead and post the bandwidth stats.
Get ready for it.
A board that has 200 posts per day, and 200 registrations per day will use only 6MB in addition to what they already use with bbProtection installed. That's per month. 6MB per month.