diaspora* doesn’t need an e-mail to be used. The e-mail is useful only to get back its password and to receive notifications. We don’t even send a verification e-mail to check if the address is valid and the user owns it.
I propose to make the e-mail field optional in the registration form with an indication like “Enter an e-mail address if you want to be able to recover your password and you interested to receive notifications by e-mail”.
Note: This discussion was imported from Loomio. Click here to view the original discussion.
@macieklozinski Yes, this would remain in the users profile section so they can add an email address at a later date if they wish.
@juansantiago No, asking for an email address is of no use for controlling spam registrations as we do not require account activation so the spammer can just enter a fake email address. The CAPTCHA image is used to control spam registration.
Absolutely, doubt anyone would block this. It should however be in pod settings, whether to require the field. I hope some day optional email validation becomes a possible pod setting too.
If we do this we should do it right and properly handle disabled mailer at the same time. So if either email input is disabled or the mailer is disabled:
Do not show password reset links
Do not show invite by email links
Do not show email notification settings
Go through all texts and check they don’t refer to sent emails.
Do not require email confirmation when changing the email address and the mailer is disabled.
Go through all mailers and handle graceful handling when the user has no email set.
But if the mail functions are enabled on the pod, but a user has signed up without an email address (optional) then if the user has no email address on their profile then do all that stuff in you list, but other users who do have an email address on their profile will still have those functions, right?
Those kind questions is exactly why this “feature” is nothing you “just do”, you create all kinds of open ends. I’m personally not motivated to do all that work and if you want me to review a submission that implements this, you should start by working out specific action points and things that need to be changed, else the reviewer has to duplicate all the work of considering all edge cases that the implementer did already.