On Monday, 23 May 2016 at 17:56:17 UTC, cy wrote:
[...]
I've filled out one of these for every post I've made here. Yet
I'm logged in, with a persistent state on the server side.
Could something be implemented along the lines of:
ALTER TABLE users ADD COLUMN num_captchas_solved INTEGER
DEFAULT 0 NOT NULL ETC;
I can understand if even an ordinary user like myself could be
suspected of spam. The Internet doesn't make it easy to
distinguish in a lot of cases. But my account login status
does. If you made it so someone solving 12 captchas didn't get
asked any more (until they actually start sending spam), that'd
be really nice.
You could even award achievements! (Achievement unlocked: On
Fire. 100 posts in a week? Jeezus!)
Not sure if this is the right place to ask, but this is
regarding the posting server on forums.dlang.org, which I use
to access all these mailing lists and such, without getting all
the messages in all the lists sent to my email inbox.
One thing that could be done is to disable the spam checker when
the user is registered. As a counter part registering must be
very strong: image capcha + text capcha + guess the code result +
?
