4 ms·
There's also fairly robust pure JS implementation of the BitTorrent DHT that works in both Node and the browser: https://github.com/feross/bittorrent-dht https:
by lewisl9029 11y ago
There's also fairly robust pure JS implementation of the BitTorrent DHT that works in both Node and the browser: https://github.com/feross/bittorrent-dht https://github.com/feross/bittorrent-dht
I'd love to see more decentralized web apps built on similar technologies.
- DiThi 11y agoHow can it work in the browser? There's no reference to WebRTC in the code.
- lewisl9029 11y agoSorry, it looks like you're right, there's no browser support yet. I had always simply assumed that since webtorrent works in the browser, the DHT it uses must also work in the browser, but apparently browser DHT support is still a work in progress: https://github.com/feross/webtorrent/issues/288 https://github.com/feross/webtorrent/issues/288
- kauffj 11y agoWe're building one: http://lbry.io http://lbry.io
- motoboi 11y agoVery interesting project. I got curious why you decided to use a one-level namespace. A multi-level namespace guarantees that if I manage to build a strong brand, I can continue to use it, creating sub-domains. The alternative being people buying up names to sell them later. Example: lbry://avengers The first movie come out, makes a lot of success. A brand is built. One year later, I make Avengers II: lbry://avengers.ageofultron and so on. But with one-level namespace, when avengers make success, people will buy all variants of it. TL:DR Just let people buy namespace levels and do whatever they want with it.
- kauffj 11y agoSuper slow to respond to this, but this is possible! But note there can be no speculation in names since selling is mandatory.