ivarson

Members
  • Posts

    58
  • Joined

  • Last visited

Posts posted by ivarson

  1. As discussed here, if my Resilio config is compromised somehow, there's no way of revoking access for a specific peer/computer if I understand it right?

    I would really like to see a way to ban such machine.

    A revokation if that sort would (which I actually was in place) require ( machine ID + user ID ) = Peer ID.

    Probably a big change in how identities are built, but would it be possible in the futher?

    again, correct me if im wrong here.

  2. @Lost Copter

    Quite interesting observation. 

    Without knowing much about Sync's internals, when you're joining a machine with your identity you basically transfer at least the user certificate to that box, but I thought there were a machine certificate generated during join-process too. Unlink-process should then invalidate that machine cert so no other peer would accept it, sorta revocation. 

     

    Any official comment on that? 

  3. 26 minutes ago, Wierdbeard65 said:

    Ok,

    So before I started, I had:

    
    d:\Sync\FolderA
    d:\Sync\FolderB

    I backed up that folder. Swapped to the new OS Drive. Re-Installed BitSync. Restored the folder. Was prompted to enter my key. And...

    
    d:\Sync\FolderA
    d:\Sync\FolderA(1)
    d:\Sync\FolderB
    d:\Sync\FolderB(1)

    :-(

    Any ideas?

     

    sync appends (1) by default, if the requested foldername already existed upon 'linkin'. To avoid re-seeding anything you simply remove those paranthesis manually in the add folder dialogue, and confirm when Sync warns you that it already exists. the older folder will not get overwritten if its the same share, it would only be rehashed as @GreatMarko mentioned.

     

     

     

  4. 20 hours ago, hoochalaffa said:

    @ivarson What about a Browser Plugin? It could make it sending files to non-BT-sync-users so much easier? I started a post here.

    I think what I was trying to say there, was that installing a plugin is "sort of _like_ installing a standalone client. s/love/like...

    I don't like plugins in general but that discussion is OT :-)

  5. On 2016-03-01 at 4:46 PM, VDub said:

    I actually am having this very same problem.  I have an encrypted rPi setup, and was running btsync 2.2.x for months with no problem -- syncing to encrypted external 3TB hard drives.  After updating to 2.3.3, the btsync seems to crash every 30-90minutes. I can't seem to figure out why.  When i switch back to btsync 2.2.x, it seems to work fine...

    Is anyone else having this issue?

    I haven't got this issue before, it started yesterday. i turned overclocked to 1ghz and also installed plexmediaserver, which is pretty heavy.

    [12031.754019] Out of memory: Kill process 683 (btsync) score 460 or sacrifice child

    probably not Sync's fault here.

  6. You misunderstood. You're correct in that there's different behavior between device-button and app-button, but it's the device's back button I'm talking about. It steps one folder up but it jumps back to the top. Not an issue alone but when you have to scroll for 20 seconds and guess a folders name because of truncation, it's time consuming to have to scroll once again. But great to hear truncation will be fixed, then the scenario I'm talking about won't be an issue for me  anyway. Looking forward to it. 

  7. "To make this re-scan as lightweight as possible, Sync only checks for file and folder modification time and size changes. If any has changed, then it re-hashes the whole file to find out which pieces of files have actually changed and need to be synced.

    - http://help.getsync.com/hc/en-us/articles/205458185-Setting-how-often-Sync-should-check-for-file-changes-

  8. I've got lots of shares on my laptop, many of them has their destination on a removable usbdevice which isnt always attached, but there are some shares on C-drive too.

     

    When launching Sync and 15 folders are missing, its pretty 'bleepy' and flashy for a very long time.

     

    Although It's important to alert if a share isnt working, id like it to easier to work with. You could make the warnings cumulative, stop flashing in for so long in the UI etc.