👀

Docs for reference: docs.bsky.app/docs/api/com...

The way I do it for @offprint.app is:
1. Provide handle or DID to `com.atproto.identity.resolveIdentity`
2. Receive DID Document which includes their current service endpoint

This allows me to never ask for the service endpoint, less friction. Hope that helps!

Yup

should also resolve at:// uris and blobs

Maybe you could if they were your Stripe customers already? I’d need to look into that

Migration of content could be made decently easy but the main issue well and any other platform you’d want to move to is keeping your revenue intact as your subscribers would need to essentially re-consent/re-subscribe as payment intents couldn’t just be migrated.

I need to get on your level, damn. The questions you’re asking are just 😘👌

Perfect, I am doing some assuming here because I don’t have your vision in my head so sorry about that. But I’m excited to see how we’ll solve these issues together!

Exactly, our products need to be the end-to-end solution not the documentation if we want at proto to thrive.

Good to know, I’ll have to find these creators. Curious what’d help with those sources of friction.

Better migration tools?

But I'm also really focused on helping normies understand why data portability and ownership matters.

I feel normie creators need to be catered to more when building products on atproto because they're the ones that will bring the masses. And help influence others to care about decentralization.

I'm coming at this from a creator economy angle, which is decently different from @leaflet.pub blogging approach. Think Substack but actually decentralized.

Got a few features planned like analytics and metrics, publishing tools, pledges and more.

Seems legit? 🤔