Use names for sites instead of number

[krlwlfrt]

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

---

Feature request

Which Nextcloud Version are you currently using:

Nextcloud Hub 10 (31.0.2)

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

It would be nice if it would be possible to use names for external sites instead of numbers in the URL, e.g. /apps/external/foo instead of /apps/external/1.

I frequently type out URLs, because it's faster than navigating the UI with the mouse and not being able to tell which app I'll open by a name makes that hard if not impossible.

Describe the solution you'd like

Add another property for external sites to choose a name or suggest one from the supplied URL.

Related, but different premise: #61

[provokateurin]

Makes sense, but when implemented we need to make sure that the chosen IDs are all unique.

[fz0000]

For labeling such unordered items, could we consider using UUIDs or random strings rather than sequential numeric IDs?

See examples below:

• Google Docs: https://docs.google.com/document/d/1v6S7IkDL_YIaVn1rBcVbqFr3rbNUX9_kLfFc00WTtx8
• ArcGIS Experience Builder: https://experience.arcgis.com/experience/670e112e04ae415e9755f2d65fded76c
• Microsoft Store: https://apps.microsoft.com/detail/9MSMLRH6LZF3

Another solution is using both the ID and the Name. It keeps the readability while resolving the issue of duplicate names.
For example, in App Store, different apps can have the same name:

• https://apps.apple.com/us/app/calculator/id1069511488
• https://apps.apple.com/us/app/calculator/id552974550

[provokateurin]

UUIDs don't make sense, they are not more readable than integer IDs and they also do not provide any potential security improvement being non-enumerable.

Having the name and the ID sounds good to me, as we can just ignore the name parameter entirely when parsing the URL. So while the link will contain a specific name, you could just put anything in there and it would still work.
However when this is implemented it must keep compatibility with existing URLs to avoid breaking links.