rl834bb

I'm not on a local network, but I did enable that setting just in case. Anyway, I've just gone back on to re-check that setting was enabled and it's miraculously now working... which is good, except I'm now rather suspicious of whether to trust the rate limiting functionality not to eat into my daytime data allowance! I paid for the pro version to get access to the new scheduler to remove my clunky set of scripts using the api to start/stop and speed up/down across the day, but I'm not going to trust it for a while yet. To be honest it's symptomatic of my experience with bysync from the start - great when it works, but just too unpredictable, flaky and unreliable to use commercially in my day job...

Since upgrading to 2.4 I notice all temp files are now stored in .sync with uid names. Unless I'm missing something, this effectively means there's no way to keep an eye on individual file download status? The UI is not much use either as it just shows which files are being downloaded and not their status. Is there anywhere else to see this, or an option to go back to old temp file approach? I also just gave "selective sync" a try in case that gave some better options... although all that did was delete my half-gig of part downloaded files without warning me (thanks for that!).

Just bought pro and upgraded to version 2.4. Noticed the global bandwidth limit doesn't appear to be working. See attached screenshot with upload limit set to 75K and upload still running at around 275K. Am I doing something wrong, or is it a known issue, or needs a bug report? Thanks!