From 14cf035c4f3a749ff696e2cf5bf08d11279a6918 Mon Sep 17 00:00:00 2001
From: Rutger Broekhoff
Date: Fri, 26 Apr 2024 23:26:28 +0200
Subject: Update README (I lied about Gitolfs3 not requiring any kind of
 storage)

---
 README.md | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index f639dfd..434e4da 100644
--- a/README.md
+++ b/README.md
@@ -23,10 +23,12 @@ Currently, it has the following features:
   believe this was nice when wanting to push to some ssh://git@asdf/blabla.git
   repo without having to type `/srv/git` before the repo name. And I don't want
   to have to use something like Gitolite.)
-- Gitolfs3 (the server, `git-lfs-authenticate` and `git-shell` implementation)
-  do not require any kind of persistent nor temporary storage. Instead, user
-  authentication/authorization between `git-lfs-authenticate` and the Gitolfs3
-  server is done using HMAC(-SHA256) MACs.
+- Gitolfs3 does not require any kind of persistent nor temporary storage for
+  token storage. Instead, user authentication/authorization between
+  `git-lfs-authenticate` and the Gitolfs3 server is done using HMAC(-SHA256)
+  MACs.
+- Limiting unauthenticated public downloads on a per-hour basis. Storage is
+  required for this. (This feature is implemented pretty badly.)
 - Public/private repos based on the `git-daemon-export-ok` file in the bare
   repo. (I have a very particular setup in which this is desirable.)
     - Downloads for files in public repositories are 'proxied' through the
-- 
cgit v1.2.3