wimbit

Members
  • Posts

    66
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by wimbit

  1. Thanks BitDuck. I'm hoping the team chimes in. I don't see any way to get the EROS without changing the key at this point.
  2. Apart from the query in the above post, I need to be able to use an already defined RW secret to get the encrypted-read-only secret because it is already synchronized with an Android device and several machines.
  3. 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:
  4. Strange ... The folder share secret is already only 33 long. Does EROS secret not exist for folders also shared on an Android device?
  5. I'm completely lost. The 'share' keys are all 33 chars now and I can't figure out a way to generate a EROS key without the api. How to generate Encrypted Read Only Secret? And if the api is the only way now, then perhaps a 'for dummies' guide to getting EROS nodes up and running. Any help would be appreciated
  6. 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
  7. I've got a few large folders (7GB, 200GB, 500MB) and they are setup on a machine on the WLAN with the encrypted read only secret. The upload/download is at 5kB/s and the sync never ends, sometimes appears to restart back at 0%.
  8. 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
  9. The Android phone has a backup sync setting feature which does a backup of the secrets and folders. Why not for desktop. Then, at least, a bad version update (ahem!!) could be rolled back by the user reinstalling an old version and restoring the settings. Makes sense to me
  10. 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. 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
  12. OK. Now working. But PC shows lots of peers that are all the same name?
  13. But is self-sleeps very quickly and it is hard to even get to any features without the app minimizing. But the old folders also do not sync.
  14. newer version does not resolve issues. same issues.
  15. Does not appear to have. 1) As soon as I click on 'sync'and the app opens, in a few seconds it closes it's own window. 2) Sync itself not appears to be working at all.
  16. New version is crap. Does not sync and also sleeps while being configured. Whoever tested this should be ... Can I get back my old version, please?
  17. The new Android version is buggy: 1) Sleeps even when being configured. 2) Does not sync anything that was previously configured with any machines. Installing the old version, does not work for long because it auto-updates. Seriously, who tested this? Baaaaad.
  18. The new Android version makes all folders put in 'download'. This breaks all previous setups where the synced folder location could be specified on the Android device. This is a major bug as far as I am concerned.
  19. I have over 500 GB on MyBookLive with the higher workload Encrypted Read Only secrets and it runs fine. No issues yet with the MyBookLive having to work too much.
  20. ".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.
  21. 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 ( 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!
  22. 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
  23. 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. 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.
  24. This is warning to all: 1.3 is buggy. Not everything is syncing. It crashes. Too many problems. I am reverting to 1.2.92 and I hope the problems get fixed.