RomanZ

Thank you for your interest in the Sync API and being part of our developer community. The varied ways you’ve leveraged Sync’s technology are inspiring and we’re excited to continue to enable them. We want to let you know that in June we’re planning an update to our API. This update will bring significant new functionality to the API, including access to 2.0 folders for all the existing calls. We’ll provide you with updated documentation and much more information around these features when the new API launches, but wanted to keep our current API users informed All calls using the existing API will continue to work at minimum through the end of 2015 to provide you with time to transition to the new API. We will continue to stay in touch before any changes to the existing API are made.The new API will require a new Sync build, which will be released at the same timeWe’re aware of interest in the API for mobile use, but this functionality will not be in the planned update.The API will continue to be free to use for non-commercial use. We sent all of you an email with this information, but wanted to post here as well to make sure everyone was kept aware.

@eldrin Sorry about that, missed your question. It is going to be okay. Both x64 and x86 are using same storage location and reuse it with no issues. @josh4trunks @PacketMan We ddon't have official FreeBSD ports. If you take a look at the maintainer name, you can see that the person is outside of BitTorrent: joshruehlig@gmail.com @andrewb That's rather strange. Sync 2.0 has icon in system tray - and this code did not change. Is it reproduced stably?

@hugligan Should be working fine (with minor cosmetic issues) on Yosemite. What exactly is not working? @GJames Well, actually Sync does checks if current OS is going to support 2.0 or not. So, Sync is only displaying update for Windows with core 6.1 and newer. Although. it seems that this is not true for non-supported OS X. Thanks for reporting, we'll fix it. This does not require client update, it is more related to the update server.

@tjluoma It might be indeed some conflict between Sync and BBEdit. Could you please provide the sync.log and *.journal files from your Sync storage dir (for precise location of storage folder per OS see item #3 here)? I've opened a ticket for you so you can attach it there. We'll take a look why it happened ASAP.

@Revearti Yes, you can. Just note that you'll have to setup folders from scratch and apply your license again. @Dj.Bea We want to implement it in future.

@aduermael Sync 2.0 has CLI, though its rather limited and won't allow you adding folders or alike. I'd advise using API for that - and yes, at the moment API only supports 1.4 functionality, so you can only operate 1.4 folders. We would like to extend API functionality to cover 2.0 features as well, though I can't share any precise plans or ETAs at the moment - sorry.

@eldrin Yep, we are aware of this issue. Will be fixed eventually. Currently user has to choose himself for the x86 / x64 build. @merlinuwe Searching over internet indicates that Medion Lifetab has Intel CPU onboard. Unfortunately, Sync currently only supports ARM processors and won't run on Intel. @PacketMan We'd like to get into official FreeBSD ports tree or Linux repositories in future, but its not in the closest future plans.

@urza Let me comment out. It is not true starting from version 1.4. Sync v1.4 can generate a link which requires explicit approval from resource owner to actually share the key. You can see this article for more details on how it works. Sync 2.0 has even more advanced protection and no longer operates key, but uses X.509 certificates instead and can revoke access to already existing share. At the end of day open source also has to be trusted: vast majority of users have no skills to verify what was written by devs. As well, majority of developers have no security verification / penetration testing skills to verify that code is secure and ensure that no other devs managed to deploy a well-hidden backdoor. A heartbleed vulnerability in OpenSSL would be a good sample here. Also, as topic states - security is really our top priority. To ensure that Sync is implemented in a secure way, BitTorrent passed a security audit by 3rd party company (iSEC Partners). So yes, BitTorrent Sync is secure application.

@rupert Mostly because of iOS itself limitations. Current status is pretty much the same - we are aware of the request in this branch, though can't provide ETA or any plans for iOS API.

@gurkesaft I believe you got the response from our support - I'll duplicate here for other users. Unfortunately, Sync 2.0 is no longer supported for OS X 10.6 and older due to new features and security used in 2.0. OS X 10.6 has very small amount of users and Sync Team decided to concentrate on more popular versions of OS X. I apologize for inconvenience.

@2disbetter Unfortunately no workaround for this issue. As Sync stores its data in binary format, you can't edit it with text editor as it is going to ruin binary data. We know about this issue and plan to address it to future releases. Also note, that Sync automatically cleans up old devices after around 30 days being offline.

@HeliosOmega 1) The pricing model and amount was commented by our VP, Erik Pounds. 2) We are working to make it easier in future releases. Many users complain on complexity of devices management. 3) Yep, we are aware of it. Current workaround for changing the key would be re-adding folder.

@stevenkasapi I've opened a support ticket for you. Please send you debug logs there.

@aero-super Sync stores directory trees available for syncing in internal DB, and its size proportional to amount of files and their volume (as it also stores hashes for all file pieces, files themselves and directories). There is an option in Android to move application to external storage - you can move your Sync to ExtSD to not to occupy precious internal storage space. Just don't forget to shut Sync down before moving.

@petra There is no mechanism to hide peers list directly, although there are some tricks you can do to avoid other peers to see anyone except server. Option 1. Get rid of UI and run sync in config mode. Not very convenient for end user, although it will be easier to deploy Sync and users won't see any other peers. Option 2. Disable tracker / relay / LAN search / DHT on clients. Preconfigure your server's IP / DNS name on your cleint's computers in folder preferences. Reset Sync's cache of contacted computers. In this case your clients will only be able to see central server - though, they will also lose a great advantage of helping each other to send / receive data.

@all, If someone of you got large amount of .journal files - i'll be happy to take a look on what happens inside. They should stay rather small as they contain only limited amount of operations on some selected folder. Please PM me and I'll share uploading link.

@2disbetter QNAP will update their repository soon. Although, its a bit strange they are not in our Help Center - I'll check it.

@zorza I presume, you mean - to move file from folder with one key to a folder with another key? If I'm correct - then no, it is not implemented and not planned. Sync (or Sync API) does not moves files between Sync folders. It is completely out of its design.

@verleihnix Yes, if 1.4 Sync version is 1.4.110 and newer. Older version may not work well with 2.0. Yes, you can setup 2.0 server. API is same as it was in 1.4. 1.4 clients can connect there - if they are 1.4.110 or newer. Well... yes. See above. 1.4 is not capable of dealing with 2.0 folders, though. @vladr Support is loaded now and it takes a while to respond to everyone. The API is supported and working, though it does not cover all new features. If you encounter some issues with it or API documentation - please report and they will be addressed. Note, that help center moved here, don't confuse it with old location.

Unfortunately fix is not in 2.0.105 yet - but planned on next update (no ETA at the moment).

@redbird71 It depends on users amount & usage of your big folder. 1. If you use it for personal use and only for yourself - you don't need a license (unless you want to use PRO features). 2. If you use it alone for business use or want PRO features - you'll need 1 Pro license. EULA allows only Sync Pro for business use. 3. If several users use it for business use / or require PRO features - you'll need amount of licenses equal to your users amount. You can read more in this article on our Help Center.

@trbvm There are technical issues with Sync 2.0 running on 10.7. Due to low amount of users we decided to cease support of 10.7 and direct our efforts to make Sync better for more popular OSes. I would also appreciate more constructive posts without false accusations in future. @AzimutTheUt 2.0.105 for Synology and other NASes are available now on our Help Center.

@mumen The link was sent already. Methodology is correct. For android just send a feedback and agree to attach debug logs (they are always at debug level). In android's feedback mention something that will help us to find it and link to your issue (forum topic link or your nickname would be enough).

@Electronic_Lad I don't have any sample at my hand, but its rather simple. When Sync runs in API mode - it opens a TCP socket on whatever port you configure. Your app should connect to this socket and send HTTP requests there. You can even try to do it without any programming via simple browser - API will respond you.

@Syveren, We don't have a per-folder speed API call. I can advise 2 ways: 1) either use get_speed API call - though it is per whole app, not per folder 2) or try to check the get_folder_peers call. It indicates the amount of data to download and upload in bytes.