benguild

Members
  • Content Count

    42
  • Joined

  • Last visited

About benguild

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  1. I don't know what's wrong with 2.0.93, but: 1) It's showing hundreds of ghost peers. 2) It locks up on my Mac and pinwheels in the background. 3) It's overwriting files coming back from another peer with older versions! This is a huge problem! The betas were fine, the launch version seemed fine, but now I can't even use it. I think this is it for me, sorry guys.
  2. Just updated to 2.0.93 (Mac) and have this issue with a test server that's running Linux. Honestly this software has gotten too complex for me and I'm kind of unsure on how to proceed. This seems like a beta glitch and I'm surprised that this version was released to the public. I've been using Sync for a while without issues like this. Any ideas? The program is locking up now as well...
  3. Certificate based folders? That sounds interesting, but who is the certificate authority? How are user access changes propagated?
  4. So if we have a couple of folders syncing between two computers with 2.0 installed, why do the folders still say 1.4 on them? I'm kind of confused as to what's happened with this "Pro" feature introduction... as I'm pretty sure that I don't need to upgrade for any reason but I'm afraid something will break after the 30 day trial. Can anyone clarify what is going on here? (P.S. I almost feel like I'm being penalized for being a beta tester now.)
  5. Is there a solution to this? I tried ignoring it but it still shows up in the pending items.
  6. 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.
  7. 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
  8. 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.)
  9. I agree that a solution like this would make sense
  10. Nodes were only appearing duplicated over LAN, not WAN. Cannot reproduce when connecting via WAN and therefore the logs are unavailable.
  11. 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
  12. 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?
  13. 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.
  14. 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