From 70534dc23e532b4054abad6f96d8199927fadbac Mon Sep 17 00:00:00 2001 From: Raven Scott Date: Mon, 23 Feb 2026 19:16:17 -0500 Subject: [PATCH] update --- ...ive Messaging: Finally Bringing P2P to the Modern Browser.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 509b28c..93f7d37 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 @@ -456,7 +456,7 @@ BridgeSwarm consists of three main parts working together: ## Finding the Way In -Chrome extensions have this feature called native messaging. It's been around since the early days, but the official documentation focuses on mundane use cases: integrating with password managers, connecting to desktop notification systems, that sort of thing. The technical capability underneath is much more powerful. +Chrome extensions have this feature called native messaging. It's been around, but the official documentation focuses on mundane use cases: integrating with password managers, connecting to desktop notification systems, that sort of thing. The technical capability underneath is much more powerful. Native messaging lets an extension spawn a process outside the browser and communicate with it through standard input and standard output. The browser handles spawning the process, manages its lifecycle, and provides a clean message-passing interface. Nothing fancy, but effective.