git ssb

%7hcvpITRduLDNKpLqN6Xm+8d/t7aQu2YqZhBO3CtSC0=.sha256

{
  "previous": "%TPGDL1qjmEIFHgOyvAjFcE3FGFWrBTX5gKyYt0vMfmg=.sha256",
  "author": "@EMovhfIrFk4NihAKnRNhrfRaqIhBv1Wj8pTxJNgvCCY=.ed25519",
  "sequence": 4630,
  "timestamp": 1475179441149,
  "hash": "sha256",
  "content": {
    "type": "post",
    "root": "%joW3UgGmfvcnxQ2wj3ZMte/Hgoj4pHWjXCxNv/LeBAo=.sha256",
    "branch": "%joW3UgGmfvcnxQ2wj3ZMte/Hgoj4pHWjXCxNv/LeBAo=.sha256",
    "channel": "patchwork",
    "text": "In a centralized system, the database is the source of all truth and enforcer of rules. Enforcing a rule like \"all names must be unique!\" is easy.\n\nIn a decentralized system, like ssb, there is no single source of truth. peers must enforce a rule with collective action. This makes for a _lot_ more wiggle room. To put it in database terms, it means anyone can write anything, but other clients will ignore what they think is invalid.\n\nSo, names is patchwork are somewhat like IRC, except that when I mention you [@akkartik](@1DfC2qFuXuli/HOg3kJbKwxiOpc3jXLdJD3TnhtzWNs=.ed25519) it records both your human name and your public key, then I sign this message, so there is a cryptographic record that I call `@1DfC2qFuXuli/HOg3kJbKwxiOpc3jXLdJD3TnhtzWNs=.ed25519` \"akkartik\"\n\nI can call you anything. Unlike IRC, but like \"real life\", other people choose your name. So, in ssb, a _name_ is just a mapping from a string to a cryptographic token (i.e. public key, and git-ssb repos also have names)\n\nIf I start using a new name for you, my old messages will still bear the name I used then, but it would still link to your public key.",
    "mentions": [
      {
        "link": "@1DfC2qFuXuli/HOg3kJbKwxiOpc3jXLdJD3TnhtzWNs=.ed25519",
        "rel": "mentions",
        "name": "akkartik"
      }
    ]
  },
  "signature": "W2ZGFnceHt914RprgVmwXKEyYxY3echEjEnQDXlR4+dUSUweLo6N3bE48lAzdosNOVoWI2yzpg0uDQ2V/I8RCA==.sig.ed25519"
}