1
00:00:00,000 --> 00:00:03,960
Welcome to the Deep Dive! This is where we really get into the details from a bunch

2
00:00:03,960 --> 00:00:04,480
of sources to

3
00:00:04,480 --> 00:00:08,410
pull out what matters for you. And before we get started today, a big thank you to

4
00:00:08,410 --> 00:00:09,280
our supporter

5
00:00:09,280 --> 00:00:13,230
SafeServer. They're fantastic with hosting solutions and helping businesses

6
00:00:13,230 --> 00:00:13,760
navigate their

7
00:00:13,760 --> 00:00:20,150
digital transformation. If you want to know more, check them out at www.safeserver.de.

8
00:00:20,150 --> 00:00:20,480
They really

9
00:00:20,480 --> 00:00:25,840
help us keep doing these deep dives. Okay, so today's topic. It's something pretty

10
00:00:25,840 --> 00:00:26,560
much everyone

11
00:00:26,560 --> 00:00:31,970
deals with if you own a smartphone or a camera managing all those digital photos.

12
00:00:31,970 --> 00:00:32,560
Specifically,

13
00:00:32,560 --> 00:00:36,030
you asked us to look into a system called lychee. So we've been digging through

14
00:00:36,030 --> 00:00:36,640
their website,

15
00:00:36,640 --> 00:00:41,680
the GitHub repo, what people are saying the whole lot. Yeah. And our goal here

16
00:00:41,680 --> 00:00:42,480
really is simple. We

17
00:00:42,480 --> 00:00:45,700
want to cut through maybe some of the tech talk and figure out what lychee actually

18
00:00:45,700 --> 00:00:46,560
is, you know,

19
00:00:46,560 --> 00:00:51,520
why is it pitched as this interesting alternative to say Google Photos or iCloud

20
00:00:51,520 --> 00:00:52,240
and what's actually

21
00:00:52,240 --> 00:00:56,200
involved if you wanted to use it. Especially if you're maybe new to this whole idea

22
00:00:56,200 --> 00:00:56,640
of running

23
00:00:56,640 --> 00:01:01,430
stuff on your own server. Right. Think of this as your shortcut to getting the gist

24
00:01:01,430 --> 00:01:02,080
of lychee.

25
00:01:02,080 --> 00:01:06,850
Because, I mean, let's face it, managing digital photos can feel a bit like hurting

26
00:01:06,850 --> 00:01:07,600
cats sometimes,

27
00:01:07,600 --> 00:01:11,880
can't it? Oh, definitely. They end up everywhere. Your phone, your laptop, maybe

28
00:01:11,880 --> 00:01:12,560
some old cloud

29
00:01:12,560 --> 00:01:16,190
service you tried years ago. Then you hit storage limits or you start worrying

30
00:01:16,190 --> 00:01:17,520
about privacy or just,

31
00:01:17,520 --> 00:01:21,380
you know, feeling like you don't really own your own memories anymore. It's a

32
00:01:21,380 --> 00:01:21,920
really common

33
00:01:21,920 --> 00:01:25,520
feeling, that fragmentation, your moments are scattered or maybe they're sitting on

34
00:01:25,520 --> 00:01:26,160
some company

35
00:01:26,160 --> 00:01:29,880
servers where you're just, well, part of their data pool. That sense of real

36
00:01:29,880 --> 00:01:32,480
ownership, it can get lost.

37
00:01:32,480 --> 00:01:37,100
Exactly. And that seems to be the exact problem lychee is trying to solve based on

38
00:01:37,100 --> 00:01:37,680
what we read.

39
00:01:37,680 --> 00:01:43,600
They describe it as this really good looking, easy to use photo management system.

40
00:01:43,600 --> 00:01:44,640
But the big

41
00:01:44,640 --> 00:01:49,540
difference is you host it yourself. It runs on your server in your online space.

42
00:01:49,540 --> 00:01:50,560
The main idea seems

43
00:01:50,560 --> 00:01:55,360
to be take back control of your photos. And it's not just about storage, is it? The

44
00:01:55,360 --> 00:01:56,080
sources frame it

45
00:01:56,080 --> 00:02:00,590
more like a complete cycle, managing them, sharing them, and viewing them. Okay,

46
00:02:00,590 --> 00:02:01,440
yeah, let's unpack

47
00:02:01,440 --> 00:02:05,580
that. That manage share view loop. What does that actually look like if you're

48
00:02:05,580 --> 00:02:06,720
using lychee? Well,

49
00:02:06,720 --> 00:02:12,440
think of lychee as like your own personal private photo gallery website. But you

50
00:02:12,440 --> 00:02:13,440
build it, you

51
00:02:13,440 --> 00:02:18,000
control it. Instead of sending your photos off to some huge company, you install

52
00:02:18,000 --> 00:02:19,360
this lychee software

53
00:02:19,360 --> 00:02:24,130
on, let's say, some web space you rent, or maybe a server you run at home. Got it.

54
00:02:24,130 --> 00:02:25,120
So it's my space

55
00:02:25,120 --> 00:02:29,640
just for my pictures. Precisely. And the manage part seems surprisingly capable for

56
00:02:29,640 --> 00:02:30,240
something

57
00:02:30,240 --> 00:02:34,920
self-hosted. We saw you can upload photos, obviously from your computer, but also

58
00:02:34,920 --> 00:02:35,600
straight from a server

59
00:02:35,600 --> 00:02:41,380
location using a web URL. They even mention integrations like pulling from Dropbox.

60
00:02:41,380 --> 00:02:41,840
Okay.

61
00:02:41,840 --> 00:02:45,920
Once they're in, the in-face looks really clean. You can sort them into albums,

62
00:02:45,920 --> 00:02:46,720
move things around,

63
00:02:46,720 --> 00:02:50,720
rename files, add descriptions. And they mentioned batch selection, right? Selecting

64
00:02:50,720 --> 00:02:51,440
multiple photos

65
00:02:51,440 --> 00:02:55,560
at once. That feels essential. Nobody uploads just one photo at a time, usually.

66
00:02:55,560 --> 00:02:56,800
Exactly. That's a

67
00:02:56,800 --> 00:03:01,760
must-have. And things like adding tags or marking photos is important, or favorites

68
00:03:01,760 --> 00:03:02,240
that helps you

69
00:03:02,240 --> 00:03:05,410
find stuff later. Makes sense. And for anyone who's, you know, more serious about

70
00:03:05,410 --> 00:03:05,920
photography,

71
00:03:05,920 --> 00:03:12,000
something that really stood out was the support for EXIF and IPTC metadata. Ah,

72
00:03:12,000 --> 00:03:12,560
okay. So that's

73
00:03:12,560 --> 00:03:16,720
the hidden camera info, like settings, location. Yeah, exactly. Shutter speed,

74
00:03:16,720 --> 00:03:18,960
aperture, maybe GPS

75
00:03:18,960 --> 00:03:23,760
data, copyright notes you've added. Lyche actually reads and displays that

76
00:03:23,760 --> 00:03:25,440
information. It's not just

77
00:03:25,440 --> 00:03:29,800
technical data. It's about preserving the context of your image, which a lot of

78
00:03:29,800 --> 00:03:30,960
platforms might just

79
00:03:30,960 --> 00:03:35,200
strip out or ignore. I felt like a big plus for photographers. Yeah, definitely.

80
00:03:35,200 --> 00:03:36,960
Okay, so managing

81
00:03:36,960 --> 00:03:41,280
sounds pretty thorough. What about share? People like sharing photos. Sharing seems

82
00:03:41,280 --> 00:03:41,920
designed to be

83
00:03:41,920 --> 00:03:45,510
really straightforward. The sources really emphasize that you can make an entire

84
00:03:45,510 --> 00:03:46,800
album or even just one

85
00:03:46,800 --> 00:03:51,990
photo public with basically one click. Just one click? That sounds simple. It does.

86
00:03:51,990 --> 00:03:52,400
And if you need

87
00:03:52,400 --> 00:03:56,530
more privacy, you can password protect albums, share the link and the password, and

88
00:03:56,530 --> 00:03:56,960
only those

89
00:03:56,960 --> 00:04:00,930
people can see it. Okay. And a neat little detail we picked up on. It supports

90
00:04:00,930 --> 00:04:01,840
things like Twitter

91
00:04:01,840 --> 00:04:06,160
cards and open graph, but specifically for single shared images, not the whole

92
00:04:06,160 --> 00:04:07,360
album view. What does

93
00:04:07,360 --> 00:04:11,320
that mean practically? It means if you share a link to just one public photo on

94
00:04:11,320 --> 00:04:12,800
Twitter or Facebook,

95
00:04:12,800 --> 00:04:16,380
it should show a nice preview of the actual photo right there in the feed, maybe

96
00:04:16,380 --> 00:04:17,600
with the description.

97
00:04:17,600 --> 00:04:21,540
Makes the shared link look much better. Ah, that's a nice touch. Shows they've

98
00:04:21,540 --> 00:04:22,000
thought about how

99
00:04:22,000 --> 00:04:27,410
things look outside lichy too. And then view. How does it look when you or someone

100
00:04:27,410 --> 00:04:28,080
else views the

101
00:04:28,080 --> 00:04:31,910
photos? The viewing part looks pretty slick. Modern, full screen mode, easy

102
00:04:31,910 --> 00:04:33,440
navigation. They

103
00:04:33,440 --> 00:04:37,430
even mentioned keyboard shortcuts for skipping through photos. Oh, nice. Like using

104
00:04:37,430 --> 00:04:38,000
arrow keys.

105
00:04:38,000 --> 00:04:42,320
Yeah, exactly. Suggests a smooth browsing experience. And anyone you share with

106
00:04:42,320 --> 00:04:42,800
publicly

107
00:04:42,800 --> 00:04:46,480
just visits your lichy web address and gets that same clean interface. Okay, so it

108
00:04:46,480 --> 00:04:47,280
looks good. It's

109
00:04:47,280 --> 00:04:51,270
easy to use for managing, sharing, viewing. But let's circle back to that core idea.

110
00:04:51,270 --> 00:04:52,640
Self-hosted.

111
00:04:52,640 --> 00:04:59,920
Why would someone used to the convenience of, say, Google Photos, take on running

112
00:04:59,920 --> 00:05:00,560
this themselves?

113
00:05:00,560 --> 00:05:04,710
What's the real draw? Right, and this is where the sources really hammer home the

114
00:05:04,710 --> 00:05:05,600
benefits.

115
00:05:05,600 --> 00:05:12,890
It loops back to that control idea. Number one, security and control. The message

116
00:05:12,890 --> 00:05:14,160
is super clear.

117
00:05:14,160 --> 00:05:19,120
Your server, your data, your rules. You're not trusting your entire photo library,

118
00:05:19,120 --> 00:05:23,840
which can be really personal, to a third-party company. Whose terms might change or

119
00:05:23,840 --> 00:05:24,160
whose

120
00:05:24,160 --> 00:05:28,900
business model might shift. Exactly. You decide who sees what, how it's stored,

121
00:05:28,900 --> 00:05:29,280
everything.

122
00:05:29,280 --> 00:05:33,540
You're not locked in. You're not locked in. Benefit number two, no limits. Or

123
00:05:33,540 --> 00:05:34,080
rather,

124
00:05:34,080 --> 00:05:38,480
the limits are your own. With LeChi and your server, you aren't bumping up against

125
00:05:38,480 --> 00:05:39,520
those free storage

126
00:05:39,520 --> 00:05:43,440
caps that constantly push you to upgrade. Right. And crucially, you're not having

127
00:05:43,440 --> 00:05:44,160
your photos

128
00:05:44,160 --> 00:05:48,240
automatically compressed or downsized by the service provider to save them space.

129
00:05:48,240 --> 00:05:48,800
Your limits

130
00:05:48,800 --> 00:05:52,590
are just how much storage you've allocated. So the quality stays pristine and you

131
00:05:52,590 --> 00:05:53,600
just add more disk

132
00:05:53,600 --> 00:05:57,530
space if you need it. Precisely. And the third big one they highlight is that it's

133
00:05:57,530 --> 00:05:58,320
open source.

134
00:05:58,320 --> 00:06:04,160
Which means the code is public. Exactly. The code is freely available for anyone to

135
00:06:04,160 --> 00:06:04,480
look at.

136
00:06:04,480 --> 00:06:10,000
That builds trust, right? You can see how it works. Check. There's nothing sneaky

137
00:06:10,000 --> 00:06:10,720
going on. Plus,

138
00:06:10,720 --> 00:06:14,980
it means a whole community can contribute fixes, improvements. It suggests the

139
00:06:14,980 --> 00:06:15,600
project has

140
00:06:15,600 --> 00:06:19,620
resilience beyond just the original developers. If they stopped, someone else could

141
00:06:19,620 --> 00:06:20,320
potentially

142
00:06:20,320 --> 00:06:24,720
pick it up. Yeah, that open source aspect does add a layer of reassurance,

143
00:06:24,720 --> 00:06:25,680
especially for something

144
00:06:25,680 --> 00:06:31,540
like personal photos. Okay, but that phrase runs on your server, still has that

145
00:06:31,540 --> 00:06:32,960
slightly intimidating

146
00:06:32,960 --> 00:06:37,550
pecky ring to it for a beginner. How easy is it really to get light you running?

147
00:06:37,550 --> 00:06:38,160
Yeah, they seem

148
00:06:38,160 --> 00:06:41,390
aware of that hurdle. And they've clearly tried to make the setup easier,

149
00:06:41,390 --> 00:06:42,400
especially for just

150
00:06:42,400 --> 00:06:46,480
getting started. The sources point quite strongly to one method being the most

151
00:06:46,480 --> 00:06:47,520
beginner friendly,

152
00:06:47,520 --> 00:06:51,140
using Docker. Okay, Docker, we hear that a lot. Can you give us the super simple

153
00:06:51,140 --> 00:06:52,240
explanation again?

154
00:06:52,240 --> 00:06:57,680
Huh. Okay. Think of Docker like, like a self-contained box for software,

155
00:06:57,680 --> 00:07:02,870
lychee, and everything it needs to run all the underlying code libraries, settings,

156
00:07:02,870 --> 00:07:03,680
etc. It's

157
00:07:03,680 --> 00:07:07,760
all packaged neatly inside this Docker container. You install the main Docker

158
00:07:07,760 --> 00:07:09,040
program on your server,

159
00:07:09,040 --> 00:07:13,040
then you just tell it to run the official lychee container. Docker handles making

160
00:07:13,040 --> 00:07:14,080
sure lychee plays

161
00:07:14,080 --> 00:07:18,640
nicely with your server's operating system. Oh, okay. It avoids most of the hassle

162
00:07:18,640 --> 00:07:19,120
of

163
00:07:19,120 --> 00:07:24,760
manually installing PHP, setting up a database, configuring web server settings,

164
00:07:24,760 --> 00:07:25,280
all those steps

165
00:07:25,280 --> 00:07:29,520
that can trip people up. It's much closer to downloading a ready-made appliance. So

166
00:07:29,520 --> 00:07:30,400
Docker

167
00:07:30,400 --> 00:07:35,480
kind of takes away a lot of the potential setup headaches, makes it more plug and

168
00:07:35,480 --> 00:07:36,560
play-ish. Yeah,

169
00:07:36,560 --> 00:07:40,260
much more so than the traditional ways. The sources do mention other methods like

170
00:07:40,260 --> 00:07:41,040
just copying the

171
00:07:41,040 --> 00:07:44,200
files to a web server or even building it from the source code yourself. And

172
00:07:44,200 --> 00:07:45,200
building from source

173
00:07:45,200 --> 00:07:49,680
sounds, complicated. Oh yeah, significantly more involved. That's getting into web

174
00:07:49,680 --> 00:07:50,000
development

175
00:07:50,000 --> 00:07:54,190
territory. You'd need to handle PHP versions, use tools like Composer and NPM, set

176
00:07:54,190 --> 00:07:54,800
up the database

177
00:07:54,800 --> 00:07:58,300
manually, run command line, build steps. Okay. It offers flexibility if you know

178
00:07:58,300 --> 00:07:59,520
what you're doing,

179
00:07:59,520 --> 00:08:04,640
but definitely for a beginner just wanting to try lychee, Docker seems like the

180
00:08:04,640 --> 00:08:06,000
clear recommendation

181
00:08:06,000 --> 00:08:10,320
to avoid that initial complexity. Got it. Stick with Docker if you're new to this.

182
00:08:10,880 --> 00:08:15,440
Now, are there ways to enhance lychee once it's running? Any optional extras

183
00:08:15,440 --> 00:08:16,000
mentioned?

184
00:08:16,000 --> 00:08:19,120
Yeah. A couple of things stood out. One is integrating image magic.

185
00:08:19,120 --> 00:08:22,080
Image magic. Sounds familiar. Image processing.

186
00:08:22,080 --> 00:08:26,560
Exactly. It's a separate tool you can install on your server. If lychee detects it,

187
00:08:26,560 --> 00:08:30,870
it can use image magic when you upload photos, particularly for creating thumbnails

188
00:08:30,870 --> 00:08:31,360
and different

189
00:08:31,360 --> 00:08:35,530
sizes needed for display. We gather this can speed things up and potentially

190
00:08:35,530 --> 00:08:36,000
improve the

191
00:08:36,000 --> 00:08:40,160
quality of those generated images. It's optional, but a nice boost if you can set

192
00:08:40,160 --> 00:08:40,480
it up.

193
00:08:40,480 --> 00:08:44,240
Okay, so a helper tool on the server side. Makes sense. Anything else?

194
00:08:44,240 --> 00:08:48,240
The other one was email notifications. You have to configure your server to

195
00:08:48,240 --> 00:08:48,560
actually

196
00:08:48,560 --> 00:08:53,030
send emails first, which involves setting up mail server details and maybe a

197
00:08:53,030 --> 00:08:53,840
scheduled task,

198
00:08:53,840 --> 00:08:56,480
a cron job. Right, not totally trivial maybe?

199
00:08:56,480 --> 00:09:01,920
No, a bit more setup. But if you do, lychee can apparently send out notifications,

200
00:09:01,920 --> 00:09:08,080
like weekly digests of new photos added to the administrator, or to people an album

201
00:09:08,080 --> 00:09:08,480
is shared

202
00:09:08,480 --> 00:09:13,280
with. Users can opt in if they want updates. Ah, that's quite thoughtful. Letting

203
00:09:13,280 --> 00:09:13,600
people

204
00:09:13,600 --> 00:09:18,640
subscribe to updates on shared albums. Useful. What if you get stuck though?

205
00:09:18,640 --> 00:09:22,240
Trying to set up Docker or using a feature? Is there help?

206
00:09:22,240 --> 00:09:25,840
Yeah, definitely. Even though you're hosting it, you're not completely alone.

207
00:09:25,840 --> 00:09:31,200
The project website has documentation, FAQs, troubleshooting guides, and because it's

208
00:09:31,200 --> 00:09:31,440
open

209
00:09:31,440 --> 00:09:35,120
source, there's that community aspect. People report issues and ask questions on

210
00:09:35,120 --> 00:09:35,840
GitHub.

211
00:09:35,840 --> 00:09:39,520
There are also community chat channels mentioned, like Gitter or Discord,

212
00:09:39,520 --> 00:09:41,680
where you can connect with other users or developers.

213
00:09:41,680 --> 00:09:45,520
So there are places to ask questions and get help from people who actually use it.

214
00:09:45,520 --> 00:09:46,080
That's good.

215
00:09:46,080 --> 00:09:49,920
Absolutely. And that whole open development process on GitHub means

216
00:09:49,920 --> 00:09:53,360
you can see what's being worked on. They mentioned stable versions versus maybe

217
00:09:53,360 --> 00:09:53,600
more

218
00:09:53,600 --> 00:09:57,410
cutting edge development branches, which relates to the Docker tags you might

219
00:09:57,410 --> 00:09:58,000
choose.

220
00:09:58,000 --> 00:10:02,480
It all feels quite transparent. And seeing support from companies like JetBrains,

221
00:10:02,480 --> 00:10:05,920
who make developer tools, adds a bit of credibility too.

222
00:10:05,920 --> 00:10:09,680
Speaking of credibility, did we get any sense of how many people are actually using

223
00:10:09,680 --> 00:10:11,440
Lychee? Any stats?

224
00:10:11,440 --> 00:10:14,080
Yeah, the sources had some pretty impressive numbers, actually.

225
00:10:14,080 --> 00:10:17,200
Things like 25,000 direct downloads were mentioned.

226
00:10:17,200 --> 00:10:22,480
Over 300, 700 stars on GitHub that's like a bookmark or a vote of interest in the

227
00:10:22,480 --> 00:10:23,680
open source world.

228
00:10:23,680 --> 00:10:27,280
Around 339 forks, meaning people have copied the code to modify it.

229
00:10:27,840 --> 00:10:33,160
And maybe the most telling one for that Docker ease of use, 3.4 million pulls of

230
00:10:33,160 --> 00:10:34,480
the official Docker image.

231
00:10:34,480 --> 00:10:37,840
Wow, 3.4 million Docker pulls. That's huge.

232
00:10:37,840 --> 00:10:40,960
That really does suggest that Docker method is super popular.

233
00:10:40,960 --> 00:10:43,760
It really does. It shows it's not some tiny niche project.

234
00:10:43,760 --> 00:10:46,960
Oh, and the latest version noted in the material was 6.6.5.

235
00:10:46,960 --> 00:10:50,400
And I think I saw a quick mention of a supporter edition. What's that?

236
00:10:50,400 --> 00:10:54,400
Yeah, that popped up. It seems like an optional paid version that offers some extra,

237
00:10:54,400 --> 00:10:58,320
more advanced features on top of the free open source core.

238
00:10:58,320 --> 00:11:01,760
It's a way for users who need those extra capabilities to get them,

239
00:11:01,760 --> 00:11:05,040
and also presumably to financially support the project's development.

240
00:11:05,040 --> 00:11:09,200
Right, makes sense. Okay, so let's try and wrap this up.

241
00:11:09,200 --> 00:11:12,800
Lightsheet comes across as this really capable open source,

242
00:11:12,800 --> 00:11:16,400
good looking way to manage, share, and view your photos.

243
00:11:16,400 --> 00:11:20,720
The huge differentiator is you host it, giving you total control.

244
00:11:20,720 --> 00:11:24,480
Key things are the flexible uploads, solid organization tools,

245
00:11:24,480 --> 00:11:28,400
including that important metadata support, easy sharing with privacy options,

246
00:11:28,400 --> 00:11:31,520
and a clean viewing experience. And for beginners, the path of least

247
00:11:31,520 --> 00:11:34,880
resistance seems to be definitely using Docker for setup.

248
00:11:34,880 --> 00:11:37,920
Plus, there's documentation and a community if you need help.

249
00:11:37,920 --> 00:11:41,440
Yeah, it really positions itself as a strong alternative if you value that

250
00:11:41,440 --> 00:11:45,200
autonomy and control over your data, moving away from relying solely on big

251
00:11:45,200 --> 00:11:47,920
platforms. Which leads us nicely into our final

252
00:11:47,920 --> 00:11:52,480
thought for you, the listener, to ponder. In this digital age where so much of our

253
00:11:52,480 --> 00:11:55,360
lives, photos, documents, chats ends up living

254
00:11:55,360 --> 00:12:01,280
on servers owned by other companies, what's the real maybe hidden value to

255
00:12:01,280 --> 00:12:04,880
you? What's the value in terms of privacy, long-term security, and just

256
00:12:04,880 --> 00:12:08,160
that feeling of actual ownership over your digital memories,

257
00:12:08,160 --> 00:12:11,680
like your entire photo collection, if you decide to take that step and host

258
00:12:11,680 --> 00:12:14,720
it yourself? It definitely shifts the focus from pure

259
00:12:14,720 --> 00:12:18,160
convenience towards empowerment and ownership, doesn't it? It really does.

260
00:12:18,160 --> 00:12:20,560
Something to think about. And that concludes our deep dive into

261
00:12:20,560 --> 00:12:22,960
Lychee. Thanks again to Safe Server for supporting

262
00:12:22,960 --> 00:12:26,160
us. Remember, they can help with hosting and digital transformation.

263
00:12:26,160 --> 00:12:32,960
Check them out at www.safeserver.de. We'll catch you on the next deep dive.