From 1de0e60fb6f4525179c8823b17369bfd74cb76ce Mon Sep 17 00:00:00 2001 From: David Dworken Date: Fri, 4 Nov 2022 21:18:49 -0700 Subject: [PATCH] Add a short blurb summarizing syncing --- README.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 4fc4c82..f26972a 100644 --- a/README.md +++ b/README.md @@ -123,7 +123,12 @@ The `hishtory` CLI is written in Go. It hooks into the shell in order to track i ### Syncing Design -See [hiSHtory: Cross-device Encrypted Syncing Design](https://blog.daviddworken.com/posts/hishtory-explained/) to learn how syncing works. +See [hiSHtory: Cross-device Encrypted Syncing Design](https://blog.daviddworken.com/posts/hishtory-explained/) to learn how syncing works. The tl;dr is that everything magically works so that: + +* The backend can't read your history. +* Your history is queryable from all your devices. +* You can delete items from your history as needed. +* If you go offline, you'll have an offline copy of your history. And once you come back online, syncing will transparently resume. ## Security