ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: How to Become Your Own ISP

Your phone can talk to the world, but only the part of it connected to the legacy telecom stack.

But soon, that same phone will be able to discover, connect to, and exchange encrypted data with a mesh network spanning Bluetooth,

LoRa, even over-the-horizon packet radio.

No internet required.

Together, these otherwise disconnected communication networks become a kind of super mesh.

One network of networks that can use whatever path is available.

Unlike 5G cellular or fiber internet, the networks we're talking about are free to use and open source.

It's the foundation for a parallel internet that no single company owns or controls, something today's telecom stack was never designed to provide.

This is Reticulum, an open cryptographically complete networking stack for building resilient networks over just about any medium

that can push ones and zeros.

of relying on IP addresses and fixed infrastructure, it uses cryptographic destinations to find a path across whatever links are available,

even if they're completely offline.

Same permissionless, community-operated spirit as Web3, except without the casino.

It's basically the blockchain of communication.

That means no monthly subscriptions, no central service sitting in the middle, and privacy by default.

And over the past few months, the Reticulum ecosystem has really come alive.

New hardware, new apps, and more builders pushing it forward.

I don't think people understand how transformative the next era of the internet is going to be.

But for Reticulum to live up to the hype and actually be ready for prime time, it can't only work for radio heads willing to assemble elaborate hardware.

Everyday people need to be able to use it on devices that they already understand.

Whether you're at home, or deep in the backcountry, or somewhere that conventional infrastructure has failed,

joining the network should still begin with a device you already understand.

Which presents us with one clean challenge.

Can my partner Amelia, who has no Reticulum experience, download an app and send a message to an offline LoRa device

and receive a reply even though it has no internet connection?

With what I know about reticulum i think we can i've

spent the last few years building networks you can actually own

and operate without subscriptions designed to work when conventional infrastructure fails

but each new implementation requires other like devices in order to begin building out

that mesh and as cool as that might be they're locked to either laura

or bluetooth or whatever the radio modulation is Even within projects like Meshtastic or Meshcore,

you have to use the same frequency and parameters to reach other nodes.

I recently drove from Florida all the way to New Hampshire and back with a Meshtastic node running in my car, and it was listening on Meshtastic's long, fast channel.

So the LoRa frequency was 906, it had a bandwidth of 250 kHz, spreading factor of 11, and a coding rate of 4 over 5.

All said and done, I picked up a healthy 458 nodes along my journey.

And that proves that the interest, infrastructure, and community already exist at scale.

But none of those LoRa connections automatically became one network with other LoRa configurations, Wi-Fi Halo, Packet Radio, HF,

the regular internet, or really anything attempting to do the same thing in another lane.

That's when I realized that the infrastructure buildout wasn't the missing piece.

The ability to bridge network types was.

And that realization brought me to Reticulum.

Now I'll be honest, putting my own public Reticulum transport node on the internet makes me a little nervous.

It means exposing a TCP backbone that anyone can connect to and use, or potentially abuse.

I've never deliberately opened infrastructure like this to the public before.

Building networking infrastructure by the people who use it for the people who use it.

And learning how to do that safely.

But getting the node online would only prove that I could build it.

It wouldn't prove that everyday people could actually use it on devices they already own.

For that, Amelia is a good candidate.

She has none of my context and has never used reticulum.

She gets the free app and once the node is ready, one address.

After that, I'm not going to help her.

If she can't figure it out, then I haven't built an internet for everyone, I've built another network for experts.

This is RMAP, a live map of the Reticulum network.

It shows nodes that choose to make themselves discoverable, where they're located, and what protocols they support.

For Amelia to enter Reticulum through Wi-Fi, 5G, or LTE, her app needs the public address of a TCP backbone node.

Now, we could use one that already exists.

Builders like dude.eth, the creator of Ratspeak, and Ken, also known as Frosty,

who built a mobile reticulum hotspot are already pushing this ecosystem in some really interesting directions.

But I didn't want this project to only consume what others had built.

I wanted to leave the network larger than we found it.

So I decided to build a public parallel node hosted on GCP, one Amelia could use for this challenge,

but also one anyone could use after this video ends.

Now, the irony isn't lost on me that I'm building an open source internet that no one controls on Google Cloud Platform, which is about as centralized as infrastructure gets.

But that's the beauty of Reticulum.

It can use legacy infrastructure without being permanently tied to it.

As LoRa, APRS, HF, and other links fill in the gaps, the network can eventually route around the internet itself.

And that's where I truly believe this space is heading.

I installed Reticulum and enabled the transport, and I gave the TCP interface an address Amelia could reach.

When the daemon started, the server began announcing itself to the wider network.

But this was also where I got nervous.

I wanted to make sure bad actors couldn't abuse my public node or use it as a way into my servers, since this is now publicly exposed.

Years ago, my Google Cloud account was compromised.

I woke up to dozens of virtual machines burning through expensive GPUs and draining my wallet by the minute.

So yeah, ask me how I know.

Nothing will put the fear of god in you faster than

watching a metered service run up a cloud bill tied to your account.

And that's where this video's sponsor TryHackMe comes in.

It's a hands-on, browser-based, cyber security training platform

that lets you safely practice real-world attacks and defenses in a sandboxed environment running in your browser.

It helps you understand how hackers think so you can spot problems before they do.

You get guided rooms and learning paths, all based on real world exploits.

You also get Echo, your AI tutor, which helps you learn faster.

Here I am in the offensive security room where we're essentially simulating hacking into an online bank.

Ethically of course.

TryHackMe spins up a virtual machine where I can run a command line tool called GoBuster,

which finds hidden pages on the site by brute forcing a word list and checking status codes.

And here we go.

It found a custom internal transfer page intended only for bankers.

And if you want to see if we can make an actual bank transfer on that page, then go ahead and continue the course.

And that's how you learn to think like an attacker. By doing.

In my opinion, investments along these lines will always pay dividends.

Particularly in the age of AI, these attacks are becoming increasingly sophisticated.

You can even showcase awards and certifications on your LinkedIn profile, helping you level up both personally and professionally.

If you want to try this yourself, jump into TryHackMe with the link in the description below.

Start with the offensive security room and see how far you get.

Many of the rooms are free to play and if you use my code SLAYER, you'll get 25% off the annual plan if you want full access.

And that matters here because this whole project only becomes useful if people can run public pieces of infrastructure without unnecessary risk.

Which brings us back to the node.

100

We had the node exposed and working under a public static IP address, but I wanted to give it its own domain.

101

So I created a CNAME on build with parallel called rns1 pointing to our GCP compute engine instance.

102

We added the static GPS coordinates for the general vicinity where the node is managed

103

so it would appear on the map where we renamed the node

104

and shut off any additional ports and access it didn't need.

105

Finally, it was ready.

106

And there it is.

107

Our public parallel node.

108

Live on our map alongside other nodes around the world.

109

I could stop here and call this a successful build, but a dot on a map doesn't prove that anyone can actually use it.

110

We've only built the doorway.

111

We still have to have someone walk through it.

112

Now in prior videos, we've moved reticulum data over LoRa, Ethernet, traditional Wi-Fi, even Wi-Fi Halo.

113

In fact, we even sent a message over Tailscale Mesh VPN.

114

But in this video, we want to send messages without requiring any exotic gear from our sender, Amelia.

115

Before handing it to Amelia, I need to prove the node worked from somewhere outside GCP.

116

So on my Mac, I opened Crosstalk, the Reticulum client I've been building.

117

It works in a browser or as a standalone app.

118

I'll put a link to that in the the description below.

119

I added rns1.buildwithparallel.com as a TCP interface, entered the port, and enabled it, the same way anyone else would connect to the node.

120

Within seconds, Crosstalk had a path to the network.

121

Crosstalk has one view that I'm going to deliberately not show you quite yet.

122

I recently added it to expose the infrastructure operating underneath the network, but showing it now would give away one of the tests coming later,

123

but I wanted something more visual than a connection indicator.

124

So I opened Nomad Network Browser and entered the cryptographic address of a tiny page I created.

125

And there it is.

126

This is NomadNet, a lightweight, text-based alternative to the web.

127

Instead of living at a conventional website or domain, pages are addressed and delivered directly over Reticulum.

128

Many are privately hosted on tiny, low-powered systems, some even running on solar.

129

So our node wasn't just online and routing traffic, it was already serving a tiny piece of the open source internet.

130

And this is only one small piece of the larger mission.

131

On this channel, our goal is to build a free open source internet that anyone can use, build, and own.

132

But connecting from another computer is still a builder's test.

133

Amelia has to prove this works for a normal person on a normal phone.

134

For that, we're using Columba, which is an Android client for Reticulum.

135

Sideband proved Reticulum could work on Android, but Columba is the first client I've used that begins to feel like a normal messaging app and can connect through TCP,

136

Wi-Fi, Bluetooth, or an R node.

137

In my experience, it has also been considerably more reliable than Sideband.

138

That matters because if joining this network requires a terminal tutorial, it will never reach everyday people.

139

I gave Amelia the app and one address, the public node that we just built.

140

From here she's on her own.

141

Now the obvious objection is that I've built an alternative internet using Google Cloud.

142

And you'd be right.

143

So far this is still the regular internet carrying reticulum traffic, just with extra steps.

144

Today the conventional internet is carrying the long haul portion, but to Reticulum, even the internet is only another temporary interface.

145

The real test is whether that message can leave conventional infrastructure and reach a device that has no internet connection at all.

146

To get a message from Amelia to a phone with no internet, I needed three pieces working together.

147

First, Amelia's phone.

148

She's using Columba over LTE, connected by TCP to the public node we just built on GCP.

149

Second, the field bridge.

150

This is Haven connected to Starlink and a USB R node.

151

Haven is running Reticulum with two interfaces,

152

a TCP connection to our public node through Starlink and a 915 MHz LoRa connection through the R node.

153

That means traffic can arrive from the internet on one side and leave over LoRa on the other.

154

Third, the offline phone.

155

This is a backup Android phone running columba with cellular wi-fi

156

and bluetooth disabled its only connection is the r node attached over usb

157

and its only path to the network is laura if everything works

158

that route should carry a message in both directions okay

159

so amelia is back at the house with her android phone

160

and she's gonna just try sending us messages we're gonna try

161

sending messages to her her android phone is connected to the

162

internet the internet is connected to our starlink our Starlink is connected to our Heltech V4 way over there, but then from there the internet drops off and it's just LoRa.

163

So that is the mission here.

164

And experiments like this are exactly why I like Haven.

165

Underneath it's a Raspberry Pi running Linux so I can connect SDRs,

166

microcontrollers, LoRa boards, and whatever strange peripheral the next experiment requires.

167

Unlike most closed all-in-one wireless systems haven provides its own power usb connectivity

168

and a full field computer

169

that i can mount on a tripod i'm just gonna test to see

170

if i can send a message and get it through

171

because now that the node's up

172

that might just work i'm gonna do test two see what happens it's not up the hell tech is up

173

so the routing just hasn't established yet two checks i do we're looking good

174

so what this will let me do is put the android phone up there

175

and then also the antenna is going to be that guy

176

so just a little bit better of a setup here

177

so now i just want to drive out

178

and see how far we can go and still get messages through so that's our goal right now

179

okay so we're at half a mile here

180

so i think it's a good time to run a little test radio check test

181

so i'm just gonna do t2 it says last seen eight

182

minutes ago it's not a good sign oh last seen just now

183

so i think we're still good that's half a mile

184

so we're gonna keep going here no cellular connection no wi-fi the only possible path between us is laura

185

so two check boxes this time uh we are 0.84 miles away

186

so we're gonna keep going until the signal dies there but Alright, so we're at 2.3 miles.

187

I want to see if I can get anything through here, but I doubt it because we have a whole lot of foliage, quite a few obstacles, or obstructions rather.

188

So I don't expect this to go through.

189

Okay, we're about two and a half miles away from the base station, and we have no connection.

190

So now you get to see what I was hiding.

191

This is Old Faithful.

192

We're officially infrastructure maxing, and the node attached to it doesn't need a phone, a Raspberry Pi or even a full operating system.

193

Earlier I flashed another Helltech v4 with a special new firmware called RTnode.

194

A builder who goes by JRL290 on GitHub packaged Micro Reticulum into a usable standalone transport node for this board.

195

Okay so what I came up with here is I basically implemented like a version of micro reticulum

196

which is an entire rns stack running just on an mcu

197

and this guy's set up to act as just a relay

198

so it's not an identity but it can broaden the mesh

199

and support the mesh it doesn't need a full-fledged computer just

200

runs on the mcu this wasn't possible even just like a couple months ago

201

but because there's so much innovation in the space i was able to get this to work

202

so i'm going to do is i'm going to take this i'm going to throw it on the drone

203

and then maybe my car could relay messages through this back to our original base station.

204

This is what makes this different from the two ground R nodes.

205

Those act as LoRa radios for a phone or a computer, but this actually runs Reticulum itself.

206

And remember the part of crosstalk I refuse to show you?

207

Most Reticulum clients focus on LXMF delivery addresses, the people and services you can actually message.

208

But some nodes don't have an LXMF delivery address at all.

209

They aren't contacts.

210

They exist only to discover paths and relay traffic.

211

I added a feature to Crosstalk that exposes those infrastructure nodes too.

212

And there it is.

213

The Heltec V4 transport node, Old Faithful.

214

Crosstalk can see it even though it has no messaging address, because its only job is to act as a relay infrastructure.

215

The US military helped pioneer packet networking.

216

I improved it by attaching a $20 transport node to a drone.

217

You're welcome.

218

And I haven't seen anyone do this with reticulum yet, so this might be a first.

219

Up until recently, this kind of self-contained drone relay was something I had only seen Meshtastic do.

220

But now with Micro Reticulum, we can run full self-contained nodes on microcontrollers.

221

That means drone nodes like SkyMesh here, along with other solar-powered and exotic self-contained off-grid infrastructure,

222

which is super exciting stuff.

223

The Heltec drone adapter fits the Heltec V3 and V4 and can be purchased on the website.

224

I just love cheap rigs that punch outside their weight class and this is definitely an example of that.

225

I configured it as a standalone transport node, a LoRa only repeater.

226

It isn't a messaging contact, its only job is to discover paths and relay traffic.

227

It uses the same LoRa parameters as both ground radios.

228

And because LoRa depends heavily on line of sight, lifting this above the trees could be sufficient to extend our LoRa path back to our base station.

229

At least that's the theory.

230

If it works, the offline phone should regain a path without us changing anything else at all.

231

The old faithful here has to get airborne.

232

But before that could even happen, the drone started overheating.

233

Lovely.

234

So I turned the car's AC all the way up and improvised a cooling station.

235

Bruno may have been overheating too, or maybe he just likes being blasted with cool air.

236

Our ground path was dead.

237

The base station was draining its Life PO4 battery, and now the only thing capable of completing the route couldn't get off the ground.

238

Few minutes later the warning disappeared so I went ahead

239

and launched before the drone could find another reason to ruin the experiment.

240

But the problems weren't over.

241

I literally got a vulture trying to take out my drone right now.

242

You guys have no idea.

243

A vulture started circling it and I've done enough field tests to know it wasn't just admiring the technology.

244

Vulture seems to be gone, hopefully.

245

With Old Faithful finally above the trees, I went back to my Android phone and started testing.

246

Okay we have our drone up there, I'm flying it right here, but it still says six minutes ago so it hasn't relayed anything yet.

247

So I'm gonna go a bit higher and I'm gonna do an announce and see if that helps at all.

248

The micro reticulum relay was working, then reticulum should be able to discover a path through the drone back to Amelia.

249

So I started firing off some messages.

250

And at first it was just crickets.

251

So you can see right here, we tried sending some messages, but mostly not getting any checks.

252

I guess we might not get two checks because we're not going to be reading them on the other side.

253

But after quite a bit of back and forth, there it was.

254

A message from Amelia, delivered to our Android phone with no internet connection.

255

Super pumped with that result.

256

So we got some messages through.

257

So that is from Amelia.

258

But I guess if you really think about it, the Rnode did have an internet connection since it eventually routed to a node with an internet on-ramp.

259

So yeah, this LoRa node has internet, which is crazy.

260

It crossed LoRa to the drone, was repeated to the R node beside Haven,

261

then traveled through the Starlink and our public GCP node before reaching Amelia over LTE.

262

Perhaps the most over-engineered text message in history, but I'm okay with that.

263

Her message crossed the conventional internet, passed through our field bridge, left the internet entirely and traveled over LoRa,

264

through the airborne relay to the offline phone in my hand.

265

One phone was on LTE and the other was completely offline.

266

Between them, Reticulum stitched the public internet, Starlink, and LoRa into a single encrypted path,

267

a network of networks that were never designed to work together, the next era of communication.

268

The number one question I get is how do I even get started in this space?

269

So I built a course called the Parallel primer that gives you all my hard-won insights, the hardware, the software, how the different radios work together,

270

and how to get your first node up and running as fast as possible.

271

I actually build a solar node from beginning to end, and I walk you through the entire stack, front to back, and get you capable enough to build your own infrastructure.

272

The link to that is in the description below.

273

In this test, the legacy internet still carried the middle of the journey.

274

Laura solved the edge and elevation gave it reach.

275

But scaling this approach would require many more elevated relays or alternatively putting some of them in orbit.

276

But those are pricey propositions.

277

I called cell tower leasing companies and for that you're looking at a $3,000 installation fee, a minimum three-year commitment, and monthly rent.

278

A CubeSat could bypass the towers but even a bare bones attempt pushes into five figures.

279

And I've been turning that problem over in my head for nearly a year now, but I think I've finally found another way to bridge the distance.

280

This is Kilo Romeo 4 November November Papa field test 1.

281

HF gateway 1 online, target path 200 miles.

282

Internet relays zero.

283

Standing by for gateway 2, initiating long-haul transport test.

284

Bridging reticulum. For more, click here.

✨ วิดีโอแนะนำ

176 ประโยค

เทคนิค Shadowing คืออะไร?

Shadowing เป็นเทคนิคการเรียนรู้ภาษาที่ได้รับการรับรองทางวิทยาศาสตร์ พัฒนาขึ้นสำหรับการฝึกนักแปลมืออาชีพ วิธีการนี้เรียบง่ายแต่ทรงพลัง: คุณฟังเสียงภาษาอังกฤษจากเจ้าของภาษาและพูดตามทันที — เหมือนเงาที่ตามผู้พูดด้วยช่วงเวลาห่าง 1-2 วินาที การวิจัยแสดงว่าเทคนิคนี้ปรับปรุงความแม่นยำในการออกเสียง ทำนองเสียง จังหวะ การเชื่อมเสียง การฟังเข้าใจ และความคล่องแคล่วในการพูดได้อย่างมีนัยสำคัญ

เทคนิค shadowing: อ่านคู่มือฉบับเต็มทีละขั้นตอน →

ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: How to Become Your Own ISP

Every Networking Concept Explained | Networking 101 (2026)

How Cell Phones Impact Our Relationships

The mystery is solved... and the answer is 40x cheaper than Claude

Mini Project - Implementing a Simple Web Identity Federation Application

Don't Find A Niche. Become The Niche.

The Ultimate IoT Roadmap in 2026? | Embedded Systems & IoT Career Roadmap

Next.js 16.3 got good (if you care)

I think AI slop is about to trigger a renaissance, actually

THIS Is Where the Internet Lives

I Self-Hosted for a Year... Here's What I'd Do Differently.

Understanding the Organization Working in Transmission

GATHERING IN THE DIGITAL ERA

เกี่ยวกับบทเรียนนี้

เทคนิค Shadowing คืออะไร?