I want people to be comfortable paying for an atproto account (ie. space on a PDS) It’s the bedrock of everything we’re building; if it’s not funded it’ll get squeezed in ways that are bad for users (hi Gmail) We should normalise having (very cheap) paid-tier PDS accounts on the services we build

1/X I made an atproto proposal around PDS to PDS repo migration that gets around all of the pain points of account migration today and intentionally builds a migration flow for users to go to the PDS that they want to move to and commence the migration from there.

The week-end is over so I'm pressing ⏸️ on my custom PDS project for now. Here's part 2 of my dev journal. I've learned a lot already and so far I feel like it might actually be worth finishing. It's really cool to get a more intimate understanding of ATProtocol and it's implementation.

Shower thought idea: What about expanding the role of the PDS for account management? E.g. when signing up on atproto with any app/service for the first time, redirect to the already existing account interface (`/account/`) already present on reference PDS, making this flow mandatory to support.

here is how i've been explaining PDS migration to the 115 users i've migrated: imagine your bluesky account as being an apartment. you're upset the rent is changing, so you move to a cheaper apartment on the other side of town. after you move, you have to update your address with the post office.

Did a quick write up on the work I've been enjoying to make a PDS distributed. #atproto

i think it's time someone made a google suite alternative in atproto, have that be the "default" PDS; literally just replace sign in with google then everyone understands the concept of oauth and we can move on with our happy atmospheric lives