WEBVTT 00:00.000 --> 00:15.200 The work for an organization that's completely modern and fully AI enables. 00:15.200 --> 00:20.160 It's I can, which is the organization that runs the DNS and apart from showing the 00:20.160 --> 00:24.480 AI enabled first page I have to show this. 00:24.480 --> 00:32.840 I can is a bunch of meetings, a bunch of consensus finding, not my favorite task, but 00:32.840 --> 00:39.160 I'm very glad that we do it, particularly this year, I appreciate actual cooperation and 00:39.160 --> 00:40.160 it's hard. 00:40.160 --> 00:46.800 There are 200 countries, maybe 500 or 1000 organizations that need to cooperate in order 00:46.800 --> 00:52.120 to have a single internet for all of us. 00:52.120 --> 00:56.200 The technical side of I can include things like issuing numbers. 00:56.200 --> 00:58.720 You probably know all of those four numbers. 00:58.720 --> 01:08.440 It also includes IP addresses and much else and many more fringe tasks. 01:08.440 --> 01:15.120 There's someone probably somewhere I can today who researchers DNS bugs, searches. 01:15.120 --> 01:20.600 Why are there so many lookups for domains in the .tu e top level domain, but only on 01:20.600 --> 01:24.440 Tuesdays. 01:24.440 --> 01:27.560 The bug didn't apply to Monday. 01:27.560 --> 01:29.760 Somebody has to do this in order to make the DNS work. 01:29.760 --> 01:32.760 It's our job. 01:32.760 --> 01:38.360 My job is to learn with unique codes. 01:38.360 --> 01:44.640 Ideancy is about using about a quarter of unique codes for domains, 35,000 code points, not 01:44.640 --> 01:46.120 all of them. 01:46.120 --> 01:52.120 In nights during the bare and food event, I will be happy to talk a bit about that. 01:52.120 --> 01:58.240 My job is about using the same part of unique codes in everything else. 01:58.240 --> 02:02.600 Most notably email addresses. 02:02.600 --> 02:05.800 Well, and everything else. 02:05.800 --> 02:12.400 I do that because I want to use my skills to help the world forwards. 02:12.400 --> 02:15.000 That's also why I'm an ITF contributor. 02:15.000 --> 02:24.600 I have maybe 15 RFCs and I have written a truckload of open servers with past 30 years. 02:24.600 --> 02:27.200 I've used the same email address for 30 years. 02:27.200 --> 02:28.200 Anyone else? 02:28.200 --> 02:29.200 No. 02:29.200 --> 02:30.200 Come right. 02:30.200 --> 02:31.200 Wow. 02:31.200 --> 02:33.200 No, too. 02:33.200 --> 02:34.200 Verified. 02:34.200 --> 02:40.120 And I'm self-hosted for almost all of that time. 02:40.120 --> 02:47.120 Last year, I needed to test some self-hostible webmail systems because some people, for 02:47.120 --> 02:52.600 example, in India, using Devon Array, want that. 02:52.600 --> 02:53.360 So I found some. 02:53.360 --> 02:58.000 I tested them in the course of doing that. 02:58.000 --> 03:00.520 I learned about webmail. 03:00.520 --> 03:04.760 It's very much better than it was five years ago. 03:04.760 --> 03:12.560 Since despite having used mutt, news, MH, that kind of two before 30 years, I now actually 03:12.560 --> 03:15.160 use webmail. 03:15.160 --> 03:17.720 I send HTML email. 03:17.720 --> 03:24.840 Feel free to interrupt me on the way. 03:24.840 --> 03:34.720 The new webmail systems that we have might appeal to many people who like self-hostible 03:34.720 --> 03:42.800 testing in general, even if it has been much too difficult in the past decades. 03:42.800 --> 03:48.720 There's a group of systems that are just webmail. 03:48.720 --> 03:54.960 They tend to use SNTP and IMAP and access a mail store somewhere. 03:54.960 --> 04:01.120 Some of them can actually access your mail running at Gmail. 04:01.120 --> 04:07.320 It's entirely clear to me why one would want to do that, but open source, if you can do 04:07.320 --> 04:10.000 what they want. 04:10.000 --> 04:16.200 Then we have a set of webmail systems that drive for feature parity with the big freemail 04:16.200 --> 04:18.720 hosties. 04:18.720 --> 04:25.280 Most notably contacts and calendar, but files are also appearing. 04:25.280 --> 04:29.720 These people overlap with the J-MAP crowds. 04:29.720 --> 04:34.200 How many people know about J-MAP? 04:34.200 --> 04:35.200 Nothing. 04:35.200 --> 04:44.840 And then there's the total takeover system to where you copy your email there, forget what 04:44.840 --> 04:50.400 you had before. 04:50.400 --> 05:01.840 It's not a mail, the purist of the pure webmail systems with mentioning, well, because 05:01.840 --> 05:06.160 it's the purist really, it's a small email system. 05:06.160 --> 05:14.280 It just received your email, answers your email, and tries to be really fast about it. 05:14.280 --> 05:22.840 Yes, and IMAP had written one of the IMAP RFCs and contributed to most of them, surprised 05:22.840 --> 05:26.520 by how well it's able to use IMAP. 05:26.520 --> 05:32.200 It's quick and done, a very pleasant user experience. 05:32.200 --> 05:39.000 Part of that comes from Rayen Luke, which is for support from, part of that is strong focus 05:39.000 --> 05:41.120 on actually being snappy. 05:41.120 --> 05:42.720 They benchmark. 05:42.720 --> 05:43.720 They care. 05:43.720 --> 05:46.800 That's almost the only thing they do care about. 05:46.800 --> 05:48.800 It has to be fast. 05:48.800 --> 05:50.640 It has to be pleasant to use. 05:50.640 --> 05:54.240 There aren't many features. 05:54.240 --> 06:05.560 The important feature is, though, RFC-6154, which is, which is an RFC from Google describing 06:05.560 --> 06:11.840 the magic Gmail mailboxes, like archive. 06:11.840 --> 06:19.840 If many IMAP service support that by and by, if the IMAP service supports it, then it 06:19.840 --> 06:25.840 just works, and there's a single button to archive lots of mail without really reading 06:25.840 --> 06:27.840 it. 06:27.840 --> 06:28.840 Snappy. 06:28.840 --> 06:38.120 Is anyone here really happy about the PHP programming language? 06:38.120 --> 06:44.080 Especially when I worked on some code last year, I contribute to a lot of things that 06:44.080 --> 06:53.120 was quite simply good code, PHP, it's possible. 06:53.120 --> 06:55.720 The greatest respect for the people who do that. 06:55.720 --> 07:02.960 Now, I have the greatest respect for the people who brought an actual good code slide 07:02.960 --> 07:06.760 to PHP. 07:06.760 --> 07:12.120 The more important, perhaps, is that it's regularly updated. 07:12.120 --> 07:24.120 There will be a talk later today that may stimulate some people to issuing quick new releases 07:24.120 --> 07:28.320 to fix some minor problems. 07:28.320 --> 07:29.320 They will do that. 07:29.320 --> 07:31.040 I'm sure. 07:31.040 --> 07:39.600 The mail libraries are forged, they're from, they write IMAP themselves really, started 07:39.600 --> 07:44.880 with libraries, and now they write IMAP themselves, and they do it well. 07:44.880 --> 07:54.760 The emphasis on performance has led to an IMAP client that doesn't make mistakes. 07:54.760 --> 08:02.640 As an IMAP head, I don't look at the protocol trace and see, oh, God. 08:02.640 --> 08:06.520 It's just fast and correct. 08:06.520 --> 08:12.560 It's so fast and correct that this is the one I use despite it being written in PHP. 08:12.560 --> 08:15.120 It looks like this. 08:15.120 --> 08:18.120 How many of you have seen this spam? 08:18.120 --> 08:24.720 I found it by random chance while I was testing these tools, and used it for my 08:24.760 --> 08:30.600 screen shot because it's not anyone's private data. 08:30.600 --> 08:42.320 Getting screenshots through communications review is a very hard job where I work. 08:42.320 --> 08:50.840 It's a simple interface, it's workable, you click these things and it works. 08:50.840 --> 08:59.920 After we have Alps, which is much the same in many ways, except different. 08:59.920 --> 09:06.360 Also really focused on email and using your existing service, assuming that you're happy 09:06.360 --> 09:09.400 with those. 09:09.400 --> 09:18.760 But if you do have existing calendar and contact service, CalDAV and CardDAV, then it will 09:18.760 --> 09:24.440 be used those automatically. 09:24.440 --> 09:32.760 If the server has IMAP metadata support, then we'll use that as well, which is where it 09:32.760 --> 09:40.200 deviates slightly from the read-only file also, because that data is stored in a way 09:40.200 --> 09:49.280 that's visible only to Alps. 09:49.280 --> 09:57.200 To me, Alps seems a little bit more focused on providers, web hosters who will provide 09:57.200 --> 10:00.520 this to their customers and do configuration. 10:01.320 --> 10:03.720 Perfectly usable for someone who's self-hosts. 10:03.720 --> 10:07.040 I set it up in an hour or two. 10:07.040 --> 10:08.040 Not a problem. 10:08.040 --> 10:16.040 I had to set up CalDAV to get it working, get it working as I wanted, but it's workable even 10:16.040 --> 10:21.400 for a single user, but you have to configure it. 10:21.400 --> 10:26.640 The code may be seen as nicer by many people. 10:26.640 --> 10:31.720 It doesn't modern go, it receives updates, that's important to me. 10:31.720 --> 10:40.560 I really do want that if something happens, there will be a quick update. 10:40.560 --> 10:50.760 The documentation for this slide is a little more worthy than the total documentation. 10:51.720 --> 10:57.720 But the code is very nice. 10:57.720 --> 10:59.960 The code is very nice. 10:59.960 --> 11:06.520 Use a stock libraries, again, it uses IMAP and it's in to be flawlessly. 11:06.520 --> 11:15.080 And I believe that there should be a maintainer in this room, no? 11:15.120 --> 11:25.880 Correct, the approach is to, yep, go and praise the increase in nice go codes and ask 11:25.880 --> 11:32.160 him for a better documentation. 11:32.160 --> 11:42.320 Exactly the opposite is representative for, oh, screenshot first, is this IMAP, no sorry, 11:42.400 --> 11:55.000 is this info serency H, in 1991, or is it a modern web mail system? 11:55.000 --> 12:00.840 This is what happens if you just compile it and run it. 12:00.840 --> 12:08.400 You have to configure this thing, the HTML is good, it's fast, and if you give it style 12:08.440 --> 12:22.080 the same thing turns into this, it's the same spam, I think I didn't redirect the sender 12:22.080 --> 12:29.080 quite as well, but I reacted to my own address up there. 12:29.400 --> 12:38.920 Again, it's very fast, oddly, it doesn't have quite the same snappy feeling. 12:38.920 --> 12:43.640 Once you learn it, it's good. 12:43.640 --> 12:48.200 Currier is the opposite. 12:48.200 --> 12:51.800 Currier is also good. 12:51.880 --> 12:59.360 However, oh, in Currier, with a K, if anyone remembers Currier, with a C, this is not that. 12:59.360 --> 13:01.040 Proder opposite. 13:01.040 --> 13:08.040 That was small programming, and another small programming, this is a bunch of note 13:08.040 --> 13:17.120 Js and so many documents that installing it on a gigabit connection to 15 minutes. 13:17.120 --> 13:21.120 I don't know, some people like that style, other people don't, certainly there's a lot 13:21.120 --> 13:29.200 of code reuse going on, and very, very many features, extremely good documentation. 13:29.200 --> 13:37.760 We'll do everything in a sense, if you want local web mail system that looks nice and 13:37.760 --> 13:45.720 copies the mail from your Gmail and sends it out directly via SMTP, we'll do that. 13:45.720 --> 13:52.200 If you want something that copies your mail from Office 365, and delete it from Office 365, 13:52.200 --> 13:59.000 and supports sending mail merge with giant attachments via a send grid, if you generally 13:59.000 --> 14:09.040 like NodeJs, when I wrote this, I said, very rapid development and new, which was entirely 14:09.040 --> 14:15.680 true, but in the post couple of weeks, there have been no commits, until then we're 14:15.680 --> 14:22.040 then three or five minutes every day, extremely rapid development. 14:22.040 --> 14:34.120 To me, it seems to emphasize a single user more, and really want to give single users experience 14:34.120 --> 14:44.440 like the big hostess, extremely pleasant, very, well, a single page app, a nice modern 14:44.440 --> 14:54.320 single page app, and last, which came in for special reasons, is a mail server with a special 14:54.320 --> 14:55.320 feature. 14:55.320 --> 14:57.440 It has been mentioned here before. 14:57.440 --> 15:02.880 The key feature here is that this mail server does not let you make a mistake such that 15:02.880 --> 15:08.800 Gmail rejects your mail. 15:08.800 --> 15:14.000 Many people think it's difficult to configure a mail so that Gmail Office 365 now 15:14.000 --> 15:17.120 Yahoo will accept your mail. 15:17.120 --> 15:23.760 This is a mail server that stores your mail locally, has webmail, has iMac, has everything 15:23.760 --> 15:27.960 you want, and pretty much forces you to have a correct configuration. 15:27.960 --> 15:29.960 And it checks. 15:29.960 --> 15:41.000 When you install it, it connects to Gmail and checks that this looks right. 15:41.000 --> 15:44.400 It's small, it's fast. 15:44.400 --> 15:48.000 This is not NodeJS and Docker. 15:48.000 --> 15:56.080 However, much like apps, it requires that you put some effort into it. 15:56.080 --> 16:05.320 You have to learn how to do backups to yourself, and everyone should do backups. 16:05.320 --> 16:11.640 And it's worse than apps in that respect, because you have to copy your mail into it. 16:11.640 --> 16:18.840 You have to do migration using something like iMacSync. 16:18.840 --> 16:26.480 There's more, however, I ran out of patience while discussing with the comes department 16:26.480 --> 16:28.520 what I can and cannot say. 16:28.520 --> 16:35.000 That's also why I didn't have a screenshot for a career. 16:35.000 --> 16:41.000 If you want to show you the unredacted screenshot of that spam lady. 16:41.000 --> 16:49.240 Same app, rather encourages making single-page apps, and I think someone in the room 16:49.240 --> 16:50.840 is doing that. 16:50.840 --> 16:53.240 It will be great when it comes. 16:53.240 --> 16:59.520 So what we have is a new generation of email tools and it's still growing. 16:59.520 --> 17:05.120 Some of the old tools are still improving. 17:05.200 --> 17:12.800 Mail in the box and roundtube have both had fairly recent releases. 17:12.800 --> 17:14.920 The number of options is growing. 17:14.920 --> 17:18.320 From my point of view, this is great. 17:18.320 --> 17:22.760 I want the net to be there for people. 17:22.760 --> 17:26.160 There's a lot. 17:26.160 --> 17:32.360 I want to tell this slide about the sweet new week. 17:32.400 --> 17:38.720 In summary, what we have now is a new generation tool that gives people options. 17:38.720 --> 17:47.360 People such as me who have an old mail store, there are options for us in the plural. 17:47.360 --> 17:53.240 For people who are not happy with wherever they're made is now, there's an option 17:53.240 --> 17:59.480 mox, for example, there are other options. 17:59.480 --> 18:04.240 I mention mox because it's an all in one thing. 18:04.240 --> 18:13.480 For people who are a little bit more modern than I, I want to have an appetite for 18:13.480 --> 18:27.320 docket, and want to do these complex things with Gmail, I'm extremely happy that we now 18:27.360 --> 18:32.760 have options in the plural. 18:32.760 --> 18:39.880 As I said before, it's still growing. 18:39.880 --> 18:43.560 Highlands, JMAP thing will be presented later today. 18:43.560 --> 18:47.720 Stollward will be presented later today. 18:47.720 --> 18:53.080 This is simply a selection that I picked with the available working time I had in order 18:53.080 --> 18:56.200 to find something that could be recommended. 18:56.200 --> 19:01.240 The result was much better than I hoped, and several of these things actually do support 19:01.240 --> 19:05.080 unicode email. 19:05.080 --> 19:12.840 And even well, I have links to all of them and guess what, I have to show one more I can 19:12.960 --> 19:24.320 paint. 19:24.320 --> 19:29.940 That's right. 19:29.940 --> 19:36.720 Yes. 19:36.720 --> 19:42.800 So, you say do you think that actually this approach of having a single 19:42.800 --> 19:47.000 or running a web mail is good one, is that what you would refer? 19:47.000 --> 19:49.760 Well, do you think that is because you think it's going to be more 19:49.760 --> 19:55.280 snappy or faster, and am I hearing that why do you think 19:55.280 --> 19:59.320 that the JMA should actually be the future of the building 19:59.320 --> 20:05.680 to a webbed line, or the personal PNSA user for it? 20:05.680 --> 20:10.440 OK, I am third repeat the question. 20:10.440 --> 20:14.960 The question in short was about whether single page applications 20:14.960 --> 20:17.400 are better in my personal opinion. 20:17.400 --> 20:19.840 Wow, my personal opinion. 20:19.840 --> 20:24.440 I'm here to provide internet for people, 20:24.440 --> 20:30.120 and we see that the user's migrates in vast numbers 20:30.120 --> 20:36.000 to single page applications, Gmail, more than anyone else. 20:36.000 --> 20:42.000 I think that says that the people have decided. 20:42.000 --> 20:46.240 Now, the question also asked for my personal opinion. 20:46.240 --> 20:51.280 And as well as I have one in that of the testing, 20:51.280 --> 20:55.640 I just continued using a single page application. 20:55.640 --> 21:00.320 It was not put I expected, but it is what I did. 21:00.320 --> 21:03.640 So clearly, there is something in single page applications 21:03.640 --> 21:06.840 that appeals to me as well. 21:06.840 --> 21:11.400 But I think users are the key here, and the users 21:11.400 --> 21:14.680 have voted very strongly for single page applications 21:14.680 --> 21:17.240 at the big mail hosties in the past years. 21:22.040 --> 21:23.880 No, that's. 21:23.880 --> 21:25.080 Yeah. 21:25.080 --> 21:26.680 Another question for the audience is, well, 21:26.680 --> 21:30.040 I'm wondering how many people are using a web mail at all, instead of 21:30.040 --> 21:43.080 using a web mail, is that only web mail or not using web mail? 21:43.080 --> 21:46.080 The last ones were not web mail, or something like that. 21:46.080 --> 21:51.160 Well, I was in the not web mail camp until this. 21:51.160 --> 21:54.760 Now, I use a combination of news in e-mix. 21:54.760 --> 21:56.760 Oh, that's over. 21:57.720 --> 22:05.240 And e-mix, now, and snappy mail, which, oh, and smart phone 22:05.240 --> 22:08.280 mail as well, it. 22:08.280 --> 22:10.360 Does it make sense? 22:10.360 --> 22:13.160 Well, my fingers know these things. 22:13.160 --> 22:16.440 All right, there's one more question. 22:16.440 --> 22:23.640 Does the question was, does Mox provide web mail? 22:23.640 --> 22:25.960 It does provide a web mail. 22:25.960 --> 22:28.040 It works fairly well. 22:28.040 --> 22:31.960 When you look at it, you'll probably 22:31.960 --> 22:36.600 come to the conclusion that Mox is an excellent programmer. 22:41.400 --> 22:42.360 But it works. 22:42.360 --> 22:44.200 I wasn't annoyed. 22:44.200 --> 22:46.120 I got you a relationship. 22:46.120 --> 22:55.240 Oh, and I wanted to show that, but I was too late to review 22:55.240 --> 22:55.960 what's too difficult.