the open ecosystem for atproto makes it super easy for one developer to build a compelling and feature rich application in their free time that cannot possibly be maintained by one developer in their free time

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

Hi, we're HappyProto. We help you build on atproto... without the hard parts. You create the app, we'll run the backend: auth, private data, scripting, and an API over 46 million accounts. Welcome to atproto on easy mode. Join the waitlist at happyproto.at?utm_source=bluesky&utm_medium…. #atproto

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.

The most significant extension to the protocol since launch—atproto spaces—is now officially alpha software you can start testing with. Here's more about the goals and how to start testing. atproto.com/blog/atproto-spaces-alpha

anyone have tips for building atproto stuff without a backend ? i’d like to make userinput better, currently it can be kinda slow. looking for best practices i may not have thought of.

Testing an idea that I've had for a while, but I think is even better suited for atproto Internet, meet plts.at

Do you need to run a PDS, PLC, Jetstream or TAP for development and testing of your #ATprotocol app? A couple of us needed it for independent projects and we try to DRY so first pass is at github.com/OpenMeet-Team/atproto-devnet How are you managing that stack for your project?