Comments on: Authenticating Using Email vs Username

By: nike shox

nike shox — Fri, 09 Jul 2010 12:53:00 +0000

Thanks a landlord it! I acquired yet some insight. Life is so colorful, we should be able to live in, such as Korea and honor the planet. Human life is like rivers, slowly flowing, flowing rivers, flowing through the snow, flows through the prairie and ultimately into the sea, return to the embrace of nature, start a new reincarnation. Allow us to feel the meaning of life will come only to those you have those memories http://www.cheap-nikeshox.com/nike-shox-R3.html

By: gucci outlet

gucci outlet — Mon, 05 Jul 2010 13:16:24 +0000

The post of content is very interesting and exciting. I learned a lot from here.The content from simple to complex, so all of you can come in . No matter you want to see what can be found.By the way ,there are some websites is also very wonderful,you can go and see.such as air jordan 16.5

By: zoltanctoth

zoltanctoth — Thu, 14 Jan 2010 03:06:07 +0000

I have just run into this issue by developing my first django project. I still cannot see the drawbacks of implementing this in django. The aim of a framework should be to be as general as possible if it does not lead to a major tradeoff.

By: cwurld

cwurld — Mon, 28 Dec 2009 20:15:18 +0000

Hi - I implemented something like this a few years ago. I am kind surprised it is not builtin by now. I could not find James Bennet's discussion of this topic.

The website I run, requires users to login and our users are sales and marketing types (generally not very tech savy). Login is by far our biggest problem. Our users have a difficult time remembering a username. They are much better at remembering their email address. Also, we need to have their email address for password recovery.

If we used a username for login and did not require an email address for each user, we would spend half our day reminding users of their username or creating new passwords for them.

I have implemented OpenID on our development site and it works pretty well. But I am reluctant to go live with it because I think our users will be absolutely freaked out by it; too much magic.

By: cwurld

cwurld — Mon, 28 Dec 2009 14:15:18 +0000

By: AYY88

AYY88 — Fri, 09 Oct 2009 12:42:36 +0000

Enjoy shopping at our online kicks outlet and keep up with upcoming fusion jordan shoes!We are commited to provide most up-to date sneakers at sale price.

By: Brian

Brian — Fri, 23 May 2008 12:57:29 +0000

oh…and your authenticate and get_user functions should be explicitly returning None as the last line

By: Brian

Brian — Fri, 23 May 2008 12:47:51 +0000

btw..here is your 1 liner..using the and/or trick

def authenticate(self, **credentials):
return ‘username’ in credentials and self.authenticate_by_username(**credentials) or self.authenticate_by_email(**credentials)

By: Brian

Brian — Fri, 23 May 2008 12:44:39 +0000

what is wrong with
http://code.google.com/p/django-openid
or
http://wiki.developers.facebook.com/index.php/PythonPyFacebookTutorial#Django_Helpers

and if you don’t want to code at all
http://www.google.com/friendconnect/

By: Andrew

Andrew — Wed, 21 May 2008 09:37:51 +0000

Email logins may be convenient for website administrators but in my experience is a hassle. If I don’t remember which email address used to register I have to reregister. They are also longer to type if not saved by the browser password manager on the computer I happen to be on. On the other hand, prefer to use my regular login name that is short and obscure enough to be accepted everywhere.

OpenID is the real solution, though. Please add OpenID support here!