4 ms·
I'm not sure you are right about this. The following link will stream big buck bunny directly from the network with full P2P support. It is not using a gateway
by georgyo 6y ago
I'm not sure you are right about this. The following link will stream big buck bunny directly from the network with full P2P support. It is not using a gateway node for the video content.
https://bbb.fu.io/ https://bbb.fu.io/
You can run the following in the console to see all your peers
for await (const peer of await node.swarm.peers()) { console.log(peer.addr.toString()) }
The console currently get's spammed pretty hard because they haven't implemented filtering out plain ws (non-wss) peers if you are connecting https. But it will use webrtc to find peers, and find all wss nodes in the network.
- magila 6y agoFor me at least the vast majority of the data is being downloaded from various servers under bootstrap.libp2p.io or preload.ipfs.io. These are clearly dedicated servers not true peers. The contact info for these servers appears to be retrieved via the DNS rather than the DHT. This isn't surprising because browser clients can't participate in the DHT, but the DHT is currently one of the biggest weak points of IPFS. IPFS's DHT is so chatty that it consumes over a megabit of throughput just to maintain an idle node. Lookups are excruciatingly slow and often fail completely.
- georgyo 6y agoSorta, a peer can advertise dns addresses, and the browser can participate in the dht as a client. The example above uses webrtc-star for browser to browser discovery. $ ipfs dht findpeer 12D3KooWJxNHY6zE1KnzFdBJrTMCbhCVNtSLvjp7qR5Wsp49DnUC /dnsaddr/ipfs.scalable.io /dns4/ipfs.scalable.io/udp/4001/quic /dns6/ipfs.scalable.io/tcp/443/wss /dns6/ipfs.scalable.io/udp/4001/quic /dns4/ipfs.scalable.io/tcp/443/wss
- haywirez 6y agoTook a good 10 seconds until the video started playing. Anything over a second is too long in terms of UX expectations.