From 6d9544206c47b2171346f49a2aa842614d770fbd Mon Sep 17 00:00:00 2001 From: Ryan Baumann Date: Mon, 7 Jun 2021 03:55:32 +0000 Subject: [PATCH] Update from Forestry.io Ryan Baumann updated src/_blog/a-guide-to-ipfs-connectivity-in-web-browsers.md --- src/_blog/a-guide-to-ipfs-connectivity-in-web-browsers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_blog/a-guide-to-ipfs-connectivity-in-web-browsers.md b/src/_blog/a-guide-to-ipfs-connectivity-in-web-browsers.md index e3532d26..a697a8c9 100644 --- a/src/_blog/a-guide-to-ipfs-connectivity-in-web-browsers.md +++ b/src/_blog/a-guide-to-ipfs-connectivity-in-web-browsers.md @@ -40,7 +40,7 @@ In a browser discovering and connecting to peers can be very hard, as we can't l The chat example achieves this in 2 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 has a status indicator in the top-left to let you know too what kind of connection you have. Green means you're connected to the relay, even if it's via another peer, yellow mean you're only seeing direct peers, and red means you have no peers (at least none using the chat application). -![QmbuCP1LtWM4dYUFGhCwR3Swz2FhtetRR1kXHcECxzJ8b5](https://ipfs.io/ipfs/QmbuCP1LtWM4dYUFGhCwR3Swz2FhtetRR1kXHcECxzJ8b5 "QmbuCP1LtWM4dYUFGhCwR3Swz2FhtetRR1kXHcECxzJ8b5") +![BrowserIPFSNetworkGraph_Transparent.png](https://ipfs.io/ipfs/QmX2og5BKJCMVaebEm9ZGsACEYExoGqxhJjePKNc2mZ2pE "BrowserIPFSNetworkGraph_Transparent.png") 🌟 The diagram above demonstrates what a 3 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)