while the permissionlessness vector of atproto will certainly enable new things we can't imagine the pattern of "____ but on atproto" is key for taking our daily lives back. a framing i prefer is "i can now do {boringDailyLifeThing} without {shittyExtractiveApp}"

reminder that the inaugural ATP (atproto) working group meeting will be taking place soon! we are scheduled for the Thursday of #IETF126. you can register and participate remotely. if you have a topic you want to discuss, reply to the chairs on the mailing list; this is roughly final call

Found a conventional use for atproto (replacing high school state associations/athletic conference/school sports websites) the other day and built a spec because I couldn't help myself. it's live but I'll share a blog post about it before sharing

what is atproto?

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.

Frankly atproto is a great technology that just has yet to really be successfully productized. A few orgs are putting real work into that productization now but only time will tell if it succeeds.

Some initial atproto-related learnings from #Rebuild Helsinki 🇫🇮 * most people building apps here have no idea what atproto is, which is a shame since especially when building social apps, atproto is a great starting point for many reasons