What if the user puts in a "fake" e-mail that belongs to someone else?
Then any service notifications go to the poor person who owns the e-mail
address, not the person who signed up for the account. Also the user
would get to take advantage of the benefits of the service.
With B only the initial activation e-mail would get sent there. There
is no benefit to the user to put in a fake e-mail address because they
still don't have access to the service.
Hope this helps,
Casey
On 08/09/2010 03:38 PM, kostia wrote:
A. If we have a form of registration only with password and username
fields. Then the user may write some fake email (foreign).
B. We use registration activation link sent into email like it is done
on Facebook, Linkedin, Twitter and so on.
Why B is better than A? Why A is a wrong solution? Any arguments?
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
