feat: add a blog/section on how peer-to-peer browsers work

[akhileshthite]

The current guide on How Browsers Work covers traditional client-server web browsing (HTTP, DNS, TCP, rendering, DOM, etc.) very well.
However, with the rise of DWeb (decentralized web) technologies (e.g., IPFS, Hypercore, BitTorrent), a new class of peer-to-peer (P2P) browsers like PeerSky and Agregore is emerging that doesn’t rely on central servers or traditional HTTP requests.

A dedicated blog/section on “How P2P Browsers Work” would help readers understand how browsers like PeerSky (and others in the DWeb space) interpret and load content using P2P URLs such as ipfs:// and hyper://, run local nodes, and publish content directly without centralized infrastructure.

The blog/section could:

• Explain how P2P browsers differ from traditional HTTP/HTTPS browsers.
• Introduce the concept of native protocol handlers (e.g., IPFS, Hypercore) and how they replace DNS/IP lookups with content addressable systems.
• Show examples of loading content via ipfs:// or hyper:// URLs instead of https://.
• Briefly compare traditional browser networking (HTTP over TCP) with decentralized networking (peer discovery and content routing).
• Provide simple interactive examples or visualizations demonstrating P2P fetch flows.

PeerSky:
https://peersky.p2plabs.xyz/
https://github.com/p2plabsxyz/peersky-browser