YouTube2Text

🎙️ 𝐏𝐎𝐃𝐂𝐀𝐒𝐓 | Épisode 3 // Récit de l’auto-hébergement du Low-tech Lab — Transcript

by Low-tech Lab · 6,218 words · 1,000 segments · language en · Watch on YouTube

Full transcript

  1. 0:00The whole goal of this podcast for
  2. 0:03those listening is basically to say: "
  3. 0:05Okay, when we're in a structure, an
  4. 0:08association, or an organization, and we
  5. 0:11notice that our digital environment
  6. 0:14could be better, what are the steps to
  7. 0:17take and the actions to initiate to
  8. 0:20envision a digital environment that is
  9. 0:22more low-tech, more ethical, and also
  10. 0:25more sustainable?" So that’s really
  11. 0:28how we’re going to build this podcast
  12. 0:30, to guide people in their thinking and
  13. 0:33provide them with the major steps for a
  14. 0:36transition toward a digital environment
  15. 0:38that’s more serene and ethical.
  16. 0:40When we first arrived, we realized that
  17. 0:43the digital tools used by the Low-Tech
  18. 0:46Lab weren't very consistent with the
  19. 0:49values they were defending. So we
  20. 0:52wanted to find a better way to make our
  21. 0:55common tools available, like the wiki,
  22. 0:58the website, and so on.
  23. 1:01What if the convivial, sober, and
  24. 1:02sustainable society of tomorrow were
  25. 1:04already here? Welcome to Visage
  26. 1:08Low-Tech, the podcast that opens the
  27. 1:10door a crack and shows you this joyful
  28. 1:12society springing up all over the
  29. 1:14country. Here, we head out to meet
  30. 1:16those who are experimenting with and
  31. 1:17spreading low-tech in their daily lives
  32. 1:19. We want to show you concrete,
  33. 1:21practical applications of the low-tech
  34. 1:23approach to inspire you and make you
  35. 1:25want to connect with others in your
  36. 1:27area. So today on Visage Low-Tech, I am
  37. 1:32hosting Marion Bouder and Nathanael Le
  38. 1:34Prête. Nathanael and Marion are in
  39. 1:36charge of what we call, in our jargon,
  40. 1:38the "common tools" at the Low-Tech Lab.
  41. 1:40They ensure that all the low-tech
  42. 1:42knowledge we aggregate here and have
  43. 1:44been providing open access to since
  44. 1:452013 is well-documented and
  45. 1:46disseminated. And first off, I'd like
  46. 1:49us to clarify what we mean in our
  47. 1:51jargon by "common tools," whether
  48. 1:54digital or not. Could you tell us a
  49. 1:56little bit about what you do at the
  50. 1:57Low-Tech Lab? "Common tools" refers to
  51. 2:01all the tools used by the network team,
  52. 2:05the communities, and more broadly, the
  53. 2:09general public who mostly visit the
  54. 2:12wiki, which was launched in 2017-2018
  55. 2:16during the first Nomade des Mers
  56. 2:19expedition and was set up to publicly
  57. 2:22document all the low-tech discovered
  58. 2:26along the way. Could you tell us a
  59. 2:29little bit about what you noticed when
  60. 2:32you arrived, and what digital projects
  61. 2:35you started to envision for the future
  62. 2:38within the Low-Tech Lab? Well, when we
  63. 2:42arrived, we realized that the digital
  64. 2:44tools used by the Low-Tech Lab weren't
  65. 2:47very consistent with the values they
  66. 2:50were defending. So that's something
  67. 2:53that surprised us a little bit. And in
  68. 2:55fact, the Low-tech Lab essentially uses
  69. 2:57software and applications that are
  70. 3:00proprietary and run in big data centers
  71. 3:03, uh, which centralize that data and
  72. 3:05also centralize the energy needed to
  73. 3:08run them. And so that struck us because
  74. 3:10, uh, it was inconsistent with the
  75. 3:13Low-tech Lab's overall approach. Indeed
  76. 3:16, the problem with data centers is that
  77. 3:19you aggregate many machines in one
  78. 3:22place that require a lot of energy, and
  79. 3:25so that also requires high-tech
  80. 3:27engineering to produce energy for the
  81. 3:30data centers. There's an inconsistency
  82. 3:34in having our common tools for
  83. 3:38communicating with the general public
  84. 3:42hosted in large spaces that consume a
  85. 3:46lot of land, cause soil
  86. 3:49artificialization, and require a lot of
  87. 3:53high-tech for the result, really. So,
  88. 3:58we wanted a more low-tech way to make
  89. 4:01common tools available, like the wiki,
  90. 4:05the website, and so on. You, uh, we
  91. 4:08need to introduce you because,
  92. 4:11precisely, perhaps the profiles that
  93. 4:13were at the Low-tech Lab historically
  94. 4:16were engineer profiles from design
  95. 4:18offices who, well, you can't wear every
  96. 4:21hat, and maybe didn't have that
  97. 4:24slightly geeky side or weren't really
  98. 4:26focused on digital usage. I don't know
  99. 4:30if it's intentional that we don't
  100. 4:32necessarily cite the tools or not, but
  101. 4:34it's true that we arrived at a Low-tech
  102. 4:37Lab that uses Google Drive. Our
  103. 4:39presentations are made with the office
  104. 4:42suite tool internal to Google Drive.
  105. 4:46It's true that you wanted to update
  106. 4:49that, and that's the whole heart of our
  107. 4:51podcast, this transition from
  108. 4:53proprietary tools, as you say Marion,
  109. 4:56or even sometimes Big Tech, to open
  110. 4:58source, and that's where you're going
  111. 5:01to introduce yourselves quickly. But
  112. 5:04first, shouldn't I take a moment to
  113. 5:06tell our listeners where we are,
  114. 5:08because it's quite a unique and nice
  115. 5:10place, and perhaps a bit low-tech too,
  116. 5:13I don't know. Nathanel, you're hosting
  117. 5:16us, uh, in your environment here in
  118. 5:18Lorient, and I might let you take the
  119. 5:20floor to introduce, well, the shared
  120. 5:22roofs where we are located, and perhaps
  121. 5:25before that I'll start with a
  122. 5:27description and you can correct me if,
  123. 5:29uh, I make any mistakes. If I
  124. 5:31understand correctly, we're in a
  125. 5:34residence that was built a year or two
  126. 5:37ago, I don't remember exactly. About
  127. 5:40fifteen or twenty, or fifteen
  128. 5:42households moved in here last year. You
  129. 5:46have common areas, uh, shared under
  130. 5:49these roofs. Today, we are working in
  131. 5:52the common room that you reserved for
  132. 5:54us. There's a shared vegetable garden,
  133. 5:56too. There's compost, we have
  134. 5:58composting toilets, and it's quite
  135. 6:00green as well. It's a very pleasant
  136. 6:03environment, very contemporary, too.
  137. 6:05Honestly, I'm always quite charmed when
  138. 6:08I arrive here at your place, and it's a
  139. 6:10project that I feel took 10 years to
  140. 6:12come to life, having been thoughtfully
  141. 6:15designed through collective
  142. 6:16intelligence. That's what I've
  143. 6:19understood of it. But can we really
  144. 6:22take a quick minute or two? Well, with
  145. 6:26a few adjustments, you've said almost
  146. 6:28everything; it's a 15-year project. The
  147. 6:31first time the residents of that time,
  148. 6:34the future residents of that time,
  149. 6:37gathered was in 2010 with the actual
  150. 6:40idea of creating participatory housing
  151. 6:44where the goal isn't just to live next
  152. 6:47to your neighbor, but to really know
  153. 6:50and share time with your neighbor. And
  154. 6:54then along the way, they were pioneers
  155. 6:57in a field in France which is the
  156. 7:01housing cooperative. Now, it's a model
  157. 7:04that is very widespread in other
  158. 7:06countries, notably Switzerland, but in
  159. 7:08France, it's almost non-existent for
  160. 7:10political reasons. And this concept is
  161. 7:14that the residents group themselves
  162. 7:18into a cooperative society that owns
  163. 7:21the building. And the residents are the
  164. 7:26tenants. So they are both collectively
  165. 7:29owners and individually tenants of
  166. 7:31their own cooperative. Which allows us
  167. 7:35to take the building out of the real
  168. 7:37estate market and real estate
  169. 7:40speculation. And then, since we built
  170. 7:43our building for ourselves, we tried to
  171. 7:47build it well, so it's rated A ++++ in
  172. 7:51energy performance certificates and
  173. 7:54other rankings. Uh, we built it with
  174. 7:57wood, wood insulation. Uh, so it's
  175. 8:01pleasant to live in, with good, good
  176. 8:05soundproofing too, because that was
  177. 8:08something very important for the
  178. 8:12residents.
  179. 8:13Uh, because we live in an
  180. 8:15intergenerational setting, and so there
  181. 8:17are needs for calm, you know, for
  182. 8:20silence, for calm or...
  183. 8:21for festivity, conversely.
  184. 8:23And as the pioneers wanted, as it was
  185. 8:25planned from the start, we therefore
  186. 8:27have common areas. We have a shared
  187. 8:29laundry room. No one has a washing
  188. 8:32machine at home. Uh, we have four for
  189. 8:35the whole building. We have 12
  190. 8:37households,
  191. 8:3820 people including the children.
  192. 8:41Uh, two guest rooms, because it's
  193. 8:45pointless for people
  194. 8:48living alone to have a guest room for
  195. 8:50themselves, whereas for hosting family
  196. 8:52once a year, well, the idea is to have
  197. 8:55guest rooms. OK. Very good. Shared.
  198. 8:58communal, in which we are currently
  199. 9:01here today to work together as a team.
  200. 9:04OK.
  201. 9:04And also the workshop you saw earlier
  202. 9:08next to the garden. OK.
  203. 9:12Can you save us?
  204. 9:13Ah yes, that's right. The hot water is
  205. 9:16solar heated. We're in the Lot region.
  206. 9:18We also have photovoltaics. It's a bit
  207. 9:20less low-tech, but it allows for local
  208. 9:22energy production.
  209. 9:23Well, listen, yeah, we can close that
  210. 9:25little parenthesis, but
  211. 9:28well, I can make a pretty nice
  212. 9:30transition, because as for shared
  213. 9:33things, we host our data on a computer
  214. 9:35that is self-hosted and where the
  215. 9:38residents use common tools. There you
  216. 9:41go. So, an easy transition.
  217. 9:42That's funny. Who could have set up
  218. 9:45this system? One wonders.
  219. 9:48OK. Uh, OK. And so, well, first of all,
  220. 9:53this podcast is called "Visages
  221. 9:55Low-tech." So it's also to introduce
  222. 9:58new faces. Uh, so what will interest us
  223. 10:01is also to introduce you. Mario, can
  224. 10:05you tell us briefly who you are and now
  225. 10:07that you're at Low-tech Lab? Well, I
  226. 10:11grew up in a household where I always
  227. 10:13saw a computer, and I was always
  228. 10:15fascinated by human-machine interaction
  229. 10:18. I thought it was great, and I
  230. 10:20believed in it, so very quickly I
  231. 10:22became interested in the uses we could
  232. 10:24make of the computer so that it would
  233. 10:26be enabling for everyone. So, I
  234. 10:28directed my studies and professional
  235. 10:31experiences toward usage, accessibility
  236. 10:34, and digital access, and. And that's
  237. 10:37how I was drawn to the offer from the
  238. 10:39Low-tech Lab, which was to get hands-on
  239. 10:42with common tools and, among other
  240. 10:44things, the uses of these common tools.
  241. 10:46So that's how I arrived here.
  242. 10:50Yeah. And you, Nathanel?
  243. 10:52Well, for me, it happened later. Uh, IT
  244. 10:55was a constraint in the beginning, and
  245. 10:59then, while traveling around the world,
  246. 11:03I wanted to master my blog and my tools
  247. 11:06, so I looked into how it all worked.
  248. 11:10Uh, and since I had been following what
  249. 11:14Framasoft was doing for some time,
  250. 11:17that's how I got into free software,
  251. 11:20then self-hosting, and I met the "
  252. 11:23Chatons." Maybe we'll come back to that
  253. 11:26later. Well, actually, I'm even one of
  254. 11:29the founders of Les Châtons with
  255. 11:32Framasoft, and then when I returned
  256. 11:35from my travels, I was hired by Marion
  257. 11:38seven years ago now. And so, I got into
  258. 11:42digital technology a bit more
  259. 11:44professionally with her, and after that
  260. 11:47, we didn't part ways; we started an
  261. 11:50association in the digital field, and
  262. 11:53then we joined the Low-Tech Lab when we
  263. 11:56saw the job offers that really appealed
  264. 11:59to us. Yes, yes, it's funny because I
  265. 12:02think the Low-Tech Lab was looking for
  266. 12:04one person to manage their digital
  267. 12:07tools, and they got two because you
  268. 12:09always come in pairs.
  269. 12:11That's right.
  270. 12:12We offered to split the job in two
  271. 12:14because our skills are complementary.
  272. 12:17So, it matched the offer quite well and
  273. 12:20allowed us to keep our other digital
  274. 12:22activities on the side.
  275. 12:24Great. So, you introduced yourselves in
  276. 12:27one big paragraph. Now, I'll try a
  277. 12:28slightly harder exercise. If you had to
  278. 12:31describe yourselves in two opposing
  279. 12:33adjectives.
  280. 12:35Well, I would say never late, always
  281. 12:37right on time. Ah.
  282. 12:39Yes, okay. That fits you pretty well,
  283. 12:44it works.
  284. 12:45And I would say I am solastalgic, yet
  285. 12:49optimistic.
  286. 12:51Uh, it's not nostalgic, it's
  287. 12:53solastalgic. So, it's linked to
  288. 12:56nostalgia, it's the fact of regretting
  289. 12:59losses that have occurred that we
  290. 13:02didn't experience, such as the
  291. 13:04disappearance of species, the changing
  292. 13:07climate, landscapes we won't see
  293. 13:10anymore but that did exist. We know
  294. 13:13they existed and we miss them.
  295. 13:15Because we didn't experience them
  296. 13:17precisely because we didn't know them.
  297. 13:20Which is different from nostalgia,
  298. 13:22where you regret something you did
  299. 13:24experience.
  300. 13:26Okay, great. Okay, so now we are going
  301. 13:28to dive into the heart of the podcast.
  302. 13:30We will try to explain, first of all,
  303. 13:32the steps you decided to take and in
  304. 13:35what order, based on the respective
  305. 13:37observations you made at the Low-Tech
  306. 13:40Lab. Having a site hosted at OVH in
  307. 13:43France, I didn't think it was
  308. 13:45necessarily scandalous. Or using, well
  309. 13:48yes, sharing files on Google Drive, we
  310. 13:50know it's really not ideal, but we are
  311. 13:53looking for alternatives. Do we have
  312. 13:56robust tools to replace that? Beyond
  313. 14:00the tools and the processes we
  314. 14:02implement, I would like us to return to
  315. 14:04what is really at stake politically and
  316. 14:07ethically in these choices we make. Why
  317. 14:10hosting your site with OVH is good, but
  318. 14:13if you want to be low-tech and be a bit
  319. 14:16more exemplary, you have to go even
  320. 14:19further. What’s really at stake here?
  321. 14:21Well,
  322. 14:23technically, it's true that there are
  323. 14:28three levels for IT and hosting; you
  324. 14:33can take the simplest path and be
  325. 14:38hosted by highly redundant tools,
  326. 14:41hosted in something a bit obscure
  327. 14:44called the cloud, which we don't really
  328. 14:48know how it works. But it seems to work
  329. 14:53, and the data is replicated across a
  330. 14:56bunch of servers in different data
  331. 14:59centers around the world. So here,
  332. 15:03we're at a level of high-tech and
  333. 15:06complexity that is truly maximal. In a
  334. 15:09second level, you can effectively
  335. 15:12choose to host yourself in a single,
  336. 15:16more local data center like OVH, where
  337. 15:19you already regain control over your
  338. 15:23digital tools and data. And then, in a
  339. 15:27third level, you regain control over
  340. 15:30the materiality of digital tech, sort
  341. 15:33of like getting your hands dirty with a
  342. 15:37bike or working on a car engine
  343. 15:40yourself. Whereas with very modern cars
  344. 15:42today, well, you can't do anything, and
  345. 15:44even mechanics can't do anything; you
  346. 15:46have to go to the dealership. Well,
  347. 15:48that’s the same idea, and so if you
  348. 15:51want, from a low-tech perspective, to
  349. 15:54regain control over technology, you
  350. 15:57have to move toward self-hosting where
  351. 16:00you master your server, even at the
  352. 16:02hardware level. Now, it's true that in
  353. 16:06exchange, you have to accept that
  354. 16:09sometimes the service won't be
  355. 16:11accessible for a while, but that's
  356. 16:14something we need to work on as a
  357. 16:17society.
  358. 16:19Speaking of sites that don't always
  359. 16:22work, there's also the Low-Tech
  360. 16:25Magazine, which runs from Barcelona
  361. 16:27using solar panels when there's sun.
  362. 16:30Fortunately, they have a bit more than
  363. 16:31we do in Brittany. But
  364. 16:33exactly, that's the idea.
  365. 16:34I find it incredibly charming to accept
  366. 16:37that a digital service might be
  367. 16:40unavailable because there's no sun. It
  368. 16:43really teaches us about behaviors and
  369. 16:45expectations that we don't have much of
  370. 16:48anymore in our collective impatience.
  371. 16:52Very well. So, I really want to get
  372. 16:54into the heart of the matter. Could you
  373. 16:58describe the various steps you followed
  374. 17:01to accomplish this entire digital
  375. 17:05transformation of the Low-Tech Lab over
  376. 17:08the last few months? I'd just like to
  377. 17:13add one small thing, which is that
  378. 17:16moving away from big tech, GAFAM, and
  379. 17:19other similar major corporations is
  380. 17:21also well, being a fervent defender of
  381. 17:25those who can fuel fascism today, and
  382. 17:28that's also a position we either want
  383. 17:30to take or not. But it's interesting to
  384. 17:33keep that notion in mind because these
  385. 17:35large companies are the ones shaping
  386. 17:38the world of tomorrow, and not
  387. 17:40endorsing what they do is also a form
  388. 17:42of defense.
  389. 17:44Yeah, that's quite relevant, indeed. Uh
  390. 17:46,
  391. 17:46there, that was a little side note.
  392. 17:48Yeah. Yes.
  393. 17:49Politico-strategic, let's say. Yeah,
  394. 17:52for sure. And a sovereignty issue, well
  395. 17:56, when we were talking about what's
  396. 17:58really at stake here. And so,
  397. 18:01afterwards, we did it step by step: we
  398. 18:05started by migrating calendars,
  399. 18:07migrating contacts; the biggest part
  400. 18:09was migrating files, where we migrated
  401. 18:12data from Google to a more open
  402. 18:14solution. So, the solution we're using,
  403. 18:18well, maybe we'll come back to it, but
  404. 18:22we're on a solution based on the
  405. 18:25software Nextcloud, which is an
  406. 18:28application that allows you to store,
  407. 18:32and not just store, but manage your
  408. 18:35data. So once we migrated those files,
  409. 18:39the next step was obviously to support
  410. 18:42the transition in usage.
  411. 18:45Yeah, because—if I may add a side
  412. 18:47note—when you migrate all your Google
  413. 18:50Drive documents, which are designed
  414. 18:52with Google Sheets, Google Slides,
  415. 18:54Google Docs, or whatever the Word
  416. 18:56equivalent is called, but uh
  417. 18:59yeah, each of those files, and if you
  418. 19:02have 1,800 of them, you have to convert
  419. 19:05them.
  420. 19:06Exactly. You have to convert them all
  421. 19:08and then export them. So there was a
  422. 19:10bunch of scripts, maybe not manual, I
  423. 19:12assume, but
  424. 19:12there was a lot of work from Nathanael
  425. 19:15on the technical side to convert and
  426. 19:18then migrate all those documents, and
  427. 19:21then verify that everything was
  428. 19:23properly converted and migrated.
  429. 19:26And we're still in an analysis phase
  430. 19:29before deleting all our documents and
  431. 19:32folders from Google. We're still
  432. 19:35analyzing whether we've migrated
  433. 19:37everything correctly and with the right
  434. 19:39formats.
  435. 19:40Going through 10, even 13 years of
  436. 19:43association communication files, seems
  437. 19:46like a pretty pretty significant task,
  438. 19:50but ultimately, every time I open one,
  439. 19:52the conversion seems to have been done
  440. 19:55well, and it's doable. Google puts
  441. 19:57spokes in our wheels;
  442. 19:58they don't make the job easy, to say
  443. 20:00the least. In terms of timeline, it
  444. 20:03might seem monumental, but you were
  445. 20:06still incredibly efficient from the
  446. 20:08moment you said "that's it, we're
  447. 20:10migrating, converting, and
  448. 20:12re-transferring," it's just a few weeks
  449. 20:14. Well,
  450. 20:15initially, we planned for 2 days, it
  451. 20:18took us 3 weeks.
  452. 20:20Close enough.
  453. 20:21Roughly.
  454. 20:22Uh, it's true that at the beginning, I
  455. 20:26didn't know the Google environment; I
  456. 20:28had never worked with it. And I told
  457. 20:30myself, well, I'll just download all
  458. 20:32the files and then re-import them. That
  459. 20:36seems quite natural, shall we say,
  460. 20:38quite logical. But the thing is, Google
  461. 20:41, having no interest in that obviously,
  462. 20:44doing everything to keep people on
  463. 20:46their platform, doesn't provide any
  464. 20:48information on the quantity of files or
  465. 20:51the amount of data there is, or it
  466. 20:53provides contradictory information that
  467. 20:56is very complicated to...
  468. 20:57It's organized by folder, but you don't
  469. 21:00know what's in the folders.
  470. 21:02That's it. You can't know how much
  471. 21:04space a folder takes up or how much it
  472. 21:06...
  473. 21:07You can't know. You have to download it
  474. 21:08to find out. And then, effectively
  475. 21:11downloading, well, you end up with
  476. 21:15files that aren't necessarily converted
  477. 21:17. Uh, in short, it's quite complicated.
  478. 21:20Uh, so you really have to use a
  479. 21:21dedicated tool for that. Uh, which tool
  480. 21:25? Well, free software, obviously. Uh,
  481. 21:29but uh since we don't know how much
  482. 21:33data we're going to download, I, quite
  483. 21:35simply, saturated my disk. Uh, so there
  484. 21:38, I had to get another disk until I
  485. 21:41found a disk that was large enough to
  486. 21:44hold all the data. So, that's a setback
  487. 21:47, we lose time, we start over. Uh, and
  488. 21:50then, uh for obscure reasons, there are
  489. 21:55files that won't be converted during
  490. 21:57the transfer. So you have to go back at
  491. 22:00the end, redo them, search to find the
  492. 22:02ones that weren't converted. And then
  493. 22:05afterwards, there are all the little
  494. 22:06joys of amusing things like files that
  495. 22:11have long-winded names, which then
  496. 22:15interrupt the entire migration process
  497. 22:19because the process finds an error and
  498. 22:23stops because the file name is too long
  499. 22:27.
  500. 22:28Uh, and sometimes, I saw whole
  501. 22:30sentences used as file names.
  502. 22:31There you go. Alright. If we go back to
  503. 22:35the steps, yes, we were at this whole
  504. 22:38migration of files, even the migration
  505. 22:41of the calendar, contacts, and files.
  506. 22:45Uh, if you have anything else to say
  507. 22:46about that, don't hesitate. Otherwise,
  508. 22:48if I pick up the thread after that,
  509. 22:50there is the support for usage. And I
  510. 22:52feel like that's where you're
  511. 22:54supporting us by saying, "Well, here
  512. 22:56you go, we've done the job." Do you
  513. 22:58approve? Are you finding everything you
  514. 23:00need? Regarding the files you're
  515. 23:03responsible for, do you have all your
  516. 23:06documents, or does this new tool, the
  517. 23:10LibreOffice, well, the Nextcloud tool
  518. 23:13that takes over from Google Sheets or
  519. 23:16replaces our file formats. Have you
  520. 23:19managed to get the hang of them?
  521. 23:21Because, similarly, we're also trying
  522. 23:24to move away from Microsoft or Keynote
  523. 23:26for our presentations. We're switching
  524. 23:29from PowerPoint to open-source software
  525. 23:31. Basically, we're relearning all our
  526. 23:34digital habits to try and be more
  527. 23:37consistent with our values. So we're in
  528. 23:40this space, and it's both exciting and
  529. 23:43challenging for us. I mean, in terms of
  530. 23:46productivity, we have to accept slowing
  531. 23:49down, being a bit less productive,
  532. 23:52learning a new piece of software, the
  533. 23:54open-source equivalent to PowerPoint,
  534. 23:57what's the suite called?
  535. 23:59Collabora Online, which is installed on
  536. 24:02Nextcloud.
  537. 24:03Colab, which is, yes. Which is
  538. 24:04suggested by Nextcloud for usage, right
  539. 24:06? It's one of the tools, one of the
  540. 24:09office suites that's a collaborative
  541. 24:12online version, and so we can integrate
  542. 24:15it into Nextcloud. And that's what we
  543. 24:17did for our current needs. We're using
  544. 24:19a free version. For future needs, we'll
  545. 24:22see over time, but for now, the free
  546. 24:24version is enough for us.
  547. 24:26And regarding the country behind it, is
  548. 24:28it European, is it a specific country,
  549. 24:31or are we not quite sure?
  550. 24:32It's English, English as well. Okay.
  551. 24:36Okay. And the free aspect actually
  552. 24:38depends on the number of users. Unless
  553. 24:42the Nextcloud instance becomes massive,
  554. 24:46we'll stay on the free version.
  555. 24:47There you go.
  556. 24:48And Nextcloud is a German solution,
  557. 24:50originally. It was German developers
  558. 24:53who developed it,
  559. 24:55a few years ago now. And that's the
  560. 24:57question I asked myself when we started
  561. 25:00all of this. I have a bit of, how do
  562. 25:04you say it? I think within the team, I
  563. 25:08needed to be reassured about the
  564. 25:10robustness of an open-source tool, how
  565. 25:13long it's been around. How long have
  566. 25:15they been around? Will they still be
  567. 25:17here in three years? Often these are
  568. 25:21fairly loose, fragile structures that
  569. 25:24rely on donations, and how do we
  570. 25:27reassure an organization by saying, "No
  571. 25:30, it's not a capitalist monster sitting
  572. 25:33on a huge pile of capital that keeps it
  573. 25:37secure for the next 50 years." But
  574. 25:40still, it seems to us to be the most
  575. 25:43robust thing right now and the one to
  576. 25:46strive for. Well, actually, it's
  577. 25:49because there's an image that has
  578. 25:51likely been created, because
  579. 25:53open-source software is what runs the
  580. 25:55vast majority of the digital world
  581. 25:57today. A vast majority of mobile phones
  582. 26:02, smartphones, run on Android. We say
  583. 26:06Android is Google. Except that 90%of
  584. 26:08the code in Android is Linux. It's
  585. 26:12open-source software. Only the
  586. 26:14proprietary commercial overlay belongs
  587. 26:19to Google. And that's how it is for the
  588. 26:22vast majority of the digital world.
  589. 26:25Today, most servers that power the
  590. 26:29world's websites run on Debian or
  591. 26:32another Linux distribution, which is
  592. 26:36open-source software, and a site using
  593. 26:41a CMS called WordPress, which manages
  594. 26:4540%of global internet traffic. It's
  595. 26:49open-source software. And yet it runs
  596. 26:54the planet, and it lasts for a long
  597. 26:56time.
  598. 26:57Yes. So for you, in scenarios where an
  599. 27:00actor disappears and leaves us a bit in
  600. 27:02the lurch, there will always be...
  601. 27:05It can happen.
  602. 27:06Yeah. Yeah.
  603. 27:07But no more or less than a big company
  604. 27:10developing software. Yeah.
  605. 27:14The software we've chosen to use for
  606. 27:17the Lot Club are proven programs that
  607. 27:20have developer communities that are,
  608. 27:24yeah. that are really solid. They have
  609. 27:26a foundation that's been there for
  610. 27:27several years. We aren't getting into
  611. 27:30open-source software that's new,
  612. 27:31unproven, and so on. Yeah.
  613. 27:33The idea isn't to put the Lot at a
  614. 27:35disadvantage, but to show that with
  615. 27:38existing tools and what's being done
  616. 27:40today, it's possible and it works.
  617. 27:43As Marion said, we talk about community
  618. 27:45, a bit like in the Lot, we have LCHC
  619. 27:47communities, and that's how you see the
  620. 27:49maturity of a piece of software and its
  621. 27:51longevity. It's more about that than a
  622. 27:53company that might be behind it. If
  623. 27:55there's a large community of developers
  624. 27:58and users, in principle, the software
  625. 28:00will be long-lasting.
  626. 28:02Yeah. Yeah. Yeah. Exactly. And so in
  627. 28:05this step, to pick up our thread again,
  628. 28:09we were at support for usage. Uh,
  629. 28:12you're also working on documenting all
  630. 28:15of this. We’re documenting it here
  631. 28:18with audio in a podcast, but you're
  632. 28:20working on written documentation that
  633. 28:23could guide organizations wanting to
  634. 28:26start this process. I’m wondering, if
  635. 28:30we don't have Marion or Nathanael
  636. 28:34around, is it something you can set up
  637. 28:38quite easily if you’re just a bit
  638. 28:42savvy with IT tools? The idea behind
  639. 28:46this documentation is to show what we
  640. 28:48were able to do with the skills we had
  641. 28:50in-house. But it’s also to show
  642. 28:52what’s possible with fewer skills,
  643. 28:54and the types of providers you can turn
  644. 28:57to if you don't have those skills
  645. 28:58in-house. Hm.
  646. 28:59Hm.
  647. 29:00There are plenty of those providers in
  648. 29:02the region. Identifying them is more
  649. 29:04difficult when you aren't from the
  650. 29:06open-source community. But in this
  651. 29:09documentation, we’ll include a
  652. 29:12non-exhaustive list of actors capable
  653. 29:15of supporting organizations locally
  654. 29:19with self-hosting their data, just as
  655. 29:22we propose. Exactly. The documentation
  656. 29:25has two goals. It’s to provide an
  657. 29:27overview of our approach, how we went
  658. 29:31about it, and what the results were, as
  659. 29:34well as to offer entry points for
  660. 29:37communities that have the necessary
  661. 29:40human resources or external partners.
  662. 29:43And like you said, it’s about
  663. 29:45providing reassurance; when you have a
  664. 29:48well-made tutorial, which we’re
  665. 29:50trying to create,
  666. 29:52it makes it less daunting to embark on
  667. 29:54the adventure.
  668. 29:56As I said when I introduced myself, I
  669. 29:59don't come from a tech background, so I
  670. 30:02learned as I went by doing things, and
  671. 30:05I definitely made some mistakes.
  672. 30:09That’s actually what allowed me to
  673. 30:11learn how to do self-hosting. And well,
  674. 30:14if a helping hand is needed, we’re
  675. 30:16here for that too,
  676. 30:18to support communities. There’s
  677. 30:19mutual aid, but that’s the whole "
  678. 30:21low-tech" culture, really—it started
  679. 30:23from that "do it yourself" mindset,
  680. 30:25understanding your technology, and
  681. 30:27benefiting from others 'experiments.
  682. 30:29And documenting it. And for us, our
  683. 30:32goal is surely to create documentation
  684. 30:34that evolves along with how it's used.
  685. 30:38And I see the next step, after
  686. 30:41supporting the usage, is precisely,
  687. 30:44once the whole new culture has spread
  688. 30:46and infused the organization, uh, to
  689. 30:49think about it, you...You say the next
  690. 30:52step is a bit about adding new features
  691. 30:55...uh, well, that's counting new tools.
  692. 30:58Actually, once we're comfortable with
  693. 31:01the base, we'll gradually add new
  694. 31:04features, new applications that are
  695. 31:06interesting and that could possibly
  696. 31:09improve productivity, even if that's
  697. 31:12not the goal. But administratively, if
  698. 31:14we can become autonomous in accounting
  699. 31:16and administrative management, that's
  700. 31:18great. So, uh, that's it, it's adding
  701. 31:21new tools and/or applications
  702. 31:23integrated into Nextcloud, possibly to
  703. 31:26make our daily lives easier. And the
  704. 31:31difference is that before, for
  705. 31:32everything it was done independently.
  706. 31:37We had a need, and well, we would pick
  707. 31:40software that met that need, but
  708. 31:43without any cohesion within the common
  709. 31:46ecosystem of digital tools. Uh, the
  710. 31:50idea here is that by taking back
  711. 31:52control of what already exists, we will
  712. 31:56then be able to develop, or have
  713. 31:58developed, or install existing software
  714. 32:01that is consistent with what we already
  715. 32:05have.
  716. 32:05Yeah. Yeah. Yes, and it's true that in
  717. 32:08my usage, I was using just about
  718. 32:09anything and everything. And it reminds
  719. 32:12me of the moment I showed you what a
  720. 32:14Linktree was for the Instagram account
  721. 32:18where you were a bit stunned that there
  722. 32:20were proprietary services for inventing
  723. 32:23something so simple that had already
  724. 32:25been invented at the birth of the
  725. 32:27internet.
  726. 32:29But it's true that a Linktree, why not
  727. 32:31build it yourself?
  728. 32:33Completely. Yes, I really
  729. 32:38I read the distress in your eyes. Why
  730. 32:41do you need that, Xavier?
  731. 32:44Uh, okay. Uh, so I think we've gone
  732. 32:47through the steps a bit. Uh, what I
  733. 32:50also wanted, a bit like a recipe, was
  734. 32:54for us to visualize a bit what you
  735. 32:58needed to set all this up, even in
  736. 33:02terms of hardware: what are the
  737. 33:05ingredients? And maybe even a little
  738. 33:08budget sheet, what kind of amount are
  739. 33:11we talking about to set all this up? To
  740. 33:15put it simply, we needed five essential
  741. 33:18things, which are a computer that acts
  742. 33:20as a server, an internet connection,
  743. 33:23preferably fiber for a smooth
  744. 33:25experience in using the tools,
  745. 33:27a domain name
  746. 33:29which was already existing in this case
  747. 33:31, but if you're setting up your own
  748. 33:33community, well, it will be important.
  749. 33:35Uh, something to do remote backups, so
  750. 33:39provide a hard drive that allows for
  751. 33:43backing up and a subscription for an
  752. 33:46email relay. If you want to self-host
  753. 33:49your emails and not depend on anyone,
  754. 33:52you absolutely must have a relay to get
  755. 33:54through the Microsoft, Google, and
  756. 33:56other filters. So there you go, those
  757. 33:59were the five really essential things.
  758. 34:01Yeah. Yeah. And the budget, uh, it cost
  759. 34:05us, uh
  760. 34:06about € 350
  761. 34:09for the purchase and then for usage. Uh
  762. 34:11, as for the email relay, which allows
  763. 34:15you to have a good reputation as an
  764. 34:18email server, which is hard to get when
  765. 34:22you're self-hosting. So it's good to go
  766. 34:25through a provider for that, and there
  767. 34:27are some very good ones. Uh, it
  768. 34:30currently costs us € 50 per year. If
  769. 34:34we ever, and that's the intention,
  770. 34:36scale it up a bit, share it with other
  771. 34:39communities, and so on, it will cost us
  772. 34:41a little bit more, maybe up to € 200
  773. 34:44or € 300 per year. Uh, but it's
  774. 34:48something that has its value. Knowing
  775. 34:52that it also advantageously replaces a
  776. 34:55newsletter provider, for example, which
  777. 34:57would cost about the same price for a
  778. 35:00mass email send. Typically,
  779. 35:03we had SAP
  780. 35:04that we had before.
  781. 35:06We're now switching to List. Yes,
  782. 35:08that's it. It's it's List that asks you
  783. 35:10for that price to, uh, kind of
  784. 35:14authenticate. Well, List
  785. 35:18but, on the other hand, to be able to
  786. 35:21send emails in a way that's acceptable
  787. 35:24to
  788. 35:25Big Tech, you have to go through an IP
  789. 35:27address. Uh, the IP address is the
  790. 35:31equivalent of a physical postal address
  791. 35:34in the physical world.
  792. 35:36Well, the IP address is what addresses
  793. 35:38a machine in the digital world, and it
  794. 35:41needs to have a good reputation to be
  795. 35:44accepted by Big Tech
  796. 35:46and for it to land in the mailboxes.
  797. 35:48And that it lands well in the right
  798. 35:50mailboxes. Whereas if you self-host,
  799. 35:52well, your IP address has an unknown
  800. 35:54reputation, and Big Tech will block it
  801. 35:56quite easily.
  802. 35:57Yeah. So you're talking about this
  803. 35:59annual cost a bit. Uh, the cloud, we
  804. 36:01don't have it either, our cloud, does
  805. 36:05it have a cost? I don't know how much
  806. 36:08fiber cost, it has a hardware cost, but
  807. 36:10it didn't cost us more than € 250.
  808. 36:13Yeah, because it's really on our own
  809. 36:16server.
  810. 36:16Yeah, it's our Nextcloud, our cloud on
  811. 36:20our server machine with
  812. 36:22because that was an expense of, I think
  813. 36:25, 2 terabytes on a Google Drive, it's
  814. 36:2810 € per month. That's 120 € saved
  815. 36:32per year. Well, it's more than that
  816. 36:35because actually we had Google Drive
  817. 36:37costs, but we also had OVH costs
  818. 36:39and we also had costs from Infomaniak,
  819. 36:41which is a competitor to OVH. So, in
  820. 36:44fact, all those costs will eventually
  821. 36:47no longer exist. Exactly, they are
  822. 36:49still ongoing for this year, but
  823. 36:50eventually they won't exist anymore.
  824. 36:52And so this saving, what we pay every
  825. 36:55year, is equal to our one-time startup
  826. 36:58investment for our server.
  827. 37:01And afterwards, the only costs will be
  828. 37:03the electricity to run the server and
  829. 37:04the fiber internet. But we use the
  830. 37:06fiber for work anyway. So
  831. 37:08what are you planning in terms of I
  832. 37:12don't know, backups, or just since
  833. 37:14everything is physically based? Well,
  834. 37:16in this case, in Concarneau at the
  835. 37:18office. Um, if, uh, lightning strikes,
  836. 37:22or, well, if we burn out the server, is
  837. 37:26there a quarterly backup, or what do we
  838. 37:29, what do we, um
  839. 37:30how do we secure things a bit, um
  840. 37:32there is a digital backup rule called
  841. 37:35the 3-2-1 rule. Sorry. It's having data
  842. 37:38in three different places on two
  843. 37:41different media, including one offsite.
  844. 37:44That's right.
  845. 37:45And
  846. 37:46and today, we follow that. Which means
  847. 37:48we have our data on a main disk, these
  848. 37:51data are duplicated on a second disk in
  849. 37:54the same machine, and there is a third
  850. 37:57duplication, a second duplication, on
  851. 37:59an external server which is in Lorient.
  852. 38:02On a server in Lorient.
  853. 38:04Yeah. And, uh, so if the machine burns
  854. 38:06out or gets stolen, we have the
  855. 38:09external backup. If the first disk
  856. 38:11fails, the second disk takes over and
  857. 38:14we then replace the first disk. So, in
  858. 38:16fact,
  859. 38:17whether it's against theft, a failure,
  860. 38:20a fire, or anything else, we will
  861. 38:22always have a solution to restore the
  862. 38:25data.
  863. 38:26And for that, there is a script that
  864. 38:28automates it a bit
  865. 38:29at midnight, we have a remote backup.
  866. 38:33At worst, we lose 24 hours of data.
  867. 38:35Ah, yes, yes. OK.
  868. 38:37Uh, that's what we were saying earlier
  869. 38:39about the essential things, the five
  870. 38:41essential things. So there was the
  871. 38:43server, there was the email relay, and
  872. 38:45there was the backup. And that is where
  873. 38:47you need to find service providers when
  874. 38:50you want to do self-hosting. For email
  875. 38:53relaying, you generally need to go
  876. 38:54through a pro, and there are some very
  877. 38:56good ones, especially within the "
  878. 38:57Châtons" network. And off-site backups
  879. 39:01can be done via self-hosting with
  880. 39:04someone else in the community who also
  881. 39:07has a small server at home that
  882. 39:10receives the backup every night.
  883. 39:13Okay.
  884. 39:14Or remotely with someone else.
  885. 39:18Or you could also do it in an even more
  886. 39:20low-tech way. You plug in a drive every
  887. 39:23night before leaving, copy the data,
  888. 39:25head home, take the drive with you, and
  889. 39:27bring it back the next evening.
  890. 39:29That's the most low-tech version you
  891. 39:31can find.
  892. 39:32Yeah.
  893. 39:33Could you tell us one or two big
  894. 39:35pitfalls you encountered or knew about
  895. 39:38beforehand regarding this transition?
  896. 39:41Trying to be too rushed; it's important
  897. 39:46to take your time because to migrate
  898. 39:50well, you need to have an overview.
  899. 39:55This helps avoid potential roadblocks,
  900. 39:59meaning at some point you end up with
  901. 40:03redundant digital services. For
  902. 40:06instance, right now our data is still
  903. 40:09with Google, even though we have all
  904. 40:12the data on our own server.
  905. 40:14Yeah.
  906. 40:15It's necessary to verify that we
  907. 40:17haven't forgotten anything. We can't
  908. 40:20just delete our Google account without
  909. 40:22being certain that we've migrated all
  910. 40:24our data properly. So there is
  911. 40:27inevitably a necessary transition
  912. 40:29period for copying all those files, but
  913. 40:32also for everyone to get comfortable
  914. 40:35with the tools. We don't all have the
  915. 40:39same level of usage or the same needs.
  916. 40:41We must ensure that everyone is
  917. 40:43satisfied with the tools implemented
  918. 40:45and that they meet the needs and
  919. 40:48expectations of every potential user.
  920. 40:51Yeah. So, you need a bit of an overlap
  921. 40:53phase with dual services while making
  922. 40:56sure not to rush things at that point.
  923. 40:59You have to be in a hurry to take your
  924. 41:00time.
  925. 41:00You have to be in a hurry to take your
  926. 41:02time. And timing is important, as is
  927. 41:06pacing yourself, because often those
  928. 41:10who don't have a good grasp of digital
  929. 41:15processes think it's instantaneous.
  930. 41:19Digital tools are supposed to just work
  931. 41:22and function immediately. But, that's
  932. 41:25not the case. You need time to copy,
  933. 41:27time to transfer, time to migrate, time
  934. 41:31to adapt, time to learn, and so you
  935. 41:33have to take the time, just as Mario
  936. 41:36said. Hm.
  937. 41:37And more personally, another thing, uh,
  938. 41:41that you always have to anticipate and
  939. 41:44that always causes problems—and will
  940. 41:47always be the case as long as they
  941. 41:49exist—is passwords, because users,
  942. 41:52users generally, uh, tend to get
  943. 41:55confused, forget their passwords, and
  944. 41:58so, well, that doesn't work, but in
  945. 42:03fact it works just fine. It's just that
  946. 42:05the password isn't the right one, but
  947. 42:06it's very recurrent.
  948. 42:07What are you talking about? We have our
  949. 42:10new service that is almost effective
  950. 42:13and operational. When will we be able
  951. 42:16to officially get away from Google? And
  952. 42:19well, the idea is to leave in June for
  953. 42:22good because the subscription, uh,
  954. 42:25is renewed in June, and the idea is not
  955. 42:27to renew the subscription. So our
  956. 42:29timeline is June. And so the
  957. 42:32appropriation of the data, the tools,
  958. 42:35etc., by all members of the group,
  959. 42:38staff, interns, civic service
  960. 42:40volunteers, and Cosphere members before
  961. 42:43June. Uh, well, do you want to conclude
  962. 42:47? Do you have a final word of
  963. 42:49encouragement for small, medium, or
  964. 42:52large organizations listening to us,
  965. 42:55for associations, to, uh, encourage
  966. 42:58them to initiate this little digital
  967. 43:01and technological shift or
  968. 43:04well, taking back control of your data,
  969. 43:07it's important, especially in today's
  970. 43:10world. And starting to think about it.
  971. 43:13That's already the first step. If you
  972. 43:16don't start the process right away,
  973. 43:18that's okay. But just starting a
  974. 43:21reflection, uh, is essential in the
  975. 43:24global context we're in today. And then
  976. 43:28it can be fun, you have to take it as a
  977. 43:31game too. Uh, in IT, you always have
  978. 43:34the right to make mistakes. So, well,
  979. 43:37you have to try, you have to experiment
  980. 43:39, and then when you're sure of yourself
  981. 43:41, you launch the right, the right
  982. 43:42method. This iteration of testing,
  983. 43:47failing, learning, it's completely
  984. 43:50logical and, uh, fun.
  985. 43:54So cool. We can wrap up on that, that's
  986. 43:57great. Well, thank you both for coming
  987. 44:00to speak at this microphone. The people
  988. 44:03listening to us will be able to go, uh,
  989. 44:06soon, or maybe even now that this
  990. 44:08podcast is online, to see the
  991. 44:10documentation you are producing and, uh
  992. 44:12, really get the process and the
  993. 44:15step-by-step tutorial. All the links
  994. 44:17and services that Nathanael and Marion
  995. 44:20recommend are currently being
  996. 44:22documented and will be available very
  997. 44:25soon, or perhaps even by the time this
  998. 44:28podcast is online. Well, thank you both
  999. 44:30. Thank you.
  1000. 44:31Xavier.

About this transcript

This page contains the full transcript of 🎙️ 𝐏𝐎𝐃𝐂𝐀𝐒𝐓 | Épisode 3 // Récit de l’auto-hébergement du Low-tech Lab by Low-tech Lab, generated from the public captions YouTube serves with the video. The transcript has 6,218 words across 1,000 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to choose a caption track available on the video.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.