🎙️ 𝐏𝐎𝐃𝐂𝐀𝐒𝐓 | Épisode 3 // Récit de l’auto-hébergement du Low-tech Lab — Transcript
Full transcript
- 0:00The whole goal of this podcast for
- 0:03those listening is basically to say: "
- 0:05Okay, when we're in a structure, an
- 0:08association, or an organization, and we
- 0:11notice that our digital environment
- 0:14could be better, what are the steps to
- 0:17take and the actions to initiate to
- 0:20envision a digital environment that is
- 0:22more low-tech, more ethical, and also
- 0:25more sustainable?" So that’s really
- 0:28how we’re going to build this podcast
- 0:30, to guide people in their thinking and
- 0:33provide them with the major steps for a
- 0:36transition toward a digital environment
- 0:38that’s more serene and ethical.
- 0:40When we first arrived, we realized that
- 0:43the digital tools used by the Low-Tech
- 0:46Lab weren't very consistent with the
- 0:49values they were defending. So we
- 0:52wanted to find a better way to make our
- 0:55common tools available, like the wiki,
- 0:58the website, and so on.
- 1:01What if the convivial, sober, and
- 1:02sustainable society of tomorrow were
- 1:04already here? Welcome to Visage
- 1:08Low-Tech, the podcast that opens the
- 1:10door a crack and shows you this joyful
- 1:12society springing up all over the
- 1:14country. Here, we head out to meet
- 1:16those who are experimenting with and
- 1:17spreading low-tech in their daily lives
- 1:19. We want to show you concrete,
- 1:21practical applications of the low-tech
- 1:23approach to inspire you and make you
- 1:25want to connect with others in your
- 1:27area. So today on Visage Low-Tech, I am
- 1:32hosting Marion Bouder and Nathanael Le
- 1:34Prête. Nathanael and Marion are in
- 1:36charge of what we call, in our jargon,
- 1:38the "common tools" at the Low-Tech Lab.
- 1:40They ensure that all the low-tech
- 1:42knowledge we aggregate here and have
- 1:44been providing open access to since
- 1:452013 is well-documented and
- 1:46disseminated. And first off, I'd like
- 1:49us to clarify what we mean in our
- 1:51jargon by "common tools," whether
- 1:54digital or not. Could you tell us a
- 1:56little bit about what you do at the
- 1:57Low-Tech Lab? "Common tools" refers to
- 2:01all the tools used by the network team,
- 2:05the communities, and more broadly, the
- 2:09general public who mostly visit the
- 2:12wiki, which was launched in 2017-2018
- 2:16during the first Nomade des Mers
- 2:19expedition and was set up to publicly
- 2:22document all the low-tech discovered
- 2:26along the way. Could you tell us a
- 2:29little bit about what you noticed when
- 2:32you arrived, and what digital projects
- 2:35you started to envision for the future
- 2:38within the Low-Tech Lab? Well, when we
- 2:42arrived, we realized that the digital
- 2:44tools used by the Low-Tech Lab weren't
- 2:47very consistent with the values they
- 2:50were defending. So that's something
- 2:53that surprised us a little bit. And in
- 2:55fact, the Low-tech Lab essentially uses
- 2:57software and applications that are
- 3:00proprietary and run in big data centers
- 3:03, uh, which centralize that data and
- 3:05also centralize the energy needed to
- 3:08run them. And so that struck us because
- 3:10, uh, it was inconsistent with the
- 3:13Low-tech Lab's overall approach. Indeed
- 3:16, the problem with data centers is that
- 3:19you aggregate many machines in one
- 3:22place that require a lot of energy, and
- 3:25so that also requires high-tech
- 3:27engineering to produce energy for the
- 3:30data centers. There's an inconsistency
- 3:34in having our common tools for
- 3:38communicating with the general public
- 3:42hosted in large spaces that consume a
- 3:46lot of land, cause soil
- 3:49artificialization, and require a lot of
- 3:53high-tech for the result, really. So,
- 3:58we wanted a more low-tech way to make
- 4:01common tools available, like the wiki,
- 4:05the website, and so on. You, uh, we
- 4:08need to introduce you because,
- 4:11precisely, perhaps the profiles that
- 4:13were at the Low-tech Lab historically
- 4:16were engineer profiles from design
- 4:18offices who, well, you can't wear every
- 4:21hat, and maybe didn't have that
- 4:24slightly geeky side or weren't really
- 4:26focused on digital usage. I don't know
- 4:30if it's intentional that we don't
- 4:32necessarily cite the tools or not, but
- 4:34it's true that we arrived at a Low-tech
- 4:37Lab that uses Google Drive. Our
- 4:39presentations are made with the office
- 4:42suite tool internal to Google Drive.
- 4:46It's true that you wanted to update
- 4:49that, and that's the whole heart of our
- 4:51podcast, this transition from
- 4:53proprietary tools, as you say Marion,
- 4:56or even sometimes Big Tech, to open
- 4:58source, and that's where you're going
- 5:01to introduce yourselves quickly. But
- 5:04first, shouldn't I take a moment to
- 5:06tell our listeners where we are,
- 5:08because it's quite a unique and nice
- 5:10place, and perhaps a bit low-tech too,
- 5:13I don't know. Nathanel, you're hosting
- 5:16us, uh, in your environment here in
- 5:18Lorient, and I might let you take the
- 5:20floor to introduce, well, the shared
- 5:22roofs where we are located, and perhaps
- 5:25before that I'll start with a
- 5:27description and you can correct me if,
- 5:29uh, I make any mistakes. If I
- 5:31understand correctly, we're in a
- 5:34residence that was built a year or two
- 5:37ago, I don't remember exactly. About
- 5:40fifteen or twenty, or fifteen
- 5:42households moved in here last year. You
- 5:46have common areas, uh, shared under
- 5:49these roofs. Today, we are working in
- 5:52the common room that you reserved for
- 5:54us. There's a shared vegetable garden,
- 5:56too. There's compost, we have
- 5:58composting toilets, and it's quite
- 6:00green as well. It's a very pleasant
- 6:03environment, very contemporary, too.
- 6:05Honestly, I'm always quite charmed when
- 6:08I arrive here at your place, and it's a
- 6:10project that I feel took 10 years to
- 6:12come to life, having been thoughtfully
- 6:15designed through collective
- 6:16intelligence. That's what I've
- 6:19understood of it. But can we really
- 6:22take a quick minute or two? Well, with
- 6:26a few adjustments, you've said almost
- 6:28everything; it's a 15-year project. The
- 6:31first time the residents of that time,
- 6:34the future residents of that time,
- 6:37gathered was in 2010 with the actual
- 6:40idea of creating participatory housing
- 6:44where the goal isn't just to live next
- 6:47to your neighbor, but to really know
- 6:50and share time with your neighbor. And
- 6:54then along the way, they were pioneers
- 6:57in a field in France which is the
- 7:01housing cooperative. Now, it's a model
- 7:04that is very widespread in other
- 7:06countries, notably Switzerland, but in
- 7:08France, it's almost non-existent for
- 7:10political reasons. And this concept is
- 7:14that the residents group themselves
- 7:18into a cooperative society that owns
- 7:21the building. And the residents are the
- 7:26tenants. So they are both collectively
- 7:29owners and individually tenants of
- 7:31their own cooperative. Which allows us
- 7:35to take the building out of the real
- 7:37estate market and real estate
- 7:40speculation. And then, since we built
- 7:43our building for ourselves, we tried to
- 7:47build it well, so it's rated A ++++ in
- 7:51energy performance certificates and
- 7:54other rankings. Uh, we built it with
- 7:57wood, wood insulation. Uh, so it's
- 8:01pleasant to live in, with good, good
- 8:05soundproofing too, because that was
- 8:08something very important for the
- 8:12residents.
- 8:13Uh, because we live in an
- 8:15intergenerational setting, and so there
- 8:17are needs for calm, you know, for
- 8:20silence, for calm or...
- 8:21for festivity, conversely.
- 8:23And as the pioneers wanted, as it was
- 8:25planned from the start, we therefore
- 8:27have common areas. We have a shared
- 8:29laundry room. No one has a washing
- 8:32machine at home. Uh, we have four for
- 8:35the whole building. We have 12
- 8:37households,
- 8:3820 people including the children.
- 8:41Uh, two guest rooms, because it's
- 8:45pointless for people
- 8:48living alone to have a guest room for
- 8:50themselves, whereas for hosting family
- 8:52once a year, well, the idea is to have
- 8:55guest rooms. OK. Very good. Shared.
- 8:58communal, in which we are currently
- 9:01here today to work together as a team.
- 9:04OK.
- 9:04And also the workshop you saw earlier
- 9:08next to the garden. OK.
- 9:12Can you save us?
- 9:13Ah yes, that's right. The hot water is
- 9:16solar heated. We're in the Lot region.
- 9:18We also have photovoltaics. It's a bit
- 9:20less low-tech, but it allows for local
- 9:22energy production.
- 9:23Well, listen, yeah, we can close that
- 9:25little parenthesis, but
- 9:28well, I can make a pretty nice
- 9:30transition, because as for shared
- 9:33things, we host our data on a computer
- 9:35that is self-hosted and where the
- 9:38residents use common tools. There you
- 9:41go. So, an easy transition.
- 9:42That's funny. Who could have set up
- 9:45this system? One wonders.
- 9:48OK. Uh, OK. And so, well, first of all,
- 9:53this podcast is called "Visages
- 9:55Low-tech." So it's also to introduce
- 9:58new faces. Uh, so what will interest us
- 10:01is also to introduce you. Mario, can
- 10:05you tell us briefly who you are and now
- 10:07that you're at Low-tech Lab? Well, I
- 10:11grew up in a household where I always
- 10:13saw a computer, and I was always
- 10:15fascinated by human-machine interaction
- 10:18. I thought it was great, and I
- 10:20believed in it, so very quickly I
- 10:22became interested in the uses we could
- 10:24make of the computer so that it would
- 10:26be enabling for everyone. So, I
- 10:28directed my studies and professional
- 10:31experiences toward usage, accessibility
- 10:34, and digital access, and. And that's
- 10:37how I was drawn to the offer from the
- 10:39Low-tech Lab, which was to get hands-on
- 10:42with common tools and, among other
- 10:44things, the uses of these common tools.
- 10:46So that's how I arrived here.
- 10:50Yeah. And you, Nathanel?
- 10:52Well, for me, it happened later. Uh, IT
- 10:55was a constraint in the beginning, and
- 10:59then, while traveling around the world,
- 11:03I wanted to master my blog and my tools
- 11:06, so I looked into how it all worked.
- 11:10Uh, and since I had been following what
- 11:14Framasoft was doing for some time,
- 11:17that's how I got into free software,
- 11:20then self-hosting, and I met the "
- 11:23Chatons." Maybe we'll come back to that
- 11:26later. Well, actually, I'm even one of
- 11:29the founders of Les Châtons with
- 11:32Framasoft, and then when I returned
- 11:35from my travels, I was hired by Marion
- 11:38seven years ago now. And so, I got into
- 11:42digital technology a bit more
- 11:44professionally with her, and after that
- 11:47, we didn't part ways; we started an
- 11:50association in the digital field, and
- 11:53then we joined the Low-Tech Lab when we
- 11:56saw the job offers that really appealed
- 11:59to us. Yes, yes, it's funny because I
- 12:02think the Low-Tech Lab was looking for
- 12:04one person to manage their digital
- 12:07tools, and they got two because you
- 12:09always come in pairs.
- 12:11That's right.
- 12:12We offered to split the job in two
- 12:14because our skills are complementary.
- 12:17So, it matched the offer quite well and
- 12:20allowed us to keep our other digital
- 12:22activities on the side.
- 12:24Great. So, you introduced yourselves in
- 12:27one big paragraph. Now, I'll try a
- 12:28slightly harder exercise. If you had to
- 12:31describe yourselves in two opposing
- 12:33adjectives.
- 12:35Well, I would say never late, always
- 12:37right on time. Ah.
- 12:39Yes, okay. That fits you pretty well,
- 12:44it works.
- 12:45And I would say I am solastalgic, yet
- 12:49optimistic.
- 12:51Uh, it's not nostalgic, it's
- 12:53solastalgic. So, it's linked to
- 12:56nostalgia, it's the fact of regretting
- 12:59losses that have occurred that we
- 13:02didn't experience, such as the
- 13:04disappearance of species, the changing
- 13:07climate, landscapes we won't see
- 13:10anymore but that did exist. We know
- 13:13they existed and we miss them.
- 13:15Because we didn't experience them
- 13:17precisely because we didn't know them.
- 13:20Which is different from nostalgia,
- 13:22where you regret something you did
- 13:24experience.
- 13:26Okay, great. Okay, so now we are going
- 13:28to dive into the heart of the podcast.
- 13:30We will try to explain, first of all,
- 13:32the steps you decided to take and in
- 13:35what order, based on the respective
- 13:37observations you made at the Low-Tech
- 13:40Lab. Having a site hosted at OVH in
- 13:43France, I didn't think it was
- 13:45necessarily scandalous. Or using, well
- 13:48yes, sharing files on Google Drive, we
- 13:50know it's really not ideal, but we are
- 13:53looking for alternatives. Do we have
- 13:56robust tools to replace that? Beyond
- 14:00the tools and the processes we
- 14:02implement, I would like us to return to
- 14:04what is really at stake politically and
- 14:07ethically in these choices we make. Why
- 14:10hosting your site with OVH is good, but
- 14:13if you want to be low-tech and be a bit
- 14:16more exemplary, you have to go even
- 14:19further. What’s really at stake here?
- 14:21Well,
- 14:23technically, it's true that there are
- 14:28three levels for IT and hosting; you
- 14:33can take the simplest path and be
- 14:38hosted by highly redundant tools,
- 14:41hosted in something a bit obscure
- 14:44called the cloud, which we don't really
- 14:48know how it works. But it seems to work
- 14:53, and the data is replicated across a
- 14:56bunch of servers in different data
- 14:59centers around the world. So here,
- 15:03we're at a level of high-tech and
- 15:06complexity that is truly maximal. In a
- 15:09second level, you can effectively
- 15:12choose to host yourself in a single,
- 15:16more local data center like OVH, where
- 15:19you already regain control over your
- 15:23digital tools and data. And then, in a
- 15:27third level, you regain control over
- 15:30the materiality of digital tech, sort
- 15:33of like getting your hands dirty with a
- 15:37bike or working on a car engine
- 15:40yourself. Whereas with very modern cars
- 15:42today, well, you can't do anything, and
- 15:44even mechanics can't do anything; you
- 15:46have to go to the dealership. Well,
- 15:48that’s the same idea, and so if you
- 15:51want, from a low-tech perspective, to
- 15:54regain control over technology, you
- 15:57have to move toward self-hosting where
- 16:00you master your server, even at the
- 16:02hardware level. Now, it's true that in
- 16:06exchange, you have to accept that
- 16:09sometimes the service won't be
- 16:11accessible for a while, but that's
- 16:14something we need to work on as a
- 16:17society.
- 16:19Speaking of sites that don't always
- 16:22work, there's also the Low-Tech
- 16:25Magazine, which runs from Barcelona
- 16:27using solar panels when there's sun.
- 16:30Fortunately, they have a bit more than
- 16:31we do in Brittany. But
- 16:33exactly, that's the idea.
- 16:34I find it incredibly charming to accept
- 16:37that a digital service might be
- 16:40unavailable because there's no sun. It
- 16:43really teaches us about behaviors and
- 16:45expectations that we don't have much of
- 16:48anymore in our collective impatience.
- 16:52Very well. So, I really want to get
- 16:54into the heart of the matter. Could you
- 16:58describe the various steps you followed
- 17:01to accomplish this entire digital
- 17:05transformation of the Low-Tech Lab over
- 17:08the last few months? I'd just like to
- 17:13add one small thing, which is that
- 17:16moving away from big tech, GAFAM, and
- 17:19other similar major corporations is
- 17:21also well, being a fervent defender of
- 17:25those who can fuel fascism today, and
- 17:28that's also a position we either want
- 17:30to take or not. But it's interesting to
- 17:33keep that notion in mind because these
- 17:35large companies are the ones shaping
- 17:38the world of tomorrow, and not
- 17:40endorsing what they do is also a form
- 17:42of defense.
- 17:44Yeah, that's quite relevant, indeed. Uh
- 17:46,
- 17:46there, that was a little side note.
- 17:48Yeah. Yes.
- 17:49Politico-strategic, let's say. Yeah,
- 17:52for sure. And a sovereignty issue, well
- 17:56, when we were talking about what's
- 17:58really at stake here. And so,
- 18:01afterwards, we did it step by step: we
- 18:05started by migrating calendars,
- 18:07migrating contacts; the biggest part
- 18:09was migrating files, where we migrated
- 18:12data from Google to a more open
- 18:14solution. So, the solution we're using,
- 18:18well, maybe we'll come back to it, but
- 18:22we're on a solution based on the
- 18:25software Nextcloud, which is an
- 18:28application that allows you to store,
- 18:32and not just store, but manage your
- 18:35data. So once we migrated those files,
- 18:39the next step was obviously to support
- 18:42the transition in usage.
- 18:45Yeah, because—if I may add a side
- 18:47note—when you migrate all your Google
- 18:50Drive documents, which are designed
- 18:52with Google Sheets, Google Slides,
- 18:54Google Docs, or whatever the Word
- 18:56equivalent is called, but uh
- 18:59yeah, each of those files, and if you
- 19:02have 1,800 of them, you have to convert
- 19:05them.
- 19:06Exactly. You have to convert them all
- 19:08and then export them. So there was a
- 19:10bunch of scripts, maybe not manual, I
- 19:12assume, but
- 19:12there was a lot of work from Nathanael
- 19:15on the technical side to convert and
- 19:18then migrate all those documents, and
- 19:21then verify that everything was
- 19:23properly converted and migrated.
- 19:26And we're still in an analysis phase
- 19:29before deleting all our documents and
- 19:32folders from Google. We're still
- 19:35analyzing whether we've migrated
- 19:37everything correctly and with the right
- 19:39formats.
- 19:40Going through 10, even 13 years of
- 19:43association communication files, seems
- 19:46like a pretty pretty significant task,
- 19:50but ultimately, every time I open one,
- 19:52the conversion seems to have been done
- 19:55well, and it's doable. Google puts
- 19:57spokes in our wheels;
- 19:58they don't make the job easy, to say
- 20:00the least. In terms of timeline, it
- 20:03might seem monumental, but you were
- 20:06still incredibly efficient from the
- 20:08moment you said "that's it, we're
- 20:10migrating, converting, and
- 20:12re-transferring," it's just a few weeks
- 20:14. Well,
- 20:15initially, we planned for 2 days, it
- 20:18took us 3 weeks.
- 20:20Close enough.
- 20:21Roughly.
- 20:22Uh, it's true that at the beginning, I
- 20:26didn't know the Google environment; I
- 20:28had never worked with it. And I told
- 20:30myself, well, I'll just download all
- 20:32the files and then re-import them. That
- 20:36seems quite natural, shall we say,
- 20:38quite logical. But the thing is, Google
- 20:41, having no interest in that obviously,
- 20:44doing everything to keep people on
- 20:46their platform, doesn't provide any
- 20:48information on the quantity of files or
- 20:51the amount of data there is, or it
- 20:53provides contradictory information that
- 20:56is very complicated to...
- 20:57It's organized by folder, but you don't
- 21:00know what's in the folders.
- 21:02That's it. You can't know how much
- 21:04space a folder takes up or how much it
- 21:06...
- 21:07You can't know. You have to download it
- 21:08to find out. And then, effectively
- 21:11downloading, well, you end up with
- 21:15files that aren't necessarily converted
- 21:17. Uh, in short, it's quite complicated.
- 21:20Uh, so you really have to use a
- 21:21dedicated tool for that. Uh, which tool
- 21:25? Well, free software, obviously. Uh,
- 21:29but uh since we don't know how much
- 21:33data we're going to download, I, quite
- 21:35simply, saturated my disk. Uh, so there
- 21:38, I had to get another disk until I
- 21:41found a disk that was large enough to
- 21:44hold all the data. So, that's a setback
- 21:47, we lose time, we start over. Uh, and
- 21:50then, uh for obscure reasons, there are
- 21:55files that won't be converted during
- 21:57the transfer. So you have to go back at
- 22:00the end, redo them, search to find the
- 22:02ones that weren't converted. And then
- 22:05afterwards, there are all the little
- 22:06joys of amusing things like files that
- 22:11have long-winded names, which then
- 22:15interrupt the entire migration process
- 22:19because the process finds an error and
- 22:23stops because the file name is too long
- 22:27.
- 22:28Uh, and sometimes, I saw whole
- 22:30sentences used as file names.
- 22:31There you go. Alright. If we go back to
- 22:35the steps, yes, we were at this whole
- 22:38migration of files, even the migration
- 22:41of the calendar, contacts, and files.
- 22:45Uh, if you have anything else to say
- 22:46about that, don't hesitate. Otherwise,
- 22:48if I pick up the thread after that,
- 22:50there is the support for usage. And I
- 22:52feel like that's where you're
- 22:54supporting us by saying, "Well, here
- 22:56you go, we've done the job." Do you
- 22:58approve? Are you finding everything you
- 23:00need? Regarding the files you're
- 23:03responsible for, do you have all your
- 23:06documents, or does this new tool, the
- 23:10LibreOffice, well, the Nextcloud tool
- 23:13that takes over from Google Sheets or
- 23:16replaces our file formats. Have you
- 23:19managed to get the hang of them?
- 23:21Because, similarly, we're also trying
- 23:24to move away from Microsoft or Keynote
- 23:26for our presentations. We're switching
- 23:29from PowerPoint to open-source software
- 23:31. Basically, we're relearning all our
- 23:34digital habits to try and be more
- 23:37consistent with our values. So we're in
- 23:40this space, and it's both exciting and
- 23:43challenging for us. I mean, in terms of
- 23:46productivity, we have to accept slowing
- 23:49down, being a bit less productive,
- 23:52learning a new piece of software, the
- 23:54open-source equivalent to PowerPoint,
- 23:57what's the suite called?
- 23:59Collabora Online, which is installed on
- 24:02Nextcloud.
- 24:03Colab, which is, yes. Which is
- 24:04suggested by Nextcloud for usage, right
- 24:06? It's one of the tools, one of the
- 24:09office suites that's a collaborative
- 24:12online version, and so we can integrate
- 24:15it into Nextcloud. And that's what we
- 24:17did for our current needs. We're using
- 24:19a free version. For future needs, we'll
- 24:22see over time, but for now, the free
- 24:24version is enough for us.
- 24:26And regarding the country behind it, is
- 24:28it European, is it a specific country,
- 24:31or are we not quite sure?
- 24:32It's English, English as well. Okay.
- 24:36Okay. And the free aspect actually
- 24:38depends on the number of users. Unless
- 24:42the Nextcloud instance becomes massive,
- 24:46we'll stay on the free version.
- 24:47There you go.
- 24:48And Nextcloud is a German solution,
- 24:50originally. It was German developers
- 24:53who developed it,
- 24:55a few years ago now. And that's the
- 24:57question I asked myself when we started
- 25:00all of this. I have a bit of, how do
- 25:04you say it? I think within the team, I
- 25:08needed to be reassured about the
- 25:10robustness of an open-source tool, how
- 25:13long it's been around. How long have
- 25:15they been around? Will they still be
- 25:17here in three years? Often these are
- 25:21fairly loose, fragile structures that
- 25:24rely on donations, and how do we
- 25:27reassure an organization by saying, "No
- 25:30, it's not a capitalist monster sitting
- 25:33on a huge pile of capital that keeps it
- 25:37secure for the next 50 years." But
- 25:40still, it seems to us to be the most
- 25:43robust thing right now and the one to
- 25:46strive for. Well, actually, it's
- 25:49because there's an image that has
- 25:51likely been created, because
- 25:53open-source software is what runs the
- 25:55vast majority of the digital world
- 25:57today. A vast majority of mobile phones
- 26:02, smartphones, run on Android. We say
- 26:06Android is Google. Except that 90%of
- 26:08the code in Android is Linux. It's
- 26:12open-source software. Only the
- 26:14proprietary commercial overlay belongs
- 26:19to Google. And that's how it is for the
- 26:22vast majority of the digital world.
- 26:25Today, most servers that power the
- 26:29world's websites run on Debian or
- 26:32another Linux distribution, which is
- 26:36open-source software, and a site using
- 26:41a CMS called WordPress, which manages
- 26:4540%of global internet traffic. It's
- 26:49open-source software. And yet it runs
- 26:54the planet, and it lasts for a long
- 26:56time.
- 26:57Yes. So for you, in scenarios where an
- 27:00actor disappears and leaves us a bit in
- 27:02the lurch, there will always be...
- 27:05It can happen.
- 27:06Yeah. Yeah.
- 27:07But no more or less than a big company
- 27:10developing software. Yeah.
- 27:14The software we've chosen to use for
- 27:17the Lot Club are proven programs that
- 27:20have developer communities that are,
- 27:24yeah. that are really solid. They have
- 27:26a foundation that's been there for
- 27:27several years. We aren't getting into
- 27:30open-source software that's new,
- 27:31unproven, and so on. Yeah.
- 27:33The idea isn't to put the Lot at a
- 27:35disadvantage, but to show that with
- 27:38existing tools and what's being done
- 27:40today, it's possible and it works.
- 27:43As Marion said, we talk about community
- 27:45, a bit like in the Lot, we have LCHC
- 27:47communities, and that's how you see the
- 27:49maturity of a piece of software and its
- 27:51longevity. It's more about that than a
- 27:53company that might be behind it. If
- 27:55there's a large community of developers
- 27:58and users, in principle, the software
- 28:00will be long-lasting.
- 28:02Yeah. Yeah. Yeah. Exactly. And so in
- 28:05this step, to pick up our thread again,
- 28:09we were at support for usage. Uh,
- 28:12you're also working on documenting all
- 28:15of this. We’re documenting it here
- 28:18with audio in a podcast, but you're
- 28:20working on written documentation that
- 28:23could guide organizations wanting to
- 28:26start this process. I’m wondering, if
- 28:30we don't have Marion or Nathanael
- 28:34around, is it something you can set up
- 28:38quite easily if you’re just a bit
- 28:42savvy with IT tools? The idea behind
- 28:46this documentation is to show what we
- 28:48were able to do with the skills we had
- 28:50in-house. But it’s also to show
- 28:52what’s possible with fewer skills,
- 28:54and the types of providers you can turn
- 28:57to if you don't have those skills
- 28:58in-house. Hm.
- 28:59Hm.
- 29:00There are plenty of those providers in
- 29:02the region. Identifying them is more
- 29:04difficult when you aren't from the
- 29:06open-source community. But in this
- 29:09documentation, we’ll include a
- 29:12non-exhaustive list of actors capable
- 29:15of supporting organizations locally
- 29:19with self-hosting their data, just as
- 29:22we propose. Exactly. The documentation
- 29:25has two goals. It’s to provide an
- 29:27overview of our approach, how we went
- 29:31about it, and what the results were, as
- 29:34well as to offer entry points for
- 29:37communities that have the necessary
- 29:40human resources or external partners.
- 29:43And like you said, it’s about
- 29:45providing reassurance; when you have a
- 29:48well-made tutorial, which we’re
- 29:50trying to create,
- 29:52it makes it less daunting to embark on
- 29:54the adventure.
- 29:56As I said when I introduced myself, I
- 29:59don't come from a tech background, so I
- 30:02learned as I went by doing things, and
- 30:05I definitely made some mistakes.
- 30:09That’s actually what allowed me to
- 30:11learn how to do self-hosting. And well,
- 30:14if a helping hand is needed, we’re
- 30:16here for that too,
- 30:18to support communities. There’s
- 30:19mutual aid, but that’s the whole "
- 30:21low-tech" culture, really—it started
- 30:23from that "do it yourself" mindset,
- 30:25understanding your technology, and
- 30:27benefiting from others 'experiments.
- 30:29And documenting it. And for us, our
- 30:32goal is surely to create documentation
- 30:34that evolves along with how it's used.
- 30:38And I see the next step, after
- 30:41supporting the usage, is precisely,
- 30:44once the whole new culture has spread
- 30:46and infused the organization, uh, to
- 30:49think about it, you...You say the next
- 30:52step is a bit about adding new features
- 30:55...uh, well, that's counting new tools.
- 30:58Actually, once we're comfortable with
- 31:01the base, we'll gradually add new
- 31:04features, new applications that are
- 31:06interesting and that could possibly
- 31:09improve productivity, even if that's
- 31:12not the goal. But administratively, if
- 31:14we can become autonomous in accounting
- 31:16and administrative management, that's
- 31:18great. So, uh, that's it, it's adding
- 31:21new tools and/or applications
- 31:23integrated into Nextcloud, possibly to
- 31:26make our daily lives easier. And the
- 31:31difference is that before, for
- 31:32everything it was done independently.
- 31:37We had a need, and well, we would pick
- 31:40software that met that need, but
- 31:43without any cohesion within the common
- 31:46ecosystem of digital tools. Uh, the
- 31:50idea here is that by taking back
- 31:52control of what already exists, we will
- 31:56then be able to develop, or have
- 31:58developed, or install existing software
- 32:01that is consistent with what we already
- 32:05have.
- 32:05Yeah. Yeah. Yes, and it's true that in
- 32:08my usage, I was using just about
- 32:09anything and everything. And it reminds
- 32:12me of the moment I showed you what a
- 32:14Linktree was for the Instagram account
- 32:18where you were a bit stunned that there
- 32:20were proprietary services for inventing
- 32:23something so simple that had already
- 32:25been invented at the birth of the
- 32:27internet.
- 32:29But it's true that a Linktree, why not
- 32:31build it yourself?
- 32:33Completely. Yes, I really
- 32:38I read the distress in your eyes. Why
- 32:41do you need that, Xavier?
- 32:44Uh, okay. Uh, so I think we've gone
- 32:47through the steps a bit. Uh, what I
- 32:50also wanted, a bit like a recipe, was
- 32:54for us to visualize a bit what you
- 32:58needed to set all this up, even in
- 33:02terms of hardware: what are the
- 33:05ingredients? And maybe even a little
- 33:08budget sheet, what kind of amount are
- 33:11we talking about to set all this up? To
- 33:15put it simply, we needed five essential
- 33:18things, which are a computer that acts
- 33:20as a server, an internet connection,
- 33:23preferably fiber for a smooth
- 33:25experience in using the tools,
- 33:27a domain name
- 33:29which was already existing in this case
- 33:31, but if you're setting up your own
- 33:33community, well, it will be important.
- 33:35Uh, something to do remote backups, so
- 33:39provide a hard drive that allows for
- 33:43backing up and a subscription for an
- 33:46email relay. If you want to self-host
- 33:49your emails and not depend on anyone,
- 33:52you absolutely must have a relay to get
- 33:54through the Microsoft, Google, and
- 33:56other filters. So there you go, those
- 33:59were the five really essential things.
- 34:01Yeah. Yeah. And the budget, uh, it cost
- 34:05us, uh
- 34:06about € 350
- 34:09for the purchase and then for usage. Uh
- 34:11, as for the email relay, which allows
- 34:15you to have a good reputation as an
- 34:18email server, which is hard to get when
- 34:22you're self-hosting. So it's good to go
- 34:25through a provider for that, and there
- 34:27are some very good ones. Uh, it
- 34:30currently costs us € 50 per year. If
- 34:34we ever, and that's the intention,
- 34:36scale it up a bit, share it with other
- 34:39communities, and so on, it will cost us
- 34:41a little bit more, maybe up to € 200
- 34:44or € 300 per year. Uh, but it's
- 34:48something that has its value. Knowing
- 34:52that it also advantageously replaces a
- 34:55newsletter provider, for example, which
- 34:57would cost about the same price for a
- 35:00mass email send. Typically,
- 35:03we had SAP
- 35:04that we had before.
- 35:06We're now switching to List. Yes,
- 35:08that's it. It's it's List that asks you
- 35:10for that price to, uh, kind of
- 35:14authenticate. Well, List
- 35:18but, on the other hand, to be able to
- 35:21send emails in a way that's acceptable
- 35:24to
- 35:25Big Tech, you have to go through an IP
- 35:27address. Uh, the IP address is the
- 35:31equivalent of a physical postal address
- 35:34in the physical world.
- 35:36Well, the IP address is what addresses
- 35:38a machine in the digital world, and it
- 35:41needs to have a good reputation to be
- 35:44accepted by Big Tech
- 35:46and for it to land in the mailboxes.
- 35:48And that it lands well in the right
- 35:50mailboxes. Whereas if you self-host,
- 35:52well, your IP address has an unknown
- 35:54reputation, and Big Tech will block it
- 35:56quite easily.
- 35:57Yeah. So you're talking about this
- 35:59annual cost a bit. Uh, the cloud, we
- 36:01don't have it either, our cloud, does
- 36:05it have a cost? I don't know how much
- 36:08fiber cost, it has a hardware cost, but
- 36:10it didn't cost us more than € 250.
- 36:13Yeah, because it's really on our own
- 36:16server.
- 36:16Yeah, it's our Nextcloud, our cloud on
- 36:20our server machine with
- 36:22because that was an expense of, I think
- 36:25, 2 terabytes on a Google Drive, it's
- 36:2810 € per month. That's 120 € saved
- 36:32per year. Well, it's more than that
- 36:35because actually we had Google Drive
- 36:37costs, but we also had OVH costs
- 36:39and we also had costs from Infomaniak,
- 36:41which is a competitor to OVH. So, in
- 36:44fact, all those costs will eventually
- 36:47no longer exist. Exactly, they are
- 36:49still ongoing for this year, but
- 36:50eventually they won't exist anymore.
- 36:52And so this saving, what we pay every
- 36:55year, is equal to our one-time startup
- 36:58investment for our server.
- 37:01And afterwards, the only costs will be
- 37:03the electricity to run the server and
- 37:04the fiber internet. But we use the
- 37:06fiber for work anyway. So
- 37:08what are you planning in terms of I
- 37:12don't know, backups, or just since
- 37:14everything is physically based? Well,
- 37:16in this case, in Concarneau at the
- 37:18office. Um, if, uh, lightning strikes,
- 37:22or, well, if we burn out the server, is
- 37:26there a quarterly backup, or what do we
- 37:29, what do we, um
- 37:30how do we secure things a bit, um
- 37:32there is a digital backup rule called
- 37:35the 3-2-1 rule. Sorry. It's having data
- 37:38in three different places on two
- 37:41different media, including one offsite.
- 37:44That's right.
- 37:45And
- 37:46and today, we follow that. Which means
- 37:48we have our data on a main disk, these
- 37:51data are duplicated on a second disk in
- 37:54the same machine, and there is a third
- 37:57duplication, a second duplication, on
- 37:59an external server which is in Lorient.
- 38:02On a server in Lorient.
- 38:04Yeah. And, uh, so if the machine burns
- 38:06out or gets stolen, we have the
- 38:09external backup. If the first disk
- 38:11fails, the second disk takes over and
- 38:14we then replace the first disk. So, in
- 38:16fact,
- 38:17whether it's against theft, a failure,
- 38:20a fire, or anything else, we will
- 38:22always have a solution to restore the
- 38:25data.
- 38:26And for that, there is a script that
- 38:28automates it a bit
- 38:29at midnight, we have a remote backup.
- 38:33At worst, we lose 24 hours of data.
- 38:35Ah, yes, yes. OK.
- 38:37Uh, that's what we were saying earlier
- 38:39about the essential things, the five
- 38:41essential things. So there was the
- 38:43server, there was the email relay, and
- 38:45there was the backup. And that is where
- 38:47you need to find service providers when
- 38:50you want to do self-hosting. For email
- 38:53relaying, you generally need to go
- 38:54through a pro, and there are some very
- 38:56good ones, especially within the "
- 38:57Châtons" network. And off-site backups
- 39:01can be done via self-hosting with
- 39:04someone else in the community who also
- 39:07has a small server at home that
- 39:10receives the backup every night.
- 39:13Okay.
- 39:14Or remotely with someone else.
- 39:18Or you could also do it in an even more
- 39:20low-tech way. You plug in a drive every
- 39:23night before leaving, copy the data,
- 39:25head home, take the drive with you, and
- 39:27bring it back the next evening.
- 39:29That's the most low-tech version you
- 39:31can find.
- 39:32Yeah.
- 39:33Could you tell us one or two big
- 39:35pitfalls you encountered or knew about
- 39:38beforehand regarding this transition?
- 39:41Trying to be too rushed; it's important
- 39:46to take your time because to migrate
- 39:50well, you need to have an overview.
- 39:55This helps avoid potential roadblocks,
- 39:59meaning at some point you end up with
- 40:03redundant digital services. For
- 40:06instance, right now our data is still
- 40:09with Google, even though we have all
- 40:12the data on our own server.
- 40:14Yeah.
- 40:15It's necessary to verify that we
- 40:17haven't forgotten anything. We can't
- 40:20just delete our Google account without
- 40:22being certain that we've migrated all
- 40:24our data properly. So there is
- 40:27inevitably a necessary transition
- 40:29period for copying all those files, but
- 40:32also for everyone to get comfortable
- 40:35with the tools. We don't all have the
- 40:39same level of usage or the same needs.
- 40:41We must ensure that everyone is
- 40:43satisfied with the tools implemented
- 40:45and that they meet the needs and
- 40:48expectations of every potential user.
- 40:51Yeah. So, you need a bit of an overlap
- 40:53phase with dual services while making
- 40:56sure not to rush things at that point.
- 40:59You have to be in a hurry to take your
- 41:00time.
- 41:00You have to be in a hurry to take your
- 41:02time. And timing is important, as is
- 41:06pacing yourself, because often those
- 41:10who don't have a good grasp of digital
- 41:15processes think it's instantaneous.
- 41:19Digital tools are supposed to just work
- 41:22and function immediately. But, that's
- 41:25not the case. You need time to copy,
- 41:27time to transfer, time to migrate, time
- 41:31to adapt, time to learn, and so you
- 41:33have to take the time, just as Mario
- 41:36said. Hm.
- 41:37And more personally, another thing, uh,
- 41:41that you always have to anticipate and
- 41:44that always causes problems—and will
- 41:47always be the case as long as they
- 41:49exist—is passwords, because users,
- 41:52users generally, uh, tend to get
- 41:55confused, forget their passwords, and
- 41:58so, well, that doesn't work, but in
- 42:03fact it works just fine. It's just that
- 42:05the password isn't the right one, but
- 42:06it's very recurrent.
- 42:07What are you talking about? We have our
- 42:10new service that is almost effective
- 42:13and operational. When will we be able
- 42:16to officially get away from Google? And
- 42:19well, the idea is to leave in June for
- 42:22good because the subscription, uh,
- 42:25is renewed in June, and the idea is not
- 42:27to renew the subscription. So our
- 42:29timeline is June. And so the
- 42:32appropriation of the data, the tools,
- 42:35etc., by all members of the group,
- 42:38staff, interns, civic service
- 42:40volunteers, and Cosphere members before
- 42:43June. Uh, well, do you want to conclude
- 42:47? Do you have a final word of
- 42:49encouragement for small, medium, or
- 42:52large organizations listening to us,
- 42:55for associations, to, uh, encourage
- 42:58them to initiate this little digital
- 43:01and technological shift or
- 43:04well, taking back control of your data,
- 43:07it's important, especially in today's
- 43:10world. And starting to think about it.
- 43:13That's already the first step. If you
- 43:16don't start the process right away,
- 43:18that's okay. But just starting a
- 43:21reflection, uh, is essential in the
- 43:24global context we're in today. And then
- 43:28it can be fun, you have to take it as a
- 43:31game too. Uh, in IT, you always have
- 43:34the right to make mistakes. So, well,
- 43:37you have to try, you have to experiment
- 43:39, and then when you're sure of yourself
- 43:41, you launch the right, the right
- 43:42method. This iteration of testing,
- 43:47failing, learning, it's completely
- 43:50logical and, uh, fun.
- 43:54So cool. We can wrap up on that, that's
- 43:57great. Well, thank you both for coming
- 44:00to speak at this microphone. The people
- 44:03listening to us will be able to go, uh,
- 44:06soon, or maybe even now that this
- 44:08podcast is online, to see the
- 44:10documentation you are producing and, uh
- 44:12, really get the process and the
- 44:15step-by-step tutorial. All the links
- 44:17and services that Nathanael and Marion
- 44:20recommend are currently being
- 44:22documented and will be available very
- 44:25soon, or perhaps even by the time this
- 44:28podcast is online. Well, thank you both
- 44:30. Thank you.
- 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.