public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Andrew Pinski <pinskia@gmail.com>,
	Joel Brobecker <brobecker@adacore.com>,
	Simon Marchi <simon.marchi@polymtl.ca>,
	Pedro Alves <pedro@palves.net>
Subject: Re: getting spammed on bugzilla
Date: Fri, 12 Nov 2021 09:55:26 +0100	[thread overview]
Message-ID: <YY4r/kPvrr20RsZV@wildebeest.org> (raw)
In-Reply-To: <YY3wQQQ/R/th3Dki@adacore.com>

Hi,

On Fri, Nov 12, 2021 at 08:40:33AM +0400, Joel Brobecker via Overseers wrote:
> My thinking on this is that we should try doing the same for
> sourceware's bugzilla, and see how it goes. I'm hoping the extra
> step will be a high enough barrier that it'll encourage the majority
> of spammers to find somewhere else to go. Even if not perfect, if
> we can block the majority of spam, that'll already be a great win
> for us.

I don't like it, but I don't see another solution.  I did tweak the
spam filters to count http[s]:// and reject any comments containing
10+ urls. That seems to have worked a little. But soon after we saw
even more spam comments that simply use 1 url (and copy/paste some
earlier comment text). Currently I am blocking ~3 users and tagging
~10 comments as spam a day. Which isn't really productive use of my
time, and not really sustainable. So unless someone knows a better way
of automatically detecting spam bugzilla comments and blocking users
that post them I am afraid we will have to restrict who can sign up
for a bugzilla account or explicitly approve first time bug posters.

Cheers,

Mark


  reply	other threads:[~2021-11-12  8:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11  3:29 Joel Brobecker
2021-11-11  3:47 ` Andrew Pinski
2021-11-12  4:40   ` Joel Brobecker
2021-11-12  8:55     ` Mark Wielaard [this message]
2021-11-12 13:26       ` Carlos O'Donell
2021-11-22  4:03         ` Joel Brobecker
2021-11-24 10:09           ` Mark Wielaard
2021-11-24 14:55             ` Frank Ch. Eigler
2021-11-24 23:40               ` Mark Wielaard
2021-11-25  0:19                 ` Frank Ch. Eigler
2021-11-25 17:49                   ` Joseph Myers
2021-11-25 17:54                     ` Frank Ch. Eigler
2021-11-25 17:59                       ` Joseph Myers
2021-11-28 17:01                   ` Mark Wielaard
2021-11-28 17:35                     ` Frank Ch. Eigler
2021-11-28 18:07                       ` Mark Wielaard
2021-11-29 17:12                         ` Joseph Myers
2021-12-17  2:50                           ` Joel Brobecker
2021-12-17 17:19                             ` Frank Ch. Eigler

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=YY4r/kPvrr20RsZV@wildebeest.org \
    --to=mark@klomp.org \
    --cc=brobecker@adacore.com \
    --cc=overseers@sourceware.org \
    --cc=pedro@palves.net \
    --cc=pinskia@gmail.com \
    --cc=simon.marchi@polymtl.ca \
    /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).