• Content Count

  • Joined

  • Last visited

  • Days Won


About nellie4568

  • Rank
  1. Yes, that should work fine, as long as changes are propagated from A->B, changes found on B will be sent B->C. Since you don't mention where B is located, if you're concerned regarding security you could make B and encrypted-key-only share, and it will still function the same way. That way B can store and share changes to files, but is entirely unable to read those files (just don't lose your RW key).
  2. Thanks all. I was able to get it working with michaelbaxters solution. For some reason I couldn't get the service to work correctly, but was able to manually start it and it seems to run fine.
  3. I have a raspberry pi where I'm attempting to install btsync using the official deb package from here. I downloaded the deb using wget. Ran as sudo dpkg -i appears to install but the btsync service start silently fails. When I run 'service btsync status' I get 'btsync for USER pi: not running'. When I try and start it via command line with either 'service btsync start' or 'sudo service btsync start' it tries to start but silently fails. Status once again reveals 'btsync for USER pi: not running'. Any
  4. Are you syncing across LAN or elsewhere? I would say offhand you either have a firewall issue or your ISP is throttling traffic.
  5. At the moment, only if client1's desired shows and client2's desired shows are in different folders with different btsync secrets.
  6. I remember seeing some media content being distributed on this forum when it was first opened for public use. Dig far enough back and you'll find some secrets.
  7. You really should look at the FAQ and documentation as this is quite thoroughly covered there. But, in a few short words: Yes, this is possible. You will need to add the folder in question to BTsync using your main computer. Then copy & use the read-only secret on your phone. This will make it one-way sync. To find the read-only secret: Right click on folder in main btsync window --> Open folder info
  8. You really should look at the FAQ first, as this has been answered many times before, but as we are a nice and friendly community this is what you need to know: _____________________________ BTsync using just the randomly generated sync key is more than safe enough. The chances of generating the same key as anyone else is: 1 / (36^32) or 1 in 6.33 e49 (technically twice that if you also include D,E,and F secrets) So essentially almost never in the lifetime of the universe. If you are extra paranoid you can (after disabling tracker, relay, dht) have btsync only connect to IP addresses
  9. I believe there is a request for a .syncOnlyAllow type system sometime in the future. Cast your vote for it in For the moment, the easiest way would be to exclude the most common video formats. Unless you're recording/encoding in something really strange I would suggest adding the following to your .syncIgnore: *.avi *.divx *.f4v *.flv *.m4v *.mov *.mp4 *.mpeg *.mpg *.mkv *.ogv *.vob *.wmv *.webm *.xvid Of course, check and make sure you don't have video files that are going to be outside that range. My guess is the list above will cov
  10. Well, on Android it's as simple as making a folder and adding the same secret to all 3 devices. Works great. iOS......... good luck...
  11. You can always install btsync on a raspberry pi or grab a cheap vps (like backupsy) to act as an intermediary and sync changes when only one computer is online. Sort of like creating your own cloud storage.
  12. Glad I could help! Sounds like you have a great plan in mind. That's a heck of a lot of resiliency! You can make encrypted read-only (sometimes called "F" secrets, see linked post for details on what A through F means) without the API. Check out the following post for details. Keep in mind that if you are already sharing the folder you intend to use, you'll have to remove ALL computers that are sharing that key (likely all "A" secrets) and generate the new D, E, and F keys. And remember,
  13. Probably better off rolling your own dedicated backup host for btsync. Backupsy is fantastic for this and they specifically allow BTsync.
  14. I'm having a hard time deciphering what you're intending to do. Do you want to use your members as additional encrypted file sync/storage? Or do you want them to see the files and contribute to your work? Very confused as you mention the API. Under the API the encrypted read-only folder that the API creates would prevent any contribution. Any computer that has an encrypted read-only secret for a folder will contribute to the 'swarm' and upload/sync changes (they just don't have the key to decode and view said files). Same if you add another fully standard computer to the swarm the encrypted
  15. 1) Not at this time. Take a look through the feature requests forum for this topic. 2) Not at this time. Although, read-only users can only see the read-only key. 3) Currently sharing (meaning online) clients and folder show up on the Win client under 'devices' however it doesn't specify if they have full-access, read-only, or encrypted secrets being used. The linux webUI lists active clients under each folder. 4) Not at this time. Again take a look at the feature requests and add your vote to those items you would like to see implemented. You can also use the btsync log but will have to par