How I understand pretty paths in the new system

@Untitled Contact @Untitled Contact and I were discussing about the new system a couple hours ago and Burdi mentioned that the new system basically is like a URL Shortener, but some of the things both were mentioning did not feel to me like a "normal URL shortener":

Image shared by Burdi on Discord

What I have in mind about it

I remember back in the day when we used to write code, I had a URL shortener deployed to netlify that was a simple tabular file with two columns: the preety path short url and the target URL. that's it

Understanding that a pretty URL can just point to ONE thing (a ref to a resource), I see that there's no ambiguity on how to resolve either a document resource or a zoomed resource to a block, because the resource itself can just poing to either of those:

horacio.com/foo -> hm://<horacio_space>/:r/<resource_id> horacio.com/foo/bar -> hm://<horacio_space>/:r/<resource_id>/:z/<block_id> horacio.com/baz -> hm://<horacio_space>/:r/<another_resource_id>

If the pretty path is always pointing to a ref, and that ref can be about anything (resource, block, profile, even comment, or a block fragment) then I don't see where's the ambiguity of pretty path resolution.

Maybe what the ref cannot be is to a specific block or something else than a full resource?

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime

Comments