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

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.

why is this needed 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

Hey #atprotodev; should we make a convention for annotating HTML elements with the AT uris they’re built with? (So that, say, a browser extension could offer links to @pds.ls) Something like this? <li typeof="schema:Thing" resource="at://did:web:example.com/org.example.lexicon/rkey">

Added support for Standard.site to cross-posted Bluesky posts. This is a new convention for long-form blogging using the AT Protocol. Initially, you can think of it as extra metadata for your blog posts on Bluesky, with more interoperability between platforms possible later.

Finalizing our new Shortcuts system. In this example we're using @atmo.garden, a new integration. Not every AT Protocol service uses identifiers like c/, so users can now create their own shortcuts. For example, @semble.so could be s/, sem/, or even /👀. This allows fast and quick results 👀

The confusion about standard.site is that there are two distinct and different users. Those that use it as a database schema and those that use it as a new syndication format (like a Wordpress blog with a plugin). But HTML and RSS are views, whereas JSON doubles as both a storage schema and a view

I think this breaking change for standard.site needs to become an ecosystem-wide conversation and convention. Any web page that represents a corresponding AT record needs to include a meta tag that includes that record. <meta name=“at:uri” content=“at://…” \>

I kind of want to make a @standard.site format for characters..... Would be useful for adoptables and roleplayers and TTRPG people I think.