• Posts

  • Joined

  • Last visited

Recent Profile Visitors

949 profile views

voz's Achievements


Member (2/3)

  1. Hi. Is there a way to see some stats for the Sync client running in the API mode, starting from the date it was installed. For instance, the total size of the data transferred (uploaded/downloaded) or the total number of folders that were added. I'm writing a report on the Sync usage and that would be useful.
  2. @RomanZ I have sent a PM with the log
  3. @RomanZ thanks for trying to help I've put --nodaemon and no logs appear, the same as without it. I run /Applications/BitTorrent\ Sync.app/Contents/MacOS/BitTorrent\ Sync --nodaemon --config /xyz/system/btsync/btsync_config.json from my terminal, it launches the Sync, but there is no output in the terminal.
  4. @RomanZ, thanks for the info.
  5. @RomanZ I've tried cleaning the cookies and also the anonymous mode of Chrome, the result is the same. Yes, I make a call for a token every time. I've also tried removing and installing again the Sync and specifying a clean metadata folder, it did not help.
  6. Hi, I use an evaluation API key for building an application around the sync API. Till few days ago everything worked well and I was able to call the APIs successfully. Now when I start the Sync on one of my machines with a config file (please see below), I can not open, it just shows "Invalid request". I get the same response on all API calls on that machine. This behaviour is the same across browsers: Chrome/Safari/Firefox. Interestingly, on other development machines everything works well and the APIs work as expected. So the evaluation key seems to be valid (it should still be valid for another 3 month). We run: Mac OS 10.11.3 Sync 2.3.1 (259) Any idea what could be the reason? Could it be related to the fact that I am using an evaluation key or it is something else? My config file as it is: { "agree_to_EULA": "yes", "device_name": "xyz-server", // path to folder where Sync will store its internal data, // folder must exist on disk "storage_path" : "/xyz/system/btsync/metadata", // run Sync in GUI mode "use_gui" : true, "webui" : { // IP address and port to access HTTP API "listen" : "", // login and password for HTTP basic authentication // authentication is optional, but it's recommended to use some // secret values unique for each Sync installation "login" : "abc", "password" : "def", // replace xxx with API key received from BitTorrent "api_key" : "MY-API-KEY" } }
  7. @RomanZ thanks for the information, now we manually manage folders when file-related events come. This adds a bit of overhead, having remote folder-related events would simplify our life. Just to plan accordingly, is it something you consider implementing later on, or there is no big demand for it?
  8. Hi, I'm trying the api and everything works well till now. I'm handling the file-related events (EVENT_REMOTE_FILE_ADDED, EVENT_REMOTE_FILE_REMOVED) so my app knows when files are created or removed by other peers. Now I want to do the same for subfolders, even when they are empty. I see that empty subfolders are synced but no event is fired. I would expect to have the same EVENT_REMOTE_FOLDER_ADDED and EVENT_REMOTE_FOLDER_REMOVED as I have for files. Am I doing something wrong or you do not have subfolder events implemented at the moment?
  9. +1 for the list of errors. This is important to make proper error handling in our libraries.
  10. "If we see that particular key abuses something" @kos13 Could you please elaborate on things that you would consider as an abuse? I seem not to be able to find it anywhere.
  11. I was able to run on Mac OS 10.9: $ /Applications/BitTorrent\ Sync.app/Contents/MacOS/BitTorrent\ Sync-config ~/btconfig/config.json Make sure that you have the latest version of the client.
  12. In general it would be great to have a 'webhooks' api for a set of btsync events, with ability to add, modify, remove webhooks. For instance, I would like btsync to post to my web-app a json with information about newly synced file.
  13. Have the same experience. I would expect to be able to get an encryption secret by providing an existing secret. Or are we missing something?
  14. +1, a really needed feature in my application