Clarify "72 hour window"

[makoConstruct]

Clarify "72 hour window"

[dholms]

More on PLC here: https://atproto.com/specs/did-plc

[dholms]

Yup thanks for the feedback. I actually just did some work revamping PLC & we're going to give all the docs a revamp soon 👍

A recovery key can "fork history" & the PLC server will side with its fork over the signing key's fork.

So if a signing key "attacks" my did by trying to rotate it away from me, I have a 72 hour window during which I can create a new operation that overrides that operation.

It can override any operation that alters the did document. If the signing key was making bad commits to the repo, then the recovery key will need to update the did document to take control away from the signing key, then rewrite & rebase repo history to return it to a good state.

[makoConstruct]

That clarifies a lot, but I don't know what a PLC is.

(Will close when I see the new overview, looking forward to reading it.)

[bnewbold]

Documentation of the DID PLC method has moved over to here: https://github.com/bluesky-social/did-method-plc

Going to close this issue here; if you have more questions please do re-open over in the other repo!