Disappointed Cat

  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by Disappointed Cat

  1. Backupsy seems like a really good deal. But it has a terrible bandwith to Central Europe (i.e. Hungary). I could only get 160 KB/s over HTTP which is still a little bit better than Dropbox but it's all the way on the east coast while backupsy is in Illinois.

    For me one of the main reasons for changing to BTSync was the bandwith - I can get better speeds from my home server than any major cloud storage provider. Except Google, they have a server farm in my country, but GDrive is just terrible.

    It's still a very good backup solution. But I'd prefer something in Europe.

  2. No it wouldn't. You do realize you have to download everything from the seedbox if you want to use what you torrented?

    Of course you could stream, but you need a pretty good connection for that so you might as well just torrent at home (if you can).

    But I think the OP wants to sync a folder up to the seedbox via rtorrent/rutorrent.

    Well that works differently, you'd have to rehash the whole folder and create a .torrent file to upload everytime.

  3. Let me start with that I really love this app so far and it has even more potential. :)

    So I have the following problem: After I restart the client (linux, 1.0.132) it forces a reindex on my biggest share. It's my music library consisting of approx. 36K files and 450GB. I want to sync most of it to my laptop. There is no selective sync yet so I used the ignore list.

    It's annoying having to wait out hours of indexing. As far as I can tell this problem is not present with any of my other shares but those are all less than 1GB so it might just be fast enough that it finishes before the webUI starts up.

    And this brings me to another problem:

    If one share is indexing all other tasks have to wait in line. This is a pain if that indexing happens to take hours.

    Couldn't this be simply solved by multithreading?

    Edit: Come to think of it this re-indexing did not happen until there was no ignore list (which excludes ~250GB) and the laptop wasn't connected.

    Edit: Dispite the ignore list - which had to be correct because the reported size of the share was correct (on the source) - the laptop still received excluded files. The laptop had the same ignore list as specified. I think this re-indexing bug may be related to the ignore list in some wierd way. I'll just wait for the selective sync, this was meant to be a temporary/test solution anyway.

  4. I'd very much like an option to extend the read only access to ready only and encrypted.

    So basically we could set up peers for redundancy and performance anywhere with the data remaining encrypted.

    And tiny behaviour modification: If .SyncTrash is disabled in a share please do not auto-create it.