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
Copy file name to clipboardExpand all lines: content/guides/getting-started/webrtc.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -449,7 +449,7 @@ A couple of note-worthy things about these changes:
449
449
- The `pubsub` service adds GossipSub protocol capabilities to the node.
450
450
-`pubsubPeerDiscovery` depends on the `pubsub` service and introduces the peer discovery mechanism. [GossipSub is a large dependency](https://packagephobia.com/result?p=%40chainsafe%2Flibp2p-gossipsub) making it suboptimal for browser bundles.
451
451
- When js-libp2p discovers a new peer (and its multiaddrs) it emits a `peer:discovery` event.
452
-
- To dial the newly discovered peers, add an event listener for the `peer:discovery` event and dial the peer with the `dial` method.
452
+
- To dial a newly discovered peer, add an event listener for the `peer:discovery` event and dial the peer with the `dial` method.
453
453
- PubSub peer discovery works well for demos and guides, but its current design is not battle-tested for production use cases.
454
454
455
455
Next, open two browser tabs of the frontend, and you should see them connected to each other within a couple of seconds 🎉.
0 commit comments