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

one thing I really like about atproto is that it provides the infrastructure needed to make open source user apps that actually fucking sync data across devices sorry but the average random hobbyist is absolutely not going to run a user account server for their homebrew todo list app

Still seeking: - Decentralized direct-messaging (DM) service - Works with atproto identities - E2EE - Self-hostable / FOSS - Permissionless - Frontend-agnostic / plug-n-play - No blockchain Group messaging would be a bonus. We'd be your github sponsor + public champion.

Oi! Howzit? こんにちは! We're now available in Brazil, South Africa, and Japan. Welcome to our new users! We’re here to answer your questions about E2EE messaging on Germ DM.

Atmosphere social client apps should make it easier to broadcast beyond the protocol. Ex. In-app mirroring tools for Threads, X, and other microblogging platforms. As well as having post scheduling. Let people share across the social internet, but make sure ATproto feels like home base.

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.

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

some thoughts on atproto as a post-app paradigm

The vector for new signups of atproto accounts is apps. Adoption is unlikely to come through just one app. A “drive” app would actually make sense and I have some ideas there but I think it will be varied. A lot of different apps can get big - from recipes to events to whatever.