From 8a24c42969d6ff5977cba400a42a134ad25cf927 Mon Sep 17 00:00:00 2001
From: Kaj Schittecat <kaj@schittecat.com>
Date: Sun, 18 Oct 2026 16:59:38 +0200
Subject: [PATCH] site: drop the unverified Insecure-content tip

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---
 deploy/site/webclient.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/deploy/site/webclient.html b/deploy/site/webclient.html
index 4dac85f..8954fed 100644
--- a/deploy/site/webclient.html
+++ b/deploy/site/webclient.html
@@ -208,7 +208,7 @@
         <li>Open the <a href="http://wifi.wadamesh.com/">Wi-Fi version</a> (wifi.wadamesh.com) of the web client.</li>
         <li>Press Connect, then Wi-Fi, and type the node's address.</li></ol></div>
     </div>
-    <p class="note">Why a separate Wi-Fi version? Nodes speak plain, unencrypted WebSocket on your network (encryption is too heavy for the radio's chip next to Wi-Fi), and browsers do not let a secure https page open an unencrypted connection. The Wi-Fi version is the same client on plain http. Browsers in turn only allow USB, Bluetooth and your location on secure pages, so those work in the main version. In Chrome you can also allow "Insecure content" for the site to use Wi-Fi from the main version.</p>
+    <p class="note">Why a separate Wi-Fi version? Nodes speak plain, unencrypted WebSocket on your network (encryption is too heavy for the radio's chip next to Wi-Fi), and browsers do not let a secure https page open an unencrypted connection. The Wi-Fi version is the same client on plain http. Browsers in turn only allow USB, Bluetooth and your location on secure pages, so those work in the main version.</p>
   </section>
 
   <section class="sec" id="where">