Transmogrify Record - Lexicon Garden
Transform records between ATProtocol lexicon schemas
Guide for migrating your app to atproto
This is a quick response to this post @anniesexton.com on Bluesky Please do edit and point to other resources If you have an existing database powered app, here is a rough guide to thinking about migrating to atproto Figure out which data is private, this will stay in your database Figure out what the main data is. Look around for an existing lexicon or create your own. When creating new records, write them to the user PDS. You’ll need to start aggregating your lexicon types from the ne...
ATProto Standards Bodies | Sam Clemente | Offprint
How do we go about maintaining lexicons across apps?
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...
Lexicon Store - ATProto Lexicon Schema Registry
Discover and explore AT Protocol lexicon schemas. The verified registry for Bluesky and ATProto lexicons.
Can atproto scale down?
Decomposing the Bluesky appview and self-hosting the pieces
Bitesize Proto: Upserting ATProto Records - Hitchhiker's Guide to the Atmosphere
Tired of creating duplicate records in a repo from your atproto app?
There are no instances in ATProto | Hacker News
I feel like you've (perhaps purposefully?) misinterpreted "instances" just to plug ATProto specifically at the expense of ActivityPub (and RSS, a bit). I think you lower yourself by doing this:
As the Atmosphere grows beyond Bluesky, assuming every user has a Bluesky profile won't hold up. A base profile sounds like the fix, but the UX gets weird fast. Lexicon generics — a pattern built from existing ATProto concepts — could make profile-type records discoverable and translatable across apps without flattening them into a single record.
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
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?
Are there any atproto apps that use records from competitors? This ecosystem won't feel open to me until @bsky.app uses something from outside the `app.bsky` namespace as part of its core experience
Are there any atproto apps that use records from competitors? This ecosystem won't feel open to me until @bsky.app uses something from outside the `app.bsky` namespace as part of its core experience
ATmospheric Apps
Things that use ATProto to create their own records (NOT Bluesky clients / Appviews)
AT://links
collection of fun / useful apps built to work on / with ATProtocol
atproto apps
not really exhaustive list, more to store the ones i might have missed
Skywatch Statistics
AT Todo - Decentralized Todo App on AT Protocol
About - Monomarks
plyr.fm - music streaming on atproto
Popfeed
Rocksky
import.py
Archivers AT
Brickster — Build anything, together.
BlueHarbor
Kimbia - A training journal that belongs to you.
Currents
atmoBB Forums
atmeet — Blueskyで、集まろう。
GainForest — Biodiversity Observations & Nature Projects
badge.blue — CID-First Attestation Specification
arecipe
Radial
