• Posts

  • Joined

  • Last visited

donquijote's Achievements


Member (2/3)

  1. I also have the exact same issue with my galaxy s3. I wonder how many people have this issue and DON'T know about this forum... ... or how many people just download the apk from that dropbox link, and never report this problem... ...because I cannot post a review for the app in the Android Market, presumably because you can't review something incompatible with your device.... Just pointing out that this might be an issue with a lot of people that would otherwwise love to use this app....
  2. I have the exact same problem on a mbwe white light. if anyobdy has any solutions, I am eagerly checking this thread periodically
  3. to improve on that, bitTorrent music streaming, that would stream music files to the phone from you other nodes could be a space-saving option, since phones have less available storage than, say, laptops.
  4. i'd be using it to sync my music collection, mostly. Possibly also pictures. But I'd make the pictures one-way: full key on the phone, read-only key on my home repository, and somehow make the home repository never delete anything. option to sync only over wifi is a must, i don't think that should be a restriction though. It should work over 3g/4g/whatever as well. like i also said on the main wishlist, wiFi ssid-based bandwidth capping would be great, since the phone is more mobile than the laptop, and not all networks might be suitable/happy/understanding with you bitTorrenting from them.
  5. for windows (tested on win7): sort by columns in "Transfer" tab move to next field/checkbox in "Preferences" tab by pressing the tab key additionally, platform-independent: * transfer speed plot in time would be nice (not required) * uTorrent style scheduling would be even nicer - for optimizing transfers in networks with strong time/related congestion * Wireless SSID-based transfer capping would be awesome: at work, stay under the radar. at home: go full blast. when i connect to the mobile hotspot, stop completely.
  6. Thank you for putting it into kinder words than I might have
  7. throughut this discussion, i was not advocating ignoring anything. I merely acknowledged one proposed setup.
  8. SHOULD be: The solution with .SyncIgnore is good until you are not really willing to sync those subfolders on machines 1 and 2. if i grasp the common understanding of the concept i introduced, syncing with machine2 would be REQUIRED to keep machine1 in sync with machine3
  9. i did not know that (since i did not try it out yet, and it was not obvious to me, from the techincal info i got so far.) That is indeed "A" solution, but the issue of having to have a mental inventory of the subfolder is still there. if,say, i buy a new machine and want all my giant folder to sync directly, i'd have to remember that some (at least one) subfolders are filtered out, and add them manually on my new machine. which might be no problem if you have only one such subfolder, or perhaps an UNIMPORTANT subfolder. But neither is a guaranteed given fact.
  10. I could immagine that it might cause confussion inside the app, possibly even make it crash. Or perhaps some issues regarding to which file version is the most recent. surely, i'd have to try it out. and i WILL try it out. But i was thinking maybe other people have tried it before.
  11. actually.... 12.05.37.png
  12. I am sorry if i don't see everything you post, because i am currently composing. I appologize in advance, and assure you that i am trying to understand the entire thread, as a whole, even if we get out-of-sync with posts.
  13. oh. This makes sense to me. But i'd still have to keep track of what is shared where, exactly.
  14. i disagree. I am a regular user, and i came up with this test idea, because i would like to use it that way. and my idea is a subset of the parallel sync scenario. say machine1-type instances are my personal computers, and machine3-type instances are: my media streaming server, and a computer in my car. I would like to sync a folder with music. machine2 type instances would serve as a "bonding agent" precisely to make sure that changes in the machine-3 type shares are reflected to the machine1-type instances, and viceversa. there is no reason why i would want to have my vacation pictures on my media streaming box. Or in my car. But if i start doing like you suggested with: musc folders, picture folder, various other category-based folder, like projects, and subprojects shared with various machines/people, the entire system would require careful records as to which share is synced on which machine, and i need to hire my own sysadmin to make sure everything is where i want it to be. That being said, i am not blind to the complexity of managing this in the SyncApp, software, but i'd rather build that into the software once, than having EACH user do it BY HIMSELF for every particular situation in the world.
  15. Which would increase the time needed to invest in micro-managing all those micro-shares.