WEBVTT 00:00.000 --> 00:24.440 So welcome. I would like to present to you a completely brand new email application. 00:24.440 --> 00:32.760 It's very different from Arc. It's email, chat, media conference, calendar, contacts, and 00:32.760 --> 00:39.080 five sharing all-world into one application. And we're looking after giving a little 00:39.080 --> 00:47.040 of the gift competition to Outlook. First about myself, I've been working for about 25 years 00:47.040 --> 00:53.520 as a core contributor to Thunderbird. I started in 1999, and I've been on in the 00:53.520 --> 01:00.960 product leadership until last year, when I resigned for ruler. I've been in like the 01:00.960 --> 01:04.960 auto configuration 15 years ago, that was my idea, that you can automatically come 01:04.960 --> 01:12.720 from your email client, Apple Mail, until today, cannot do that. And I've been writing 01:12.720 --> 01:20.160 lots of the IMF, Pop3, and S&TP authentication logic, a lot of the plaintext, email handling, 01:20.160 --> 01:26.000 and lots of other stuff. In the recent years, I've been doing an add-on, which connects Thunderbird 01:26.000 --> 01:32.240 to Office 365, and Microsoft Exchange Service, because Thunderbird natively cannot do that yet. 01:32.240 --> 01:37.600 And that gave me a little insight into the corporate world how they are using email, 01:37.600 --> 01:42.640 and what I saw was shocking, and that was one of the reasons what triggered a building 01:42.640 --> 01:46.800 perula, and I'm going to talk a little bit about this. I've also been for 20 years, 01:46.880 --> 01:52.240 consultant, for companies, tech-lead, building software applications, for software companies, 01:52.880 --> 02:02.240 and some of them reach multiple millions of users. So when I did out, I was really shocked 02:02.240 --> 02:08.640 in which the date email is. You probably know just that about 30% of your friends are using 02:08.640 --> 02:15.280 Gmail, and the corporate world is much, much worse. There is very difficult to get real statistics 02:15.280 --> 02:19.680 about that we search for days, and we can, because depending on how you measure, it's very different. 02:19.680 --> 02:26.400 But from what I've been seeing, I would guess that 80% to 90% of the companies are using Microsoft 02:27.360 --> 02:32.160 Exchange, either on premise, traditionally they had an exchange server in their office, 02:32.160 --> 02:38.560 but many of them today are switching over to Office 365. My guess would be that about 60% of all 02:38.640 --> 02:44.400 companies worldwide, or at least in the western part, are using Office 365 by now. 02:46.160 --> 02:51.040 If you look at who that is, that's really like pretty much every company, Samsung, Sony, 02:52.320 --> 03:00.960 Cisco, even direct competitors choose to Microsoft, are enemies of Microsoft are using Office 365 03:00.960 --> 03:06.240 to host their emails. And I was really shocked to see that. And these are companies who sell 03:06.240 --> 03:14.480 email servers, and they use Office 365. So why is that? It's really unhealthy 03:14.480 --> 03:19.760 states that we're in, because if the communication is controlled by a single company, that is 03:20.000 --> 03:24.960 obviously a problem, I don't need to tell you why. It's a problem for privacy for people. 03:25.760 --> 03:33.360 It's the direct conflict to the GDPR in Europe. It's a problem for the confidentiality for companies 03:33.440 --> 03:38.960 to lead their business secrets. And it's not just companies, they're also universities. 03:38.960 --> 03:44.640 We're standing here in the ULB, University of Nebraska. This is an open-source fashion, 03:44.640 --> 03:49.440 I would assume, because we're here, right? I would assume to have the competence to set up an 03:49.440 --> 04:00.560 email server, guess what they're using. So why is that? But I was wondering, why? Like there 04:00.560 --> 04:05.440 is so many good email servers out there, they're for free. You can set them up. We have stalwart 04:05.440 --> 04:12.560 right here, we have Mox here, we have Doffcott over there somewhere. And why? I mean, they have 04:12.560 --> 04:16.720 the competence, like in university, has an IT department, why do they not set up their own server? 04:17.920 --> 04:23.360 Well, it's the clients. The companies feel like they don't have a real alternative, because 04:23.360 --> 04:30.400 what they see, it's a client. And the clients that open-source are just not up to the job for being used 04:30.480 --> 04:36.480 in a big company with 30,000 users. We have the EU commission here. They're using what 04:36.480 --> 04:42.240 get a while you're guessing. And there's a big intergovernmental fight about that in the EU. 04:42.240 --> 04:48.000 And they feel like they have no alternative. Why? Because they need this, they need the email client. 04:48.000 --> 04:53.440 And it needs to work for the manager. What is the manager doing all day long? He's doing meetings. 04:53.440 --> 04:57.440 He's not writing emails, he's doing meetings. So the calendar needs to work well. The schedule needs 04:57.440 --> 05:02.000 to work well. He needs to see when people are free. And oftentimes, it's not him doing that. 05:02.000 --> 05:07.680 It's a secretary doing that for him. So that kind of process needs to work really well. And we don't 05:07.680 --> 05:14.000 really have good open source alternatives for these kind of use cases, where which can be used by 05:14.000 --> 05:23.040 30,000 people. So they have long email threads, then you do pair features. So it's the clients. 05:23.040 --> 05:28.080 They need outloaded any teams. They need desktop client. They need chat. They need video conference. 05:30.080 --> 05:34.800 So let's do something about that. That's the purpose of prula. 05:36.080 --> 05:40.720 This is a completely fresh new written from scratch email client. Obviously, I'm using libraries 05:40.720 --> 05:45.040 for when I can. I'm not re-venting the wheel. If there's already a good well-working library, 05:45.040 --> 05:50.160 but otherwise it's a completely written from scratch. With my background from Thunderbird, 05:50.160 --> 05:55.120 I heard a lot of feedback over 25 years. You can assume that. So I'm trying to take 05:55.120 --> 06:00.560 apply that kind of knowledge so that it works for the old-time internet people, 06:00.560 --> 06:05.040 at least to some degree. That's, but that's not my core market. You can use Arc if you want to. 06:06.640 --> 06:12.640 But to build a client that works for everybody, including for corporations, for governments, 06:12.640 --> 06:19.920 like a big user group that does not really, is not nerdy, but just wants the thing to work 06:19.920 --> 06:25.680 and not think about it. Still, email is a port for them. Some of them are spending two to five 06:25.680 --> 06:30.800 hours per day with an email client. So this needs to really work smoothly for them. 06:30.800 --> 06:35.440 They cannot use a patchy solution that works kind of. It needs to go well. 06:37.040 --> 06:41.920 I would like to also for this to work for private people, for your family, for your 06:41.920 --> 06:45.680 amount, for your friends that would like this to work as well. If you want an email client 06:45.680 --> 06:50.720 to give to your family, I want this that you can give them for Rula and not worry about it. 06:52.320 --> 06:56.480 In, I would like to innovate. I would like this to be fresh, to be making something new, 06:57.760 --> 07:01.920 Hansio called this modern email and I want to make email modern again. 07:01.920 --> 07:06.640 There's no need why we need to run after WhatsApp. We can actually overtake them with innovation 07:07.280 --> 07:11.840 because WhatsApp is controlled by a single company. If email is free, we can actually innovate 07:11.840 --> 07:18.080 much more and do much better. I give you a very simple example, try to make a meeting with 15 07:18.080 --> 07:23.680 people and agree on a time and do that by email. Anybody ever try to do that? It's not pretty. 07:24.960 --> 07:30.000 Try the same thing with WhatsApp. They just have you make a poll in as much much easier, 07:30.000 --> 07:35.120 and we can actually go better than that. We can build specific features to accommodate that specific 07:35.120 --> 07:39.200 use case, so it's actually easier than a WhatsApp. We just need to do that and we need to get 07:39.200 --> 07:44.640 out of this idea that email is just simple plain text written from one human to another because today 07:44.640 --> 07:50.320 it's not. So the idea here is to have a fully integrated email client that 07:51.520 --> 07:56.560 includes everything that you need to communicate with another human being, no matter on which channel 07:56.560 --> 08:02.240 it is, no matter which form of communication that is. It should include email, chat, video conference, 08:02.720 --> 08:07.760 and if you want to transfer files, it can do file sharing in so long. 08:09.440 --> 08:15.520 So it has multiple applications built into one, and I would like to give you a demo for that. 08:16.560 --> 08:21.600 So that's not my notebook. This is a life demo now, so I'm going to see how well that works. 08:24.000 --> 08:29.040 Can you hear me well at the back? Is this all good? If you don't, because I'm sitting down now, 08:29.040 --> 08:42.320 you're pleased to be able to look at it. So this is a set up, adding an email address. 08:42.320 --> 08:44.320 This is just a test email address. 09:00.000 --> 09:04.480 So did you notice how long this took? Half a second, found the configuration? 09:08.400 --> 09:10.400 It's done. Set up. 09:12.640 --> 09:18.880 So now you can add additional accounts here. So you can add all your email accounts and 09:19.680 --> 09:23.520 hopefully they're able to all work with one exception prototype because it doesn't support IMF. 09:24.320 --> 09:28.960 And you can add calendar accounts, video conferences, chat accounts, and so on. 09:31.120 --> 09:35.920 So I'm going to click on the first one, and you see the email inbox is already there. 09:37.280 --> 09:45.520 I can scroll through it. You should be able to scroll through 40,000 or 100,000 emails with the same 09:45.520 --> 09:50.000 speed as I'm doing here now. I just don't have that many emails here in this test account, 09:50.000 --> 09:52.480 but it should be going straight down. 09:54.000 --> 09:57.840 This, um, the classical view here, the accounts you select here. 09:59.120 --> 10:04.080 I, this is now the view for which looks a little bit like Microsoft Outlook with the three 10:04.080 --> 10:10.400 pain things. The vertical column, we call this the vertical view, but, oops, sorry. 10:13.200 --> 10:18.880 Maybe I'm full screened. But you can also do the classical table view 10:19.840 --> 10:25.040 that you might be used from a more traditional email clients, and it looks like this. 10:25.680 --> 10:30.560 And it's the same here. You can scroll through easily through this. 10:32.720 --> 10:38.720 And we are also building a chat view, which doesn't work yet, where you can view emails 10:38.720 --> 10:43.040 in the same way that you see what's at messages, and the emails are going to compress, 10:43.040 --> 10:45.920 and it's going to be shown like a kind of like a chat conversation. 10:48.960 --> 10:55.520 So that's the email part. So the mail part, we're concentrating first on building the mail 10:55.520 --> 10:59.920 part. The mail part is roughly in beta right now, and I need you help for testing. I'll talk 10:59.920 --> 11:05.200 about that later, but we're also building the other features. So I'm for now I'm going because 11:05.200 --> 11:09.840 we haven't implemented all of that yet. We have some video conference built in, which is actually 11:09.840 --> 11:17.920 working. We have some matrix implementation that is kind of pre-alpha, so it's not ready to show 11:18.000 --> 11:24.720 you yet. We're going to working on XMPP protocol, and I want for video conference I would like 11:24.720 --> 11:31.360 to support JITC and the number of others. So the idea here is to have a multi-protrical strategy 11:31.360 --> 11:37.680 to be able to connect to pretty much everything that is either an open standard or in widespread 11:37.680 --> 11:46.720 use if possible. By the way, I have mentioned that as runs on Windows, Linux, and Mac, 11:46.960 --> 11:51.920 and we're going to build clients for Android and iOS as well as soon as we have time, 11:53.120 --> 12:02.960 which is hopefully mid this year. So this is now some demo data that I'm loading, 12:06.240 --> 12:12.480 and I would like to show you the concepts here. So here I'm getting email from the 12:13.360 --> 12:18.560 imaginary one-drill moan, so I clicked on this email to read this email from him, 12:20.400 --> 12:27.360 and then I can click on chat, and I see the chat messages with that same person. 12:28.400 --> 12:34.000 So I'm reading the email and I want to respond to him directly because I want to follow up. 12:34.000 --> 12:39.360 I just need to click on the chat and I see the chat messages and I can directly send him 12:39.440 --> 12:51.120 the chat. So the advantage here is that I don't have to go, did not work, I guess, huh? 12:51.120 --> 12:59.440 Okay. Well, it's just email feature. The advantage here is I select an email, I can seamlessly 12:59.440 --> 13:04.000 go over to chat, continue to chat with him without having to switch to another application and 13:04.000 --> 13:09.520 find the same person again in my contact list. I just click on chat and it's already there. 13:09.520 --> 13:13.440 And I can do the same thing with the video call, if I want to call him directly, 13:13.440 --> 13:20.320 either by video or by phone, I just click on need, and here is a button called his guy, 13:22.320 --> 13:26.160 and I can directly call him. Very pretty face. 13:26.720 --> 13:38.560 I'm going to make some test call, so no, he's not sleeping so. 13:41.360 --> 13:48.320 So this is here the participants. So now I can add some other person in the participants list, 13:48.400 --> 13:57.120 but just clicking here and adding whatever, whatever we have here is also test data. 13:57.120 --> 14:02.560 So normally, if I type somebody here, there would be a pop-ups that can select from my contacts list, 14:02.560 --> 14:08.880 which person I want to bring in. And the application can look in my contacts, which forms of 14:08.880 --> 14:14.080 communication I know for that person. So for example, if that other person I want to bring in is 14:14.080 --> 14:21.680 in my company, it will make a direct message to this and bring on his application in the 14:21.680 --> 14:28.960 same way that you just saw the incoming call coming. And if the other person is, for example, 14:28.960 --> 14:34.640 if I'm calling my mother and I'd only have a contact from my mother, it will take the URL 14:34.640 --> 14:39.440 to the online meeting and send the URL for what's up to her. Or if I'm caught into a customer 14:39.440 --> 14:44.240 and I have an email address for him, it will take the URL for the meeting and send the meeting 14:44.240 --> 14:49.920 URL to him by email. And here I don't have to care about that. I just have to enter which person I 14:49.920 --> 14:54.720 want to talk to or bring into the meeting and the application can know what is the performed form 14:54.720 --> 15:00.240 of communication with that person and send him the meeting link to that person and then they just 15:00.240 --> 15:04.720 need to click on that link and open up in the browser and he's going to have the meeting in the 15:04.720 --> 15:10.880 browser here and they can call and talk with me here in the in the prola you are. And if on the other 15:10.880 --> 15:15.440 and they also have prola because in the same company they will see that the call here in prola. 15:18.640 --> 15:25.200 We also get the calendar okay so here oh by the way if I'm in the meeting, 15:25.200 --> 15:41.600 I don't know something broke. That's something metal sorry. That's a demo like sorry. 15:42.240 --> 15:57.360 So this is a calendar. There's a two-paying view. I can see that today and the whole month. 15:58.400 --> 16:06.400 And we have contacts here. It can see the different contacts can add different communication methods 16:07.040 --> 16:15.120 in different forms. We also have file sharing okay there's nothing here here now but in the 16:15.120 --> 16:21.680 file sharing tab I should would be seeing which emails which files as exchange with that person. 16:21.680 --> 16:26.800 And if I send an email to somebody with an email file attachment it would appear here. I just 16:26.800 --> 16:31.360 need to click on the person and you can find the file that I sent to them but either by email or by 16:31.360 --> 16:36.800 chat or by a file sharing with web dog or a nice cloud or something. So we want to integrate next 16:36.800 --> 16:44.880 cloud and own cloud and whatever so that it can share files this way. There's also an app 16:44.880 --> 16:52.880 feature here where I can integrate a third-party web apps like Nero or whatever using 16:53.360 --> 16:58.960 ox stocks or a cook pad you can include that and work with somebody else this way. 17:03.600 --> 17:10.080 That's a little bit the demo regarding features so for mail we are implementing currently 17:10.080 --> 17:20.480 I'm app. We've implemented J map just to me yeah for the cloud this cloud for it's like last week 17:20.480 --> 17:27.760 I've looked at J back for the cloud for it. We're implementing three different Microsoft exchange protocols 17:27.760 --> 17:34.880 implementing EWS active sync and OWA which is three different ways to talk to exchange servers so 17:34.880 --> 17:39.600 no matter what your administrator has enabled it is able most likely you can get to the email. 17:40.480 --> 17:47.680 OWA is an protocol that I think no other email client implements and so if you have the 17:47.680 --> 17:54.000 old web access interface you can go to your web mail for your company you can probably get to that 17:54.000 --> 18:00.400 with our look and I don't think it has any other email client which can do that and 18:02.640 --> 18:10.000 anything else yeah it runs on Linux Mac and Windows right now in with planning for Android and 18:10.000 --> 18:18.640 IOS all right so let's roughly the idea do you have any questions yeah everybody go 18:26.640 --> 18:28.960 all right let's start in the front 18:40.240 --> 18:46.080 so if we if you're using exchange protocols like active sync EWS or OWA we're already bringing 18:46.080 --> 18:52.480 in your address book from your account so that we already thinking that you can change it right to it 18:52.480 --> 18:58.480 and the changes will be applied on the server we don't support the global address book yet so 18:58.480 --> 19:03.840 that you can just look for anybody in the company but we're planning to do that we're also planning 19:03.840 --> 19:12.240 to do CalDov and CardDov so to have open protocols to do that and as soon as somebody 19:12.240 --> 19:18.000 implements that we have Jay Jay's calendar or Jay's contact we would like to implement that as 19:18.000 --> 19:30.800 well for Jay Map it's either XMPP or both so you can add whatever accounts you have XMPP 19:30.800 --> 19:38.720 matrix and we try to implement also proprietary protocols if we can we will see what how that works 19:39.520 --> 19:43.600 so basically the idea is whatever accounts you have you should be able to bring it in here if possible 19:43.600 --> 20:02.160 yes search let's see about that so there's a search feature here this is now I don't 20:02.160 --> 20:12.720 have to try that with a demo data let's see how that works do we have any web to east of yes 20:12.720 --> 20:20.640 so I just type here and this email is up here here and I can search save the search as a folder 20:20.640 --> 20:25.600 so I have the dynamic like whenever a click is a virtual folder when I click on that folder it 20:25.600 --> 20:30.960 we run set search and next things we're going to like next few weeks we're going to build rules 20:30.960 --> 20:35.520 so that when you've made a search you can save that search a rule and then say okay filter all these 20:35.520 --> 20:40.800 emails that I see here into that folder or mark them as deleted or something thank you 20:49.680 --> 20:50.800 I like your battery 20:50.800 --> 21:06.160 yes yes yes yes for phone yes we do so it's going to be part of the meet so if you have a 21:06.160 --> 21:12.560 zip account you should be able to set that up as and then you can call with a normal 21:12.560 --> 21:22.560 phone system yes based on the contacts there exactly good idea 21:32.560 --> 21:39.120 very good question yes we plan to support add-ons I haven't done the like word yet to 21:39.120 --> 21:44.640 implement that because you want to bring them in a little sandbox and make the API available on 21:44.640 --> 21:49.680 all that but yes we're planning that I haven't really decided how exactly we're going to do that 21:50.480 --> 21:56.160 but so the idea would be yes if there's new email coming in you have the ability to process that 21:56.160 --> 22:01.680 so if you have whatever you have an invoice coming in you can process that or you can do some 22:01.680 --> 22:07.440 things about that or if you can set when you send out an email specific points that add on can 22:07.680 --> 22:25.760 into act yes right yeah well they they are really doing the same mistake that 22:26.800 --> 22:31.360 therefore there's been doing that they're cutting off the old extension system and building in 22:31.360 --> 22:36.400 you one which they've been killing a lot of the extensions but yeah the ideas to do that 22:44.400 --> 22:50.320 yes it's like on the back of the feature list because we're looking at how many people are 22:50.320 --> 22:56.480 actually using encryption is and in reality is like 1% to 5% of the user base so it's not the 22:56.480 --> 23:01.040 first feature we're implementing but yes we want to do with extensions we want to implement both 23:01.040 --> 23:11.040 SMIM as well as PTP yes correct wait did you see that 23:23.760 --> 23:29.200 not yet so first we want to finish email then we want to do the other features then 23:29.200 --> 23:35.920 we want to do Android then iOS and the next thing is web so web is web version is basically the 23:35.920 --> 23:42.160 same thing with the back at cart off by the way just to add to this we're really paying attention 23:42.160 --> 23:47.040 for being code architecture we're clearly separating the front end from the back end so the 23:47.040 --> 23:52.160 protocol implementation are completely independent from the UI the UI is very thin so it would be 23:52.160 --> 23:57.600 possible to write a different UI for the same back end features on adding a new protocol is really 23:57.920 --> 24:03.040 easy because we're clearly separating front end from back end so this is kind of lessons learned 24:03.040 --> 24:05.040 from other email claim 24:13.600 --> 24:19.440 no this is completely independent from Mozilla the main funding has been providing myself 24:20.480 --> 24:26.080 from our money and we've gotten a grant quite recently from an alnet the 24:26.080 --> 24:30.080 NGI you might have seen them here on first them so they're funding our project 24:32.160 --> 24:34.560 for this year at least and hopefully a little bit longer yeah 24:36.640 --> 24:40.160 and to answer I think your question goes to the business model are the guys 24:44.960 --> 24:52.800 so the the the the money long term is is because I need to pay rent somehow right so long term the 24:53.440 --> 24:58.880 money is going to come from the proprietary protocols and not open sauce so the course open 24:58.880 --> 25:03.040 sauce the open standard should be open sauce this two things that I'm not open sauce is the 25:03.040 --> 25:09.280 proprietary protocols like the exchange protocols or if you make a proprietary google connector 25:09.280 --> 25:15.280 that would be paid add on and the video part is not the video conference part is not open sauce but the 25:15.280 --> 25:23.440 rest is my mother's in the may and I won't chat with her I'd be come to chat with her 25:31.920 --> 25:36.720 with the address book with the address book so it recognizes when you read the email it recognizes 25:36.720 --> 25:40.960 from your address book finds the identity in your address book and it sees okay I have this other 25:41.520 --> 25:45.360 at this other contact chat contact and it finds the same contact 25:50.160 --> 25:52.560 if you don't have your mother in your address book you have other problems 26:02.400 --> 26:03.600 sorry I couldn't hear can you say again 26:11.920 --> 26:25.600 in your company so your company deployment we haven't really figured out a real way how to do 26:25.600 --> 26:31.200 then absolutely no questions asked part yet so what you would do it would pick up up the same 26:31.200 --> 26:37.360 dialogue that you see and your email address you lock in but then you're fine I would like to build 26:37.360 --> 26:41.840 the feature that when you deploy that in a whole company it automatically knows your email address 26:41.840 --> 26:47.280 but I need to talk to some administrators how exactly they want to work it depends on the specific 26:47.280 --> 26:52.240 environment but yeah we want to do that not yet 26:53.200 --> 27:01.200 yeah I'm very sure I'm very happy I want to find a feature is it like something developed by 27:01.200 --> 27:09.600 the power itself or to grow the attachments the files feature we're going to do implore 27:09.600 --> 27:14.800 what that I would like to integrate with next cloud and out and cloud so that you can share files 27:14.800 --> 27:20.240 with a specific person and it creates a link and it can send the linkless way and it's going to 27:20.240 --> 27:24.400 show your email attachments that's already working right now so when you get your email you can 27:24.400 --> 27:28.400 you click on the person you can see the email attachments that you change with that person 27:28.400 --> 27:31.600 and the same thing with the chat 27:32.640 --> 27:39.440 thank you I hope that's something very very important things 27:41.280 --> 27:46.720 we need you help right now we feature complete we need data testing so please please please 27:46.880 --> 27:52.240 install this tried with all your accounts and give me the feedback whether it's working well 27:52.240 --> 27:57.120 what is not working for you if if you want to make this your primary email client and what doesn't 27:57.120 --> 28:01.920 work for you please send me we need that feedback this is how we need to progress right now 28:01.920 --> 28:05.840 and please help spread the word about this this is what the two-blocking things that we have right now 28:05.840 --> 28:10.160 please spread the word and please give us feedback