<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: First steps in long-range mesh networks: Meshtastic on LilyGo T-Deck Plus</title>
	<atom:link href="http://jfxpt.com/2025/first-steps-in-long-range-mesh-networks-meshtastic-on-lilygo-t-deck-plus/feed/" rel="self" type="application/rss+xml" />
	<link>http://jfxpt.com/2025/first-steps-in-long-range-mesh-networks-meshtastic-on-lilygo-t-deck-plus/</link>
	<description>The search for invariants</description>
	<pubDate>Sat, 18 Apr 2026 16:25:37 +0000</pubDate>
	<generator>http://polimedia.us</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jacob Welsh</title>
		<link>http://jfxpt.com/2025/first-steps-in-long-range-mesh-networks-meshtastic-on-lilygo-t-deck-plus/#comment-3490</link>
		<dc:creator>Jacob Welsh</dc:creator>
		<pubDate>Wed, 25 Mar 2026 03:56:30 +0000</pubDate>
		<guid isPermaLink="false">http://jfxpt.com/?p=299#comment-3490</guid>
		<description>For an update on this, we got some Heltec nodes built too and so can now confirm that the system does work at least to some degree; their range so far is not great but better than the Lilygo's which is almost nonexistent. We've picked up signals from around 8 other nodes around town, on LongFast frequency slot 20, of which one so far has responded to a basic hello, but connectivity is quite intermittent.</description>
		<content:encoded><![CDATA[<p>For an update on this, we got some Heltec nodes built too and so can now confirm that the system does work at least to some degree; their range so far is not great but better than the Lilygo's which is almost nonexistent. We've picked up signals from around 8 other nodes around town, on LongFast frequency slot 20, of which one so far has responded to a basic hello, but connectivity is quite intermittent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Welsh</title>
		<link>http://jfxpt.com/2025/first-steps-in-long-range-mesh-networks-meshtastic-on-lilygo-t-deck-plus/#comment-3431</link>
		<dc:creator>Jacob Welsh</dc:creator>
		<pubDate>Tue, 16 Dec 2025 01:42:27 +0000</pubDate>
		<guid isPermaLink="false">http://jfxpt.com/?p=299#comment-3431</guid>
		<description>@Diana Coman: the instructions literally said to cd into a directory which didn't exist. The device-install.sh as well as the firmware &#038; littlefs images for a variety of boards are all inside the zip file, so if it's indeed supposed to do something in-place it's entirely unclear what's the program that would be doing it. But yes, I expect littlefs is a filesystem for the embedded device itself.</description>
		<content:encoded><![CDATA[<p>@Diana Coman: the instructions literally said to cd into a directory which didn't exist. The device-install.sh as well as the firmware &#038; littlefs images for a variety of boards are all inside the zip file, so if it's indeed supposed to do something in-place it's entirely unclear what's the program that would be doing it. But yes, I expect littlefs is a filesystem for the embedded device itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diana Coman</title>
		<link>http://jfxpt.com/2025/first-steps-in-long-range-mesh-networks-meshtastic-on-lilygo-t-deck-plus/#comment-3430</link>
		<dc:creator>Diana Coman</dc:creator>
		<pubDate>Mon, 15 Dec 2025 08:28:58 +0000</pubDate>
		<guid isPermaLink="false">http://jfxpt.com/?p=299#comment-3430</guid>
		<description>Sounds like quite the dig, glad to hear it did work out in the end. 

Fwiw, that exploding zip + littlefs seems likely to be some embedded file system. Those were at some point all the rage and I think they've been coming back via all the various environments that aim for some sort of prepackaged "whole" (I wouldn't be surprised if docker and similars use something of the sort too). So possibly the unzip step wasn't necessarily missing, if the thing simply works with the .zip file as a "packaged whole including its own little filesystem" directly.</description>
		<content:encoded><![CDATA[<p>Sounds like quite the dig, glad to hear it did work out in the end. </p>
<p>Fwiw, that exploding zip + littlefs seems likely to be some embedded file system. Those were at some point all the rage and I think they've been coming back via all the various environments that aim for some sort of prepackaged "whole" (I wouldn't be surprised if docker and similars use something of the sort too). So possibly the unzip step wasn't necessarily missing, if the thing simply works with the .zip file as a "packaged whole including its own little filesystem" directly.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
