1
00:00:00,020 --> 00:00:01,000
I don't want to know your phone number.

2
00:00:01,200 --> 00:00:04,260
I don't want to know anybody's phone number who's using FastMail.

3
00:00:04,800 --> 00:00:07,240
The phone number for account verification.

4
00:00:08,780 --> 00:00:10,060
Welcome to Techlore Talks.

5
00:00:10,180 --> 00:00:14,680
Today I have the privilege of inviting Ricardo from FastMail on the podcast to discuss FastMail,

6
00:00:14,820 --> 00:00:19,500
their approach to email privacy, how it differs from other people who use end-to-end encryption

7
00:00:19,740 --> 00:00:24,480
like Proton, their approach to security, features, why they're even called FastMail, their history,

8
00:00:24,880 --> 00:00:28,260
and how they still approach email security and how they still enable those options.

9
00:00:28,720 --> 00:00:30,680
It's just a very interesting conversation about email.

10
00:00:31,420 --> 00:00:35,300
We ended up talking for almost two hours, and so this was quite an interesting interview

11
00:00:35,450 --> 00:00:38,080
that I had a lot of fun with, and I learned a lot along the way.

12
00:00:38,620 --> 00:00:39,760
Now, to the interview.

13
00:00:40,140 --> 00:00:43,780
All right, well, do you want to introduce yourself and just say who you are and what you're working on?

14
00:00:44,480 --> 00:00:44,800
Yeah, sure.

15
00:00:45,780 --> 00:00:47,420
So my name is Ricardo Cignas, Rick.

16
00:00:48,220 --> 00:00:50,400
I am a chief engineer at FastMail.

17
00:00:51,300 --> 00:00:57,140
Technically, I'm the chief of developer experience, but day-to-day, I mostly work with the Cyrus team,

18
00:00:57,540 --> 00:01:03,220
which is our open source IMAP and JMAP and CalDAV and contact server.

19
00:01:04,540 --> 00:01:08,920
But also, as a chief engineer, I'm one of the people that all the random stuff falls to.

20
00:01:08,970 --> 00:01:12,780
So I've got my fingers in a lot of pies, and I try to keep an eye on everything going on here at FastMail.

21
00:01:13,080 --> 00:01:15,200
And how long have you been at FastMail?

22
00:01:16,240 --> 00:01:21,500
So it's a funny question, because I've been in this job for 20 years.

23
00:01:22,939 --> 00:01:27,220
FastMail bought the previous place I worked, Pobox.com, which is a very similar product.

24
00:01:27,840 --> 00:01:32,020
about 10 years ago. So I've been with Fastmail for 10 years, but it's sort of seamless from

25
00:01:32,030 --> 00:01:39,040
the previous 10 years working on the same stuff. Got it. Why have you stayed with Fastmail? Like,

26
00:01:39,220 --> 00:01:45,740
what about it do you enjoy? What kind of draws you to it? Yeah, there's quite a few things I like

27
00:01:45,840 --> 00:01:52,679
about Fastmail. I think the most important thing is our values. And the technology is really

28
00:01:52,700 --> 00:01:57,200
important. I like our technology and I like the problem space we work in. But I tell people this

29
00:01:57,340 --> 00:02:02,700
story about just about 10 years ago when we from the Philadelphia office had been newly acquired

30
00:02:03,300 --> 00:02:07,940
and we were visiting Australia and we were having a strategic planning session. And one of the

31
00:02:08,119 --> 00:02:12,100
directors said, we really shouldn't be talking about long-term plans without stating what our

32
00:02:12,380 --> 00:02:16,340
values are. So let me write this down. And he stood up and he wrote four sentences on a board

33
00:02:16,720 --> 00:02:21,759
and all the directors said, yep, you nailed it. And like they all knew what the company's values

34
00:02:21,760 --> 00:02:27,640
were, and there was no argument, and we haven't changed them. They're on our blog, and I think

35
00:02:27,660 --> 00:02:31,800
that inside the company, and I hope outside, you can really see that we live those values.

36
00:02:33,140 --> 00:02:38,580
Things like, we are stewards of your data. It's not our data, it's your data. We don't want to

37
00:02:38,600 --> 00:02:43,960
take it. We're good internet citizens. That's why we do open source software. And these values

38
00:02:44,540 --> 00:02:50,539
drive us to do work that I think is worth doing, and that makes me feel good about, you know, what I'm

39
00:02:50,560 --> 00:02:56,780
doing 20 years, right? What I'm doing with my life. Working in email is sort of an outcome of that,

40
00:02:56,870 --> 00:03:02,400
right? If we believe in being good internet citizens, we want the internet to be an open

41
00:03:02,650 --> 00:03:07,540
set of federated systems. And email is the original social network, the original federated system.

42
00:03:08,180 --> 00:03:12,780
And it's, I don't ever want to see it go away. I'd like to see it continue to evolve, which is a

43
00:03:13,080 --> 00:03:18,080
tough proposition. But that's the outcome. That's, I mean, that's the second step, not the first one.

44
00:03:18,120 --> 00:03:20,200
The first one is being a good internet citizen.

45
00:03:20,450 --> 00:03:25,180
So that's, I know it's sort of a pie in the sky answer, but it really is what I like about

46
00:03:25,360 --> 00:03:25,960
FastMail the most.

47
00:03:26,740 --> 00:03:27,000
Nice.

48
00:03:27,180 --> 00:03:34,820
And so when it comes to email, I'd say the majority, I mean, by far the largest provider

49
00:03:34,830 --> 00:03:36,000
is going to be Gmail for people.

50
00:03:36,130 --> 00:03:41,500
And so what makes you a better, and so I'm going to give kind of the, you know, both sides

51
00:03:41,590 --> 00:03:42,700
of the spectrum here.

52
00:03:42,830 --> 00:03:48,080
So we're going to see maybe Gmail on one end, Proton, and kind of where you guys fit and

53
00:03:48,100 --> 00:03:54,160
guys approach this. So when you compare yourself to Gmail, what makes you guys a better, you know,

54
00:03:54,380 --> 00:03:58,540
handler of data? How are you a better internet citizen? How do you compare yourself to that if

55
00:03:58,640 --> 00:04:05,560
someone were to ask you? The answer we used to talk about a lot, and this still gets trotted out

56
00:04:05,560 --> 00:04:12,800
by some people time to time, is we don't read your mail. And I, on one hand, I've never liked this

57
00:04:12,980 --> 00:04:17,420
phrasing. It sounds pretty crappy towards Gmail. They're not reading your, they're not, they're not

58
00:04:17,440 --> 00:04:22,720
out there to read your mail, but they have had a long history of figuring out why are they in

59
00:04:22,990 --> 00:04:27,760
the email market. And some of this is about large scale data analytics, right? And even if they're

60
00:04:27,880 --> 00:04:34,040
not reading your email to do super creepy things specifically about you, why are they doing this?

61
00:04:34,380 --> 00:04:38,540
Right? The old saw that if you're not the customer, you're the product is,

62
00:04:39,520 --> 00:04:42,620
It's a little pat, but it's not totally wrong.

63
00:04:46,139 --> 00:04:48,380
And that's sort of the one big answer.

64
00:04:49,440 --> 00:04:55,720
For me, it's true, but maybe more to the point for me is that I don't think Gmail is very good email.

65
00:04:57,820 --> 00:04:59,120
I live in my email.

66
00:05:00,440 --> 00:05:02,560
I have basically two to-do lists.

67
00:05:02,850 --> 00:05:05,860
I have my email and I have our internal bug tracking system.

68
00:05:06,580 --> 00:05:10,240
So everything that I've got to do in my day is in my email or my calendar.

69
00:05:10,620 --> 00:05:12,180
And my calendar is my email with FastMail.

70
00:05:13,100 --> 00:05:13,940
It needs to be good.

71
00:05:14,390 --> 00:05:16,360
It needs to like organize itself for me.

72
00:05:16,360 --> 00:05:21,200
The search needs to be like unbeatable and using it needs to be quick.

73
00:05:21,640 --> 00:05:24,440
Like not just I click a message and it's immediately loaded.

74
00:05:24,860 --> 00:05:26,320
That's nice, but that's almost candy.

75
00:05:26,940 --> 00:05:31,120
It's when I sit down to do my morning 30 minutes, 45 minutes of email.

76
00:05:32,920 --> 00:05:34,880
It has to feel like there's no friction.

77
00:05:35,300 --> 00:05:36,720
Like I'm just coasting through it.

78
00:05:37,120 --> 00:05:38,740
And when I use Gmail, all I feel is friction.

79
00:05:39,920 --> 00:05:40,800
And some people don't care.

80
00:05:42,420 --> 00:05:45,680
Fastmail is a tiny, tiny drop in the bucket compared to Gmail, right?

81
00:05:45,800 --> 00:05:48,000
The people say Gmail is a competitor.

82
00:05:48,080 --> 00:05:49,480
And like, technically, it's true.

83
00:05:50,460 --> 00:05:53,240
80%, I think, of email addresses are Gmail addresses these days.

84
00:05:53,400 --> 00:05:55,060
It's some absurdly large number.

85
00:05:55,920 --> 00:06:00,100
But we don't have to think about how do we beat Gmail.

86
00:06:00,740 --> 00:06:05,120
It's how do we find users who want the same things out of email that we want to provide.

87
00:06:05,180 --> 00:06:14,220
And for me, many of us have different motivations, but for me, it's that seamless, fast, efficient, in and out, make your life better and get out of the way experience.

88
00:06:15,880 --> 00:06:20,560
I think that's the thing that is most compelling for me in my day-to-day use of FastMail.

89
00:06:20,740 --> 00:06:25,400
The support's also very good, but I don't usually have to worry about the support because I can go log into the servers, and that's not fair.

90
00:06:27,660 --> 00:06:27,760
Yeah.

91
00:06:28,300 --> 00:06:31,780
Did you want me to say more about the other end of that, the proton angle?

92
00:06:32,160 --> 00:06:33,360
I'll get to the other angle.

93
00:06:34,180 --> 00:06:38,420
I do want to first comment that on the other angle.

94
00:06:38,590 --> 00:06:41,680
So I'm still a Proton user right now.

95
00:06:42,120 --> 00:06:43,820
No, no bad blood here.

96
00:06:44,760 --> 00:06:48,500
You even mentioned you saw the comparison before we started recording.

97
00:06:48,610 --> 00:06:53,360
And so I hope that people know my position is like there's different people for each of these different providers.

98
00:06:55,480 --> 00:07:01,800
And let's just say projects that I don't know if I'm allowed to say this.

99
00:07:01,940 --> 00:07:08,120
So a project that I do work for has migrated to G Suite for certain things.

100
00:07:08,270 --> 00:07:12,460
And I had to use Gmail for the first time since like 2015.

101
00:07:13,280 --> 00:07:16,580
It's been like a decade since I've actually opened and used Gmail.

102
00:07:16,950 --> 00:07:23,280
And in my head, Gmail was a really good, clean, minimal, usable email experience.

103
00:07:24,760 --> 00:07:28,200
And my God, it's just not my memory at all.

104
00:07:28,640 --> 00:07:35,940
I don't know if I was disillusioned to think it was good back then or if it's just gotten worse slash the same after 10 years.

105
00:07:36,480 --> 00:07:37,320
But I opened it.

106
00:07:37,500 --> 00:07:39,600
I just wanted a unified inbox.

107
00:07:39,960 --> 00:07:44,720
Now it's like everything's broken up into different inboxes, which is a bit confusing to my brain.

108
00:07:45,100 --> 00:07:45,240
Yeah.

109
00:07:46,180 --> 00:07:50,540
And the settings page is just raw HTML, it seems like.

110
00:07:51,040 --> 00:07:51,800
Yeah, that's a mess.

111
00:07:53,120 --> 00:07:56,840
So, yeah, and it was hard to find where to even add a signature in Gmail.

112
00:07:57,120 --> 00:08:00,900
So I was just very disappointed in the Gmail experience and it felt neglected.

113
00:08:01,500 --> 00:08:05,360
And when I did trial FastMail, it was much cleaner.

114
00:08:05,540 --> 00:08:14,020
And then I actually gained more appreciation for all of the email services, including Proton and Tuda, who I feel like I've in my head painted as worse than Gmail.

115
00:08:14,260 --> 00:08:16,100
But I actually think in some ways they are.

116
00:08:16,140 --> 00:08:19,880
And I do think of all of those three, FastMail is still my top for usability.

117
00:08:20,240 --> 00:08:24,420
So you guys are I still think are killing that usability angle of things.

118
00:08:24,680 --> 00:08:29,620
Because, yeah, it's not that you're not doing a good job, but I don't think it's hard to beat Gmail anymore.

119
00:08:30,420 --> 00:08:36,919
I think both those things are, I think it's true that we're doing a great job, but also Gmail's got a tough position, right?

120
00:08:37,080 --> 00:08:43,599
They're serving individual people who are signing up all the way up to 10,000 person enterprises with one product.

121
00:08:44,000 --> 00:08:46,300
It's just going to be real tough.

122
00:08:47,040 --> 00:08:47,220
Yeah.

123
00:08:47,770 --> 00:08:51,340
So on this note, you know, I want to touch more on the other side of things, data.

124
00:08:51,470 --> 00:08:53,840
But what is kind of your core target demo?

125
00:08:54,060 --> 00:08:58,080
You know, if I'm on your website, it seems like you guys are pretty 50-50 individual in business.

126
00:08:58,460 --> 00:09:00,160
So who's kind of your core target?

127
00:09:00,940 --> 00:09:02,840
Right now, yeah, right now we're much more individual.

128
00:09:03,900 --> 00:09:11,860
We have some businesses, some that are sort of sizable, but I would say mostly very small micro businesses are with us.

129
00:09:13,360 --> 00:09:16,400
I would like to be more appealing to small business.

130
00:09:16,900 --> 00:09:18,260
I think that we have a lot of great features.

131
00:09:18,420 --> 00:09:27,080
And, you know, when I just say Gmail's got a hard time because they've got to appeal to this very, very broad demographic, it creates incentives inside.

132
00:09:28,060 --> 00:09:30,060
I suspect I don't work there.

133
00:09:30,380 --> 00:09:33,960
I suspect it creates incentives inside the product that are sort of competing with one another.

134
00:09:34,080 --> 00:09:37,540
And they lead to this tension in the settings screen or this sort of fruit salad of options.

135
00:09:38,639 --> 00:09:40,960
And we really don't want to be that.

136
00:09:41,300 --> 00:09:48,400
Right. Like we we sort of have a good understanding internally that every extra button is a problem for a lot of reasons.

137
00:09:48,670 --> 00:09:52,300
Every in every a button is bad enough, but like a checkbox is way worse.

138
00:09:52,980 --> 00:09:57,980
A checkbox, any checkbox on your settings page doubles the number of possible configurations a user could be in.

139
00:09:58,300 --> 00:10:01,680
Right. So like you don't want to mess around with just adding lots and lots of options.

140
00:10:02,420 --> 00:10:07,960
And when we say we want to sort of expand to be somewhat more appealing to businesses, that means adding options.

141
00:10:08,200 --> 00:10:18,700
So they have to be really carefully pitched, really carefully put together, because we want the whole product to feel just as perfect to a small business or to a team as it does to an individual.

142
00:10:20,739 --> 00:10:25,100
So maybe it's a long-winded answer to part of that, but that's sort of the how are we split.

143
00:10:25,120 --> 00:10:26,880
We're split mostly towards individuals right now.

144
00:10:27,340 --> 00:10:29,760
I'd like to see that change in the coming year or two.

145
00:10:31,680 --> 00:10:33,740
And then as a question of, well, which individuals?

146
00:10:34,140 --> 00:10:38,780
Earlier I said FastMail is kind of not even a drop in the bucket compared to the size of Gmail.

147
00:10:39,220 --> 00:10:45,340
So, you know, we don't have to worry about carving off 1% of their users and having a huge number of different audiences we appeal to.

148
00:10:46,180 --> 00:10:49,620
The question comes down to, well, for whom are we the best pick?

149
00:10:50,300 --> 00:10:59,420
And I usually start by saying, you eliminate a huge number of people by saying, start with anybody who's willing to shop around for their email.

150
00:11:00,400 --> 00:11:03,400
If someone's like, I need an email account, that means Gmail.

151
00:11:04,060 --> 00:11:08,500
I need an email account. That means Hotmail. There's only so many, depending on your generation.

152
00:11:09,070 --> 00:11:14,100
At some point, I need an email account. It's AOL. But there's just the pick, the default pick.

153
00:11:15,160 --> 00:11:20,200
Once you find someone who doesn't want the default pick, it's a pretty good definition of the starting

154
00:11:20,440 --> 00:11:23,960
point for Fastmail users. And then what do you find? Well, you want people who want something

155
00:11:24,190 --> 00:11:29,319
really, really fast. Not for nothing that Fastmail started in Australia, where I can tell you the

156
00:11:29,340 --> 00:11:37,820
latency times are unbearable. Here, I am milliseconds from data center access. And in

157
00:11:38,040 --> 00:11:42,260
Australia, like, you know, I type in and I wait for my keystrokes to show up. It's painful. So

158
00:11:42,800 --> 00:11:47,120
fast mail being so fast is a function of that. You find people who want what I want,

159
00:11:47,500 --> 00:11:52,920
the productivity built into their email, especially very customizable productivity,

160
00:11:53,420 --> 00:11:57,380
not we have decided how you will be productive, but we are giving you a bunch of tools to figure out.

161
00:11:58,360 --> 00:12:06,620
And then there's the people who are in the privacy space. And I think that your video talking about Tudor and Proton and FastMail is a good slicing of that cake.

162
00:12:06,840 --> 00:12:14,080
Some people are in the privacy space and what they want is privacy. They want to know that nobody wants to use their data, that they can kind of have their own space.

163
00:12:14,500 --> 00:12:22,180
And some people want secrecy. They want to know that their data is unassailable. Their data is noise as far as the service provider is concerned.

164
00:12:22,800 --> 00:12:27,540
And people will look at us and kind of figure out we are providing good privacy.

165
00:12:27,800 --> 00:12:30,180
We're providing decent, we're providing really good security.

166
00:12:31,120 --> 00:12:32,440
And we're providing a great service.

167
00:12:32,720 --> 00:12:38,280
And there's always that slider between, as you said, actually, convenience and secrecy.

168
00:12:38,860 --> 00:12:40,700
And people make their choice on that front.

169
00:12:41,660 --> 00:12:41,820
Yeah.

170
00:12:42,060 --> 00:12:50,140
So that was, you know, definitely the big difference between you and then Tudan Proton is the lack of native end-to-end encryption.

171
00:12:50,300 --> 00:12:54,460
And so why have you opted for that approach for kind of your goals?

172
00:12:56,860 --> 00:13:01,260
I think that end-to-end encryption is good.

173
00:13:01,620 --> 00:13:02,880
I like end-to-end encryption.

174
00:13:03,740 --> 00:13:08,440
And in a perfect world, we would be able to end-to-end encrypt all of our communications.

175
00:13:09,660 --> 00:13:13,760
And for us, I think, or at least for me, but I think I can speak a little more broadly,

176
00:13:14,500 --> 00:13:19,660
the difficulty is that email is not well-suited to end-to-end encryption.

177
00:13:21,200 --> 00:13:26,580
It can get there. I think it requires sort of systemic change, but there's a number of

178
00:13:26,840 --> 00:13:35,100
significant problems. The transmission of email is built around having this RFC 822 and subsequent

179
00:13:35,360 --> 00:13:40,420
standard document, and that document is in the clear. And there have been a number of attempts

180
00:13:40,480 --> 00:13:44,480
to talk about how do you encrypt that document, and many of them are like, well, you encrypt this

181
00:13:44,640 --> 00:13:49,700
part of it, but all these other parts are not encrypted, cannot be encrypted. And the standards

182
00:13:49,720 --> 00:13:58,120
doing that are numerous and really overcomplicated, I would say, and poorly adopted. So this is the

183
00:13:58,180 --> 00:14:03,700
first barrier to just having end-to-end encrypted email work. The next problem is key distribution,

184
00:14:04,280 --> 00:14:08,820
right? You want to be able to email somebody from their business card and send them an encrypted

185
00:14:09,020 --> 00:14:15,360
message. And on the open internet, that's kind of a non-starter. There simply is not a good

186
00:14:16,140 --> 00:14:22,520
private key infrastructure or public infrastructure for doing these kind of from scratch boot ups.

187
00:14:22,680 --> 00:14:29,000
This is a problem that needs to be solved for email to have the kind of convenience

188
00:14:29,860 --> 00:14:34,620
for initiating and carrying on end-to-end encrypted conversations. And if you can't do that,

189
00:14:34,880 --> 00:14:39,839
what you're really saying is we're going to have a sort of walled garden and the wall has to go

190
00:14:39,860 --> 00:14:45,520
somewhere. It might be within our enterprise, right? You're using a Microsoft Exchange server.

191
00:14:45,760 --> 00:14:50,640
You're part of Google Enterprise. Within our enterprise, all the key activation and creation

192
00:14:50,700 --> 00:14:54,700
and trust is generated automatically behind the scenes and you don't worry about it. Your workplace

193
00:14:54,900 --> 00:14:59,480
manages it. All the encryption happens. Everything is perfect. But as soon as you want to email outside

194
00:15:00,000 --> 00:15:05,320
of your ecosystem, and that might be your business, it might be the service provider using, as soon as

195
00:15:05,340 --> 00:15:10,440
you want to go outside of that, weird stuff happens, right? Either they get a message that's

196
00:15:10,460 --> 00:15:14,260
like signed but not encrypted or it's encrypted but not well encrypted or it's encrypted and they

197
00:15:14,400 --> 00:15:19,620
can't read it. Everything gets bad. Or you get what we see in the U.S. with healthcare providers

198
00:15:19,920 --> 00:15:24,620
where you get an email and the email says you have an email. And then that takes you somewhere. You

199
00:15:24,800 --> 00:15:30,860
leave email and you go to the web. And I love the web too, but I don't want my email to be pointers

200
00:15:30,880 --> 00:15:38,720
to the web. That's weird. I want my email to be email. So FastMail is interested in encrypted

201
00:15:38,920 --> 00:15:44,500
email. We would like to make the technology capable of doing that, but it has to stay email,

202
00:15:45,080 --> 00:15:51,840
and it has to stay this open federated system. And until we can do that, I think that we don't want

203
00:15:51,840 --> 00:15:58,459
to compromise on the ease of use, because fundamentally, most users do not need that

204
00:15:58,480 --> 00:16:03,320
kind of security for what they use email for. I never want to say that users don't need the

205
00:16:03,480 --> 00:16:07,900
ability to communicate in secret. They don't need the mathematical privacy guarantees,

206
00:16:08,720 --> 00:16:12,780
but they don't necessarily need that in their email. There are other options available until

207
00:16:13,100 --> 00:16:18,840
email provides that in a user-friendly way. Do you think email will provide that ever?

208
00:16:19,440 --> 00:16:25,619
I don't know. It's a great question. Will it ever? I don't know. I can tell you that it's a live

209
00:16:25,640 --> 00:16:33,120
topic of conversation among people who are doing serious standards work. We're pretty heavily

210
00:16:33,400 --> 00:16:38,420
invested in the Internet Engineering Task Force. We tend to show up at all the IETF general meetings

211
00:16:38,500 --> 00:16:43,260
and talk with other email providers and other technologies, but of course email and calendars

212
00:16:43,260 --> 00:16:50,519
and contacts are our big mainstays. There's some new work right now about improving signatures on

213
00:16:50,540 --> 00:16:55,980
email. Signatures are not encryption, but they give you something. The idea is giving you signatures

214
00:16:56,170 --> 00:17:03,800
on your email without making the email look weird, which is great, but it's almost the opposite of

215
00:17:04,079 --> 00:17:09,760
what about encrypted email. I think that the thing we need to figure out is the key exchange.

216
00:17:11,300 --> 00:17:19,179
If we can solve key exchange, solve. If we can have a realistic, widely trusted solution for key

217
00:17:19,199 --> 00:17:24,199
exchange, that's going to improve not just email, but many, many other technologies. And I think that

218
00:17:24,339 --> 00:17:27,720
that's a place that the industry needs to keep working. And there is work going on there.

219
00:17:29,100 --> 00:17:36,200
And then as for email, the main issue becomes, how do you communicate emails server to server

220
00:17:37,040 --> 00:17:40,660
in a way that they can communicate with one another and understand it's an email and know

221
00:17:40,800 --> 00:17:46,940
how to route it? And the two answers to that are you use SMTP and you send a message that is

222
00:17:48,100 --> 00:17:53,680
encrypted, but has enough information to be delivered. And the other answer is you replace

223
00:17:53,960 --> 00:17:59,680
SMTP. And they're both bad answers, because SMTP is not a great solution for end-to-end encrypted

224
00:17:59,880 --> 00:18:05,040
communication. It can be made better, but you need to make a lot of constraints on how it's currently

225
00:18:05,300 --> 00:18:10,540
permitted to work, on how much technical nonsense you want to get into. And replacing SMTP is a great

226
00:18:10,780 --> 00:18:14,399
solution, except for the part where you build a new system, get everybody to agree on it, and widely

227
00:18:14,420 --> 00:18:24,600
deploy it, which we haven't managed to do that for 50 years. Yeah. So if someone is a fast mail

228
00:18:24,800 --> 00:18:29,040
customer, but they want end to end encryption, what are their options? I assume they can still

229
00:18:29,180 --> 00:18:36,740
use PGP manually. Absolutely. Yeah. So they can use PGP, they can use S-MIME. Both of these are

230
00:18:37,220 --> 00:18:43,180
pretty tried and true systems. I shouldn't say recently, I can't recall how long it's been,

231
00:18:43,320 --> 00:18:48,020
but I was a really ride or die Mutt user for a long time.

232
00:18:48,660 --> 00:18:50,540
Mutt is, you're making a face.

233
00:18:50,880 --> 00:18:51,520
Yeah, I don't know.

234
00:18:52,299 --> 00:18:57,540
Mutt is, I would say, the last great console-based mail client.

235
00:18:58,660 --> 00:19:00,100
I love Mutt intensely.

236
00:19:00,640 --> 00:19:02,500
Maybe some other time you can ask me about it.

237
00:19:02,560 --> 00:19:04,800
I mean, I'll talk about it as much as you want, but I'm guessing you don't want to hear it.

238
00:19:05,080 --> 00:19:06,760
People probably don't know what it is.

239
00:19:07,520 --> 00:19:13,220
Well, when I first started using email, the clients of the day were mostly Pine and Elm.

240
00:19:13,540 --> 00:19:15,140
Both of these ran in your Unix terminal.

241
00:19:16,000 --> 00:19:17,820
You could use Outlook Express.

242
00:19:18,060 --> 00:19:20,020
I think Outlook Express was maybe brand new at the time.

243
00:19:20,100 --> 00:19:21,340
And there was a few other things.

244
00:19:22,080 --> 00:19:23,960
But most of us were using text.

245
00:19:25,240 --> 00:19:28,220
And Mutt was sort of the next generation email client.

246
00:19:28,340 --> 00:19:29,720
It ran in your terminal window.

247
00:19:30,420 --> 00:19:34,460
And it was extremely customizable and pretty programmable.

248
00:19:34,760 --> 00:19:37,960
It didn't have a programming language built into it, but it had a lot of automation points.

249
00:19:38,840 --> 00:19:41,080
And so everybody who used MUT used MUT a different way.

250
00:19:41,170 --> 00:19:45,120
And you could see 10 people at terminals working and not know they were all running the same thing.

251
00:19:45,200 --> 00:19:46,520
They're all running MUT, but you can't tell.

252
00:19:48,320 --> 00:19:50,280
And I used OpenPGP.

253
00:19:50,370 --> 00:19:51,920
I signed every message that I sent.

254
00:19:51,950 --> 00:19:54,060
I encrypted some of the messages I sent, and it was painless.

255
00:19:54,210 --> 00:19:55,120
It just worked.

256
00:19:55,150 --> 00:19:56,660
You hit E, and the message was encrypted.

257
00:19:57,440 --> 00:19:59,340
It was sent, and the other person would receive it.

258
00:19:59,500 --> 00:20:09,600
And if they were using a client that understood OpenPGP, they'd get a little lock or a little whatever sigil or, in my case, a little blue bar of text saying signature verified, here's the key ID.

259
00:20:10,260 --> 00:20:14,140
All that stuff works because one of our values is to be a good Internet citizen.

260
00:20:14,820 --> 00:20:23,580
Being a good Internet citizen, it means that we support the protocols that the Internet has agreed should work for email.

261
00:20:24,160 --> 00:20:27,920
We don't support every single email RFC, but I'll tell you what, we support a lot of them.

262
00:20:29,220 --> 00:20:35,660
And the goodness for OpenPGP is you don't actually have to support that much special stuff for OpenPGP to work through your server.

263
00:20:36,320 --> 00:20:37,500
Just the clients need to support it.

264
00:20:37,720 --> 00:20:38,420
Anybody can do that.

265
00:20:39,800 --> 00:20:41,600
That's probably the first thing I would suggest.

266
00:20:42,380 --> 00:20:48,600
But that said, I haven't personally used OpenPGP outside of Mutt almost ever.

267
00:20:49,420 --> 00:20:56,460
Other clients like MacMail and AlkExpress, they tend to have built-in support for S-MIME.

268
00:20:57,040 --> 00:21:03,480
And the kind of the big interesting difference between those two systems is that in OpenPGP,

269
00:21:04,340 --> 00:21:07,800
nobody is really in charge of the trust of your keys.

270
00:21:08,620 --> 00:21:10,780
So you make a key and you show it to someone.

271
00:21:10,960 --> 00:21:11,880
Maybe you show them your passport.

272
00:21:12,100 --> 00:21:14,180
You give them a blood sample and they're like, OK, I'm going to trust this.

273
00:21:14,800 --> 00:21:15,920
And then you can sign it.

274
00:21:15,960 --> 00:21:17,820
And anybody who trusts you will trust their key.

275
00:21:17,840 --> 00:21:19,340
And you get this big web of trust.

276
00:21:20,040 --> 00:21:24,280
And the web of trust is a really cool idea, sort of an early Internet, like we're all cowboys

277
00:21:24,380 --> 00:21:25,640
on the cyberspace kind of idea.

278
00:21:26,060 --> 00:21:31,900
The problem is it kind of sucks for scaling automatically and people just knowing how to use it.

279
00:21:32,320 --> 00:21:34,220
So you get a new key and like, do you trust this key?

280
00:21:34,500 --> 00:21:37,560
And, you know, everybody clicks yes on every dialogue that pops up.

281
00:21:37,760 --> 00:21:39,280
So it doesn't have a great trust model.

282
00:21:40,100 --> 00:21:41,040
Smime is the other way.

283
00:21:41,220 --> 00:21:52,080
Smime is like your web browser having a certification authority that signs it, which means if you want a key for signing your email, you've got to find someone who is willing to issue you that key.

284
00:21:52,160 --> 00:21:52,900
And then they sign it.

285
00:21:52,900 --> 00:21:54,340
But now everything's trusted automatically.

286
00:21:55,300 --> 00:21:57,600
Nobody's doing that for people's email addresses.

287
00:21:58,180 --> 00:22:00,680
There's no let's encrypt for S-MIME certificates.

288
00:22:01,190 --> 00:22:07,860
And one of the reasons is that most mail clients are kind of crummy when it comes to how do you install a certificate and how do you use it.

289
00:22:07,980 --> 00:22:08,920
It's a bootstrapping problem.

290
00:22:10,280 --> 00:22:13,560
So this is, again, I'm sorry, I keep digressing, but that's the way I am.

291
00:22:15,040 --> 00:22:22,120
When you ask about what do I suggest, yeah, I think that OpenPGP and S-MIME both have their place for adding this to email.

292
00:22:22,470 --> 00:22:23,580
But you face a lot of problems.

293
00:22:24,460 --> 00:22:34,360
And then the next option, you put it in the video, and I thought it was a little funny, but I think it's true, is you use email to establish how will you switch to a secure channel.

294
00:22:35,640 --> 00:22:37,600
Which is what you guys have on your website, too.

295
00:22:38,300 --> 00:22:41,980
Good. Well, good. I'm glad it's there. I didn't know it was there, but I'm glad we're consistent.

296
00:22:43,520 --> 00:22:53,020
Yeah, if email is not going to give you end-to-end encryption or it's going to give it to you through, like, snake oil of, well, here's a certificate that you can trust for absolutely no reason.

297
00:22:53,900 --> 00:22:55,580
Upgrade is something that you think you can trust.

298
00:22:56,360 --> 00:22:56,960
I use Signal.

299
00:22:57,370 --> 00:23:01,200
I don't worry too much about this kind of encryption person-to-person,

300
00:23:01,440 --> 00:23:04,700
but I find Signal to have been largely reliable for my needs.

301
00:23:04,870 --> 00:23:07,700
And, of course, there's a lot of other technology people use for that.

302
00:23:08,220 --> 00:23:08,460
Yeah.

303
00:23:08,970 --> 00:23:12,040
Yeah, no, I think the specific web page, if I remember correctly,

304
00:23:12,110 --> 00:23:15,500
it's been a couple months at this point since I was researching for that video,

305
00:23:15,590 --> 00:23:17,920
but I think it was like why we don't do end-to-end encryption,

306
00:23:18,100 --> 00:23:21,840
and it pretty much says one of the reasons is there's just better tools than email.

307
00:23:22,220 --> 00:23:22,600
Use Signal.

308
00:23:23,420 --> 00:23:23,500
Yeah.

309
00:23:24,320 --> 00:23:26,580
And I think everyone would agree with that.

310
00:23:26,580 --> 00:23:35,760
I think even Proton said that in the past before when people were criticizing some of the privacy and security differences between them and things that could be better.

311
00:23:35,820 --> 00:23:38,060
And they're like, well, we're making email better.

312
00:23:38,120 --> 00:23:40,920
We're not trying to beat signal through email.

313
00:23:43,000 --> 00:23:44,660
You talked a little bit about clients.

314
00:23:46,360 --> 00:23:49,460
Does FastMill do native clients or are you guys pretty much web first?

315
00:23:49,640 --> 00:23:52,700
I know you have the mobile clients, but do you have any native desktop clients?

316
00:23:52,760 --> 00:24:14,520
We don't publish a native desktop client. And when we publish a native desktop client someday, it's going to be like the mobile client. It's going to be you are getting a web app that has been encased in a native frame and wired up through that to the native facilities you want.

317
00:24:14,540 --> 00:24:19,720
right? Real desktop notifications, access through certain native API systems, you can't get over the

318
00:24:19,720 --> 00:24:27,280
web API. I think that'll be great. I think that a lot of services work that way now. I don't,

319
00:24:28,060 --> 00:24:33,960
I think that, I think that often people say, well, there's no native app, there's only the web,

320
00:24:34,480 --> 00:24:38,660
and it's kind of disappointing. And you're like, but I wanted a native app. And I've had the

321
00:24:38,740 --> 00:24:42,260
disappointment too. I don't think, I don't think FastMail is going to provide that experience.

322
00:24:42,860 --> 00:24:48,060
You know, I've said a couple of times, I think we shoot for like extremely highly polished interface.

323
00:24:48,340 --> 00:24:51,440
And I think it's going to feel really good.

324
00:24:51,620 --> 00:24:54,340
I don't I think that it's it's just going to work out to be.

325
00:24:54,600 --> 00:24:55,780
This is actually what I wanted.

326
00:24:56,000 --> 00:24:58,040
It's I basically wanted the fast mill interface.

327
00:24:58,700 --> 00:25:06,340
If we didn't do that, the amount of effort required to to say, how do we make a native application that is really native?

328
00:25:06,640 --> 00:25:12,560
Right. Built in the native toolkits, some portable interface that we can implement everywhere because we already have that into the Web.

329
00:25:13,360 --> 00:25:19,580
the amount of effort would be enormous. So I don't think that you're going to see a Windows 11

330
00:25:20,200 --> 00:25:24,620
native app written exactly for Windows 11. You know, someday you're going to be able to say,

331
00:25:24,640 --> 00:25:28,020
give me the FastMill Windows 11 app, and it's going to be a beautiful web interface,

332
00:25:29,000 --> 00:25:32,860
just like your mobile app. Nobody really complains about the mobile app being a web view,

333
00:25:33,680 --> 00:25:37,740
unless it's to say, why doesn't it do offline? And the good news is we do offline as of a couple

334
00:25:37,760 --> 00:25:44,680
weeks ago in production. So hopefully that'll go great. Yeah. And then when it comes to

335
00:25:44,860 --> 00:25:51,800
integrations with things like email aliasing and kind of the other features, the way that I was,

336
00:25:52,220 --> 00:25:59,300
again, it's really hard to review things because reviews are tough on my end because I want to ask

337
00:25:59,620 --> 00:26:04,840
questions for things to make sure they're accurate. But I also don't want to ask too many questions

338
00:26:04,860 --> 00:26:10,400
because then I'm injecting the company's opinion into a review.

339
00:26:11,460 --> 00:26:15,180
So my assessment, and I'm wondering if this is accurate, actually,

340
00:26:15,400 --> 00:26:19,860
my assessment in that comparison video is that you guys rely a bit more on integrations with third parties.

341
00:26:20,140 --> 00:26:24,880
You guys have your email aliasing that integrates with other services.

342
00:26:25,410 --> 00:26:27,360
I believe you integrate with 1Password.

343
00:26:28,440 --> 00:26:31,260
But you're not out there to build your own password manager either.

344
00:26:32,020 --> 00:26:33,080
Do you think that's fair?

345
00:26:33,720 --> 00:26:37,780
How do you kind of envision FastMail integrating with people's overall workflows?

346
00:26:38,320 --> 00:26:39,940
Yeah, I think that's a reasonable assessment.

347
00:26:40,100 --> 00:26:53,620
I think there's a fine line because when we provide points of integration, what we like to do is to say, how is this meant to work?

348
00:26:53,840 --> 00:26:57,160
What is the normal way to integrate with something like this?

349
00:26:58,020 --> 00:27:00,000
And so that's stuff like, well, we offer CalDAV.

350
00:27:00,420 --> 00:27:05,840
And if we want to do a calendar integration with a service, we will work with them.

351
00:27:06,000 --> 00:27:11,520
We worked with YouCanBookMe, for example, on integrating with their scheduling system.

352
00:27:12,280 --> 00:27:16,200
And it was largely, here's how our calendar implementation works.

353
00:27:16,490 --> 00:27:24,460
How do we figure out what either side of us is not doing as well as we could to the standard to make it work as effectively as we can?

354
00:27:24,530 --> 00:27:28,660
Because, of course, if we fix our implementation of the standards, it benefits everybody.

355
00:27:29,400 --> 00:27:35,320
If you can synchronize your full calendar set more effectively from FastMail, sure, it helps our partner, but then it helps every other partner.

356
00:27:36,100 --> 00:27:37,120
Sometimes that doesn't exist.

357
00:27:38,240 --> 00:27:46,040
Masked emails, the feature that we've developed that together with 1Password, we wanted a means where 1Password could say,

358
00:27:46,700 --> 00:27:47,820
I'm signing up for a new service.

359
00:27:48,180 --> 00:27:49,420
Don't just give me a new password.

360
00:27:49,560 --> 00:27:50,500
Give me a new username.

361
00:27:50,980 --> 00:27:57,940
And it would sort of immediately go to your FastMail account, make that username, and drop it into 1Password.

362
00:27:58,460 --> 00:28:01,960
One password sure as heck did not want to run an email service to offer this feature.

363
00:28:02,700 --> 00:28:06,120
And I think we've never had any interest in doing anything like a password manager.

364
00:28:07,000 --> 00:28:14,260
So it was obvious to do something and we needed an API. So we wrote one. And that's the sort of

365
00:28:14,400 --> 00:28:18,300
thing we would probably do in the future with other kinds of features we want to add.

366
00:28:19,780 --> 00:28:23,179
Fastmail is built on a protocol called JMAP, which we developed and it's now

367
00:28:24,600 --> 00:28:29,360
It's got an internet standard document, and it's meant to be very extensible for features like that.

368
00:28:29,520 --> 00:28:31,760
Masked emails, for example, are built into JMAP.

369
00:28:32,760 --> 00:28:36,320
But the difficulty is some features don't have anything like that.

370
00:28:36,580 --> 00:28:38,400
You want to talk about spreadsheets, right?

371
00:28:38,460 --> 00:28:40,460
Well, when are you going to have a spreadsheet in the file system?

372
00:28:40,520 --> 00:28:44,580
Well, there's no standard, and then I invoke the web spreadsheet editor.

373
00:28:45,200 --> 00:28:48,180
So you say, well, you could integrate with Microsoft Office.

374
00:28:48,340 --> 00:28:51,180
You could integrate with CollabSuite, all these other things.

375
00:28:51,260 --> 00:29:00,900
They're not standard. And you either lock yourself into somebody's proprietary API, which you then have to chase year after year as it as it changes, probably for good reason.

376
00:29:01,800 --> 00:29:09,080
Or you have to implement four or five different APIs to interact with systems that are all different, but in the same space.

377
00:29:09,900 --> 00:29:16,220
That's the kind of place we are looking at our Dropbox integration, where you want to integrate with Dropbox and Google Drive and Microsoft OneDrive.

378
00:29:16,880 --> 00:29:19,360
They all have different APIs, even though they're all file systems.

379
00:29:20,080 --> 00:29:25,060
So every time we look at integrating with a third-party system, the first question is, can we do it with open standards?

380
00:29:25,450 --> 00:29:27,040
Because that keeps the internet open.

381
00:29:27,630 --> 00:29:31,300
And if we can't do it, can we, first of all, we can't do it, is it worth doing?

382
00:29:32,080 --> 00:29:33,860
And can we do it by making a standard?

383
00:29:34,050 --> 00:29:36,540
Even if it's only a draft, we might publish later.

384
00:29:37,000 --> 00:29:43,460
And if we can't do that, how do we prevent it from being an ongoing maintenance cost more than it's worth?

385
00:29:43,760 --> 00:29:45,480
Because most people don't use most features.

386
00:29:46,580 --> 00:29:48,960
So every feature has to really pat a punch.

387
00:29:50,060 --> 00:29:55,600
Got it. Okay. And I want to ask more about JMAP. But before that, you've mentioned good internet

388
00:29:56,130 --> 00:30:02,500
citizens quite a bit. How do you feel that you guys are good citizens? I know you've already

389
00:30:02,640 --> 00:30:07,040
maybe touched on a few of those things, but if you could summarize what you think you guys do,

390
00:30:07,360 --> 00:30:10,940
that makes you good citizens. I'm so tempted to go see what we've written on the webpage,

391
00:30:11,190 --> 00:30:17,139
but I won't because it would be cheating. I think that there's a bunch of things. What I would love

392
00:30:17,160 --> 00:30:22,100
to hear, maybe I should do, is ask our staff what their various answers would be from the

393
00:30:22,140 --> 00:30:30,560
different departments. But I can tell you what I think. I think that for me, the internet is a

394
00:30:30,700 --> 00:30:37,660
really amazing place. It doesn't really have centralized governance. It doesn't really have

395
00:30:37,660 --> 00:30:42,260
a central authority for almost anything, and certainly not the things that we use most directly.

396
00:30:42,960 --> 00:30:48,560
And that lets the internet grow and evolve and invite new people into it really freely.

397
00:30:49,680 --> 00:30:56,940
And the downside of that is that, A, it means it's sort of ripe for takeover by anybody who

398
00:30:57,020 --> 00:31:03,140
can overwhelm the value of its open standards, which is unfortunately easy because open standards

399
00:31:03,310 --> 00:31:07,000
tend to be slow and private companies can move quickly.

400
00:31:08,040 --> 00:31:16,880
And it also means that without a central moderating authority, on one hand, nobody is there to tell you that you are too weird to be allowed to talk in public.

401
00:31:17,780 --> 00:31:23,140
But also no one is really there to tell you that you are too hateful to be allowed to talk in public.

402
00:31:24,000 --> 00:31:44,520
So everything in my mind about being a good internet citizen is about understanding the systems that you're building socially and technically and how they moderate people's life experience, whether that's communicating with other people, whether it's communicating with strangers, whether it's how they live their life or their multiple lives.

403
00:31:44,720 --> 00:31:50,120
They have several different personalities, several different identities or contexts that they experience life in.

404
00:31:50,800 --> 00:31:58,300
Giving people the tools to manage their life or the parts of their lives in ways that empower

405
00:31:58,400 --> 00:32:02,540
them and that let them separate the concerns of their life is really important.

406
00:32:03,020 --> 00:32:06,680
And building a system where those tools can be effective, right?

407
00:32:06,760 --> 00:32:11,180
Not where there's one central authority who knows all your secrets, but where you can isolate

408
00:32:11,200 --> 00:32:16,160
the parts of your life and have them work together in a federated way where you might as well

409
00:32:16,160 --> 00:32:19,060
be two strangers communicating with yourself if you want to be.

410
00:32:19,860 --> 00:32:24,240
To me, that's how we make the Internet a good place.

411
00:32:24,900 --> 00:32:26,900
And the other part of it is not being a dick.

412
00:32:27,440 --> 00:32:27,940
Don't be an asshole.

413
00:32:28,300 --> 00:32:29,820
Like, that's really, really important.

414
00:32:30,660 --> 00:32:34,440
And that's something that it's hard to do on a corporate level.

415
00:32:34,600 --> 00:32:39,100
Of course, we try not to be terrible, but that's a personal responsibility.

416
00:32:39,960 --> 00:32:42,120
Yeah, so I think it's really easy to hear that.

417
00:32:42,380 --> 00:32:48,920
And I think a lot of people on the Internet have become disillusioned with what bad things look like.

418
00:32:49,020 --> 00:32:59,460
And we can look back in history to even compare because Microsoft in a day was being held legally liable for doing things that look like nothing nowadays.

419
00:32:59,860 --> 00:33:03,320
Right. Like pairing their own browser with an operating system.

420
00:33:03,940 --> 00:33:08,240
Right. That was that was seen as horrendous just, what, 30 years ago now.

421
00:33:10,080 --> 00:33:13,700
But nowadays it's like they do all this crazy stuff. Everyone gets away with it.

422
00:33:13,820 --> 00:33:15,820
So what does a bad citizen look like?

423
00:33:16,040 --> 00:33:19,800
What is, if someone's listening to this for the first time, and of course, we don't need

424
00:33:19,820 --> 00:33:26,300
to like single out anybody here, but how do you kind of, if someone doesn't really pay

425
00:33:26,500 --> 00:33:30,320
attention to tech, tech for them is just, you know, they just plug in something in their

426
00:33:30,440 --> 00:33:31,400
GPS in their car.

427
00:33:31,460 --> 00:33:32,900
It's how they get from point A to point B.

428
00:33:33,080 --> 00:33:34,100
They're not thinking about it.

429
00:33:34,820 --> 00:33:38,460
How would they think a bit more critically about what a bad citizen looks like if they

430
00:33:38,540 --> 00:33:40,840
don't really notice anything wrong in their day-to-day life?

431
00:33:41,560 --> 00:33:41,720
Yeah.

432
00:33:42,200 --> 00:33:49,460
Well, first I will plug our completed podcast, off the air podcast that we did for a couple of seasons called Digital Citizen.

433
00:33:49,860 --> 00:33:55,420
And it is largely about this question of what does it look like to be a responsible Internet citizen.

434
00:33:55,660 --> 00:34:01,440
But I'm not just I'll keep going because I'm not going to ask everybody to hit pause and go listen to, you know, 26 episodes or whatever.

435
00:34:03,520 --> 00:34:09,659
I think that one of the most important things for people to do is to pay attention.

436
00:34:10,679 --> 00:34:14,320
And that's easy advice to give.

437
00:34:16,880 --> 00:34:23,879
But early on in this conversation, I said that a big selector for people who might use

438
00:34:24,020 --> 00:34:27,100
Fastmail is people who even think about what email would they use.

439
00:34:28,139 --> 00:34:32,020
And I was talking then sort of in a product marketing kind of sense, right?

440
00:34:32,480 --> 00:34:36,679
If you stop and think about what do you want out of your email, you know, is it fast?

441
00:34:36,879 --> 00:34:37,419
Is it private?

442
00:34:37,480 --> 00:34:38,000
Is it secret?

443
00:34:38,260 --> 00:34:38,340
Whatever.

444
00:34:40,320 --> 00:34:49,320
But on the other hand, you should be thinking about those things not just for your product satisfaction, but for the way it impacts your life and the way you experience the Internet.

445
00:34:50,060 --> 00:34:50,940
And, you know, let's get real.

446
00:34:50,980 --> 00:34:52,820
The Internet is a part of the fabric of everyday life.

447
00:34:52,899 --> 00:34:55,879
So the way you experience the Internet is the same way that you experience Broad Street.

448
00:34:56,440 --> 00:34:57,500
It's the same thing.

449
00:34:58,140 --> 00:35:10,140
And if you want to understand the impact that the tools you use, that the society that you're part of, that the ecosystems you're using impact you, you have to stop and think about them all.

450
00:35:11,300 --> 00:35:20,640
And it's not necessarily an easy or a super reasonable thing to be asked to do, but it's also, I think, sort of the only way to do it.

451
00:35:20,980 --> 00:35:25,720
You know, at best, you could find one really trusted source and outsource all your decisions to that.

452
00:35:25,780 --> 00:35:27,580
But like, first off, you won't find them.

453
00:35:27,780 --> 00:35:31,980
And secondly, once they become that influential, let's see how long they remain super trustworthy.

454
00:35:33,200 --> 00:35:36,920
So I think the thing to think about is where are you spending your time?

455
00:35:37,360 --> 00:35:38,720
Where are you spending your talents?

456
00:35:39,100 --> 00:35:40,520
Where are you spending your cash?

457
00:35:41,720 --> 00:35:46,620
And are you putting it into places that put aside are good for the whole world?

458
00:35:46,760 --> 00:35:48,640
Although I hope people think about that.

459
00:35:48,980 --> 00:35:50,680
Are they good for you, right?

460
00:35:50,780 --> 00:35:56,060
if you're spending five hours a day, you know, doom scrolling on one of the infinite scrolling

461
00:35:56,280 --> 00:36:01,160
apps, is that good for you? Are you thinking about it? How does it affect your friendships

462
00:36:01,550 --> 00:36:07,000
and so on? I guess it's a, it's always feels like a disappointing answer because

463
00:36:08,800 --> 00:36:12,300
I'll digress one little bit more than I'll stop. Many years ago, I lost a lot of weight

464
00:36:13,200 --> 00:36:17,539
and my coworkers, I wanted to buy new clothes. So I came in now I looked like I lost the weight

465
00:36:17,560 --> 00:36:23,200
because my clothes fit. And a bunch of coworkers that week asked me, how'd you do it? And I said,

466
00:36:24,060 --> 00:36:29,320
exercise, and I ate less. And every time I said that, they would say, oh, they all wanted me to

467
00:36:29,420 --> 00:36:36,360
say, I just ate grapefruit every morning. Cold bath plunges, whatever the new trend is.

468
00:36:36,630 --> 00:36:40,740
You just do one thing and it's going to, you know, one quick trick. There's no one quick trick

469
00:36:41,480 --> 00:36:46,059
to have a better internet life. You have to pay attention. You have to think about it. And I would

470
00:36:46,080 --> 00:36:51,900
suggest that the payoff is worth it. But I'm the guy who chose to work for 20 years at a company

471
00:36:52,100 --> 00:36:55,800
founded on the idea that the payoff of being a good internet citizen is worth it. So you can decide

472
00:36:55,940 --> 00:36:59,240
whether that makes me more or less credible in this case. Yeah, and it's interesting. I mean,

473
00:36:59,240 --> 00:37:06,160
it ties in. It's nice to see some things get into the public spotlight. The whole removal of Google's

474
00:37:06,280 --> 00:37:12,460
don't be evil statement ties into this. And I know they just say, yeah, it might be a legal thing.

475
00:37:12,700 --> 00:37:14,840
we can't like legally be held to that, whatever they say.

476
00:37:15,060 --> 00:37:18,760
But the fact that was removed, I think it does make people realize like we've removed

477
00:37:19,980 --> 00:37:23,800
this core identity of trying to be the best people on the internet.

478
00:37:23,800 --> 00:37:29,480
And I know they still claim to be, and that's something that they try to keep that image there.

479
00:37:29,740 --> 00:37:38,340
But I actually like don't be evil as just an overall motto to stick to for most companies.

480
00:37:39,740 --> 00:37:39,840
Yeah.

481
00:37:39,960 --> 00:37:41,300
And for every person, right?

482
00:37:41,380 --> 00:37:49,260
And if every person was able to seriously keep that as their personal motto, you'd like to think that the companies would naturally follow.

483
00:37:49,700 --> 00:37:51,320
But it's hard.

484
00:37:51,320 --> 00:37:53,680
And also people disagree on where the boundary is.

485
00:37:54,560 --> 00:37:54,760
Yeah.

486
00:37:57,180 --> 00:38:01,520
I want to go into a few more technical pieces about FastMail now.

487
00:38:01,610 --> 00:38:04,560
And so this is going to include things like JMAP.

488
00:38:05,660 --> 00:38:07,040
What exactly is open source?

489
00:38:07,190 --> 00:38:10,940
Because I didn't think you guys were open source, but it sounds like you might have some aspects that are open source.

490
00:38:11,140 --> 00:38:12,740
So I want to get into the nitty gritty there.

491
00:38:13,240 --> 00:38:19,160
I want to get into jurisdiction, phone number registration, which I know is something I mentioned,

492
00:38:19,320 --> 00:38:21,280
and I was hoping to ask a bit more about that.

493
00:38:21,620 --> 00:38:25,140
And then kind of we'll start with those kind of things.

494
00:38:25,380 --> 00:38:27,080
So I want to start with JMAP.

495
00:38:28,140 --> 00:38:33,020
Do you want to explain for anyone who doesn't know how emails work, what regular technology

496
00:38:33,220 --> 00:38:36,320
looks like, and then what JMAP is and why you have your own protocol?

497
00:38:37,040 --> 00:38:39,180
Yes, I would like nothing more than to talk about JMAP.

498
00:38:40,720 --> 00:38:50,260
So the two most common protocols people use for their email these days are SMTP and IMAP.

499
00:38:50,680 --> 00:38:51,680
There's a bunch of other protocols.

500
00:38:51,960 --> 00:38:53,320
I'm going to talk about those two really briefly.

501
00:38:53,860 --> 00:39:00,060
First thing I'll say is SMTP comes from the 70s and IMAP comes, I think, from the 89.

502
00:39:00,520 --> 00:39:02,780
It's from like the late 80s, maybe 1990.

503
00:39:03,640 --> 00:39:04,240
But they're old.

504
00:39:04,460 --> 00:39:05,000
They're old protocols.

505
00:39:05,780 --> 00:39:09,800
And there's nothing wrong with the protocol being old, but it tends to mean it's, you know,

506
00:39:09,860 --> 00:39:14,800
it's like reading, I'll be really complimentary and say it's like reading Shakespeare. Maybe it is

507
00:39:15,060 --> 00:39:17,920
wonderful and beautiful, but you got to put in some effort to understand how the thing works.

508
00:39:17,950 --> 00:39:21,220
And you got to have this whole mental model of like, you know, what exactly does that little

509
00:39:21,430 --> 00:39:27,020
accent mark mean I'm supposed to say this? I don't think it's actually like Shakespeare. I think that

510
00:39:27,160 --> 00:39:33,600
SMTP and IMAP are both kind of dreadful. They're built on a lot of assumptions about the way computers

511
00:39:34,100 --> 00:39:39,299
work, the way that people are going to use their email. And then what we tend to do over time

512
00:39:39,320 --> 00:39:42,840
is add complications to these systems

513
00:39:43,050 --> 00:39:46,900
to cope with the situation of our contemporary problems.

514
00:39:48,160 --> 00:39:49,840
SMTP is used for two things.

515
00:39:50,060 --> 00:39:52,300
It's used for getting email from one server to another.

516
00:39:52,800 --> 00:39:54,220
So if I send you an email,

517
00:39:54,530 --> 00:39:56,700
at some point it's going to leave a FastMail server

518
00:39:56,880 --> 00:39:57,820
and go to a Proton server.

519
00:39:58,960 --> 00:40:00,680
And it's also used usually

520
00:40:01,210 --> 00:40:04,700
for getting email from my computer to my server.

521
00:40:05,480 --> 00:40:07,180
We call that SMTP submission.

522
00:40:07,780 --> 00:40:10,400
So I hit send, it goes through SMTP to my server,

523
00:40:10,570 --> 00:40:11,880
it goes SMTP to your server,

524
00:40:12,050 --> 00:40:13,420
and now it's waiting there for you to read.

525
00:40:14,059 --> 00:40:16,320
Now, Proton's a little weird,

526
00:40:16,470 --> 00:40:18,620
so we're not going to talk about Proton as your end of the example.

527
00:40:18,720 --> 00:40:20,260
Let's say I've convinced you to move to FastMail.

528
00:40:20,450 --> 00:40:22,360
So now you're going to read your mail with IMAP.

529
00:40:23,320 --> 00:40:24,280
IMAP is the other part.

530
00:40:24,290 --> 00:40:26,260
It's the Internet Message Access Protocol.

531
00:40:26,580 --> 00:40:29,560
The idea behind IMAP is your mail is on a server

532
00:40:29,760 --> 00:40:31,360
and you want to access it over the Internet.

533
00:40:31,650 --> 00:40:34,460
So you connect over IMAP and you say things like,

534
00:40:34,490 --> 00:40:36,680
hey, open up this folder, tell me what's new,

535
00:40:36,900 --> 00:40:42,380
get that message. I want to read it. And it's all designed so that all the mail can then be stored

536
00:40:42,700 --> 00:40:48,540
on your computer. So you've connected to IMAP. All your mail is downloaded with IMAP to your computer

537
00:40:48,800 --> 00:40:53,100
where it can be kept in sync with the server efficiently. And then you can read it even if

538
00:40:53,100 --> 00:40:59,340
you go through the Lincoln Tunnel. And all that's great. And the problem statement is still a real

539
00:40:59,580 --> 00:41:04,039
problem. How do you get your mail efficiently, update it, communicate offline? It's just that

540
00:41:04,060 --> 00:41:08,780
The solution for doing it is built for the problems of the 90s with a bunch of bolt-ons.

541
00:41:09,550 --> 00:41:15,740
And also, you have to understand, if you're programming in it, you have to understand how to,

542
00:41:17,060 --> 00:41:19,940
you have to understand all the concepts built into it, which aren't concepts found anywhere else.

543
00:41:20,660 --> 00:41:26,180
And last point, if you are sitting at your computer and you are connected to your IMAP server,

544
00:41:26,420 --> 00:41:31,900
waiting for new mail to come in, you will keep at least one and possibly more than one open connection

545
00:41:32,330 --> 00:41:33,180
to your IMAP server.

546
00:41:34,040 --> 00:41:38,500
This is actually a really interesting point, because open connections are not free.

547
00:41:39,300 --> 00:41:45,120
Every open connection you keep to your server is work being done by both your computer and the server.

548
00:41:45,900 --> 00:41:47,560
That server is probably serving a lot of people.

549
00:41:47,860 --> 00:41:52,540
If you imagine it's a Google IMAP server, it's got a squintillion people connecting to it,

550
00:41:52,940 --> 00:41:57,500
doing huge amounts of work just to keep connections open and stay when new mail came in.

551
00:41:58,220 --> 00:42:01,700
It's designed for a time when these weren't the real problems,

552
00:42:01,820 --> 00:42:06,560
And if you wanted to solve the problem of tell me about new mail, you solved it by adding something weird to IMAP.

553
00:42:07,560 --> 00:42:14,480
So JMAP sort of came about about 10 years ago when we said, what if we just built something new?

554
00:42:14,860 --> 00:42:19,420
What if we built a new protocol designed for today's problems, but backwards compatible?

555
00:42:20,280 --> 00:42:24,920
And one of the authors of IMAP said to us something like, you're dreaming if you think it's ever going to work.

556
00:42:25,780 --> 00:42:29,000
But we decided to continue dreaming and we built this thing.

557
00:42:29,680 --> 00:42:30,900
And the thing we built is JMAP.

558
00:42:31,080 --> 00:42:33,420
It only replaces the IMAP part of this equation.

559
00:42:33,920 --> 00:42:36,560
It doesn't replace server to server.

560
00:42:37,200 --> 00:42:40,800
It does replace sending your mail in from your laptop to the computer.

561
00:42:41,720 --> 00:42:43,700
And there's two important things to talk about.

562
00:42:44,600 --> 00:42:47,800
One is it's just HTTP and JSON.

563
00:42:48,880 --> 00:42:57,360
And if you ever go look at email, email submission, calendars, contacts, which DMAP also handles,

564
00:42:57,860 --> 00:43:00,680
all a bunch of weird protocols like DAV.

565
00:43:01,500 --> 00:43:03,220
It's all a bunch of weird data structures

566
00:43:03,520 --> 00:43:05,020
like vCard and iCalendar.

567
00:43:05,480 --> 00:43:06,940
I mean, I know them pretty well these days,

568
00:43:07,030 --> 00:43:08,420
but they're just a nightmare.

569
00:43:09,380 --> 00:43:10,420
And if you were going to say,

570
00:43:10,420 --> 00:43:11,820
I want to write a couple little tools,

571
00:43:11,910 --> 00:43:15,640
a couple little toys for me to use for my personal data,

572
00:43:15,690 --> 00:43:17,140
because remember, your data belongs to you

573
00:43:17,380 --> 00:43:19,400
and the server is just there to be a steward of your data.

574
00:43:19,740 --> 00:43:22,140
You have to go learn these crazy ancient protocols.

575
00:43:23,560 --> 00:43:26,760
Every programmer these days knows HTTP and Json.

576
00:43:26,840 --> 00:43:32,960
excuse me it's it's how the internet works these days so jmap gives you a way to say i want all

577
00:43:32,990 --> 00:43:36,220
these benefits i want to synchronize my mail offline i want to finish efficient communication

578
00:43:36,500 --> 00:43:41,200
back with the server but i want to do it in a simple way that i can understand and if i need

579
00:43:41,440 --> 00:43:46,260
real-time communication like a real-time update from the server we have ways for doing that now

580
00:43:46,360 --> 00:43:50,179
it's how you get a push notification to your phone right it's a it's a web push those things don't

581
00:43:50,200 --> 00:43:53,620
don't require open network connections,

582
00:43:54,200 --> 00:43:54,980
which means they eliminate

583
00:43:56,320 --> 00:43:58,380
surprisingly large amount of resource usage

584
00:43:58,560 --> 00:43:59,160
in data centers

585
00:44:00,000 --> 00:44:01,900
and make your services a lot more reliable.

586
00:44:02,000 --> 00:44:03,360
They also have a lot of benefits for authentication.

587
00:44:03,580 --> 00:44:04,940
And I'll stop going on about that,

588
00:44:04,980 --> 00:44:06,020
but I really could.

589
00:44:07,060 --> 00:44:08,380
It's really kind of shocking

590
00:44:09,100 --> 00:44:10,940
about how much better,

591
00:44:11,260 --> 00:44:14,140
both in terms of simplicity

592
00:44:14,980 --> 00:44:15,660
and leverage,

593
00:44:16,220 --> 00:44:16,740
JMAP is.

594
00:44:17,060 --> 00:44:17,800
Also, as a programmer,

595
00:44:17,940 --> 00:44:18,760
it's really nice.

596
00:44:18,940 --> 00:44:20,080
It's really nice to work with.

597
00:44:20,080 --> 00:44:21,240
I feel very good about using it.

598
00:44:21,400 --> 00:44:25,080
So to summarize this, so there are essentially two communications.

599
00:44:26,440 --> 00:44:27,220
There's a communication.

600
00:44:27,370 --> 00:44:32,460
If I'm sending an email, there's communication from me to the server of the service that I use.

601
00:44:32,550 --> 00:44:34,560
And then there is server to server.

602
00:44:35,380 --> 00:44:39,780
If the other person is using a different email provider, then it has to go there.

603
00:44:40,110 --> 00:44:47,320
You guys don't modify that second half of the equation because that would probably break the interoperability between you and other people.

604
00:44:47,420 --> 00:44:53,260
unless you found a way to translate protocols between each other or something goofy that I don't understand.

605
00:44:53,860 --> 00:44:54,700
Yeah, we just wouldn't do it.

606
00:44:55,320 --> 00:44:55,420
Yeah.

607
00:44:55,830 --> 00:45:00,300
So you guys are only able to do essentially what's within your own ecosystem for your own customers.

608
00:45:01,800 --> 00:45:03,100
That's right, but yes.

609
00:45:03,410 --> 00:45:04,160
So I'll start with yes.

610
00:45:04,650 --> 00:45:09,000
But the important thing to note is when you say within our ecosystem,

611
00:45:09,280 --> 00:45:12,300
you're correct that we're not changing the way server-to-server works.

612
00:45:13,340 --> 00:45:17,200
But JMAP is a set of Internet standard documents.

613
00:45:17,580 --> 00:45:21,020
So you can go look at RFC 8620, RFC 8621.

614
00:45:21,760 --> 00:45:25,740
Those define the core JMAP specification and JMAP for email.

615
00:45:26,760 --> 00:45:27,940
You can find those documents.

616
00:45:28,160 --> 00:45:30,120
They're published by the Internet Engineering Task Force.

617
00:45:30,280 --> 00:45:33,360
You can download them and you can write software that implements those.

618
00:45:33,960 --> 00:45:36,660
And then you can point that software at Fastmail and it will work.

619
00:45:37,420 --> 00:45:37,560
Great.

620
00:45:37,800 --> 00:45:44,520
And the dream, the further dream, is that more people will build JMAP clients.

621
00:45:44,740 --> 00:45:45,420
And there are some.

622
00:45:45,480 --> 00:45:52,180
You can go on the iOS app store and the Android app store and find some JMAP clients that are not our web UI.

623
00:45:52,350 --> 00:45:58,280
So if you really want that native client that's built in Swift, because that's what you want to run on your iOS phone, you can get one.

624
00:45:59,120 --> 00:46:06,420
And there are other people who have implemented JMAP servers other than the JMAP server that we use.

625
00:46:07,000 --> 00:46:16,140
And so you could take a JMAP client someone else has written and a JMAP server someone else has written and have your own ecosystem still using JMAP.

626
00:46:16,580 --> 00:46:19,440
So that's the big difference in being a walled garden.

627
00:46:19,940 --> 00:46:23,660
We made plans for how to make gardens that would all connect up beautifully.

628
00:46:23,980 --> 00:46:26,220
We published those, and so far it's going pretty well.

629
00:46:27,080 --> 00:46:30,860
Has any other major email provider integrated JMAP?

630
00:46:33,120 --> 00:46:36,260
Well, Thunderbird says that their new product is going to.

631
00:46:36,560 --> 00:46:37,780
That was released pretty recently.

632
00:46:40,500 --> 00:46:43,840
There's a few people who have been doing some larger scale work.

633
00:46:44,480 --> 00:46:47,200
I think Thunderbird's probably the biggest who's made a really clear announcement.

634
00:46:48,020 --> 00:46:50,260
We've spoken with a number of pretty large providers.

635
00:46:50,720 --> 00:47:01,580
And in a lot of ways, the short version of the mega large email providers is they all see the benefit of doing it and are keen to do it.

636
00:47:01,660 --> 00:47:02,940
But there's a chicken and egg problem.

637
00:47:03,700 --> 00:47:15,800
If the Apple iOS client, the number one mail client in the world, does not support JMAP, then what does Google save by implementing it?

638
00:47:16,680 --> 00:47:29,480
On the other hand, if the top four mail clients supported JMAP, all those active server connections to Gmail would have value to Google.

639
00:47:29,920 --> 00:47:31,800
And value to Google here, I mean dollar signs.

640
00:47:32,120 --> 00:47:34,400
It would reduce the amount of CPU.

641
00:47:34,620 --> 00:47:36,320
It would reduce the amount of bandwidth used.

642
00:47:36,400 --> 00:47:37,860
It would have significant changes.

643
00:47:38,120 --> 00:47:43,980
So there are economic forces at play in very complicated ways on the really large things.

644
00:47:45,020 --> 00:47:50,560
I think for me, it's not a big economic scale, but for me, it's always about delighting the developers.

645
00:47:51,460 --> 00:47:53,160
JMAP is a delight to work with.

646
00:47:53,280 --> 00:48:00,340
And so we see people saying, I want to build a really nice JMAP client or a new JMAP server and building these things,

647
00:48:00,780 --> 00:48:04,440
which means we're building up expectations and experience around the system working,

648
00:48:04,580 --> 00:48:06,100
which I think is going to have a long-term effect.

649
00:48:06,500 --> 00:48:09,920
But I would love to see at some point Apple and Google coming out and saying,

650
00:48:09,940 --> 00:48:11,740
we've decided we're both rolling out JMAP next year.

651
00:48:12,140 --> 00:48:12,660
That'd be terrific.

652
00:48:13,040 --> 00:48:15,040
It sounds like it'd be nothing but an improvement.

653
00:48:15,140 --> 00:48:16,620
And I guess that's my next question.

654
00:48:16,760 --> 00:48:20,540
So for a regular person listening to this who's maybe not a tech nerd,

655
00:48:21,320 --> 00:48:25,680
they just log into their email, they just care about the realistic benefits to them.

656
00:48:26,600 --> 00:48:28,140
How does JMAP change their day-to-day life?

657
00:48:28,200 --> 00:48:28,780
Is it faster?

658
00:48:28,980 --> 00:48:31,220
Does it offer any security or privacy benefits?

659
00:48:31,980 --> 00:48:33,540
What can they expect?

660
00:48:34,780 --> 00:48:36,240
- So it is faster.

661
00:48:37,700 --> 00:48:40,840
It's faster, it synchronizes more quickly and more reliably.

662
00:48:42,280 --> 00:48:44,560
It makes a lot of these operations simpler

663
00:48:44,960 --> 00:48:46,740
for both client and servers to implement.

664
00:48:47,420 --> 00:48:50,180
So one of the things that you don't think about a lot

665
00:48:50,260 --> 00:48:52,840
is places where, we started with this standard in 1990

666
00:48:53,200 --> 00:48:56,040
and now we've bolted on a bunch of extensions.

667
00:48:56,900 --> 00:49:02,420
Sometimes the extensions aren't really perfectly designed to work together and they'll allow weird things to happen.

668
00:49:02,810 --> 00:49:11,860
Or in fact, putting aside extensions, IMAP itself has the means to say, I want a message to be in one folder or another.

669
00:49:12,600 --> 00:49:16,620
But the original IMAP does not have a way to say move this email from folder one to folder two.

670
00:49:17,300 --> 00:49:22,440
Instead, you copy it from folder one to folder two and then you delete it from folder one.

671
00:49:23,180 --> 00:49:28,060
I can almost see this because in like the Apple mail client, it says moving.

672
00:49:29,140 --> 00:49:33,780
Like I think it almost describes that in a way because it says, oh, moving and then it deletes.

673
00:49:34,060 --> 00:49:37,280
And it's like, oh, it seems like it's multi-step just to do things.

674
00:49:37,280 --> 00:49:37,840
It can be.

675
00:49:38,290 --> 00:49:38,980
Now there's extensions.

676
00:49:39,200 --> 00:49:40,700
There's extensions for moving atomically.

677
00:49:41,080 --> 00:49:42,020
But there's two problems here.

678
00:49:42,160 --> 00:49:44,280
One is what if your mailbox is full?

679
00:49:44,380 --> 00:49:45,180
You've used all your quota.

680
00:49:45,360 --> 00:49:47,660
Well, you can't copy a message when you're out of space.

681
00:49:48,140 --> 00:49:49,200
So you can't move that message.

682
00:49:49,660 --> 00:49:54,260
And also, what if your connection dies after you have copied it, but before you have deleted it?

683
00:49:55,060 --> 00:49:58,800
These are not big things, but imagine these little things multiplied all throughout the system.

684
00:49:59,640 --> 00:50:03,480
Those kind of problems have largely been carved away in JMAP.

685
00:50:04,260 --> 00:50:06,680
These are issues that we don't want people to see.

686
00:50:07,520 --> 00:50:10,980
What it ends up feeling like is the system just works better.

687
00:50:11,580 --> 00:50:18,560
And we can make a list of the little things that have been improved, but the short version is it just feels rock solid.

688
00:50:18,960 --> 00:50:31,640
Because even if IMAP has extensions for making an atomic move happen, if you have to support every IMAP server out there, the first thing you do is implement copy and delete.

689
00:50:32,400 --> 00:50:39,020
And after you've done that, maybe you don't go back and implement move because the feature seems to work.

690
00:50:39,380 --> 00:50:41,140
Sure, it has a couple edge cases, but it works.

691
00:50:43,260 --> 00:50:45,540
The other question is about security.

692
00:50:45,560 --> 00:50:48,860
there's a number of security cases and some of them are kind of obscure but i'll tell you one

693
00:50:48,900 --> 00:50:54,320
it's not obscure in imap i said earlier if you want to stay connected and you want to listen for

694
00:50:54,320 --> 00:50:59,260
new mail coming in what actually happens is your imap client has connected to the server and you say

695
00:50:59,520 --> 00:51:03,720
i'm going to idle and then it just sits there and everyone's while the server's like i'm still here

696
00:51:03,840 --> 00:51:07,720
and the client's like i'm still here but if there's a new message you can say hey you got a message

697
00:51:08,140 --> 00:51:13,940
and then you fetch the message and you read it and everything is good um if you are on a mobile

698
00:51:14,000 --> 00:51:18,560
handset, right? Your Android device, your iOS device, they don't let you keep an open IMAP

699
00:51:18,760 --> 00:51:23,120
connection. It's antithetical to the way they work, right? They want to be able to kill off

700
00:51:23,120 --> 00:51:27,660
your application whenever they need more resources. So keeping a network connection all the time,

701
00:51:27,940 --> 00:51:37,540
that's out. So what happens instead is some mail clients will, when you sign up, they will take your

702
00:51:37,640 --> 00:51:42,619
OAuth token or they'll take your password and they'll store it securely. I put quotes on, that's

703
00:51:42,640 --> 00:51:49,760
not fair. They store it somehow, hopefully securely in the cloud. And then they have a client that sits

704
00:51:50,120 --> 00:51:54,940
idling on your mailbox in the cloud with your password. And when it sees there's a new message,

705
00:51:55,040 --> 00:51:58,440
they convert that into a push that goes to your phone and tells your phone to get it.

706
00:51:59,860 --> 00:52:05,720
It is totally possible to do that in a way that is very low knowledge, not really zero knowledge,

707
00:52:07,320 --> 00:52:12,040
but it's not zero knowledge. And it's tricky. And it's a lot more effort than saying, yeah,

708
00:52:12,120 --> 00:52:14,640
we just have an IMAP client and sure it could read all your mail, but we won't.

709
00:52:16,460 --> 00:52:19,480
With JMAP, we use standard web push.

710
00:52:19,660 --> 00:52:20,940
Web push is another open standard.

711
00:52:21,010 --> 00:52:22,300
I think it's RFC 8030.

712
00:52:22,760 --> 00:52:23,400
It's somewhere around there.

713
00:52:24,479 --> 00:52:30,420
And you can just say, I want pushes to come to this web push mailbox.

714
00:52:31,080 --> 00:52:33,800
And the server, when it has new mail, will post.

715
00:52:34,260 --> 00:52:36,320
It will make a post to your endpoint and say, there's new mail.

716
00:52:37,100 --> 00:52:37,760
Get it if you want.

717
00:52:38,200 --> 00:52:38,920
Don't if you don't want to.

718
00:52:39,170 --> 00:52:39,660
But that's it.

719
00:52:39,670 --> 00:52:41,820
The connection lasts for, you know, 10 milliseconds.

720
00:52:43,020 --> 00:52:46,520
And with that, your device doesn't need to give extra credentials to anybody, which is

721
00:52:46,520 --> 00:52:48,360
a significant security improvement.

722
00:52:49,700 --> 00:52:55,940
Is this why, and I know this is totally to the wrong audience, I don't even know how many

723
00:52:56,100 --> 00:52:57,980
Gmail users we have who are listening to this.

724
00:52:58,340 --> 00:53:03,600
I'm hoping that the stat is reversed, where maybe 20% of people listening to this use Gmail,

725
00:53:03,900 --> 00:53:04,660
80% don't.

726
00:53:07,440 --> 00:53:12,140
If you try to log into your Google account on your iOS device, like in the settings, and

727
00:53:12,280 --> 00:53:18,840
try to use Gmail inside of Apple Mail, to this day, in 2025, there is no push notification

728
00:53:19,160 --> 00:53:19,320
support.

729
00:53:19,630 --> 00:53:24,300
You don't get push notifications, and that's because I think Google uses IMAP, and Google

730
00:53:24,440 --> 00:53:27,400
doesn't want to host IMAP push notifications for Apple Mail.

731
00:53:27,480 --> 00:53:28,740
They want you to use their native app.

732
00:53:29,380 --> 00:53:32,340
Yeah, I can't speak with a position of authority, but that's my assumption.

733
00:53:33,200 --> 00:53:34,420
Is that because I don't want to...

734
00:53:34,780 --> 00:53:35,700
It's a resource thing?

735
00:53:36,180 --> 00:53:36,760
That's a guess.

736
00:53:36,840 --> 00:53:44,840
I can make a bunch of speculation. So one is, gosh, I'll get technical and you can decide if

737
00:53:44,840 --> 00:53:50,800
you want to delete me babbling. You know, one possibility is that when you are authenticating

738
00:53:50,800 --> 00:53:56,380
with a very large service, you don't usually use a password. Sometimes you will, and Google will

739
00:53:56,660 --> 00:54:01,280
sometimes let you make app-specific passwords. I don't know whether iOS uses those anymore. I would

740
00:54:01,300 --> 00:54:06,940
be shocked. Almost certainly what you have to do when logging your iOS or Android, well, Android's

741
00:54:06,940 --> 00:54:12,180
a special case, logging your iOS device into Google is to enter an OAuth authentication workflow,

742
00:54:12,960 --> 00:54:16,980
where you get brought over to Google and they say, oh, hey, this is your friendly Google web page.

743
00:54:17,340 --> 00:54:23,740
Do you want to allow Apple's mail client to connect? And so then they give you a token,

744
00:54:24,520 --> 00:54:25,980
and you can use that token to authenticate.

745
00:54:27,860 --> 00:54:31,320
Those tokens, you are meant, you should,

746
00:54:31,540 --> 00:54:33,020
it's not a must, but you should

747
00:54:33,620 --> 00:54:36,520
only have one thing using that token at a time.

748
00:54:37,160 --> 00:54:39,280
And what tends to happen is you use the token,

749
00:54:39,480 --> 00:54:40,920
eventually you say, can I get a replacement?

750
00:54:41,080 --> 00:54:42,020
This token is wearing thin.

751
00:54:42,600 --> 00:54:44,020
And their server says, yeah, here's a new token.

752
00:54:44,220 --> 00:54:44,860
Keep using that one.

753
00:54:46,200 --> 00:54:49,400
If two different things ask for a new token,

754
00:54:50,000 --> 00:54:52,480
the server's like, yeah, you're saying,

755
00:54:52,620 --> 00:54:58,160
can I replace token 5? I already replaced token 5. Something is broken. You're messed up. And what

756
00:54:58,160 --> 00:55:05,780
that means is your iOS device can't have a token to talk to Gmail, but Apple can't run a service in

757
00:55:05,780 --> 00:55:12,340
the cloud that's using that OAuth token to idle and send these connections to you. That's one

758
00:55:12,600 --> 00:55:17,940
possibility. And that's a real possibility that affects some services that use OAuth in that way.

759
00:55:18,900 --> 00:55:24,380
The other option with Apple is that Apple doesn't really mess around on questions of privacy and security.

760
00:55:24,940 --> 00:55:35,340
And if you went into Apple's mail team and said, I think that we should run a service in the cloud with access to people's authentication tokens that sits on IMAP idle, they would boo you out of the room very quickly.

761
00:55:36,040 --> 00:55:38,300
So there's at least two strong possibilities.

762
00:55:38,380 --> 00:55:39,640
But as for the facts, I don't know.

763
00:55:40,160 --> 00:55:40,240
Yeah.

764
00:55:40,900 --> 00:55:41,040
Interesting.

765
00:55:41,200 --> 00:55:43,860
And then another Apple question here.

766
00:55:45,880 --> 00:55:51,620
iCloud released a really cool feature, Advanced Data Protection, several years ago now.

767
00:55:52,360 --> 00:55:53,380
I think it's a wonderful feature.

768
00:55:53,600 --> 00:55:58,800
It has enabled end-to-end encryption for so many people who might have never even used it before.

769
00:55:59,080 --> 00:55:59,880
It's super convenient.

770
00:56:00,200 --> 00:56:02,260
People won't even notice a difference if they enable it.

771
00:56:02,620 --> 00:56:06,000
I highly recommend people enable it if they haven't in the Apple ecosystem.

772
00:56:06,460 --> 00:56:13,360
But it excludes calendar, contacts, and email, which all use these technologies you've been talking about today.

773
00:56:14,640 --> 00:56:18,660
Again, this is another thing I'm asking you to comment on on behalf of another company.

774
00:56:19,010 --> 00:56:21,560
But do you have any speculations as to why they did that?

775
00:56:21,690 --> 00:56:25,780
I mean, we can just, you know, guess, I suppose.

776
00:56:26,240 --> 00:56:27,800
Gosh, you know, I'm not really sure I know.

777
00:56:28,340 --> 00:56:29,620
I'm aware of the feature existing.

778
00:56:31,180 --> 00:56:32,220
I haven't used it.

779
00:56:36,359 --> 00:56:37,280
I don't know.

780
00:56:37,410 --> 00:56:39,240
And I don't think I'm even in a good position to guess.

781
00:56:39,520 --> 00:56:43,140
What I would say is if you are curious, and I might do this research myself, but don't wait for me.

782
00:56:43,920 --> 00:56:48,820
If you were curious, what I would do is go read Apple's technical knowledge-based documentation

783
00:56:49,440 --> 00:56:54,900
on their advanced data protection, because Apple's documentation is often good on these topics,

784
00:56:55,620 --> 00:57:01,640
and it may include, here are our motivations and criteria. And if it does, it might be enough

785
00:57:01,840 --> 00:57:05,620
information to figure out why, but I haven't read it, and also the documentation might not exist or

786
00:57:05,760 --> 00:57:10,240
might be bad. But no, fundamentally, I don't know the answer. Okay, cool. Just figured I'd ask.

787
00:57:11,760 --> 00:57:22,620
One other question, I know this is, you mentioned earlier that FastMail would love to do end-to-end encryption if it's feasible and it probably doesn't sacrifice the user experience.

788
00:57:23,420 --> 00:57:28,700
This is a bit more of a hypothetical, so it's not me asking because you did this, that means you do this.

789
00:57:28,860 --> 00:57:37,960
But does JMAP and that tighter integration that's more reliable and stable make it easier to do end-to-end encryption theoretically than IMAP?

790
00:57:38,760 --> 00:57:38,880
Yeah.

791
00:57:39,840 --> 00:57:44,800
I know it doesn't solve the issues of end-to-end encryption, but I'm just kind of curious if it helps.

792
00:57:44,840 --> 00:57:45,400
It's not clear.

793
00:57:45,660 --> 00:57:47,460
I mean, I guess I'd have to think about it a lot more.

794
00:57:47,620 --> 00:57:48,880
There's a couple things to think about.

795
00:57:49,080 --> 00:57:57,620
If you look at how JMAP works, and we've got a YouTube video that's me explaining JMAP versus IMAP somewhere.

796
00:57:58,019 --> 00:58:01,280
If you send it to me by email after, I'll include it.

797
00:58:01,280 --> 00:58:01,920
I'll send you a link.

798
00:58:02,250 --> 00:58:02,340
Yeah.

799
00:58:06,740 --> 00:58:13,440
You can look at JMAP and really, I would say, pretty easily understand what it's doing, which is one of the hallmarks of a nice protocol.

800
00:58:13,640 --> 00:58:14,380
It just makes sense.

801
00:58:15,560 --> 00:58:23,880
And what you'll see is things like email search from whatever and from Henry.

802
00:58:24,780 --> 00:58:25,880
And then you get a response back.

803
00:58:25,920 --> 00:58:29,540
So these emails, you know, 1, 7, 19 and 4 are from Henry.

804
00:58:31,020 --> 00:58:37,460
Well, the problem there is whatever the server that you're talking to actually needs to be able to see the from of the message.

805
00:58:38,540 --> 00:58:44,480
Now, the way that FastMail's offline support works, and I think we have blog posts about the technology.

806
00:58:44,740 --> 00:58:48,540
Actually, I know we do, but I don't recall in depth whether they explain this part.

807
00:58:49,000 --> 00:58:55,640
is that your web browser effectively runs a tiny JMAP server inside of the tab,

808
00:58:56,500 --> 00:59:01,460
and the web client talks to the server in your web browser, which caches data,

809
00:59:01,810 --> 00:59:03,380
and it gets the data by talking to the server.

810
00:59:04,240 --> 00:59:07,620
So when the whole point of IMAP and then JMAP was having an efficient way

811
00:59:08,140 --> 00:59:12,940
to synchronize your data offline, to have a powerful cache and cache management system,

812
00:59:13,320 --> 00:59:18,020
and resynchronize effectively and efficiently, we've done that in multiple levels.

813
00:59:18,220 --> 00:59:26,480
The browser synchronizes from the server and the client, which runs in your web browser, is synchronizing from the server also running in your web browser.

814
00:59:27,380 --> 00:59:36,320
So on one hand, that lets us do offline because it lets us say the worker thread in the browser is going to use the browser storage for storing the cache.

815
00:59:37,180 --> 00:59:45,780
On the other hand, it's a way to say, well, the JMAP server running on FastML side or whatever server side may not have access to the data.

816
00:59:46,000 --> 00:59:50,900
And so if you try to search or like you can only search by date received, that's the only information we have.

817
00:59:51,660 --> 01:00:01,940
We could then transmit to you encrypted data, which your web browser could decrypt, store in its local cache, decrypted, and allow you to search it there.

818
01:00:02,600 --> 01:00:05,140
And in that sense, you would be able to use JMAP.

819
01:00:05,420 --> 01:00:09,060
Any JMAP client that could speak to that would work.

820
01:00:09,820 --> 01:00:15,360
But if that happens to sound familiar, it's because what I'm describing is the Proton IMAP bridge.

821
01:00:15,460 --> 01:00:19,280
right? It's a way of saying, well, the data is all encrypted somewhere else, but we're going to

822
01:00:19,640 --> 01:00:25,900
synchronize it here and then present a interface to it that is a standard protocol. And yeah,

823
01:00:26,020 --> 01:00:32,040
that's fine. Like it's a way of solving this problem, but JMAP would help by letting you use

824
01:00:32,040 --> 01:00:38,900
a very high quality, high efficiency client, but you would need something that was managing the local

825
01:00:38,920 --> 01:00:47,160
decryption of this data. Got it. Open source. So you've mentioned that you guys do some open

826
01:00:47,340 --> 01:00:52,060
source stuff. What is that? Because again, I think I mentioned you guys are entirely open source,

827
01:00:52,280 --> 01:01:00,580
but what does this kind of look like? So the, I think it's, I don't want to be wrong, but I think

828
01:01:00,640 --> 01:01:06,860
the most notable, certainly the largest scale open source work that we do is the Cyrus JMAP server.

829
01:01:08,240 --> 01:01:14,940
So Cyrus is one of the most popular open source IMAP and JMAP servers.

830
01:01:15,800 --> 01:01:26,940
It's originally developed at Carnegie Mellon University, but these days where the IMAP, I'd have to look, I think I looked recently, it was something like 92% of commits in the last 10 years were written by FastMail.

831
01:01:28,700 --> 01:01:41,720
It's an open source server that does at least IMAP, JMAP, CalDAV, CardDAV, some amount of RSS service, NNTP.

832
01:01:42,770 --> 01:01:44,000
I think it might have had LDAP.

833
01:01:44,260 --> 01:01:49,500
It's a real pile of internet standards, some of which I would like to quietly throw into the ocean.

834
01:01:49,600 --> 01:02:02,760
But when you talk to FastMail and you are speaking JMAP to us or you're speaking CalDAV or CardDAV or IMAP, there's a very thin proxy layer that does a little bit of work, but basically you're talking to Cyrus and all of that is open source.

835
01:02:03,800 --> 01:02:14,580
That's the team that I work with the most, that team I'm talking about how do we deliver what FastMail needs and how do we make all of that work as readily available to open source users as we can.

836
01:02:16,300 --> 01:02:23,260
I would say largely all of the big features of our email calendars and contacts are available on open source.

837
01:02:24,480 --> 01:02:26,680
I'd probably have to draw a diagram to figure out just what isn't.

838
01:02:27,880 --> 01:02:35,020
Our webmail is not open source, although there is a stripped down version of it that you can find on GitHub.

839
01:02:35,260 --> 01:02:40,260
I'm afraid I don't remember where that we kind of offer as a way to test your JMAP implementation.

840
01:02:40,480 --> 01:02:43,360
Because, of course, the web client is just a JMAP client that runs in your browser.

841
01:02:44,600 --> 01:02:51,880
We've got a lot of FastMail is written in Perl, and we've published quite a lot of our software to

842
01:02:52,160 --> 01:02:56,240
the comprehensive Perl Archive Network, which is where you can find open source Perl libraries.

843
01:02:56,780 --> 01:03:03,020
A lot of the email libraries in Perl are written or maintained by FastMail staff.

844
01:03:05,420 --> 01:03:16,280
And Squire, which is our rich text editor in our composer, is a pretty popular library for implementing a rich text editor.

845
01:03:17,240 --> 01:03:23,360
I don't remember anymore who's using it these days, but it's had a number of very notable users in the past.

846
01:03:23,770 --> 01:03:25,820
So we publish a lot of stuff open source.

847
01:03:26,630 --> 01:03:27,840
Not everything, but a lot.

848
01:03:29,010 --> 01:03:35,300
And I think our default position is sort of like, if we think this is going to be a useful library worth maintaining for the public, we'll publish it.

849
01:03:35,480 --> 01:03:38,140
But a lot of what we do is just keeping our servers running.

850
01:03:39,740 --> 01:03:44,860
And tack onto that is our open standards work, which is where I think we're a bit more prolific.

851
01:03:45,920 --> 01:03:51,880
Like I said earlier, when we are developing a new way to do something, we want to do it with open standards.

852
01:03:52,280 --> 01:03:56,480
And that either means, do the existing standards let us do this?

853
01:03:57,100 --> 01:04:07,420
Or is this work going to be of sufficiently high quality that it's worth writing it down as a standard and giving it to the world,

854
01:04:07,600 --> 01:04:13,900
taking it to the engineering task force and say, we think this should be a document that people can use to implement this feature other places.

855
01:04:14,500 --> 01:04:18,540
It's not really the same as open source software, but it's scratching the same itch for me.

856
01:04:19,680 --> 01:04:34,280
Yeah. So what's your general response if somebody is, you know, a hardcore open source advocate and maybe even they exclusively only use open source software and they don't think that your approach really aligns with their values?

857
01:04:34,360 --> 01:04:39,540
And of course, you can just say, well, you don't need to use us. But like, what's your general response to that?

858
01:04:39,580 --> 01:04:46,320
Like, what benefits do you think they're missing out on? Or maybe it doesn't matter in their situation. I'm just kind of curious for that.

859
01:04:46,500 --> 01:05:11,020
Yeah, I think it's tough. I think the short version as well, and you probably shouldn't use FastMail. I think of myself as a pretty strong advocate of open source software when it is appropriate and effective. And there are costs to open sourcing your software. You know, in theory, you can take your software and throw it over the wall, right? Like, here you go, it's our software.

860
01:05:12,640 --> 01:05:16,040
But number one, if you do that, you look like a jerk and maybe you are a jerk.

861
01:05:17,160 --> 01:05:21,380
And number two, you're still pretty likely to be creating costs for yourself.

862
01:05:22,440 --> 01:05:30,200
And the question is largely, it's a question of how do you produce the most benefit for the most people?

863
01:05:30,940 --> 01:05:48,120
And I think that our view is, well, providing people a way to build and run JMAP services and IMAP and so on, but especially JMAP services and JMAP clients in the wild is really valuable and benefits anybody who wants to do it.

864
01:05:48,760 --> 01:05:56,780
And the maintenance cost is something that will really, almost by definition, be shared across the entire JMAP ecosystem.

865
01:05:57,900 --> 01:06:06,940
taking the implementation of the thing that generates the email that says you've been invited to an event and making that open source.

866
01:06:07,780 --> 01:06:11,040
It's real minimal value for anybody outside of FastMail.

867
01:06:11,600 --> 01:06:22,180
And any reported bug that we don't blow off becomes kind of a significant amount of work to take the bug report,

868
01:06:22,360 --> 01:06:26,900
turn it into a test case, integrate the test case, fix the bug, see what else might have been.

869
01:06:27,120 --> 01:06:28,600
Like, it's a huge problem.

870
01:06:28,840 --> 01:06:35,620
And we have to figure out how do we use our person time to the greatest effect.

871
01:06:36,340 --> 01:06:40,160
And that isn't always the greatest effect for FastMail as a business.

872
01:06:40,440 --> 01:06:42,760
It's for FastMail's mission, right?

873
01:06:42,980 --> 01:06:44,480
We are here to make email better.

874
01:06:45,060 --> 01:06:46,580
And that includes the rest of the world.

875
01:06:46,620 --> 01:06:50,060
And we think sometimes the way you do that is not by throwing all the software over the wall.

876
01:06:50,680 --> 01:06:53,460
It's by figuring out how to use our time to the best advantage.

877
01:06:53,860 --> 01:06:57,540
And I should also note here, one of the other things that we value, I think it's not on our

878
01:06:57,740 --> 01:07:01,480
values list, but I can tell you we all value, is being a small company.

879
01:07:02,580 --> 01:07:09,100
At a certain level of scale, your ability to maintain a vision, to maintain levels of quality,

880
01:07:09,500 --> 01:07:16,340
to keep true to your values becomes harder and harder, especially when you are not focused on

881
01:07:16,540 --> 01:07:21,340
how do we create a culture that can and does scale, but rather how do we make a product?

882
01:07:21,760 --> 01:07:28,940
So when we keep our staffing small, it means that open sourcing everything, to me, is kind

883
01:07:28,940 --> 01:07:29,480
of a scary risk.

884
01:07:30,720 --> 01:07:30,880
Right.

885
01:07:31,080 --> 01:07:34,080
And then I do want to touch on that, actually, like your team, where you guys are based and

886
01:07:34,080 --> 01:07:35,620
that kind of stuff shortly.

887
01:07:35,870 --> 01:07:43,380
So is your overall summary, and I guess it's not something that I hear often, not to say

888
01:07:43,440 --> 01:07:46,000
it's not true, it's just that it's not a reason I've heard too much.

889
01:07:46,170 --> 01:07:51,720
So you think the efficiency that you're able to work on the software that you produce for

890
01:07:52,280 --> 01:07:55,200
is better when you don't open source it.

891
01:07:58,260 --> 01:07:59,040
That's one of those cases

892
01:07:59,520 --> 01:08:00,900
where I have to think about what you've said

893
01:08:00,900 --> 01:08:02,360
and decide if it does it exactly

894
01:08:02,520 --> 01:08:03,840
or correctly summarize what I said.

895
01:08:03,880 --> 01:08:04,540
It probably does.

896
01:08:04,740 --> 01:08:05,680
I'm not trying to trip you up.

897
01:08:05,680 --> 01:08:06,940
I'm just trying to find a way to summarize.

898
01:08:08,200 --> 01:08:10,340
I think that's part.

899
01:08:10,440 --> 01:08:13,060
I think that's at least close,

900
01:08:13,300 --> 01:08:13,960
at least part of it.

901
01:08:15,160 --> 01:08:16,540
I also think that fundamentally,

902
01:08:16,940 --> 01:08:17,680
a lot of the time,

903
01:08:19,540 --> 01:08:21,700
it's not so deeply thought through

904
01:08:21,720 --> 01:08:27,240
performed a careful economic analysis. It's, we can look at a piece of work we've done and say,

905
01:08:27,680 --> 01:08:32,400
is it worth open sourcing this? And then you imagine, like, who would use it? How would they

906
01:08:32,620 --> 01:08:36,799
use it? What's the maintenance cost? What does it look like to make that piece of software

907
01:08:37,440 --> 01:08:41,400
carvable out of our existing repository? Right? Because of course, if it's open source,

908
01:08:41,580 --> 01:08:44,580
you probably want that software published in some other repository that is not

909
01:08:45,259 --> 01:08:48,740
the repository inside of FastMail. So you're saying there's overhead

910
01:08:49,720 --> 01:08:56,359
to open sourcing things that you guys like feel like isn't worth or you don't have the

911
01:08:57,259 --> 01:09:01,600
I think that's I would personally say that's my view on it and I wouldn't want to speak for all

912
01:09:01,600 --> 01:09:07,200
the other chiefs but but yeah that's my view okay so I'm trying to find a good way to summarize

913
01:09:07,759 --> 01:09:12,440
I think overhead is totally reasonable I've done a lot I've done a lot of open source work I've run

914
01:09:12,540 --> 01:09:18,720
some some large open source projects and I love it I think it's important I think it it makes the

915
01:09:18,740 --> 01:09:24,100
But man, like when you're the project manager of a large open source project, like your life is overhead.

916
01:09:24,500 --> 01:09:25,960
It's a lot of work.

917
01:09:25,980 --> 01:09:30,460
And you got to figure out, you know, how do you make that work?

918
01:09:31,299 --> 01:09:41,060
Yeah, I've definitely heard that even from, I've seen some interviews with Linus Torvalds and hearing him talk about like managing the Linux kernel is pretty.

919
01:09:41,279 --> 01:09:42,140
Yeah, enormous.

920
01:09:42,880 --> 01:09:43,740
Enormous, incredible.

921
01:09:44,759 --> 01:09:53,859
And I know people, he gets criticized a lot for being, losing his temper in certain situations.

922
01:09:54,540 --> 01:09:59,260
But if I had to navigate the situation that he's in, I don't think I'd have very much patience either.

923
01:09:59,740 --> 01:10:07,520
Yeah, I mean, yes, he is dealing with enormous amounts of change and enormous amounts of expectations.

924
01:10:08,080 --> 01:10:13,500
Those two things, people have expectations and they do or do not want change and often both.

925
01:10:13,920 --> 01:10:16,860
So like it's and they're people and people are hard to deal with.

926
01:10:16,900 --> 01:10:17,920
I love people, but they're hard.

927
01:10:18,580 --> 01:10:21,240
Yeah, especially I think the Internet does make that more challenging, too.

928
01:10:22,180 --> 01:10:24,380
So it's it's layers on layers.

929
01:10:26,300 --> 01:10:29,620
Now, I promise I'm getting down to the last few things here.

930
01:10:31,020 --> 01:10:37,179
One, I guess one concern I would have about the lack of maybe zero knowledge, and it has

931
01:10:37,200 --> 01:10:48,620
It's nothing to do with trust, actually, on the company's behalf, but it's more about like an insider threat or if a hacker infiltrates your guys' system.

932
01:10:48,850 --> 01:10:59,100
So what protections do you guys have in place or assurances to make sure that, like, you know, someone who has, you know, bad intentions can access their emails?

933
01:10:59,540 --> 01:11:02,920
And that's that is I think we tend to view that as our biggest threat model.

934
01:11:03,210 --> 01:11:06,340
Right. Like, how do you prevent that from from being leveraged?

935
01:11:06,520 --> 01:11:12,680
And it's something that we spend a decent amount of time every year talking about and working on improving the issues there.

936
01:11:13,330 --> 01:11:17,220
I don't really, well, first off, I do not have a great list in front of me.

937
01:11:17,250 --> 01:11:18,440
So I'll just fire some things from the hip.

938
01:11:19,880 --> 01:11:23,280
The thing I actually like the best we do is sort of low tech.

939
01:11:25,220 --> 01:11:27,660
And I don't know, I feel very pleased about it.

940
01:11:28,560 --> 01:11:30,020
We have really good customer service.

941
01:11:30,540 --> 01:11:36,380
And when I talk to people about why they should use FastMail, and what I want to say is, let me tell you all about JMAP.

942
01:11:36,480 --> 01:11:39,160
It's so exciting, but, you know, my barber doesn't care about JMAP.

943
01:11:40,260 --> 01:11:48,240
But what I end up saying is, like, well, if you have a problem with getting your Apple Mail to connect, you talk to a human being who will get right back to you.

944
01:11:48,650 --> 01:11:57,380
And if they can't help you, they can shout, you know, 10 meters across the room to me, like one of the foremost people in a position to fix your problem.

945
01:11:58,220 --> 01:12:01,400
And compare that to very large providers, that's a great experience.

946
01:12:01,610 --> 01:12:06,160
But it means that we've got a support team who want to be able to help you solve your problem.

947
01:12:07,760 --> 01:12:12,540
When they do that, they can access your account, I put in scare quotes, because what they actually

948
01:12:12,840 --> 01:12:16,640
get is sort of an interface that looks kind of like your interface with kind of the same

949
01:12:16,840 --> 01:12:17,000
shape.

950
01:12:17,220 --> 01:12:22,580
And like there's 17 messages in a folder, but those messages all say lorem ipsum and the

951
01:12:22,760 --> 01:12:23,980
folders are all foo, right?

952
01:12:24,120 --> 01:12:28,780
And it's like they get an interface where they can see massive structural problems occurring.

953
01:12:29,670 --> 01:12:35,260
But if they want to access your information, you need to positively opt in and say, I am giving access to support.

954
01:12:36,140 --> 01:12:40,940
And this is different than protecting against the person who's gotten into the data center and plugged a keyboard into a server.

955
01:12:41,640 --> 01:12:50,640
But it protects against a lot of, how do I put it, social engineering becomes a lot harder.

956
01:12:52,220 --> 01:12:58,740
access through the support staff who are the people who are very trained in how to understand

957
01:12:58,970 --> 01:13:05,360
social engineering. It's the thing we take very seriously, but also are not looking at every single

958
01:13:05,560 --> 01:13:10,440
step happening at every part of the request, right? They're an attack service. And first off,

959
01:13:10,450 --> 01:13:15,760
we train them really well to understand what's going on there. And secondly, we've built systems

960
01:13:15,780 --> 01:13:24,040
that isolate them from walking into this danger room of user data. User data is toxic. You never

961
01:13:24,180 --> 01:13:32,200
really want to be exposed to it. Apart from that, we do a lot of auditing. So when systems are

962
01:13:32,540 --> 01:13:36,900
accessed, we can always see who's accessed it, what have they done, that gets reviewed. And you

963
01:13:36,900 --> 01:13:41,841
know, we can be like, why were you logged into the Caldab server over here? Oh, well, this bug

964
01:13:41,860 --> 01:13:46,700
number, which you can reference, and that's going to be an explanation there. Those are the things

965
01:13:46,820 --> 01:13:52,800
that I think are most important because they build into the way we work. A culture of access and user

966
01:13:52,960 --> 01:13:58,760
data is bad. The things that you do should be constrained to the systems where you are meant,

967
01:13:58,820 --> 01:14:04,440
the log server, the places you are meant to be doing investigation. I think it's going to take,

968
01:14:05,240 --> 01:14:11,820
it would take a lot of work to get us to be fully a zero trust system. Putting aside the question of

969
01:14:11,840 --> 01:14:17,400
zero knowledge of like, technically do the bytes of your data exist in plain text on a live service.

970
01:14:18,860 --> 01:14:25,240
But it is a problem that we are continually working on because when we talk about your data

971
01:14:25,500 --> 01:14:30,980
being private, we've solved the problem. We don't want to look at your data. There's nothing in it

972
01:14:31,100 --> 01:14:37,139
for us. And the next question is, how do we avoid accidental issues or how do we prevent

973
01:14:38,120 --> 01:14:42,420
external parties from getting some kind of insider access to it. That's an ongoing concern.

974
01:14:43,200 --> 01:14:53,520
Got it. And then for the phone number registration, if I can guess, my guess is it's just an easy way

975
01:14:53,600 --> 01:15:00,680
to prevent spam, and it's a very common onboarding thing. Yeah. There's a couple things.

976
01:15:01,640 --> 01:15:05,620
Yeah. Did you want to say anything about where it came from or where this question comes from?

977
01:15:05,740 --> 01:15:07,060
Because you and I both know it's from your other video.

978
01:15:07,140 --> 01:15:08,160
I don't know what you want to...

979
01:15:08,160 --> 01:15:09,480
Yeah, I mean, it's because...

980
01:15:09,480 --> 01:15:12,800
So I guess some context here, and this is definitely more rare.

981
01:15:13,640 --> 01:15:15,920
So I don't really blame you guys for not accommodating it.

982
01:15:17,420 --> 01:15:21,360
But our community may have this a little bit more than most communities.

983
01:15:22,580 --> 01:15:25,980
I don't really have a regular phone number.

984
01:15:27,380 --> 01:15:27,500
Yep.

985
01:15:28,480 --> 01:15:31,420
I only use VOIP numbers on my phone.

986
01:15:31,740 --> 01:15:34,860
And, you know, this doesn't mean I use just random generated phone numbers.

987
01:15:34,940 --> 01:15:38,860
It's just I have a Google voice number, which is like very nice to use.

988
01:15:38,890 --> 01:15:42,800
It means when I travel internationally, I don't have to deal with international SIMs or

989
01:15:42,920 --> 01:15:43,560
international phone plans.

990
01:15:43,700 --> 01:15:46,120
I'm just data only and I still have my regular phone numbers.

991
01:15:47,020 --> 01:15:48,120
So it's just very convenient.

992
01:15:48,820 --> 01:15:51,780
And but I wasn't able to register for FastMail with any of my numbers.

993
01:15:53,180 --> 01:15:57,180
And I was willing even to like put in a credit card number like I was willing and I was really

994
01:15:57,360 --> 01:16:00,300
happy to accidentally discover the mobile workaround.

995
01:16:00,460 --> 01:16:02,860
Like I was able to register on mobile.

996
01:16:03,180 --> 01:16:06,340
I was able to pay on mobile and it didn't ask me for a phone number when I did that.

997
01:16:07,060 --> 01:16:09,140
And then I'm like, cool, I got in and I was really happy.

998
01:16:10,120 --> 01:16:12,480
Is that on purpose?

999
01:16:13,980 --> 01:16:15,120
It's at least somewhat on purpose.

1000
01:16:15,220 --> 01:16:15,940
And I'll tell you some.

1001
01:16:16,140 --> 01:16:25,920
The first thing I should say is those issues around sign up and verification are sort of constantly in motion.

1002
01:16:27,400 --> 01:16:32,740
Every time you adapt to attackers, their attacks change and you have to keep moving.

1003
01:16:33,200 --> 01:16:35,580
And I'll come back to why these attackers even exist in a little bit.

1004
01:16:37,520 --> 01:16:44,300
I was a little surprised by the implication that you couldn't just pay to skip phone verification.

1005
01:16:45,200 --> 01:16:48,380
That might be a mistake on our part.

1006
01:16:48,480 --> 01:16:48,960
It might be a bug.

1007
01:16:49,680 --> 01:16:53,740
It might be that the intended behavior changed and I didn't notice the memo.

1008
01:16:54,120 --> 01:16:55,260
Like, really possible.

1009
01:16:55,940 --> 01:16:59,640
And it might be that there was some, you know, click here to just pay that you missed.

1010
01:16:59,960 --> 01:17:01,220
I just don't know which one it is.

1011
01:17:01,700 --> 01:17:01,760
Yeah.

1012
01:17:02,020 --> 01:17:05,060
But let me start by saying, I don't want to know your phone number.

1013
01:17:05,250 --> 01:17:08,360
I don't want to know anybody's phone number who's using FastMail.

1014
01:17:08,960 --> 01:17:16,060
The phone number for account verification is like, we'll keep it on file to help you with security to some extent there.

1015
01:17:16,720 --> 01:17:22,820
But yeah, as you said, it's a question of reducing fraud.

1016
01:17:24,220 --> 01:17:29,020
And letting people verify with a VoIP number does not reduce fraud.

1017
01:17:29,620 --> 01:17:39,220
Because the ability of robots to immediately get 10,000 different VoIP numbers for 10 minutes to go through this process is unbelievable.

1018
01:17:39,800 --> 01:17:41,380
It's crazy how easily that can happen.

1019
01:17:42,880 --> 01:17:45,260
And I really wish we didn't have to do any of it.

1020
01:17:45,460 --> 01:17:47,660
What I would like to say is, yeah, you get your trial account.

1021
01:17:47,690 --> 01:17:49,120
At the end of the trial account, you pay or you don't.

1022
01:17:49,150 --> 01:17:50,320
And in the meantime, what the hell do I care?

1023
01:17:51,180 --> 01:17:57,040
The problem is email is a service that you use for talking to other networks.

1024
01:17:57,720 --> 01:18:01,340
You don't get a FastMail account only to talk to other FastMail users.

1025
01:18:02,200 --> 01:18:04,080
You might, but it's uncommon.

1026
01:18:04,370 --> 01:18:05,540
You want to talk to Gmail.

1027
01:18:05,770 --> 01:18:06,840
You want to talk to Hotmail.

1028
01:18:06,910 --> 01:18:07,880
You want to talk to Proton.

1029
01:18:08,900 --> 01:18:14,320
And one of the things some people want to do when they talk to Gmail is to send emails that say,

1030
01:18:14,750 --> 01:18:16,040
your Amazon package is delayed.

1031
01:18:16,420 --> 01:18:18,540
Click here to find out more and put in your credit card.

1032
01:18:18,900 --> 01:18:20,380
Phishing is huge.

1033
01:18:20,960 --> 01:18:21,860
There's two ends to it.

1034
01:18:22,280 --> 01:18:33,220
One is people who want to send phishing mail, and one is people who want to receive verification emails from other services so they can create a whole bunch of signups, receive these messages, and read them.

1035
01:18:33,920 --> 01:18:46,280
So we do things to prevent people from sending or reading mail if something's going on with the account, if it's from an unusual IP, if there's a lot of ifs, there's a big algorithm somewhere in the system.

1036
01:18:48,460 --> 01:18:51,560
And it would be really nice if we didn't have to do that.

1037
01:18:52,340 --> 01:18:59,400
But the problem isn't just that being a good internet citizen means we don't want people using our platform to send garbage.

1038
01:19:00,520 --> 01:19:08,100
It's that the way everybody in email does anti-spam is going to include IP reputation.

1039
01:19:09,040 --> 01:19:17,920
So if Google starts getting a thousand phishing messages from one of our IPs, they're going to say, I don't know what's going on over that IP, but I don't want it to mail.

1040
01:19:18,740 --> 01:19:32,220
And now this one signup, and it's usually more like 25 signups, blasting out email as fast as they can, has a negative impact on the performance of the mail of everybody else.

1041
01:19:32,720 --> 01:19:40,000
We've done a lot of things to isolate that, to contain how it works, but it's never quite going to be enough to fully isolate it.

1042
01:19:40,220 --> 01:19:51,020
And one minor tech digression here is we're especially hamstrung because server-to-server email communication is pretty much entirely on IPv4.

1043
01:19:51,960 --> 01:19:56,140
So you only have so many IP addresses that you can isolate new signups into.

1044
01:19:56,170 --> 01:20:03,560
You can't say, well, all the new signups get their own little tiny niche of IPv6 space, and you can figure out exactly what's going on.

1045
01:20:03,890 --> 01:20:07,180
You have to put them on this very, very scarce resource.

1046
01:20:08,340 --> 01:20:10,080
So it stinks.

1047
01:20:10,720 --> 01:20:15,780
I wish people didn't have to do almost anything to verify, but that would only work if we didn't

1048
01:20:15,920 --> 01:20:20,720
have jerks signing up and making life worse for people who definitely are paying.

1049
01:20:21,360 --> 01:20:22,240
Yeah, and it's a bummer.

1050
01:20:23,580 --> 01:20:29,080
So when I'm asking this question, really, if I'm wrong about being able to bypass that

1051
01:20:29,100 --> 01:20:32,820
and I just missed something, I super apologize because that fully addresses my concern.

1052
01:20:34,080 --> 01:20:39,900
Because I, you know, Signal asks for a phone number.

1053
01:20:40,140 --> 01:20:40,860
People ask why.

1054
01:20:41,400 --> 01:20:42,500
Probably very similar reasons.

1055
01:20:43,760 --> 01:20:47,960
Proton, people complain, oh, I'm just trying to sign up for a free account, but they make

1056
01:20:47,960 --> 01:20:52,100
me put in a valid recovery email and it can't be an alias service.

1057
01:20:52,760 --> 01:20:55,420
So people are like, well, it's not even in a fully anonymous sign up anymore.

1058
01:20:55,520 --> 01:21:00,240
And it's like, yeah, because that's how you can still have a usable service for people.

1059
01:21:00,500 --> 01:21:07,600
So I have no issue with services having ways to verify people are legitimate, that they're there for the right reasons.

1060
01:21:08,270 --> 01:21:09,860
And I think it's really good that you guys do that.

1061
01:21:10,380 --> 01:21:13,860
I just didn't see the – I was like, I just want to put in my credit card.

1062
01:21:14,150 --> 01:21:18,360
So I might have totally missed something, and if that's an honest mistake, I'm very sorry about that.

1063
01:21:18,360 --> 01:21:19,540
It could be a problem in our end, too.

1064
01:21:19,550 --> 01:21:20,000
I just don't.

1065
01:21:21,000 --> 01:21:26,880
So, yeah, that was mainly – I wanted to see if that was intentional or not or if there was a specific reason for that one.

1066
01:21:28,620 --> 01:21:30,300
Because, yeah, I don't have a phone number.

1067
01:21:31,120 --> 01:21:36,260
even even taking payment is not a great guarantee because the the it seems like the ease with which

1068
01:21:36,360 --> 01:21:43,100
people can get access to stolen credit cards that work is uh i mean it's just all bad yeah um but

1069
01:21:43,100 --> 01:21:47,800
nobody can't do a trial of an email service if you can't send mail yeah these people seem creative um

1070
01:21:48,120 --> 01:21:54,119
it's a bummer too because like you guys don't have to offer a free trial proton doesn't have to have

1071
01:21:54,140 --> 01:22:00,620
free plan like like none of these services have to offer these things for free and it's yeah it's

1072
01:22:01,090 --> 01:22:05,320
yes i mean it's cool you guys probably get some there's probably been some value you guys have found

1073
01:22:05,480 --> 01:22:09,240
where it's like oh when people actually try our service they see how good it is and they're more

1074
01:22:09,340 --> 01:22:14,420
likely to subscribe so i'm sure there's that as a big factor as well but you guys don't have to have

1075
01:22:14,420 --> 01:22:21,239
a free trial like yeah you could just pay all of it and then no one could even try using it um and i

1076
01:22:21,260 --> 01:22:22,660
But we'd still have the same problem.

1077
01:22:23,040 --> 01:22:27,360
We'd have the same problem because those payment still gets you access to send.

1078
01:22:27,540 --> 01:22:33,180
And it's like, well, and two days later, the charges are reversed when the person figured out that their credit card got stolen.

1079
01:22:33,460 --> 01:22:38,900
But by that time, the signup has already sent 24,000, whatever number of messages.

1080
01:22:40,200 --> 01:22:41,400
It's just a hard problem.

1081
01:22:41,720 --> 01:22:46,440
And the solution to that problem is for people to not be jerks on the Internet.

1082
01:22:46,520 --> 01:22:50,940
But there's a lot of motivations for people to be involved in scamming, too.

1083
01:22:51,740 --> 01:22:59,160
yeah i believe it um australia that's uh something i've seen the community talk about um

1084
01:23:00,480 --> 01:23:05,520
it's mostly in the context of encryption because australia seems to be heading in a very

1085
01:23:06,080 --> 01:23:10,780
anti-encryption direction but so is the whole world right now so you know a session the messenger

1086
01:23:11,060 --> 01:23:14,940
moved from australia and they changed all the way to switzerland and now switzerland's being

1087
01:23:15,180 --> 01:23:20,960
anti-encryption it's very unfortunate for them um so it's maybe less of a thing for you guys

1088
01:23:20,980 --> 01:23:26,080
but do you see the Australian jurisdiction having any implication for the privacy and security that

1089
01:23:26,080 --> 01:23:33,260
you guys are able to offer your consumers? I think that what we see is people having

1090
01:23:33,640 --> 01:23:42,480
concerns about it. And what would be great is having a jurisdiction that was as good as Australia,

1091
01:23:43,040 --> 01:23:50,940
plus had lots and lots of things in place to uphold data privacy and so on. And Australia

1092
01:23:50,960 --> 01:23:56,680
not have as much regulation around that as some places do. And it has some laws that seem kind of

1093
01:23:56,820 --> 01:24:00,720
maybe creepy, but we haven't seen how they're actually going to play out, right? Like if we

1094
01:24:00,940 --> 01:24:05,160
look even, if we look at the analysis of things like Cloudact over the years, like it's changed

1095
01:24:05,260 --> 01:24:13,520
quite a bit what people think it will or won't do. In practice, I can say that I have never felt

1096
01:24:14,080 --> 01:24:19,739
concerned about Australia. We have gotten, you've seen the disclosure numbers, we've gotten very few

1097
01:24:19,760 --> 01:24:20,560
I'm looking at it.

1098
01:24:20,560 --> 01:24:20,720
I'm looking at it.

1099
01:24:20,820 --> 01:24:25,260
A 24, 16 total.

1100
01:24:25,520 --> 01:24:26,700
Yeah, very small numbers.

1101
01:24:26,900 --> 01:24:34,860
I think that in every case we've seen the details of what's going on and it's, you know, it's not, there's no blanket anything.

1102
01:24:35,340 --> 01:24:39,980
There's no give me everything on this person for reasons that you will never know and no one can ever disclose.

1103
01:24:41,020 --> 01:24:43,320
We funnel all these requests through Australia.

1104
01:24:44,120 --> 01:24:46,320
The Australian legal process we found to be pretty reliable.

1105
01:24:47,140 --> 01:24:54,280
It's, you know, it's not a perfect world, but I don't, but when we look at our concerns and our

1106
01:24:54,450 --> 01:25:02,960
risks internally, the actual impact of Australian legislation is not incredibly high on our list.

1107
01:25:03,240 --> 01:25:08,500
It's a thing that we're aware of that we would like Australia to have different legislation in

1108
01:25:08,500 --> 01:25:13,780
a number of places because we think it's the right thing to do. And we think that the laws should be

1109
01:25:13,800 --> 01:25:18,440
doing the right thing, but that's different than them having a negative practical impact on anything

1110
01:25:18,560 --> 01:25:23,200
that's actually happening. Got it. And so if people want to keep up with that, I mean, I see the data

1111
01:25:23,380 --> 01:25:27,860
transparency report on your website. Is that where people can follow that kind of thing? Yeah, that's

1112
01:25:27,860 --> 01:25:34,000
what I would suggest. Keep an eye on that. And from time to time, we post blog posts about things

1113
01:25:34,140 --> 01:25:38,720
like Cloud Act, Telecommunication Act. It may have been a while since our last one, but you can find

1114
01:25:38,730 --> 01:25:42,960
in our blog archive our discussion of our analyses of these and how they're going to play out. Also,

1115
01:25:43,040 --> 01:25:48,100
a lot of this stuff is untested as it reflects email or internet providers. So, you know, what

1116
01:25:49,020 --> 01:25:52,740
the law can say one thing, and then what does it actually mean? And what would it get enforced?

1117
01:25:53,260 --> 01:25:57,800
A lot of that's not clear. Got it. And then, so what's your team look like? Like,

1118
01:25:57,850 --> 01:26:02,860
how many of you guys are in Australia? I'm not hearing an Australian accent from you.

1119
01:26:03,240 --> 01:26:10,100
No, no. So I'm sitting here in Philadelphia, center city, go birds. And we have an office

1120
01:26:10,120 --> 01:26:15,100
here in Philadelphia. About 10 of us. I should know the numbers off the top of my head, but I

1121
01:26:15,240 --> 01:26:22,360
don't at this point. Right now, for the next year, year and a half, our CEO is located here. He does

1122
01:26:22,410 --> 01:26:29,080
have an Australian accent. Normally, he is back in our world headquarters in Melbourne,

1123
01:26:30,000 --> 01:26:34,000
Melbourne, Australia, where we have, I would say, about half of our staff. Again, I don't have the

1124
01:26:34,020 --> 01:26:42,760
exact numbers. We're a bit shy of 50 people, I think, at this point. We've got about half of that

1125
01:26:42,760 --> 01:26:50,320
in Australia, some here and some in India, where we have a support team. And this works really well

1126
01:26:50,680 --> 01:26:56,700
for a couple of reasons. We have on-call. Basically, everybody's awake when they are on-call.

1127
01:26:57,220 --> 01:27:02,900
I don't need to be on-call at three in the morning. This is maybe not a big deal for users who don't

1128
01:27:02,920 --> 01:27:08,660
care as long as somebody is on call. But, you know, when you work at Fast Mill, we want you to feel like

1129
01:27:09,000 --> 01:27:14,200
you come to work if you leave work. And, you know, then you have your own life that you enjoy fully,

1130
01:27:14,400 --> 01:27:18,500
which can be hard to do if you can't put away your computer and go to the movies or go to sleep.

1131
01:27:19,980 --> 01:27:25,260
So the U.S. team is online during the U.S. day. The Australian team is online during the Australian

1132
01:27:25,420 --> 01:27:32,340
day. And the Indian team picks up a lot of the difference or the middle ground between the U.S.

1133
01:27:32,720 --> 01:27:38,460
and Australian support teams. So we have someone on support. I don't think 24-7, but we cover a lot

1134
01:27:38,460 --> 01:27:44,700
of that. And then we're all on one Slack. We have integrated Zoom meetings. We all interact directly.

1135
01:27:44,820 --> 01:27:49,600
There's not really any sort of like, well, that office over there only communicates through its

1136
01:27:50,240 --> 01:27:54,580
individual lead. We do also have a couple of remote people in the US and in Europe.

1137
01:27:55,380 --> 01:28:00,960
Got it. And yeah, I guess just kind of pivoting to the last few questions I have here,

1138
01:28:01,060 --> 01:28:03,820
or more just broad, fast mail questions.

1139
01:28:05,310 --> 01:28:07,080
A big thing that's been rising in popularity,

1140
01:28:07,600 --> 01:28:11,180
not for me, because all these things are treating like,

1141
01:28:11,760 --> 01:28:14,060
you know, it's like the Chanel bags now of email clients,

1142
01:28:15,920 --> 01:28:17,620
superhuman, all of these fancy,

1143
01:28:18,130 --> 01:28:20,480
like ultra productivity AI things.

1144
01:28:21,520 --> 01:28:23,060
It actually seems to have similar,

1145
01:28:23,780 --> 01:28:26,580
I don't want to put words in your mouth,

1146
01:28:26,660 --> 01:28:27,400
this is a bit extreme.

1147
01:28:27,510 --> 01:28:30,080
It has a similar aspect of what you said earlier,

1148
01:28:30,340 --> 01:28:33,220
which is being like heavy into productivity and just working for you.

1149
01:28:33,820 --> 01:28:35,660
That seems to be a common overlap there.

1150
01:28:36,120 --> 01:28:40,760
Are you guys, do you guys already feel like you offer, I've never used any of these.

1151
01:28:40,860 --> 01:28:45,020
So this is more of just me like reading these different web services or these email services.

1152
01:28:45,580 --> 01:28:46,740
Do you guys see value in that?

1153
01:28:46,880 --> 01:28:50,920
Is there a potential integration or something you want to do that kind of mimics those?

1154
01:28:51,260 --> 01:28:53,260
Or do you guys feel like you're taking the right approach?

1155
01:28:54,380 --> 01:28:59,340
Well, I'm going to start by, start at the end, which is I think we're taking the right approach

1156
01:28:59,380 --> 01:29:03,840
because what we're doing is we're offering the standard mechanisms for interacting with email.

1157
01:29:04,700 --> 01:29:12,720
And if somebody wanted something like superhuman to exist for fast mail, they would then implement

1158
01:29:12,940 --> 01:29:17,040
it either with IMAP or JMAP and it would work everywhere. That's how that should work. That's

1159
01:29:17,040 --> 01:29:20,840
how the internet should work. I don't want to say end of story, but like only Google, right?

1160
01:29:20,900 --> 01:29:25,920
They don't even... Superhuman is, that's right. And really it's understandable. You know, when I'm

1161
01:29:25,940 --> 01:29:31,840
complaining about these like antiquity of IMAP and the email format like yeah it stinks right you're

1162
01:29:31,840 --> 01:29:36,160
gonna how much of my brain is wasted remembering things like how do you what are the six ways of

1163
01:29:36,260 --> 01:29:41,460
encoding a non-7 bit clean string in email it's a terrible terrible thing yeah it's common too

1164
01:29:41,720 --> 01:29:47,480
notion mail same thing I think it's Google only because all these they seem to be nice email clients

1165
01:29:47,640 --> 01:29:54,420
but you have to have Gmail to use them I think that the cure for that is JMAP I think that JMAP

1166
01:29:54,440 --> 01:29:58,740
switches it from having to learn all these really weird ways of interacting with your data

1167
01:29:59,360 --> 01:30:03,920
to learning one or two fairly straightforward ways of interacting with your data. And then you

1168
01:30:04,020 --> 01:30:10,480
can interact with any email server that implements JMAP. And implementing JMAP as a bar, something

1169
01:30:10,660 --> 01:30:16,340
has to do it. But if you're running a Cyrus mail server at your university, you have JMAP, right?

1170
01:30:16,380 --> 01:30:21,260
You just have to turn it on and offer a little bit of a configuration change. If you're running

1171
01:30:22,280 --> 01:30:25,000
if you're running an Apache James server, you have a JMAP server.

1172
01:30:25,720 --> 01:30:27,360
And there's other options out there.

1173
01:30:28,300 --> 01:30:30,160
JMAP gives you push.

1174
01:30:30,230 --> 01:30:31,500
It gives you real-time notification.

1175
01:30:31,680 --> 01:30:32,280
That's another thing, right?

1176
01:30:32,450 --> 01:30:34,120
You talk about these open connections sitting there.

1177
01:30:34,820 --> 01:30:37,440
Superhuman doesn't want to have all these open connections sitting around

1178
01:30:37,800 --> 01:30:40,300
keeping in touch with your IMAP server.

1179
01:30:40,940 --> 01:30:43,580
They want to get told by the server there's a message.

1180
01:30:43,950 --> 01:30:46,500
Then they pass it on to your browser or like an event stream.

1181
01:30:47,420 --> 01:30:48,140
And there you go, right?

1182
01:30:48,160 --> 01:30:48,520
It just works.

1183
01:30:49,120 --> 01:30:52,680
They're using Gmail because it's the only way to efficiently implement their product.

1184
01:30:54,160 --> 01:30:55,280
JMAP is another way to do it.

1185
01:30:56,200 --> 01:30:58,660
It needs market penetration for it to be worth doing that way.

1186
01:30:58,690 --> 01:30:59,580
So that's one part of it.

1187
01:30:59,630 --> 01:31:00,860
Like, are we doing the right thing?

1188
01:31:01,080 --> 01:31:03,120
Yes, they should be targeting JMAP.

1189
01:31:03,310 --> 01:31:03,800
Why aren't they?

1190
01:31:04,070 --> 01:31:07,240
Because 80% of the world's users have access to the GData API, right?

1191
01:31:07,410 --> 01:31:07,740
The end.

1192
01:31:10,040 --> 01:31:12,080
Do we want to offer things like that?

1193
01:31:12,220 --> 01:31:18,400
I think that when we talk about productivity users, they are part of our user base.

1194
01:31:19,240 --> 01:31:22,840
we have a lot of productivity features. The productivity features we offer,

1195
01:31:23,940 --> 01:31:28,700
the good news is that you can use only the ones you want or all of the ones you want,

1196
01:31:29,080 --> 01:31:34,160
and you can use them in whatever combination you want. And the bad news is you have to figure out

1197
01:31:34,300 --> 01:31:41,140
which ones you want to use and in what combination. So when we are adding features, productivity

1198
01:31:41,460 --> 01:31:47,040
features, but any features, we have to think about what does this do in combination with every

1199
01:31:47,060 --> 01:31:50,980
other feature we're offering, right? We've added, that's more than a checkbox, right? We've added a

1200
01:31:50,980 --> 01:31:55,580
whole lot of complexity by adding even like memos we added to email recently. You can put a little

1201
01:31:55,780 --> 01:31:59,240
memo on any email you receive telling you what you wanted to say when you eventually reply.

1202
01:32:00,740 --> 01:32:04,640
That's, it's a, it's just one little text box, right? But there's a bunch of things to think about

1203
01:32:04,640 --> 01:32:12,300
how does that interact? Superhuman and some other products like it sort of start by saying,

1204
01:32:12,740 --> 01:32:15,500
we have a bunch of thoughts about how email should work.

1205
01:32:16,320 --> 01:32:18,660
That is one unified way of thinking about it.

1206
01:32:18,860 --> 01:32:21,980
And you can approach that and you get all this leverage,

1207
01:32:22,180 --> 01:32:24,480
but you have to want to pull exactly the lever they've built,

1208
01:32:24,800 --> 01:32:26,420
or at least a lever in that general shape.

1209
01:32:27,060 --> 01:32:29,160
PassMill's giving more flexibility,

1210
01:32:30,040 --> 01:32:32,200
which is great for people who have a lot of opinions.

1211
01:32:32,940 --> 01:32:35,080
And for people who don't really know what they want yet,

1212
01:32:35,440 --> 01:32:38,600
it's a question of figuring out what's the next feature that we can offer them

1213
01:32:39,160 --> 01:32:41,240
to hook them in to wanting to learn about more,

1214
01:32:41,420 --> 01:32:43,540
How do we teach them about more of these features?

1215
01:32:44,070 --> 01:32:52,180
I think that something like a radical departure from the standard email interface like Superhuman is, I don't think it's real likely.

1216
01:32:52,270 --> 01:33:03,200
I think that it would require a lot more investment on people wanting to learn how to use a tool as opposed to get in, use a tool they already understand, but works really well and get out.

1217
01:33:03,760 --> 01:33:13,300
Got it. So you're saying that your approach is to offer, you know, a more focused, more polished experience that even has more productivity in something like Gmail.

1218
01:33:13,880 --> 01:33:18,800
And you want to offer like the core critical tools that you think most people need.

1219
01:33:19,130 --> 01:33:26,680
And then you would hope that if this tool were to exist, it would be utilizing JMAP to integrate well with the tools you offer.

1220
01:33:27,560 --> 01:33:30,940
Yeah, I think that's right. I mean, the person to really ask here is our product officer.

1221
01:33:31,580 --> 01:33:36,140
In almost all questions like this, I'm like, actually, I'm the weirdo who used Mutt for 20 years.

1222
01:33:37,160 --> 01:33:40,760
If we want to know what we do with the product, we ask the guy who really knows everything about it.

1223
01:33:40,980 --> 01:33:43,340
So I'm giving you my opinion, but I think it's probably pretty accurate.

1224
01:33:43,780 --> 01:33:44,000
Got it.

1225
01:33:44,180 --> 01:33:44,920
Yeah, and I think it makes sense.

1226
01:33:45,100 --> 01:33:45,500
It's a bummer.

1227
01:33:45,620 --> 01:33:48,281
You know, these tools need to be...

1228
01:33:51,620 --> 01:33:54,360
It really locks the kind of consumer away, right?

1229
01:33:54,600 --> 01:33:56,400
I mean, I don't think Superhuman cares.

1230
01:33:56,820 --> 01:34:00,420
I don't know if they still do this, but I heard they interview you.

1231
01:34:00,840 --> 01:34:08,000
have to be on boarded. Yeah. And you have to use Google. So you either are a Gmail user or you use

1232
01:34:08,080 --> 01:34:12,480
Google workspace for your business. Otherwise you just can't use the service and they don't seem to

1233
01:34:12,580 --> 01:34:18,280
care. And that's probably okay. Cause they charge $30 a month for you to use their service. But I

1234
01:34:18,380 --> 01:34:22,560
think it would be awesome to have this ultra powerful email client that was meant to be used

1235
01:34:22,860 --> 01:34:32,440
with anything. Now, if someone, the answer is yes, but just for clarification, you guys do work with

1236
01:34:32,560 --> 01:34:39,480
IMAP. Oh, yeah. That's not clients that don't support JMAP. Absolutely. Okay. And is that because

1237
01:34:39,600 --> 01:34:45,060
you just still support IMAP or is it because JMAP is interoperable with IMAP? Does that make sense?

1238
01:34:45,620 --> 01:34:51,700
I know what you mean. No, it's because most male clients are IMAP clients. And so what we want,

1239
01:34:51,740 --> 01:34:53,180
You meet your customers where they are.

1240
01:34:53,620 --> 01:35:00,320
If the data belongs to you, we should permit you the reasonable ways that you would expect to get at your data.

1241
01:35:01,600 --> 01:35:02,620
We're just stewards, right?

1242
01:35:02,620 --> 01:35:10,240
And if 60% of our users say we want to use iOS mail, you know, my first response might be, it's not that great.

1243
01:35:11,100 --> 01:35:12,220
But the next one kind of has to be.

1244
01:35:12,380 --> 01:35:15,260
But in matters of taste, the customer is always right.

1245
01:35:16,020 --> 01:35:18,120
So we even offer POP.

1246
01:35:18,500 --> 01:35:21,420
And pop is the terrible, terrible thing that came before IMAP.

1247
01:35:21,490 --> 01:35:23,040
And I dislike it immensely.

1248
01:35:23,500 --> 01:35:25,280
But people use it.

1249
01:35:25,370 --> 01:35:27,420
And people really want to keep using it.

1250
01:35:27,430 --> 01:35:28,560
And so we permit it.

1251
01:35:28,760 --> 01:35:32,700
What I would like is not that someday we take away IMAP from people.

1252
01:35:32,960 --> 01:35:35,620
It's that someday everybody says IMAP can go now.

1253
01:35:36,250 --> 01:35:37,540
And nobody still wants it.

1254
01:35:38,260 --> 01:35:38,500
Got it.

1255
01:35:38,970 --> 01:35:39,740
I forgot to ask.

1256
01:35:40,200 --> 01:35:44,660
Is the reason why FastMail is called FastMail predominantly because of JMAP?

1257
01:35:45,380 --> 01:35:47,240
Is that where the speed benefit is found?

1258
01:35:48,220 --> 01:35:50,340
Okay, well, okay, so there's two questions there.

1259
01:35:50,660 --> 01:35:54,380
One is, is the speed benefit from JMAP?

1260
01:35:54,730 --> 01:35:57,620
And the other one is, is it called FastMail because of JMAP?

1261
01:35:57,840 --> 01:36:00,120
FastMail was called FastMail way before JMAP existed.

1262
01:36:00,760 --> 01:36:05,680
In fact, FastMail was called FastMail before the precursor to JMAP existed.

1263
01:36:06,480 --> 01:36:08,320
And it was just called that because it was supposed to be fast.

1264
01:36:09,200 --> 01:36:13,620
And if you go back, gosh, I wonder if we published any of the really old screenshots.

1265
01:36:13,960 --> 01:36:18,600
If you go back and look at what FastMet looked like in 2002, it looks very 2002.

1266
01:36:19,700 --> 01:36:24,980
You know, it doesn't look a whole lot better than many other things that existed, but it

1267
01:36:25,120 --> 01:36:25,980
was very fast.

1268
01:36:26,660 --> 01:36:31,040
And it was doing all kinds of, I would say, nasty tricks to be fast.

1269
01:36:31,720 --> 01:36:34,280
And in 2002, the web was still kind of a baby.

1270
01:36:36,180 --> 01:36:38,640
And in fact, I think it went online in 99 or 2000.

1271
01:36:40,800 --> 01:36:42,680
And it was still in Australia, right?

1272
01:36:42,880 --> 01:36:45,860
So like it was there's still these questions about latency to the rest of the world.

1273
01:36:48,280 --> 01:36:53,360
In, you know, 10 years later, I'm going to say around 2014, 2013, 2014,

1274
01:36:55,520 --> 01:36:58,640
we introduced something internally called Ajax UI.

1275
01:36:59,560 --> 01:37:05,560
And Ajax UI shifted the entire client to live in the browser.

1276
01:37:06,360 --> 01:37:10,080
So previously, you know, you'd click on a message and it would tell the server,

1277
01:37:10,300 --> 01:37:13,960
I want to see this message, the server would render something and send it back to you and now you get a new page.

1278
01:37:14,840 --> 01:37:20,540
So kind of like a traditional web page where clicking on something, got a new rendered page.

1279
01:37:20,640 --> 01:37:21,940
A lot of things still work this way.

1280
01:37:22,120 --> 01:37:24,520
Anything written in PHP mostly works these days.

1281
01:37:27,160 --> 01:37:33,160
Ajax UI said, well, we're going to put an application running in the browser that can go ask the server for information,

1282
01:37:33,560 --> 01:37:38,780
add it to its local data storage, and then update the UI in real time using like a model view controller system.

1283
01:37:39,440 --> 01:37:41,960
And this was revolutionary.

1284
01:37:42,600 --> 01:37:45,100
It really changed how fast mail could work.

1285
01:37:45,700 --> 01:37:55,180
It let you be very, very fast by caching data, by updating the user interface as soon as the user clicked a button and before the server had finished responding.

1286
01:37:55,840 --> 01:37:59,400
So this really, I think, changed the kind of perceived speed.

1287
01:37:59,980 --> 01:38:05,220
It maybe didn't always change the actual speed because the server still had to actually delete the message you clicked delete on.

1288
01:38:05,720 --> 01:38:07,420
But you click delete, the message went away.

1289
01:38:07,550 --> 01:38:09,140
A little bit later, the server had deleted it.

1290
01:38:09,740 --> 01:38:16,740
huge. And then JMAP was us saying, this is really, really good, right? What if we made this available

1291
01:38:16,880 --> 01:38:20,860
for the rest of the world? We got to fix all the weird stuff that we did along the way. And then we

1292
01:38:20,950 --> 01:38:25,980
took it out to the mailing list to the public and had discussions about how to ship that.

1293
01:38:27,640 --> 01:38:33,300
Then the question is, is that why fast mail is so fast now? It's certainly a big part of it.

1294
01:38:34,380 --> 01:38:37,660
Part of it is because JMAP is designed to be very efficient, to be very fast.

1295
01:38:38,180 --> 01:38:40,940
Part of it is that it can hide some of the work.

1296
01:38:41,280 --> 01:38:43,500
So the work happens after you asked for the work.

1297
01:38:43,800 --> 01:38:46,440
We assume the work is going to be successful.

1298
01:38:47,160 --> 01:38:49,740
And if it's not, you know, you hit delete and the message comes back and you get an error.

1299
01:38:49,940 --> 01:38:50,780
Actually, I couldn't delete it.

1300
01:38:51,040 --> 01:38:52,100
But that almost never happens.

1301
01:38:52,320 --> 01:38:53,720
So it actually feels very, very fast.

1302
01:38:54,420 --> 01:38:57,680
But also, there's plenty of other work that we do to keep it fast.

1303
01:38:58,040 --> 01:39:04,780
Just before we started this call, I was working on a bug that when you rename your user,

1304
01:39:06,060 --> 01:39:09,240
sometimes your old sessions get one error and then start working.

1305
01:39:11,200 --> 01:39:13,380
And the bug's not that interesting to anybody but me.

1306
01:39:14,300 --> 01:39:16,300
But in fixing it, all of this is like,

1307
01:39:16,310 --> 01:39:19,420
well, how do I make sure all of that works without making the user wait?

1308
01:39:20,260 --> 01:39:22,600
You don't want to wait while your session is updated.

1309
01:39:23,140 --> 01:39:25,340
You want to get back to work and your session is updated

1310
01:39:25,430 --> 01:39:26,280
while you're doing other stuff.

1311
01:39:26,420 --> 01:39:27,480
J-Map has nothing to do with that.

1312
01:39:28,320 --> 01:39:29,600
But what we say here a lot is,

1313
01:39:30,400 --> 01:39:31,560
fast is right there in the name.

1314
01:39:31,610 --> 01:39:33,440
I think you said it in your video, right?

1315
01:39:33,440 --> 01:39:34,260
It's right there in the name.

1316
01:39:34,400 --> 01:39:35,580
It's really important to us.

1317
01:39:36,580 --> 01:39:39,500
Part of that fast is that when you click something, it happens right away.

1318
01:39:39,660 --> 01:39:44,400
And part of that fast is the whole interface is designed to let you get in, do your business, and get out.

1319
01:39:44,940 --> 01:39:48,140
And that requires constant attention at sort of every level of operation.

1320
01:39:48,800 --> 01:39:52,480
Yeah, and creative engineering, it sounds like, to not just do the...

1321
01:39:53,680 --> 01:40:00,700
It is almost hacky in a way, but not in a bad way where it's like instead of just, you know, clicking order of operations,

1322
01:40:00,800 --> 01:40:02,760
you're like, well, we can hide this from the user.

1323
01:40:03,080 --> 01:40:05,220
We can offload it so it's out of their site.

1324
01:40:06,240 --> 01:40:08,980
And I think that's a lot of creativity involved,

1325
01:40:09,380 --> 01:40:11,040
probably, in crafting those workflows.

1326
01:40:11,720 --> 01:40:12,040
Absolutely.

1327
01:40:12,240 --> 01:40:13,960
And engineering is quite good.

1328
01:40:15,160 --> 01:40:18,020
I would say it's not a hack in a bad sense.

1329
01:40:18,220 --> 01:40:21,340
I don't have anything against a crazy hack.

1330
01:40:21,480 --> 01:40:22,780
I perpetrate those regularly.

1331
01:40:23,460 --> 01:40:26,100
But the software implementation is quite good.

1332
01:40:26,100 --> 01:40:27,180
It's quite easy to work with,

1333
01:40:27,300 --> 01:40:29,020
and it hides the complexity in a good way.

1334
01:40:29,380 --> 01:40:36,640
The other thing, it's a fun fact while we're on the topic, something else I was dealing with this week, we have this offline support now, and I described it earlier.

1335
01:40:36,780 --> 01:40:38,140
You've got your data cached in your browser.

1336
01:40:38,640 --> 01:40:47,700
We've reached a point where if you are in Australia, having an offline cache or in your browser cache for all your data, huge win.

1337
01:40:47,800 --> 01:40:48,900
Your mail is so much faster.

1338
01:40:49,700 --> 01:40:52,480
Here in the U.S., it's not always clear.

1339
01:40:52,960 --> 01:40:59,720
Sometimes it is faster to go ask the incredibly beefy server to do some work for you and get the answer.

1340
01:40:59,950 --> 01:41:06,360
A full round trip, you know, several hundred miles or however far it's going to go, than it is to let your browser do the work.

1341
01:41:06,860 --> 01:41:11,260
Because your laptop and especially the browser storage APIs are so inefficient.

1342
01:41:11,960 --> 01:41:20,300
So, like, now we've got to think about things like how do we decide where to send the work, which is a great example of the choices being made between convenience and privacy.

1343
01:41:21,280 --> 01:41:29,020
Yeah. Yeah, that's interesting. And I assume, is that something that's user customizable? Can a person say, I want to only do offline?

1344
01:41:29,840 --> 01:41:40,580
Yes, you can't say only offline. Right now, if you say you want offline, I think it always works through the proxy. I guess I'd have to go look at some actual, it's complicated.

1345
01:41:40,920 --> 01:41:45,900
But generally, if you say, I want offline support, your requests channel through your local proxy.

1346
01:41:46,400 --> 01:41:52,660
But if it can't find the data it needs or just to update, it will pull in data from the server.

1347
01:41:53,060 --> 01:41:59,240
But it will not at present say, I've determined that you're so close to the server, I'm not going to use your cache and go directly.

1348
01:41:59,300 --> 01:42:00,220
It can't really work that way.

1349
01:42:01,020 --> 01:42:01,120
Okay.

1350
01:42:02,420 --> 01:42:04,460
Yeah, so, you know, who's FastMail for?

1351
01:42:04,600 --> 01:42:07,860
What's your kind of ideal avatar to kind of wrap things up?

1352
01:42:08,160 --> 01:42:11,420
And what are you guys planning for the future that you're able to share?

1353
01:42:12,140 --> 01:42:12,260
Yeah.

1354
01:42:14,240 --> 01:42:17,380
Every once in a while, we talk about who our user is, and we've got a bunch of different

1355
01:42:17,620 --> 01:42:17,960
archetypes.

1356
01:42:19,100 --> 01:42:24,780
And I think what I'll say, when I think about who is using Fastmail, I try to imagine this

1357
01:42:24,860 --> 01:42:30,060
sort of very simple baseline of someone who cares a little bit about their email.

1358
01:42:30,880 --> 01:42:35,620
Now, I care a lot about email in general and my email specifically, and I have a lot of

1359
01:42:35,640 --> 01:42:42,800
customization, a lot of rules, and I want people to have that available. But I just want, I think

1360
01:42:42,800 --> 01:42:48,200
that we look at targeting people who kind of at least care a little bit, right? Someone who says,

1361
01:42:48,680 --> 01:42:53,280
my email is important, either because if I don't pay attention to it, it becomes a drag,

1362
01:42:53,860 --> 01:43:05,600
or because I leverage my email for like, getting stuff done efficiently through my day. And

1363
01:43:05,620 --> 01:43:08,260
what next level of features those people need.

1364
01:43:08,640 --> 01:43:09,520
They tend to tell us.

1365
01:43:09,760 --> 01:43:10,880
And then, you know, we'll get,

1366
01:43:11,560 --> 01:43:12,840
people tell us their 50 big problems.

1367
01:43:13,020 --> 01:43:14,540
And we're like, well, which of these problems,

1368
01:43:14,900 --> 01:43:17,120
can we solve 26 of these problems with one feature?

1369
01:43:17,700 --> 01:43:18,260
Right, and then it's like,

1370
01:43:18,360 --> 01:43:19,380
now we know what we wanna build next.

1371
01:43:21,620 --> 01:43:23,660
I imagine that the product team

1372
01:43:23,820 --> 01:43:26,380
has some more clear ideas about this,

1373
01:43:26,520 --> 01:43:27,580
but they keep me away from the product

1374
01:43:27,640 --> 01:43:28,600
'cause I use them up for so long.

1375
01:43:29,780 --> 01:43:30,760
Things we're doing next.

1376
01:43:30,880 --> 01:43:32,500
Well, I'll be super short about the things

1377
01:43:32,500 --> 01:43:34,720
that excite me the most, which are open standards work.

1378
01:43:35,280 --> 01:43:41,600
we're working on polishing up the final forms of JMAP for calendars and JMAP for contacts.

1379
01:43:42,400 --> 01:43:47,100
We've offered calendars and contacts over JMAP for quite a while now, but only to our web client.

1380
01:43:47,220 --> 01:43:50,920
You couldn't write your own client with them because they've still gone through a standardization process.

1381
01:43:51,580 --> 01:43:53,960
That's done. The standards are largely done and dusted.

1382
01:43:54,360 --> 01:43:58,040
So now we're getting all the rough edges of our implementation polished off,

1383
01:43:58,460 --> 01:44:03,420
which means soon someone could write a JMAP calendar client or a JMAP address book client.

1384
01:44:03,740 --> 01:44:05,300
And that'll be, I am excited about that.

1385
01:44:05,990 --> 01:44:09,160
The number of users who are probably excited about that, I'm guessing, is under 100.

1386
01:44:12,060 --> 01:44:17,400
Another actually bit of standards work that I am very excited about is we have been working

1387
01:44:18,060 --> 01:44:23,520
with some people in the ITF, the OAuth group, and the email group on automatic configuration

1388
01:44:24,140 --> 01:44:26,380
and a simplified OAuth profile.

1389
01:44:26,810 --> 01:44:33,700
What that really means is if you get a mail client that supports these standards, and you

1390
01:44:33,720 --> 01:44:36,300
type in, you know, henry@fisher.biz,

1391
01:44:37,080 --> 01:44:39,660
it will just say, great, here's OAuth.

1392
01:44:40,000 --> 01:44:41,260
It'll just give you a web browser

1393
01:44:41,400 --> 01:44:42,560
for whoever provides your email.

1394
01:44:43,100 --> 01:44:44,980
You don't need to type in an IMAP server name.

1395
01:44:45,320 --> 01:44:47,580
You don't need to select, oh, I'm using Google

1396
01:44:47,940 --> 01:44:48,980
from the little dropdown, you know,

1397
01:44:49,040 --> 01:44:50,180
little list of providers.

1398
01:44:51,020 --> 01:44:52,660
It just makes everything work.

1399
01:44:52,980 --> 01:44:55,460
And then you OAuth and everything happens.

1400
01:44:56,060 --> 01:44:57,380
This is huge.

1401
01:44:57,840 --> 01:44:59,740
The amount of time that support agents,

1402
01:44:59,860 --> 01:45:01,480
not just at FastMail, but everywhere,

1403
01:45:02,000 --> 01:45:07,220
support agents spend on client configuration issues is enormous. And if that goes away,

1404
01:45:07,800 --> 01:45:12,680
because it's replaced by a simple standard that everybody implements, all those support agents are

1405
01:45:13,140 --> 01:45:17,240
available for all the other issues, the response time goes way up and everybody feels like,

1406
01:45:17,700 --> 01:45:22,260
man, the support of FastMail is so great, or the support of everywhere else. So I'm really excited

1407
01:45:22,260 --> 01:45:25,440
about that. It's going to be good for the users. And we talked earlier about Teams work, which is

1408
01:45:25,460 --> 01:45:32,520
hopefully going to be happening at some point not too long yeah um that's all really exciting stuff

1409
01:45:32,800 --> 01:45:41,920
and i hope to be using fastmail more on my end to play out some of these things um yeah yeah and um

1410
01:45:42,320 --> 01:45:47,820
and i i don't know i i'm tempted because i just know that i would enjoy the experience of using

1411
01:45:48,060 --> 01:45:54,900
fastmail better and i don't think that's very debatable um if you if you give it a go and you

1412
01:45:54,920 --> 01:46:01,460
hit weird things or want advice, you know, drop me a line. I love talking about how email, how I do

1413
01:46:01,510 --> 01:46:05,940
my email. Most of the time, it's not a conversation people want to have, but if you're playing around

1414
01:46:06,100 --> 01:46:11,360
with it, I'm sitting here. I mean, we got people on here for well over an hour talking about email,

1415
01:46:11,600 --> 01:46:18,760
so I think there's a lot, and the passion is there through the screen, and I know you've taught me a

1416
01:46:18,860 --> 01:46:22,780
lot about email, and I hope that you've taught others as well here about email and something

1417
01:46:22,800 --> 01:46:29,860
that. Where can people find you and or Fastmail if they want to connect with you guys online?

1418
01:46:30,420 --> 01:46:37,140
Yeah, well, fastmail.com is us on the web. I think our webpage is pretty good. It lists our

1419
01:46:37,380 --> 01:46:41,520
values pretty prominently, which I said was to me a big selling point. It runs you through the

1420
01:46:41,720 --> 01:46:48,039
product. And trying a free trial is a great way to see what you think about it. And we have a really

1421
01:46:48,060 --> 01:46:56,460
good import tool. So my suggestion for people is sign up, make a free trial, use the import tool

1422
01:46:56,550 --> 01:47:00,760
to bring your mail in, and just see what it would be like to have your mail in there. And if you

1423
01:47:00,880 --> 01:47:04,220
don't convert the trial, we scrub all the data, we throw it away. I don't want your email on our

1424
01:47:04,400 --> 01:47:08,060
server if you're not giving us money. I want to get that the heck off of there as soon as possible.

1425
01:47:10,660 --> 01:47:15,580
And in our blog, you will hopefully be seeing some of the exciting stuff that I was saying was

1426
01:47:15,600 --> 01:47:19,980
going to be coming uh we've posted some technical stuff we post some stuff about the standards we

1427
01:47:20,120 --> 01:47:25,360
work on and we post about the new features um i mean that's about it i'm i'm on mastodon but i

1428
01:47:25,500 --> 01:47:29,760
mostly just post nonsense about borderlands like i'm not really talking about email too much there

1429
01:47:30,300 --> 01:47:36,920
yeah yeah it's kind of like my mastodon account too um yeah it's it feels nice it's very it's as

1430
01:47:37,230 --> 01:47:43,080
quiet and as popular as it needs to be right now i think and i hope it stays that way at least that's

1431
01:47:43,100 --> 01:47:48,620
my experience of Mastodon. But yeah, that's all I have on my end. So I want to thank you,

1432
01:47:48,720 --> 01:47:53,840
Ricardo, for being here and sharing so much good knowledge. And of course, you can find all the

1433
01:47:53,880 --> 01:47:58,480
links that you share down in the description. Great. Well, yeah, thanks for having me. I had

1434
01:47:59,080 --> 01:48:03,760
a great time. I got to talk about JMAP and email, so always a good day for me. Great. I want to give

1435
01:48:03,800 --> 01:48:09,780
a massive thanks to Ricardo for taking almost two hours of his time to do this interview. And I want

1436
01:48:09,800 --> 01:48:13,760
to thank, of course, you all for watching and learning hopefully something new about not just

1437
01:48:13,980 --> 01:48:18,280
FastMail, but email as a whole and kind of what is the future of email and also the different

1438
01:48:18,880 --> 01:48:24,560
legitimate approaches to email privacy. I am not a FastMail customer or a user, but I still got a

1439
01:48:24,660 --> 01:48:28,840
lot of value talking to them, and it's super great to learn about the different approaches that

1440
01:48:29,140 --> 01:48:33,060
companies are taking when it comes to this stuff. And if you do want to watch a more thorough deep

1441
01:48:33,280 --> 01:48:38,120
dive, we made a whole video that compares FastMail to Tudor to Proton, which I believe Ricardo

1442
01:48:38,140 --> 01:48:44,240
overall likes. So I don't think that's too out there to recommend as a next step if you do want

1443
01:48:44,240 --> 01:48:48,240
to learn how FastMail compares to something like Proton and Tudup. Teaser, if you use any of the

1444
01:48:48,400 --> 01:48:51,480
three, you're still better off than if you're using Gmail or Yahoo or something like this.

1445
01:48:51,740 --> 01:48:54,600
So check those out, and I'll see you guys next time on TechLore.