1
00:00:00,000 --> 00:00:03,600
We're told all the time that modern tech is, you know, all about convenience.

2
00:00:03,600 --> 00:00:05,240
You scroll, you click, you share.

3
00:00:05,240 --> 00:00:06,380
It's instant.

4
00:00:06,380 --> 00:00:10,080
But we all kind of know there's this unspoken cost, right?

5
00:00:10,080 --> 00:00:11,680
Our privacy. Exactly.

6
00:00:11,680 --> 00:00:15,440
We trade our data, our habits, our digital independence

7
00:00:15,440 --> 00:00:19,020
really for these slick platforms run by massive corporations.

8
00:00:19,020 --> 00:00:23,560
And that trade off feels well, it feels a bit sneaky

9
00:00:23,560 --> 00:00:27,900
because the moment that platform changes its terms or gets bought out

10
00:00:27,900 --> 00:00:32,140
or just shuts down, you lose everything, the community, your history, all of it.

11
00:00:32,140 --> 00:00:33,800
It's gone and you have no control.

12
00:00:33,800 --> 00:00:37,000
So today we are doing a deep dive into something that was built from the ground

13
00:00:37,000 --> 00:00:39,340
up to just bypass that problem entirely.

14
00:00:39,340 --> 00:00:41,100
We're looking at Sources on RetroShare.

15
00:00:41,100 --> 00:00:44,440
It's a free and open source software or FOSS platform.

16
00:00:44,440 --> 00:00:47,220
It's a whole toolkit, really, for communication, for sharing,

17
00:00:47,220 --> 00:00:50,620
all built on one core concept, secure, decentralized,

18
00:00:50,620 --> 00:00:52,820
friend to friend networking or F2F.

19
00:00:52,820 --> 00:00:57,020
And our mission here is to give you a really clear, beginner friendly roadmap

20
00:00:57,260 --> 00:01:01,860
to understand how a network built on trust not on giant servers actually works.

21
00:01:01,860 --> 00:01:05,100
But before we get into all that, we really want to thank the supporter

22
00:01:05,100 --> 00:01:06,360
of this deep dive.

23
00:01:06,360 --> 00:01:09,540
Safe Server handles hosting and supports your digital transformation.

24
00:01:09,540 --> 00:01:12,540
They're great for projects like this open source software

25
00:01:12,540 --> 00:01:14,640
that needs robust architecture.

26
00:01:14,640 --> 00:01:18,240
You can find more info at www.safeserver.de.

27
00:01:18,240 --> 00:01:23,040
OK, so to set the stage, just think of RetroShare as a secure app.

28
00:01:23,040 --> 00:01:24,220
It runs pretty much everywhere.

29
00:01:24,220 --> 00:01:28,120
Linux, Windows, Mac, Android, but the huge difference is that it gives you

30
00:01:28,120 --> 00:01:30,520
things like chat, mail, file sharing.

31
00:01:30,520 --> 00:01:35,100
But with zero reliance on any central authority, no corporate server.

32
00:01:35,100 --> 00:01:37,160
It makes you the owner of your own little network.

33
00:01:37,160 --> 00:01:39,740
Exactly. OK, so that brings up the big question, the why.

34
00:01:39,740 --> 00:01:41,200
I mean, why go to all this trouble?

35
00:01:41,200 --> 00:01:43,040
We've got a million free chat apps.

36
00:01:43,040 --> 00:01:46,540
What's the the real driver behind building something that asks you

37
00:01:46,540 --> 00:01:49,380
to sort of push back against the easy option?

38
00:01:49,380 --> 00:01:52,380
Well, at its core, it's all about independence.

39
00:01:52,940 --> 00:01:55,220
And self-determination.

40
00:01:55,220 --> 00:01:59,220
The people behind this saw where things were heading years ago.

41
00:01:59,220 --> 00:02:02,560
One of their main goals was just creating a social sharing network

42
00:02:02,560 --> 00:02:05,120
that had zero ties to any corporation.

43
00:02:05,120 --> 00:02:09,200
Because those centralized services, they can just disappear.

44
00:02:09,200 --> 00:02:10,560
They have an expiry date.

45
00:02:10,560 --> 00:02:13,100
Oh, or they just change the rules without any warning.

46
00:02:13,100 --> 00:02:14,500
We've all seen that happen.

47
00:02:14,500 --> 00:02:19,780
I mean, the sources mention things like my space or that German platform students.

48
00:02:20,140 --> 00:02:24,240
One day they're massive, the next they're a ghost town and years of community

49
00:02:24,240 --> 00:02:24,680
history.

50
00:02:24,680 --> 00:02:26,680
Just poof. Exactly.

51
00:02:26,680 --> 00:02:30,180
Or, you know, think about a company like Skype getting bought by Microsoft.

52
00:02:30,180 --> 00:02:34,620
The moment that control gets consolidated, the user experience can change overnight.

53
00:02:34,620 --> 00:02:38,220
Your privacy guarantees can change and there's nothing you can do about it.

54
00:02:38,220 --> 00:02:41,920
Retro share is designed to be stable ground away from all that.

55
00:02:41,920 --> 00:02:43,360
So independence is number one.

56
00:02:43,360 --> 00:02:47,400
What about the other goals like security and free expression?

57
00:02:47,660 --> 00:02:51,800
So goal two is just favoring really strong cryptography and everything you do.

58
00:02:51,800 --> 00:02:55,180
The point is to make your information hidden from, well,

59
00:02:55,180 --> 00:02:57,680
intelligence agencies and big data collecting companies.

60
00:02:57,680 --> 00:03:01,520
And that ties right into goal three, freedom of speech.

61
00:03:01,520 --> 00:03:05,620
I mean, if your forum or your chat group is spread out across

62
00:03:05,620 --> 00:03:09,780
hundreds of user computers, it's censorship resistant by its very design.

63
00:03:09,780 --> 00:03:13,320
There's no single server you can send a takedown notice to.

64
00:03:13,320 --> 00:03:14,760
And this is really important.

65
00:03:14,760 --> 00:03:19,060
The sources stress that it's F.O.S.S. free and open source software.

66
00:03:19,060 --> 00:03:23,260
Why is that so critical for something that promises security?

67
00:03:23,260 --> 00:03:25,660
Because security has to be verifiable.

68
00:03:25,660 --> 00:03:28,700
I mean, if the code is secret, you just have to trust the company

69
00:03:28,700 --> 00:03:30,440
that it's doing what it says it's doing.

70
00:03:30,440 --> 00:03:32,100
That there's no back door. Right.

71
00:03:32,100 --> 00:03:35,380
That it isn't secretly collecting your data with F.O.S.S.

72
00:03:35,380 --> 00:03:37,240
The code is right there out in the open.

73
00:03:37,240 --> 00:03:38,920
Any developer in the world can look at it.

74
00:03:38,920 --> 00:03:42,640
They can check the C++ code and they can verify that the crypto is solid

75
00:03:42,640 --> 00:03:44,520
and the app isn't phoning home.

76
00:03:44,520 --> 00:03:46,020
That transparency. Yeah.

77
00:03:46,020 --> 00:03:48,500
That's the only real foundation for trust.

78
00:03:48,500 --> 00:03:50,860
Okay. So that brings us to the big technical question.

79
00:03:50,860 --> 00:03:55,540
If you get rid of central servers, how do you actually connect people securely?

80
00:03:55,540 --> 00:03:59,900
And that's solved by what they call the friend to friend or F2F topology.

81
00:03:59,900 --> 00:04:02,140
F2F. It sounds simple,

82
00:04:02,140 --> 00:04:05,680
but it's a completely different mindset from what we're used to. Right.

83
00:04:05,680 --> 00:04:08,580
We live in this world where we just log into Google servers.

84
00:04:08,580 --> 00:04:12,720
So break down F2F for us. Okay. Think of it like this.

85
00:04:12,720 --> 00:04:16,780
Normally everyone uses a big public post office to send mail.

86
00:04:16,780 --> 00:04:21,320
In RetroShare, you can only send a letter directly to your verified friends.

87
00:04:21,320 --> 00:04:25,160
You're building a network of individual computers nodes, we call them.

88
00:04:25,160 --> 00:04:27,020
And you run your own node. You run your own node.

89
00:04:27,020 --> 00:04:30,340
And the only people you connect to directly are the people you choose,

90
00:04:30,340 --> 00:04:32,440
the people you trust, and the people you verify.

91
00:04:32,440 --> 00:04:34,900
So it's not some big automatic global thing.

92
00:04:34,900 --> 00:04:38,740
It's more like a secure neighborhood and you're the one handing out the keys.

93
00:04:38,740 --> 00:04:42,180
And that key exchange is done by swapping these RetroShare certificates, right?

94
00:04:42,180 --> 00:04:45,820
Precisely. And here's the crucial security detail.

95
00:04:45,820 --> 00:04:49,380
The actual location of your node, your IP address,

96
00:04:49,380 --> 00:04:53,220
is only known to your direct neighbors, the people you swap certificates with.

97
00:04:53,220 --> 00:04:55,960
So if I'm your friend, I know your IP address.

98
00:04:55,960 --> 00:04:59,420
But my friend, who isn't your friend, has no idea where you are.

99
00:04:59,420 --> 00:05:00,600
None at all.

100
00:05:00,600 --> 00:05:04,540
And that massively increases your privacy compared to a normal PTP system.

101
00:05:04,540 --> 00:05:09,200
That makes the line between who you trust and who you don't crystal clear.

102
00:05:09,200 --> 00:05:13,220
But what if I want to talk to someone beyond my direct friends, a friend of a

103
00:05:13,220 --> 00:05:14,240
friend?

104
00:05:14,240 --> 00:05:18,020
How does the system keep that secure and anonymous?

105
00:05:18,020 --> 00:05:19,980
OK, so that needs two layers of security.

106
00:05:19,980 --> 00:05:22,360
The first layer is authentication.

107
00:05:22,360 --> 00:05:26,620
And that's where you get these strong asymmetric keys in the PGP format.

108
00:05:26,620 --> 00:05:30,100
Think of PGP like your digital passport and your signature all in one.

109
00:05:30,100 --> 00:05:31,860
It guarantees you are who you say you are.

110
00:05:31,860 --> 00:05:33,020
It guarantees that, yes.

111
00:05:33,020 --> 00:05:35,660
It authenticates the link between your two nodes.

112
00:05:35,660 --> 00:05:37,960
OK, so PGP handles identity.

113
00:05:37,960 --> 00:05:40,300
What keeps the data itself secret?

114
00:05:40,300 --> 00:05:41,800
That's later, too.

115
00:05:41,800 --> 00:05:44,900
And that's handled by an open SSL implementation of TLS,

116
00:05:44,900 --> 00:05:46,300
Transport Layer Security.

117
00:05:46,300 --> 00:05:50,340
This basically creates a secure encrypted tunnel between you and your friend.

118
00:05:50,340 --> 00:05:52,940
But the really important detail here is that it uses something called

119
00:05:52,940 --> 00:05:54,580
Perfect Forward Secrecy.

120
00:05:54,580 --> 00:05:56,460
That definitely sounds like a technical buzzword.

121
00:05:56,460 --> 00:05:58,060
What does that mean in simple terms?

122
00:05:58,060 --> 00:06:00,700
It means that if, say, years from now,

123
00:06:00,700 --> 00:06:04,860
someone manages to steal your main private key, your master key,

124
00:06:04,860 --> 00:06:07,900
they still can't go back and decrypt your old conversations.

125
00:06:07,900 --> 00:06:11,740
Because each chat session uses a brand new temporary key

126
00:06:11,740 --> 00:06:13,780
that gets destroyed right after you're done.

127
00:06:13,780 --> 00:06:16,580
So even if someone steals the key to the vault later,

128
00:06:16,580 --> 00:06:19,020
all the old evidence has already been burned.

129
00:06:19,020 --> 00:06:20,940
It protects you from future compromises.

130
00:06:20,940 --> 00:06:21,780
Wow.

131
00:06:21,780 --> 00:06:26,140
So you've got this F2F network with PGP for identity and TLS

132
00:06:26,140 --> 00:06:28,820
with Perfect Forward Secrecy for the encryption.

133
00:06:28,820 --> 00:06:31,740
It's like a mathematically verified web of trust.

134
00:06:31,740 --> 00:06:35,900
It's a closed loop system built for exactly that resilience.

135
00:06:35,900 --> 00:06:38,260
OK, now for the really interesting part,

136
00:06:38,260 --> 00:06:42,340
the actual services running on top of this secure mesh.

137
00:06:42,340 --> 00:06:45,740
Because RetroShare isn't just about security for its own sake,

138
00:06:45,740 --> 00:06:47,980
it's about having tools that can survive

139
00:06:47,980 --> 00:06:49,620
without a central company.

140
00:06:49,620 --> 00:06:51,460
So what can you actually do with it?

141
00:06:51,460 --> 00:06:54,140
Well, because the data transfer is so robust,

142
00:06:54,140 --> 00:06:56,300
it allows for a whole suite of services

143
00:06:56,300 --> 00:06:59,580
that feel familiar but work in a totally different way.

144
00:06:59,580 --> 00:07:01,460
You got your standard instant chat, of course,

145
00:07:01,460 --> 00:07:05,060
for text and images and decentralized chat rooms,

146
00:07:05,060 --> 00:07:06,620
a bit like old-school IRC.

147
00:07:06,620 --> 00:07:08,140
And you can chat with friends of friends too, right?

148
00:07:08,140 --> 00:07:09,700
You can. That's called distant chat,

149
00:07:09,700 --> 00:07:11,420
and it goes through those anonymous tunnels

150
00:07:11,420 --> 00:07:12,540
we were just talking about.

151
00:07:12,540 --> 00:07:15,460
But the mail system, that's what really caught my eye.

152
00:07:15,460 --> 00:07:17,260
If there's no Gmail server,

153
00:07:17,260 --> 00:07:20,100
how does asynchronous mail getting a message

154
00:07:20,100 --> 00:07:22,780
when you're offline, how does that even work?

155
00:07:22,780 --> 00:07:24,540
That is the really clever part.

156
00:07:24,540 --> 00:07:26,380
When you send an encrypted message,

157
00:07:26,380 --> 00:07:28,580
RetroShare doesn't send it to a server.

158
00:07:28,580 --> 00:07:31,380
It securely stores copies of that message

159
00:07:31,380 --> 00:07:32,900
on your friends' nodes.

160
00:07:32,900 --> 00:07:35,200
Wait, so my social network is my mail server.

161
00:07:35,200 --> 00:07:36,040
Exactly.

162
00:07:36,040 --> 00:07:38,420
Your trusted friends act as these temporary,

163
00:07:38,420 --> 00:07:40,340
secure mail relays.

164
00:07:40,340 --> 00:07:42,020
When you finally log back in,

165
00:07:42,020 --> 00:07:43,780
their nodes deliver the messages to you

166
00:07:43,780 --> 00:07:45,420
and then they delete their copies.

167
00:07:45,420 --> 00:07:47,460
It removes that single point of failure.

168
00:07:47,460 --> 00:07:50,340
That's a fascinating way to flip the model on its head.

169
00:07:50,340 --> 00:07:51,540
Okay, what about content?

170
00:07:51,540 --> 00:07:53,500
Like forums, discussions, that kind of thing.

171
00:07:53,500 --> 00:07:54,460
All decentralized.

172
00:07:54,460 --> 00:07:56,420
They have forums where you can actually read

173
00:07:56,420 --> 00:07:58,980
and write posts even when you're completely offline.

174
00:07:58,980 --> 00:08:00,140
Offline. Yup.

175
00:08:00,140 --> 00:08:03,780
Then when you reconnect, RetroShare uses its data sync system,

176
00:08:03,780 --> 00:08:06,100
it's called GXS, to automatically sync up

177
00:08:06,100 --> 00:08:08,300
all the new posts across the network.

178
00:08:08,300 --> 00:08:11,380
And that's why the forums are so censorship resistant.

179
00:08:11,380 --> 00:08:13,420
The content literally lives everywhere.

180
00:08:13,420 --> 00:08:16,300
And this GXS system, that's the big technical jump

181
00:08:16,300 --> 00:08:18,980
from version 0.6 that the source has mentioned, right?

182
00:08:18,980 --> 00:08:21,300
It's the engine that makes it all possible, yeah.

183
00:08:21,300 --> 00:08:24,060
It abstracts how all this authenticated data

184
00:08:24,060 --> 00:08:26,300
gets distributed and synchronized.

185
00:08:26,300 --> 00:08:28,340
It powers the offline forums,

186
00:08:28,340 --> 00:08:31,980
but also things like boards for sharing pictures and links

187
00:08:31,980 --> 00:08:33,700
with voting and comments built in.

188
00:08:33,700 --> 00:08:36,700
And for bigger stuff, like media feeds or files.

189
00:08:36,700 --> 00:08:38,220
For that, you have channels.

190
00:08:38,220 --> 00:08:40,500
Users can publish files, and if you subscribe,

191
00:08:40,500 --> 00:08:42,340
you automatically download the latest content

192
00:08:42,340 --> 00:08:43,580
when you connect.

193
00:08:43,580 --> 00:08:45,900
And then there's the core file sharing,

194
00:08:45,900 --> 00:08:47,580
which uses a swarming technology,

195
00:08:47,580 --> 00:08:49,900
a bit like BitTorrent, to speed things up.

196
00:08:49,900 --> 00:08:52,260
But the key is that all those transfers are routed

197
00:08:52,260 --> 00:08:54,620
through the secure anonymous tunnels

198
00:08:54,620 --> 00:08:55,860
to protect your privacy.

199
00:08:55,860 --> 00:08:57,100
And we should probably mention,

200
00:08:57,100 --> 00:09:00,180
the sources say there is an experimental prototype

201
00:09:00,180 --> 00:09:02,580
for voice and video calls through a plugin.

202
00:09:02,580 --> 00:09:03,700
So it's still growing.

203
00:09:03,700 --> 00:09:05,380
It shows the framework is extensible.

204
00:09:05,380 --> 00:09:06,780
They're always trying to build more

205
00:09:06,780 --> 00:09:08,420
on top of that secure mesh.

206
00:09:08,420 --> 00:09:10,660
Okay, so let's talk about the next level of security.

207
00:09:10,660 --> 00:09:14,500
For people who need maximum operational security,

208
00:09:14,500 --> 00:09:18,020
you mentioned hiding your IP even from your direct friends.

209
00:09:18,020 --> 00:09:19,580
How does RetroShare do that?

210
00:09:19,580 --> 00:09:20,780
This is where it can integrate

211
00:09:20,780 --> 00:09:22,900
with networks like Tor and ITP.

212
00:09:22,900 --> 00:09:26,500
You can choose to tunnel your entire RetroShare connection

213
00:09:26,500 --> 00:09:27,820
through one of those services.

214
00:09:27,820 --> 00:09:29,700
And what does that do, exactly?

215
00:09:29,700 --> 00:09:33,100
The significance is that if you're using Tor, for example,

216
00:09:33,100 --> 00:09:34,780
even your direct friend nodes

217
00:09:34,780 --> 00:09:36,940
can't see your real IP address.

218
00:09:36,940 --> 00:09:39,980
All they see is an exit node from the Tor network.

219
00:09:39,980 --> 00:09:41,240
That seems critical,

220
00:09:41,240 --> 00:09:42,660
especially if you're connecting with people

221
00:09:42,660 --> 00:09:44,380
you don't know perfectly well,

222
00:09:44,380 --> 00:09:47,020
or if you're in a place with heavy surveillance.

223
00:09:47,020 --> 00:09:49,300
Absolutely, and the developers know

224
00:09:49,300 --> 00:09:50,640
that can be tricky to set up.

225
00:09:50,640 --> 00:09:52,820
So they provide specific builds of RetroShare

226
00:09:52,820 --> 00:09:55,900
that have Tor embedded and managed automatically.

227
00:09:55,900 --> 00:09:57,820
It just lowers that technical barrier

228
00:09:57,820 --> 00:09:59,160
to getting high security.

229
00:09:59,160 --> 00:10:02,420
So we've got the why, the how, the what.

230
00:10:02,420 --> 00:10:04,860
It honestly sounds like a digital utopian dream.

231
00:10:04,860 --> 00:10:07,020
It's free, it's secure, it's open source,

232
00:10:07,020 --> 00:10:08,220
it's censorship resistant.

233
00:10:08,220 --> 00:10:11,460
So I have to ask the classic question, what's the catch?

234
00:10:11,460 --> 00:10:13,900
And it's important to be really clear here.

235
00:10:13,900 --> 00:10:15,340
There is no monetary catch.

236
00:10:15,340 --> 00:10:17,860
It's free software, no ads, no hidden costs,

237
00:10:17,860 --> 00:10:19,420
no profit motive.

238
00:10:19,420 --> 00:10:21,900
The catch is entirely social.

239
00:10:21,900 --> 00:10:22,740
Which is?

240
00:10:22,740 --> 00:10:23,900
You have to build your own network.

241
00:10:23,900 --> 00:10:26,780
RetroShare doesn't come with a billion users already on it.

242
00:10:26,780 --> 00:10:28,540
You have to go out and recruit your friends,

243
00:10:28,540 --> 00:10:29,700
convince them to install it,

244
00:10:29,700 --> 00:10:32,020
and then you have to exchange those digital certificates.

245
00:10:32,020 --> 00:10:33,860
It takes real effort.

246
00:10:33,860 --> 00:10:35,500
So the friction isn't the technology,

247
00:10:35,500 --> 00:10:37,220
it's the social commitment.

248
00:10:37,220 --> 00:10:38,940
Instead of paying with your data,

249
00:10:38,940 --> 00:10:41,180
you're paying with your time and initiative.

250
00:10:41,180 --> 00:10:43,100
That's a powerful difference.

251
00:10:43,100 --> 00:10:45,860
It's a price of real digital independence.

252
00:10:45,860 --> 00:10:47,960
Let's touch on the history for a second.

253
00:10:47,960 --> 00:10:49,940
The project was started by a developer,

254
00:10:49,940 --> 00:10:52,820
Dubob, way back in 2006.

255
00:10:52,820 --> 00:10:54,580
I mean, that's ancient in internet years.

256
00:10:54,580 --> 00:10:55,220
It really is.

257
00:10:55,220 --> 00:10:57,060
It speaks to its staying power.

258
00:10:57,060 --> 00:10:59,500
And that long history allowed for that big evolution

259
00:10:59,500 --> 00:11:02,660
we mentioned, version 0.6 with the GXS system.

260
00:11:02,660 --> 00:11:04,380
That wasn't just adding features,

261
00:11:04,380 --> 00:11:07,380
it was completely standardizing how this distributed data gets

262
00:11:07,380 --> 00:11:10,340
handled, which made things like the asynchronous mail

263
00:11:10,340 --> 00:11:12,380
and the resilient forms even possible.

264
00:11:12,380 --> 00:11:14,980
So for our listeners who really appreciate the goals here,

265
00:11:14,980 --> 00:11:17,540
this kind of censorship evading tech,

266
00:11:17,540 --> 00:11:19,260
how can they get involved?

267
00:11:19,260 --> 00:11:21,980
There are a bunch of ways, and the sources lay them out.

268
00:11:21,980 --> 00:11:24,500
The simplest is to just tackle that social catch

269
00:11:24,500 --> 00:11:25,540
we talked about.

270
00:11:25,540 --> 00:11:27,900
Spread the word, invite your friends.

271
00:11:27,900 --> 00:11:29,580
On a non-technical level, you can

272
00:11:29,580 --> 00:11:31,820
help translate RetroShare into other languages,

273
00:11:31,820 --> 00:11:33,740
or just report bugs when you find them.

274
00:11:33,740 --> 00:11:37,540
And for anyone listening with some C++ or QMake skills who

275
00:11:37,540 --> 00:11:38,900
wants to get their hands dirty.

276
00:11:38,900 --> 00:11:40,660
Oh, they're explicitly welcomed.

277
00:11:40,660 --> 00:11:44,180
The sources say you can create patches, submit poll requests.

278
00:11:44,180 --> 00:11:46,500
A platform like this needs constant work,

279
00:11:46,500 --> 00:11:49,140
and the community benefits from every single developer who

280
00:11:49,140 --> 00:11:51,860
shares that vision of digital sovereignty.

281
00:11:51,860 --> 00:11:53,580
So looking back on this doom dive,

282
00:11:53,580 --> 00:11:55,580
the key takeaways for me are pretty clear.

283
00:11:55,580 --> 00:12:00,100
RetroShare is F-O-S-S. It's built on a secure F2F network

284
00:12:00,100 --> 00:12:03,940
using PGP and TLS with perfect forward secrecy.

285
00:12:03,940 --> 00:12:06,180
It enables these incredibly resilient services

286
00:12:06,180 --> 00:12:10,180
like forums and mail by storing data on friends' nodes,

287
00:12:10,180 --> 00:12:11,580
not a central server.

288
00:12:11,580 --> 00:12:15,420
And it has optional high level anonymity through Tor and I2P.

289
00:12:15,420 --> 00:12:17,380
It's a platform driven purely by the goals

290
00:12:17,380 --> 00:12:18,980
of security and freedom.

291
00:12:18,980 --> 00:12:21,800
It's a genuine alternative, but only if you're

292
00:12:21,800 --> 00:12:23,500
willing to put in the work.

293
00:12:23,500 --> 00:12:26,820
And that really leaves us with our final provocative thought.

294
00:12:26,820 --> 00:12:28,780
The biggest barrier to truly secure

295
00:12:28,780 --> 00:12:32,020
decentralized communication isn't the technology.

296
00:12:32,020 --> 00:12:35,740
It's the social effort required to build your trusted network.

297
00:12:35,740 --> 00:12:37,980
So if digital sovereignty is the prize,

298
00:12:37,980 --> 00:12:41,020
how much work are you actually willing to put in to get it?

299
00:12:41,020 --> 00:12:43,580
Thank you so much for joining us for this deep dive

300
00:12:43,580 --> 00:12:44,940
into RetroShare.

301
00:12:44,940 --> 00:12:47,260
And a final thank you to our supporter, Safe Server,

302
00:12:47,260 --> 00:12:48,700
for making this possible.

303
00:12:48,700 --> 00:12:50,580
You can find out how they can help with your hosting

304
00:12:50,580 --> 00:12:55,220
and digital transformation needs at www.safe-server.de.

305
00:12:55,220 --> 00:12:57,740
Keep exploring these concepts of digital sovereignty.

306
00:12:57,740 --> 00:12:59,540
We'll catch you on the next deep dive.