On 03/05/2016 04:03 AM, Aditya Divekar wrote:
I was mostly basing this idea on the lines that it is easy to put in a spam subscription request to the mailing lists now. Implementing captcha could nip most of these attempts in the bud itself, and save mailman the extra efforts of sending the confirmation link to the subscriber.
Subscription confirmation has nothing to do with spam subscription attempts. It is to prevent me (a human) from subscribing other people's addresses to lists. Captchas and similar hoops to jump through do not stop my doing that and do not obviate the need for confirmation.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Mar 05, 2016, at 10:33 AM, Mark Sapiro wrote:
Subscription confirmation has nothing to do with spam subscription attempts. It is to prevent me (a human) from subscribing other people's addresses to lists. Captchas and similar hoops to jump through do not stop my doing that and do not obviate the need for confirmation.
I'll be honest, I really hate captchas.
Cheers, -Barry
Barry Warsaw writes:
I'll be honest, I really hate captchas.
I do too, and will not work on adding them. But they're a frequent RFE (or were at one time), and with Google oomph behind reCAPTCHA, I wouldn't be surprised if they rise in popularity again. And they don't violate any RFCs.
If Abhilash wants to work on them, let him! As long as it's a boolean option using an external service like reCAPTCHA (if you think set(Google) <= set(NSA) you need not use it), the bug maintenance burden should be low, we can always refuse future RFEs, and if it keeps some people from trying to filter spam or spammer subscriptions in Mailman it might even be a net configuration support win.
IMO the only tough call would be a GSoC proposal, because that probably would force us to refuse another proposal. There I would advocate taking the attitude that we should look at the quality of the students and their likelihoods of future attachment to Mailman, and not discriminate against this particular potential project unless the students really are quite equivalent.
Steve
- Stephen J. Turnbull <stephen@xemacs.org>:
Barry Warsaw writes:
I'll be honest, I really hate captchas.
I do too, and will not work on adding them. But they're a frequent RFE (or were at one time), and with Google oomph behind reCAPTCHA, I wouldn't be surprised if they rise in popularity again. And they don't violate any RFCs.
If Abhilash wants to work on them, let him! As long as it's a boolean option using an external service like reCAPTCHA (if you think set(Google) <= set(NSA) you need not use it), the bug maintenance burden should be low, we can always refuse future RFEs, and if it keeps some people from trying to filter spam or spammer subscriptions in Mailman it might even be a net configuration support win.
Same here. If it's optional, why not?
-- Ralf Hildebrandt Charite Universitätsmedizin Berlin ralf.hildebrandt@charite.de Campus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155
I was thinking of this as a side project to work on, not related to gsoc. And I would be interested in working on this in case it's started as a project :)
participants (5)
-
Aditya Divekar -
Barry Warsaw -
Mark Sapiro -
Ralf Hildebrandt -
Stephen J. Turnbull