Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove e-mail verification success e-mails #3124

Merged
merged 1 commit into from
Jun 16, 2023

Conversation

sunaurus
Copy link
Collaborator

@sunaurus sunaurus commented Jun 15, 2023

This is a proposed change to completely remove the "e-mail verification success" e-mails from Lemmy.

For context, when a user signs up on an instance that requires e-mail verification:

  • They first receive an e-mail with a link they need to click to verify their e-mail
  • On clicking this link, they are directed to their home instance, where they see an "E-mail verified" success message
  • Finally, they receive a second e-mail which tells them that their e-mail has successfully been verified <---- This is the e-mail that this PR proposes to remove

Arguments for removal:

  • From the perspective of users, this e-mail doesn't add a lot of value, because they receive it at the same time as the website notifies them that their e-mail was verified anyway. Basically, it's a duplicated notification, which I'm sure some users might even consider a form of spam.
  • From the perspective of instance admins, this e-mail doubles the e-mail related costs of any new user. On lemm.ee, we have sent 1400 of these e-mails in the past week, which accounts for 14% of our usage cap for this month on our currently active e-mail plan.

This PR is related to #3011

@Nutomic
Copy link
Member

Nutomic commented Jun 15, 2023

Makes sense to me. You also need to remove these strings from the translations repo

@dessalines dessalines merged commit 007c7d5 into LemmyNet:main Jun 16, 2023
1 check passed
@sunaurus sunaurus deleted the remove_email_verified_emails branch June 16, 2023 22:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants