jrl290

Members
  • Content Count

    5
  • Joined

  • Last visited

About jrl290

  • Rank
    New User
  1. I'm sure others have already asked for this: but +1 Mobile SDK for integration into Android and iPhone apps
  2. You could set up an ordinary samba share or use Ajaxplorer. But that wouldn't have the benefit of the bittorrent protocol.
  3. Can I just go balls to the wall with this concept? Turn it into a complete file system where everyone stores everyone else's data. Call it, the Ubercloud. Files have one of three states on any given computer: 1. Fully contained on the computer's hard drive 2. Symbolically linked to the data distributed across the ubercloud 3. Contained in encrypted fragments with multiple redundancy across the ubercloud Sharing a file is a matter of sending a symbolic file with encryption and tracking data. Users can dynamically change between symbolically stored on their drive and fully stored. Being symbolically stored is like accessing a file over a samba share, where it gets pulled before it is opened. Fairness would have to be dealt with in terms of shared space, uptime and bandwidth for any given computer. It would create an economy of trading space and upload bandwidth for space and download bandwidth. I know that this is far outside of the realm of Btsync in its current state, but I figured most people had this thought and were too polite to say it. But I think its fun to entertain anyway.
  4. I'd like to vote down this (with all due respect). But say that the solution could come from any other private provider that simply accepts share keys and has btsync running constantly. My reasoning being that the application itself should be kept private.
  5. First, awesome! I appreciate that most everything on my wishlist has already been asked, but it's all just a bunch of +1's - A file serve only mechanism, where local copies are not kept, but files can still be downloaded with the benefits of the bittorrent protocol via WebDAV or ordinary web interface. That way a user is not limited to the hard drive size of his smallest computer. - Per computer priority settings that allow user to maintain file sync capability, but use less bandwidth on slower or data limited connections. This is not the same as straight bandwidth limits, as setting the upload rate to 0 would disable syncing completely, but any higher setting would pull data from a limited computer when there are copies available from other places. - The ability to host data in incomplete and encrypted form, providing higher storage efficiency (think RAID5), more redundancy, and higher performance with the use of otherwise unused free space. This is akin to the idea of donating free hard drive space without having access to another user's files. Could be implemented using a global secret. - Versioning, both for backup and bandwidth efficiency purposes - Transparent handling of the nested folder issue I realize these concepts that may seem simple actually mean massive amounts of extra complexity. This is just my feeling on how this app would best serve everyone's needs. Keep up the great work!