If we do this, one has to be designated "primary" (like Projects) so we can get a consistent default /u/xyz when rendering. This broadly seems like a lot of work for not a lot of payoff, to me, at least today.

Some possible alternatives:

• Do nothing; this doesn't really cause any problems today, even if using two different URLs isn't as purely correct as it could be.
• Warn users when creating a URL which is the same as another URL?
• Add a "Disabled" state which just serves as a visual hint that a URL is not preferred.
• We just point U200 at U100 (that is, change the URL to /u/100) so it redirects through the earlier link.
  • Maybe later, Phurl gets better at recognizing/understanding this.

Of these approaches, my first thought is to favor the internal aliasing by just pointing one URL at another URL. I think this generalizes well into Phurl getting smarter when ((whatever)) points at a task or revision or wiki page or JIRA issue (if it recognizes that it knows about the targets, it can do stuff like smarter hovercard/preview rendering).

In a broader sense, this problem may be very rare, and our use case may be unusual. In the long term, our use case will largely remove to "Common Responses" or similar in Nuance anyway.