From 197e449518082e68605fedcbaee4b19e1c52a148 Mon Sep 17 00:00:00 2001 From: Noah Date: Tue, 24 Mar 2026 10:17:17 -0400 Subject: [PATCH] Map subdomain changes, add additional redirects --- _redirects | 6 +++++- index.html | 2 +- meshtastic-resources.html | 4 ++-- 3 files changed, 8 insertions(+), 4 deletions(-) diff --git a/_redirects b/_redirects index b69a36b..ff2885e 100644 --- a/_redirects +++ b/_redirects @@ -1,3 +1,7 @@ /discord https://discord.gg/m4F328as3K 302 /merch https://ctmesh.redbubble.com 302 -/store https://ctmesh.redbubble.com 302 \ No newline at end of file +/store https://ctmesh.redbubble.com 302 +/map https://map.ctmesh.org 302 +/resources https://ctmesh.org/meshcore-resources 302 +/coverage https://bdl.meshmapper.net 302 +/analyzer https://analyzer.letsmesh.net/packets?region=BDL 302 \ No newline at end of file diff --git a/index.html b/index.html index c56c308..bf56f0c 100644 --- a/index.html +++ b/index.html @@ -421,7 +421,7 @@ About the project - + Map
Node Map diff --git a/meshtastic-resources.html b/meshtastic-resources.html index ee8ea79..255904e 100644 --- a/meshtastic-resources.html +++ b/meshtastic-resources.html @@ -267,7 +267,7 @@

These tools use data reported to our MQTT server by nodes across the state.

    -
  • Meshtastic Map - live map of Meshtastic nodes CT Mesh has heard
  • +
  • Meshtastic Map - live map of Meshtastic nodes CT Mesh has heard
  • Global Map - Meshtastic nodes around the world
  • Malla - deeper packet-level metrics and mesh performance insights fed from MQTT
  • PotatoMesh NEW! - packet, chat, node list, and map fed from RF on Box Mountain
  • @@ -288,7 +288,7 @@

    Key size: 128 bit

    MQTT

    -

    Our MQTT broker is uplink-only and designed for fixed nodes across the state to serve as gateway nodes. Its purpose is not to bridge gaps or extend mesh coverage, but to report local traffic to our own map and other web-based tools for analytical data and metrics to assess the mesh's performance. This role is best suited for stable, well-placed nodes with reliable coverage. If that describes your setup, follow the steps at on this page to get set up.

    +

    Our MQTT broker is uplink-only and designed for fixed nodes across the state to serve as gateway nodes. Its purpose is not to bridge gaps or extend mesh coverage, but to report local traffic to our own map and other web-based tools for analytical data and metrics to assess the mesh's performance. This role is best suited for stable, well-placed nodes with reliable coverage. If that describes your setup, follow the steps at on this page to get set up.

    Key Settings