From: "LpSolit at netscape dot net" <gcc-bugzilla@gcc.gnu.org>
To: overseers@gcc.gnu.org
Subject: [Bug web/72856] Trottle bug creation for newly created accounts (to limit spam)
Date: Wed, 10 Aug 2016 12:33:00 -0000 [thread overview]
Message-ID: <bug-72856-5127-4hbQjcO3bW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-72856-5127@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72856
--- Comment #5 from Frédéric Buclin <LpSolit at netscape dot net> ---
(In reply to Gerald Pfeifer from comment #2)
> As for rate throttling, how about only allowing for a single bug
> report per day until a bug report has been "processed"
Isn't one bug per day a bit rude for legit users? I would be tempted to say
that above 2 or 3 new bug reports, it's reasonable to question if the user is
trying to spam Bugzilla or not. This is why I made the proposal in comment 0 to
use something exponential. This would give us something like:
3**n-1 5**n
====== ====
T0 : account created T0 : account created
T0 : 1st bug created T0+1min : 1st bug created
T0+2min : 2nd bug created T0+6min : 2nd bug created
T0+10min: 3rd bug created T0+31min: 3rd bug created
T0+36min: 4th bug created T0+2.5h : 4th bug created
T0+2h : 5th bug created T0+13h : 5th bug created
T0+6h : 6th bug created T0+65h : 6th bug created
T0+18h : 7th bug created etc...
T0+55h : 8th bug created
etc...
So a spammer could file at most 6-8 bugs in a week, but a legit user could
still easily file his first 2-3 bugs in a half hour. Of course, this rate limit
would only apply to users without editbugs privileges, so e.g. @gcc.gnu.org
accounts would not be affected.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-08-10 12:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 2:43 [Bug web/72856] New: " LpSolit at netscape dot net
2016-08-10 2:44 ` [Bug web/72856] " LpSolit at netscape dot net
2016-08-10 5:50 ` trippels at gcc dot gnu.org
2016-08-10 8:33 ` gerald at pfeifer dot com
2016-08-10 11:46 ` manu at gcc dot gnu.org
2016-08-10 12:04 ` LpSolit at netscape dot net
2016-08-10 12:33 ` LpSolit at netscape dot net [this message]
2016-08-10 12:41 ` fche at redhat dot com
2016-08-11 11:58 ` joseph at codesourcery dot com
2016-08-15 19:57 ` redi at gcc dot gnu.org
2016-08-16 14:41 ` LpSolit at netscape dot net
2016-08-22 20:10 ` bernd.edlinger at hotmail dot de
2016-08-23 6:07 ` [Bug web/72856] Throttle " gerald at pfeifer dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-72856-5127-4hbQjcO3bW@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=overseers@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).