• Content Count

  • Joined

  • Last visited

  • Days Won


About delegatevoid

  • Rank
    Advanced Member

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
  • Interests
    .NET/Mono development targeting anything from embedded, mobile and desktop devices all the way up to the cloud.

    Languages such as, but not limited to:
    C#, F#, (Iron)Python, JavaScript, ...
  1. It's a bullshit move. We (the entire community here) have been testing and providing feedback for btsync since the very beginning. I'm sure there are many like myself who have set up many sync folders, moving from other services such as Dropbox, GDrive, etc... to BTSync because of the promises made by the Bittorrent team. And now they want to limit us to 10 folders (which is a purely artificial limitation) unless we cough up money for every device in our sync setup? This doesn't just affect business users, it affects all users. Of course they have every right to make money (and they should)
  2. This is rather important isn't it :-) Otherwise no commercial product would ever be able to support BTSync, so they'd only be able to support Dropbox, GDrive, OneDrive, etc, etc....
  3. The problem is I'm letting do the parsing automatically, don't feel like doing it manually just because the BTSync team fix it. It still feels like this whole thing is someone's pet project :-)
  4. If you look at the preferences in the latest version of BTSync, the values of some settings are being prefixed with "*", even though, when you set them, they are pure integers. I've no idea what the meaning of this "*" is, but what I do know is that it breaks the API. If you look at the JSON returned by the API: You'll see it returns "*" as part of some values which means they can no longer be parsed as integers which in turn breaks the clients.
  5. It would be nice if would link to a page with a list of API implementations per programming language/platform. Since I assume the BTSync team has their hands full at this moment, it would be best if the community could manage this page. A forum post would be one option, but I'm pretty sure it'd get messy real soon. The API is great, but it's not for every developer and I don't think everybody should try to implement the API from scratch in their favorite language. Showing potential developers a list of available implementations might push the
  6. Just a quick note/update: At some point the package on was outdated, but once you've installed the package, you can simply overwrite the binary on the NAS every time a new version is released. Works like a charm.
  7. This was one of the first things that jumped to mind when I learned about the encrypted keys. - You set up a service where users can sign in - They would then be able to enter their encrypted key and the btsync on that server would start "backup up" their files - They could be charged by volume (since a storage service is being provided to them) - They could be charged by allowing others to sync data on their system Same applies to managing backups within a company. It's easy enough to set up one ore more backup servers and then allow users to sign in and add their various keys to
  8. You will have to create the folder prior to adding it to BTSync, that of course is easy enough to do - If the specified folder does not exist create it - Add the newly created folder to BTSync Windows, MacOS, Linux, basically any desktop platform on which BTSync works, just not the mobile versions, since they don't currently expose an API
  9. It's possible on Windows, Linux and MacOS. Only the mobile versions are different.