Ajax Renfort

Which god?

...SL, the 100mb loads from a hard drive... in Texas Good thing I'm in Texas

<quote> Your login name usually becomes the primary key for your account in the database. </quote> Actually, a random Integer is used as a primary key not a string. Using a string would hinder performance.

You're funny.... not really.

Actually, the scenario was Anshe Chung (anshee.chung), so if the user open the profile he would see Anshee Chung and therefore could still be duped.

The scenario you present can be exactly duplicated today with a Group title. Were you also against Group title’s for the same reason?

Marry me!

Yes I agree. I think the main problem here is the opponents of Display Name’s really don't know very much about the implementation, this is probably because they have not read the documentation nor have they tried it for themselves. They just keep reinforcing each other’s fears and keep bring up the Linden’s name, which you are absolutely right about the TOS. I wonder why the REAL name’s of SL are not here complaining, like the SL grand winner herself Anshe Chung?

Very well said. I agree completely.

The username is never hidden, it's always visible. Even when a user changes his display name. I really don't see an issue with display names. You are still your user name, think of display names as titler's, thats all they are really.

That's funny. we will all have default display names... so I guess you'll be alone on your land.

I must have missed the post the contained the URL to the survey results. Would you mind reposting it for me?

... and users are going to mistake you for "John Doe.Facebookhero75"! how?

We can't change it. What do the majority of users think about Display Names? Is there a survey somewhere? If a minority of users don't like it should the majority then cater to the minorities views?

No I can't. But I'm going to accept change. Using the format DisplayName.UniqueName, it's pretty hard to argue your identity will be compromised.