50 things i won't build on atproto - permablog

I made meme-museum.at to explore making a complete (if simple) atproto app. Build a collection of meme images and post htem. I don't know if anyone needs it, but, as I tried to lay out in the post, I'll be happy if it helps demonstrate why I'm so excited about the potential of atproto.

I'm going to "lets build: substack clone on atproto".

atproto devs, read this:

The ATProto community built a ton of great features and products over the past year. For our next trick, let's mature them into products and businesses.

Can everyone building on atproto please answer this question? 😇

I think if you're saying "atproto doesn't need a ____" then you're missing the point. Let people build the things they want to see in the ecosystem that they, themselves, will use. We don't need ten things shaped the exact same way, we need every type of shape.

ooh nice my talk got posted! this is a 30 min whirlwind introduction to atproto through a technical lens, basically building up the stack from DIDs -> repos -> PDSes -> relays -> lexicons -> OAuth -> applications

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.