Do you have a reference to this 32 node cap for Resilio? I just tried doing a quick search and did not see any specific results showing this limit. Thanks.
Re:Syncthing Usage Data
by vocatus_gate on Monday March 13, 2017 @01:02PM
(#13859765)
I found the original thread, turns out the peer count is 50 (not 32 like I originally stated).
Here's the thread in question: https://forum.resilio.com/topic/30525-please-please-please-p...
It's now 100 active peers per folder:
https://forum.resilio.com/topic/41520-max-number-of-users-fo...
Re:Syncthing Usage Data
by pricechild on Monday March 13, 2017 @11:37AM
(#13858721)
That's interesting... so even the original 'master' client is treated equally? Other clients can decide to send/receive amongst themselves?
How do you deal with that?
Re:Syncthing Usage Data
by vocatus_gate on Tuesday March 14, 2017 @09:41AM
(#13867361)
I basically post a warning that says "be aware that someone might attempt this." There's unfortunately nothing I can do about it with the way Syncthing is currently architected. We haven't had any malicious users yet but I'm sure we will eventually.
Fallback is just to provide a static .exe on the mirrors and leave the Resilio Sync node running alongside it.
There is no concept of a single "Master". The folder types are "Send & Receive" and "Send only" and the latter will not accept changes from any other client. I still agree it's not the best solution for a network you don't control and that might have a malicious actor in it.
We used Resilio Sync (aka Bittorrent Sync aka BT Sync) for a while for the Tron project ( https://reddit.com/r/TronScript ). It worked great for our use-case: distributing a large number of files to a large number of nodes who required read-only access. Anytime I changed a file on the master node it would blast out to everyone else while simultaneously preventing any other node in the swarm from propagating changes.
Unfortunately with all the restrictions they introduced, it stopped working reliably. Internally they introduced a hard-coded peer cap of something like 32, while our swarm was already over 500.
We switched to Syncthing and it's been working well. There is still one major issue and that's that anyone can mark their copy of the folder as "read-only" (formerly called "Master"), and then they will attempt to propagate changes out to the rest of the swarm. So, there's that. But strictly on a distributed file syncing level, it works great.