1
00:00:00,000 --> 00:00:04,630
Welcome back to the deep dive where we take the complicated and well try and make

2
00:00:04,630 --> 00:00:05,120
it concise

3
00:00:05,120 --> 00:00:09,890
Insightful and honestly a lot of fun. I think we succeed most of the time. I hope

4
00:00:09,890 --> 00:00:10,080
so

5
00:00:10,080 --> 00:00:14,920
Today we're strapping in for a deep dive that really addresses a question

6
00:00:14,920 --> 00:00:19,850
I think we all grapple with who actually owns the stuff you create and post online,

7
00:00:19,850 --> 00:00:20,400
right?

8
00:00:20,400 --> 00:00:24,610
It's a huge question and we're gonna be moving beyond those, you know, the

9
00:00:24,610 --> 00:00:26,000
traditional social media silos

10
00:00:26,280 --> 00:00:29,920
We're exploring a platform that's designed specifically to put true content

11
00:00:29,920 --> 00:00:31,360
ownership back in your hands

12
00:00:31,360 --> 00:00:35,840
That's it. Exactly. Our mission today is to give you a really beginner-friendly

13
00:00:35,840 --> 00:00:40,610
Accessible entry point into understanding decentralized publishing and we're doing

14
00:00:40,610 --> 00:00:43,360
that by looking at a specific tool, right?

15
00:00:43,360 --> 00:00:48,130
We are it's an open source tool called known and it's more than just software

16
00:00:48,130 --> 00:00:48,440
really

17
00:00:48,440 --> 00:00:52,650
It's a social publishing platform that actively tries to deliver on that old

18
00:00:52,650 --> 00:00:54,680
promise of the open web the one we all hope for

19
00:00:54,680 --> 00:00:56,780
yeah flexible user controlled and

20
00:00:56,780 --> 00:01:01,720
Completely sovereign. We want to make sure you walk away with a crystal-clear idea

21
00:01:01,720 --> 00:01:03,720
of not just what it is

22
00:01:03,720 --> 00:01:07,890
But why it matters and before we dive into the you know, the fundamental

23
00:01:07,890 --> 00:01:09,840
architecture of this open web challenger

24
00:01:09,840 --> 00:01:14,960
We do want to acknowledge the support that makes this deep dive possible

25
00:01:14,960 --> 00:01:19,410
Absolutely, this whole exploration of digital sovereignty and content ownership is

26
00:01:19,410 --> 00:01:20,720
supported by safe server

27
00:01:20,720 --> 00:01:25,490
They focus on hosting and supporting your digital transformation, which is I mean a

28
00:01:25,490 --> 00:01:27,680
perfect fit for today's topic

29
00:01:27,680 --> 00:01:31,900
It really is they make sure you have the robust infrastructure you need to truly

30
00:01:31,900 --> 00:01:33,160
own your space online

31
00:01:33,160 --> 00:01:36,120
They're a dedicated host for software just like known

32
00:01:36,120 --> 00:01:40,280
So if you're looking to take control of your digital future, you can find out more

33
00:01:40,280 --> 00:01:40,280
at

34
00:01:40,280 --> 00:01:42,880
www.safeserver.de

35
00:01:42,880 --> 00:01:44,900
great

36
00:01:44,900 --> 00:01:48,320
Fantastic. Okay, let's untack this our sources today are

37
00:01:48,840 --> 00:01:52,760
drawn straight from the platform's official documentation and feature lists right

38
00:01:52,760 --> 00:01:55,720
from the horse's mouth exactly the true DNA of the project

39
00:01:55,720 --> 00:02:00,020
Which gives us a clear picture of what known is designed to do and how it actually

40
00:02:00,020 --> 00:02:01,680
works for an everyday person

41
00:02:01,680 --> 00:02:07,450
Okay, let's start at the top the philosophy right the documentation calls known and

42
00:02:07,450 --> 00:02:09,920
open publishing platform and a social

43
00:02:09,920 --> 00:02:15,490
Publishing platform and then it makes this bold almost revolutionary statement. It

44
00:02:15,490 --> 00:02:17,600
says this is really how the web should be

45
00:02:17,640 --> 00:02:21,850
It's a huge claim and it immediately sets up a conflict doesn't it does because we

46
00:02:21,850 --> 00:02:24,220
associate social with you know

47
00:02:24,220 --> 00:02:29,420
Facebook or Instagram where the company owns the feed the algorithm everything it

48
00:02:29,420 --> 00:02:31,840
absolutely does and the core identity here is

49
00:02:31,840 --> 00:02:36,840
Bridging that gap between convenience and sovereignty. We're always told we have to

50
00:02:36,840 --> 00:02:37,120
choose

51
00:02:37,120 --> 00:02:41,330
You can have the easy sharing of a walled garden like X or you can have the

52
00:02:41,330 --> 00:02:42,800
technical headache of self-hosting

53
00:02:43,200 --> 00:02:47,660
Exactly and known basically says no you can have the ease of use and control your

54
00:02:47,660 --> 00:02:48,080
data

55
00:02:48,080 --> 00:02:52,290
The platform is designed to do all those everyday social things sharing photos

56
00:02:52,290 --> 00:02:53,360
notes updates stuff

57
00:02:53,360 --> 00:02:57,040
We do now all of it, but because you own the installation you own the

58
00:02:57,040 --> 00:02:58,200
infrastructure

59
00:02:58,200 --> 00:03:02,410
So the source is really really lean into the simplicity angle. It's built for

60
00:03:02,410 --> 00:03:03,700
simple publishing

61
00:03:03,700 --> 00:03:07,700
It lets users create and share photos notes stories songs and more

62
00:03:08,160 --> 00:03:12,530
For someone who might be a little wary of self-hosting how does known make sure

63
00:03:12,530 --> 00:03:15,760
that interface is truly friendly and not I don't know

64
00:03:15,760 --> 00:03:19,480
Not like you're managing a database and that's a crucial distinction. It's a real

65
00:03:19,480 --> 00:03:22,760
fear people have known tackles that perceived

66
00:03:22,760 --> 00:03:27,830
Complexity with accessibility just baked right into the design. Okay, the interface

67
00:03:27,830 --> 00:03:28,800
is fully responsive

68
00:03:28,800 --> 00:03:33,570
Which means it works fluidly on any device. The goal is to make managing your

69
00:03:33,570 --> 00:03:35,320
content feel, you know

70
00:03:35,840 --> 00:03:39,520
Instantaneous regardless of where you are that accessibility is crucial, but let's

71
00:03:39,520 --> 00:03:40,160
be realistic

72
00:03:40,160 --> 00:03:42,800
I mean responsive design is pretty standard now true

73
00:03:42,800 --> 00:03:47,580
What specifically makes knowns mobile experience feel less constrained than say

74
00:03:47,580 --> 00:03:50,800
trying to manage a full-scale WordPress blog from your phone?

75
00:03:50,800 --> 00:03:55,710
Yeah, which can be a nightmare. It can be the key is what you could call context-aware

76
00:03:55,710 --> 00:03:57,280
publishing is designed around

77
00:03:57,280 --> 00:04:02,500
Microformats these small specific content types. So like if I post a photo it knows

78
00:04:02,500 --> 00:04:03,440
I'm posting a photo

79
00:04:03,960 --> 00:04:08,870
Exactly, when you post a photo it knows you want photo metadata when you post a

80
00:04:08,870 --> 00:04:09,280
note

81
00:04:09,280 --> 00:04:11,280
It knows you just need a simple text field

82
00:04:11,280 --> 00:04:16,850
this is why you can view edit and post whether you are sharing a sunset picture

83
00:04:16,850 --> 00:04:17,840
from the beach or

84
00:04:17,840 --> 00:04:22,340
Blogging from the road. I see the system is built to eliminate those location or

85
00:04:22,340 --> 00:04:25,180
device constraints that you get with traditional web publishing

86
00:04:25,180 --> 00:04:29,810
It gives you the same flexibility as a dedicated mobile app, but without handing

87
00:04:29,810 --> 00:04:31,120
over the keys to your data

88
00:04:31,120 --> 00:04:35,500
That's the punchline. That makes perfect sense. The simplicity is about reducing

89
00:04:35,500 --> 00:04:35,720
the

90
00:04:35,720 --> 00:04:38,600
The cognitive load on the user

91
00:04:38,600 --> 00:04:38,960
Yeah

92
00:04:38,960 --> 00:04:43,120
The platform helps you more easily organize all your digital info in one place

93
00:04:43,120 --> 00:04:45,600
because everything is structured from the moment you hit publish

94
00:04:45,600 --> 00:04:50,960
Precisely the key insight for you. The learner is that knowns design philosophy

95
00:04:50,960 --> 00:04:55,730
Let's you regain ownership without sacrificing that immediacy and accessibility you've

96
00:04:55,730 --> 00:04:57,520
come to expect from social media

97
00:04:57,520 --> 00:04:59,520
Okay, here's where it gets really interesting for me

98
00:04:59,520 --> 00:05:03,730
Let's dive into the essential features because this is where known directly

99
00:05:03,730 --> 00:05:04,720
challenges the functionality

100
00:05:04,720 --> 00:05:08,160
We rely on every day in those big social silos, right?

101
00:05:08,160 --> 00:05:12,160
What are the tools that actually make it usable exactly what makes it simple and

102
00:05:12,160 --> 00:05:15,200
fast enough to genuinely compete with a dedicated app?

103
00:05:15,200 --> 00:05:19,970
Okay, let's start with reducing friction. They offer a simple but really powerful

104
00:05:19,970 --> 00:05:22,760
tool called the bookmark lit a bookmark lit

105
00:05:22,760 --> 00:05:26,120
Okay, it's a small browser tool. Basically a piece of JavaScript

106
00:05:26,120 --> 00:05:30,860
You just drag to your bookmarks bar that lets you easily post links save content

107
00:05:30,860 --> 00:05:33,120
and even respond to comments from any page on the web

108
00:05:33,120 --> 00:05:33,680
Oh, wow

109
00:05:33,680 --> 00:05:37,680
So you don't have to navigate back to your known site to share something you just

110
00:05:37,680 --> 00:05:39,040
found not at all

111
00:05:39,040 --> 00:05:43,340
It removes that step completely that immediately addresses the ease of use factor

112
00:05:43,340 --> 00:05:46,240
for curating content and for organization

113
00:05:46,240 --> 00:05:49,180
I see you can use hashtag tags just like we're used to yep

114
00:05:49,180 --> 00:05:53,240
hashtags with any content to categorize and organize what you publish and

115
00:05:53,360 --> 00:05:58,730
That organization ties directly back into control how so well for content creation

116
00:05:58,730 --> 00:05:59,240
itself

117
00:05:59,240 --> 00:06:03,200
Known acknowledges that users have different needs you have a choice

118
00:06:03,200 --> 00:06:08,180
You can handcraft your posts in HTML if you want absolute pixel perfect control for

119
00:06:08,180 --> 00:06:10,320
the power users for the power users

120
00:06:10,320 --> 00:06:16,000
Or you can opt for maximum convenience with the wise. I we G editor the

121
00:06:16,000 --> 00:06:21,920
What you see is what you get rich text editor. So it's that duality again

122
00:06:21,920 --> 00:06:26,170
It's a microcosm of knowns philosophy. Mm-hmm control when you wanted simplicity

123
00:06:26,170 --> 00:06:27,640
when you need it and this flexibility

124
00:06:27,640 --> 00:06:32,640
Extends pretty significantly into ownership, which again is the whole point of this

125
00:06:32,640 --> 00:06:33,120
deep dive

126
00:06:33,120 --> 00:06:37,760
Let's talk about the features that define that sovereignty the custom URL

127
00:06:37,760 --> 00:06:42,040
That has to be the foundation, right? Absolutely when you're on a centralized

128
00:06:42,040 --> 00:06:42,440
service

129
00:06:42,440 --> 00:06:45,850
You're essentially just renting space right if that service disappears or if it

130
00:06:45,850 --> 00:06:47,960
changes its terms your content is at risk

131
00:06:48,400 --> 00:06:53,550
Known explicitly gives you the power to bring your own URL and really own your site

132
00:06:53,550 --> 00:06:54,920
with a custom domain

133
00:06:54,920 --> 00:06:58,320
So you are the landlord not the tenant. That's the perfect analogy

134
00:06:58,320 --> 00:07:02,180
It's the single greatest assurance against archival risk and you know changing

135
00:07:02,180 --> 00:07:05,440
terms of service and beyond just the domain control also means control

136
00:07:05,440 --> 00:07:10,670
Over who sees what you post correct privacy is paramount and known builds that

137
00:07:10,670 --> 00:07:12,520
granularity right into the system

138
00:07:12,520 --> 00:07:15,240
You have the ability to keep your entire site private

139
00:07:15,240 --> 00:07:19,160
Which would be perfect for what personal thoughts or a private group discussion as

140
00:07:19,160 --> 00:07:19,680
the docs say?

141
00:07:19,680 --> 00:07:24,680
Exactly, you can use it as a digital diary that no one else sees or as a secure

142
00:07:24,680 --> 00:07:26,400
communication hub for a small team

143
00:07:26,400 --> 00:07:30,810
And what if you were building something bigger like a community project or a

144
00:07:30,810 --> 00:07:32,080
collaborative blog?

145
00:07:32,080 --> 00:07:36,080
Then the multi-author feature scales your sovereignty

146
00:07:36,080 --> 00:07:41,130
You can invite an unlimited number of collaborators to a multi-user site, but you

147
00:07:41,130 --> 00:07:42,120
still own the root

148
00:07:42,360 --> 00:07:46,280
URL you still own it, but you allow others to contribute seamlessly

149
00:07:46,280 --> 00:07:52,820
This shows known is built not just for the individual but for these small self-governing

150
00:07:52,820 --> 00:07:53,720
communities

151
00:07:53,720 --> 00:07:57,360
Okay. Finally, let's talk about the feedback loop. We are so used to instant

152
00:07:57,360 --> 00:07:58,480
notifications on apps

153
00:07:58,480 --> 00:08:02,040
How does known make sure you don't miss out on interaction when your content is

154
00:08:02,040 --> 00:08:02,840
decentralized?

155
00:08:02,840 --> 00:08:07,750
It ensures robust connectivity through comprehensive feed formats. Your content is

156
00:08:07,750 --> 00:08:10,120
accessible via RSS XML

157
00:08:10,540 --> 00:08:14,040
JSON or KML. Okay. Those are a lot of acronyms. They are

158
00:08:14,040 --> 00:08:18,180
But they're just different ways machines and services can consume your data

159
00:08:18,180 --> 00:08:24,010
RSS and XML are great for traditional readers, but JSON is super fast and efficient

160
00:08:24,010 --> 00:08:26,120
for machine-to-machine updates

161
00:08:26,120 --> 00:08:31,200
But wait a second. Why would a social publishing platform need KML specifically?

162
00:08:31,200 --> 00:08:35,410
That's usually for geographical data for maps. That is a fascinating detail in the

163
00:08:35,410 --> 00:08:36,800
source documentation, isn't it?

164
00:08:36,800 --> 00:08:41,400
It is. Yeah. What does that tell us about their broader ambition? Well, KML stands

165
00:08:41,400 --> 00:08:43,060
for keyhole markup language

166
00:08:43,060 --> 00:08:47,300
And it's used for encoding location data for programs like Google Earth. Its

167
00:08:47,300 --> 00:08:49,860
inclusion suggests that known is

168
00:08:49,860 --> 00:08:54,630
Anticipating and supporting location-based posts. Like that sunset picture from the

169
00:08:54,630 --> 00:08:55,920
beach. Exactly.

170
00:08:55,920 --> 00:09:00,080
And ensuring that location data is also owned, organized, and available for

171
00:09:00,080 --> 00:09:02,520
consumption by specialized mapping services

172
00:09:02,520 --> 00:09:06,100
Rather than being locked into some proprietary systems location tag.

173
00:09:06,100 --> 00:09:10,310
It just expands the definition of what content actually means. You really don't.

174
00:09:10,310 --> 00:09:12,440
That attention to detail is pretty insightful plus

175
00:09:12,440 --> 00:09:15,690
I see they still support email notifications, so you get updated when someone

176
00:09:15,690 --> 00:09:17,060
responds. You still get that familiar

177
00:09:17,060 --> 00:09:21,270
immediate feedback loop. So at the end of the day you have the flexibility of an

178
00:09:21,270 --> 00:09:21,960
app, the

179
00:09:21,960 --> 00:09:26,910
customization of a blog, and the ownership of your own server. Let's transition now

180
00:09:26,910 --> 00:09:29,800
to the foundational element that makes known truly unique.

181
00:09:29,800 --> 00:09:35,080
What's fascinating here is its connection to the decentralized IndieWeb movement.

182
00:09:35,360 --> 00:09:40,270
Now for a beginner, that term sounds like a massive technical hurdle, but at its

183
00:09:40,270 --> 00:09:42,960
heart, it's really just a protocol for

184
00:09:42,960 --> 00:09:47,730
polite digital conversation, isn't it? That's a great way to put it. It is a

185
00:09:47,730 --> 00:09:50,760
philosophical leap that requires technical support,

186
00:09:50,760 --> 00:09:55,530
but we can simplify the core idea. Please do. If we connect this to the bigger

187
00:09:55,530 --> 00:09:55,920
picture,

188
00:09:55,920 --> 00:09:58,720
the IndieWeb is about breaking down the silos.

189
00:09:58,720 --> 00:10:00,240
Think of it like email.

190
00:10:00,240 --> 00:10:05,360
You can send a message from Gmail and I can read it on Outlook or a private server.

191
00:10:05,360 --> 00:10:05,400
And it just works.

192
00:10:05,400 --> 00:10:07,340
The communication is federated. Exactly.

193
00:10:07,340 --> 00:10:10,840
It doesn't need a single intermediary to function. And the current social web is

194
00:10:10,840 --> 00:10:13,760
the total opposite of that. If I post a photo on Instagram,

195
00:10:13,760 --> 00:10:18,300
it lives and dies on Instagram. Exactly. Your platform acts as a gatekeeper.

196
00:10:18,300 --> 00:10:24,340
The IndieWeb philosophy, which NONE is built on, is that sites running these

197
00:10:24,340 --> 00:10:27,040
compatible platforms can respond to each other,

198
00:10:27,800 --> 00:10:32,240
bookmark each other's content, and leave comments on each other's posts directly.

199
00:10:32,240 --> 00:10:35,670
So instead of logging into five different corporate platforms to interact, my

200
00:10:35,670 --> 00:10:37,960
personal site becomes the hub.

201
00:10:37,960 --> 00:10:42,380
Your personal site is the hub, communicating directly with other people's personal

202
00:10:42,380 --> 00:10:42,800
sites.

203
00:10:42,800 --> 00:10:47,840
It is true peer-to-peer social interaction. It sounds like taking the best parts of

204
00:10:47,840 --> 00:10:48,200
early

205
00:10:48,200 --> 00:10:53,150
conversational blogging and injecting modern social connectivity, all while cutting

206
00:10:53,150 --> 00:10:54,960
out the corporate middleman.

207
00:10:54,960 --> 00:10:59,180
That's the perfect summary. It decentralizes the social graph, making sure that the

208
00:10:59,180 --> 00:11:02,240
relationships between users are maintained by the users themselves.

209
00:11:02,240 --> 00:11:06,370
Okay, so if someone listening is inspired by this movement and wants to get started,

210
00:11:06,370 --> 00:11:08,800
the technology can sometimes be intimidating?

211
00:11:08,800 --> 00:11:09,720
It can be, yeah.

212
00:11:09,720 --> 00:11:13,930
Are there beginner-friendly installation paths, or is this strictly for people who

213
00:11:13,930 --> 00:11:15,600
enjoy writing code on weekends?

214
00:11:15,600 --> 00:11:20,070
The good news is, getting started isn't nearly as hard as it sounds, which is a

215
00:11:20,070 --> 00:11:22,400
major victory for the platform.

216
00:11:22,920 --> 00:11:28,360
The sources outline a very clear path for beginners, emphasizing one-click sites.

217
00:11:28,360 --> 00:11:29,560
One-click sites.

218
00:11:29,560 --> 00:11:30,060
Yep.

219
00:11:30,060 --> 00:11:36,150
Known to work seamlessly on hosts like Reclaim Hosting and Dream Host, which often

220
00:11:36,150 --> 00:11:39,840
include these pre-packaged one-click installation features.

221
00:11:39,840 --> 00:11:42,520
So the technical barrier basically disappears?

222
00:11:42,520 --> 00:11:46,020
For most people, yes. You install it the way you'd install a basic app on your

223
00:11:46,020 --> 00:11:46,520
phone.

224
00:11:46,520 --> 00:11:48,520
Okay, that removes the setup nightmare.

225
00:11:48,520 --> 00:11:52,810
But for those who are curious, or who might be considering self-hosting for maximum

226
00:11:52,810 --> 00:11:56,120
control, what are the basic technical requirements, just for context?

227
00:11:56,120 --> 00:11:59,560
Right, for the self-hosters among you, it's important to know.

228
00:11:59,560 --> 00:12:02,920
Known is under active development, so it needs a modern server environment.

229
00:12:02,920 --> 00:12:03,720
Which means?

230
00:12:03,720 --> 00:12:09,440
It requires PHP 8.1 or newer, with a few extensions, along with a supported

231
00:12:09,440 --> 00:12:11,160
database like MySQL.

232
00:12:11,160 --> 00:12:15,370
And importantly, if you're managing dependencies like installing new features or

233
00:12:15,370 --> 00:12:18,440
updating the platform, you'll be using a tool called Composer.

234
00:12:18,440 --> 00:12:20,920
What exactly is Composer in this context?

235
00:12:20,920 --> 00:12:25,960
Composer is the standard package and dependency manager in the PHP world.

236
00:12:25,960 --> 00:12:30,190
It's what tells the known installation what other pieces of software it needs to

237
00:12:30,190 --> 00:12:31,000
function.

238
00:12:31,000 --> 00:12:34,600
Mentioning it just shows that this is a professional modern project.

239
00:12:34,600 --> 00:12:39,580
And because this is an open source project, licensed under the Apache Software License

240
00:12:39,580 --> 00:12:40,280
2.0,

241
00:12:40,280 --> 00:12:43,080
that ability to collaborate is open to everyone, right?

242
00:12:43,080 --> 00:12:44,120
Absolutely.

243
00:12:44,120 --> 00:12:48,330
The Apache License means it's fully open source, you can use it, modify it,

244
00:12:48,330 --> 00:12:49,960
distribute your own modifications.

245
00:12:49,960 --> 00:12:52,920
And this active community is key to its development.

246
00:12:52,920 --> 00:12:55,320
You can see that through the open support channels.

247
00:12:55,320 --> 00:12:56,200
You can.

248
00:12:56,200 --> 00:13:00,360
Things like the known dev mailing list and the IRC channel, hashtag knownchat on

249
00:13:00,360 --> 00:13:00,920
freenode.

250
00:13:00,920 --> 00:13:02,520
This isn't some abandoned project.

251
00:13:02,520 --> 00:13:05,560
It's a vibrant community pushing the platform forward.

252
00:13:05,560 --> 00:13:09,060
And even for users who are already up and running, there's still room for advanced

253
00:13:09,060 --> 00:13:10,120
customization.

254
00:13:10,120 --> 00:13:12,920
The sources mention custom JavaScript and CSS.

255
00:13:12,920 --> 00:13:16,520
I assume that's how you can fundamentally change the site's look and feel.

256
00:13:16,520 --> 00:13:17,240
Precisely.

257
00:13:17,240 --> 00:13:20,360
Or add your own analytics trackers without asking for permission.

258
00:13:20,360 --> 00:13:23,160
Gives you maximum flexibility to tailor the experience.

259
00:13:23,160 --> 00:13:26,520
You are not bound by themes or templates imposed by the platform.

260
00:13:26,520 --> 00:13:28,440
You control the front end entirely.

261
00:13:28,440 --> 00:13:30,200
And to connect this back to the bigger picture.

262
00:13:30,200 --> 00:13:33,880
Known has over a thousand stars on GitHub.

263
00:13:33,880 --> 00:13:35,400
It has continuous releases.

264
00:13:35,400 --> 00:13:39,320
It reflects a vibrant, sustained community.

265
00:13:39,320 --> 00:13:42,440
It's a serious player in the decentralized web movement.

266
00:13:42,440 --> 00:13:45,000
So what does this all mean for you, the learner?

267
00:13:45,000 --> 00:13:48,920
We've covered the philosophy, the features, and the technical backbone.

268
00:13:48,920 --> 00:13:49,560
That's a lot.

269
00:13:49,560 --> 00:13:50,360
It is.

270
00:13:50,360 --> 00:13:55,130
But Known is a powerful, flexible, open source tool for anyone who's serious about

271
00:13:55,130 --> 00:13:56,360
owning their content.

272
00:13:56,360 --> 00:14:00,360
It offers simple, responsive publishing alongside deep control.

273
00:14:00,360 --> 00:14:05,160
That control comes from custom URLs, granular privacy settings,

274
00:14:05,160 --> 00:14:09,640
and the ability to seamlessly integrate into that broader decentralized Indie web.

275
00:14:09,640 --> 00:14:13,250
It means that the choice you face today isn't between a slick platform and a clumsy

276
00:14:13,250 --> 00:14:13,640
one?

277
00:14:13,640 --> 00:14:14,600
No, not anymore.

278
00:14:14,600 --> 00:14:17,930
It's between a platform that owns your data and one that gives you the tools to

279
00:14:17,930 --> 00:14:19,000
host and own it yourself.

280
00:14:19,000 --> 00:14:23,610
Known is a working example of a movement that says your thoughts, photos, and

281
00:14:23,610 --> 00:14:25,000
stories belong to you.

282
00:14:25,000 --> 00:14:26,680
Not to a corporation's server farm.

283
00:14:26,680 --> 00:14:27,640
Exactly.

284
00:14:27,640 --> 00:14:30,600
And that ownership doesn't have to mean technical paralysis.

285
00:14:30,600 --> 00:14:34,870
And as we wrap up this deep dive, that raises a really important question for you

286
00:14:34,870 --> 00:14:35,480
to consider.

287
00:14:36,120 --> 00:14:41,480
If the web should be fully open and tools like Known exist to make that possible

288
00:14:41,480 --> 00:14:42,120
without being

289
00:14:42,120 --> 00:14:47,130
a programming genius, what future advancements or feature conveniences would it

290
00:14:47,130 --> 00:14:47,560
take for the

291
00:14:47,560 --> 00:14:52,330
majority of users to abandon the ease of the walled garden and commit to content

292
00:14:52,330 --> 00:14:53,240
ownership?

293
00:14:53,240 --> 00:14:54,680
That's the million dollar question.

294
00:14:54,680 --> 00:14:59,080
Is the convenience of that corporate lease agreement truly worth forfeiting control

295
00:14:59,080 --> 00:14:59,320
over

296
00:14:59,320 --> 00:15:01,080
your entire digital archive?

297
00:15:01,080 --> 00:15:05,640
Something certainly to mull over as you browse your favorite social feeds today?

298
00:15:05,640 --> 00:15:06,360
Definitely.

299
00:15:06,360 --> 00:15:10,520
This deep dive into open publishing and content ownership was brought to you by

300
00:15:10,520 --> 00:15:11,160
Safe Server.

301
00:15:11,160 --> 00:15:14,990
They help with hosting and digital transformation, so find out more about how they

302
00:15:14,990 --> 00:15:15,800
can support your

303
00:15:15,800 --> 00:15:19,960
shift to digital ownership at www.safeserver.de.

304
00:15:19,960 --> 00:15:21,640
Thank you for joining us for the deep dive.

305
00:15:21,640 --> 00:15:22,520
We'll see you next time.