Content Naming Standard

[tiller-tolbus]

We would like to be able to address content in a general way that provides most of the guarantees of fully-qualified scry paths but can be made useful in environments constrained to HTTP like the browser. With SSO, one can assume that all Urbit IDs have a corresponding public URL that can be resolved by any ship.

There is the possibility of unifying this standard with the idea of a "pretty-path", or the idea of a user-facing scry path that strips some data from the FQSP to be more legible to human eyes.

Example:
pretty-path: ~tiller-tolbus/blog/aegean
FQSP: ~tiller-tolbus/data/~.~2024.2.3..20.12.12..c863/cx/home/blog/aegean/udon
URL: https://tiller-tolbus.redhorizon.com/blog/aegean

In essence, we should try to define a standard in which every piece of content that follows the standard exposes 1) a human-readable address, 2) a way to derive a FQSP, and 3) a clearweb-accessible URL.

This would be helpful to resolve some questions in #11 and #12

[tiller-tolbus]

Within the Gall/Clay model:

The pretty-path should be specified as:

[@p =desk /rest/of/path]

The difference between a pretty-path and a FQSP is that the case and care are assumed (latest timestamp and %gx respectively).

Supported marks should one-to-one with what is supported by HTTP scry (presumably, anything with a valid tube to MIME)

There are prior examples of discussions of this idea within urbit/urbit that should be investigated further.

[tiller-tolbus]

Relevant: https://github.com/urbit/UIPs/blob/main/UIPS/UIP-0121.md

[tiller-tolbus]

Pretty-paths are part and parcel of shrub. Closing this for now as the shrub path solves this issue.