also, I kinda feel like calling the things that consume atproto data "apps" does a disservice to understanding what they are / how they work / what their potential is. But that is a partially-formed hot take I can't fully defend yet.

the single most important part of atproto is the PDS as a user-controlled auth and storage layer to which clients can connect directly. death to appviews

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

It seems a fork lies ahead, is atproto a portable database for a bunch of apps or a new type of post-app, social filesystem?

The future of atproto lies in bespoke AppViews: highly tailored features that seamlessly integrate with and elevate existing network-wide behaviors. Due to that, I am incredibly energized by the strategic innovations emerging from SkyBeMoreBlue and BlueSky Radio.

difficult to imagine atproto apps building to significant revenue in a world where you can just clone any given app in an afternoon & still access the backing data

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

ATProto is a post-app protocol trapped in a world of apps. I can feel it all around the edges of the network.

difficult to imagine atproto apps building to significant revenue in a world where you can just clone any given app in an afternoon & still access the backing data

what is our “moat” on atproto even? what keeps people using a specific atproto app vs a fully compatible other app?