I'm confused on two points ...<br><br>1) Austin are you proposing that we move to encouraging use of FirstnameLastname as the username for all future accounts or also try to move current account holders?<br><br>In general, I thought that we had been trying all along to have people's username reflect their real name in some way. I consider the usernames that don't reflect a person's real name to be a failure of our ability to check username requests. I don't see how moving to a more uniform username scheme like FirstnameLastname addresses this problem?
<br><br>2) Wouldn't an alternative approach be to seed the person's user page with their name and affiliation automatically upon account creation. (Presumably this is doable with some coding effort?) Thus, every user page would be seeded with some information about the person? Is this an acceptable policy?
<br><br>-Reshma<br><br><div><span class="gmail_quote">On 4/19/07, <b class="gmail_sendername">Austin Che</b> <<a href="mailto:austin@csail.mit.edu">austin@csail.mit.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
"Jason Kelly" <<a href="mailto:jasonk@MIT.EDU">jasonk@MIT.EDU</a>> mumbled mindlessly:<br><br>> Yeah, I think one good point is that we're not looking for anonymity<br>> here, so it would be great to have a system where as soon as someone
<br>> signed up you would know their full name . (unlike current system<br>> where they need to fill in their userpage).<br><br> I still don't understand what's wrong with putting that info in<br> the user name in the first place.
<br><br>> I'd happily adopt the facebook model -- e.g. log in with email<br>> address, but you can search people by real names and use schools for<br>> disambiguation. I think most people could remember which email
<br>> address they signed in with -- it seems to work fine for facebook, I<br>> think the 10 different email phenomenon may be specific to you austin<br>> :) Trouble here is that it would need some coding to implement this.
<br><br> It would actually need lots of coding if you want to toss out the<br> user system. What link would it create when you signed something?<br> What would a user's page be? MediaWiki is inherently user based
<br> and requires users to have user pages. An alternative would be to<br> assign random strings to users i.e. User:x214g90kueatn but they<br> log in with their email. But to me, this is much more confusing<br> than logging in with their name.
<br><br>> While we could require people to have username FirstLast with the<br>> existing system, I'm a little hesitant because although we may not<br>> have name conflicts now we should expect to have them in the future.
<br>> If we are going to implement a new login system, I'd like to go with<br>> something that can scale as the site grows -- and I think FirstLast<br>> only works for the first JasonKelly. Unless people can think of a
<br>> clever way to deal with poor JasonKelly2.<br><br> The point is that we don't have to implement anything new at all<br> to get something which improves on the current situation. Someone<br> could currently create an account called JasonKelly. Would you get
<br> upset? Would it confuse people? Who gets the right to the page<br> "Jason Kelly"? What if their favorite username is jasonk and now<br> they are stuck with jasonk2? It's not like those issues don't
<br> already exist. So I can't think of any reason to not move people<br> to use more descriptive user names where ever possible as it<br> requires absolutely no change in technology.<br><br>--<br>Austin Che <
<a href="mailto:austin@csail.mit.edu">austin@csail.mit.edu</a>> (617)253-5899<br>_______________________________________________<br>OpenWetWare Steering Committee Mailing List<br><a href="mailto:sc@openwetware.org">
sc@openwetware.org</a><br><a href="http://mailman.mit.edu/mailman/listinfo/oww-sc">http://mailman.mit.edu/mailman/listinfo/oww-sc</a><br></blockquote></div><br>