3 ms·
So let's say I'm building a decentralized chat app built on some DHT and would like to host it on IPFS. I imagine getting the static html/js/css for the client
by lewisl9029 11y ago
So let's say I'm building a decentralized chat app built on some DHT and would like to host it on IPFS.
I imagine getting the static html/js/css for the client-side app onto IPFS should be simple enough, but how would I handle bootstrapping?
Even in a decentralized service, clients need to connect to a seed server somewhere to start querying for other peers on the DHT. Would it be possible to host such a seed server on IPFS? Or would the seed server still need to live on a traditional server somewhere on the "old web"?
- whyrusleeping 11y agoThe way our network currently bootstraps is to dial a set of peers that are hardcoded into the default config file. We also have mdns for finding peers that are on your LAN without the need for any hard coded addresses.
- lewisl9029 11y agoThanks for the quick reply. I was actually thinking of an app running on a separate IP-based DHT, but your reply brought to my attention that IPFS actually already runs on a DHT. Since IPFS runs on its own DHT, are there any plans for a client-side IPFS DHT library for apps to use to connect to peers on the IPFS network? Similar to https://github.com/feross/bittorrent-dht https://github.com/feross/bittorrent-dht, but with native support for IPFS peers? Something like this would make building a client-side real-time app based on IPFS a much more streamlined experience since developers won't have to depend on an external DHT.