Published part two on wiring up Standard.Site as a test of said wiring, in my hubris, and: no dice. Looks like discussion around arbitrary `rkey` values is still in flux — my “slugified post path” rkeys no longer validate, and I get no fancy preview for documents with an `rkey` > 13 characters.
Is TID the best choice for rkeys? #7
tangled.orgJun 8, 2026 at 5:13 PM
How to easily add Standard.site support to your website | Mastro Blog
No need to store rkeys in your YAML frontmatter – just derive them from your existing URL paths.
The Accidental History of the @ Symbol
Once a rarely used key on the typewriter, the graceful character has become the very symbol of modern electronic communication
What the hell is a rotation key? - HItchhikers Guide to the atmosphere
Why it's important that YOU should have a rotation key and backups for your Bluesky/AT Protocol account that is hosted on a third party PDS
What the hell is a rotation key? - Hitchhiker's Guide to the Atmosphere
Why it's important that YOU should have a rotation key and backups for your Bluesky/AT Protocol account that is hosted on a third party PDS
Unkey's Globally Distributed API key generation - with cofounder James Perkins
fedi-e2ee/public-key-directory-specification
Specification for a Fediverse Directory Server for Public Keys
@standard.site Is there a reason that rkeys must be tids, rather than arbitrary string rkeys?
going with single ‘.’ for link-in-rkey, like sh.tangled.graph.vouch:. thanks @thoth.ptnote.dev for the suggestion! indexing in constellation is working, will try to roll out to prod tomorrow with all the backlogged tangled vouches!
fig (aka:[phil])
Constellation "link sources" are currently(ish): `<NSID>:<RecordPath>` like "app.bsky.feed.like:subject" soooo `<NSID>^rkey` like "sh.tangled.graph.vouch^rkey"? or just "sh.tangled.graph.vouch^"?
yes, we're planning to just switch to "any". we were considering issues, but it seems like TIDs are still generated if an rkey is not set on record creation. so no breaking changes to existing tools/apps. have a few other things we're exploring for the next update, still working on those
mary🐇
wrt @standard.site, has there been any discussions internally over how tangled.org/standard.site/lexicons/issues… should be dealt with? IMO this is a high sev blocker for services attempting to integrate with standard.site
i'm seeing an unfortunate trend of atmosphere apps abandoning/forgetting the convention of including key protocol identifiers or URI components in their URL paths (rkey, handle, etc), making it impossible to easily locate/lookup the underlying protocol record makes adding @aturi.to support hard
