Jacob Heun
Jacob Heun
> Do we want to maintain permanent connections to bootstrap nodes? It may be more fault tolerant and put less stress on those nodes to prioritize them as "Hi-Lo" -...
@mpetrunic the original consolidation effort is at https://github.com/libp2p/js-libp2p/issues/384, and it links to a larger [discussion in js-ipfs](https://github.com/ipfs/js-ipfs/issues/2222). The main reasoning for pulling in these core modules to js-libp2p is to...
Both of those dependencies are optional in [email protected] and are properly listed in the `peerDependenciesMeta` field. npm @6.11.x shouldn't be printing the warnings since they are listed as optional. The...
There is also some discussion around implementing QUIC as a native node module, https://github.com/nodejs/node/issues/23064, potentially starting early next year.
The chat example here is pretty basic. You might want to take a look at the more detailed example at https://github.com/libp2p/js-libp2p-examples/tree/hackfs. This branch in particular is for the recent HackFS...
> Q: Do we really need a low watermark? We could have a configurable number of connection slots that would be used internally and we should try to be connected...
It looks like you are using `ip4/188.166.203.82/tcp/20000/wss/p2p-webrtc-star` as your signaling server. This won't work, as the browser requires SSL encryption for websocket connections. You can see more details in the...
> ws://0.0.0.0:9090/socket.io/?EIO=3&transport=websocket You need to change the listen address of your libp2p node to match your webrtc server address, or get rid of it and connect manually. ```js this.libp2p =...
> '/127.0.0.1:13579/wss/p2p-webrtc-star' This is not a valid multiaddr. If you go to the address the signaling server is running on it should load a webpage with the address you need...
Are you running the server locally or on a server? `gcc.world` doesn't resolve to anything so you aren't going to be able to connect to that address. ``` $ nslookup...