ChrisH

Members
  • Posts

    247
  • Joined

  • Last visited

  • Days Won

    12

Posts posted by ChrisH

  1. This is as designed.

    Then your design is flawed. An upgrade (regardless of how big the changes are) should never lead to data loss.

    I (kinda) get the decision to use the simplest conflict resolution method there is - last added wins -, but that only works for changed files after the first initial sync has been done. For all other cases the user should be asked what to do (e.g. when adding a new folder with an existing secret there should be a option to decide whether to replace local or remote files on conflict), and like I said, a "simple" (for the user) update should not change the status quo.

  2. The main wishlist thread has become somewhat cluttered because all issues (protocol, features, UI, bugs) are mixed together.

    I would like to clear that up a little by starting a separate thread for all UI improvements, i.e. all things that can be made better without adding core features or changing the core behaviour of sync.

    Since I only use the Windows GUI, I cannot speak for Mac / web GUIs, but from what I could see on screenshots they should be pretty similar.

    Feel free to add your ideas or comment mine here.

    My wishes:

    • show the folder (number or short name) in both the "transfer" and "history" tabs
    • add a separate "queue" tab showing all yet unsynced files as a treeview per folder and device with options to skip / ignore single files (or maybe integrate it with the "transfers" tab?)
    • show conflicts / overwritten / deleted files in a separate tab with options to restore the overwritten version
    • show an ETA and/or overall sync progress
    • show a drill-down report at the "finished syncing with <DEVICE>" event so the user can easily determine what exactly was changed without having to scroll through the history tab
    • add an option to skip / defer a running file transfer from the "transfer" tab so more "important" files can be synced first
    • separate the GUI from the worker daemon so BTSync can run as a native Windows service (or use the existing web GUI also for Windows - whatever works)

  3. I've got a phone with small screen (3") and when I try to setup a sync I have to 1. Choose the folder and then 2. Scan QR code which I cannot do because I can't see any button to do it. I only get OK button which asks me to scan a QR code.

    Any one else?

    Same on my wife's Motorola Pro+. However it had an option to scale the app's interface so the QR button can be (barely) made visible.

  4. Lock/unlock is kind of complicated in p2p.

    Yes, but it's solvable. Here's my suggestion (including the read-encrypted-only wish from the wishlist thread):

    Have four secrets per folder.

    1) Master: Can approve new devices, and read and write cleartext. Device approval list is signed and distributed with the folder content.

    2) Read/Write (as it is now): Can read and write cleartext, but only devices on the approval list can connect.

    3) Read only (as it is now): Can read cleartext, and only devices on the approval list can connect.

    4) Store only: Can only read data in its encrypted form, and only the hashes or similar, not the original filenames.

    Each device should also have a unique key, guessing an approved device name must obviously not be enough.