From e5d50f7b0c571be6d4b5d099f4403ceb8c4c8c2d Mon Sep 17 00:00:00 2001 From: Raven Scott Date: Mon, 23 Feb 2026 18:56:50 -0500 Subject: [PATCH] remove numbers --- ...ssaging: Finally Bringing P2P to the Modern Browser.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/markdown/Native Messaging: Finally Bringing P2P to the Modern Browser.md b/markdown/Native Messaging: Finally Bringing P2P to the Modern Browser.md index 954fbc4..11d5447 100644 --- a/markdown/Native Messaging: Finally Bringing P2P to the Modern Browser.md +++ b/markdown/Native Messaging: Finally Bringing P2P to the Modern Browser.md @@ -261,7 +261,7 @@ P2P Networking: ### Key Networking Differences -#### 1. Discovery vs Connection +#### Discovery vs Connection In traditional networking, a **DNS server** tells your browser the IP address of a server. You connect directly to that IP. @@ -280,7 +280,7 @@ swarm.on('connection', (conn, peerInfo) => { }); ``` -#### 2. No Port Forwarding Required +#### No Port Forwarding Required Traditional servers need **port forwarding** - you configure your router to forward incoming connections to your server. @@ -290,7 +290,7 @@ P2P uses **NAT traversal** (hole punching): - Both peers send packets to each other, "punching holes" in the NAT - After hole punching, direct P2P communication is possible -#### 3. Always-On vs On-Demand +#### Always-On vs On-Demand **Client-Server**: Server runs 24/7, clients connect as needed **P2P**: Peers can come and go; the network adapts @@ -308,7 +308,7 @@ P2P: [Peer A] ──────► [Peer B] -#### 4. Trust Model +#### Trust Model **Client-Server**: You trust the server to: - Not read your data (depends on server honesty)