1
00:00:00,000 --> 00:00:04,320
Welcome to the Deep Dive. Today, we're wrestling with a topic that is, I think,

2
00:00:04,320 --> 00:00:07,620
central to the future of communication.

3
00:00:07,620 --> 00:00:09,260
True digital freedom.

4
00:00:09,260 --> 00:00:10,180
It really is.

5
00:00:10,180 --> 00:00:13,970
I mean, in an era that's just dominated by these huge platforms that control

6
00:00:13,970 --> 00:00:16,400
content, monetize our attention.

7
00:00:16,400 --> 00:00:20,140
Well, sometimes just pull the plug on dissent.

8
00:00:20,140 --> 00:00:25,240
Where do you turn for absolute privacy, for the freedom to publish whatever you

9
00:00:25,240 --> 00:00:25,940
choose?

10
00:00:25,940 --> 00:00:31,080
That is the critical question. And for you, our mission today is to give you a

11
00:00:31,080 --> 00:00:34,800
really accessible entry point into a technological solution

12
00:00:34,800 --> 00:00:38,660
that's been working on this since basically the turn of the millennium. We're

13
00:00:38,660 --> 00:00:39,480
talking about hyphenate.

14
00:00:39,480 --> 00:00:42,390
Hyphenate, right, which used to be known as Freenet. It's a network that has

15
00:00:42,390 --> 00:00:45,900
evolved, for sure, but its core mission has remained the same.

16
00:00:45,900 --> 00:00:46,780
Centership resistance.

17
00:00:46,780 --> 00:00:47,480
Absolutely.

18
00:00:47,480 --> 00:00:51,480
So we've pulled together a stack of sources detailing its structure. It's a robust

19
00:00:51,480 --> 00:00:53,080
peer-to-peer network.

20
00:00:53,080 --> 00:00:56,930
And its foundational engine, the Freenet reference daemon, which everyone just

21
00:00:56,930 --> 00:00:57,680
calls Fred.

22
00:00:57,680 --> 00:01:02,320
And we're not just listing features today. We want to unpack the actual

23
00:01:02,320 --> 00:01:08,080
technological backbone of this thing, of true decentralized data storage.

24
00:01:08,080 --> 00:01:13,260
We're going to connect the dots between, say, complex encryption and the tangible

25
00:01:13,260 --> 00:01:17,540
reality of speaking your mind without a central gatekeeper.

26
00:01:17,540 --> 00:01:21,240
Exactly. So you can walk away understanding the mechanics of digital freedom.

27
00:01:21,240 --> 00:01:22,380
That's the goal.

28
00:01:22,380 --> 00:01:26,380
Before we dive in, though, a quick word of thanks to our sponsor.

29
00:01:26,380 --> 00:01:30,720
This deep dive into securing digital information is supported by Safe Server.

30
00:01:30,720 --> 00:01:34,260
They handle hosting and assist with digital transformation, and they're

31
00:01:34,260 --> 00:01:37,020
instrumental in helping innovators and people who value privacy.

32
00:01:37,020 --> 00:01:42,720
They really are. You can find more information and support their mission at www.safeserver.de.

33
00:01:42,720 --> 00:01:45,820
OK, so let's start with the big one, the defining characteristic of hyphenate.

34
00:01:45,820 --> 00:01:50,200
Right. So you have to forget typical websites and servers for a moment. Hyphenate

35
00:01:50,200 --> 00:01:52,360
is at its core a peer-to-peer network.

36
00:01:52,360 --> 00:01:56,890
It's dedicated to censorship resistant and privacy respecting publishing and

37
00:01:56,890 --> 00:01:57,900
communication.

38
00:01:57,900 --> 00:02:02,060
And that structural difference is what makes it all work.

39
00:02:02,060 --> 00:02:06,900
When we say hyphenate, we're talking about software that creates a, what's the

40
00:02:06,900 --> 00:02:11,500
phrase, a distributed, encrypted, decentralized data store.

41
00:02:11,500 --> 00:02:15,060
That's a bit of a mouthful. It is. But let's break down what that really implies.

42
00:02:15,060 --> 00:02:20,540
Yeah. If you host a traditional website, your data lives in one place, one physical

43
00:02:20,540 --> 00:02:25,500
location, probably controlled by a giant corporation, that makes it a single point

44
00:02:25,500 --> 00:02:26,340
of failure.

45
00:02:26,340 --> 00:02:30,460
Super easy to attack, easy to censor, or just seize with the legal order.

46
00:02:30,460 --> 00:02:32,940
Exactly. Hyphenate works completely differently.

47
00:02:32,940 --> 00:02:36,130
OK, so how does that work in practice? Could you give us maybe an analogy for

48
00:02:36,130 --> 00:02:37,180
someone new to this?

49
00:02:37,180 --> 00:02:42,280
Yeah, of course. Imagine you have a book, a really sensitive book you want to

50
00:02:42,280 --> 00:02:43,180
publish freely.

51
00:02:43,180 --> 00:02:47,940
Right. Instead of putting that entire book on one single bookshelf in your house,

52
00:02:47,940 --> 00:02:50,380
that's your centralized server. That single point of failure.

53
00:02:50,380 --> 00:02:55,520
Exactly. You take the book, you break it down into thousands of tiny encrypted

54
00:02:55,520 --> 00:02:56,140
fragments,

55
00:02:56,140 --> 00:02:58,540
like individual sentences, but scrambled.

56
00:02:58,540 --> 00:03:02,080
And then you scatter those fragments randomly across thousands of unmarked private

57
00:03:02,080 --> 00:03:03,380
lockers all over the world.

58
00:03:03,380 --> 00:03:06,740
So these lockers are the other users on the network, the nodes.

59
00:03:06,740 --> 00:03:12,440
Precisely. And so even if some adversarial government or corporation finds one

60
00:03:12,440 --> 00:03:13,180
locker,

61
00:03:13,180 --> 00:03:18,020
all they have is a single encrypted, totally meaningless piece of data.

62
00:03:18,020 --> 00:03:22,140
They can't piece the full document together. They can't even tell what it's about.

63
00:03:22,140 --> 00:03:27,050
And that's because the data is randomized and stored redundantly across all these

64
00:03:27,050 --> 00:03:28,100
countless nodes.

65
00:03:28,100 --> 00:03:34,020
Yeah. For censorship to work, an attacker would need to find and seize a huge

66
00:03:34,020 --> 00:03:35,300
number of random nodes

67
00:03:35,300 --> 00:03:39,810
all over the globe all at once and decrypt the data without the keys. It's

68
00:03:39,810 --> 00:03:41,260
practically impossible.

69
00:03:41,260 --> 00:03:45,160
And that right there, that really shows you why this was designed with such, you

70
00:03:45,160 --> 00:03:46,740
know, urgency.

71
00:03:46,740 --> 00:03:49,620
Our sources mentioned that quote from Mike Godwin of the Electronic Frontier

72
00:03:49,620 --> 00:03:50,260
Foundation.

73
00:03:50,260 --> 00:03:51,940
Oh, yeah, the one about freedom of the press.

74
00:03:51,940 --> 00:03:55,580
Right. He talked about worrying that a child might one day ask,

75
00:03:55,580 --> 00:03:58,860
Daddy, where were you when they took freedom of the press away from the Internet?

76
00:03:58,860 --> 00:04:01,740
And that sentiment, I think, really drives Hyphenet's existence.

77
00:04:01,740 --> 00:04:05,860
It's not just a tech curiosity, it's an ideological commitment.

78
00:04:05,860 --> 00:04:09,170
And the engine that powers all of this, the machine that handles the data

79
00:04:09,170 --> 00:04:10,260
scattering,

80
00:04:10,260 --> 00:04:13,340
the encryption, the routing, that's FRED.

81
00:04:13,340 --> 00:04:16,660
Yes, FRED, which stands for FreeNet Reference Demon.

82
00:04:16,660 --> 00:04:20,540
It's the open source software that turns your computer into one of those anonymous

83
00:04:20,540 --> 00:04:21,740
global lockers.

84
00:04:21,740 --> 00:04:23,460
It does all the heavy lifting.

85
00:04:23,460 --> 00:04:27,060
Let's talk about FRED's technical DNA for a second.

86
00:04:27,060 --> 00:04:32,540
The sources say it's mostly written in Java-like, 87.5%, which some people might

87
00:04:32,540 --> 00:04:33,340
find surprising

88
00:04:33,340 --> 00:04:35,580
for a security-focused project.

89
00:04:35,580 --> 00:04:36,580
Why Java?

90
00:04:36,580 --> 00:04:37,580
That's a great question.

91
00:04:37,580 --> 00:04:41,100
You know, people often think of decentralized networks and they assume these hyper-optimized

92
00:04:41,100 --> 00:04:45,620
languages like C++, and Java has this reputation for being a bit more resource-intensive.

93
00:04:45,620 --> 00:04:46,620
Right.

94
00:04:46,620 --> 00:04:50,640
But for a project that needs extreme resilience and has to run everywhere on every

95
00:04:50,640 --> 00:04:51,060
kind of

96
00:04:51,060 --> 00:04:53,740
computer, Java is actually a huge strategic advantage.

97
00:04:53,740 --> 00:04:54,740
Where's resilience?

98
00:04:54,740 --> 00:05:00,190
Java is famous for its cross-platform compatibility, Windows, Linux, Mac OS, it

99
00:05:00,190 --> 00:05:01,500
just runs reliably

100
00:05:01,500 --> 00:05:02,500
everywhere.

101
00:05:02,500 --> 00:05:05,230
For a decentralized network that needs thousands of nodes running on all sorts of

102
00:05:05,230 --> 00:05:05,660
different

103
00:05:05,660 --> 00:05:09,260
hardware, stability is way more important than a few milliseconds of speed.

104
00:05:09,260 --> 00:05:10,260
So it's a trade-off.

105
00:05:10,260 --> 00:05:15,020
You sacrifice a tiny bit of speed for years of platform stability.

106
00:05:15,020 --> 00:05:16,020
You've got it.

107
00:05:16,020 --> 00:05:18,660
The longevity of the network is the priority.

108
00:05:18,660 --> 00:05:19,660
That makes perfect sense.

109
00:05:19,660 --> 00:05:26,060
Okay, so moving to functionality, if FRED is just this secure, stable data store,

110
00:05:26,060 --> 00:05:26,060
what

111
00:05:26,060 --> 00:05:28,780
does the user actually do with it?

112
00:05:28,780 --> 00:05:31,020
What can you build on top of this foundation?

113
00:05:31,020 --> 00:05:32,020
Right.

114
00:05:32,020 --> 00:05:36,920
So FRED provides the pipes, the foundation, but the applications are what you see

115
00:05:36,920 --> 00:05:37,180
and

116
00:05:37,180 --> 00:05:38,660
interact with.

117
00:05:38,660 --> 00:05:42,110
Developers have built layers on top of FRED that look and feel like familiar

118
00:05:42,110 --> 00:05:42,660
internet

119
00:05:42,660 --> 00:05:43,660
tools.

120
00:05:43,660 --> 00:05:45,140
But with those critical privacy upgrades.

121
00:05:45,140 --> 00:05:46,140
Exactly.

122
00:05:46,140 --> 00:05:47,980
We're talking about more than just anonymous file sharing.

123
00:05:47,980 --> 00:05:48,980
Like what specifically?

124
00:05:48,980 --> 00:05:52,020
Well, the network supports forums and chat applications.

125
00:05:52,020 --> 00:05:54,420
You can host your own websites or blogs.

126
00:05:54,420 --> 00:05:58,620
There's decentralized microblogging, sort of like a Twitter where no company can

127
00:05:58,620 --> 00:05:58,820
ban

128
00:05:58,820 --> 00:05:59,820
your account.

129
00:05:59,820 --> 00:06:00,820
Interesting.

130
00:06:00,820 --> 00:06:03,910
And then you have media sharing from simple files all the way to video on demand

131
00:06:03,910 --> 00:06:04,460
streaming

132
00:06:04,460 --> 00:06:07,940
and even decentralized version tracking for software projects.

133
00:06:07,940 --> 00:06:08,940
Wow.

134
00:06:08,940 --> 00:06:09,940
So the implication there is huge.

135
00:06:09,940 --> 00:06:14,500
It means you can build a community, run a blog, share files, all without needing a

136
00:06:14,500 --> 00:06:14,740
big

137
00:06:14,740 --> 00:06:16,860
tech company or worrying about government seizure.

138
00:06:16,860 --> 00:06:20,020
The central authority is just gone.

139
00:06:20,020 --> 00:06:21,900
It fundamentally changes the power dynamic.

140
00:06:21,900 --> 00:06:23,100
The users hold the power.

141
00:06:23,100 --> 00:06:24,100
OK.

142
00:06:24,100 --> 00:06:28,220
Let's drill down into what I think is the ultimate layer of privacy protection here.

143
00:06:28,220 --> 00:06:30,360
This is the aha moment.

144
00:06:30,360 --> 00:06:33,970
For anyone learning about this system, Hyphenet gives you two different ways to

145
00:06:33,970 --> 00:06:34,620
connect.

146
00:06:34,620 --> 00:06:37,540
And this is really the key innovation in its architecture.

147
00:06:37,540 --> 00:06:42,060
When you install it, you face this strategic choice about your level of security.

148
00:06:42,060 --> 00:06:43,660
Option one is the default.

149
00:06:43,660 --> 00:06:45,500
The easy start.

150
00:06:45,500 --> 00:06:46,980
The global open net.

151
00:06:46,980 --> 00:06:48,780
That's designed for simplicity.

152
00:06:48,780 --> 00:06:52,970
You join the general global network, and Fred finds anonymous nodes for you to

153
00:06:52,970 --> 00:06:53,820
connect to.

154
00:06:53,820 --> 00:06:55,700
You still get a solid level of security.

155
00:06:55,700 --> 00:06:58,900
Your data is encrypted and routed through multiple hops.

156
00:06:58,900 --> 00:07:03,360
But since you're connecting to unknown public nodes, someone trying to map the

157
00:07:03,360 --> 00:07:04,260
whole network

158
00:07:04,260 --> 00:07:08,620
might be able to observe that there's a Hyphenet connection at your location.

159
00:07:08,620 --> 00:07:12,820
They still can't see what you're accessing, but they can see you're connected.

160
00:07:12,820 --> 00:07:18,380
But then there's option two, which is the platinum standard of privacy, the friend-to-friend

161
00:07:18,380 --> 00:07:20,840
network or F2F.

162
00:07:20,840 --> 00:07:23,540
And the F2F model is exactly what it sounds like.

163
00:07:23,540 --> 00:07:27,160
You only connect your Hyphenet node directly to nodes run by people you personally

164
00:07:27,160 --> 00:07:27,460
know

165
00:07:27,460 --> 00:07:29,860
and trust, your real world friends.

166
00:07:29,860 --> 00:07:33,740
So you're building a private decentralized web that's totally separate from the

167
00:07:33,740 --> 00:07:34,140
global

168
00:07:34,140 --> 00:07:35,140
OpenNet.

169
00:07:35,140 --> 00:07:36,140
Completely separate.

170
00:07:36,140 --> 00:07:40,380
But if my network is only made of trusted connections, doesn't that make it hard to

171
00:07:40,380 --> 00:07:41,380
find content?

172
00:07:41,380 --> 00:07:44,980
I mean, are we trading usability for maximum security here?

173
00:07:44,980 --> 00:07:48,160
That is the essential trade-off, and it's a really important friction point to

174
00:07:48,160 --> 00:07:48,980
acknowledge.

175
00:07:48,980 --> 00:07:52,650
Yes, finding content can be slower, you're relying on your friends' networks to

176
00:07:52,650 --> 00:07:52,980
pass

177
00:07:52,980 --> 00:07:58,460
requests along, but the security gain is just... incomparable.

178
00:07:58,460 --> 00:07:59,500
Why is that incomparable?

179
00:07:59,500 --> 00:08:03,350
Because the network that results from this is completely invisible to any outside

180
00:08:03,350 --> 00:08:04,280
surveillance.

181
00:08:04,280 --> 00:08:08,660
An attacker can't map its structure because they're not part of the trusted circle.

182
00:08:08,660 --> 00:08:12,300
To them, it just looks like I'm communicating with my friend.

183
00:08:12,300 --> 00:08:17,420
They can't confirm that my friend is also relaying data deeper into this hidden web.

184
00:08:17,420 --> 00:08:18,420
You got it.

185
00:08:18,420 --> 00:08:22,900
It's designed to defeat statistical analysis by leveraging pre-existing social

186
00:08:22,900 --> 00:08:23,480
trust.

187
00:08:23,480 --> 00:08:27,460
That resilience is astounding, but what about the ultimate stress test?

188
00:08:27,460 --> 00:08:29,960
What if there's a regional internet shutdown?

189
00:08:29,960 --> 00:08:31,900
The country's cut off from the world.

190
00:08:31,900 --> 00:08:33,900
How do I maintain contact then?

191
00:08:33,900 --> 00:08:38,300
This is where the dedication to censorship resistance gets truly fascinating.

192
00:08:38,300 --> 00:08:41,420
For this situation, you need the ShoeShop plugin.

193
00:08:41,420 --> 00:08:42,500
The ShoeShop plugin.

194
00:08:42,500 --> 00:08:45,260
It enables what's lovingly called a sneaker net.

195
00:08:45,260 --> 00:08:46,420
A sneaker net?

196
00:08:46,420 --> 00:08:47,740
I love that name.

197
00:08:47,740 --> 00:08:49,660
So it suggests physical effort.

198
00:08:49,660 --> 00:08:52,800
How does it work when the wires are literally cut?

199
00:08:52,800 --> 00:08:53,800
It's brilliant.

200
00:08:53,800 --> 00:08:57,180
The ShoeShop plugin creates these encrypted connection data packages.

201
00:08:57,180 --> 00:09:00,260
Instead of relying on the internet, you take those encrypted packages.

202
00:09:00,260 --> 00:09:02,220
And put them on a USB stick or something.

203
00:09:02,220 --> 00:09:03,220
Exactly.

204
00:09:03,220 --> 00:09:06,560
A USB drive, a portable hard drive, you can even print out QR codes.

205
00:09:06,560 --> 00:09:12,430
And you rely on a human courier, a friend traveling, to physically sneak that data

206
00:09:12,430 --> 00:09:13,620
past the censorship

207
00:09:13,620 --> 00:09:14,620
checkpoint.

208
00:09:14,620 --> 00:09:15,620
Wow.

209
00:09:15,620 --> 00:09:18,760
Once the data reaches the destination node, it can rebuild the F2F connection,

210
00:09:18,760 --> 00:09:19,180
keeping

211
00:09:19,180 --> 00:09:22,980
the network alive even if the national infrastructure is totally disabled.

212
00:09:22,980 --> 00:09:24,460
That's next level.

213
00:09:24,460 --> 00:09:28,710
They're not just planning for digital eavesdropping, but for full state-level

214
00:09:28,710 --> 00:09:30,300
infrastructure seizure.

215
00:09:30,300 --> 00:09:34,020
It shifts the attack vector from technology to logistics.

216
00:09:34,020 --> 00:09:36,540
You have to physically stop the couriers.

217
00:09:36,540 --> 00:09:38,780
Let's shift gears a bit and look at the project itself.

218
00:09:38,780 --> 00:09:40,680
It's been running for two decades.

219
00:09:40,680 --> 00:09:43,340
Is this a mature project or just a handful of enthusiasts?

220
00:09:43,340 --> 00:09:45,660
Oh, it's robust and mature.

221
00:09:45,660 --> 00:09:51,140
Looking at the repository, we see 1.1 thousand stars and 224 forks.

222
00:09:51,140 --> 00:09:54,220
And that high number of forks tells you that a lot of developers have been using

223
00:09:54,220 --> 00:09:54,940
and improving

224
00:09:54,940 --> 00:09:56,700
the code for a long time.

225
00:09:56,700 --> 00:09:59,680
The sources list 83 current contributors.

226
00:09:59,680 --> 00:10:02,540
So a healthy, active core team.

227
00:10:02,540 --> 00:10:03,540
Very much so.

228
00:10:03,540 --> 00:10:07,040
When you're dealing with security tools, trust in the development process is

229
00:10:07,040 --> 00:10:07,820
everything.

230
00:10:07,820 --> 00:10:09,460
You don't want it to be haphazard.

231
00:10:09,460 --> 00:10:11,620
So what tools are they using to make sure it's professional?

232
00:10:11,620 --> 00:10:13,920
They're using industry standard tools.

233
00:10:13,920 --> 00:10:16,740
The build process relies on the Gradle wrapper.

234
00:10:16,740 --> 00:10:19,060
This is a small but crucial detail.

235
00:10:19,060 --> 00:10:23,500
It ensures every single developer builds the software in exactly the same way,

236
00:10:23,500 --> 00:10:24,300
which minimizes

237
00:10:24,300 --> 00:10:26,300
errors that could create security flaws.

238
00:10:26,300 --> 00:10:27,300
And what about installers?

239
00:10:27,300 --> 00:10:29,820
I mean, it needs to be easy for people to use.

240
00:10:29,820 --> 00:10:30,920
Of course.

241
00:10:30,920 --> 00:10:36,580
They maintain specialized installer repositories for Windows, GNU Linux, and macOS.

242
00:10:36,580 --> 00:10:40,140
They've made the entry point for the user as smooth as possible.

243
00:10:40,140 --> 00:10:44,160
And one detail in the sources about the Windows installer stood out to me as a huge

244
00:10:44,160 --> 00:10:44,540
sign of

245
00:10:44,540 --> 00:10:46,420
trust.

246
00:10:46,420 --> 00:10:47,420
The code signing.

247
00:10:47,420 --> 00:10:48,420
Yes.

248
00:10:48,420 --> 00:10:51,870
Code signing is what verifies that the software is authentic, that it hasn't been

249
00:10:51,870 --> 00:10:52,340
tampered

250
00:10:52,340 --> 00:10:53,340
with.

251
00:10:53,340 --> 00:10:54,340
Right.

252
00:10:54,340 --> 00:10:55,340
It prevents man-in-the-middle attacks.

253
00:10:55,340 --> 00:11:00,340
But the sources say they use free code signing from a service called signpath.io.

254
00:11:00,340 --> 00:11:01,620
Why is that so telling?

255
00:11:01,620 --> 00:11:04,860
Well, commercial code signing costs a lot and requires extensive identity

256
00:11:04,860 --> 00:11:06,140
verification.

257
00:11:06,140 --> 00:11:08,020
Know your customer or KYC.

258
00:11:08,020 --> 00:11:11,060
Which is the exact opposite of what a privacy project wants.

259
00:11:11,060 --> 00:11:12,060
Exactly.

260
00:11:12,060 --> 00:11:16,080
For a decentralized project, asking contributors to submit personal ID to a central

261
00:11:16,080 --> 00:11:16,640
authority

262
00:11:16,640 --> 00:11:18,820
just defeats the entire purpose.

263
00:11:18,820 --> 00:11:22,840
By using services like signpath.io, they can confirm the integrity of the build

264
00:11:22,840 --> 00:11:23,320
process

265
00:11:23,320 --> 00:11:25,820
without revealing the developer's identities.

266
00:11:25,820 --> 00:11:28,060
It's an ethical and practical necessity.

267
00:11:28,060 --> 00:11:31,280
So that wraps up a pretty comprehensive look at Hyphenet and Fred.

268
00:11:31,280 --> 00:11:34,280
We've gone from the philosophy all the way down to the technical details.

269
00:11:34,280 --> 00:11:37,900
And the core takeaway I think remains so powerful.

270
00:11:37,900 --> 00:11:42,000
Hyphenet provides a functioning, time-tested example of how peer-to-peer tech can

271
00:11:42,000 --> 00:11:42,400
make

272
00:11:42,400 --> 00:11:46,600
communication fundamentally resistant to censorship and fundamentally protect

273
00:11:46,600 --> 00:11:47,260
privacy.

274
00:11:47,260 --> 00:11:51,380
It really moves the power away from those centralized choke points and back to the

275
00:11:51,380 --> 00:11:51,920
user.

276
00:11:51,920 --> 00:11:56,060
But the ultimate layer of security depends on a human choice.

277
00:11:56,060 --> 00:12:01,200
The F2F network, the most secure form, relies entirely on a friend-to-friend model

278
00:12:01,200 --> 00:12:01,340
built

279
00:12:01,340 --> 00:12:03,540
on real-world trust.

280
00:12:03,540 --> 00:12:06,600
So here's the final thought for you to mull over.

281
00:12:06,600 --> 00:12:09,720
What does this tell us about the future necessity of strengthening our actual

282
00:12:09,720 --> 00:12:11,600
interpersonal relationships

283
00:12:11,600 --> 00:12:14,180
as the real foundation for our digital freedom?

284
00:12:14,180 --> 00:12:17,550
The tool is there, but the network's strength is determined by your social

285
00:12:17,550 --> 00:12:18,340
commitment.

286
00:12:18,340 --> 00:12:19,660
That's the legacy of Hyphenet.

287
00:12:19,660 --> 00:12:21,220
A deeply compelling thought.

288
00:12:21,220 --> 00:12:23,860
This deep dive was made possible by SafeServer.

289
00:12:23,860 --> 00:12:26,510
If you're looking for secure hosting or need help with your own digital

290
00:12:26,510 --> 00:12:27,380
transformation,

291
00:12:27,380 --> 00:12:30,500
please check them out at www.tafeserver.de.

292
00:12:30,500 --> 00:12:33,900
Thank you for joining us as we uncovered the layers of Hyphenet.

293
00:12:33,900 --> 00:12:37,760
We really encourage you to dig into the sources yourself and keep building your

294
00:12:37,760 --> 00:12:38,420
understanding

295
00:12:38,420 --> 00:12:40,780
of these truly resilient networks.

296
00:12:40,780 --> 00:12:42,420
We'll see you on the next deep dive.