capi

Members
  • Posts

    70
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by capi

  1. I'd recommend "syncing" the new location in read-write mode from the first server, this way it becomes part of the sync network and no other device is effected by the new server.

    Simply moving the files may be a problem, as some meta-data is kept outside of the sync directory, as far as I know, but I might be wrong.

  2. I'd vote for a more rsync like behavior of the temp file while syncing, i.e for file file.ext, make the file.ext!sync a copy, and move to the original file (i.e overwriting/replacing it). This would be a huge benefit when syncing webpage content, as there'll be no 404 while a sync of a file is in progress.

    Along this line (requested by somebody else) would be the option to have this copy temp-file in a separate folder and not alongside the file, in order not to expose partially synced files.

    I do see the purpose of the current behavior for many scenarios though (i.e preventing someone from concurrently modifying the file, saving disk space as you don't end up using twice the space during transfer, etc.), so it would be very nice if this could be configurable on a per-folder basis.

  3. A small improvement I'd really like to see would be when adding a share via the Web-UI, allow to edit the sharing preferences before the share is created. At the moment, a new share is created with default settings (like tracker enabled, search LAN). If I want to use only known-hosts, I still broadcast to the tracker at least once during the creation of the share.

  4. What happened today when I started up sync again after a few days off, is that it forgot that I had Camera Backup enabled, it wants me to setup it again. The backup itself still works, as the Camera folder is still listed as sync folder in the "Sync" tab.

  5. This! I'm pretty new to Android, so maybe I'm doing something wrong, but I haven't even added a folder yet and I can't figure out a way to get rid of the tray icon. Is this thing running in the background constantly?

    It seems to be running until you select "Exit" from the menu in the application. I assume that they are running as high-priority service, which requires the display of a notification icon.

    What I still need to test is if there'll be image backup if the application is not running (i.e. if the service is started/triggered by taking photos) or not.

  6. Ah, one more thing:

    The image backup works a little bit unintuitively regarding deleted images (from my point of view):

    - If you delete a file on the device, it is also removed from the backup share.

    - If you delete a file on the backup share, it is kept in the device's gallery.

    For me, I would either make it a full sync (i.e. deleting on either side will also delete on the other side) OR write-only to the backup share, i.e. removing from device will not remove from backup share (in this case, it would really be a backup).

  7. I was also playing around with the Android version I got in my hands today and I really, really like it. It is great for a first alpha version (let's all keep this in mind :)).

    As feedback is the reason for us being alpha testers, I'd like to add the following thoughts:

    - Please add most of the options on a per-share basis (like others requested), i.e. cellular data yes/no

    - Add an option to a share to auto-download new files.

    - Add an option to whitelist WiFis to use for sync (on a per-share basis).

    - Add options to search LAN only / predefined hosts.

    - Add a schedule for each share when to auto-sync.

    - Add a possibility to remove downloaded files from inside the application (without removing it from the sync peers), i.e. distinguish between "Delete from shares" and "Delete from device only"

    - Add possibility (on a per-share basis) to sync while connected to power only.

    That's all that comes to my mind at the moment after the first few hours of playing with it. Thanks again to the whole team for this nice pice of software!

  8. Thanks for the awesome tool! What I'd like to get is an option to limit connections to/from the predefined hosts. If I disable all options and have a predefined host, the host will be used to detect other peers.

    As one of my clients is on a notebook which is often connected via GPRS/3G, I'd like to only connect to a predefined hub but not waste bandwidth and transfer volume to upload changes to more than this one predefined hosts.

    This feature would allow to build a hub architecture where a central server is used to collect and distribute changes, while some of the clients could also synchronize among each others.