Client: Show full organization name in URL

[john-light]

Is your feature request related to a problem? Please describe.

When an organization that uses a subdomain of aragonid.eth is loaded in a browser, the name in the URL is truncated to just the subdomain name and not the full name.

Describe the solution you'd like
Show the full name of the organization in the URL.

[luisivan]

Could you expand on the rationale for that? The rationale for truncating it is that aragonid.eth is the default ENS domain for all DAOs, so it makes sense to just show their "username". If the domain is different, however, the whole URL is shown.

[john-light]

Because the URL is the main way that people share information about organizations, and showing the full name in the URL will prevent any confusion about what the full name of the organization is.

It's probably fine to assume that when someone types only the subdomain abc, that it will autocomplete to show the full name abc.aragonid.eth. But I don't think the inverse should be true (that a full name gets truncated to show only the subdomain).

Edit: Pondering it more, the rationale is also about getting users used to looking at/ recognizing/ verifying the full ENS name, rather than assuming what the full name is. I predict based on experience in Web2 and darknets that we will see "phishing" types of attacks that get people to try to send money to a subdomain of an attack name instead of the legit name (e.g. charity.attacker.eth instead of charity.legit.eth). The damage these attacks do could be minimized if users are trained to look at and verify the full name. So we should avoid conditioning them to accept only a partial name.

[luisivan]

What about getting users used to checking the full name only if it's not an aragonid.eth name? So basically aragonID is the default, and users would always see the full one otherwise.

I think we should do whatever is better for UX now, which may be hiding this, and then if there is any case, we can push an update. In the future you may even just see the name and icon, so we may need to think more about this, but I'd say it's not a problem until we have adoption.

[john-light]

I think we should do whatever is better for UX now, which may be hiding this, and then if there is any case, we can push an update. In the future you may even just see the name and icon, so we may need to think more about this, but I'd say it's not a problem until we have adoption.

I don't see how hiding part of the name is better for the UX. It's not an obvious UX improvement to automatically truncate the name, and it introduces a potential security vulnerability. And users shouldn't have to have a bunch of "exceptions" to the rule of "always check the full name" in their heads: "except for when using Aragon, except for when using ABC dapp, except for when using XYZ dapp" etc, this just adds to the complexity and mental overhead of using dapps. So if anything it's a UX degradation and a security vulnerability.

My argument: sure, autocomplete a1 to a1.aragonid.eth so users don't have to type .aragonid.eth every time. But don't take a full name and truncate it, or only show the subdomain if that's all they type in. We should always show the full name in the address bar and throughout the app so that users are always certain of exactly which org they are looking at and can't as easily fall prey to phishing attacks.

[luisivan]

Fair enough. I don't have a very strong opinion and I don't think it's worth it to spend a lot of time on this decision anyway. So I'd wait until @sohkai is back so he can chime in, as he was the owner for this, and then we can make a decision

[sohkai]

The main reason for truncating it in cases of aragonid.eth is to provide shorter URLs, which many people internally and externally have requested as UX wins.

This is primarily a question for @dizzypaty though.

[sohkai]

Closing for now; we will prefer shorter URLs in the short term.