git ssb


%SAuBzX/4DJoZHIVTeJDuqhjIXvNWF7/qqITM/GNB9Xk=.sha256

{
  "previous": "%UyZV78C6r26AFhegOT0Uys0HPXPncjsezHEkVR/26rc=.sha256",
  "author": "@f/6sQ6d2CMxRUhLpspgGIulDxDCwYD7DzFzPNr7u5AU=.ed25519",
  "sequence": 5111,
  "timestamp": 1492077373005,
  "hash": "sha256",
  "content": {
    "type": "post",
    "text": "to set up a testnet, change your pub and client's `~/.ssb/config` to have `{\"caps\": {\"shs\": \"KEY\"}}` where `KEY` is some key for your network, which you can generate in node with `crypto.randomBytes(32).toString('base64')`. related: %Xm7Xz8O7omtbRkrol2PtxtNKXgWDSPuQrmtfQ4jR4FY=.sha256\n\nthe public key and private key are in `~/.ssb/secret`.\n\ncreating a new identity is as you said. one possible issue is that i think private messages are only indexed once, for the current identity, so if you change identities and then sync a message that is a private message for the swapped-out identity, if you switch to that identity again, the private message might not show up in a thread as a reply, or as an update to a git-repo, or whatever else it is. i dunno if that will be an issue for what you are trying to do.\n\ni think the connection error is because the pub answers the request too slowly, possibly because it is busy replicating with other peers, and the client connection times out. there are a few places in the handshake where a timeout can happen which would cause the connection to fail.",
    "mentions": [
      {
        "link": "%Xm7Xz8O7omtbRkrol2PtxtNKXgWDSPuQrmtfQ4jR4FY=.sha256"
      }
    ],
    "root": "%Tp0C0dkzuPENrGWFQbNVHjIxu7AmwIGeM96jHVgUIdY=.sha256",
    "branch": "%Tp0C0dkzuPENrGWFQbNVHjIxu7AmwIGeM96jHVgUIdY=.sha256",
    "channel": "scuttlebot"
  },
  "signature": "+JYCYWzOewH3v7eeuE1QyuEILVD7ebUKX/5W1VQ/A1tOPGgDGeUUminezei124edasV14M09f5KWROFPdIfTCQ==.sig.ed25519"
}

Built with git-ssb-web