@keithpp @CobaltVelvet I don't think it's any more fatal than the fact there are lots of John Smiths in one town or another. At least here there is only one per town (instance). People deal with that fine in real life, why not online. This also remove the feeling we need to have a globally unique handle for everyone to know us. That's not feasible with 7 billion people. When you see post from the truncated name you can then click their id to see the instance. It's a natural thing to me.
@rateldajer @CobaltVelvet Please read and comprehend. I actually address what yoiu say re many with the name John Smith. But if we have an ID on this network, eg @keithpp and no one is going to look beyond that, then it has to be unique across the network as @keithpp not required where registered. It may be a natural thing for techies, not for the average user.
@keithpp @rateldajer @CobaltVelvet You're defining Mastodon as "a network" when really:
Mastodon = email
instance = email host
octodon.social = gmail.com
@user@instance = email@address.com
The mistake you're making is thinking Mastodon = gmail.com.
@codydh @rateldajer @CobaltVelvet I am not thinking that all.
@keithpp @rateldajer @CobaltVelvet Most solutions that would normalize a username across all instances would also require centralized control. That is not what Mastodon is about.
@codydh @rateldajer @CobaltVelvet Most solutions is not all solutions. Find a solution not bombard me with excuses. Unless you wish to exist in a little niche. Which is what it will remain if not solved, as the more it grows, the bigger this problem will become.
@keithpp @rateldajer @CobaltVelvet I think you're right that there's the potential for some confusion, but wholeheartedly disagree with you decrying it as "the fatal flaw." Maybe a solution is (ugh) similar to what Facebook does, which is mainly referring to people by their 'Name' as opposed to their 'username.' So that they're less exposed. But I largely dislike that idea.
