Post

That is a very good listen that explains the protocol design and decisions in a concise way, thank you! Are you guys hiring? 🙌

We are! bsky.social/about/join and more postings on the way

Hah, actually the Go BE is right up my alley, 100% what’s in there and some. But I am in Europe and not sure if my wife would let me work PST hours again. 😅 How much of overlap is needed? Currently I am working at around 30-40% but with EST.

I was struck at how using our own domains was a kind of afterthought rather than central. Our domains are legally owned by us, that's their purpose - it is how we own ourselves online inasmuch as we use deeds to own our houses. It is the main central thing that makes Bluesky better.

First two? minutes: a practiced high level description Literally everything after: the protocol design just spilling out of my brain

Honestly I recommend this podcast for the protocol nerds who know atproto pretty well. I'm relistening now and I explain a lot of design decisions

like a moth to the flame, me to the quotidian details

11M registered users 🤔 I take it not recorded recently.

First thank you Paul and all those that support! And open web like this just might turn the tide! Next I’m going to ask a dumb question. Often when I see a Bluesky post and want to reply I’ll go to my browser or photos to locate content. Then when I return, the feed has moved on…

Is that a PEBKAC problem? Am I being dumb? Is there a way to backtrack? More importantly, that has nothing to do with the ATS protocol correct? A protocol is just a white paper. So if that behavior were a bug/feature then that would be on the Blue Sky implementation of the protocol?

Thanks for sharing! I've been digging into AT for the past few months, and I have to say this is probably the best engineering I've ever seen.