![]() I'd love to see this extend to Sync, which I feel could be excellent not just for users syncing their data amongst multiple computing devices of their own, or sharing with friends, but creating another protective web when it comes to file-sharing, adding privacy protections - an intermediary step that doesn't have nearly the speed/hardware demands of say, operating BitTorrent exclusively through Tor. I personally am no fan of the proprietary uTorrent client, but thankfully I can make use of Deluge, KTorrent, or Transmission and have access to the latest features on the BitTorrent network, able to interact with others so long as they were using open protocols. I can nearly guarantee that if the original BitTorrent protocol had not been released free and open source (along with many of the most popular evolutions of said protocol, such as DHT/PEX/uTP, encryption, private trackers etc.) it would not have come to such prominence. From being able to audit the code if you have the skills, to crafting decentralized and inter-operative networks across multiple platforms, operating systems and more etc. While I was initially intrigued by Sync's feature set, especially the "shared secret" encryption variations (master key, one way sync, one time sync and more.), as well as that they could be integrated within BitTorrent's existing (and open source) protocols such as DHT, using a BitTorrent tracker, PEX, stream encryption etc, when I read that the implementation was not planning to be free and open source, that is a major blow to its long-term viability as part of next-generation file-sharing protocols.Įspecially in a world of "Six Strikes", overzealous industry groups and corporate cronies, government censorship and more, it is absolutely imperative that the tools that those interested in privacy, activism, journalism etc.be free and open source. If your plan involves all two dozen members of your club, or your entire extended family and a tedious-but-HD vacation video, bittorrent starts to look better but with the advantage that this 'key/encryption' stuff allows you to have a single host serving different folders with different access controls, unlike conventional trackers that are usually 'public' or 'private', with granular control, if any, mostly hacked on.Īside from the ease of use, though, the amount of benefit you'd see over rsync seems likely to be directly related to how wide your distribution is.Īfter reading over threads such as on their website, I am disappointed to find that SyncApp (as well as Surf, and Live, other BTLabs projects) is not currently open source, and apparently the most they're shooting for at the moment is some sort of API in the future. If it's just keeping Host A and Host B synchronized, you aren't going to do much better than break even, at best, with rsync. It might also be useful if your sharing scenario involves enough people that the efficiencies of bittorrent come into play. ![]() Nothing intrinsic to bittorrent as a protocol but certainly a side effect of bittorrent's history. For the non-techies, I assume that coming, out of the box, with the various tricks that bittorrent clients use to Just Work behind nasty little plastic NAT boxes would be the major advantage.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |