[ckan-dev] Using e-mails as usernames
Vitor Baptista
vitor at vitorbaptista.com
Thu Aug 8 01:29:55 UTC 2013
Hi Stefan,
These are good points.
Em 07/08/2013 19:41, "Stefan Oderbolz" <stefan.oderbolz at liip.ch> escreveu:
> - Users can identify themself and others better with a username than with
> an e-mail address
> - I don't want to expose my e-mail address to everyone (this is imho kind
> of private)
>
The user's email wouldn't be exposed anywhere. We would have to change
links like http://demo.ckan.org/user/vitorbaptista to
http://demo.ckan.org/user/USER_ID. This would make links uglier, I agree,
but I don't think this page is used much.
But you're right, I forgot to add this to the "first steps". If we're going
to add emails in usernames at first, we need to change these links.
> - In the activity stream and basically everywhere where the username is
> visible, it'll look messy when there are just e-mail addresses. Of course
> you could get rid of the domain part, but then what's the difference to the
> usernames we have today?
>
In the activity stream we don't show the name, not the username. Check
http://demo.ckan.org/user/activity/vitorbaptista. That won't change. I'm
not sure if there're many places where an username is visible. I guess only
when searching.
As far as I can see, usernames just gives us better user profiles' URLs,
and might make it easier to search a user, if there're many with the same
name (not likely, I suppose). How useful these functionalities are to you?
Cheers,
Vítor Baptista
Developer | http://vitorbaptista.com |
LinkedIn<http://www.linkedin.com/in/vitorbaptista>|
@vitorbaptista <http://twitter.com/vitorbaptista>
The Open Knowledge Foundation <http://okfn.org>
*Empowering through Open Knowledge*
http://okfn.org/ | @okfn <http://twitter.com/okfn> | OKF on
Facebook<https://www.facebook.com/OKFNetwork> |
Blog <http://blog.okfn.org/> | Newsletter<http://okfn.org/about/newsletter/>
2013/8/7 Stefan Oderbolz <stefan.oderbolz at liip.ch>
> Hi,
>
> I personally think we need usernames for various reasons:
>
> - Users can identify themself and others better with a username than with
> an e-mail address
> - I don't want to expose my e-mail address to everyone (this is imho kind
> of private)
> - In the activity stream and basically everywhere where the username is
> visible, it'll look messy when there are just e-mail addresses. Of course
> you could get rid of the domain part, but then what's the difference to the
> usernames we have today?
>
>
> I think it would be good to enable e-mail addresses to login (sometimes I
> don't remember my username, but I probably know which e-mail address I most
> likely used). I even think it's a good idea as a temporary solution to
> invite people, but there needs to be a username field, which should be
> filled once the user activates his account.
>
> Just my 2ct...
>
> Regards Stefan
>
>
> On Wed, Aug 7, 2013 at 7:33 PM, Vitor Baptista <vitor at vitorbaptista.com>wrote:
>
>> Hi all,
>>
>> I'm working on a feature to add invites to users. To do so, I'm adding a
>> "state" field to the user. When you invite someone, it'll create a
>> "pending" user, with the name/email that you provide, and will send an
>> email to the user asking him/her to activate the account.
>>
>> The problem is that I can't create a user without an username and a
>> password. To work around this, I'll set them to random values. For the
>> password, it's OK. But for the username, it's weird. Wouldn't it be nice if
>> we could set the username as the e-mail, and be done with it? Why do we
>> have usernames in the first place?
>>
>> If we didn't, then this functionality would be basically the same as the
>> "Forgot Password". We would just need to change the e-mail template, so the
>> user knows what we're talking about, and making sure we activate the
>> account when she changes the password. We could reuse most of the code.
>>
>> The first step would be to accepting symbols in the username (@, +, .),
>> so we can add an email there. Then we would remove the username field from
>> the create user form. And, the final step would be to change the code to
>> use emails wherever we're using username, and we could finally kill the
>> column.
>>
>> For this card, simply allowing symbols in the usernames would be enough.
>> It would be a first step in this direction.
>>
>> What do you think?
>>
>> Cheers,
>>
>> Vítor Baptista
>>
>> Developer | http://vitorbaptista.com | LinkedIn<http://www.linkedin.com/in/vitorbaptista>|
>> @vitorbaptista <http://twitter.com/vitorbaptista>
>>
>> The Open Knowledge Foundation <http://okfn.org>
>>
>> *Empowering through Open Knowledge*
>>
>> http://okfn.org/ | @okfn <http://twitter.com/okfn> | OKF on Facebook<https://www.facebook.com/OKFNetwork> |
>> Blog <http://blog.okfn.org/> | Newsletter<http://okfn.org/about/newsletter/>
>>
>>
>> _______________________________________________
>> ckan-dev mailing list
>> ckan-dev at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/ckan-dev
>> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
>>
>>
>
>
> --
> Liip AG // Feldstrasse 133 // CH-8004 Zurich
> Tel +41 43 500 39 80 // GnuPG 0x7B588C67 // www.liip.ch
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20130807/4097656a/attachment-0001.html>
More information about the ckan-dev
mailing list