Post

Subscriber features necessitate a protocol-level infrastructure for handling permissioned data. As the blogpost says, permissioned data will be the main focus for this year.

The docs are online, so all they need to do is implement the ability to connect an atproto account and publish to it.

Working on it, Simon, great to know that's a feature you'd want. It's always helpful for them to hear from customers (and potential customers!) as well

How can I get started with this? Is there an easy "get started" guide that starts from an empty code folder that I'm just missing?

The current approach is still pretty rough, but it’s the fastest solution I could think of. Feel free to take a look. only need to clone the repo, update the config, and deploy it to Cloudflare. After that, you can immediately access your own articles from standard.site. bsky.app/profile/tass...

standard.siteStandard.site - One schema. Every platform.Standard.site provides shared lexicons for long-form publishing on AT Protocol. Making content easier to discover, index, and move across the ATmosphere.
Tassis@tassis.cc

github.com/tassis/atfie... An experimental AT Protocol-to-HTTP bridge. It integrates lexicon formats from standard.site, Bluesky, and WhiteWind, and exposes a set of basic HTTP endpoints. #Bluesky #ATProtocol #Tech #Coding

For integrating standard.site to your website? This is a collection of ATProto lexicon that you publish on your PDS. (I have created a hand-crafted library implementing them in Go if you want : tangled.org/anhgelus.world/goat-site) Feel free to reach me if something is not clear :D

standard.siteStandard.site - One schema. Every platform.Standard.site provides shared lexicons for long-form publishing on AT Protocol. Making content easier to discover, index, and move across the ATmosphere.