Issue tracker moved to https://gitlab.archlinux.org/archlinux/aurweb/-/issues
FS#17222 - Defend AUR out-of-date notification method from spammers.
Attached to Project:
AUR web interface
Opened by Laszlo Papp (djszapi) - Friday, 20 November 2009, 22:25 GMT
Last edited by Lukas Fleischer (lfleischer) - Thursday, 12 July 2012, 06:00 GMT
Opened by Laszlo Papp (djszapi) - Friday, 20 November 2009, 22:25 GMT
Last edited by Lukas Fleischer (lfleischer) - Thursday, 12 July 2012, 06:00 GMT
|
DetailsI saw yesterday in case of core/extra/community packages that when I'd
like to flag a package as out-of-date, I need for a confirmation, to fill a form. Maybe it would be a good idea for AUR/unsupported packages too (with captcha if possible). Maybe this thread can help: http://mailman.archlinux.org/pipermail/aur-general/2009-October/006764.html |
This task depends upon
Closed by Lukas Fleischer (lfleischer)
Thursday, 12 July 2012, 06:00 GMT
Reason for closing: Won't implement
Additional comments about closing: No need for this. Reopen if this becomes a real issue.
Thursday, 12 July 2012, 06:00 GMT
Reason for closing: Won't implement
Additional comments about closing: No need for this. Reopen if this becomes a real issue.
Captchas or anti-bot measures, or even email validation won't protect from disgruntled user spammers.
So, I'm thinking this is a useless measure.
http://www.archlinux.org/packages/flag/26793/
I think something similar would be useful to reduce the out-of-date spams, a lot of users complaint about it recently, and I don't have better idea than this one that Aaron implemented in the case of official repositories (core/extra/community). It won't protect from the spammers in 100%, but lesser spammers will be I think so, and it's not a bug task to implement for the sake of security/protection.