Comments (4)
More on PLC here: https://atproto.com/specs/did-plc
from atproto-website.
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.
from atproto-website.
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.)
from atproto-website.
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!
from atproto-website.
Related Issues (20)
- specs: auth "entryway" mechanism (detect actual PDS instance)
- RSS for /blog
- specs: consider limiting record-key length to 64 (not 512)
- specs: clarify non-removal of off-spec fields from data records
- specs: allow digits in DID method HOT 2
- Lexicon specs are missing, links 404 HOT 4
- Node IPLD specification is incorrect and incomplete
- additional spec docs (Spring 2024)
- specs: note in auth/JWT/crypto specs that we don't enforce low-S for JWT service auth
- bug: the email input on the subscription form in the footer is cutoff on mobile
- service proxying details needed
- This link in the identity docs resolves to a 404 HOT 1
- document PDS/Relay crawling relationship
- `left` and `tree` in MST nodes are documented as "optional" but implemented as "nullable" HOT 1
- specs: what specific blocks should firehose "commit" blocks contain?
- Incorrect explanation based on old handle specifications
- specs: clarify what data types can appear in a union (object only, or token/ref allowed)
- specs: clarify data encoding of tokens
- specs: clarify what can go in `unknown`: objects? blobs? anything?
- handles: consider clarifying that TXT data could be comma-separated
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from atproto-website.