nils

Members
  • Content Count

    238
  • Joined

  • Last visited

  • Days Won

    5

About nils

  • Rank
    Advanced Member

Contact Methods

  • Website URL
    http://thx.tel

Profile Information

  • Gender
    Not Telling
  • Location
    UK
  • Interests
    engineer, kopimi, p2p enthusiast, teaching, BTC bucket 1nHT5XLcDdrFdZvRytGLXqFA6qNzA3bDW
  1. You could have a netatalk share as Time Machine network backup drive and then on that machine have a sync instance running, which backs up your data offsite. In addition you could then set up a VPN allowing you to make ™ backups on the road (given the internet speed is fast enough). With this, you get a nice networked solution, which itself is then synchronised to another server. This will alleviate your problems with users on the Mac, as you could easily run the btsync instance with the same user that has access rights on the netatalk server
  2. @elpo RTFM, thank you Yet, I would have expected this to be mentioned in a changelog and not just a README? I updated from 1.4.83 to 1.4.9x and this was not explicitly mentioned.
  3. Since version 1.4.9x the web ui on FreeBSD does not seem to work any longer on the default port 8888. Any thoughts on this? EDIT: I tried lynx on the console of the FreeBSD server running btsync and was able to get a connection with cookie prompt on 127.0.0.1:8888 (no UI though), but no connection on that port for the external IP.
  4. The UI problem, where the main window can be resized and then hiding the share and pref buttons on the far right. NB: I reckon this has been mentioned before, but the 1.4.x UI window is horrendously large on machines with small screens e.g. 13", taking up almost the entire screen. A setting for text/general size would be a nice-to-have.
  5. In OS X, it seems resizing can hide the rightmost icons for a share i.e. the share button and the three dots for preferences. This seems like a bug or should be fixed. I would not expect these to disappear when shrinking the main window.
  6. into the IgnoreList file. Also delete/comment out the streams in the StreamList files, to make sure that the streams are not included (not sure if BTsync handles this automatically or prioritises the IgnoreList over the StreamList, therefore deletion of streams will make sure it stays the way you want it)
  7. Some thoughts on the new WebUI: It is nice to see a convergence of UI elements, in this case the folder icon on the UI matches the iOS version, making it easier for new users.I do not understand, as already said, why the overall upload/download is at the bottom of the page. E.g. if someone has a lot of shares, the user will only find out about this by scrolling down. Why not implementing this at the top at the same level as +Add Folder and Preferences.The mouse-overs are nice, but I would still like the ability to see the same info per each share as before: connection status: direct/through relay, upload and download rates per each connected device.I know, that you are probably trying to make the UI as similar as possible, but it seems this UI is going one step forward in UI alignment and two backwards in terms of usability.
  8. Half and half: yes, you need a desktop to set up the share, which you then connect with your phone through a QR code. once you have done this, you could theoretically delete the share on the desktop and have it only running from your phone. Then you can connect new smart devices from your phone to the same share. You do not need to have a desktop/server version running in order for the phone node to work on its own.
  9. Although the mobile app versions support connecting with QR codes, they are not capable of creating their own shares. There used to be a quick method of sending files with mobile devices by selecting some files and creating a temporary secret, but this feature was unfortunately removed a few versions ago.
  10. Disabling DHT, tracker and relay should do the trick. If you want to get even more restrictive, disable LAN search and then enter the IP and port in the defined hosts setting. This should give you a LAN only sync.
  11. The setting you are looking for is called folder_rescan_interval and accepts values in seconds e.g. 600 = 10 minutes (also the standard value). You will need to use a config in conjunction with the btsync command. If you call the btsync binary from the CLI with the option --dump-sample-config you can get a config template and continue from there.
  12. I have disabled them in each share by excluding the streams listed by @RomanZ in my .SyncIgnore. The reason for this was the incompatibility of streams on cross platform shares, e.g. OS X xattr cannot be written on FreeBSD fs.
  13. - Scan QR codes on desktop version - get back the option to see and copy the read only secret in the iOS Photo Backup. Sending an email should not be the only option. (yes, I can create an email and copy the secret, but I liked it the way it was before.) - get back the quick sharing function in the iOS version, which enabled ad-hoc creation of sharing files with mobile users.
  14. In the API, the BTsync node's OS can be identified. This information could surely be used to discern between xattr supporting and non-supporting OSes and make the syncing behaviour change accordingly.
  15. To my knowledge this is not possible with the current desktop version of BTsync. However, when looking at the iOS btsync client, the camera backup works that way: cow can delete camera photos on the iPhone, and they will stay on the receiving end, which is a RO client. I would very much like to see this behaviour implemented in the desktop app, as this could then easily be a backup node, where files get dumped and overwritten only, but not deleted if removed from the master.