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

Does anyone have a good guide for migrating existing apps/platforms to use ATProto?

now updated my atproto oauth reference from last year! github.com/j4ckxyz/atproto-oauth-referen… - explains why to avoid `transition:generic` AND a skills file for your coding agent!!! github.com/j4ckxyz/atproto-oauth-referen… no reason to not have #atproto oauth anymore!

ActivityPub always felt like “I’m creating my own MySpace and you can make yours too if you want”, while AtProto feels more like a revised way to think about how this sort of service should work.

PART TWO: All the other reasons i don't like CARs for atproto repo exports! In this one: ambiguities and inefficiencies. (the biggest problem is already hopefully getting fixed in the IETF draft though, yay!)

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

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

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.

There's lots I haven't yet understood about atproto, but I simply won't do the standard.site thing whilst it offers a worse UX than… not doing it.

There are many things being built on atproto. Many of them won’t get adopted or thrive. And yes, many are built without user research. It’s OK? Don’t use things you don’t want to. Promote things you like. And build something yourself if you feel like it. Do it the way YOU want it to be.

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}"

That should be the guiding principle for all atproto "alternatives"