Ryan Barrett

@saschanaz oof, Windows, sorry. And exciting that you're interested in contributing! Fair warning though, this won't be an easy starter project. Conversion and formatting happens in granary, writes happen here...

Interesting prior art for this: thread points aka thread break points: visual indicators that you can drag around your full length post to show where to break for a given...

The other difficulty here is that we currently expect a one-to-one mapping between an original post and its bridged version on another network. It would take some rearchitecting internally to...

> To justify making a change we would need an actual positive justification, like a real world valuable use case that isn't possible today. One such real world use case...

Yes! Great idea and contribution. [Bridgy Fed](https://fed.brid.gy/) added `bluesky` to its nodeinfo protocol list back in Feb, https://github.com/snarfed/bridgy-fed/commit/c68e06654b9453d0256cd78b3542e85f78a3e934#diff-8173c603aa47f9de9ea5c1296ee31a82dcc44d8e7ca16a4b420cfc4517c6503dR283, and then later changed it to `atproto`. I'll change it to `atprotocol`...

I'm thinking of doing this first for Nostr keys, #446, to see how it goes, and then migrate keys for existing protocols to it.

Open question: where to store the key? Entirely locally, on my laptop, backed up? In a secrets manager, eg GitHub's or Google's? CircleCI [SSH key](https://circleci.com/docs/deploy-over-ssh/) or environment variable? (Our deploy...

Good question! We've never done it before, but it's definitely doable. For a given user's ATProto keys, we'd just generate new ones, update their DID doc, and maybe emit an...

Oh, sorry, you probably meant how to rotate the _system-level_ key? That's easier in some senses since it's entirely internal, no PKI. Can't be done atomically, so we'd probably need...

Published now! https://atproto.com/specs/lexicon#lexicon-publication-and-resolution