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...
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
atproto made simple: publishing lexicons - underreacted
atproto made simple: publishing lexicons - underreacted
lexidex
This is a web index of atproto data and API schemas: Lexicons. It is an ✨Experimental✨ project from the protocol team at Bluesky.
Lexicon Garden - ATProtocol Lexicon Browser
Browse and discover ATProtocol lexicon schema definitions
Two Types of Interoperability Without Sharing Lexicons - Wesley's notes
Sharing lexicons is not the only way to leverage atproto’s interoperability
New Build Notes article discussing ATProto and how we as developers can go about forming standard lexicons for common datatypes without being overly prescriptive on implementation details that would limit creativity and competition blog.stygiantech.dev/a/3msmoumcr4d23-atproto-stand…
ATProto Standards Bodies—Guiding the Future of the Network
blog.stygiantech.dev@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.communityWhat'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?
This is partly why I think atproto needs a more convincing vision about being a post-app protocol. A future where atproto is a bunch of apps and each app governs their own lexicon diminishes a lot of its potential in the long-term.
Laurens
yeah i think i might actually, theres a very interesting story here that the main thing that matters is a focal point around which consensus over a lexicon can get formed
ATmospheric Apps
Things that use ATProto to create their own records (NOT Bluesky clients / Appviews)
Your files. Your account.
Chats where you truly own your data.
Build Community Online with Decentralized Tools | Blacksky
Arabica: Coffee Brew Tracking on the AT Protocol
atproto.nl
piper
