|
|
|
|
|
by thaumasiotes
2636 days ago
|
|
In this particular case, I'm guessing -- based on the URLs -- that in order to have the Instagram username "sussexroyal", it's also necessary to be located at www.instagram.com/sussexroyal . This is a design mistake. The URL identifier does not need to be the public-facing identifier, and it shouldn't be. You can have the Duke of Sussex as sussexroyal at www.instagram.com/y6llflk9 and the guy in Sussex who roots for the Royals as sussexroyal at www.instagram.com/y2q9g6uo . There is no need to have the public-facing identifier be the unique identifier, nor is there a good reason to do it. ICQ got this right, way back at the beginning. But somehow everyone forgot. |
|
Yeah, there is: it's a major UX improvement, because the URLs at issue are entry-point URLs, which need friendly names for the same reason domains for public-facing services (which are key components of entry-point URLs) do.
It's true that in the general case objects don't necessarily need a URL component that matches their friendly name, but this is not the general case.