1
00:00:00,000 --> 00:00:01,560
Welcome to the Deep Dive.

2
00:00:01,560 --> 00:00:04,960
We're the show that tackles those dense tech docs,

3
00:00:04,960 --> 00:00:07,040
research notes, all that complex stuff,

4
00:00:07,040 --> 00:00:09,640
and basically gives you the shortcut to understanding it.

5
00:00:09,640 --> 00:00:12,520
Today, we're digging into a really fascinating corner

6
00:00:12,520 --> 00:00:13,840
of consumer tech.

7
00:00:13,840 --> 00:00:17,280
What happens when you decide you want real control,

8
00:00:17,280 --> 00:00:20,680
open source control, over hardware you already own?

9
00:00:20,680 --> 00:00:22,940
Specifically, IP cameras.

10
00:00:22,940 --> 00:00:24,680
Yeah, it's a great topic, taking back control.

11
00:00:24,680 --> 00:00:25,720
Exactly.

12
00:00:25,720 --> 00:00:29,720
We're focusing on Thangino, that's T-H-I-N-G-I-N-O,

13
00:00:29,720 --> 00:00:31,800
an open source firmware project.

14
00:00:31,800 --> 00:00:33,680
And before we jump right in, I have a quick shout out

15
00:00:33,680 --> 00:00:36,380
to Safe Server for supporting this deep dive.

16
00:00:36,380 --> 00:00:38,760
Safe Server handles hosting for projects like this

17
00:00:38,760 --> 00:00:41,480
and can support you in your digital transformation.

18
00:00:41,480 --> 00:00:45,400
Check them out at www.safeserver.de.

19
00:00:45,400 --> 00:00:47,160
Good support is crucial for this kind of thing.

20
00:00:47,160 --> 00:00:48,000
Absolutely.

21
00:00:48,000 --> 00:00:50,680
So our mission today, to break down Thangino for you,

22
00:00:50,680 --> 00:00:51,920
especially if you're new to this,

23
00:00:51,920 --> 00:00:53,500
we want to give you the clear entry points,

24
00:00:53,500 --> 00:00:55,640
but also, crucially, the big warnings,

25
00:00:55,640 --> 00:00:58,520
straight from the project's own sources, like their GitHub.

26
00:00:58,520 --> 00:01:00,160
Yeah, the warnings are important here.

27
00:01:00,160 --> 00:01:01,600
OK, let's unpack this.

28
00:01:01,600 --> 00:01:02,880
Right, so first things first.

29
00:01:02,880 --> 00:01:04,920
Let's make sure everyone's on the same page about firmware.

30
00:01:04,920 --> 00:01:05,800
What is it?

31
00:01:05,800 --> 00:01:06,400
Good point.

32
00:01:06,400 --> 00:01:07,080
Go ahead.

33
00:01:07,080 --> 00:01:09,560
Well, think of firmware as basically the operating

34
00:01:09,560 --> 00:01:11,080
system for your camera.

35
00:01:11,080 --> 00:01:12,760
It's the core software that tells it

36
00:01:12,760 --> 00:01:17,240
how to record video, connect to your Wi-Fi, all that stuff.

37
00:01:17,240 --> 00:01:17,960
OK, makes sense.

38
00:01:17,960 --> 00:01:20,160
Like Windows, but for a camera.

39
00:01:20,160 --> 00:01:21,240
Sort of, yeah.

40
00:01:21,240 --> 00:01:22,880
A very specialized OS.

41
00:01:22,880 --> 00:01:25,120
And Thangino, it's a replacement for the software

42
00:01:25,120 --> 00:01:26,240
the camera came with.

43
00:01:26,240 --> 00:01:28,640
It's open source, built by the community.

44
00:01:28,640 --> 00:01:30,880
So you're swapping out the company's code

45
00:01:30,880 --> 00:01:32,240
for community code.

46
00:01:32,240 --> 00:01:35,120
But it won't work on just any camera, right?

47
00:01:35,120 --> 00:01:35,960
What's the target?

48
00:01:35,960 --> 00:01:37,080
No, definitely not.

49
00:01:37,080 --> 00:01:38,440
It's highly specialized.

50
00:01:38,440 --> 00:01:40,080
The Gino targets IP cameras that are

51
00:01:40,080 --> 00:01:42,640
built around a specific family of chips.

52
00:01:42,640 --> 00:01:44,840
Ingenic system on chips or Socus.

53
00:01:44,840 --> 00:01:49,680
Ingenic, like the T31X or T23N chips the docs mentioned.

54
00:01:49,680 --> 00:01:50,560
Exactly those.

55
00:01:50,560 --> 00:01:51,360
They're super common.

56
00:01:51,360 --> 00:01:53,640
You find them in tons of cameras, both generic ones

57
00:01:53,640 --> 00:01:54,720
and big brands.

58
00:01:54,720 --> 00:01:57,040
By focusing just on these Ingenic chips,

59
00:01:57,040 --> 00:02:00,560
then Gino can offer something really robust, customizable,

60
00:02:00,560 --> 00:02:03,880
and importantly, more private without manufacturer backdoors

61
00:02:03,880 --> 00:02:05,000
or limitations.

62
00:02:05,000 --> 00:02:08,320
And looking at the sources, this isn't some weekend project.

63
00:02:08,320 --> 00:02:09,280
It looks pretty serious.

64
00:02:09,280 --> 00:02:10,400
Oh yeah, it's active.

65
00:02:10,400 --> 00:02:12,320
The GitHub repository shows that clearly.

66
00:02:12,320 --> 00:02:14,160
We're talking an MIT license, which

67
00:02:14,160 --> 00:02:18,080
is great for open source, and the numbers.

68
00:02:18,080 --> 00:02:25,120
Wow, over 1,100 stars, 138 forks, 66 contributors.

69
00:02:25,120 --> 00:02:27,520
That's significant community backing.

70
00:02:27,520 --> 00:02:30,520
That kind of support is essential, honestly,

71
00:02:30,520 --> 00:02:32,740
given how complex firmware can be.

72
00:02:32,740 --> 00:02:34,480
And something else interesting from the source

73
00:02:34,480 --> 00:02:37,160
is the breakdown of programming languages used.

74
00:02:37,160 --> 00:02:37,960
Right, I saw that.

75
00:02:37,960 --> 00:02:41,960
Mostly shell, like almost 50%, and make file at 36%.

76
00:02:41,960 --> 00:02:42,920
What does that tell us?

77
00:02:42,920 --> 00:02:44,920
It doesn't sound like typical app development.

78
00:02:44,920 --> 00:02:46,340
It tells you this is fundamentally

79
00:02:46,340 --> 00:02:47,960
about building the environment.

80
00:02:47,960 --> 00:02:50,300
It's less about writing a fancy user interface

81
00:02:50,300 --> 00:02:52,800
and more about controlling the whole build process.

82
00:02:52,800 --> 00:02:55,560
Shell scripts and make files are perfect for automating

83
00:02:55,560 --> 00:02:58,000
the compilation of the Linux kernel, all the tools,

84
00:02:58,000 --> 00:03:00,800
the drivers, everything needed for these slightly

85
00:03:00,800 --> 00:03:02,280
different Ingenix chips.

86
00:03:02,280 --> 00:03:03,000
Oh, OK.

87
00:03:03,000 --> 00:03:04,380
So it's the scaffolding that lets

88
00:03:04,380 --> 00:03:07,040
them build the actual firmware for all those different camera

89
00:03:07,040 --> 00:03:07,960
models they support.

90
00:03:07,960 --> 00:03:08,440
Precisely.

91
00:03:08,440 --> 00:03:09,280
It's the backbone.

92
00:03:09,280 --> 00:03:11,520
It makes the whole thing manageable for the community.

93
00:03:11,520 --> 00:03:12,680
That makes a lot more sense.

94
00:03:12,680 --> 00:03:15,640
And for anyone wanting to explore or needing help,

95
00:03:15,640 --> 00:03:17,560
the project seems well set up.

96
00:03:17,560 --> 00:03:21,080
The source is mentioned, a project website, a wiki,

97
00:03:21,080 --> 00:03:23,320
even a Discord and a Telegram group.

98
00:03:23,320 --> 00:03:24,780
Yeah, it's a proper ecosystem.

99
00:03:24,780 --> 00:03:26,200
You're not left on your own.

100
00:03:26,200 --> 00:03:28,720
Which is good because, well, here's work

101
00:03:28,720 --> 00:03:31,240
it's really interesting, maybe a bit tricky.

102
00:03:31,240 --> 00:03:33,680
We have to talk about what supported camera actually

103
00:03:33,680 --> 00:03:34,360
means.

104
00:03:34,360 --> 00:03:36,680
It's not straightforward.

105
00:03:36,680 --> 00:03:39,560
This is probably the biggest hurdle for anyone starting out.

106
00:03:39,560 --> 00:03:42,840
The documentation is very clear, very blunt about this.

107
00:03:42,840 --> 00:03:44,720
Just because your camera's model name,

108
00:03:44,720 --> 00:03:49,520
say a TP-Link Tapo C110 or a Wyze Cam 3 is on their list,

109
00:03:49,520 --> 00:03:51,520
that doesn't guarantee thingy know will work.

110
00:03:51,520 --> 00:03:52,120
Wait, hold on.

111
00:03:52,120 --> 00:03:52,620
Why not?

112
00:03:52,620 --> 00:03:55,560
If I buy a specific model, shouldn't the insides

113
00:03:55,560 --> 00:03:56,420
be the same?

114
00:03:56,420 --> 00:03:57,960
You'd think so, wouldn't you?

115
00:03:57,960 --> 00:04:00,320
But unfortunately, especially with mass market electronics,

116
00:04:00,320 --> 00:04:02,200
it's common for manufacturers to swap out

117
00:04:02,200 --> 00:04:04,160
internal components between different batches

118
00:04:04,160 --> 00:04:05,360
of the exact same model.

119
00:04:05,360 --> 00:04:05,920
Really?

120
00:04:05,920 --> 00:04:07,440
Why would they do that?

121
00:04:07,440 --> 00:04:08,640
Usually cost.

122
00:04:08,640 --> 00:04:10,960
Or maybe a specific chip becomes hard to get.

123
00:04:10,960 --> 00:04:13,560
So they find a replacement part that, from the outside,

124
00:04:13,560 --> 00:04:14,720
does the same basic job.

125
00:04:14,720 --> 00:04:16,680
They don't change the model number on the box,

126
00:04:16,680 --> 00:04:18,760
because it still records video.

127
00:04:18,760 --> 00:04:21,760
But for something like Thingino, which needs to talk directly

128
00:04:21,760 --> 00:04:24,640
to the hardware, a different chip inside

129
00:04:24,640 --> 00:04:25,600
could break everything.

130
00:04:25,600 --> 00:04:26,200
Exactly.

131
00:04:26,200 --> 00:04:27,800
It completely breaks compatibility

132
00:04:27,800 --> 00:04:28,840
at that low level.

133
00:04:28,840 --> 00:04:30,560
So if you want to solve Thingino,

134
00:04:30,560 --> 00:04:32,680
you basically have to become a hardware detective.

135
00:04:32,680 --> 00:04:35,600
You need to verify four specific internal components

136
00:04:35,600 --> 00:04:37,480
in your specific camera unit.

137
00:04:37,480 --> 00:04:38,080
Four components.

138
00:04:38,080 --> 00:04:39,180
OK, that sounds intense.

139
00:04:39,180 --> 00:04:39,880
Walk us through them.

140
00:04:39,880 --> 00:04:40,880
What do you need to check?

141
00:04:40,880 --> 00:04:44,760
Number one, the most critical, the SoC, the main chip.

142
00:04:44,760 --> 00:04:47,040
As we said, it must be a compatible Ingenic one,

143
00:04:47,040 --> 00:04:48,600
like a T31X or similar.

144
00:04:48,600 --> 00:04:49,440
All right, got it.

145
00:04:49,440 --> 00:04:51,960
Second, the image sensor, that's the part that actually

146
00:04:51,960 --> 00:04:56,200
captures the picture, like a GC4653 or an SC2336,

147
00:04:56,200 --> 00:04:57,640
the Dock's List specific ones.

148
00:04:57,640 --> 00:04:58,960
OK, SoC sensor.

149
00:04:58,960 --> 00:05:01,720
Third, the Wi-Fi module, the chip that

150
00:05:01,720 --> 00:05:03,680
handles the wireless connection.

151
00:05:03,680 --> 00:05:10,120
Again, specific models matter, like an ATBM6031 or RTL189FTV.

152
00:05:10,120 --> 00:05:11,520
OK, and the last one.

153
00:05:11,520 --> 00:05:14,600
And finally, the flash chip size, the little chip

154
00:05:14,600 --> 00:05:16,360
that stores the firmware itself.

155
00:05:16,360 --> 00:05:18,680
Did your camera have an 8-millibee chip,

156
00:05:18,680 --> 00:05:20,680
16-milli, 32-milli?

157
00:05:20,680 --> 00:05:23,400
That needs to match the supported combination, too.

158
00:05:23,400 --> 00:05:24,080
Wow.

159
00:05:24,080 --> 00:05:28,360
SoC, image sensor, Wi-Fi module, and flash size.

160
00:05:28,360 --> 00:05:31,280
If even one of those doesn't match the exact combination

161
00:05:31,280 --> 00:05:34,400
listed for your model in the Thinggeno Docks,

162
00:05:34,400 --> 00:05:35,760
it might not work, or worse.

163
00:05:35,760 --> 00:05:36,940
Or worse, yeah.

164
00:05:36,940 --> 00:05:38,360
You could potentially break it.

165
00:05:38,360 --> 00:05:40,760
That's why the hardware list is so detailed, listing models

166
00:05:40,760 --> 00:05:43,920
like the Wi-Fi E220 or Wyze Cam Floodlight,

167
00:05:43,920 --> 00:05:46,880
but always with footnotes about the specific internal combo

168
00:05:46,880 --> 00:05:47,480
required.

169
00:05:47,480 --> 00:05:49,680
So the name on the box is almost irrelevant.

170
00:05:49,680 --> 00:05:51,640
It's the silicon inside that counts.

171
00:05:51,640 --> 00:05:54,160
In the world of firmware, the hardware combination

172
00:05:54,160 --> 00:05:55,480
is the real model number.

173
00:05:55,480 --> 00:05:56,600
That's the key takeaway.

174
00:05:56,600 --> 00:05:57,280
OK.

175
00:05:57,280 --> 00:05:59,520
Now, for listeners who are maybe a bit more technical,

176
00:05:59,520 --> 00:06:02,200
curious about how to actually build this firmware,

177
00:06:02,200 --> 00:06:03,920
the sources give instructions, right?

178
00:06:03,920 --> 00:06:05,540
But it's not just downloading a file.

179
00:06:05,540 --> 00:06:05,920
Not at all.

180
00:06:05,920 --> 00:06:08,720
You had to compile the entire operating system yourself.

181
00:06:08,720 --> 00:06:11,080
This involves something called cross compilation,

182
00:06:11,080 --> 00:06:13,640
meaning you use your regular computer, probably

183
00:06:13,640 --> 00:06:15,960
a Linux machine or maybe a virtual machine,

184
00:06:15,960 --> 00:06:18,280
to build software that runs on a totally different type

185
00:06:18,280 --> 00:06:20,780
of processor, the little nginic chip in the camera.

186
00:06:20,780 --> 00:06:23,000
The project uses tools like Buildroot,

187
00:06:23,000 --> 00:06:25,000
which the source has mentioned, to manage

188
00:06:25,000 --> 00:06:26,320
this whole complex setup.

189
00:06:26,320 --> 00:06:26,820
Right.

190
00:06:26,820 --> 00:06:28,520
Buildroot handles the environment.

191
00:06:28,520 --> 00:06:30,280
So let's quickly go through the main steps,

192
00:06:30,280 --> 00:06:32,520
not just reading the commands, but what they do.

193
00:06:32,520 --> 00:06:33,120
Sure.

194
00:06:33,120 --> 00:06:36,800
It usually starts with get clone recurse submodules.

195
00:06:36,800 --> 00:06:39,320
That command grabs the thinggino code,

196
00:06:39,320 --> 00:06:42,280
but the recurse submodules part is crucial.

197
00:06:42,280 --> 00:06:45,600
It also pulls down all the other necessary code libraries,

198
00:06:45,600 --> 00:06:47,680
gets to the Linux kernel, Buildroot itself,

199
00:06:47,680 --> 00:06:49,880
specific drivers, everything needed.

200
00:06:49,880 --> 00:06:52,340
So it's downloading a whole development kit, essentially.

201
00:06:52,340 --> 00:06:53,120
Pretty much, yeah.

202
00:06:53,120 --> 00:06:55,880
It can be quite large, gigabytes even, and take a while.

203
00:06:55,880 --> 00:06:57,120
You're getting the whole ecosystem.

204
00:06:57,120 --> 00:06:59,240
OK, so you've cloned the ecosystem.

205
00:06:59,240 --> 00:07:01,120
Then you navigate into the folder,

206
00:07:01,120 --> 00:07:05,160
usually CD-Thingino firmware, and the main command, make.

207
00:07:05,160 --> 00:07:05,920
Just make.

208
00:07:05,920 --> 00:07:07,360
It's just make.

209
00:07:07,360 --> 00:07:10,520
That one command triggers the whole automated process

210
00:07:10,520 --> 00:07:13,000
we talked about earlier, using all those shell scripts

211
00:07:13,000 --> 00:07:13,880
and make files.

212
00:07:13,880 --> 00:07:16,200
It configures the kernel, compiles all the software

213
00:07:16,200 --> 00:07:19,280
parts, links the right drivers for your specific hardware

214
00:07:19,280 --> 00:07:21,920
combo, those four components, and finally,

215
00:07:21,920 --> 00:07:24,440
packages it all up into a firmware image file

216
00:07:24,440 --> 00:07:26,060
that you can then flash onto the camera.

217
00:07:26,060 --> 00:07:28,880
And that make process isn't instant, I assume.

218
00:07:28,880 --> 00:07:29,680
Oh, no.

219
00:07:29,680 --> 00:07:32,760
Depending on your computer, it could easily take 20 minutes,

220
00:07:32,760 --> 00:07:34,240
maybe longer, especially the first time.

221
00:07:34,240 --> 00:07:35,280
It's doing a lot of work.

222
00:07:35,280 --> 00:07:37,240
OK, that really drives home that this

223
00:07:37,240 --> 00:07:39,880
is a serious hands-on process.

224
00:07:39,880 --> 00:07:44,120
You're building something custom for your specific camera's guts.

225
00:07:44,120 --> 00:07:45,680
So let's say you've done your homework.

226
00:07:45,680 --> 00:07:47,040
You've identified your four components.

227
00:07:47,040 --> 00:07:48,540
You've managed to build the firmware.

228
00:07:48,540 --> 00:07:49,520
Now what?

229
00:07:49,520 --> 00:07:51,240
Before you actually try to install it,

230
00:07:51,240 --> 00:07:54,320
the sources highlight two really big warnings,

231
00:07:54,320 --> 00:07:55,720
two major hurdles.

232
00:07:55,720 --> 00:07:56,640
Yes.

233
00:07:56,640 --> 00:07:58,760
And these carry significant risk.

234
00:07:58,760 --> 00:08:01,320
The first, and honestly the most dangerous one, is secure boot.

235
00:08:01,320 --> 00:08:02,280
Secure boot.

236
00:08:02,280 --> 00:08:03,080
I've heard of that.

237
00:08:03,080 --> 00:08:04,280
How does it apply here?

238
00:08:04,280 --> 00:08:07,320
Well, the sources talk about conditionally supported hardware.

239
00:08:07,320 --> 00:08:09,400
Often, that condition is whether secure boot

240
00:08:09,400 --> 00:08:13,200
is turned on in that specific camera unit.

241
00:08:13,200 --> 00:08:16,000
Basically, secure boot is a security feature

242
00:08:16,000 --> 00:08:17,880
built into the chip itself.

243
00:08:17,880 --> 00:08:20,360
Some manufacturers, during production,

244
00:08:20,360 --> 00:08:23,560
read a secret digital key into a special part of the SoZ

245
00:08:23,560 --> 00:08:25,320
called the OTP area.

246
00:08:25,320 --> 00:08:27,280
OTP, one-time programmable.

247
00:08:27,280 --> 00:08:28,360
Exactly, one time.

248
00:08:28,360 --> 00:08:31,720
Once they write that key and blow the fuse, so to speak,

249
00:08:31,720 --> 00:08:32,400
it's permanent.

250
00:08:32,400 --> 00:08:33,920
It cannot be changed or erased.

251
00:08:33,920 --> 00:08:35,440
Like etching something in stone.

252
00:08:35,440 --> 00:08:36,120
Pretty much.

253
00:08:36,120 --> 00:08:36,840
Yeah.

254
00:08:36,840 --> 00:08:40,400
And the chip is then programmed to only boot software firmware

255
00:08:40,400 --> 00:08:43,120
that's been digitally signed with the matching secret key held

256
00:08:43,120 --> 00:08:44,320
by the manufacturer.

257
00:08:44,320 --> 00:08:45,920
OK, so I see where this is going.

258
00:08:45,920 --> 00:08:48,440
The Nino, being open source and community built,

259
00:08:48,440 --> 00:08:51,000
isn't signed with the manufacturer's secret key.

260
00:08:51,000 --> 00:08:51,560
Correct.

261
00:08:51,560 --> 00:08:52,200
It can't be.

262
00:08:52,200 --> 00:08:54,600
So if you try to flash the Nino onto a camera where

263
00:08:54,600 --> 00:08:56,000
a secure boot has been permanently

264
00:08:56,000 --> 00:08:57,480
enabled in that OTP area.

265
00:08:57,480 --> 00:08:58,320
What happens?

266
00:08:58,320 --> 00:09:02,000
The camera's initial bootloader checks the signature,

267
00:09:02,000 --> 00:09:05,040
sees it doesn't match the key locked in the OTP,

268
00:09:05,040 --> 00:09:05,960
and just stops.

269
00:09:05,960 --> 00:09:07,380
It refuses to boot.

270
00:09:07,380 --> 00:09:10,900
And the result, the source is very clear, is catastrophic.

271
00:09:10,900 --> 00:09:14,440
The camera is permanently bricked, unusable.

272
00:09:14,440 --> 00:09:18,040
Bricked means it's just a plastic box, no fixing it.

273
00:09:18,040 --> 00:09:19,160
No fixing it.

274
00:09:19,160 --> 00:09:22,400
Unless you physically de-solder and replace the entire sock

275
00:09:22,400 --> 00:09:25,920
chip, which is not practical for most people, it's dead.

276
00:09:25,920 --> 00:09:26,800
Wow.

277
00:09:26,800 --> 00:09:27,680
That's a huge risk.

278
00:09:27,680 --> 00:09:30,240
It's like the camera actively rejects the transplant.

279
00:09:30,240 --> 00:09:32,560
And the docs mentioned specific models, right?

280
00:09:32,560 --> 00:09:36,060
Like some Roku or Wyze cameras tested

281
00:09:36,060 --> 00:09:37,920
were found to have it enabled.

282
00:09:37,920 --> 00:09:38,440
Yes.

283
00:09:38,440 --> 00:09:40,760
The community tries to track which specific batches

284
00:09:40,760 --> 00:09:44,040
or versions of models are known to have secure boot enabled,

285
00:09:44,040 --> 00:09:46,320
often using color codes or other identifiers mentioned

286
00:09:46,320 --> 00:09:47,200
in the wiki.

287
00:09:47,200 --> 00:09:49,280
But it's always a risk with conditionally supported

288
00:09:49,280 --> 00:09:49,640
hardware.

289
00:09:49,640 --> 00:09:51,560
You have to check carefully before flashing.

290
00:09:51,560 --> 00:09:52,840
Extreme caution needed.

291
00:09:52,840 --> 00:09:54,240
OK, what's the second big hurdle?

292
00:09:54,240 --> 00:09:56,080
Something about mystery box hardware.

293
00:09:56,080 --> 00:09:58,240
Right, this is more about the unpredictability

294
00:09:58,240 --> 00:10:01,400
of the supply chain, especially if you buy cameras from, say,

295
00:10:01,400 --> 00:10:04,280
AliExpress or similar large online marketplaces.

296
00:10:04,280 --> 00:10:05,480
What's the issue there?

297
00:10:05,480 --> 00:10:08,800
Even if the camera looks identical to a supported model,

298
00:10:08,800 --> 00:10:11,520
has the same sticker on it, sometimes the manufacturer

299
00:10:11,520 --> 00:10:14,440
has put completely different hardware inside.

300
00:10:14,440 --> 00:10:17,480
The sources specifically warn that sometimes these clones

301
00:10:17,480 --> 00:10:21,280
might contain an unsupported ARM processor instead

302
00:10:21,280 --> 00:10:23,760
of the required Ingenix Solve.

303
00:10:23,760 --> 00:10:25,920
So even if you thought you had the right model,

304
00:10:25,920 --> 00:10:28,720
the actual brain inside is totally wrong for Thinggino.

305
00:10:28,720 --> 00:10:29,360
Exactly.

306
00:10:29,360 --> 00:10:30,400
The outside looks right.

307
00:10:30,400 --> 00:10:32,160
Maybe even some of the other ships match.

308
00:10:32,160 --> 00:10:35,200
But the core processor architecture is incompatible.

309
00:10:35,200 --> 00:10:36,640
So Thinggino just won't run.

310
00:10:36,640 --> 00:10:38,360
It reinforces that idea.

311
00:10:38,360 --> 00:10:41,000
You need to verify everything, especially the SoC type.

312
00:10:41,000 --> 00:10:41,920
Got it.

313
00:10:41,920 --> 00:10:43,720
And quickly, are there types of cameras

314
00:10:43,720 --> 00:10:45,960
that are just flat out unsupported?

315
00:10:45,960 --> 00:10:46,460
Yes.

316
00:10:46,460 --> 00:10:49,000
The sources mentioned that battery-powered cameras,

317
00:10:49,000 --> 00:10:51,200
particularly those using something called the ZeraTool

318
00:10:51,200 --> 00:10:53,640
platform, are currently unsupported.

319
00:10:53,640 --> 00:10:55,200
They have different power-saving needs

320
00:10:55,200 --> 00:10:57,400
that Thinggino isn't designed for right now.

321
00:10:57,400 --> 00:11:00,240
OK, so summing this up, this deep dive

322
00:11:00,240 --> 00:11:03,200
really highlights that classic tech tension, doesn't it?

323
00:11:03,200 --> 00:11:06,160
Thinggino offers this incredible open source freedom,

324
00:11:06,160 --> 00:11:08,600
real control over your camera, getting away

325
00:11:08,600 --> 00:11:10,440
from proprietary cloud stuff.

326
00:11:10,440 --> 00:11:12,920
Which is very appealing for privacy and customization.

327
00:11:12,920 --> 00:11:14,080
Totally.

328
00:11:14,080 --> 00:11:17,200
But that freedom comes bundled with some serious

329
00:11:17,200 --> 00:11:18,040
responsibility.

330
00:11:18,040 --> 00:11:20,680
You absolutely must do that deep hardware check,

331
00:11:20,680 --> 00:11:22,560
understand the components, and you

332
00:11:22,560 --> 00:11:25,800
face that potentially fatal risk of secure boot turning

333
00:11:25,800 --> 00:11:28,000
your camera into a paperweight.

334
00:11:28,000 --> 00:11:30,380
And that risk leads to a really interesting final thought

335
00:11:30,380 --> 00:11:33,280
for you, the listener, to ponder.

336
00:11:33,280 --> 00:11:36,480
If security features that are meant to protect users,

337
00:11:36,480 --> 00:11:38,800
like secure boot verifying firmware,

338
00:11:38,800 --> 00:11:42,520
are locked down so tightly with these permanent hardware keys,

339
00:11:42,520 --> 00:11:44,720
does the convenience and, let's face it,

340
00:11:44,720 --> 00:11:47,880
the warranty back simplicity of just using the manufacturer's

341
00:11:47,880 --> 00:11:50,520
pre-signed firmware maybe outweigh the absolute

342
00:11:50,520 --> 00:11:53,000
customization you get with the Ingenio?

343
00:11:53,000 --> 00:11:55,280
Especially for something like a security camera,

344
00:11:55,280 --> 00:11:58,080
where does that balance lie for you between total control

345
00:11:58,080 --> 00:12:00,920
and guaranteed, albeit potentially restricted,

346
00:12:00,920 --> 00:12:01,800
functionality?

347
00:12:01,800 --> 00:12:03,160
That's a great question.

348
00:12:03,160 --> 00:12:07,440
Control versus safety, openness versus locked down security,

349
00:12:07,440 --> 00:12:09,360
definitely something to think about regarding

350
00:12:09,360 --> 00:12:11,440
the devices in your own home.

351
00:12:11,440 --> 00:12:14,200
A big thank you again to our supporter, Safe Server,

352
00:12:14,200 --> 00:12:16,720
for making this exploration possible.

353
00:12:16,720 --> 00:12:20,320
Remember to check them out at www.safeserver.de

354
00:12:20,320 --> 00:12:23,120
for hosting and digital transformation support.

355
00:12:23,120 --> 00:12:25,520
So whether you decide to venture into custom firmware

356
00:12:25,520 --> 00:12:27,360
or stick with what came in the box,

357
00:12:27,360 --> 00:12:30,160
now you've got a much clearer picture of the internals,

358
00:12:30,160 --> 00:12:33,000
the risks, and the power involved with your IP camera.

359
00:12:33,000 --> 00:12:34,520
Go explore these ideas further.

360
00:12:34,520 --> 00:12:35,720
Definitely worth thinking about.

361
00:12:35,720 --> 00:12:37,720
We'll catch you on the next Deep Dive.