• Posts

  • Joined

  • Last visited

  • Days Won


Quinist's Achievements


Member (2/3)

  1. Yes, the Phone is of course linked and I have multiple active folders that I can write to on this device. I'm using BTsync Pro but I doubt that makes a difference. I've managed to save a document in BTsync using the "Copy to Sync" function in the share action sheet you mentioned. "Save to Sync" causes Bittorrent Sync to crash when I choose the destination folder.
  2. Hello, The App is "Scanbot" (https://scanbot.io/en/index.html)%C2'> to reproduce I scan an image, press "iCloud Drive", choose Bittorrent Sync as the storage provider and get this screen:
  3. Hello, I'm trying to use the Bittorrent Sync document provider extension on iOS 9.0.2 with the at present latest version of the Bittorrent Sync iOS app and can't get it to work. Sync does show up as a storage provider option but when I press it, I just get a blank white screen themed like the iOS app that says "Location", "Sync", "Done" in the dark grey header with blue lettering. It doesn't actually show any of my folders which I could use as storage targets. Is this a known bug?
  4. Could you expand on this? I am a bit confused regarding the new licensing. I bought a subscription license back when 2.0 was first released and would like to convert it to a perpetual personal license. How do I do this? Does it get converted automatically or do I need to wait until this license expires (March 2016) and then buy a perpetual license?
  5. Hi, Today's OS X 10.10.3 update introduced the new Photos.app which is supposed to replace iPhoto on the Mac. I am not a big fan of Photostream, so I've used the BTSync camera backup function on iOS plus an automator folder action to automatically add new images into my iPhoto Library. This worked great but unfortunately Photos.app no longer provides an Automator action to import files. Has anybody found a good workaround yet? Do I have to give in and activate Photostream?
  6. Seconding this. The feature seems overdue.
  7. Oh please, just like 1024 bit PGP keys were "unbreakable in the foreseeable future", back in 2001. Or how 640 kB ought to be enough for everybody. Yes, and at that point I would lose mobile access and I could also store the data on other untrusted servers like Dropbox and the many other options. Don’t get me wrong, I’m not planning to save any highly sensitive data via Bittorrent Sync, but I still don’t want random people to go through my family pictures and random documents with almost no effort sometime in the future. An encrypted peer under my control with a long, self-generated secret seemed like the perfect tradeoff between security and convenience for me, but on a second thought, maybe I am stupid for trusting such a tight-lipped closed-source program with security/privacy sensitive features in the first place.
  8. I second this. I was really excited about the encrypted peer feature, but this is a deal breaker. To sum this up from my enduser perspective (I planned to use a VPS as an encrypted peer for somewhat secure cloud storage), please correct me if I am wrong: Unlike with other secrets is not and will never be possible to simply derive an encrypted peer secret from a custom, self generated base 64 RW secret. The only way to make use of the encrypted peer feature is to generate a brand new share using the "api?method=get_secrets&type=encryption" call, note down the three (RO/RW/ENC) secrets and use those for the peers accordingly.
  9. Encrypted peers seem like a feature that many end users would like to use for backing up data to an untrusted location. Is there a reason why you decided to "hide" this behind a developer-only API ?
  10. This is going to be a killer feature. An additional "encrypted read-only" secret would be so much cleaner of a solution than the various Truecrypt/EncFS workarounds. Thank you in advance!
  11. I would really appreciate if you could add this feature soon: That would be amazing for many apps like Goodreader or Jotnot (to upload and share pdfs/scans via BTsync) Thank you for your work!