Use elsewhere emails

[clone1018]

So currently we store 20,000 elsewhere email addresses.

platform	count
github	19262
bountysource	633

Can we use these emails to somehow get almost all of our participants a valid email?

Go go ideas!

[Changaco]

This query should do the trick:

UPDATE participants p
   SET email = (e.email, false)
  FROM (
           SELECT DISTINCT ON (email, participant)
                  email, participant
             FROM elsewhere
            WHERE email IS NOT NULL
         ORDER BY email, participant, platform = 'github' DESC
       ) e
 WHERE e.participant = p.username
   AND p.email IS NULL;

[chadwhitacre]

@clone1018 Good thinking. I would say once we have a confirmation flow we can send a one-time message to these folks inviting them to confirm their email address. If they don't confirm then we shouldn't mail them again and shouldn't confuse them in any way with people who voluntarily give us their email address.

We should also make a new ticket for prompting users to let us use their public GitHub email when they sign up.

[chadwhitacre]

★★☆

[mushketyk]

Why this task is not tagged as "Ready to Start"?
I think I could do it.

[chadwhitacre]

@ivanmushketyk Go for it! We don't curate the Ready to Start label very closely. You can work on things even without that label. The star priority labels are more important.

[rohitpaulk]

Copying over from #2752 (comment):

Should we really use elsewhere? Those emails were never given to us, at most we could send an email inviting those users to add that email to their Gratipay account, but we shouldn't just add them without asking. If we want to take emails from elsewhere accounts we should do that during sign-up. Until we do that during sign-up it doesn't make sense to do that for existing elsewhere's since we'll just start accumulating more elsewhere emails right away again (unless this PR also silently grabs elsewhere emails during sign-up, which I think we shouldn't do; we should ask).

[chadwhitacre]

We're moving away from social auth (#3837) and towards required emails (#1052). Closing.

[chadwhitacre]

#3506 is more relevant to requiring emails than #1052.