wimbit

Members
 View Profile  See their activity

  • Posts

    66

  • Joined

  • Last visited

  • Days Won

    3

 Content Type 

Posts posted by wimbit

  3. 1.4 And Beyond -- How To Generate Encrypted Read Only Secret?

    in Sync General Discussion

    Posted

    Since 1.4 there is a much simpler way to generate the encrypted read-only secret. No more counting characters etc..

    Add the new folder, go to the folders preferences, show the keys with “View key”, copy the “Read & Write key” simply by clicking “Copy”, click on “Update key…”, paste the key and change only the first character from A to D. Hit “Update” followed by “Close”. Open the folders preferences again. Now you can see all three keys under the folders preferences.

    I tried that. But the RW key is now 33 long, the Read only key is the longest, and the ERO is 33.

    Is that correct?

    See below, the keys are disposed of so don't mind sharing this:

    dc322620c27cc8ca3f9fe9262e72842f.jpg

  6. How Are People Using Sync 1.4?

    in Sync General Discussion

    Posted

    You guys should listen to this guy quoted below -- He makes sense and his thing about users actually willing to send money your way is not far off.

     

    And sheesh ... what happened to 'easy' -- How do I make an encrypted read only secret again?? (without some complicated API)

     

    You want to make money, make it easy. The whole secrets sharing thing got exponentially complicated and burdensome in the latest versions.

     

    Just let me know when you set up that bitcoin account so that I can send you some money. Thanks :)

     

     

    Agree. The Android update ruined it and the windows update UI is buggy. Also, I get lots of peers showing with the same name. This was not tested as much as it should have been. Everything was running very smoothly for quite some time until the latest version. My Android devices, I just removed it because it was not working properly. Sucks to say, but you had a good product before the new version and you made too many changes at once with the new release. Go, get a fresh coffee for the head developer and tell him/her to get it all working again. Thanks!!

     

    OH, and here is what you don't realize ... 

     

    I don't mind paying even for BTSYNC!!! It is that useful and I would gladly pay a small fee each year or make a donation. I have no idea how you plan to monetize this, but you can if you ask people, and then make it a better product with the funds. 

     

    Maybe you guys should think of making a public BitCoin account for receiving donations.

     

     

    But don't release shoddy versions and then ruin a fanbase that was getting quite pleased with the way things were working.

     

    My 2cents :)

     

    'cause I'll gladly send you $10 if you promise to test better next time :)

  8. Latest Desktop Build 1.4.83

    in Sync General Discussion

    Posted

    I have upgraded every machine to 1.4.83 and re-configured. OK, it is working fine. A few finagley things but otherwise much better now.

    The links from the Android app do not work so no 'backup' yet. But I just scanned the code using the Android app and it worked the other way as a normal read-write. Also, I have a few folders that I can only get a read-write and read-only key for. They refuse to show an encrypted read-only secret for some folders.

    That's all, I am over my initial grief with all the changes.

     

    It is looking better. Keep going guys 
    :)

  10. How Are People Using Sync 1.4?

    in Sync General Discussion

    Posted

    To address those that are communicating serious frustration with the product, understand that we knew there'd be some individuals, certainly those we consider advanced users, that would see the UI overhaul as a step in the wrong direction. 

     

     

    The UI is fine, but buggy. But what is bad is, the sync itself broke.

     

    The Android update broke the sync. And the PC update, it also is buggy, shows lots of peers that do not exist, syncing never ends, etc.

     

    This is not a UI issue, the sync itself was not thoroughly tested before release. The sync itself broke and that is what is frustrating.

     

    As I posted elsewhere, people actually like sync, and would even support it as a paid product. But not if you keep breaking it. This is not the first time that an update has broken the sync itself and then it needed major user intervention to get things working again. But it was stable for quite some time.

     

    As they say in software circles, release often and test test test. But you made a lot of changes and then, with One-Big-Update , made it difficult for you (and us) to know what is working and what is now broke.

  11. How Are People Using Sync 1.4?

    in Sync General Discussion

    Posted

    Agree. The Android update ruined it and the windows update UI is buggy. Also, I get lots of peers showing with the same name. This was not tested as much as it should have been. Everything was running very smoothly for quite some time until the latest version. My Android devices, I just removed it because it was not working properly. Sucks to say, but you had a good product before the new version and you made too many changes at once with the new release. Go, get a fresh coffee for the head developer and tell him/her to get it all working again. Thanks!!

     

    OH, and here is what you don't realize ... 

     

    I don't mind paying even for BTSYNC!!! It is that useful and I would gladly pay a small fee each year or make a donation. I have no idea how you plan to monetize this, but you can if you ask people, and then make it a better product with the funds. 

     

    Maybe you guys should think of making a public BitCoin account for receiving donations.

     

     

    But don't release shoddy versions and then ruin a fanbase that was getting quite pleased with the way things were working.

     

    My 2cents :)

     

    'cause I'll gladly send you $10 if you promise to test better next time :)

  21. Dealing With '.conflict.' Folders

    in Sync Troubleshooting

    Posted

    ".conflict gets added to the file when couple of files / folders attempt to be copied to a single file / folder. For example - same filename with a different letter case on Unix would be 2 different files, while on Windows it is the same file."

     

    This is not the case with my circumstance. The machines were previously in-sync using v1.2.87 prior to the update to 1.3 and prior to any folder secret reassignments. The problem started with Windows before Unix was added to the equation. So, has to be something other than a filename issue.

  22. Dealing With '.conflict.' Folders

    in Sync Troubleshooting

    Posted

    Sure.

     

    I have 6 machines, 23 folders with own secret (each main folder has own secret to avoid security exposure and make things complicated:) )

     

    EROS = Encyrpted read only secret

     

    1 NAS Debian, PowerPC (EROS everything since NAS is not encrypted)

    1 PC x86 (EROS most folders,some full secret)

    1 PC x64(Full secret all 23 folders)

    2 laptops x64 (Full secret all 23 folders)

    1 Android (5 folders, full secret) ** Had no problems here and still on 1.3. Also, no '.Conflict' folders here.

     

    Ok. So .. everything was using full-secret, fully synced.

     

    1) I updated NAS by (a) turned of btsync service ( B) deleted all folders © installed 1.3 btsync (d) turned back on. Nothing on machine, no secrets yet.

     

    2) Updated 1 laptop to 1.3. Removed all folders syncing and re-added folders with new secrets with 'D' prefix.

     

    3) Update other laptop to 1.3. Did same (2), removed all folders syncing, and re-added with 'D' prefix secrets.

     

    4) with x64 PC, just changed the secrets to 'D' prefix without removing and re-adding sync folders.

     

    .. by this time I was noticing '.Conflict' folders appearing.

     

    5) Eventually had x32 PC and NAS on with EROS secrets and syncing. No crashes on PowerPC, only x64 and x32 PC and laptops.

     

    Proceeded to get all updated and eventually stable. But a lot of crashes along the way.

     

    I assume this had nothing to do with filename case as postulated, since the sync already existed and all filenames were as original. All I can think is that the conversion to the new secret, and keeping the folders on each machine, something got buggy with filetimes or the way sync think 'which was first'.

     

    Hope that helps. Now, off to write a groovy script to amalgamate a bazzillion '.Conflict' folders and clean things up :) Oh, yeah, have someone document the '.Conflict' folder thing, pleaseeee!

  23. Bittorrent Sync 1.3

    in Sync General Discussion

    Posted

    Wimbit,

     

    Thanks for the feedback and for the crash reports. Let me know if you are willing to help us with 1.3, so I can instruct you what kind of debugs we need.

     

    I'd love to help. But I am depending on this now and although Beta status, have been for the last year with about 750GB of data. I've reverted now. Next round of updates I'll give it a shot. 1.2.92 no crashes yet and also fine with my MyBookLive NAS machine :)

  24. Bittorrent Sync 1.3

    in Sync General Discussion

    Posted

    Nickluck,

    Thanks for reporting. Seems we identified the root cause of both crashes and LAN issues, I'll update the forum soon.

     

    unsignedint,

    Thanks for proposal - we'll consider making an option to disable xattr sync.

     

    Stanha,

    I've got your feedback about beta status and folder list. For folder list - it is in discussion now and is likely to be changed soon. Also, I would appreciate your feedback in more compact form for future. Thanks for understanding.

     

    pjmsullivan,

    I'll pass by your thanks to devs team :). Are you using tracker to connect your PCs in different LANs or you have properly set up routers which let multicast pass?

    wimbit,

     

    For crashes I would appreciate crash dumps. Could you please share more info on what is not syncing? Also, which other problems are you facing?

     

    Thanks for the reply. I posted in another thread also about the '.Conflict' folders. This has made a real mess of things and might be unrelated to 1.3 but a problem/feature that should be addressed somewhere.

     

    1.3:

     

    a) the UI freezes. Happens when switching tabs/adding folders and also seems randomly.

     

    B) The sync just crashes, sometimes on indexing, sometimes while running.

     

    c) The sync is not complete. Even after syncing everything and finally having a stable image on all machines (2 encrypted-read-only machines and 3 full secret machine, all local LAN) it still found more to sync after I reverted to 1.2.92. So, I assume 1.3 actually did fail to sync everything even when it supposedly did.  And yes, I even restarted machines and verified the sync status several times. 

     

    That's all. But enough for me to doubt why I would want 1.3 at this point and also the crashes as rather disconcerting/annoying.

     

    Also, I have already submitted several of the crash dumps on my machines via the automated crash reporting tool.

     

    ... Putting all back to 1.2.92 and I'll let you know if I experience any of these problems then.

     

    I like the new UI, would be nice to have some column sorting though!, otherwise I'll wait to this beta gets ironed out a bit.