benguild

Members
  • Content Count

    42
  • Joined

  • Last visited

About benguild

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  1. Mac OS X Yosemite has "dark mode" and currently the BitTorrent Sync icon looks nearly just like a flat grey circle. Would be awesome to have an icon variant bundled to support that correctly.
  2. I'm curious about these cloud solutions but not sure what's good. The problem I see is that BitTorrent Sync is pretty limited in adoption and understanding right now ... (not to mention beta and sometimes unstable) ... so I'm wondering how anyone can really sustain an operation's development needs and costs beyond it being a simple hobby. With that said, if it is someone's hobby, I wouldn't mind paying a dollar or two a month for a bit of storage to try out? Hmm
  3. I don't understand what the different between the new sharing features are and the older key exchange. For example, I'd like to have to approve new machines to sync with mine ... and be able to revoke that approval later. Is this only on the new "sharing" system? Is this through a centralized server or authority? How does it work? (with Linux machines, etc.)
  4. I agree that a solution like this would make sense
  5. Nodes were only appearing duplicated over LAN, not WAN. Cannot reproduce when connecting via WAN and therefore the logs are unavailable.
  6. For me it's still doing this... if I disconnect from Wi-Fi for even just 10 seconds when I reconnect it says it has to reupload entire folders and eventually cuts through the entire filesize to "synced" after like 20min... but in the process it's resending all of the small files that are too small for analysis vs. transfer. Seems wasteful. Dropbox syncs instantly
  7. Screenshot attached. There are only 2 devices on these test folders. The rest are all duplicate devices that often appear instantly. From the logs I can see that the other clients are making like numerous inbound connections at once so I wonder if it's accepting multiple ones for the same folder at the same time?
  8. Very strange. I tried downgrading the other nodes to .105 but even with this, .106 still reports multiple nodes of the same machine/folder and with different statuses. OK weird, even after reverting to .105 on Mac it's still doing it. This has only been an issue since updating to .106 on all nodes and then trying to revert nodes one by one due to it.
  9. I've noticed that if I have sync paused and then tether my iPhone it begins syncing automatically. This is not ideal. Worse, I have to go into the context menu and uncheck "pause" and recheck it to get it to pause again. It still thinks it's paused but goes into zombie sync mode or something
  10. Right— However if the second key is of a variable length vs. the first being of a fixed length for simplicity and branding's sake... then that's different. Another way to treat this might be to treat the secondary key as a data encryption key ... where perhaps without it someone can connect to your "stream" just by having your secret, but won't be able to actually decode anything otherwise.
  11. Brian— 105 is the best build I've tried so far. My recommendation for you is to backup your synced folders and then completely clear out ~/Application Support/BitTorrent Sync/ to reset your sync state. I've noticed that when a Linux instance crashes a few minutes after launching that this is the only way to fix it. (just a complete rekick)
  12. I considered building a simple web script that spun up "btsync nodes" or whatever... but honestly in hosting the margins can be razor thin and with BitTorrent Sync in beta (and not always stable) it just seemed like it wasn't a good time or anything. plus to be honest all I'd pay personally is like $1-$1.50/mo for a small amount of storage of like essentials. I've got my eye out for something simple and managed but right now it seems like all there is are cheap VPSes that happen to bundle more disk space than another for the same price
  13. ref: http://forum.bittorrent.com/topic/29854-if-you-restore-from-a-backup-would-sync-overwrite-the-newer-files-on-other-nodes-with-backed-up-copies-or-pull-newer-copies-from-other-nodes/
  14. If it crashes you might need to dump the data directory and start over