0f4ee4f298
I'm unsure why this fixed it, but it did. Seems to suggest that the memory leak is not due to a bug in my code, but that ghc didn't manage to take full advantage of laziness, or was failing to gc something it could have.
23 lines
894 B
Markdown
23 lines
894 B
Markdown
git-annex sync over tor
|
|
|
|
Mostly working!
|
|
|
|
Current todo list:
|
|
|
|
* When a transfer can't be done because another transfer of the same
|
|
object is already in progress, the message about this is output by the
|
|
remotedaemon --debug, but not forwarded to the peer, which shows
|
|
"Connection reset by peer"
|
|
* update progress logs in remotedaemon send/receive
|
|
* Think about locking some more. What happens if the connection to the peer
|
|
is dropped while we think we're locking content there from being dropped?
|
|
|
|
Eventually:
|
|
|
|
* Limiting authtokens to read-only access.
|
|
* Revoking authtokens. (This and read-only need a name associated with an
|
|
authtoken, so the user can adjust its configuration after creating it.)
|
|
* address exchange via electrum-mnemonic or magic wormhole (see PAKE)
|
|
* webapp UI for easy pairing
|
|
* friend-of-a-friend peer discovery to build more interconnected networks
|
|
of nodes
|