git ssb

%3Chqm1eynYg1ECCqyAgZLZPHspGpLQQTMiS1a3yW81o=.sha256

{
  "previous": "%sVh8G+yglTwm2tVjIyE0zL8V6aDp1KJ/O7ucfed35Ok=.sha256",
  "author": "@BIbVppzlrNiRJogxDYz3glUS7G4s4D4NiXiPEAEzxdE=.ed25519",
  "sequence": 659,
  "timestamp": 1448413732895,
  "hash": "sha256",
  "content": {
    "type": "post",
    "text": "@collypops thanks!\n\nFrom a technology perspective, there are a few differences between patchwork and indie. They are both based on replication protocols, but indie is based on syncthing, and patchwork is based on secure-scuttlebutt.\n\nI think syncthing is higher level than secure-scuttlebutt, it's designed to keep file systems in sync (like dropbox). There is a syncthing android app, i use it too replicate photos & music between my phone and laptop.\n\nssb is just about replicating logs. It's more focused on being a database that has specific properties (such as about event order) that you can reason about build higher level systems on top of.\n\nIndie uses point to point encryption - when you post something it is replicated directly from my device to my followers, this is encrypted via TLS. Introducers (waystone) are used to coordinate peers to connect, although in https://forum.ind.ie/t/we-re-building-for-os-x-and-ios-not-linux-this-is-not-a-bug-it-s-a-feature-here-s-why/542 aral mentions \"decentralising it completely via IPFS/blockchain\" so that may change.\n\nIn patchwork, 3rd parties can relay (gossip) information for you, which creates improves availability. Every message is signed, so gossipers cannot interfer with the message - note this is significantly different than real world gossip! secure-gossip if you will.\n\nPatchwork also has some servers, but they are identical to the client (plus invite codes) rather than a special role, as in waystone. We feel that this doesn't make it not a peer to peer protocol, since anyone can run them, and your identity is not tied to them as in `email@domain`.\n\nWhen you want a message to be private, it is encrypted end-to-end with [private-box](https://github.com/auditdrivencrypto/private-box)\nSo gossipers will still see the cyphertext of your message, but will not see the plaintext. best of all, the recipients (including the number of recipient!) is also encrypted, so a patchwork private message leakes much less metadata than GPG. (it's obviously a message for someone in the network, but there is no clues who\\*)\n\n\\* Excepting timing information. To obsecure timing information, you'd post messages randomly and relay encrypted sends. Doable, but quite a niche, will leave this for later, once more people are using the system.\n\nFor point-to-point connections, patchwork uses secret-handshake,\nwhich handles authentication and encryption. I wrote a paper about it. [secret-handshake.pdf](&aqRD7DmVr/ZswM1z2ssbnOe7Sd7M9oNqesyYeCSj6B8=.sha256)\n\nAnyway, building a decentralized social network is really hard. If this was a web app it would be finished months ago. But despite that, it's worth investing that effort because it opens up a whole new range of possibilities.",
    "root": "%wxXcXNM1z/htyIeN6A2Nt25sh9CZcmRHreWaIFTptFs=.sha256",
    "branch": "%j7zgVqtyIC/KJmRFXLlJdntBxfBfiBmKXnA0lJTZGS8=.sha256",
    "mentions": [
      {
        "link": "@eO4/h8L6WQi4grlB3BfhfQdv/fTFGHzqyG0qCPtLaJQ=.ed25519",
        "name": "collypops"
      },
      {
        "link": "&aqRD7DmVr/ZswM1z2ssbnOe7Sd7M9oNqesyYeCSj6B8=.sha256"
      }
    ]
  },
  "signature": "rxY3VkiYvAYH7mrAXSDjf/qnj4IxzXhErmHN615QTgjYobpf+c5XgmfbOgCidKVZblsleorFU+kJvuitv60qCw==.sig.ed25519"
}