Re this post: https://bsky.app/profile/dame.is/post/3mkxn4gqycc2j
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
Currently, ATstore has "clean URLs" and it's own lexicon. It intends to align with the in-progress Community Apps Lexicon - see the working group in the forum.
So, once many front ends for app listings exist, it would be good to be able to switch between them.
I think Atstore will want to keep "clean URLs" -- maybe even shorter, like atstore.fyi/streamplace. But that a "copy URI" that is in the front end AND a pattern for having the at:// uri in the page would be good.
Short term: add a "copy aturi" feature in the footer of the page?
Maybe this is a good excuse to figure this out generically? Is this <link rel="alternate" atproto="at://some/path/here"/>
Re this post: https://bsky.app/profile/dame.is/post/3mkxn4gqycc2j
Currently, ATstore has "clean URLs" and it's own lexicon. It intends to align with the in-progress Community Apps Lexicon - see the working group in the forum.
So, once many front ends for app listings exist, it would be good to be able to switch between them.
I think Atstore will want to keep "clean URLs" -- maybe even shorter, like
atstore.fyi/streamplace. But that a "copy URI" that is in the front end AND a pattern for having the at:// uri in the page would be good.Short term: add a "copy aturi" feature in the footer of the page?
Maybe this is a good excuse to figure this out generically? Is this
<link rel="alternate" atproto="at://some/path/here"/>