You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 12, 2024. It is now read-only.
Then, update your IPFS Daemon config to include the multiaddr for this new transport on the `Addresses.Swarm` array. Add: `"/dns4/star-signal.cloud.ipfs.team/wss/p2p-webrtc-star"`
397
+
Then, update your IPFS Daemon config to include the multiaddr for this new transport on the `Addresses.Swarm` array. Add: `"/dns4/wrtc-star.discovery.libp2p.io/wss/p2p-webrtc-star"`
398
398
399
399
#### How can I configure an IPFS node to use a custom `signaling endpoint` for my WebRTC transport?
400
400
@@ -417,6 +417,26 @@ const node = new IPFS({
417
417
418
418
The code above assumes you are running a local `signaling server` on port `9090`. Provide the correct values accordingly.
419
419
420
+
#### Is there a more stable alternative to websocket-star that offers a similar functionality?
421
+
422
+
Yes, websocket-star! A WebSockets based transport that uses a Relay to route the messages. To enable it, just do:
#### I see some slowness when hopping between tabs Chrome with IPFS nodes, is there a reason why?
421
441
422
442
Yes, unfortunately, due to [Chrome aggressive resource throttling policy](https://github.com/ipfs/js-ipfs/issues/611), it cuts freezes the execution of any background tab, turning an IPFS node that was running on that webpage into a vegetable state.
0 commit comments