atproto made simple: publishing lexicons - underreacted
atproto made simple: publishing lexicons - underreacted
Standard.site: the Publishing Gateway
Another deep exploration into ATProto and implementing lexicons
Standard.site: the Publishing Gateway
Another deep exploration into ATProto and implementing lexicons
third-party apis: community infrastructure on atproto - Keith's Thoughts
you can just build things from an open set of tools
Slack → Colibri Bridge
One-way sync from the FoC Slack workspace into the Colibri atproto network. Every bridged message, reaction, and attachment is a public record on the bot's bsky.social PDS; every raw Slack event is archived losslessly under a com.feelingofcomputing.bridge.* lexicon on the same repo. The bot authors messages into channels owned by a separate community-owner DID — the inverse pattern described under Identity.
microcosm: atproto building blocks
Open-source atproto services and resilient community infrastruture to launch your next app
microcosm: atproto building blocks
Open-source atproto services and resilient community infrastruture to launch your next app
Lexicon Embeds Overview
ATProto’s inside out structure provides an opportunity for open, permissionless building on top of any component in the network, including its extensible data schema definition system, Lexicons. One of the opportunities this presents is users sharing their data and records with multiple apps. Those apps may be direct substitutions (different clients for microblogging say), or apps that use that data in a variety of ways, such as Popfeed an app which aggregates posts about a variety of media ty...
Two Types of Interoperability Without Sharing Lexicons - Wesley's notes
Sharing lexicons is not the only way to leverage atproto’s interoperability
Two Types of Interoperability Without Sharing Lexicons - Wesley's notes
Sharing lexicons is not the only way to leverage atproto’s interoperability
ATProtocol Community
A community space for coordinating, convening, and collaboration around ATProto
What's the intended app/user etiquette for atproto apps with regards to publishing to the same lexicon? Like, say I build an atproto app, would it catch users by surprise if the wrote to the same records (e.g. posts, likes, etc?) that show up in the bsky.app? Or should my app be isolated?
@atpota.to and @dame.is, we were talking about making an ATProto-powered app directory on the community forum and someone found your atproto.garden and some records lying around. Are you interested in sharing your lexicons or talking about what a simple directory lexicon might look like?
A community app lexicon
discourse.atprotocol.community
