search

keybase / proofs

Public Keybase Proof System
BSD 3-Clause "New" or "Revised" License
113 stars 57 forks source link

Update wot schema #173

Closed mlsteele closed 4 years ago

mlsteele commented 4 years ago

Using sig IDs will make it easier for server, service, and gui to communicate. Fewer fields to validate and fill in.

It means more work to present the state of the vouchee's proofs at the time of vouching. But there is no plan for that, "rest of the proofs [from failing_proofs] are assumed to be working" means that's true anyway, and it's nice not to trust A about the details of user B's proof.

patrickxb commented 4 years ago

Using sig ids looks good to me, but want to make sure @maxtaco agrees.

maxtaco commented 4 years ago

If this isn't a schema for SigIDs, can you make one?

maxtaco commented 4 years ago

(and use it)

maxtaco commented 4 years ago

Also, why are the other fields disappearing?

maxtaco commented 4 years ago

Oh, I think I remember what I was thinking here. Wasn't there a screenshot where you got to say which of the proofs you thought were useful to you, which is why only some of them are listed?

mlsteele commented 4 years ago

Back to thick proofs. But flattened.