WEBVTT Kind: captions Language: en 00:00:00.060 --> 00:00:01.110 All right, so I have two 00:00:01.110 --> 00:00:02.310 wonderful guys from Tuta 00:00:02.310 --> 00:00:04.010 who are at the Nextcloud conference. 00:00:04.010 --> 00:00:05.750 Do you guys want to kind of just give 00:00:05.750 --> 00:00:07.660 a quick recap of the main things 00:00:07.660 --> 00:00:09.510 that you announced here? Yeah, sure. 00:00:09.510 --> 00:00:11.480 So actually we started developing 00:00:11.480 --> 00:00:14.640 a Nextcloud app quite some time ago. 00:00:14.640 --> 00:00:15.840 And we're not just doing 00:00:15.840 --> 00:00:17.550 the Tuta Nextcloud app, 00:00:17.550 --> 00:00:19.300 but we are also integrating, deeply 00:00:19.300 --> 00:00:22.660 integrating Nextcloud into our Tuta apps. 00:00:22.660 --> 00:00:25.650 So we do bidirectional integration, and we 00:00:25.650 --> 00:00:27.750 believe that's where we create the biggest 00:00:27.750 --> 00:00:30.020 value for our customers and our users 00:00:30.020 --> 00:00:32.369 and of course also for Nextcloud users. 00:00:32.369 --> 00:00:34.380 So I assume the idea here is if someone's 00:00:34.380 --> 00:00:35.700 hosting their own Nextcloud 00:00:35.700 --> 00:00:37.500 or they're using a hosted Nextcloud, 00:00:37.500 --> 00:00:39.310 they can access all of their calendars 00:00:39.310 --> 00:00:41.260 and data inside of the Tuta experience? 00:00:41.260 --> 00:00:42.160 Is that kind of... 00:00:42.160 --> 00:00:43.060 and vice versa? 00:00:43.060 --> 00:00:44.560 Like they can access Tuta Mail 00:00:44.560 --> 00:00:46.380 from their Nextcloud instance as well? 00:00:46.380 --> 00:00:47.600 This is the general idea. 00:00:47.600 --> 00:00:48.530 It's not there yet. 00:00:48.530 --> 00:00:49.580 Not quite as complex. 00:00:49.580 --> 00:00:52.640 But yes, you can have this either 00:00:52.640 --> 00:00:54.340 integrate your Nextcloud into Tuta 00:00:54.340 --> 00:00:55.680 or the other way. Very cool. 00:00:55.680 --> 00:00:57.020 It's cool that you have 00:00:57.020 --> 00:00:58.370 that kind of portability. 00:00:58.370 --> 00:01:00.800 How are you guys, like if I'm a Tuta user 00:01:00.800 --> 00:01:03.839 and I'm starting to use Tuta Drive, 00:01:03.839 --> 00:01:05.170 which I know, I don't think 00:01:05.170 --> 00:01:07.160 it's public quite yet, Tuta Drive? 00:01:07.160 --> 00:01:09.070 It's in beta, but there 00:01:09.070 --> 00:01:10.620 will be public beta soon, yeah. 00:01:10.620 --> 00:01:12.020 Okay, so let's say public 00:01:12.020 --> 00:01:13.620 beta is out for Tuta Drive. 00:01:13.620 --> 00:01:15.100 How am I supposed to decide, 00:01:15.100 --> 00:01:16.880 am I using Tuta Calendar? 00:01:16.880 --> 00:01:18.590 I know that the flexibility is good, 00:01:18.590 --> 00:01:20.030 but like how are you guys kind 00:01:20.030 --> 00:01:20.920 of juggling that? 00:01:21.280 --> 00:01:23.330 And how would you recommend users decide? 00:01:23.330 --> 00:01:25.750 Do I use Tuta Mail inside my Nextcloud? 00:01:25.750 --> 00:01:27.470 Do I use Nextcloud inside my Tuta? 00:01:27.470 --> 00:01:28.970 Yeah, I mean, we leave options 00:01:28.970 --> 00:01:30.120 for the user to decide. 00:01:30.120 --> 00:01:31.170 So we want to make it 00:01:31.170 --> 00:01:33.440 as simple as possible to use. 00:01:33.440 --> 00:01:35.500 So Tuta users will probably just continue 00:01:35.500 --> 00:01:37.620 to use their Tuta Mail app 00:01:37.620 --> 00:01:38.870 and Tuta Calendar app. 00:01:38.870 --> 00:01:40.590 And then from within those apps, 00:01:40.590 --> 00:01:43.770 they can access their Nextcloud data too. 00:01:43.770 --> 00:01:47.300 So they will be able to just save a file, 00:01:47.300 --> 00:01:49.320 an attachment from a mail they received 00:01:49.320 --> 00:01:51.420 on Tuta to the Nextcloud instance. 00:01:51.940 --> 00:01:54.040 And they can use their calendar 00:01:54.040 --> 00:01:56.460 if they want to send a calendar invite. 00:01:56.460 --> 00:01:58.280 They can just with the tip 00:01:58.280 --> 00:02:01.860 of a finger add a Nextcloud Talk link. 00:02:01.860 --> 00:02:03.900 So kind of a remote meeting 00:02:03.900 --> 00:02:05.600 with other participants. 00:02:06.100 --> 00:02:07.140 And we just want to make it 00:02:07.140 --> 00:02:08.800 as easy as possible. There will be also 00:02:08.800 --> 00:02:09.979 different use cases, right? 00:02:09.979 --> 00:02:11.490 If you self-host your own Nextcloud 00:02:11.490 --> 00:02:13.540 instance, maybe the end-to-end encryption 00:02:13.540 --> 00:02:15.420 part is not as important to you. 00:02:15.420 --> 00:02:16.740 Your data is safe at home. 00:02:16.740 --> 00:02:18.500 If you don't, if your data 00:02:18.500 --> 00:02:20.640 is at a friend's house or with some 00:02:20.640 --> 00:02:22.400 provider, you can put your files 00:02:22.400 --> 00:02:24.580 in the Tuta Drive in the future. 00:02:24.580 --> 00:02:26.430 So there will be different use cases. 00:02:26.430 --> 00:02:27.750 That's why the choice is open. 00:02:27.750 --> 00:02:29.400 So this is what we're working on. 00:02:29.400 --> 00:02:31.720 Let's say I link my Nextcloud 00:02:31.720 --> 00:02:33.480 to my Tuta experience. 00:02:33.480 --> 00:02:35.580 Is that done on the account 00:02:35.580 --> 00:02:36.990 or is it done per client? 00:02:36.990 --> 00:02:38.940 Like so each Tuta client that you have, 00:02:38.940 --> 00:02:40.310 you have to link to your Nextcloud? 00:02:40.310 --> 00:02:41.760 It's account-wide, basically. 00:02:41.760 --> 00:02:44.470 I activate it by the admin on the Tuta 00:02:44.470 --> 00:02:46.520 account, but it's available for the users 00:02:46.520 --> 00:02:48.340 on that account and not device-based. 00:02:48.340 --> 00:02:49.940 Is it going to be in the desktop 00:02:49.940 --> 00:02:51.490 mobile apps, or is it just web, 00:02:51.490 --> 00:02:52.490 or all of the above? 00:02:52.490 --> 00:02:53.950 Desktop, mobile, everywhere. 00:02:53.950 --> 00:02:55.100 Got it. Very cool. 00:02:55.100 --> 00:02:55.920 Yeah, thanks guys. 00:02:55.920 --> 00:02:57.470 I'm really excited to see that. 00:02:57.470 --> 00:02:59.270 And it's a really good collaboration 00:02:59.270 --> 00:03:00.180 that I don't think you 00:03:00.180 --> 00:03:01.250 guys really needed to do. 00:03:01.250 --> 00:03:03.040 But I think now that people see the power, 00:03:03.040 --> 00:03:04.940 it's like, whoa. Like, I would have never thought 00:03:04.940 --> 00:03:06.490 about that kind of integration. 00:03:06.490 --> 00:03:08.490 Actually, users are asking for it. 00:03:08.490 --> 00:03:10.040 And we also have some employees 00:03:10.040 --> 00:03:11.790 that really wanted us to integrate. 00:03:11.790 --> 00:03:12.940 So it's all about that. 00:03:12.940 --> 00:03:14.640 We see that there's a lot of value 00:03:14.640 --> 00:03:16.940 in this partnership with Nextcloud. 00:03:16.940 --> 00:03:18.550 And we believe that we 00:03:18.550 --> 00:03:19.800 can make a big difference 00:03:19.800 --> 00:03:22.360 if we partner up against big tech. 00:03:22.360 --> 00:03:23.810 Yeah, cool. Thanks, guys. 00:03:23.810 --> 00:03:24.700 Yeah, thank you. 00:03:24.700 --> 00:03:25.500 Yeah.