> > Hi!
> >
> > Just did a process of pending comments. Things are definitely
> getting
> > worse and worse - I'd say we're now far below a 1:50 rate of
> comments
> > vs spam. We need to do something. We've previously tacked
> captcha. I
> > would like to propose something that's a lot easier - let's
> require a
> > "community login" to submit a comment (same thing you'd need to
> > submit/edit pages on techdocs). The only question is will this
> raise
> > the bar so far we don't get *any* comments anymore, or will it
> raise
> > it just enough so we get rid of the spam? I'd be willing to give
> it a
> > try at least. Implementing it should be trivial, since the login
> > system is made as a module on the site designed to plug in
> wherever
> > needed.
> >
> > Thoughts on this? Should we give it a shot?
>
> Agreed, we need to do something, and in lieu of a better idea a
> community login seems like a good idea.
Ok. Unless someone objects, I'll go ahead and put something together.
> What worries me more is the amount of load the server is handling
> because of this garbage - if the system is working as planned,
> we're not even seeing much of the spam because the regexp filters
> will be rejecting it. Each one still requires php and postgresql
> resources to be processed though.
Right. Load is likely to decrease because of this, though, since we'll
be dropping connections much faster (generally, once the spammers get
the 401 they will get because they haven't tried to log in, they will
give up. Before we even hit the database.). Even if we do hit the
database with an attempted login, things will be dropped after a simple
equality test instead of having to process a whole bunch of regexps.
//Magnus