j3d1/toolshed
2
1
Fork 0
Code Issues 9 Pull requests 1 Projects Releases Packages Wiki Activity

stash

Browse source
This commit is contained in:
j3d1 2026-08-31 19:09:58 +02:00
parent 9c9f0f2d9b
commit 6a9ed35bcd
11 changed files with 166 additions and 186 deletions
Download patch file Download diff file Expand all files Collapse all files

3
docs/handles-and-shortids.md
View file

@ -181,7 +181,8 @@ It isn't a URL and isn't meant to be openable by something that doesn't already
Toolshed short id is: there's no scheme, no path, and the payload after `:~` is bit-packed base64,
opaque to a human. It belongs to the same "context already makes clear it's Toolshed data" class as
a compact User-Qualified ID, meant for use inside the app (or between things that already speak the
short-id format), not for a physical label or a link shared outside it. What it adds over a bare
short-id format, including a physical label meant for the app's own scanner) - not a link or code
meant to be opened by something with no idea what a Toolshed short id is. What it adds over a bare
`~token` is that it no longer depends on "whichever backend I currently happen to be talking to" —
the domain travels with it, so it keeps resolving to the same entity once copied elsewhere. Unlike
a User-Qualified ID, it isn't limited to owned kinds: every kind in the short id registry can be