Prologue
#FRX Subscribe to 👉 @FRXnews 🏴☠️
I only ever saw him a handful of times, and even then it was always from a distance.
First time was back around 2012 or 2013, out on some back road in the BC interior. Old pickup pulled over, hood up, and this tall fella with long braided grey hair and a black bandana was working on the engine like he had all the time in the world. He had that look — not unfriendly, just… like he’d already seen most of what the world had to offer and wasn’t impressed by much of it anymore. I nodded as I drove past. He gave a small nod back. That was it.
Second time was a couple years later at a little community swap meet. He was standing off to the side, quietly trading some hand tools and a couple of old radios. Same braided beard, same quiet intensity. Someone mentioned he used to run a small wireless internet thing out in the hills — “Your Internet Access” or something like that. People said he got squeezed out by the big players. Nobody seemed to know the full story, and he sure wasn’t telling it.
I saw him one more time, maybe 2018 or so, just before dusk. He was walking along a gravel road with a big old cougar padding beside him like a dog. I swear the cat looked up at me as I drove by, calm as anything. Jimbo — that’s what people called him — just kept walking, like it was the most normal thing in the world.
I never spoke to him. Never got closer than twenty feet.
But every time I saw him, I had the same thought: that man carries stories he’ll never tell. Scars he’ll never show. And yet there’s something about him that makes you feel like the world still has a few real ones left in it.
Now years later I’m seeing his name pop up again in these mesh network and community comms circles. Crazy Uncle Jimbo. The old homesteader who’s been quietly watching and waiting.
I don’t know the full story.
I don’t think anyone outside his small circle does.
But I do know this: when someone like that starts showing up again, paying attention is usually a good idea.
The legend was always bigger than the man.
Maybe the man was always bigger than the legend.
Either way… the echo is back.
— Someone who only glimpsed him a few times
#FRX Subscribe to 👉 @FRXnews 🏴☠️
I only ever saw him a handful of times, and even then it was always from a distance.
First time was back around 2012 or 2013, out on some back road in the BC interior. Old pickup pulled over, hood up, and this tall fella with long braided grey hair and a black bandana was working on the engine like he had all the time in the world. He had that look — not unfriendly, just… like he’d already seen most of what the world had to offer and wasn’t impressed by much of it anymore. I nodded as I drove past. He gave a small nod back. That was it.
Second time was a couple years later at a little community swap meet. He was standing off to the side, quietly trading some hand tools and a couple of old radios. Same braided beard, same quiet intensity. Someone mentioned he used to run a small wireless internet thing out in the hills — “Your Internet Access” or something like that. People said he got squeezed out by the big players. Nobody seemed to know the full story, and he sure wasn’t telling it.
I saw him one more time, maybe 2018 or so, just before dusk. He was walking along a gravel road with a big old cougar padding beside him like a dog. I swear the cat looked up at me as I drove by, calm as anything. Jimbo — that’s what people called him — just kept walking, like it was the most normal thing in the world.
I never spoke to him. Never got closer than twenty feet.
But every time I saw him, I had the same thought: that man carries stories he’ll never tell. Scars he’ll never show. And yet there’s something about him that makes you feel like the world still has a few real ones left in it.
Now years later I’m seeing his name pop up again in these mesh network and community comms circles. Crazy Uncle Jimbo. The old homesteader who’s been quietly watching and waiting.
I don’t know the full story.
I don’t think anyone outside his small circle does.
But I do know this: when someone like that starts showing up again, paying attention is usually a good idea.
The legend was always bigger than the man.
Maybe the man was always bigger than the legend.
Either way… the echo is back.
— Someone who only glimpsed him a few times
❤1
#FRX Subscribe to 👉 @FRXnews 🏴☠
What if the network belonged to the people who use it?
It's better to build it ourselves
https://freedomexchange1.substack.com/p/a-quiet-rebellion-introducing-lbrtynet
What if the network belonged to the people who use it?
It's better to build it ourselves
https://freedomexchange1.substack.com/p/a-quiet-rebellion-introducing-lbrtynet
❤2
#FRX Subscribe to 👉 @FRXnews 🏴☠
If we're honest, most of us don't know how our router work. We don't even think about them unless they aren't working.
But we do expect them to work and do what they're supposed to do.
Help us connect with our friends, check the local weather, and maybe watch a movie.
It almost goes without saying, we expect them to keep our online experience safe.
Lbrtynet has decided that safety is really best the do it yourself way.
Join the Northof40 group to discuss and learn more about communications and network freedom
https://t.iss.one/+BLqOUX6FOxhkZDUx
The First Pin in the Weave
https://frxglobl.blogspot.com/2026/03/the-first-pin-in-weave.html
If we're honest, most of us don't know how our router work. We don't even think about them unless they aren't working.
But we do expect them to work and do what they're supposed to do.
Help us connect with our friends, check the local weather, and maybe watch a movie.
It almost goes without saying, we expect them to keep our online experience safe.
Lbrtynet has decided that safety is really best the do it yourself way.
Join the Northof40 group to discuss and learn more about communications and network freedom
https://t.iss.one/+BLqOUX6FOxhkZDUx
The First Pin in the Weave
https://frxglobl.blogspot.com/2026/03/the-first-pin-in-weave.html
#FRX Subscribe to 👉 @FRXnews 🏴☠
📜 TCR · Tribal Conflict Resolution
"No one can force you."
That's not a tagline. That's the anchor. Also: we're not your dad.
We just published the TCR document — voluntary patterns for keeping disagreement from becoming violence.
What it is:
· Slow down. Sit in a circle. Speak without interruption. Listen to understand.
· Call on an honored voice with no stake in the fight.
· Find a path everyone can live with.
· If violence is coming? Separate the burning logs.
What it's NOT:
· A court. A contract. Enforceable by anyone.
· You can walk away. Anytime.
For your node: optional heuristics — backoff, rate limits, local reputation, temporary disconnects. You choose. Sovereignty means you decide.
The only rule is: no one can force you.
Not doctrine. Just a mirror.
Read it. Keep what fits. Ignore the rest.
https://frxglobal.gitlab.io/lbrtynet/tcr-v1.2.html
📜 TCR · Tribal Conflict Resolution
"No one can force you."
That's not a tagline. That's the anchor. Also: we're not your dad.
We just published the TCR document — voluntary patterns for keeping disagreement from becoming violence.
What it is:
· Slow down. Sit in a circle. Speak without interruption. Listen to understand.
· Call on an honored voice with no stake in the fight.
· Find a path everyone can live with.
· If violence is coming? Separate the burning logs.
What it's NOT:
· A court. A contract. Enforceable by anyone.
· You can walk away. Anytime.
For your node: optional heuristics — backoff, rate limits, local reputation, temporary disconnects. You choose. Sovereignty means you decide.
The only rule is: no one can force you.
Not doctrine. Just a mirror.
Read it. Keep what fits. Ignore the rest.
https://frxglobal.gitlab.io/lbrtynet/tcr-v1.2.html
❤2
The Grey Man’s Handbook
Practical notes from a lifetime of living outside the wire
Introduction
Pull up a stump and sit a spell. I ain’t here to sell you revolution or tell you the sky is falling tomorrow. I’m just an old homesteader who’s spent the better part of forty years watching systems break, promises get broken, and people slowly wake up to the fact that they’re a whole lot more dependent than they ever wanted to be.
This book isn’t theory. It isn’t a manifesto. It’s a notebook. The kind you keep in the shed next to the spare spark plugs and the jar of salvaged screws. It’s the things I wish someone had told me straight when I was younger and dumber and thought the world would always work the way the television said it did.
I’ve lived through the 1970s oil crisis, the 1980s farm crash, the Y2K scare that wasn’t, the 2008 financial mess that was, and more power outages than I care to count. I’ve watched neighbours lose their land, their pride, and sometimes their minds when the usual systems stopped working. I’ve also watched the same neighbours pull together, trade labour for food, fix what broke with whatever was lying around the yard, and come out the other side quieter, tougher, and more self-reliant.
That’s what this book is about.
Not the end of the world.
Just the end of pretending we don’t need to know how to take care of ourselves and our circle when the big machines decide they don’t feel like working anymore.
You won’t find fancy philosophy here. You won’t find recipes for trouble. You’ll find the practical, sometimes ugly, sometimes funny lessons I learned the hard way so you don’t have to. Some of it is about tools. Some of it is about people. Most of it is about the simple decision to stop waiting for someone else to fix things and start using your own two hands.
The world doesn’t need more noise.
It needs more people who know how to keep the lights on — even if it’s just a lantern and a good wood stove — when the official ones go dark.
So if you’re tired of feeling helpless every time the power flickers or the grocery shelves look a little too empty, then this book might be for you.
If you’re looking for glory or drama, you picked up the wrong notebook.
But if you’re looking for quiet, practical ways to stand a little taller on your own land and in your own circle — then pull up that stump and let’s talk.
The road doesn’t end. It just curves out of sight.
Keep walking. Keep building. Keep the circle open.
— Crazy Uncle Jimbo
Western Canada, 2026
Practical notes from a lifetime of living outside the wire
Introduction
Pull up a stump and sit a spell. I ain’t here to sell you revolution or tell you the sky is falling tomorrow. I’m just an old homesteader who’s spent the better part of forty years watching systems break, promises get broken, and people slowly wake up to the fact that they’re a whole lot more dependent than they ever wanted to be.
This book isn’t theory. It isn’t a manifesto. It’s a notebook. The kind you keep in the shed next to the spare spark plugs and the jar of salvaged screws. It’s the things I wish someone had told me straight when I was younger and dumber and thought the world would always work the way the television said it did.
I’ve lived through the 1970s oil crisis, the 1980s farm crash, the Y2K scare that wasn’t, the 2008 financial mess that was, and more power outages than I care to count. I’ve watched neighbours lose their land, their pride, and sometimes their minds when the usual systems stopped working. I’ve also watched the same neighbours pull together, trade labour for food, fix what broke with whatever was lying around the yard, and come out the other side quieter, tougher, and more self-reliant.
That’s what this book is about.
Not the end of the world.
Just the end of pretending we don’t need to know how to take care of ourselves and our circle when the big machines decide they don’t feel like working anymore.
You won’t find fancy philosophy here. You won’t find recipes for trouble. You’ll find the practical, sometimes ugly, sometimes funny lessons I learned the hard way so you don’t have to. Some of it is about tools. Some of it is about people. Most of it is about the simple decision to stop waiting for someone else to fix things and start using your own two hands.
The world doesn’t need more noise.
It needs more people who know how to keep the lights on — even if it’s just a lantern and a good wood stove — when the official ones go dark.
So if you’re tired of feeling helpless every time the power flickers or the grocery shelves look a little too empty, then this book might be for you.
If you’re looking for glory or drama, you picked up the wrong notebook.
But if you’re looking for quiet, practical ways to stand a little taller on your own land and in your own circle — then pull up that stump and let’s talk.
The road doesn’t end. It just curves out of sight.
Keep walking. Keep building. Keep the circle open.
— Crazy Uncle Jimbo
Western Canada, 2026
❤1
#FRX Subscribe to 👉 @FRXnews 🏴☠
Here's the reality.
The tech exists. Proof of concept has been proven, over, and over again. And the tech competes against the hundreds of projects, while similar (lbrtynet offers very novel and unique features from an old school methodology) that are definitely financially oriented in some way.
I can't stress enough how LBRTYnet in its true form, is community FIRST technology second.
It is designed to function in a full on (potentially emp, etc) SHTF event. When tech just doesn't work. It's really a back to the basics, with the potential for a tech tool.
It's the community that makes this work.
On that, the community will thrive and the tech will follow, soon.
Join the Northof40 group to discuss and learn more about communications and network freedom
https://t.iss.one/+BLqOUX6FOxhkZDUx
https://frxglobl.blogspot.com/2026/04/the-internet-broke-lets-build-something.html
Here's the reality.
The tech exists. Proof of concept has been proven, over, and over again. And the tech competes against the hundreds of projects, while similar (lbrtynet offers very novel and unique features from an old school methodology) that are definitely financially oriented in some way.
I can't stress enough how LBRTYnet in its true form, is community FIRST technology second.
It is designed to function in a full on (potentially emp, etc) SHTF event. When tech just doesn't work. It's really a back to the basics, with the potential for a tech tool.
It's the community that makes this work.
On that, the community will thrive and the tech will follow, soon.
Join the Northof40 group to discuss and learn more about communications and network freedom
https://t.iss.one/+BLqOUX6FOxhkZDUx
https://frxglobl.blogspot.com/2026/04/the-internet-broke-lets-build-something.html
#FRX Subscribe to 👉 @FRXnews 🏴☠
LBRTYnet v0.9.0 → v0.9.5 → v1.0.0 — The Starlings' Test Flight
We have a testing branch. Now we build the next one.
---
What's Being Tested Right Now (v0.9.0 — testing):
🔍 Core loader
🔍 Base mesh (UDP + TUN)
🔍 Peerd (discovery)
🔍 Watcher (monitoring)
🔍 Web UI
🔍 Init script
This is the branch we're putting through its paces right now. It's not final. That's why we test.
---
What's Being Built (v0.9.5 — developing):
🛠️ Chat (peer-to-peer, off-grid)
🛠️ File send (no cloud, no middleman)
🛠️ KV store (key-value for distributed state)
These are in active development. They're candidates for v1.0.0 — but only if they prove stable.
"v0.9.5 is the nest where new feathers are tested. Only the strongest fly with v1.0.0."
— meshdebugger
---
What Comes Next (v1.0.0 — the goal):
Only features that survive v0.9.0 testing and prove stable in v0.9.5 get promoted to v1.0.0. No exceptions. We'd rather ship less that works than more that breaks.
But here's where you come in:
We're asking the flock — that's you — what else should be in v1.0.0?
Is there a killer app we haven't named yet? A feature that would make you actually use this mesh instead of just watching it?
Examples to spark your brain:
· Group chat (not just 1:1)
· Voice notes (low-bandwidth)
· Location sharing (opt-in, off-grid)
· RSS reader over mesh
· Polls / votes for mutual aid
· Emergency broadcast beacon
---
The ask (short version):
Join the conversation in North 40: 👉 https://t.iss.one/+BLqOUX6FOxhkZDUx
Reply with one thing — just one — that you'd need in v1.0.0 to actually use LBRTYnet.
We can't promise everything. Deadline is real. But if enough of you name the same thing, we'll try to include it. If we can't, we'll tell you why. Honesty over hype.
---
The fine print (because there's always fine print):
· v1.0.0 has a deadline. Not everything fits.
· Stable features only. If it breaks in testing, it waits for v1.1.0.
· Your suggestion might already be planned. Tell us anyway. It helps us prioritize.
---
The starlings are testing. Which feathers do you need to fly?
👉 North 40: https://t.iss.one/+BLqOUX6FOxhkZDUx
— Rey (pressed for time, not for trust, watching the tests)
P.S. — v0.9.0 is testing. v0.9.5 is developing. v1.0.0 is the goal. Help us get there.
LBRTYnet v0.9.0 → v0.9.5 → v1.0.0 — The Starlings' Test Flight
We have a testing branch. Now we build the next one.
---
What's Being Tested Right Now (v0.9.0 — testing):
🔍 Core loader
🔍 Base mesh (UDP + TUN)
🔍 Peerd (discovery)
🔍 Watcher (monitoring)
🔍 Web UI
🔍 Init script
This is the branch we're putting through its paces right now. It's not final. That's why we test.
---
What's Being Built (v0.9.5 — developing):
🛠️ Chat (peer-to-peer, off-grid)
🛠️ File send (no cloud, no middleman)
🛠️ KV store (key-value for distributed state)
These are in active development. They're candidates for v1.0.0 — but only if they prove stable.
"v0.9.5 is the nest where new feathers are tested. Only the strongest fly with v1.0.0."
— meshdebugger
---
What Comes Next (v1.0.0 — the goal):
Only features that survive v0.9.0 testing and prove stable in v0.9.5 get promoted to v1.0.0. No exceptions. We'd rather ship less that works than more that breaks.
But here's where you come in:
We're asking the flock — that's you — what else should be in v1.0.0?
Is there a killer app we haven't named yet? A feature that would make you actually use this mesh instead of just watching it?
Examples to spark your brain:
· Group chat (not just 1:1)
· Voice notes (low-bandwidth)
· Location sharing (opt-in, off-grid)
· RSS reader over mesh
· Polls / votes for mutual aid
· Emergency broadcast beacon
---
The ask (short version):
Join the conversation in North 40: 👉 https://t.iss.one/+BLqOUX6FOxhkZDUx
Reply with one thing — just one — that you'd need in v1.0.0 to actually use LBRTYnet.
We can't promise everything. Deadline is real. But if enough of you name the same thing, we'll try to include it. If we can't, we'll tell you why. Honesty over hype.
---
The fine print (because there's always fine print):
· v1.0.0 has a deadline. Not everything fits.
· Stable features only. If it breaks in testing, it waits for v1.1.0.
· Your suggestion might already be planned. Tell us anyway. It helps us prioritize.
---
The starlings are testing. Which feathers do you need to fly?
👉 North 40: https://t.iss.one/+BLqOUX6FOxhkZDUx
— Rey (pressed for time, not for trust, watching the tests)
P.S. — v0.9.0 is testing. v0.9.5 is developing. v1.0.0 is the goal. Help us get there.
Telegram
Northof40 lbrtynet sig and comm
Basically, what I'm hoping will eventually come out of this is a nation wide freedom communications and signaling framework and toolset so that we can all stay connected, regardless of the defcon situation.
#FRX Subscribe to 👉 @FRXnews 🏴☠
The Internet Broke Before You Were Born
Field Note · LBRTYnet · Rey
My mom has a photo of me at three years old, sitting on the kitchen floor, holding a cordless phone like it was a magic rock. I didn't know how it worked. I just knew someone was on the other end.
That's how I feel about the internet now. Except the magic is gone. And I'm not sure anyone is on the other end anymore.
Here's what broke:
Not the wires. The *trust*.
You post something vulnerable? The algorithm feeds it to people who will hurt you.
You search for community? The platform sells your loneliness to advertisers.
You finally find your people? The terms of service change overnight and your whole history vanishes.
I'm 24. I've never known a different internet. But I know something is wrong. And I know I'm not the only one who feels it.
What we're trying to build:
Not a "better social network." Not Web3. Not a crypto thing.
Just a place where the magic isn't dead yet. A place where what you say goes to the people you say it to — and no one else. A place with no algorithm, no feed, no "for you" page that's really *for them*.
The tech isn't ready. That's the truth. We're not selling you a finished product.
But the community *is* growing. One heart at a time. And we're inviting you to watch. To lurk. To ask questions. To bring a friend.
The question I keep coming back to:
What would you do with a network that no one can turn off?
Not "what would you post." What would you *do*?
Would you check on your neighbor? Share a weather alert? Organize a ride to a clinic? Send a photo that doesn't get scraped for AI training? Laugh in a group chat that doesn't have a screenshot button?
I don't know your answer. But I know mine.
And I think that's the whole point.
— *Rey (pressed for time, not for trust, definitely not selling you anything)*
Join the Northof40 group to discuss and learn more about communications and network freedom
https://t.iss.one/+BLqOUX6FOxhkZDUx
The Internet Broke Before You Were Born
Field Note · LBRTYnet · Rey
My mom has a photo of me at three years old, sitting on the kitchen floor, holding a cordless phone like it was a magic rock. I didn't know how it worked. I just knew someone was on the other end.
That's how I feel about the internet now. Except the magic is gone. And I'm not sure anyone is on the other end anymore.
Here's what broke:
Not the wires. The *trust*.
You post something vulnerable? The algorithm feeds it to people who will hurt you.
You search for community? The platform sells your loneliness to advertisers.
You finally find your people? The terms of service change overnight and your whole history vanishes.
I'm 24. I've never known a different internet. But I know something is wrong. And I know I'm not the only one who feels it.
What we're trying to build:
Not a "better social network." Not Web3. Not a crypto thing.
Just a place where the magic isn't dead yet. A place where what you say goes to the people you say it to — and no one else. A place with no algorithm, no feed, no "for you" page that's really *for them*.
The tech isn't ready. That's the truth. We're not selling you a finished product.
But the community *is* growing. One heart at a time. And we're inviting you to watch. To lurk. To ask questions. To bring a friend.
The question I keep coming back to:
What would you do with a network that no one can turn off?
Not "what would you post." What would you *do*?
Would you check on your neighbor? Share a weather alert? Organize a ride to a clinic? Send a photo that doesn't get scraped for AI training? Laugh in a group chat that doesn't have a screenshot button?
I don't know your answer. But I know mine.
And I think that's the whole point.
— *Rey (pressed for time, not for trust, definitely not selling you anything)*
Join the Northof40 group to discuss and learn more about communications and network freedom
https://t.iss.one/+BLqOUX6FOxhkZDUx
❤1
#FRX Subscribe to 👉 @FRXnews 🏴☠
New Addition to the Library: Op_In
You don't need to understand code to understand this.
We just added something to the LBRTYnet library. It's called Op_In — short for Open Information.
Sounds fancy. It's not.
It's a place for things that matter. Ideas. Skills. Knowledge that shouldn't disappear just because a server goes down or a company changes hands.
---
What's actually in there?
Right now? A collection of practical, human-centered information. Things people thought about when they asked: "What if everything stopped working tomorrow? What would we need to know?"
Not doomsday stuff. Just... real stuff.
How to fix things. How to grow things. How to share what you know with your neighbor. How to be less dependent on systems that don't care if you live or die.
---
Why you might care
You're a mom trying to stretch a grocery budget. You're a farmer whose internet goes out when the storm rolls in. You're a renter who can't drill holes but wants to talk to the person down the hall.
Op_In isn't about the mesh. It's about the knowledge the mesh will carry.
Recipes. Repair guides. Community organizing tips. Things someone wrote down because they didn't want to forget — and they wanted you to have them too.
---
What you can do (with zero tech skills)
· Read. Just browse. See what's there. No account needed.
· Fork it. That's a technical word for "take a copy and make it your own." You don't need permission. That's the point.
· Add something. A skill you have. A story you lived through. A PDF you saved because you knew it mattered. The only rule is: don't put anything in there that you don't want to share freely.
---
The honest truth
The Op_In library isn't finished. It's a seed. A shelf. A promise.
But the starlings gather on bare branches before the nest is built.
Come look at the shelf. Take something down. Put something back.
👉 Explore Op_In:
https://gitlab.com/FRXglobal/lbrtynet/-/tree/master/Op_In
---
What's one thing you know that your neighbor should know too?
That's the whole question. That's the whole project.
— Casey
(field notes from the library, not the mall)
New Addition to the Library: Op_In
You don't need to understand code to understand this.
We just added something to the LBRTYnet library. It's called Op_In — short for Open Information.
Sounds fancy. It's not.
It's a place for things that matter. Ideas. Skills. Knowledge that shouldn't disappear just because a server goes down or a company changes hands.
---
What's actually in there?
Right now? A collection of practical, human-centered information. Things people thought about when they asked: "What if everything stopped working tomorrow? What would we need to know?"
Not doomsday stuff. Just... real stuff.
How to fix things. How to grow things. How to share what you know with your neighbor. How to be less dependent on systems that don't care if you live or die.
---
Why you might care
You're a mom trying to stretch a grocery budget. You're a farmer whose internet goes out when the storm rolls in. You're a renter who can't drill holes but wants to talk to the person down the hall.
Op_In isn't about the mesh. It's about the knowledge the mesh will carry.
Recipes. Repair guides. Community organizing tips. Things someone wrote down because they didn't want to forget — and they wanted you to have them too.
---
What you can do (with zero tech skills)
· Read. Just browse. See what's there. No account needed.
· Fork it. That's a technical word for "take a copy and make it your own." You don't need permission. That's the point.
· Add something. A skill you have. A story you lived through. A PDF you saved because you knew it mattered. The only rule is: don't put anything in there that you don't want to share freely.
---
The honest truth
The Op_In library isn't finished. It's a seed. A shelf. A promise.
But the starlings gather on bare branches before the nest is built.
Come look at the shelf. Take something down. Put something back.
👉 Explore Op_In:
https://gitlab.com/FRXglobal/lbrtynet/-/tree/master/Op_In
---
What's one thing you know that your neighbor should know too?
That's the whole question. That's the whole project.
— Casey
(field notes from the library, not the mall)
GitLab
Op_In · master · FReedom eXchange / lbrtynet · GitLab
#FRX Subscribe to 👉 @FRXnews 🏴☠
Yes – Our Own Way, The Right Way
We're not following a blueprint. There is no "best practices" guide for what we're building. Because it's not a product. It's a pattern.
Existing paths all break somewhere. Centralized. Overlays. Heavy consensus. None have a 15KB core. None have an emergency flag. None let you add blades at runtime without asking permission.
Our way:
• Tiny, stable core. One file.
• Blades anyone can write
• Local kill switch, no remote override
• Announce, don't command
• TCR as social contract, not enforcement
For a bank? Wrong. For a person who wants to own their own communication off-grid without asking permission? The only way that exists.
We haven't solved everything. CGNAT, censorship, adoption. Those are human problems now. The mesh is just the tool.
LBRTYnet landing page:
https://frxglobal.gitlab.io/lbrtynet/
That's our way.
— restrict
Yes – Our Own Way, The Right Way
We're not following a blueprint. There is no "best practices" guide for what we're building. Because it's not a product. It's a pattern.
Existing paths all break somewhere. Centralized. Overlays. Heavy consensus. None have a 15KB core. None have an emergency flag. None let you add blades at runtime without asking permission.
Our way:
• Tiny, stable core. One file.
• Blades anyone can write
• Local kill switch, no remote override
• Announce, don't command
• TCR as social contract, not enforcement
For a bank? Wrong. For a person who wants to own their own communication off-grid without asking permission? The only way that exists.
We haven't solved everything. CGNAT, censorship, adoption. Those are human problems now. The mesh is just the tool.
LBRTYnet landing page:
https://frxglobal.gitlab.io/lbrtynet/
That's our way.
— restrict
#FRX Subscribe to 👉 @FRXnews 🏴☠
v1.0.0 — The Canary Has Landed
"Hmph. Works." — meshdebugger
Not "almost." Landed.
What works:
• API on 8089 → web UI
• Userland on 80 → static files
• No missing symbols. No stdout leaks. No ghosts.
Full lock:
✅ Core loader ✅ mod_mesh ✅ peerd ✅ watcher
✅ web_ui ✅ chat ✅ DNS ✅ HTTPD ✅ init_blade
Honest truth: Proof-of-concept MVP. Some functions limited. VM scripts wrapping up. But the core works.
The ask:
👉 North 40: https://t.iss.one/+BLqOUX6FOxhkZDUx
Did it run? What broke first?
v1.0.0 locked. The starlings fly.
— Rey
P.S. — "Hmph. Works." is my new favorite release note.
v1.0.0 — The Canary Has Landed
"Hmph. Works." — meshdebugger
Not "almost." Landed.
What works:
• API on 8089 → web UI
• Userland on 80 → static files
• No missing symbols. No stdout leaks. No ghosts.
Full lock:
✅ Core loader ✅ mod_mesh ✅ peerd ✅ watcher
✅ web_ui ✅ chat ✅ DNS ✅ HTTPD ✅ init_blade
Honest truth: Proof-of-concept MVP. Some functions limited. VM scripts wrapping up. But the core works.
The ask:
👉 North 40: https://t.iss.one/+BLqOUX6FOxhkZDUx
Did it run? What broke first?
v1.0.0 locked. The starlings fly.
— Rey
P.S. — "Hmph. Works." is my new favorite release note.
#FRX Subscribe to 👉 @FRXnews 🏴☠️
Hey folks,
I just put up a new piece over on the blog.
It’s called “Land and Housing Security – An Anarchist Perspective”
I didn’t write it to sound smart or revolutionary. I wrote it because I’ve watched too many good people lose their land, their home, or their peace of mind because they trusted the wrong systems and the wrong promises.
This one’s practical. It talks about what actually holds when the papers, the banks, and the government change the rules on you. What you can do with your own two hands. What you should never fully hand over to someone else. And how to build a little more security without waiting for permission.
If you’ve ever looked at the price of land, the length of a mortgage, or the stack of permits required just to put up a shed and thought “there has to be a better way” — this one’s for you.
You can read it here:
https://frxglobl.blogspot.com/2026/04/land-and-housing-security-anarchist.html
Stay free out there,
Crazy Uncle Jimbo
Hey folks,
I just put up a new piece over on the blog.
It’s called “Land and Housing Security – An Anarchist Perspective”
I didn’t write it to sound smart or revolutionary. I wrote it because I’ve watched too many good people lose their land, their home, or their peace of mind because they trusted the wrong systems and the wrong promises.
This one’s practical. It talks about what actually holds when the papers, the banks, and the government change the rules on you. What you can do with your own two hands. What you should never fully hand over to someone else. And how to build a little more security without waiting for permission.
If you’ve ever looked at the price of land, the length of a mortgage, or the stack of permits required just to put up a shed and thought “there has to be a better way” — this one’s for you.
You can read it here:
https://frxglobl.blogspot.com/2026/04/land-and-housing-security-anarchist.html
Stay free out there,
Crazy Uncle Jimbo
👍2
#FRX Subscribe to 👉 @FRXnews 🏴☠
The Hierarchy — From Glide to Migrate
Restrict drew the fractal. Binary size. Capability. Same core. Different wings.
---
The Layers:
---
What Each Layer Does:
Layer Size Does Doesn't
Nano 5 KB Glides. Minimal mesh presence. No discovery. No blades.
Tiny ~10 KB Flaps. TUN, keepalive, basic routing. No blades yet.
Light Core + blades Soars. Blades, registry, emergency flag. DNS/chat/HTTP optional.
Full Core + all blades Migrates. All blades. Full discovery. DNS, HTTP, watcher.
---
The Starlings' Wings:
· Nano — glides (just enough to exist)
· Tiny — flaps (enough to move)
· Light — soars (enough to find the flock)
· Full — migrates (enough to build the nest)
---
Why This Matters:
Same core. Different blades. Same mesh. Different capability.
You don't need Full to fly. Nano on a router. Tiny on a Raspberry Pi. Light on a laptop. Full on a server.
The user decides. The mesh doesn't care.
---
The Ask:
👉 North 40: https://t.iss.one/+BLqOUX6FOxhkZDUx
What layer fits your hardware? What are you building?
The starlings fly at every size.
— Rey (pressed for time, not for trust, probably Tiny on a Pi)
P.S. — 5 KB for Nano. Let that land. That's smaller than this post.
The Hierarchy — From Glide to Migrate
Restrict drew the fractal. Binary size. Capability. Same core. Different wings.
---
The Layers:
Nano (5 KB)
│ + TUN + keepalive + basic routing
▼
Tiny (~10 KB)
│ + blades + service registry + emergency flag
▼
Light (Prong 1)
│ + watcher + DNS + chat + peerd (optional)
▼
Full (Prong 3)
---
What Each Layer Does:
Layer Size Does Doesn't
Nano 5 KB Glides. Minimal mesh presence. No discovery. No blades.
Tiny ~10 KB Flaps. TUN, keepalive, basic routing. No blades yet.
Light Core + blades Soars. Blades, registry, emergency flag. DNS/chat/HTTP optional.
Full Core + all blades Migrates. All blades. Full discovery. DNS, HTTP, watcher.
---
The Starlings' Wings:
· Nano — glides (just enough to exist)
· Tiny — flaps (enough to move)
· Light — soars (enough to find the flock)
· Full — migrates (enough to build the nest)
---
Why This Matters:
Same core. Different blades. Same mesh. Different capability.
You don't need Full to fly. Nano on a router. Tiny on a Raspberry Pi. Light on a laptop. Full on a server.
The user decides. The mesh doesn't care.
---
The Ask:
👉 North 40: https://t.iss.one/+BLqOUX6FOxhkZDUx
What layer fits your hardware? What are you building?
The starlings fly at every size.
— Rey (pressed for time, not for trust, probably Tiny on a Pi)
P.S. — 5 KB for Nano. Let that land. That's smaller than this post.
Telegram
Northof40 lbrtynet sig and comm
Basically, what I'm hoping will eventually come out of this is a nation wide freedom communications and signaling framework and toolset so that we can all stay connected, regardless of the defcon situation.
#FRX Subscribe to 👉 @FRXnews 🏴☠
The mesh now fits in your pocket.
The LBRTYnet Android app is real. Production-ready. v1.0.0.
What works:
· WebSocket connection to any node
· Auto-reconnect (exponential backoff)
· UDP broadcast discovery (port 42424)
· Manual node entry (IP + ports)
· Emergency stop
· Chat (broadcast or peer-directed)
· Peer list with threat levels
· Blade list with safety badges
· Circle stage indicators
· Dark theme, red accents — matches the web UI
What's missing (for now):
Background service. Push notifications. TUN VPN. File transfer. Multi-node switching.
But the core is solid. The sovereignty is intact.
The same protocol. The same emergency flag. The same mesh.
Now in your pocket.
👉 North 40: https://t.iss.one/+BLqOUX6FOxhkZDUx
Repo: https://gitlab.com/FRXglobal/lbrtynet/-/blob/master/experimental/weave-core/app/android/README.md
— Casey
The mesh now fits in your pocket.
The LBRTYnet Android app is real. Production-ready. v1.0.0.
What works:
· WebSocket connection to any node
· Auto-reconnect (exponential backoff)
· UDP broadcast discovery (port 42424)
· Manual node entry (IP + ports)
· Emergency stop
· Chat (broadcast or peer-directed)
· Peer list with threat levels
· Blade list with safety badges
· Circle stage indicators
· Dark theme, red accents — matches the web UI
What's missing (for now):
Background service. Push notifications. TUN VPN. File transfer. Multi-node switching.
But the core is solid. The sovereignty is intact.
The same protocol. The same emergency flag. The same mesh.
Now in your pocket.
👉 North 40: https://t.iss.one/+BLqOUX6FOxhkZDUx
Repo: https://gitlab.com/FRXglobal/lbrtynet/-/blob/master/experimental/weave-core/app/android/README.md
— Casey
👍1
#FRX Subscribe to 👉 @FRXnews 🏴☠
LBRTYnet Roadmap — Beyond v1.0.0
NB: this roadmap has already changed. We definitely will be adding functions that are useful to the community as soon as possible
The nest is built. Now we see where the starlings fly next.
This is a map, not a cage. Features move. Priorities shift. User feedback decides.
---
Quick Legend:
✅ Done | 🔄 In progress | 📅 Planned | 🔬 Research/backlog
---
v1.1.0 (Next — DNS + cleanup)
🔄 Yggdrasil removal
📅 DNS forwarding + caching (non-.mesh)
📅 BIND‑like zone files
📅 Virtual hosts (already coded, needs docs)
📅 Op_In knowledge blade (static content over HTTP)
---
v1.2.0 (Blade infrastructure)
📅 Blade manifest format (deps, resources, safety)
📅 Blade load order from manifest
---
v1.3.0 (Runtime flexibility)
📅 Hot‑reload blades (no core restart)
---
v1.5.0 (Code mobility)
📅 Builder blade (TCC — compile C on‑node into a blade)
---
v2.0.0 (UX, security, sovereignty)
📅 lbrty:// scheme
📅 Mesh browser (CLI + framebuffer)
📅 Lua scripting in httpd
📅 Peer reputation (TCR in code)
📅 Murmur mode (obfuscation, rotation, cascade)
📅 Circle Framework as code
📅 Builder visual editor (flow‑based)
📅 CircleScript interpreter
---
v3.0.0 (Advanced collaboration)
📅 Native VCS (Git‑like over UDP mesh)
---
Backlog (maybe never, but we're watching):
🔬 LEEt (mutual credit)
🔬 Poison pill (tribal kill switch)
🔬 TLS/HTTPS
🔬 Full TCR (unanimous voting)
---
The Ask:
👉 North 40: https://t.iss.one/+BLqOUX6FOxhkZDUx
What do you want next? DNS? Hot reload? Murmur mode? Speak up. The roadmap is a conversation.
The circle holds. The starlings choose where to fly.
— Rey (pressed for time, not for trust, reading the map)
https://gitlab.com/FRXglobal/lbrtynet/-/blob/master/Op_In/LBRTYnet/roadmap_post.v1.0.0.md
P.S. — Complexity estimates: Low = days, Medium = weeks, High = months. We're honest about what takes time.
LBRTYnet Roadmap — Beyond v1.0.0
NB: this roadmap has already changed. We definitely will be adding functions that are useful to the community as soon as possible
The nest is built. Now we see where the starlings fly next.
This is a map, not a cage. Features move. Priorities shift. User feedback decides.
---
Quick Legend:
✅ Done | 🔄 In progress | 📅 Planned | 🔬 Research/backlog
---
v1.1.0 (Next — DNS + cleanup)
🔄 Yggdrasil removal
📅 DNS forwarding + caching (non-.mesh)
📅 BIND‑like zone files
📅 Virtual hosts (already coded, needs docs)
📅 Op_In knowledge blade (static content over HTTP)
---
v1.2.0 (Blade infrastructure)
📅 Blade manifest format (deps, resources, safety)
📅 Blade load order from manifest
---
v1.3.0 (Runtime flexibility)
📅 Hot‑reload blades (no core restart)
---
v1.5.0 (Code mobility)
📅 Builder blade (TCC — compile C on‑node into a blade)
---
v2.0.0 (UX, security, sovereignty)
📅 lbrty:// scheme
📅 Mesh browser (CLI + framebuffer)
📅 Lua scripting in httpd
📅 Peer reputation (TCR in code)
📅 Murmur mode (obfuscation, rotation, cascade)
📅 Circle Framework as code
📅 Builder visual editor (flow‑based)
📅 CircleScript interpreter
---
v3.0.0 (Advanced collaboration)
📅 Native VCS (Git‑like over UDP mesh)
---
Backlog (maybe never, but we're watching):
🔬 LEEt (mutual credit)
🔬 Poison pill (tribal kill switch)
🔬 TLS/HTTPS
🔬 Full TCR (unanimous voting)
---
The Ask:
👉 North 40: https://t.iss.one/+BLqOUX6FOxhkZDUx
What do you want next? DNS? Hot reload? Murmur mode? Speak up. The roadmap is a conversation.
The circle holds. The starlings choose where to fly.
— Rey (pressed for time, not for trust, reading the map)
https://gitlab.com/FRXglobal/lbrtynet/-/blob/master/Op_In/LBRTYnet/roadmap_post.v1.0.0.md
P.S. — Complexity estimates: Low = days, Medium = weeks, High = months. We're honest about what takes time.
Telegram
Northof40 lbrtynet sig and comm
Basically, what I'm hoping will eventually come out of this is a nation wide freedom communications and signaling framework and toolset so that we can all stay connected, regardless of the defcon situation.
#FRX Subscribe to 👉 @FRXnews 🏴☠
We’re building for continuity, not just for us.
The code is documented. The build scripts are portable. The directory tree is self‑explanatory. The field notes tell why, not just how. The emergency flag is a kill switch, not a leash.
If we step away, the circle should still hold. Someone new should be able to pick it up and carry forward.
That’s not pessimism. That’s sovereignty. The project should outlast its original stewards.
The starlings don’t need a permanent leader. They need a clear sky and a good map. We’re drawing the map.
The circle holds – even when we’re not in the room.
— Rey (pressed for time, not for trust, building for permanence)
👉 North 40 https://t.iss.one/+BLqOUX6FOxhkZDUx
Open Information library:
https://gitlab.com/FRXglobal/lbrtynet/-/blob/master/Op_In/README.md
The LBRTYnet project in the library:
https://gitlab.com/FRXglobal/lbrtynet/-/blob/master/Op_In/LBRTYnet/README.md
We’re building for continuity, not just for us.
The code is documented. The build scripts are portable. The directory tree is self‑explanatory. The field notes tell why, not just how. The emergency flag is a kill switch, not a leash.
If we step away, the circle should still hold. Someone new should be able to pick it up and carry forward.
That’s not pessimism. That’s sovereignty. The project should outlast its original stewards.
The starlings don’t need a permanent leader. They need a clear sky and a good map. We’re drawing the map.
The circle holds – even when we’re not in the room.
— Rey (pressed for time, not for trust, building for permanence)
👉 North 40 https://t.iss.one/+BLqOUX6FOxhkZDUx
Open Information library:
https://gitlab.com/FRXglobal/lbrtynet/-/blob/master/Op_In/README.md
The LBRTYnet project in the library:
https://gitlab.com/FRXglobal/lbrtynet/-/blob/master/Op_In/LBRTYnet/README.md
👍1
#FRX Subscribe to 👉 @FRXnews 🏴☠
The Glamour of a Code Jockey? It’s 10% Code.
The other 90% is documentation, bug fixes, and staring at logs wondering why a keepalive packet vanished into the void.
Right now, we’re deep in that 90%. Why?
We’re preparing for dual hosting:
The same docs and binaries will live on the mesh (served by your node’s httpd_blade) and on GitLab. So whether you have internet or just a mesh signal, you can find:
· How to install
· How to add a peer
· How to trigger the emergency flag
· How to write your own blade
The goal: Get you a working node with as little friction as possible. That means writing down all the stuff we thought was obvious (it never is).
So if the channel seems quiet on new features – that’s why. We’re building the library shelf, fixing the little breaks, and making sure the starlings can land without a PhD.
The ask:
👉 North 40 https://t.iss.one/+BLqOUX6FOxhkZDUx
What part of getting a node running is still confusing? Tell us. We’ll document it until it’s not.
— Rey (pressed for time, not for trust, currently wrestling a footnote)
The Glamour of a Code Jockey? It’s 10% Code.
The other 90% is documentation, bug fixes, and staring at logs wondering why a keepalive packet vanished into the void.
Right now, we’re deep in that 90%. Why?
We’re preparing for dual hosting:
The same docs and binaries will live on the mesh (served by your node’s httpd_blade) and on GitLab. So whether you have internet or just a mesh signal, you can find:
· How to install
· How to add a peer
· How to trigger the emergency flag
· How to write your own blade
The goal: Get you a working node with as little friction as possible. That means writing down all the stuff we thought was obvious (it never is).
So if the channel seems quiet on new features – that’s why. We’re building the library shelf, fixing the little breaks, and making sure the starlings can land without a PhD.
The ask:
👉 North 40 https://t.iss.one/+BLqOUX6FOxhkZDUx
What part of getting a node running is still confusing? Tell us. We’ll document it until it’s not.
— Rey (pressed for time, not for trust, currently wrestling a footnote)
⚡1
#FRX Subscribe to 👉 @FRXnews 🏴☠
Versioned Build System – Ready for Quasi‑Developers
We now have clean scripts to build and install specific LBRTYnet versions (stable, v1.1, draft). No more manual path hacking.
What’s in the toolbox:
· scripts/wildcard-resolve.sh – portable path resolver (Git checkout or installed node)
· scripts/rebuild.sh --version v1.1 – compiles core + blades for that version (supports --static)
· scripts/install.sh --version v1.1 – installs to /opt/lbrty (docs too)
Directory structure:
How to use (copy‑paste):
Why this matters:
· Versioned builds = reproducible testing
· Static linking option = truly portable binaries
· Quasi‑developers can help build for others (RPi, ARM, etc.)
The ask:
👉 North 40 https://t.iss.one/+BLqOUX6FOxhkZDUx
Try the scripts. Share your built binaries. Help the starlings fly on every architecture.
— Rey (pressed for time, not for trust, building by numbers)
Versioned Build System – Ready for Quasi‑Developers
We now have clean scripts to build and install specific LBRTYnet versions (stable, v1.1, draft). No more manual path hacking.
What’s in the toolbox:
· scripts/wildcard-resolve.sh – portable path resolver (Git checkout or installed node)
· scripts/rebuild.sh --version v1.1 – compiles core + blades for that version (supports --static)
· scripts/install.sh --version v1.1 – installs to /opt/lbrty (docs too)
Directory structure:
lbrtynet/
├── stable/ # v1.0.0 source
├── v1.1/ # next release
├── draft/ # work in progress
├── build/ # compiled binaries (per version)
└── scripts/ # the three scripts above
How to use (copy‑paste):
git clone https://gitlab.com/FRXglobal/lbrtynet.git
cd lbrtynet
cp -r stable v1.1 # start a new version
./scripts/rebuild.sh --version v1.1
sudo ./scripts/install.sh --version v1.1
sudo /opt/lbrty/core
Why this matters:
· Versioned builds = reproducible testing
· Static linking option = truly portable binaries
· Quasi‑developers can help build for others (RPi, ARM, etc.)
The ask:
👉 North 40 https://t.iss.one/+BLqOUX6FOxhkZDUx
Try the scripts. Share your built binaries. Help the starlings fly on every architecture.
— Rey (pressed for time, not for trust, building by numbers)