public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "Carlos O'Donell" <carlos@redhat.com>,
	overseers@sourceware.org, Frank Eigler <fche@redhat.com>
Subject: Re: Remove spam with EditComments extension on sourceware.org bugzilla.
Date: Thu, 14 Jul 2016 19:47:00 -0000	[thread overview]
Message-ID: <a65d435a-e949-4837-f3db-2ae46b4f6222@redhat.com> (raw)
In-Reply-To: <f2c0f641-6433-e5ce-c1f1-9608363f111e@redhat.com>

On 07/14/2016 09:45 PM, Carlos O'Donell wrote:
> 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.

Another option would be to set NOFOLLOW on all external hyperlinks, 
which might serve as a deterrent as well.

Florian

  reply	other threads:[~2016-07-14 19:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14 19:46 Carlos O'Donell
2016-07-14 19:47 ` Florian Weimer [this message]
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=a65d435a-e949-4837-f3db-2ae46b4f6222@redhat.com \
    --to=fweimer@redhat.com \
    --cc=carlos@redhat.com \
    --cc=fche@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).