summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar anarcat <anarcat@web>2015-05-31 19:57:50 +0000
committerGravatar admin <admin@branchable.com>2015-05-31 19:57:50 +0000
commit745f38f1e73fa0f28f219b8595c842296f581309 (patch)
tree25f1c59d5cc61a905e0d33cbbba30efc41d2171c
parentf0e30cee785afc9a1f5e5db00b9313e51636f1ad (diff)
mention scalability
-rw-r--r--doc/todo/syncthing_special_remote.mdwn6
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/todo/syncthing_special_remote.mdwn b/doc/todo/syncthing_special_remote.mdwn
index 0a907c43d..a51214bb9 100644
--- a/doc/todo/syncthing_special_remote.mdwn
+++ b/doc/todo/syncthing_special_remote.mdwn
@@ -5,15 +5,17 @@ First off, it is already [packaged for Debian][] with an [ITP
underway][]. Second, it seems to use a fairly simple protocol, the
[Block Exchange Protocol][]. It doesn't try to do everything under the
sun and keeps things simple: NAT transversal, reuse TLS primitives and
-TCP, etc.
+TCP, etc. It also seems to scale pretty well, if we are to believe the
+[usage statistics][].
[Syncthing]: https://syncthing.net/
[packaged for Debian]: http://apt.syncthing.net/
[ITP underway]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749887
[Block Exchange Protocol]: https://github.com/syncthing/specs/blob/master/BEPv1.md
+ [usage statistics]: https://data.syncthing.net/
It does require the syncthing daemon to be running in order to
-transfer files so it would have similar problems than the
+transfer files so it could have similar problems than the
[[special_remotes/ipfs]] remote which is that files get locally copied
between the git-annex repository and the special remote.