Lost or Compromised Keys

You don't have a nerdster.org or ONE-OF-US.NET account. If anything, you have an account with folks whove vouched for you.

Basic steps:

Use the phone so to replace your key
- You can repace it as of the last statement it signed or further back in time if it's been compromised and was used to sign fraudulently.
Compel folks to vouch for (trust) your new key.

TODO(aviv): Reference notifications in Simpsons Bot Farm... Homer lost and replaced, notifications, phone app in detail ...

Not ready (TODO: aviv)

Conflicts, Decentralized Views, Competing Algorithms, ...

Whether or not someone is human is fact, not opinion, but we anticipate that there will be mistakes, confusion, and outright fraud. In case someone in your trusted network trusts a key that someone else in your network blocks, we have a conflict.

The Nerd'ster deals with this by notifying everyone affected by this conflict and asks them to resovle it. It uses a simple and naive algorithm to decide - if it finds the trust before the block, then the key is trusted; otherwise, it's blocked. This means that from someone else's point of view (PoV), the conflict could be resolved differently or not even resolved.

You can see an example of this in the Decentralized section:

Homer lost and replaced his key, but not everyone has noticed and vouched for his new key.
TODO(aviv): I've lost track... who trusted or blocked the clowns..

Other services could use more sophisticated algorithms. (Heterogeneous)

Lost or Compromised Keys

Not ready (TODO: aviv)

Conflicts, Decentralized Views, Competing Algorithms, ...

Network Maintenance