Live data from Hacker News

Serverless Sync in Web Apps Using Bit Torrent

paul.kinlan.me

51–57 of 57 posts

Re: Serverless Sync in Web Apps Using Bit Torrent

#51

Earlier quoted context omitted.

You mean something like this? :) https://zeronet.io/

Where is the anonymity? It is unreasonable to use TOR in my opinion because despite being only a few exit nodes, it's not truly P2P then (and therefore can be slow). Tribler tried something similar. Someone needs to build an onion router of peers without defined relays or exit nodes (think of it as everyone-is-a-relay TOR, it's one of my future ideas[0]). This will speed things up substantially and can definitely wor…

You don't need exit nodes: ZeroNet support hidden service (.onion) peers and around 50% of the users are connected to the network this way.

And since the ZeroNet sites works offline it does not affects the page rendering/browsing speed.

Re: Serverless Sync in Web Apps Using Bit Torrent

#52

Earlier quoted context omitted.

Seems js-ipfs[0] is not quite ready for prime time (though it's close) and the author had a requirement to do everything from a browser. https://github.com/ipfs/js-ipfs/

Unfortunately it looks like WebRTC support and DHT support isn't planned for this current release of js-ipfs according to their roadmap [1], both of which could be a giant leap forward in enabling truly decentralized apps. Bittorrent DHT doesn't actually run in the browser yet either [2], so WebTorrent in the browser currently only has access to the tracker infrastructure, and thus isn't as decentralized as one might…

Something I've never understood regarding the "Bittorrent DHT" ... is it a singular hash table that's utilized for all BT activity, or are there many Bittorrent DHT's, and when somebody says "Bittorrent DHT" they're just referring to the concept?

Re: Serverless Sync in Web Apps Using Bit Torrent

#53
post #52

Earlier quoted context omitted.

Unfortunately it looks like WebRTC support and DHT support isn't planned for this current release of js-ipfs according to their roadmap [1], both of which could be a giant leap forward in enabling truly decentralized apps. Bittorrent DHT doesn't actually run in the browser yet either [2], so WebTorrent in the browser currently only has access to the tracker infrastructure, and thus isn't as decentralized as one might…

Something I've never understood regarding the "Bittorrent DHT" ... is it a singular hash table that's utilized for all BT activity, or are there many Bittorrent DHT's, and when somebody says "Bittorrent DHT" they're just referring to the concept?

The "Bittorrent DHT" is one big Distributed Hash Table [1] in the sky. As you participate, you become a node, and you'll receive a subset of the data in the entire node network. Here's a StackOverflow answer explaining the mechanics: https://stackoverflow.com/questions/1332107

There is actually another one called "Azureus DHT" which came first [2]. It's another big hashtable in the sky, and the Azureus/Vuze clients can connect to either DHT. All other clients only use the second one, the "Mainline DHT", which was an official extension to the protocol [3].

[1] https://en.wikipedia.org/wiki/Distributed_hash_table [2] http://www.bittorrent.org/beps/bep_0005.html [3] https://wiki.vuze.com/w/Distributed_hash_table

Re: Serverless Sync in Web Apps Using Bit Torrent

#54

Earlier quoted context omitted.

I have only slightly looked at i2p, but sadly appears the only impl requires a JVM. I have researched freenet and it does not appear to provide plausible deniability for public data (sorry on mobile and can't link easily).

It does provide plausible deniability, since you have no control over what files go to your node (files are spread as people request them) and they are encrypted, hence you can't easily know what they contain.

Both [0] and [1] seem to suggest that if you make the data "public" then someone can know they have a piece.

"It is hard, but not impossible, to determine which files that are stored in your local Freenet Datastore"

"Of course, the decryption keys, which are contained in links to the files, may be publically posted on some other site - they have to be if the site creator wants people to visit their site. But if you've never had knowledge of that link, which is very plausible if there are thousands of Freenet sites, you can't be expected to know what is contained in the encrypted files in your Freenet node."

0 - http://security.stackexchange.com/questions/12811/how-does-f...

1 - https://wiki.freenetproject.org/Plausible_deniability

Re: Serverless Sync in Web Apps Using Bit Torrent

#55
post #53
post #52

Earlier quoted context omitted.

Something I've never understood regarding the "Bittorrent DHT" ... is it a singular hash table that's utilized for all BT activity, or are there many Bittorrent DHT's, and when somebody says "Bittorrent DHT" they're just referring to the concept?

The "Bittorrent DHT" is one big Distributed Hash Table [1] in the sky. As you participate, you become a node, and you'll receive a subset of the data in the entire node network. Here's a StackOverflow answer explaining the mechanics: https://stackoverflow.com/questions/1332107 There is actually another one called "Azureus DHT" which came first [2]. It's another big hashtable in the sky, and the Azureus/Vuze clients c…

Thank you for helping me understand better.

Re: Serverless Sync in Web Apps Using Bit Torrent

#56

Earlier quoted context omitted.

From what you've described, it seems like i2p would satisfy the requirements of your first paragraph and Freenet would satisfy the requirements of the second. Both of these networks have been around for over a decade, so they're not as in vogue as newer projects.

I have only slightly looked at i2p, but sadly appears the only impl requires a JVM. I have researched freenet and it does not appear to provide plausible deniability for public data (sorry on mobile and can't link easily).

there is a c++ implementation of I2P[0].

0. https://github.com/PurpleI2P/i2pd

Re: Serverless Sync in Web Apps Using Bit Torrent

#57
post #7

Now someone could make a Chrome plugin for YouTube, which seamlessly seeds the watched videos and, when it goes offline, loads from Bittorrent.

Or when the site gets a DMCA takedown request. Or when content is blocked in your country.

There seriously needs to be a Youtube killer, and this would be a good starting point.

Post reply on HN