Mesh repeater on a local guy's house... 26ft up. This is the same 3d printed case as we put on a concrete silo two weeks ago.

Old Engineering tricks lost/forgotten on how to keep your house cool or warm

I grew all of these

Got another mesh node put together yesterday. Waiting for small magnetic feet in the mail. We're gunna see if we can "drone kerplunk" it on top of a 150ft tall truck stop sign near I-20.

We figure on top of the sign, not a soul will see it and the sloped sides should keep the wind from blowing it off.

And I put another repeater together inside a conduit Tee using a solar patio light today.

As of yesterday, we have 100% reliable off grid texting from Sumter to Florence SC. We've got a growing group of about a dozen of us in a chatroom. One of the guys is a helo pilot for the air national guard and he's seeking sites that will get us further west into Columbia SC area. Another guy is near Camden along I-20 and he too is working on some sites.

The meshcore stuff is growing organically.

✨👁️✨

Larken Rose

https://t.me/resistanceawakening

Looks like another new one just sprung up just east of Florence.

We ended up cable bracing the pole shed we built a few months ago.

Watch meshcore network in the southeast USA live.

https://cs.yoss.dev/#/live

Sugar wash distilling under way.

small ram pump.

Mesh core growth in Florence SC in the past 6 months.

I've been RTFM for meshcore protocol. No wonder it is scaleable! A quick recap. when you send a message to a specific person on MC, it initally ping pongs out thru every repeater that hears it (Flood routing). Once a path is discovered all messages travel a directed path and do not flood the whole network. This frees up repeaters in nearby areas to handle additionally messages for other people. All group chatroom traffic is flood routed all the time.

But wait there's more... when a repeater receives a packet it waits a random amount of time before repeating it so that another repeater that heard the same packet won't transmit at the same time. So as it turns out, the repeater software is smart enough to know if a packet is a flood type or a directed message type. We can program flood packets to move more slowly thru the network and move direct message type packets along in the queue faster. Even if it means jumping ahead in line around the flood types.

Imagine trains running on one track and the bulk freight trains get put on a siding to allow the passenger trains to pass. The freight train eventually gets there, but it's a lower priority.

I'm going to increase the txdelay factor from 0.5 to 1.3 on my repeaters and leave the direct.txdelay factor at 0.2.