tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

[Imported from Trac: page Capabilities, version 15]

amontero 2013-12-13 18:06:21 +00:00
parent 626b722fbd
commit 659880eb1a
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Capabilities.md

@ -59,7 +59,7 @@ share to be validated (hashes checked, signatures verified, etc). That means
When we talk about a "repaircap", we mean "the weakest capability that can
still be used to repair the file". Given the current limitations of the
repairer and our web-API, that means we're talking about #{1,4,7,10}.
Eventually we'll fix this limitation, and any verifycap should be usable as
Eventually we'll fix this limitation (watch for #568), and any verifycap should be usable as
a repaircap too. (There's much less work involved to let !#2 repair a file or
!#8 repair a directory... it's just an incomplete API, rather than a fundamental
redesign of the server protocol.)