On 08/23/2010 05:53 AM, Joshua Bell wrote: >> Ideally, IMHO, there would be at least three "names": >> >> (1) login identifier (used with password as login credential) >> (2) unique human readable identifier >> (3) casual conversational identifier >> >> Prior to "Display Names", the Second Life (firstname, lastname) tuple >> was used as all three. "Display Names" separates (2) and (3), but (1) >> and (2) are still the same. >> >> I'm not sure if the work to do so is on anyone's backlog - I'm >> betting there's a PJIRA on it, though. You'd win :-) SVC-6212 <http://jira.secondlife.com/browse/SVC-6212> (which also includes the 1:many relationship between (1) and (2) Argent suggests below)
>> Technically, it's much less code to touch than "Display Names" (since >> a login-only private credential would be used in far fewer places in >> the code than username or display names), but it would be mostly >> server-side so the community can't help much. We could write user stories :-P On 08/23/2010 06:15 AM, Argent Stonecutter wrote: > The other thing SL needs is a 1:many relationship between (1) and (2), so > that Argent David and Argent Stonecutter are both avatars associated with the > same account... like they are in Avatars United. Which would allow for interesting permission schemes, like allowing transfer of products only between avatars of the same account. (This would probably have to be a new permission. Allowing transfer of all "no-transfer" items between Alts, as SVC-4319 <http://jira.secondlife.com/browse/SVC-4319> suggests, would probably upset quite some people.) But even without that, a 'master account' would make a lot of things easier, like one could account verify all Alts at once, see billings for all linked agents centrally etc. cheers Boroondas
_______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
