verloren

I've done something similar: Laptop has a folder called BTSync Desktop also has BTSync, and another called BTArchive Other storage has BTSync (ro) and BTArchive (ro) BTSync is 'live', and everything is duplicated from it to everywhere else. When I've finished with something in BTSync but still want to keep it I move it on my Desktop to BTArchive, where it is still backed up, but no longer filling up my laptop.

Shut the app down (using kill -15 {process id} - is there a better way?) and an hour later it's only released ~266MB. As you say, it's still a beta...

I'm running btsync on a VPS with 2G of memory (1.8GB shown as free on reboot using free -h). When I start btsync the memory gradually drops to ~25MB. I'm syncing ~200GB from multiple sources, covering about 140,000 files. The log file doesn't seem to show anything interesting - there are a bunch of "ReadFile error" messages for some iPhoto/Aperture files that I guess it struggles to get a lock on, and some errors such as: [20140113 11:16:45.622] UPnP: Could not map UPnP Port on this pass, retrying. [20140113 11:16:50.618] UPnP: Unable to map port 37.187.98.29:62573 with UPnP. Is this amount of memory usage normal, and if not what can I do about it? Cheers, Paul

You should do a little searching for the probabilities of someone guessing a secret, Hassanova. If you do that you'll find that your suggestion making it 1,000x harder to guess isn't good enough, because somebody could still guess it. In fact if you make it a trillion times harder that's still not good enough, because somebody could still guess it. Perhaps you have a suggestion that will make it impossible to guess it?

1% ~ 4.8 billion billion billion 0.1% ~ 480 million billion billion To demonstrate how unlikely even that last number is, if every human alive had started creating secrets when the universe began, at a rate of 9 per minute, we'd now have hit that 0.1% chance of a collision.

Well if you have two secrets then you have a greater than zero possibility of a collision, though the probability really is very small. More interestingly, sing the first approximation from http://en.wikipedia.org/wiki/Birthday_problem#Approximations we can work out how many secrets there would need to be before we had a 50/50 chance of a collision. Assuming my maths is right, which is a massive assumption, it looks like you'd need 12 billion billion billion secrets to get those odds. That's about 240 million billion secrets for every human that has ever existed. The maths: http://www.wolframalpha.com/input/?i=1+-+e%5E%28-%28%281.2*10%5E28%29*%281.2*10%5E28%29%29%2F%282*36%5E36%29%29

But you already had a backup, right n_u? Not having a backup when you're using alpha software, well that wouldn't be a good idea.

Backupsy - $7 for 500GB (check lowendtalk for regular offers from them to get this), and they can offer more space if you contact them.

It's been discussed many times (search is your friend), but basically if you guessed a million secrets per second from now until the sun swallowed up the earth you'd be incredibly unlikely to get a single match, even if everyone on earth had a million secrets each. It seemed unlikely to me at first as well, but that's how the numbers work out!

What operating system are you using?

Can test on iPhone and iPad.

I like that idea - it's probably more likely that you'll accidentally call a random phone number that happens to belong to a hacker, who before you know what's going on hypnotises you into giving him your secret. So I guess we should encourage the devs to make btsync even more secure, and in the meantime chocobai can work on his anti-hypnotism techniques

Did you have the folder shared as read-only?

I'm puzzled by your statement that downloading from the central server will be fastest. Even if your server is 10 times faster than any node, it will still be quicker to download from the server *and* some nodes than from the server alone. The only time that isn't true is if the server's bandwidth is greater than your download bandwidth. But in that case it doesn't matter where the data is coming from, you're still getting it as fast as you can.

It seems like that's your 'fault', rather then BTSync's - you have a machine that you've designated as read only, and then you're making changes on it. If you don't do that then it shouldn't get out of sync. And if you do accidentally make a change, undo the change or manually copy the deleted files back onto that machine.