• Content Count

  • Joined

  • Last visited

About Timbo

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

630 profile views
  1. I don't begrudge them for trying to make money. I'm sure their business model has changed frequently over the years. It's hard to compete with free, especially when "if you don't necessarily need the special features" for the majority of users.
  2. They probably have other priorities and do not have any manpower to monitor the forums nor work on the bugs reported.
  3. What kind of files are these? 12919 files only being 3MB of files is nonsensical. You likely have filesystem corruption. Run chkdsk if you're on Windows. Double check you never ran out of space somewhere and these aren't all 0 byte files or something. You might also consider syncing more smaller sized folders with less files in each sync share.
  4. That's not a solution. That's not even an acceptable workaround. I'd rather the resources go into preventing and automatically resolving such an issue, not allow the worst band-aid, ever.
  5. - uninstall - Just delete the .db files No app needed, and if it was needed, these actions should never, ever have to be done. Resilio resources are stretched and need to prioritize. This ain't one of them. Any improvements to fix syncing issues should be implemented in the webGUI and visible to the user so its more intuitive than having to break out the CLI tool and read up on documentation.
  6. My feedback: Upgraded main Windows sync from 2.6.3, was the fastest and easiest upgrade I've ever experienced with Resilio so far. I almost thought the install didn't happen but Resilio opened up and showed 2.7.1 version. So far, only issue is that my local windows peer on the network is now showing up twice, as "Offline" and "Synced with". The peer correctly shows only one instance name of my main windows box. I've reopened Resilio and same thing. Maybe it'll time out. Upgraded my other windows sync box on the network. This time, I was prompted to set a default sync mode tha
  7. On May 21, @Helen said "Packages will be pushed to repo later". That being said, I said, "what the hell" and upgraded from 2.6.3 to on Centos 8 VPS and saw a substantial improvement. Finally seeing speeds I was expecting to see. On 2.6.3 right before the upgrade, it was averaging about 12MB/s (~100Mbps) from a VPS to my home. And I've consistently seen it max out around that for a long time. After the upgrade, the transfer resumed at ~300Mbps. Next time I have a long transfer, I'll check top for rslsync's CPU usage. I've thought that was using a lot for the 100Mbps tra
  8. If you've seen the current debug logs, I doubt there is interest in users self debugging issues. It's not an open source product and fixing the problem isn't really in the user's capability, so spending resources on user's to use CLI debugging tools doesn't make much sense. They'd rather you contact them directly to get to the root of the problem, and then they'll assign resources to bugs that users are actually complaining about. But +1 vote for improving their logging verbosity and structure.
  9. I think leaving it default enabled and 30 days is best for the majority of users, especially since you should always lean towards data safety by default. I've had a few accidental deletes on media files and being able to go to the other side, move it from archive back into the sync folder and recover is by far faster and easier than having a separate backup solution. But they need to break out a lot of the power user settings into main configuration settings so that it isn't forgotten about and is brought to user's attention before they run out of space. Setting your trash days from 30 to
  10. kos13, Good post. I'm glad you guys were able to take care of the server refugees. Yes, that would have been ideal. I'm glad this was actually on your radar, at least. Next time... On the licensing front, am I correct that Pro license was a 5 user license and now a business license with 1 Server license means they would get a 20 user license? Or you're cooking up a special 5 user license for Pro->Server refugees? And I assume you've implemented a cutoff date < June 1st? Or I guess you just can't buy Pro anymore, so that is probably moot.
  11. Another problem with just releasing this feature deprecation without a release in between, is that on Server installs you should flat out prevent auto upgrade instead of allowing it. Upgrading within software and it stops working, that is 100% on the vendor and totally avoidable. Microsoft deprecates major features in nearly all the major releases they do when the feature was poorly designed or it has minimal usage. The differences are that they do not hide the fact, they announce it MONTHS in advance, they release beta builds without said features, and while they may ADD additional lice
  12. Just to be clear, no, not "completely legal". All Microsoft can verify is that a key is valid, they cannot validate the license terms you're clearly breaking. Legal isn't defined by whether the key installs or not, its usage. You're not even being naive (ignorance is not a legal argument), just obtuse. That being said, many IT people have home labs and access to technical subscriptions from Microsoft and can obtain legal licenses for cheap (no, not $12, either) that are NOT intended for production but testing and development purposes. Having access to Windows Essentials by an IT person is
  13. @Helen 1. When will the linux repo's be updated to 2.7.0? The Centos repo is still 2.6.3. It is my understanding you initially said linux x86/x64 wouldn't be supported anymore but I assume your edited post and release notes that specifically say Windows Servers no longer includes Linux OS so that Linux VPS' will continue to be supported? 2. Are there any known issues if Windows Server version 2.6.3 inter-operated with 2.7.0+ going forward? All the home users that used Resilio on cheap Windows VPS' ($25-$55/year) that are clearly not in the business or Enterprise game need to stick wi
  14. Dude, just don't update your programs and stop complaining about an issue only existing in your head. Talk about nonsense... The users generally chomping at the bit for updates is that we have chronic issues that don't get addressed. So for us as users, we always have to decide to put up with bugs/workarounds or look for another program. If development is stopped, then we know to look for permanent solutions, not temporary workarounds. If development isn't stopped, then an update may fix it and then its wait and see. Plenty of updates in the past have resolved previous issues, just look a
  15. How about a link to an internal Windows version that has a fix for when the sync fails at like 16% showing a conflict with 2 files, but instead of saying which two files are in conflict, it just goes to a Loading... page that says "These files cannot be downloaded as there are no source peers online for too long time. Sync will continue downloading if any source peer appears online" and never ever finishes loading to show the 2 frickin' files holding up TB's worth of syncing. It's the most frustrating bug for me for 2018-2019 (yes, more than a year old bug). The source side shows no prob