ScotMesh Wiki - Recent changes [en-gb]

Troubleshooting

ScotMesh — Thu, 17 Sep 2026 12:36:45 GMT

Drop the 433 MHz profile: it has been scrapped, ScotMesh is 868 MHz only

← Older revision		Revision as of 13:36, 17 September 2026
Line 65:		Line 65:
	=== Two LoRa radios cannot hear each other ===		=== Two LoRa radios cannot hear each other ===

	Frequency, bandwidth, spreading factor and coding rate must match exactly. A mismatch gives no error; the radios are simply deaf to each other. Compare against the [[RNode\|ScotMesh ~~profiles~~]]. Then check the antenna is for the right band and actually connected: transmitting into no antenna at 22 dBm can damage the radio.		Frequency, bandwidth, spreading factor and coding rate must match exactly. A mismatch gives no error; the radios are simply deaf to each other. Compare against the [[RNode\|ScotMesh profile]]. Then check the antenna is for the right band and actually connected: transmitting into no antenna at 22 dBm can damage the radio.

	=== Everything worked yesterday ===		=== Everything worked yesterday ===

The ScotMesh node

ScotMesh — Thu, 17 Sep 2026 12:36:44 GMT

rrc-hub retired: the chat room is run by the ScotMesh chat hub

← Older revision		Revision as of 13:36, 17 September 2026
Line 14:		Line 14:
	== Where it is and what it runs on ==		== Where it is and what it runs on ==

	The node is hosted in Dalgety Bay, Fife. It runs on Ubuntu, with one Reticulum daemon (<code>rnsd</code>) shared by ~~the chat hub (<code>[https://github.com/thatSFguy/reticulum-relay-chat rrc-hub]</code>),~~ the propagation node (<code>lxmd</code>), the Nomad Network node and an I2P router (<code>i2pd</code>) for the [[Access over I2P\|I2P entry point]].		The node is hosted in Dalgety Bay, Fife. It runs on Ubuntu, with one Reticulum daemon (<code>rnsd</code>) shared by the propagation node (<code>lxmd</code>), the Nomad Network node and an I2P router (<code>i2pd</code>) for the [[Access over I2P\|I2P entry point]].

	Its live status, updated every two minutes from the daemon itself, is on [https://rns.scotmesh.net rns.scotmesh.net] and at the top of this wiki's [[Main Page\|home page]].		Its live status, updated every two minutes from the daemon itself, is on [https://rns.scotmesh.net rns.scotmesh.net] and at the top of this wiki's [[Main Page\|home page]].

Services and addresses

ScotMesh — Thu, 17 Sep 2026 12:36:43 GMT

Drop the 433 MHz profile: it has been scrapped, ScotMesh is 868 MHz only

← Older revision		Revision as of 13:36, 17 September 2026
Line 10:		Line 10:
	\| I2P \|\| <code>a3pswrtvpuro62ijhb7lwdt2n6aqgajglof27ynbonynmolzlz7q.b32.i2p</code> \|\| For networks that block outbound connections. Interface type <code>I2PInterface</code>. See [[Access over I2P]].		\| I2P \|\| <code>a3pswrtvpuro62ijhb7lwdt2n6aqgajglof27ynbonynmolzlz7q.b32.i2p</code> \|\| For networks that block outbound connections. Interface type <code>I2PInterface</code>. See [[Access over I2P]].
	\|-		\|-
	\| LoRa \|\| ~~ScotMesh 433 or~~ ScotMesh 868 radio profile \|\| Within range of a gateway only. See [[RNode]].		\| LoRa \|\| ScotMesh 868 radio profile \|\| Within range of a gateway only. See [[RNode]].
	\|}		\|}

Line 27:		Line 27:
	\|}		\|}

	== Radio ~~profiles~~ ==		== Radio profile ==

	Every radio on the network must use exactly these settings; see [[RNode]] for why.		Every radio on the network must use exactly these settings; see [[RNode]] for why.

	{\| class="wikitable"		{\| class="wikitable"
	! ~~!! ScotMesh 433~~ !! ScotMesh 868		! !! ScotMesh 868
	\|-		\|-
	\| Frequency ~~\|\| 433.775 MHz~~ \|\| 869.4625 MHz		\| Frequency \|\| 869.4625 MHz
	\|-		\|-
	\| Bandwidth ~~\|\| 125 kHz~~ \|\| 125 kHz		\| Bandwidth \|\| 125 kHz
	\|-		\|-
	\| Spreading factor ~~\|\| 8~~ \|\| 9		\| Spreading factor \|\| 9
	\|-		\|-
	\| Coding rate ~~\|\| 4/5~~ \|\| 4/5		\| Coding rate \|\| 4/5
	\|-		\|-
	\| TX power ~~\|\| 7 dBm~~ \|\| 22 dBm		\| TX power \|\| 22 dBm
	\|}		\|}

ScotMesh microReticulum

ScotMesh — Thu, 17 Sep 2026 12:36:42 GMT

Drop the 433 MHz profile: it has been scrapped, ScotMesh is 868 MHz only

← Older revision		Revision as of 13:36, 17 September 2026
Line 7:		Line 7:
	* a position on [https://rmap.world rmap.world].		* a position on [https://rmap.world rmap.world].

	Source: [https://github.com/~~A13xB0~~/microReticulum_Firmware github.com/~~A13xB0~~/microReticulum_Firmware]. Firmware: [https://rnode.scotmesh.net rnode.scotmesh.net] (choose ''Standalone node'').		Source: [https://github.com/ScotMesh/microReticulum_Firmware github.com/ScotMesh/microReticulum_Firmware]. Firmware: [https://rnode.scotmesh.net rnode.scotmesh.net] (choose ''Standalone node'').

	== Boards ==		== Boards ==
Line 38:		Line 38:
	# Open [https://rnode.scotmesh.net rnode.scotmesh.net] in Chrome or Edge on a computer. Choose '''Standalone node''', pick your board, and flash.		# Open [https://rnode.scotmesh.net rnode.scotmesh.net] in Chrome or Edge on a computer. Choose '''Standalone node''', pick your board, and flash.
	# On the configure step:		# On the configure step:
	#* pick '''ScotMesh 868''' ~~(or 433)~~;		#* pick '''ScotMesh 868''';
	#* give the node a name;		#* give the node a name;
	#* choose its role (normally ''Fixed relay'');		#* choose its role (normally ''Fixed relay'');
Line 137:		Line 137:
	[[File:radio.png\|frameless\|upright=2.2\|Radio page]]		[[File:radio.png\|frameless\|upright=2.2\|Radio page]]

	'''Radio changes are a trial.''' Enter new settings (or pick ''ScotMesh 868~~'' / ''433~~'') and press ''Try these''. The node uses them for five minutes. Reconnect on the new settings and press ''Keep''. If you don't, the node goes back to the old settings by itself, so a mistake can't strand a remote node.		'''Radio changes are a trial.''' Enter new settings (or pick ''ScotMesh 868'') and press ''Try these''. The node uses them for five minutes. Reconnect on the new settings and press ''Keep''. If you don't, the node goes back to the old settings by itself, so a mistake can't strand a remote node.

	[[File:role.png\|frameless\|upright=2.2\|Role page]]		[[File:role.png\|frameless\|upright=2.2\|Role page]]
Line 217:		Line 217:
	# This restarts the node with a Bluetooth firmware-update service for '''20 minutes'''. It advertises as <code>SenseCAP P1 DFU</code>.		# This restarts the node with a Bluetooth firmware-update service for '''20 minutes'''. It advertises as <code>SenseCAP P1 DFU</code>.
	# Within Bluetooth range, open '''nRF Device Firmware Update''' or '''nRF Connect''' on a phone.		# Within Bluetooth range, open '''nRF Device Firmware Update''' or '''nRF Connect''' on a phone.
	# Send the node's <code>rnode_firmware_seeed_solar_node_p1.zip</code> from the [https://github.com/~~A13xB0~~/microReticulum_Firmware/releases releases].		# Send the node's <code>rnode_firmware_seeed_solar_node_p1.zip</code> from the [https://github.com/ScotMesh/microReticulum_Firmware/releases releases].

	If nothing connects, the node restarts normally when the window closes.		If nothing connects, the node restarts normally when the window closes.

ScotMesh firmware

ScotMesh — Thu, 17 Sep 2026 12:36:41 GMT

Firmware repository moved to ScotMesh/microReticulum_Firmware

← Older revision		Revision as of 13:36, 17 September 2026
Line 91:		Line 91:

	* '''Flash it from a browser:''' [https://rnode.scotmesh.net rnode.scotmesh.net], choose ''Standalone node''. It fetches the firmware, flashes it, and walks you through naming the node, choosing its radio profile and adding yourself as its admin.		* '''Flash it from a browser:''' [https://rnode.scotmesh.net rnode.scotmesh.net], choose ''Standalone node''. It fetches the firmware, flashes it, and walks you through naming the node, choosing its radio profile and adding yourself as its admin.
	* '''Releases:''' [https://github.com/~~A13xB0~~/microReticulum_Firmware/releases github.com/~~A13xB0~~/microReticulum_Firmware/releases]		* '''Releases:''' [https://github.com/ScotMesh/microReticulum_Firmware/releases github.com/ScotMesh/microReticulum_Firmware/releases]
	* '''Source and changes from upstream:''' [https://github.com/~~A13xB0~~/microReticulum_Firmware github.com/~~A13xB0~~/microReticulum_Firmware]		* '''Source and changes from upstream:''' [https://github.com/ScotMesh/microReticulum_Firmware github.com/ScotMesh/microReticulum_Firmware]

	[[Category:Hardware]]		[[Category:Hardware]]

ScotMesh Mail

ScotMesh — Thu, 17 Sep 2026 12:36:41 GMT

Repository is private: drop the dead link

← Older revision		Revision as of 13:36, 17 September 2026
Line 31:		Line 31:
	\|}		\|}

	It runs on ScotMesh's own server alongside the [[ScotMesh chat hub\|chat hub]], and stores messages for mailboxes that are away through the [[Propagation node\|propagation node]]. The code is in a private repository~~, [https://github.com/A13xB0/rmail A13xB0/rmail]; it~~ has no licence yet.		It runs on ScotMesh's own server alongside the [[ScotMesh chat hub\|chat hub]], and stores messages for mailboxes that are away through the [[Propagation node\|propagation node]]. The code is in a private repository for now and has no licence yet.

	== Who is working on it ==		== Who is working on it ==

ScotMesh chat hub

ScotMesh — Thu, 17 Sep 2026 12:36:40 GMT

Released 1.0.1; code is public at ScotMesh/scotmesh-chat

← Older revision		Revision as of 13:36, 17 September 2026
Line 15:		Line 15:
	== Status ==		== Status ==

	'''Live'''~~, version 1~~.0.0~~-rc~~.~~4 as of 13~~ September 2026~~, running on ScotMesh's own server~~.		'''Live''' on ScotMesh's own server. The latest release is [https://github.com/ScotMesh/scotmesh-chat/releases/tag/v1.0.1 v1.0.1] (15 September 2026).

	== Where to find it ==		== Where to find it ==
Line 29:		Line 29:
	\|}		\|}

	Commands are on [[Chat commands]]. The code is ~~in a private repository,~~ [https://github.com/~~A13xB0~~/scotmesh-chat ~~A13xB0~~/scotmesh-chat], under the MIT licence.		Commands are on [[Chat commands]]. The code is public at [https://github.com/ScotMesh/scotmesh-chat github.com/ScotMesh/scotmesh-chat], under the MIT licence.

	== Who is working on it ==		== Who is working on it ==

	Alex.		Alex.

	~~== Next ==~~

	* Release 1.0.0 once the release candidate has settled on the network.

	[[Category:Projects]]		[[Category:Projects]]

RNode

ScotMesh — Thu, 17 Sep 2026 12:36:39 GMT

Drop the 433 MHz profile: it has been scrapped, ScotMesh is 868 MHz only

← Older revision		Revision as of 13:36, 17 September 2026
Line 8:		Line 8:
	\|-		\|-
	!		!
	~~! ScotMesh 433~~
	! ScotMesh 868		! ScotMesh 868
	\|-		\|-
	\| '''Frequency'''		\| '''Frequency'''
	~~\| 433.775 MHz~~
	\| 869.4625 MHz		\| 869.4625 MHz
	\|-		\|-
	\| '''Bandwidth'''		\| '''Bandwidth'''
	~~\| 125 kHz~~
	\| 125 kHz		\| 125 kHz
	\|-		\|-
	\| '''Spreading factor'''		\| '''Spreading factor'''
	~~\| 8~~
	\| 9		\| 9
	\|-		\|-
	\| '''Coding rate'''		\| '''Coding rate'''
	~~\| 4/5~~
	\| 4/5		\| 4/5
	\|-		\|-
	\| '''TX power'''		\| '''TX power'''
	~~\| 7 dBm~~
	\| 22 dBm		\| 22 dBm
	\|}		\|}
Line 45:		Line 39:
	txpower = 22		txpower = 22
	spreadingfactor = 9		spreadingfactor = 9
	~~codingrate = 5~~

	~~# ScotMesh 433~~
	~~[[ScotMesh RNode]]~~
	~~type = RNodeInterface~~
	~~enabled = yes~~
	~~port = /dev/ttyUSB0~~
	~~frequency = 433775000~~
	~~bandwidth = 125000~~
	~~txpower = 7~~
	~~spreadingfactor = 8~~
	codingrate = 5</syntaxhighlight>		codingrate = 5</syntaxhighlight>
	== Flashing a board ==		== Flashing a board ==
Line 66:		Line 49:
	# '''Connect''' and '''Flash''' — pick the port from the browser prompt; nRF52 boards are put into their bootloader automatically (press reset twice if that fails).		# '''Connect''' and '''Flash''' — pick the port from the browser prompt; nRF52 boards are put into their bootloader automatically (press reset twice if that fails).
	# '''Provision''' — the board's identity block and firmware hash are written and verified, the same as <code>rnodeconf --autoinstall</code>.		# '''Provision''' — the board's identity block and firmware hash are written and verified, the same as <code>rnodeconf --autoinstall</code>.
	# '''Configure''' — for an RNode radio only Bluetooth; the radio profile is set by the app you connect it to, so the ScotMesh values are shown for you to enter there. For a standalone node: the ScotMesh ~~433 or~~ 868 profile, a name, its role and the identities allowed to manage it.		# '''Configure''' — for an RNode radio only Bluetooth; the radio profile is set by the app you connect it to, so the ScotMesh values are shown for you to enter there. For a standalone node: the ScotMesh 868 profile, a name, its role and the identities allowed to manage it.

	If the board does not appear in the port list, hold its BOOT button while plugging it in, and check you are using a data USB cable rather than a charge-only one.		If the board does not appear in the port list, hold its BOOT button while plugging it in, and check you are using a data USB cable rather than a charge-only one.
Line 72:		Line 55:
	=== Standalone node (microReticulum) ===		=== Standalone node (microReticulum) ===

	The same boards can run [https://github.com/~~A13xB0~~/microReticulum_Firmware microReticulum], the RNode firmware with a Reticulum transport stack built in. The board then ''is'' the node: it has its own identity, routes for others, serves a NomadNet page and can be managed over the mesh with <code>rnstatus -R</code> — no Raspberry Pi or computer attached. That is what ScotMesh uses for solar and hilltop relays; [[ScotMesh firmware]] explains what our build adds. Choose '''Standalone node''' in the flasher; the '''Seeed SenseCAP Solar Node P1''' (solar charger and battery built in) is the reference board and is built by ScotMesh — it does not exist in the upstream firmware. ''Reconfigure an existing node'' on the flasher's first screen connects over USB or Bluetooth to change settings later.		The same boards can run [https://github.com/ScotMesh/microReticulum_Firmware microReticulum], the RNode firmware with a Reticulum transport stack built in. The board then ''is'' the node: it has its own identity, routes for others, serves a NomadNet page and can be managed over the mesh with <code>rnstatus -R</code> — no Raspberry Pi or computer attached. That is what ScotMesh uses for solar and hilltop relays; [[ScotMesh firmware]] explains what our build adds. Choose '''Standalone node''' in the flasher; the '''Seeed SenseCAP Solar Node P1''' (solar charger and battery built in) is the reference board and is built by ScotMesh — it does not exist in the upstream firmware. ''Reconfigure an existing node'' on the flasher's first screen connects over USB or Bluetooth to change settings later.

	The command-line route does the same job and works on any platform:		The command-line route does the same job and works on any platform:
Line 92:		Line 75:
	* LilyGO T-Echo		* LilyGO T-Echo
	* RAK4631		* RAK4631
	* Seeed XIAO ESP32S3 with Wio-SX1262 (~~433 and~~ 868)		* Seeed XIAO ESP32S3 with Wio-SX1262 (868 version)
	* Homebrew RNode		* Homebrew RNode

	'''Buy the board for the band you want.''' An 868 MHz board cannot be moved to ~~433~~ MHz by changing settings — the radio and the antenna are physically different parts.		'''Buy the board for the band you want.''' ScotMesh uses 868 MHz only, and many boards are also sold for other bands. A board built for another band cannot be moved to 868 MHz by changing settings — the radio and the antenna are physically different parts.

	== Serial or Bluetooth ==		== Serial or Bluetooth ==

Project index

ScotMesh — Thu, 17 Sep 2026 12:36:38 GMT

Drop 433 MHz (scrapped); current firmware and chat hub versions; ScotMesh repo links

← Older revision		Revision as of 13:36, 17 September 2026
Line 26:		Line 26:
	\| [[The ScotMesh node]] \|\| The public transport node, chat hub, propagation node and Nomad Network node for Scotland \|\| Live \|\| [https://rns.scotmesh.net rns.scotmesh.net]		\| [[The ScotMesh node]] \|\| The public transport node, chat hub, propagation node and Nomad Network node for Scotland \|\| Live \|\| [https://rns.scotmesh.net rns.scotmesh.net]
	\|-		\|-
	\| [[RNode\|ScotMesh Flasher]] \|\| Set up an RNode radio or a standalone node from a browser, with the ScotMesh radio ~~profiles~~ built in \|\| Live \|\| [https://rnode.scotmesh.net rnode.scotmesh.net]		\| [[RNode\|ScotMesh Flasher]] \|\| Set up an RNode radio or a standalone node from a browser, with the ScotMesh radio profile built in \|\| Live \|\| [https://rnode.scotmesh.net rnode.scotmesh.net]
	\|-		\|-
	\| [[ScotMesh firmware]] \|\| Our build of microReticulum for solar and hilltop relays: remote management from the node's own page, telemetry, updates without a cable, the SenseCAP Solar Node P1 \|\| Live (v1.86-scotmesh.4) \|\| [https://github.com/~~A13xB0~~/microReticulum_Firmware GitHub]		\| [[ScotMesh firmware]] \|\| Our build of microReticulum for solar and hilltop relays: remote management from the node's own page, telemetry, updates without a cable, the SenseCAP Solar Node P1 \|\| Live (v1.86-scotmesh.6) \|\| [https://github.com/ScotMesh/microReticulum_Firmware GitHub]
	\|-		\|-
	\| LoRa gateways \|\| ScotMesh radios on air, linking LoRa users to the backbone \|\| Prototype: the first gateway is on air in Fife, ~~carrying both profiles~~ \|\| [[RNode]]		\| LoRa gateways \|\| ScotMesh radios on air, linking LoRa users to the backbone \|\| Prototype: the first gateway is on air in Fife, on the ScotMesh 868 profile \|\| [[RNode]]
	\|-		\|-
	\| [[Reticulum over MeshCore and Meshtastic]] \|\| Carry Reticulum traffic over MeshCore and Meshtastic radios, so existing meshes become Reticulum bearers \|\| Live: gateway at The Pole, Cadham \|\| [https://github.com/ScotMesh/RNS_Over_Meshcore MeshCore], [https://github.com/ScotMesh/RNS_Over_Meshtastic Meshtastic]		\| [[Reticulum over MeshCore and Meshtastic]] \|\| Carry Reticulum traffic over MeshCore and Meshtastic radios, so existing meshes become Reticulum bearers \|\| Live: gateway at The Pole, Cadham \|\| [https://github.com/ScotMesh/RNS_Over_Meshcore MeshCore], [https://github.com/ScotMesh/RNS_Over_Meshtastic Meshtastic]
	\|-		\|-
	\| [[ScotMesh chat hub]] \|\| The chat room: one conversation reached over RRC, as an LXMF group or on a Nomad Network page, with one name per identity \|\| Live (1.0.~~0-rc.4~~) \|\| [[The chat room]]		\| [[ScotMesh chat hub]] \|\| The chat room: one conversation reached over RRC, as an LXMF group or on a Nomad Network page, with one name per identity \|\| Live (v1.0.1) \|\| [[The chat room]]
	\|-		\|-
	\| [[ScotMesh Mail]] \|\| Email over Reticulum: identity login, a MeshChatX plugin, Nomad Network webmail, a postmaster for Sideband, and <code>@mail.scotmesh.net</code> to the internet \|\| Prototype \|\| [[ScotMesh Mail#Where to find it\|Addresses]]		\| [[ScotMesh Mail]] \|\| Email over Reticulum: identity login, a MeshChatX plugin, Nomad Network webmail, a postmaster for Sideband, and <code>@mail.scotmesh.net</code> to the internet \|\| Prototype \|\| [[ScotMesh Mail#Where to find it\|Addresses]]

Main Page

ScotMesh — Thu, 17 Sep 2026 12:36:37 GMT

Drop the 433 MHz profile: it has been scrapped, ScotMesh is 868 MHz only

← Older revision		Revision as of 13:36, 17 September 2026
Line 61:		Line 61:
	'''Behind CGNAT or a firewall you do not control?''' Use the I2P entry point instead; no port needs forwarding at either end. See [[Access over I2P]].		'''Behind CGNAT or a firewall you do not control?''' Use the I2P entry point instead; no port needs forwarding at either end. See [[Access over I2P]].

	'''Got a LoRa radio?''' ScotMesh's first gateway is on air in Fife, ~~carrying both profiles~~ below and linked to the backbone, and standalone [[ScotMesh firmware\|solar nodes]] are going out. Coverage is small so far, so a radio built anywhere in Scotland will hear the others as they arrive. Every radio must match all five settings exactly: a board with a different spreading factor is not weakly connected, it is completely deaf, and nothing reports an error. The 868 profile moved from 867.5 to 869.4625 MHz on 11 September 2026 (Ofcom's 869.40–869.65 MHz sub-band), so retune any radio still on the old frequency. [https://rnode.scotmesh.net rnode.scotmesh.net] applies ~~either~~ profile in one click.		'''Got a LoRa radio?''' ScotMesh's first gateway is on air in Fife, on the ScotMesh profile below and linked to the backbone, and standalone [[ScotMesh firmware\|solar nodes]] are going out. Coverage is small so far, so a radio built anywhere in Scotland will hear the others as they arrive. Every radio must match all five settings exactly: a board with a different spreading factor is not weakly connected, it is completely deaf, and nothing reports an error. The 868 profile moved from 867.5 to 869.4625 MHz on 11 September 2026 (Ofcom's 869.40–869.65 MHz sub-band), so retune any radio still on the old frequency. [https://rnode.scotmesh.net rnode.scotmesh.net] applies the profile in one click.

	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
	!		!
	~~! ScotMesh 433~~
	! ScotMesh 868		! ScotMesh 868
	\|-		\|-
	\| Frequency		\| Frequency
	~~\| 433.775 MHz~~
	\| 869.4625 MHz		\| 869.4625 MHz
	\|-		\|-
	\| Bandwidth		\| Bandwidth
	~~\| 125 kHz~~
	\| 125 kHz		\| 125 kHz
	\|-		\|-
	\| Spreading factor		\| Spreading factor
	~~\| 8~~
	\| 9		\| 9
	\|-		\|-
	\| Coding rate		\| Coding rate
	~~\| 4/5~~
	\| 4/5		\| 4/5
	\|-		\|-
	\| TX power		\| TX power
	~~\| 7 dBm~~
	\| 22 dBm		\| 22 dBm
	\|}		\|}
Line 157:		Line 151:
	\| ✔		\| ✔
	\| '''Web flasher for RNodes and nodes'''		\| '''Web flasher for RNodes and nodes'''
	\| [https://rnode.scotmesh.net rnode.scotmesh.net], with ~~both~~ ScotMesh ~~profiles~~ built in.		\| [https://rnode.scotmesh.net rnode.scotmesh.net], with the ScotMesh profile built in.
	\|-		\|-
	\| ✔		\| ✔
	\| '''LoRa gateway on air'''		\| '''LoRa gateway on air'''
	\| First gateway in Fife, ~~both profiles~~, linked to the backbone.		\| First gateway in Fife, at The Pole, Cadham, linked to the backbone. It also carries Reticulum over [[Reticulum over MeshCore and Meshtastic\|MeshCore and Meshtastic]].
	\|-		\|-
	\| ✔		\| ✔

Glossary

ScotMesh — Thu, 17 Sep 2026 12:36:36 GMT

rrc-hub retired: the chat room is run by the ScotMesh chat hub

← Older revision		Revision as of 13:36, 17 September 2026
Line 56:		Line 56:

	; RRC		; RRC
	: The chat protocol used by ScotMesh's chat room, run by a hub ~~program called <code>rrc-hub</code>~~. See [[The chat room]].		: The chat protocol used by ScotMesh's chat room, run by the [[ScotMesh chat hub]]. See [[The chat room]].

	; rnsd, rnstatus, rnpath, rnprobe		; rnsd, rnstatus, rnpath, rnprobe

Antennas and siting

ScotMesh — Thu, 17 Sep 2026 12:36:35 GMT

Drop the 433 MHz profile: it has been scrapped, ScotMesh is 868 MHz only

← Older revision		Revision as of 13:36, 17 September 2026
Line 3:		Line 3:
	== The antenna must match the band ==		== The antenna must match the band ==

	An antenna is tuned for a frequency range. ~~A 433 MHz~~ antenna on an 868 MHz board ~~(or the other way round)~~ reflects most of the transmitter's power back into it: range collapses, and at 22 dBm the radio can be damaged. Check the band printed on the antenna, and '''never transmit with no antenna connected'''.		An antenna is tuned for a frequency range. An antenna made for another band on an 868 MHz board reflects most of the transmitter's power back into it: range collapses, and at 22 dBm the radio can be damaged. Check the band printed on the antenna, and '''never transmit with no antenna connected'''.

	Cheap boards often ship with a generic stub that is not tuned for ~~either band~~. Replacing it is the single best upgrade.		Cheap boards often ship with a generic stub that is not tuned for 868 MHz at all. Replacing it is the single best upgrade.

	{\| class="wikitable"		{\| class="wikitable"
Line 12:		Line 12:
	\| Stub or “rubber duck” \|\| 0 to 2 dBi \|\| Handhelds and testing on a desk		\| Stub or “rubber duck” \|\| 0 to 2 dBi \|\| Handhelds and testing on a desk
	\|-		\|-
	\| Quarter-wave whip (~~433: about 16.5 cm; 868:~~ about 8.2 cm) \|\| about 2 dBi \|\| Cheap, easy, works well with a ground plane (a metal box lid or a few radials)		\| Quarter-wave whip (about 8.2 cm at 868 MHz) \|\| about 2 dBi \|\| Cheap, easy, works well with a ground plane (a metal box lid or a few radials)
	\|-		\|-
	\| Half-wave dipole \|\| about 2 dBi \|\| Needs no ground plane; a good indoor or window antenna		\| Half-wave dipole \|\| about 2 dBi \|\| Needs no ground plane; a good indoor or window antenna
Line 36:		Line 36:
	== Cable and connectors ==		== Cable and connectors ==

	Coaxial cable loses signal, more at ~~868 MHz than at 433~~, and thin cable loses most. Ten metres of RG174 at 868 MHz throws away roughly half the power; ten metres of LMR-400 loses almost nothing. Keep the run short, use decent cable (LMR-240 or better for anything over a few metres), and put the radio near the antenna if you can: a [[ScotMesh firmware\|standalone node]] in a box at the top of the pole with a short tail to the antenna beats a long feeder to a radio indoors.		Coaxial cable loses signal, more at higher frequencies, and thin cable loses most. Ten metres of RG174 at 868 MHz throws away roughly half the power; ten metres of LMR-400 loses almost nothing. Keep the run short, use decent cable (LMR-240 or better for anything over a few metres), and put the radio near the antenna if you can: a [[ScotMesh firmware\|standalone node]] in a box at the top of the pole with a short tail to the antenna beats a long feeder to a radio indoors.

	Connectors: most boards have a u.FL or IPEX socket; most antennas have an SMA plug. Check whether you need SMA or '''RP-SMA''' (reverse polarity; common on Wi-Fi kit); they look alike and do not mate. Every adapter is a small loss and a place for water to get in.		Connectors: most boards have a u.FL or IPEX socket; most antennas have an SMA plug. Check whether you need SMA or '''RP-SMA''' (reverse polarity; common on Wi-Fi kit); they look alike and do not mate. Every adapter is a small loss and a place for water to get in.
Line 50:		Line 50:
	== Two power notes ==		== Two power notes ==

	* The licence-free bands limit both transmit power and how much of the time you may transmit. The ScotMesh ~~profiles are~~ within those limits; adding a high-gain antenna raises your effective radiated power, so do not pair the 22 dBm profile with a high-gain directional antenna without checking the rules for the band.		* The licence-free bands limit both transmit power and how much of the time you may transmit. The ScotMesh profile is within those limits; adding a high-gain antenna raises your effective radiated power, so do not pair the 22 dBm profile with a high-gain directional antenna without checking the rules for the band.
	* Transmit power is the least effective knob. If a link is marginal, raise the antenna, shorten the cable or move the node before raising the power.		* Transmit power is the least effective knob. If a link is marginal, raise the antenna, shorten the cable or move the node before raising the power.

MeshCore as a Reticulum Interface

ScotMesh — Thu, 17 Sep 2026 10:48:27 GMT

ScotMesh deleted page MeshCore as a Reticulum Interface Replaced by Reticulum over MeshCore and Meshtastic: the idea is built and live

About ScotMesh

ScotMesh — Thu, 17 Sep 2026 10:48:08 GMT

Link to Reticulum over MeshCore and Meshtastic, which replaces MeshCore as a Reticulum Interface

← Older revision		Revision as of 11:48, 17 September 2026
Line 26:		Line 26:
	* '''Reticulum''' is a networking stack rather than a radio system: it joins LoRa, the internet, I2P and anything else that can carry data into one encrypted network. See [[What Reticulum is]] and [[How Reticulum works]].		* '''Reticulum''' is a networking stack rather than a radio system: it joins LoRa, the internet, I2P and anything else that can carry data into one encrypted network. See [[What Reticulum is]] and [[How Reticulum works]].

	They are complementary rather than rivals, and some of our [[Projects\|projects]] join them together, for example [[MeshCore ~~as a Reticulum Interface~~\|carrying Reticulum over MeshCore]].		They are complementary rather than rivals, and some of our [[Projects\|projects]] join them together, for example [[Reticulum over MeshCore and Meshtastic\|carrying Reticulum over MeshCore and Meshtastic]].

	== What ScotMesh runs for Reticulum ==		== What ScotMesh runs for Reticulum ==

Project index

ScotMesh — Thu, 17 Sep 2026 10:48:07 GMT

Link to Reticulum over MeshCore and Meshtastic, which replaces MeshCore as a Reticulum Interface

← Older revision		Revision as of 11:48, 17 September 2026
Line 32:		Line 32:
	\| LoRa gateways \|\| ScotMesh radios on air, linking LoRa users to the backbone \|\| Prototype: the first gateway is on air in Fife, carrying both profiles \|\| [[RNode]]		\| LoRa gateways \|\| ScotMesh radios on air, linking LoRa users to the backbone \|\| Prototype: the first gateway is on air in Fife, carrying both profiles \|\| [[RNode]]
	\|-		\|-
	\| [[MeshCore ~~as a Reticulum Interface~~]] \|\| Carry Reticulum traffic over MeshCore radios, so an existing ~~MeshCore mesh becomes a~~ Reticulum ~~bearer~~ \|\| ~~Idea~~ \|\| [[MeshCore ~~as a Reticulum Interface~~]]		\| [[Reticulum over MeshCore and Meshtastic]] \|\| Carry Reticulum traffic over MeshCore and Meshtastic radios, so existing meshes become Reticulum bearers \|\| Live: gateway at The Pole, Cadham \|\| [https://github.com/ScotMesh/RNS_Over_Meshcore MeshCore], [https://github.com/ScotMesh/RNS_Over_Meshtastic Meshtastic]
	\|-		\|-
	\| [[ScotMesh chat hub]] \|\| The chat room: one conversation reached over RRC, as an LXMF group or on a Nomad Network page, with one name per identity \|\| Live (1.0.0-rc.4) \|\| [[The chat room]]		\| [[ScotMesh chat hub]] \|\| The chat room: one conversation reached over RRC, as an LXMF group or on a Nomad Network page, with one name per identity \|\| Live (1.0.0-rc.4) \|\| [[The chat room]]

Projects

ScotMesh — Thu, 17 Sep 2026 10:48:07 GMT

Link to Reticulum over MeshCore and Meshtastic, which replaces MeshCore as a Reticulum Interface

← Older revision		Revision as of 11:48, 17 September 2026
Line 2:		Line 2:

	* [[Project index]]		* [[Project index]]
	* [[MeshCore ~~as a Reticulum Interface~~]]		* [[Reticulum over MeshCore and Meshtastic]]
	* [[ScotMesh chat hub]]		* [[ScotMesh chat hub]]
	* [[ScotMesh Mail]]		* [[ScotMesh Mail]]

	[[Category:Books]]		[[Category:Books]]

Main Page

ScotMesh — Thu, 17 Sep 2026 10:48:06 GMT

Link to Reticulum over MeshCore and Meshtastic, which replaces MeshCore as a Reticulum Interface

← Older revision		Revision as of 11:48, 17 September 2026
Line 192:		Line 192:
	\|-		\|-
	\| '''What is ScotMesh building?'''		\| '''What is ScotMesh building?'''
	\| The [[Project index\|project index]]: the [[ScotMesh firmware]], the flasher, and [[MeshCore ~~as a~~ Reticulum ~~Interface\|~~MeshCore ~~as a Reticulum interface~~]].		\| The [[Project index\|project index]]: the [[ScotMesh firmware]], the flasher, and [[Reticulum over MeshCore and Meshtastic\|Reticulum over MeshCore and Meshtastic]].
	\|-		\|-
	\| '''I want to read and watch more'''		\| '''I want to read and watch more'''

Reticulum over MeshCore and Meshtastic

ScotMesh — Thu, 17 Sep 2026 10:48:04 GMT

New page: reaching Reticulum through a MeshCore or Meshtastic radio via the gateway at The Pole

New page

This page is for people who already have a '''MeshCore''' or '''Meshtastic''' radio and want to use it to reach Reticulum, with no internet connection and no [[RNode]]. If you have never heard of Reticulum, start with [[What Reticulum is|what Reticulum is]] and come back.

== What you are actually doing ==

Reticulum runs on your computer as usual. Normally it reaches the network over the internet ([[Connecting to ScotMesh]]) or over an [[RNode]]. Here it uses '''your MeshCore or Meshtastic radio''' as its link instead.

Reticulum's traffic is cut into small pieces and sent on a separate, private channel on your radio. A ScotMesh gateway on the same channel puts the pieces back together and passes them on to [[The ScotMesh Backbone|the backbone]]. That gateway is at '''The Pole''' in Cadham, and it is listed on node maps as ''ScotMesh RNode Cadham''.

Your radio keeps working for its own network at the same time. MeshCore or Meshtastic users around you never see the tunnel, because it runs on its own channel with its own key.

== Is this for you? ==

{| class="wikitable"
! If you have… !! Use
|-
| An internet connection, even a slow one || [[Connecting to ScotMesh]]. It is faster and costs no airtime.
|-
| An RNode, or a board you could flash as one || [[RNode]]. Reticulum runs natively on it and is many times faster.
|-
| Only a MeshCore or Meshtastic radio, within reach of the gateway || '''This page.'''
|}

Expect it to be '''slow'''. It is fine for messages (LXMF), the [[The chat room|chat room]] and small [[Nomad Network]] pages. It is no good for files or voice.

== The two routes ==

{| class="wikitable"
! !! Over MeshCore !! Over Meshtastic
|-
| '''Status''' || '''Working''' — gateway live at The Pole || '''Working''' — gateway live at The Pole since 17 September 2026. New, so tell us how it goes.
|-
| '''Your radio''' || MeshCore '''companion''' firmware v1.17 or later, over USB, Bluetooth or WiFi || Any Meshtastic node, over USB, Bluetooth or WiFi
|-
| '''Radio settings''' || UK/EU Narrow: 869.618 MHz, 62.5 kHz, SF8, CR 4/8 || EU_868, LongFast
|-
| '''Region''' || <code>sco</code> || —
|-
| '''Software''' || <code>MeshCore_Raw_Interface.py</code> from [https://github.com/ScotMesh/RNS_Over_Meshcore ScotMesh/RNS_Over_Meshcore] || <code>Meshtastic_Interface.py</code> from [https://github.com/ScotMesh/RNS_Over_Meshtastic ScotMesh/RNS_Over_Meshtastic]
|-
| '''Speed''' || At best a few hundred bytes a second || Slower: one piece of up to 155 bytes every 8 seconds on LongFast
|}

== Before you start ==

* '''Reticulum installed''' on a computer ([[Installing Reticulum]]), or '''MeshChatX''' ([[Choosing a client]]).
* '''Your radio''', connected to that computer.
* '''A path to the gateway''': in range of The Pole, or reaching it through MeshCore repeaters that relay the <code>sco</code> region.
* '''The tunnel channel details''', in the table below.

== Tunnel details ==

These are shared on purpose, so anyone can join the tunnel. The channel key only keeps the tunnel's traffic separate from ordinary channels; it is not what keeps you private. Reticulum encrypts everything you send end to end, whatever it travels over.

{| class="wikitable"
! !! MeshCore !! Meshtastic
|-
| '''Channel name''' || <code>RNSTunnel</code> || <code>RNS</code>
|-
| '''Secret''' || <code>38a46b4349a14b05c70328f444932033</code> || in the link below
|-
| '''Add it with''' || Reticulum sets it on your radio for you (step 3) || [https://meshtastic.org/e/?add=true#CicSIKzMw9L_sPDY_S2bF9AB3mRvgeyDwAhw9K6HLEBEzbc9GgNSTlMSCAgBOANAA0gB this channel link] — opens in the Meshtastic app and adds the channel next to your own
|-
| '''Region''' || <code>sco</code> || —
|}

-----

== Over MeshCore ==

[[File:Reticulum over MeshCore.svg|center|frameless|upright=3.2|alt=Diagram: Reticulum on your computer talks to your MeshCore companion radio over USB, Bluetooth or WiFi. The radio carries the tunnel on the RNSTunnel channel, directly or through MeshCore repeaters in region sco, to The Pole at Cadham, where the openHop repeater hands it to the RNSBridge companion and rnsd, which connects to the ScotMesh backbone over TCP. Broadcasts go as flooded channel datagrams of up to 148 bytes; traffic to a known peer goes as raw packets of up to 140 bytes along the repeater path.|How Reticulum travels over MeshCore to the ScotMesh backbone]]

=== 1. Set up the radio ===

# Flash '''companion''' firmware, v1.17 or later. Earlier versions lack the two commands the tunnel uses. Repeater or room server firmware will not work.
# Set the radio to '''UK/EU Narrow''': 869.618 MHz, 62.5 kHz, SF8, coding rate 4/8.
# '''Pick a spare channel slot''' for the tunnel, such as 7. Reticulum writes its channel into that slot when it connects, so '''do not use 0''': on most radios that is your Public channel, and it would be replaced.

A companion radio talks to one app at a time. While Reticulum is using it, your phone's MeshCore app cannot connect, and the other way round.

=== 2. Get the interface ===

Download <code>Interface/MeshCore_Raw_Interface.py</code> from [https://github.com/ScotMesh/RNS_Over_Meshcore ScotMesh/RNS_Over_Meshcore] and put it in Reticulum's <code>interfaces</code> folder:

{| class="wikitable"
! System !! Folder
|-
| Linux, macOS || <code>~/.reticulum/interfaces/</code>
|-
| Windows || <code>C:\Users\<you>\.reticulum\interfaces\</code>
|}

Create the folder if it is not there. The interface needs nothing beyond Reticulum itself, plus one library for your connection:

<syntaxhighlight lang="text">pip install pyserial # USB
pip install bleak # Bluetooth</syntaxhighlight>
Use <code>~/reticulum/bin/pip</code> instead if you installed Reticulum in a virtual environment. WiFi (TCP) needs nothing extra.

=== 3. Add it to your config ===

Add this block under <code>[interfaces]</code> in your Reticulum config file (where to find it: [[Connecting to ScotMesh#3. Find the config file|Connecting to ScotMesh]]). Keep exactly one of the three connection blocks.

<syntaxhighlight lang="ini"> [[ScotMesh over MeshCore]]
type = MeshCore_Raw_Interface
interface_enabled = yes

# USB
transport = serial
port = /dev/ttyUSB0 # Windows: COM3 or similar
baudrate = 115200

# Bluetooth - instead of the USB lines
# transport = ble
# ble_name = MeshCore # part of the radio's Bluetooth name

# WiFi - instead of the USB lines
# transport = tcp
# host = 192.168.1.50 # the radio's address
# tcp_port = 5000

# The ScotMesh tunnel
channel_idx = 7 # a spare slot, never 0
channel_name = RNSTunnel
channel_secret = 38a46b4349a14b05c70328f444932033
flood_scope = sco

# You are an end user, not a relay
can_route = no</syntaxhighlight>
Leave <code>mode</code> out: the default is right for an end user.

=== 4. Start it and check ===

# Start Reticulum: <code>rnsd</code>, or restart it if it was already running.
# Run <code>rnstatus</code>. '''ScotMesh over MeshCore''' should be listed as '''Up'''.
# Look for the ScotMesh node. The first answer can take a minute or two over radio.

<syntaxhighlight lang="text">rnpath 10a839df2c50635bcb0c8a299b9ca0f8</syntaxhighlight>
A reply such as ''Path found … via … on MeshCore_Raw_Interface'' means you are through. From here everything in [[Services and addresses]] works, just slowly.

=== With MeshChatX instead ===

# Open '''Settings''', then '''Interfaces''', and install a custom interface module. Upload <code>MeshCore_Raw_Interface.py</code>.
# Add an interface of type <code>MeshCore_Raw_Interface</code> with the same settings as the block above.
# Restart when asked.

MeshChatX already includes the USB and Bluetooth libraries.

On an '''Android phone''', Sideband can only use the WiFi (TCP) connection. See the fork's README for its service plugin.

-----

== Over Meshtastic ==

[[File:Reticulum over Meshtastic.svg|center|frameless|upright=3.2|alt=Diagram: Reticulum on your computer talks to your Meshtastic node over USB, Bluetooth or WiFi. The node carries the tunnel on its RNS channel, on EU_868 LongFast, directly or through other Meshtastic nodes, to The Pole at Cadham, where RepeaterTastic's radio hands it to the hosted node RSN Bridge and rnsd, which connects to the ScotMesh backbone over TCP. Each Reticulum packet is cut into pieces of up to 155 bytes, sent one every 8 seconds, and missing pieces are asked for again.|How Reticulum travels over Meshtastic to the ScotMesh backbone]]

=== 1. Set up the radio ===

# Any Meshtastic node on '''EU_868''' with the '''LongFast''' preset, which is the default in the UK.
# Open the [https://meshtastic.org/e/?add=true#CicSIKzMw9L_sPDY_S2bF9AB3mRvgeyDwAhw9K6HLEBEzbc9GgNSTlMSCAgBOANAA0gB channel link] on the phone or computer your node is paired with. It adds a channel called <code>RNS</code> next to your own.
# In the Meshtastic app's channel list, '''note which slot <code>RNS</code> landed in'''. It is usually 1, the first slot after your primary channel.

Your normal channels keep working. The node can stay paired with your phone while Reticulum uses it over USB or WiFi.

=== 2. Get the Meshtastic interface ===

Download <code>Interface/Meshtastic_Interface.py</code> from [https://github.com/ScotMesh/RNS_Over_Meshtastic ScotMesh/RNS_Over_Meshtastic] into Reticulum's <code>interfaces</code> folder (the same folder as for [[#2. Get the interface|MeshCore]]). It needs the Meshtastic library:

<syntaxhighlight lang="text">pip install meshtastic</syntaxhighlight>
'''Use ScotMesh's copy, not the original.''' The original can only use your primary channel, and it sends pieces too big for the gateway.

=== 3. Add the Meshtastic block to your config ===

Keep exactly one of the three connection lines.

<syntaxhighlight lang="ini"> [[ScotMesh over Meshtastic]]
type = Meshtastic_Interface
enabled = yes

port = /dev/ttyUSB0 # USB (Windows: COM3 or similar)
# tcp_port = 192.168.1.60 # WiFi: the node's address
# ble_port = Meshtastic_1234 # Bluetooth: the node's name

data_speed = 0 # LongFast
channel_index = 1 # the slot RNS landed in
hop_limit = 3</syntaxhighlight>
Leave <code>mode</code> out, as for MeshCore.

=== 4. Start it and check it ===

As for MeshCore:
# Start <code>rnsd</code>.
# Check that '''ScotMesh over Meshtastic''' is '''Up''' in <code>rnstatus</code>.
# Run <code>rnpath 10a839df2c50635bcb0c8a299b9ca0f8</code>.

Allow a few minutes: Meshtastic sends only one piece every 8 seconds.

-----

== Keeping the air clear ==

The UK band these radios use allows each transmitter only '''10% of the time''', and everyone shares it.
* '''Do not set <code>mode = gateway</code>''' on your end. A gateway pushes every route it knows onto the radio and can flood the channel.
* '''Do not turn on <code>enable_transport</code>''' just for this. Your machine does not need to relay for others.
* '''Send messages, not files.''' A single photo can hold the channel for many minutes.
* '''Keep <code>can_route = no</code>''' unless ScotMesh has asked you to run a relay.

== If it does not work ==

{| class="wikitable"
! What you see !! Try
|-
| The interface is not listed in <code>rnstatus</code> || The file is not in the <code>interfaces</code> folder, or <code>type</code> is misspelt. Check the Reticulum log.
|-
| Listed, but '''Down''' || Wrong port or address, or another app (your phone) is connected to the radio.
|-
| ''unsupported command'' in the log || The radio's firmware is older than v1.17. Update the companion firmware.
|-
| Up, but <code>rnpath</code> never finds anything || Wrong channel secret, wrong radio settings, or no path to The Pole. Check the secret against [[#Tunnel details|Tunnel details]] first, then the radio settings, then ask in [[The chat room|the chat room]] whether anyone can hear you.
|-
| Your Public channel disappeared || <code>channel_idx</code> was 0. Pick a spare slot, then add the Public channel back in the MeshCore app.
|-
| Meshtastic: Up, but nothing arrives || <code>channel_index</code> doesn't match the slot the <code>RNS</code> channel is in, or the node isn't on EU_868 LongFast.
|}

== See also ==

* [https://github.com/ScotMesh/RNS_Over_Meshcore ScotMesh/RNS_Over_Meshcore] and [https://github.com/ScotMesh/RNS_Over_Meshtastic ScotMesh/RNS_Over_Meshtastic] — the interfaces' code
* [[RNode]] — the faster radio route
* [[Services and addresses]]

[[Category:Getting Started]]

File:Reticulum over Meshtastic.svg

ScotMesh — Thu, 17 Sep 2026 10:48:03 GMT

ScotMesh uploaded File:Reticulum over Meshtastic.svg == Summary == Diagram for Reticulum over MeshCore and Meshtastic

New page

== Summary ==
Diagram for Reticulum over MeshCore and Meshtastic

File:Reticulum over MeshCore.svg

ScotMesh — Thu, 17 Sep 2026 10:48:03 GMT

ScotMesh uploaded File:Reticulum over MeshCore.svg == Summary == Diagram for Reticulum over MeshCore and Meshtastic

New page

== Summary ==
Diagram for Reticulum over MeshCore and Meshtastic

MediaWiki:Common.css

Maintenance script — Sun, 13 Sep 2026 12:07:22 GMT

ScotMesh brand: scotmesh/reticulum lockup in the site header

MediaWiki:Sitenotice

Maintenance script — Sun, 13 Sep 2026 12:07:22 GMT

ScotMesh brand: the lockup carries the name, so the header title is just Wiki

← Older revision		Revision as of 13:07, 13 September 2026
Line 1:		Line 1:
	<div class="sm-header">[[Main Page\|<span class="sm-flag" title="ScotMesh Reticulum Wiki"></span>]]<div class="sm-header-text"><div class="sm-header-title">[[Main Page\|~~ScotMesh Reticulum~~ Wiki]]</div><div class="sm-header-sub">Reticulum in Scotland: free, encrypted, run by the community</div></div></div>		<div class="sm-header">[[Main Page\|<span class="sm-flag" title="ScotMesh Reticulum Wiki"></span>]]<div class="sm-header-text"><div class="sm-header-title">[[Main Page\|Wiki]]</div><div class="sm-header-sub">Reticulum in Scotland: free, encrypted, run by the community</div></div></div>

MediaWiki:Common.css

Maintenance script — Sun, 13 Sep 2026 12:02:29 GMT

ScotMesh brand: keep hero art clear of the text

Show changes

MediaWiki:Citizen.css

Maintenance script — Sun, 13 Sep 2026 11:58:59 GMT

ScotMesh brand: Reticulum colours and IBM Plex fonts

New page

/* ScotMesh brand, Reticulum version: https://github.com/ScotMesh/branding
Fonts are self-hosted from /images/scotmesh-brand/fonts. Backgrounds keep Citizen's default hue (262, the Night blue);
only links, buttons and focus rings take the Reticulum violet. */
@font-face { font-family: "IBM Plex Mono"; font-weight: 400; font-style: normal; font-display: swap; src: url(/images/scotmesh-brand/fonts/ibm-plex-mono-400.woff2) format("woff2"); }
@font-face { font-family: "IBM Plex Mono"; font-weight: 600; font-style: normal; font-display: swap; src: url(/images/scotmesh-brand/fonts/ibm-plex-mono-600.woff2) format("woff2"); }
@font-face { font-family: "IBM Plex Sans Condensed"; font-weight: 400; font-style: normal; font-display: swap; src: url(/images/scotmesh-brand/fonts/ibm-plex-sans-condensed-400.woff2) format("woff2"); }
@font-face { font-family: "IBM Plex Sans Condensed"; font-weight: 600; font-style: normal; font-display: swap; src: url(/images/scotmesh-brand/fonts/ibm-plex-sans-condensed-600.woff2) format("woff2"); }

:root {
--font-family-citizen-base: "IBM Plex Sans Condensed", "Roboto", "Roboto-fallback", sans-serif;
--font-family-citizen-monospace: "IBM Plex Mono", "Roboto Mono", monospace;

/* Reticulum deep violet #6A51A4 for light pages */
--color-progressive: oklch( 50% 0.13 295 );
--color-progressive--hover: oklch( 56% 0.13 295 );
--color-progressive--active: oklch( 45% 0.13 295 );
--color-progressive--focus: oklch( 50% 0.13 295 );
--background-color-progressive: oklch( 50% 0.13 295 );
--background-color-progressive--hover: oklch( 56% 0.13 295 );
--background-color-progressive--active: oklch( 45% 0.13 295 );
--background-color-progressive--focus: oklch( 50% 0.13 295 );
--background-color-progressive-subtle: oklch( 50% 0.13 295 / 0.1 );
--background-color-progressive-subtle--hover: oklch( 50% 0.13 295 / 0.14 );
--background-color-progressive-subtle--active: oklch( 50% 0.13 295 / 0.18 );
--border-color-progressive: oklch( 50% 0.13 295 );
--border-color-progressive--hover: oklch( 56% 0.13 295 );
--border-color-progressive--active: oklch( 45% 0.13 295 );
--border-color-progressive--focus: oklch( 50% 0.13 295 );
--outline-color-progressive--focus: oklch( 50% 0.13 295 );
}

/* Reticulum tint #B199F4 for text on dark pages; buttons sit a step darker so white labels stay readable */
:root.skin-theme-clientpref-night {
--color-progressive: oklch( 74% 0.13 295 );
--color-progressive--hover: oklch( 80% 0.11 295 );
--color-progressive--active: oklch( 68% 0.13 295 );
--color-progressive--focus: oklch( 74% 0.13 295 );
--background-color-progressive: oklch( 58% 0.13 295 );
--background-color-progressive--hover: oklch( 63% 0.13 295 );
--background-color-progressive--active: oklch( 54% 0.13 295 );
--background-color-progressive--focus: oklch( 58% 0.13 295 );
--background-color-progressive-subtle: oklch( 74% 0.13 295 / 0.12 );
--background-color-progressive-subtle--hover: oklch( 74% 0.13 295 / 0.16 );
--background-color-progressive-subtle--active: oklch( 74% 0.13 295 / 0.2 );
--border-color-progressive: oklch( 74% 0.13 295 );
--border-color-progressive--hover: oklch( 80% 0.11 295 );
--border-color-progressive--active: oklch( 68% 0.13 295 );
--border-color-progressive--focus: oklch( 74% 0.13 295 );
--outline-color-progressive--focus: oklch( 74% 0.13 295 );
}
@media ( prefers-color-scheme: dark ) {
:root.skin-theme-clientpref-os {
--color-progressive: oklch( 74% 0.13 295 );
--color-progressive--hover: oklch( 80% 0.11 295 );
--color-progressive--active: oklch( 68% 0.13 295 );
--color-progressive--focus: oklch( 74% 0.13 295 );
--background-color-progressive: oklch( 58% 0.13 295 );
--background-color-progressive--hover: oklch( 63% 0.13 295 );
--background-color-progressive--active: oklch( 54% 0.13 295 );
--background-color-progressive--focus: oklch( 58% 0.13 295 );
--background-color-progressive-subtle: oklch( 74% 0.13 295 / 0.12 );
--background-color-progressive-subtle--hover: oklch( 74% 0.13 295 / 0.16 );
--background-color-progressive-subtle--active: oklch( 74% 0.13 295 / 0.2 );
--border-color-progressive: oklch( 74% 0.13 295 );
--border-color-progressive--hover: oklch( 80% 0.11 295 );
--border-color-progressive--active: oklch( 68% 0.13 295 );
--border-color-progressive--focus: oklch( 74% 0.13 295 );
--outline-color-progressive--focus: oklch( 74% 0.13 295 );
}
}

Projects

ScotMesh — Sun, 13 Sep 2026 11:17:34 GMT

Add the chat hub and ScotMesh Mail

← Older revision		Revision as of 12:17, 13 September 2026
Line 3:		Line 3:
	* [[Project index]]		* [[Project index]]
	* [[MeshCore as a Reticulum Interface]]		* [[MeshCore as a Reticulum Interface]]
			* [[ScotMesh chat hub]]
			* [[ScotMesh Mail]]

	[[Category:Books]]		[[Category:Books]]

Project index

ScotMesh — Sun, 13 Sep 2026 11:17:33 GMT

Add the chat hub and ScotMesh Mail

← Older revision		Revision as of 12:17, 13 September 2026
Line 33:		Line 33:
	\|-		\|-
	\| [[MeshCore as a Reticulum Interface]] \|\| Carry Reticulum traffic over MeshCore radios, so an existing MeshCore mesh becomes a Reticulum bearer \|\| Idea \|\| [[MeshCore as a Reticulum Interface]]		\| [[MeshCore as a Reticulum Interface]] \|\| Carry Reticulum traffic over MeshCore radios, so an existing MeshCore mesh becomes a Reticulum bearer \|\| Idea \|\| [[MeshCore as a Reticulum Interface]]
			\|-
			\| [[ScotMesh chat hub]] \|\| The chat room: one conversation reached over RRC, as an LXMF group or on a Nomad Network page, with one name per identity \|\| Live (1.0.0-rc.4) \|\| [[The chat room]]
			\|-
			\| [[ScotMesh Mail]] \|\| Email over Reticulum: identity login, a MeshChatX plugin, Nomad Network webmail, a postmaster for Sideband, and <code>@mail.scotmesh.net</code> to the internet \|\| Prototype \|\| [[ScotMesh Mail#Where to find it\|Addresses]]
	\|-		\|-
	\| This wiki \|\| Documentation for all of the above \|\| Live \|\| You are reading it		\| This wiki \|\| Documentation for all of the above \|\| Live \|\| You are reading it

ScotMesh chat hub

ScotMesh — Sun, 13 Sep 2026 11:17:31 GMT

New project page: the ScotMesh chat hub

New page

'''The ScotMesh chat hub''' runs ScotMesh's chat room: one conversation that people reach from an RRC chat client, as an LXMF group, or on a Nomad Network page, with everyone seeing the same messages under the same names. How to join is on [[The chat room]].

== What it is ==

One program that connects to [[The ScotMesh Backbone|the backbone]] over TCP, with no Reticulum daemon of its own, and serves three ways into the same room:

* '''The RRC room''' <code>#scotmesh</code>, for MeshChatX, NomadNet, rrc-tui and WeeChat.
* '''The LXMF group''', for Sideband, Columba, MeshChatX and NomadNet. Messages arrive as <code>Name: message</code>.
* '''The chat page''', read in NomadNet or MeshChatX, where you can post once you identify.

Each Reticulum identity holds one name everywhere, and lookalikes of a name that is taken are refused. When you come back you catch up on what you missed. LXMF delivery can be turned off or left automatic. Operators can moderate, and what they do is logged. Messages are kept for 7 days. The [[Propagation node|propagation node]] holds group messages for members who are away.

It replaced the earlier RRC hub and LXMF bridge.

== Status ==

'''Live''', version 1.0.0-rc.4 as of 13 September 2026, running on ScotMesh's own server.

== Where to find it ==

{| class="wikitable"
! Way in !! Address
|-
| RRC room || hub <code>004e5a15da221d9a236b0e8d74195f13</code>, room <code>scotmesh</code>
|-
| LXMF group || <code>625ad393ca4df62a1382f9d936322a0a</code>
|-
| Chat page || <code>c229a2c7d410e00b71f877375ae846bf:/page/index.mu</code>
|}

Commands are on [[Chat commands]]. The code is in a private repository, [https://github.com/A13xB0/scotmesh-chat A13xB0/scotmesh-chat], under the MIT licence.

== Who is working on it ==

Alex.

== Next ==

* Release 1.0.0 once the release candidate has settled on the network.

[[Category:Projects]]

ScotMesh Mail

ScotMesh — Sun, 13 Sep 2026 11:17:30 GMT

New project page: ScotMesh Mail (rmail)

New page

'''ScotMesh Mail''' is email over Reticulum. Your Reticulum identity is your login, so there are no passwords. Mail between people on the mesh never touches the internet, and a gateway links <code>@mail.scotmesh.net</code> to ordinary email.

== What it is ==

A mail server, '''rmail''', and the ways to use it:

* '''MeshChatX''': a plugin with folders, writing and replying, encrypted and signed mail, and your mail key.
* '''Nomad Network''': the server is also a node with webmail pages, readable in NomadNet or MeshChatX's page browser.
* '''Sideband''' and any other LXMF app: message the server's '''postmaster'''. It sends a notice when mail arrives, can forward whole messages, and takes commands such as <code>STATUS</code>, <code>INBOX</code>, <code>READ</code> and <code>REPLY</code>. Start a message with <code>to: someone@…</code> to send mail.

Several identities can share one mailbox, for example your phone and your laptop, or a group's shared address. Mail can be kept encrypted on the server with keys only the mailbox's members hold. Mail is text only and kept small, because it crosses radio links: attachments are refused.

Servers announce themselves like Nomad Network nodes, and anyone can run one. Addresses look like <code>name@<server address>.rns</code> on the mesh, and <code>name@mail.scotmesh.net</code> from the internet.

== Status ==

'''Prototype''', as of 13 September 2026. The ScotMesh server is running and joined to [[The ScotMesh Backbone|the backbone]], with the first mailbox. Sign-up is by invitation only. Mail from the internet is waiting on its firewall port being opened, and mail to the internet may land in spam folders for now, because the server's address can't be given a matching reverse DNS name.

== Where to find it ==

{| class="wikitable"
! What !! Address
|-
| Mail server || <code>45b45ffb1ce546993728cb31e9846b95</code>
|-
| Postmaster (LXMF) || <code>044b450f5f66efc790c25d703121d4a5</code>
|-
| Webmail (Nomad Network) || <code>65f06cd68ddedd8929471af0d82c1a7d:/page/index.mu</code>
|-
| Internet domain || <code>mail.scotmesh.net</code>
|}

It runs on ScotMesh's own server alongside the [[ScotMesh chat hub|chat hub]], and stores messages for mailboxes that are away through the [[Propagation node|propagation node]]. The code is in a private repository, [https://github.com/A13xB0/rmail A13xB0/rmail]; it has no licence yet.

== Who is working on it ==

Alex.

== Next ==

* Open the mail port so internet mail can arrive, and send a first message each way.
* Try the MeshChatX plugin with real users, and write a how-to page like [[The chat room]].
* Choose a licence and publish the code.
* Send out the first invitations.

[[Category:Projects]]

The chat room

ScotMesh — Sun, 13 Sep 2026 00:40:59 GMT

Step-by-step joining from MeshChatX for the room, the group and the page

@@ Line 32: / Line 32: @@
 * '''Beside it''' are the names (one per identity, lookalikes refused), moderation (operators, bans and a log of what operators do) and the store, where messages are kept for 7 days.
 * '''The propagation node''' holds group messages for LXMF members who are offline until they collect them.
 == Out of the box ==
@@ Line 38: / Line 54: @@
 ; MeshChatX
-: Open the chat section, pick the ScotMesh hub (or add it by the hub address above) and join <code>scotmesh</code>. You can also message the LXMF group. MeshChatX uses one identity for both, so your name is the same in each.
+: All three ways in work from MeshChatX, and it uses one identity for all of them, so your name is the same in each. See [[#Step by step in MeshChatX|step by step in MeshChatX]] below.
 ; Sideband, and Columba or Retichat on iPhone
 : Start a conversation with <code>625ad393ca4df62a1382f9d936322a0a</code> and send <code>/join</code>. The chat then arrives like any other conversation, as <code>Name: message</code>, and what you send reaches everyone.
 ; NomadNet
 : Open the chat page above to read along. To post, turn on "Identify when connecting" for that node and reload. NomadNet can also join the RRC room from its Channels screen.
 == Full installation ==

File:ScotMesh chat page in MeshChatX.png

ScotMesh — Sun, 13 Sep 2026 00:17:05 GMT

ScotMesh uploaded File:ScotMesh chat page in MeshChatX.png == Summary == Screenshots of the chat in MeshChatX

New page

== Summary ==
Screenshots of the chat in MeshChatX

File:ScotMesh chat LXMF group in MeshChatX.png

ScotMesh — Sun, 13 Sep 2026 00:17:05 GMT

ScotMesh uploaded File:ScotMesh chat LXMF group in MeshChatX.png == Summary == Screenshots of the chat in MeshChatX

New page

== Summary ==
Screenshots of the chat in MeshChatX

File:ScotMesh chat RRC room in MeshChatX.png

ScotMesh — Sun, 13 Sep 2026 00:17:05 GMT

ScotMesh uploaded File:ScotMesh chat RRC room in MeshChatX.png == Summary == Screenshots of the chat in MeshChatX

New page

== Summary ==
Screenshots of the chat in MeshChatX

The chat room

ScotMesh — Sun, 13 Sep 2026 00:08:50 GMT

Add the architecture diagram: how the chat hub fits together

← Older revision		Revision as of 01:08, 13 September 2026
Line 20:		Line 20:

	Every command is listed on [[Chat commands]].		Every command is listed on [[Chat commands]].

			== How it fits together ==

			[[File:ScotMesh chat hub architecture.svg\|center\|frameless\|upright=3.2\|alt=Diagram: RRC clients, LXMF messengers and NomadNet browsers each reach their own front door in the ScotMesh chat hub. Each door checks the Reticulum identity and its name, then passes messages to the hub core, which works with names, moderation and the store. The hub connects to the Reticulum backbone, and the propagation node holds group messages for members who are away.\|How the ScotMesh chat hub fits together]]

			The hub is one program on ScotMesh's own server, connected to the backbone at rns.scotmesh.net.

			* '''Three front doors.''' The RRC server, the LXMF group and the chat page each speak their own protocol, so every app works with the door it already knows.
			* '''Identity first.''' Before a message goes any further, its door checks the Reticulum identity it came from and looks up the name that identity holds. That is why a name is the same everywhere and can't be borrowed, and why messages appear under the author's own name.
			* '''One hub core''' puts messages in order, stores them once and sends them out through every door. It also handles catching up, who is here, LXMF settings and commands.
			* '''Beside it''' are the names (one per identity, lookalikes refused), moderation (operators, bans and a log of what operators do) and the store, where messages are kept for 7 days.
			* '''The propagation node''' holds group messages for LXMF members who are offline until they collect them.

	== Out of the box ==		== Out of the box ==

File:ScotMesh chat hub architecture.svg

ScotMesh — Sun, 13 Sep 2026 00:08:04 GMT

ScotMesh uploaded File:ScotMesh chat hub architecture.svg == Summary == How the ScotMesh chat hub fits together: three ways in, the hub core, names, moderation and the store

New page

== Summary ==
How the ScotMesh chat hub fits together: three ways in, the hub core, names, moderation and the store

The chat room

ScotMesh — Sun, 13 Sep 2026 00:04:22 GMT

Link to Chat commands

← Older revision		Revision as of 01:04, 13 September 2026
Line 19:		Line 19:
	\|}		\|}

	~~All the commands are~~ on [[Chat commands]].		Every command is listed on [[Chat commands]].

	== Out of the box ==		== Out of the box ==

Chat commands

ScotMesh — Sun, 13 Sep 2026 00:03:27 GMT

Every chat command, for RRC, LXMF, operators and NomadNet

New page

The commands for the [[The chat room|ScotMesh chat]]. Send them in the RRC room or as a message to the LXMF group (<code>625ad393ca4df62a1382f9d936322a0a</code>). The reply goes only to you: over RRC it arrives as a notice, and over LXMF as a message from the group.

<code>/help</code> lists the commands where you are, and <code>/help nick</code> explains one.

== Everyone ==

{| class="wikitable"
! Command !! What it does
|-
| <code>/help [command]</code> || Lists the commands, or explains one.
|-
| <code>/whoami</code> || Shows your name, identity and settings, and where you are connected.
|-
| <code>/nick Name</code> || Takes a name. Your old one is freed.
|-
| <code>/leave</code> || Frees your name and leaves the LXMF group.
|-
| <code>/who</code> || Shows who is here, on RRC and in the LXMF group.
|-
| <code>/history 20</code> || Shows earlier messages, up to 100, at most one request every 15 seconds.
|-
| <code>/topic</code> || Shows the room topic.
|}

== LXMF group ==

{| class="wikitable"
! Command !! What it does
|-
| <code>/join [Name]</code> || Joins the group, optionally with a name. With no name it uses the display name your app announces. You get the last 10 messages to start with.
|-
| <code>/lxmf on</code> || Gets every message. This is the default.
|-
| <code>/lxmf off</code> || Stops group messages. You keep your name and your place in the group.
|-
| <code>/lxmf auto</code> || Pauses group messages while you are in the room over RRC, and starts them again when you leave.
|-
| <code>/lxmf mine on</code> or <code>off</code> || Chooses whether you also get your own messages sent from RRC or the page.
|-
| <code>/pause</code>, <code>/resume</code> || The same as <code>/lxmf off</code> and <code>/lxmf on</code>.
|-
| <code>/me waves</code> || Sends an action: <code>* Name waves</code>.
|}

The <code>/lxmf</code> settings also work from the RRC room. On the chat page they are under '''Your name & settings'''.

== RRC rooms ==

Your RRC client sends joining and leaving itself. These are the hub's own room commands; <code><room></code> is the room name, such as <code>scotmesh</code>.

{| class="wikitable"
! Command !! What it does
|-
| <code>/join newroom</code> || Joins a room, or creates it if nobody is in it. You become its founder.
|-
| <code>/list</code> || Lists registered rooms and their topics.
|-
| <code>/who [room]</code> || Shows who is in a room.
|-
| <code>/topic <room> [text]</code> || Shows the topic, or sets it (only operators can if the room is <code>+t</code>).
|-
| <code>/register <room></code> || The founder keeps the room even when it is empty. It also sets <code>+n</code> and <code>+t</code>.
|-
| <code>/unregister <room></code> || The founder undoes <code>/register</code>.
|}

== Room operators ==

The founder of a room and anyone they make an operator.

{| class="wikitable"
! Command !! What it does
|-
| <code>/op <room> Name</code>, <code>/deop</code> || Makes someone an operator, or removes it.
|-
| <code>/voice <room> Name</code>, <code>/devoice</code> || Lets someone speak in a moderated (<code>+m</code>) room, or removes it.
|-
| <code>/kick <room> Name</code> || Removes someone from the room. They can come back.
|-
| <code>/ban <room> add Name</code> || Bans someone from the room. <code>del</code> lifts it and <code>list</code> shows the bans.
|-
| <code>/invite <room> add Name</code> || Invites someone to an invite-only or keyed room for 15 minutes.
|-
| <code>/mode <room> +m</code> || Sets a room mode. See below.
|}

Over LXMF the room is always <code>scotmesh</code>, so leave it out: <code>/kick Name</code>, <code>/ban add Name</code>.

{| class="wikitable"
! Mode !! Meaning
|-
| <code>+i</code> || Invite only.
|-
| <code>+k key</code> || A key is needed to join; <code>-k</code> removes it.
|-
| <code>+m</code> || Moderated: only operators and voiced people can speak.
|-
| <code>+n</code> || No messages from people not in the room.
|-
| <code>+p</code> || Private: left out of <code>/list</code>, and <code>/who</code> is refused.
|-
| <code>+t</code> || Only operators can change the topic.
|}

== Hub operators ==

{| class="wikitable"
! Command !! What it does
|-
| <code>/kline add Name [reason]</code> || Bans an identity from the whole hub and disconnects it everywhere. <code>del</code> lifts it and <code>list</code> shows the bans.
|-
| <code>/release Name</code> || Frees a name someone holds. They are told.
|-
| <code>/stats</code> || Shows the hub's counters.
|}

== Naming someone ==

Where a command takes a name, you can give:
* their name (lookalikes match, so <code>rab</code> finds <code>Rab</code>);
* their guest name, such as <code>guest-2af3</code>;
* six or more characters of their identity hash;
* the whole 32-character hash.

If several people match, the hub lists them and asks for a longer hash.

== NomadNet ==

NomadNet's RRC screen handles slash commands itself. <code>/help</code> there shows NomadNet's own list, and <code>/nick</code> sets the name NomadNet sends. It passes only these to the hub:

<code>/who /names /topic /mode /kick /ban /invite /op /deop /voice /devoice /register /unregister /kline /stats</code>

For anything else (<code>/whoami</code>, <code>/lxmf</code>, <code>/history</code>, <code>/leave</code> to free your name), message the LXMF group, or use '''Your name & settings''' on the chat page. In NomadNet, <code>/leave</code> on the RRC screen leaves the room; it doesn't free your name.

MeshChatX passes every command to the hub.

[[Category:The ScotMesh Backbone]]

The chat room

ScotMesh — Sun, 13 Sep 2026 00:03:26 GMT

Full guide to the chat: names, catching up, LXMF delivery, page, what is kept, troubleshooting, with diagrams

Show changes

← Older revision		Revision as of 13:07, 13 September 2026
Line 36:		Line 36:
	}		}

	/* Site header on every page: the ~~ScotMesh Reticulum mark~~ and the wiki's name~~, as on scotmesh.net~~ */		/* Site header on every page: the scotmesh/reticulum lockup and the wiki's name */
	#siteNotice { background: none !important; border: 0 !important; padding: 0 !important; margin: 0 0 0.6em !important; text-align: left !important; font-size: 1rem !important; }		#siteNotice { background: none !important; border: 0 !important; padding: 0 !important; margin: 0 0 0.6em !important; text-align: left !important; font-size: 1rem !important; }
	.sm-header { display: flex; align-items: center; gap: 1rem; padding: 0.9rem 32px 0.9rem; }		.sm-header { display: flex; align-items: center; gap: 1rem; padding: 0.9rem 32px 0.9rem; }
	.sm-header a { text-decoration: none !important; }		.sm-header a { text-decoration: none !important; }
	.sm-flag { display: block; width: ~~52px~~; height: ~~52px; border-radius: 4px~~; flex: none; background: url("/images/scotmesh-brand/~~mark~~.svg") center / ~~100% 100%~~ no-repeat; }		.sm-flag { display: block; width: 208px; height: 58px; flex: none; background: url("/images/scotmesh-brand/lockup-stacked-on-dark.svg") left center / contain no-repeat; }
			:root.skin-theme-clientpref-day .sm-flag { background-image: url("/images/scotmesh-brand/lockup-stacked-on-light.svg"); }
			@media (prefers-color-scheme: light) { :root.skin-theme-clientpref-os .sm-flag { background-image: url("/images/scotmesh-brand/lockup-stacked-on-light.svg"); } }
			.sm-header-text { border-left: 1px solid var(--border-color-base, #22324D); padding-left: 1rem; }
	.sm-header-title { font-size: 1.75em; font-weight: 600; font-family: "IBM Plex Mono", monospace; letter-spacing: -0.02em; line-height: 1.15; }		.sm-header-title { font-size: 1.75em; font-weight: 600; font-family: "IBM Plex Mono", monospace; letter-spacing: -0.02em; line-height: 1.15; }
	.sm-header-title a { color: var(--color-emphasized, inherit) !important; }		.sm-header-title a { color: var(--color-emphasized, inherit) !important; }
	.sm-header-sub { color: var(--color-subtle, #9ca3af); font-size: 0.98em; margin-top: 0.15em; }		.sm-header-sub { color: var(--color-subtle, #9ca3af); font-size: 0.98em; margin-top: 0.15em; }
	@media (max-width: 640px) { .sm-header { padding: 0.8rem 16px; gap: 0.75rem; } .sm-flag { width: ~~40px~~; height: ~~40px~~; } .sm-header-title { font-size: 1.35em; } .sm-header-sub { font-size: 0.88em; } }		@media (max-width: 640px) { .sm-header { padding: 0.8rem 16px; gap: 0.75rem; } .sm-flag { width: 150px; height: 42px; } .sm-header-text { padding-left: 0.75rem; } .sm-header-title { font-size: 1.35em; } .sm-header-sub { font-size: 0.88em; } }
	/* Pointer to the MeshCore / Meshtastic wiki (Main Page, above the hero) */		/* Pointer to the MeshCore / Meshtastic wiki (Main Page, above the hero) */
	.sm-otherwiki { margin: 0.2em 0 1em; padding: 0.6em 1em; border: 1px solid #22324D; border-radius: 6px; background: #0A1424; color: #fff; font-size: 0.95em; display: flex; align-items: center; gap: 0.5em 0.85em; flex-wrap: wrap; line-height: 1.45; overflow-wrap: anywhere; }		.sm-otherwiki { margin: 0.2em 0 1em; padding: 0.6em 1em; border: 1px solid #22324D; border-radius: 6px; background: #0A1424; color: #fff; font-size: 0.95em; display: flex; align-items: center; gap: 0.5em 0.85em; flex-wrap: wrap; line-height: 1.45; overflow-wrap: anywhere; }