From: Carlos O'Donell <carlos@redhat.com>
To: overseers@sourceware.org, Frank Eigler <fche@redhat.com>,
Florian Weimer <fweimer@redhat.com>
Subject: Remove spam with EditComments extension on sourceware.org bugzilla.
Date: Thu, 14 Jul 2016 19:46:00 -0000 [thread overview]
Message-ID: <f2c0f641-6433-e5ce-c1f1-9608363f111e@redhat.com> (raw)
Overseers,
Since we have disabled the ability for anonymous uses from
editing bugs, the spammers have just started filling new
bugs with spam content in the description.
We had four such bugs posted on the 12th of this month:
https://sourceware.org/bugzilla/buglist.cgi?email1=cucu%40divismail.ru&emailreporter1=1&emailtype1=exact&list_id=30036
Even with tag SPAM to hide the content the HTML source of
the page continues to have the spammy content, likely not
hiding it from indexing robots.
I suggest we install Mozilla's EditComments extension:
https://github.com/mozilla-bteam/bmo/tree/master/extensions/EditComments
And allow admins to wipe spam comments from the database.
That should be enough to make us a hard target and hopefully
they move on.
Thoughts?
--
Cheers,
Carlos.
next reply other threads:[~2016-07-14 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 19:46 Carlos O'Donell [this message]
2016-07-14 19:47 ` Florian Weimer
2016-08-09 5:19 ` Carlos O'Donell
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=f2c0f641-6433-e5ce-c1f1-9608363f111e@redhat.com \
--to=carlos@redhat.com \
--cc=fche@redhat.com \
--cc=fweimer@redhat.com \
--cc=overseers@sourceware.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).