Some more ideas about how I think to build an atproto app for artists from the needs I see in my community, and how I envision to grow this into a longer term project. I am curious about your feedback and who is interested to participate.

Building @skysquare.app, I’ve thought a lot about what the future of the @atproto.com ecosystem might look like, and I’m increasingly excited by the possibilities. Skysquare is a useful demonstration of something that feels much bigger than the application itself—the portability of the ATProto post.

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

@tynanpurdy.com told me that "imgur on ATProto" would be really simple to build. So, here's my "hello world" of ATProto projects: a free image upload service called @pixl.pics. Try it out at pixl.pics. It's simple: view all of your images, and upload more.

@tynanpurdy.com told me that "imgur on ATProto" would be really simple to build. So, here's my "hello world" of ATProto projects: a free image upload service called @pixl.pics. Try it out at pixl.pics. It's simple: view all of your images, and upload more.

ill add components to atproto-ui for this too :D, id love to embed some of these into my personal websites

some thoughts on atproto as a post-app paradigm

some thoughts on atproto as a post-app paradigm

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.