[A Proposed Use For Btsync - Feasible?]

 

As for customizing the BTSync client. Since it's closed source, you cannot.

However, here's what you can do:

 

• You create your own application that implements all the API features required to for the functionality you want your client to provide
• You then ship BTSync with your application (either as an embedded resource or as part of the installation package)
• Your client starts BTSync without a UI and controls it using the API
• The only piece of software your users will see and interact with is your own.

This is also fairly simple to set up.

 

That's exactly what I'm doing right now, except that I'm also wrapping the key exchange so it is seamless for the end user. Allows for sharing of projects online and allowing them to be automatically added to the sync client of the user.

 

And I can confirm that this, as described, is easy to do. Have a nearly (~80%) completed app on OS X after a couple of days work.

[Sync API wishlist]

I'm trying to write a wrapper around BTSync using the API so I can handle all the shares programatically.

 

I'd like to see the config being passed as value to the app in an argument rather than only as a feel on HDD. This way I can keep my api key hidden away when I pass the parameters to the app at startup.