WEBVTT 00:00.000 --> 00:10.000 All right, so we're still all learning. 00:10.000 --> 00:13.000 One thing we learned is how to make the microphone louder. 00:13.000 --> 00:15.000 I think that's great. 00:15.000 --> 00:16.000 So we made progress. 00:16.000 --> 00:19.000 We're still in the same session, basically. 00:19.000 --> 00:22.000 So we really didn't really have a break now. 00:22.000 --> 00:29.000 And we're continuing with, in this area of self-hosted, 00:29.000 --> 00:35.000 like, or hosting stuff with the project Eileen, 00:35.000 --> 00:38.000 which is about self-hosted digital islands. 00:38.000 --> 00:41.000 And Ryan Gibb is going to present about this. 00:41.000 --> 00:46.000 So round of applause for Ryan, please, and enjoy the talk. 00:47.000 --> 00:51.000 Thank you. 00:51.000 --> 00:53.000 Is it night working? 00:53.000 --> 00:54.000 Yeah, that seems to be working. 00:54.000 --> 00:58.000 All right, I'm going to give you a talk on this project called 00:58.000 --> 01:01.000 Eileen, which means island in Scottish gay. 01:01.000 --> 01:06.000 The reason for that is, it's, it's, but your digital islands. 01:06.000 --> 01:10.000 So basically, the problem I see is our digital lives are increasingly 01:10.000 --> 01:14.000 fragmented across many centralized online services. 01:15.000 --> 01:19.000 This model concentrates power, leaving us with minimal technical control 01:19.000 --> 01:23.000 over our personal data and online identities. 01:23.000 --> 01:26.000 The long-term permanence of these platforms is uncertain. 01:26.000 --> 01:29.000 And the commercial incentives are often misaligned with their users, 01:29.000 --> 01:34.000 which this RFC from marketing and kind of goes into a little bit more. 01:34.000 --> 01:38.000 And a solution that I propose for this is, 01:38.000 --> 01:40.000 inverting this model. 01:40.000 --> 01:43.000 Instead of centralizing our data in these proprietary silos, 01:43.000 --> 01:47.000 let centralize our presence under our own control 01:47.000 --> 01:51.000 using open federates and services. 01:51.000 --> 01:55.000 We describe digital islands, or islands, which are self-hosted hubs 01:55.000 --> 01:59.000 for an individual or communities online presence. 01:59.000 --> 02:01.000 By hosting these services ourselves, 02:01.000 --> 02:05.000 we regain our autonomy and control in the internet. 02:06.000 --> 02:09.000 So, I lean as a project designed to simplify the creation 02:09.000 --> 02:12.000 and management of these digital islands. 02:12.000 --> 02:16.000 The core idea is to parameterize a complete operating system deployment 02:16.000 --> 02:20.000 by a domain name and a set of services that we want to run. 02:20.000 --> 02:25.000 This allows us to easily deploy our own instance of such services. 02:25.000 --> 02:28.000 For example, matrix, massodone, email, 02:28.000 --> 02:31.000 called out for calendaring a VPN. 02:31.000 --> 02:34.000 Things I'm sure you're all familiar with. 02:34.000 --> 02:37.000 How many people are self-hosting any of these services? 02:37.000 --> 02:38.000 Can we get you a chance? 02:38.000 --> 02:42.000 Okay, that's a good amount, but it can be better. 02:42.000 --> 02:47.000 So, I took a look around the state of the world. 02:47.000 --> 02:50.000 And I thought about how can we make it easier to use these services. 02:50.000 --> 02:54.000 I had to look at some things like Ansible and other things, 02:54.000 --> 02:57.000 but Nick sauce seemed like the best solution to enable the 02:57.000 --> 02:59.000 reproducible deployment of these services. 03:00.000 --> 03:05.000 They still require a lot of setup in addition to what the Nick sauce 03:05.000 --> 03:07.000 module system provides, though. 03:07.000 --> 03:11.000 You needed to go into some external system to create domain names, 03:11.000 --> 03:14.000 other DNS records, sometimes you need to configure 03:14.000 --> 03:17.000 user accounts manually, databases, HTP Proxies, 03:17.000 --> 03:20.000 sometimes the elastic of kits. 03:20.000 --> 03:25.000 So, I lean is essentially a set of opinionated Nick sauce modules 03:25.000 --> 03:30.000 to enable the simple deployment of these services. 03:30.000 --> 03:34.000 A lot of it, I have hopes to eventually upstream to Nick sauce, 03:34.000 --> 03:39.000 but a lot of it is a little too opinionated to do so. 03:39.000 --> 03:42.000 So, one big thing in deploying any services, 03:42.000 --> 03:45.000 you need a domain name for it. 03:45.000 --> 03:50.000 So, the Nick sauce module system cannot do this for you 03:50.000 --> 03:53.000 if you are not hosting your own domain name. 03:53.000 --> 03:57.000 For example, you need to go to your DNS provider and 03:57.000 --> 04:02.000 do some sort of dance between your email setup and your 04:02.000 --> 04:05.000 registrar and fit in various decim, 04:05.000 --> 04:11.000 the smart SPS records as well as the domain names, obviously. 04:11.000 --> 04:17.000 So, what Eileen does is self host the author of DNS for your domain. 04:17.000 --> 04:21.000 So, I don't know how familiar the room is with DNS, 04:21.000 --> 04:24.000 but who is hosting their own authority in a server? 04:24.000 --> 04:25.000 Good reaction of fans. 04:25.000 --> 04:28.000 Less than the last time, who is using DNS? 04:28.000 --> 04:30.000 Who has a DNS record set up? 04:30.000 --> 04:32.000 Okay, 50, 50, maybe. 04:32.000 --> 04:36.000 So, basically, Google.com, whatever. 04:36.000 --> 04:40.000 This is the main name and it is a global decentralized system 04:40.000 --> 04:47.000 that we use to configure these key value stores, essentially. 04:47.000 --> 04:52.000 So, what we can do with Eileen is for a service such as the mail server, 04:52.000 --> 04:54.000 when the service is enabled. 04:54.000 --> 04:59.000 So, make if you configure mail server to enable, 04:59.000 --> 05:04.000 we can automatically create all the DNS records that we might need for that service 05:04.000 --> 05:06.000 in the next office module itself. 05:06.000 --> 05:09.000 So, it is declarative DNS through Nick sauce module essentially. 05:09.000 --> 05:14.000 There is more experimental integration with a name server that can 05:14.000 --> 05:19.000 also provision the TLS certificates via Captain ProtoRPC. 05:19.000 --> 05:27.000 This is useful when you might be behind a VPN or not running a publicly accessible 05:27.000 --> 05:29.000 web server. 05:29.000 --> 05:34.000 So, some examples of how you might use this is using a matrix server 05:34.000 --> 05:35.000 and deploying a bunch of bridges. 05:35.000 --> 05:37.000 And we aim to be as simple as that. 05:37.000 --> 05:43.000 So, we aim for a score of 100% on the internet.nl security testing. 05:43.000 --> 05:45.000 Very much useful. 05:45.000 --> 05:48.000 And I think that my time is up, so thank you. 05:48.000 --> 05:58.000 Thank you.