• Posts

  • Joined

  • Last visited

TimCinel's Achievements


Member (2/3)

  1. The Android reviews. The iOS reviews. The twitter metions. This thread. Oops, you Sync guys really dropped the ball on this one. Pretty hilarious.
  2. I've been using btsync since the alpha and am a bit disappointed. I think the 10 folder limit is completely artificial and agree that it's feels 'sleazy'. In my case, I have 15 and am not using it for business purposes, most of them are for sharing with friends and family. I'm not interested in paying an annual fee for this because I host all the infrastructure! I'd consider paying for a license for each major release. So I won't be upgrading. Soon, I guess I'll have to run the following: git clone git@github.com:syncthing/syncthing.gitBecause now I have a good reason to.
  3. It's really improved in newer versions, iTerm is even using more power than btsync! Ha.
  4. I've just installed the new version on OS X and Linux and think it's pretty good. I might actually be able to get my family members to figure out how to use it now =)
  5. Do you have UPnP enabled on your modem/router? That's my guess. As to why this node is connecting to you, perhaps you're acting as a STUN server (relay node).
  6. Less than 16 GB over 8 folders. Image Neato, I'm excited! If you could also include the protocol spec with the next update, that would be great. Thanks!
  7. This is targeted at the developers more than anybody. BitTorrent Sync tends to use too much power on OS X. The newest version of OS X, 10.9, makes it easy to quantify which processes are wasting power with it's new "Energy Impact" metric in the Activity Monitor. The latest version of Sync has an average impact of around 3.5, I very rarely update my Sync folders, so Sync is almost always idle (screenshot). To give some perspective, Dropbox has 0.3, Skype has 0.16, Mail.app has 0.43. On the other end of the spectrum, Chromium sits around 4.96. IMO, BitTorrent Sync should be much closer to processes like Skype and Dropbox than to processes like Chrome, especially when there is no sync activity. Earlier versions of Sync would sometimes become runaway processes, I noticed, almost maxing out the CPU. At least this seems to be solved for now. Anybody notice that BTSync is a bit of a battery-drainer? P.S. AFAIK, the energy impact is a ratio. That doesn't invalidate my argument.
  8. Just did the same thing. I'd say it's more iOS's fault than Sync's. I mean, we can't expect each "file manager" app to implement its own music player, video player, photo viewer, text viewer/editer. The Sync app works extremely well for music, video, documents and everything else on Android, so it's just another reason for me to choose an Android device next time =)
  9. Unfortunately, I don't think it's likely. Contacts are represented as files in OS X's Contacts application: /Users/{User}/Library/Application Support/AddressBook/Sources/{Address Book Hash}/Metadata/{Contact Hash}\/ABPerson.abcdpHowever, I think contacts are only stored in sqlite databases on iOS: /var/mobile/Library/AddressBook/AddressBook.sqlitedbThere were no results for files ending in "*.abcdp" on my iOS 6 file system =( Therefore, even if you could sync arbitrary files on iOS (i.e. jailbroken), it wouldn't work because storage mechanisms differ between iOS and OS X. Mac OS X 10.9 and iOS 7 both allow CardDAV syncing. Worth noting that there a bug in the account setup process in iOS 7, a simple workaround[1][2] is required to get CardDAV working again. [1]: https://discussions.apple.com/message/23375060#23375060 [2]: https://github.com/owncloud/ios-issues/issues/103
  10. On each machine, open BT Sync, go to the "Folders" tab, right-click the folder, and click "Show folder preferences". (Alternatively, modify your `sync.conf` on each machine accordingly, if you know what I'm talking about) Disable the following: Use relay server when required (use_relay_server)Use tracker server (use_tracker)Search DHT network (use_dht)Enable the following: Search LAN (search_lan)This should limit BT Sync traffic to machines within the LAN. Confirm that network traffic isn't leaking by enabling Debug logging and tailing the log file. Don't forget to turn off logging when you're done. Feedback on this advice is welcome.