blob: ca3e8f19a5bebd38d122439c4a44c4c4e2663453 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
|
git-annex sync over tor
Mostly working!
Current todo list:
* copy --to peer of a 100 mb file causes the memory of the remotedaemon
to creep up from 40 mb to 136 mb. Once the transfer is done, the
remotedaemon continues using all that memory. Memory leak. Profile it.
(The sending process creeps up some initially, but stops at 45 mb used.
That could just be buffering.)
(copy --from peer does not leak on either end; the remotedaemon uses 34
mb and the receiver 44 mb.)
* 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
|
