• Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by nils

  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. 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 (no UI though), but no connection on that port for the external IP.

  3. 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.
  4. Now with, i have to put this in ignorefile or streamlist ?

    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)

  5. 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.

  6. So in a nutshell, I'll always need a desktop since they are the only ones who can generate the secrets and allow the connections to happen?

    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.

  7. 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.

  8. - 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.

  9. If you have 3 peers, 2 Macs and 1 Linux - Macs will sync xattrs successfully. But they will fail to sync their xattrs to Linux machine. There is a certain limitation on Linux PCs how xattrs should be named, so Mac names for xattrs does not conform Linux demands.

    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.

  10. There isn't any way to only synd added files? So when I add files they are transfered but when I remove them they stay on the other side?

    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.

  11. iOS client (currently latest 1.3.25):

    - I am not sure if it might have been slightly before, but there used to be a quick share option, which created a temporary share to exchange files between mobile devices. Why has this been scrapped, please bring it back, as I saw this as a viable if one is on the road and wants to share files quickly.

    - Thank you for adding QR codes on the iOS client, now I am able to connect other mobile devices with it as well. My wish now would be to add the option to generate a secret to set up a share initially on a phone. I have tried to input some random characters, but it keeps coming back as Invalid Secret.


    Desktop (Mac):

    - Make it optional to show the full path or have a mouse over/tooltip

    - Add sorting to lists, alphabetical for names, numerical e.g. for the share size



    - Make the config file the same for webui and manual operation, instead of using a database file when using the web ui.

  12. Hello vocatus,


    If memory serves me right, the maximum number of peers a single btsync instance can concurrently connect to is set to 50. This should not be a problem in a peer to peer network, as files should not be synced from a single location only, if a lot of peers have the same secret. This in turn spreads the network load. 

    In your case, you deploy packages i.e. all the nodes use RO packages, which should not be a problem if they are not connected to you, as they should connect to each other.

  13. There is one interesting release related issue here.

    In my experience and understanding, beta is basically a nearly stable official release of the product.

    At beta phase, no new bells and whistles are added and no new functionality and, especially, the changes of behavior are to happen.

    The very definition of term beta is bug fixes ONLY. It is a final problem resolution phase of the product.

    So, to me, to call this product beta stage is simply misleading.

    So, if BTSync still continues to develop and/or add all sorts of new bells and whistles, for marketing purposes or otherwise, it would be more appropriate to reclassify BTSync as Alpha state.

    In beta state, you are dealing with basically a releasable product where only the final touches remain in terms of fixing bugs ONLY. It is a state of the product when massive testing occurs with all sorts of test suites or otherwise.

    Thank you for highlight this, I for one did not know this. I think the marketing devision at BT has to change from the terminology of "beta" to "perpetual beta" instead.

  14. That is why I have excluded them in my .SyncIgnore on the Mac, as I am mainly syncing with FreeBSD servers for backups and do not need the xattr

    Since then, all shares are syncing without problems.

  15. @RomanZ:


    The config file already use JSON formatting i.e. it should be editable with some kind of library for config files.

    Is it not possible to make changes from the UI, which then get saved to the clear text file, rather than as a database? Vice versa, when I make changes to the config file whilst running btsync, changes could get parsed as soon as atime/ctime/mtime etc change.