~ev/tildeprotocol

6826533c41435ab7963d1c61b5e9c573d5c51104 — Ev Bogue 4 years ago c165ea9
fix dropped sentence
1 files changed, 1 insertions(+), 1 deletions(-)

M README.md
M README.md => README.md +1 -1
@@ 18,7 18,7 @@ Our aim is to develop a protocol that can allow creative communication, without 

Let's take a few examples of how creative chat culture is failing on the Internet:

+ secure-scuttlebutt/bogbook are bogged down by append-only logs. Whether you're doing three-hop replication or selective per-click replication, you're still asking new participants to replicate a lot of information that they might not want to remember on their own instances. The append-only logs recall everything that ever happened, and sometimes we want to forget for practical, legal, or interpersonal reasons. ssb doesn't give curation tools at all, and bogbook only allows per-feed curation. This means that  
+ secure-scuttlebutt/bogbook are bogged down by append-only logs. Whether you're doing three-hop replication or selective per-click replication, you're still asking new participants to replicate a lot of information that they might not want to remember on their own instances. The append-only logs recall everything that ever happened, and sometimes we want to forget for practical, legal, or interpersonal reasons. ssb doesn't give curation tools at all, and bogbook only allows per-feed curation. We don't need to remember everything forever, instead we need a more flexible protocol that is also secure that will allow selective remembering.  

+ ipfs/bittorrent/dat aren't great for chat clients, but are awesome for sharing large files.