iarv/ipfs-blog
0
0
Fork 1
mirror of https://github.com/ipfs/ipfs-blog.git synced 2026-05-15 22:05:42 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update a-guide-to-ipfs-connectivity-in-web-browsers.md

Browse Source 
spacing between image, and text below
This commit is contained in:
TheDiscordian
2021-06-10 16:07:50 -04:00
committed by GitHub
parent 0e35f99853
commit 31d6e55f50
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/_blog/a-guide-to-ipfs-connectivity-in-web-browsers.md
+3 -1
View File
@@ -57,7 +57,9 @@ In a browser, discovering and connecting to peers can be very hard, as we can't
The chat example achieves this in two ways. Using WebRTC-Star, we achieve direct browser-to-browser communication, and with a circuit relay, we have a relay in the middle. The chat application also has a status indicator in the top left to let you know what kind of connection you have. Green means you're connected to the relay, even if it's via another peer; yellow means you're only seeing direct peers; and red means you have no peers (at least none using the chat application).
![Network graph showing the paths nodes can use to discover and communicate with eachother](https://ipfs.io/ipfs/QmX2og5BKJCMVaebEm9ZGsACEYExoGqxhJjePKNc2mZ2pE "Browser IPFS network graph") 🌟 The diagram above demonstrates what a three-user network can look like. It's worth noting that the browser nodes can communicate with `go-ipfs` as well, so BrowserC doesn't have to be a browser at all, but instead could be a `go-ipfs` node!
![Network graph showing the paths nodes can use to discover and communicate with eachother](https://ipfs.io/ipfs/QmX2og5BKJCMVaebEm9ZGsACEYExoGqxhJjePKNc2mZ2pE "Browser IPFS network graph")
🌟 The diagram above demonstrates what a three-user network can look like. It's worth noting that the browser nodes can communicate with `go-ipfs` as well, so BrowserC doesn't have to be a browser at all, but instead could be a `go-ipfs` node!
### 🐳 Docker (optional)