thobarth

Members
  • Posts

    2
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling

thobarth's Achievements

New User

New User (1/3)

  1. Dear Resilio team, OK, so you implemented sharing single files. This looks useful at first glance, but in the end, it does not help us much, because it is not thought to the very end: 1.) A user sharing a file wants to close down his laptop shortly after creating the share link. So, there must always be a peer who picks up the file ASAP after creating the link. We want to configure either a share, or a set of peers, where the shared file are all sent to, and who will accept and download them all, so I can drive home while others can receive the file. My colleague wanted to send me a 80MB file today using the feature, and then go home, while I still was in a meeting. I needed the file after the meeting. For such a case, the feature is totally useless without propagating the file to an always-on peer. 2.) Simple deep links to existing files on existing shares. Requested so often. The explorer/finder plugin should offer a menu item to generate a deep link to a file or directory that already exists on a share. This is just for convenience, to embed file URLs in email, Slack, Intranets and other documents, and enable users to find them without browsing the folder structure manually. 3.) A configurable rewrite pattern (per share) to generate web URLs. We want to install a web server on one of the always-on peers, or maybe a WebDAV or SMB server or something like this. Just let us configure a pattern to rewrite the path or a file or directory in a Resilio share to a URL with a configurable pattern. As soon as the always-on peer receives the file, it will make it accessible there. Per-share configuration should be synced to any peer. Internal users could click the generated URL, and the installed web application could even allow them to manage external https share links for the files there. Best, Thorsten
  2. Hi, I already posted this as a ticket, but I think the case and possible causes / fixes are worth to be shared with the community. Despite several feature suggestions which I am currently aggregating for posting them in the forum (as I am only allowed one post per day, it is difficult to create one post per suggestion), I experience a strange, scary phaenomenon, which caused a time-consuming mess on our server. I created a shared folder for a large volume on an OSX file server, where several people are doing updates throughout the day via AFP and SMB. On my personal Macbook, I connected to that share, so I just see this one peer one the server. I chose to not sync everything, so BTSync created the complete structure on my Macbook Pro, and kept updating it all the time, which took about 6 GB just for the direcetory structure, and was annoying and bandwidth-consuming. So I chose to "remove from this device" for every subfolder directly under the share, which seemed to work well, as BTSync created one .bts folder for each. Since then, I left everything untouched for several days, while the team was working on the file server. What happened since then: 1. Although I did not change or delete anything on my macbook, several folders and files appeared on the file server under ".sync" in the archive directory. I didn´t expect anything to go there. This must be a malfunction, and is very scary. Some of the files I find there, are still in the directories on the server, others aren´t. Nobody knows why. 2. Today morning, after I was just online with my MBP for some hours, nearly all folders had been deleted on the file server. After one more hour, nearly all folders were visible again. Then, in panic, I stopped BTSync on both machines, waited a moment, and started it just on the file server to be able to browse the log. In the log on the file server, there are many messages like "Remote peer added file" with files that nobody ever had changed. We are able to compare and restore with TimeMachine, but deleted folders and stuff moved to tash without warning is not what we expect from the software. I just had turned debug logs off on both machines, to evaluate performance during daily light background use, so I think I cannot provide very much. But as I read, seveal other people are experiencing similar issues in the latest release. What should we do to help finding the cause?