public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>,
	Siddhesh Poyarekar <siddhesh@gotplt.org>
Subject: Cleaned out spam accounts from Patchwork / Django.
Date: Thu, 4 Jun 2020 17:06:59 -0400	[thread overview]
Message-ID: <d7723534-c4f0-e584-8f3b-9e13f170801e@redhat.com> (raw)

Siddhesh,

FYI. We had 36,000+ django accounts because of spammers creating
patchwork accounts over the years, but then not doing anything
with them.

I have purged the accounts with "is_active==false" which means
they created accounts and then never verified them with the
post-registration confirmation.

We are down to 261 *real* accounts.

The reason I did this is that two people have already reached
out to me to "unlink" old emails from their patchwork account.

When you "unlink" an email you have to confirm the unlinking by
responding from that email. This is dumb because you often have
lost control of that old email by leaving your previous employer
so most often the "unlink" has to be done by the admin interface
and to do that you have to click a dropdown box populated with
all user names and select "----------" to unlink the patchwork
person from the associated django account (Home>Patcwork>People).

On Firefox clicking a dropdown populated with 36,000+ entries
completely hangs firefox forever.

If spammers get to be a problem we'll need a cron job to purge
is_active==false accounts that are older than a certain date
and do it with python to interface to django to do the admin
action.

I'm not sure how to script this, but I just wanted to tell you
what I just did, why, and that it's a problem.

-- 
Cheers,
Carlos.


             reply	other threads:[~2020-06-04 21:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 21:06 Carlos O'Donell [this message]
2020-06-05  2:08 ` Siddhesh Poyarekar

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=d7723534-c4f0-e584-8f3b-9e13f170801e@redhat.com \
    --to=carlos@redhat.com \
    --cc=overseers@sourceware.org \
    --cc=siddhesh@gotplt.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).