I think you are probably right. Also, a UUID would not rely on the note name. If you used a note name as a url, and renamed the note, the external link could break.
But would having a UUID rely too much on Obsidian’s database, and go against the philosophy of owning your data? If you had all your Markdown data, and rebuilt your vault, would all those UUIDs be lost and links broken?
- Scrivener uses a UUID as well.
- Notion uses a UUID, but also puts the name of a note before the UUID. But if you rename the note, the link doesn’t break. The UUID doesn’t change.
- This is a fake example: notion://www.notion.so/yourworkspace/The-Note-Name-Goes-Here-820937a9e8f70e0a7fc7097545788763
- Things also uses a UUID.
Having natural note names as urls would mean you could write them by hand, or generate them by script, which would be great. Could there be multiple access points? UUID or note name?
I imagine there would be a lot of design considerations to implement this well.