I'm thinking about how non-developers will feel about atproto. For example, will it take people by surprise that data entered into one app can show up somewhere else? More thoughts in this post.

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.

some thoughts on atproto as a post-app paradigm

Every lexicon, every "app" on ATProto is a "yes and" waiting for your contribution to the vision. We're all first party developers.

@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?

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

I'm going to be launching something pretty big next week, which just happens to include a new atproto AppView, labeler, blob proxy, lexicons. It will have tens of thousands of users, most of whom won't even know they're using atproto, or have even heard of it.

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

How hard would it be to replicate a community Slack installation to an ATProto lexicon so messages can be archived or sent to other application for indexing? Is there any community lexicons for this already?! cc @bmann.ca