1
00:00:00,020 --> 00:00:03,200
You can't shut down a peer-to-peer network because when you try to shut down a peer-to-peer

2
00:00:03,280 --> 00:00:05,920
network, it's kind of like this whack-a-mole where you can, you know, you can spend a lot

3
00:00:05,920 --> 00:00:07,560
of time to shut down one node.

4
00:00:09,100 --> 00:00:09,460
Hello, everybody.

5
00:00:09,720 --> 00:00:13,480
Today, I have the honor of bringing on Matias, who's the CEO of Holepunch.

6
00:00:14,080 --> 00:00:16,940
They develop a ton of different peer-to-peer technologies, P2P.

7
00:00:17,160 --> 00:00:17,800
Many of you know this.

8
00:00:18,060 --> 00:00:20,520
It's essentially the concept of you connecting to other people.

9
00:00:20,920 --> 00:00:25,380
He explains the principles of P2P, benefits for people like you, and the importance of

10
00:00:25,600 --> 00:00:27,880
privacy and security in light of everything happening in the world.

11
00:00:28,120 --> 00:00:29,840
Matias also shares a little bit about himself.

12
00:00:29,920 --> 00:00:34,560
challenges of building peer-to-peer messengers, and the role of open source in fostering innovation.

13
00:00:34,810 --> 00:00:37,120
Without further ado, let's dive into the interview.

14
00:00:37,580 --> 00:00:40,280
Hello, Mathias. Welcome to the Techlore Talks podcast.

15
00:00:41,280 --> 00:00:44,280
I'd love if you just said a few things about yourself to get started.

16
00:00:45,140 --> 00:00:47,440
Yeah. Hey, thanks for having me. Of course.

17
00:00:48,280 --> 00:00:52,740
So I'm Mathias. I'm the CEO at Holepunch, which is a peer-to-peer company.

18
00:00:52,890 --> 00:00:55,280
We work on exclusively peer-to-peer technology.

19
00:00:55,340 --> 00:01:00,820
And if anybody who has ever heard me before know that I like to say the word peer-to-peer.

20
00:01:01,480 --> 00:01:05,480
I've been working with peer-to-peer my entire career and throughout my open source career.

21
00:01:06,680 --> 00:01:16,860
And I'm a very, very big believer in changing the status quo and how we distribute and share data and build systems online.

22
00:01:17,010 --> 00:01:20,420
So I'm really, really excited to be here and get to talk about this kind of stuff a lot.

23
00:01:21,720 --> 00:01:25,160
Yeah, Nen, I want to talk a little bit more about your history in a second.

24
00:01:25,440 --> 00:01:38,520
But if somebody's new here and they want to learn, they never heard of peer-to-peer before, do you mind breaking down peer-to-peer very simply for them, as well as how that compares to maybe a traditional technology that most people interact with?

25
00:01:39,340 --> 00:01:42,980
Yeah, sure. It's interesting, right? Because it's two words and a number.

26
00:01:43,330 --> 00:01:46,260
So those two words are the same. So peer-to-peer.

27
00:01:46,920 --> 00:01:51,100
Actually, I'm Danish, and we actually had a discussion recently

28
00:01:51,180 --> 00:01:53,160
what the translation of peer is,

29
00:01:53,200 --> 00:01:55,200
which is a really interesting question, I think, in general,

30
00:01:55,400 --> 00:01:58,240
because it's a word that has a bunch of different connotations.

31
00:01:58,400 --> 00:02:02,840
But basically, it's systems and apps where there's no servers,

32
00:02:03,560 --> 00:02:05,300
so you don't have any infrastructure anywhere

33
00:02:05,440 --> 00:02:06,360
or running somewhere else.

34
00:02:06,360 --> 00:02:08,979
It's just devices, and you use the devices to build networks.

35
00:02:10,840 --> 00:02:13,200
That's the peer, so everybody is kind of like the same in a network

36
00:02:13,560 --> 00:02:16,320
and have the same kind of capability as everybody else.

37
00:02:16,760 --> 00:02:20,660
And you then solve through technology the problems that arise from that,

38
00:02:20,800 --> 00:02:22,900
like security, authenticity, and stuff like that.

39
00:02:23,320 --> 00:02:25,420
But by doing that with technology, you end up building these really,

40
00:02:25,510 --> 00:02:27,780
really resilient and powerful networks that are also very,

41
00:02:27,940 --> 00:02:29,820
very cost-efficient because you just have the devices

42
00:02:30,180 --> 00:02:31,220
and scale it very naturally.

43
00:02:32,280 --> 00:02:35,160
And it's also one of those things where you can hear when I talk about it,

44
00:02:35,160 --> 00:02:37,460
I'm a technical person, I love talking about tech.

45
00:02:37,510 --> 00:02:40,020
It sounds a little bit technical, but a lot of people are actually exposed

46
00:02:40,100 --> 00:02:40,860
to peer-to-peer a lot.

47
00:02:42,660 --> 00:02:44,760
In the past, probably through things like BitTorrent,

48
00:02:44,840 --> 00:02:45,480
if they ever tried that.

49
00:02:45,530 --> 00:02:47,320
That was very, very big in the early 2000s,

50
00:02:47,370 --> 00:02:49,260
which was the peer-to-peer network to distribute media.

51
00:02:49,560 --> 00:02:51,640
It still is, but was very big back then.

52
00:02:52,340 --> 00:02:55,280
And also there's been like various apps

53
00:02:55,940 --> 00:02:57,080
that's been using peer-to-peer over time

54
00:02:57,150 --> 00:02:58,600
to do different things like, you know,

55
00:02:59,120 --> 00:03:01,440
multiplayer games back in the day used to do it a lot

56
00:03:02,520 --> 00:03:03,080
and things like that.

57
00:03:04,340 --> 00:03:05,400
And so it's technology.

58
00:03:05,620 --> 00:03:06,620
Basically, we build networks

59
00:03:07,250 --> 00:03:09,620
where everybody has the same capabilities up here.

60
00:03:10,680 --> 00:03:12,140
And yes, it's super cool.

61
00:03:12,360 --> 00:03:15,180
And it's a really, really powerful thing.

62
00:03:16,040 --> 00:03:16,360
Yeah.

63
00:03:16,420 --> 00:03:17,800
And what's the core benefit?

64
00:03:18,300 --> 00:03:25,220
If somebody is listening to this and they just use regular technology, they don't think they're using Peterpeer, even though they probably are at some point or another.

65
00:03:25,420 --> 00:03:27,400
And maybe you can touch on some of those scenarios.

66
00:03:27,860 --> 00:03:29,980
But what is the real benefit there for a regular person?

67
00:03:30,520 --> 00:03:36,260
It's almost like when you use existing apps online, especially today, like what's the real disadvantages of those apps?

68
00:03:36,360 --> 00:03:38,060
There's always these things they don't tell you.

69
00:03:38,240 --> 00:03:42,740
Because when you use existing apps, there's a lot of infrastructure behind the scenes, especially that has to be paid.

70
00:03:42,970 --> 00:03:47,640
You know, when you're using apps where you upload images or things like that, who's paying for that?

71
00:03:47,720 --> 00:03:48,460
Who's storing it?

72
00:03:48,760 --> 00:03:51,740
What's the incentive for those guys making that app for you outside?

73
00:03:52,120 --> 00:03:53,760
You're just using it when you're using it for free.

74
00:03:54,170 --> 00:04:00,980
You know, people always say, you know, because you're the product, people are trying to like data mine you to make ads and stuff like that and read you data.

75
00:04:01,540 --> 00:04:09,220
So the real benefit is that in P2P networks, you don't have that because you don't have any like behind the scenes actor other than obviously there's a developer making an app.

76
00:04:09,280 --> 00:04:10,300
But like there's no infrastructure.

77
00:04:10,480 --> 00:04:12,200
It's just these self-regulating networks.

78
00:04:13,080 --> 00:04:15,240
So there's basically nothing hidden in that way.

79
00:04:15,440 --> 00:04:17,799
It's just natural networks that solve things.

80
00:04:17,880 --> 00:04:21,260
So you can actually have a much more private and forever free experience.

81
00:04:21,780 --> 00:04:28,100
So, again, if you look at something like BitTorrent, which I'm sure somebody has heard about before, that was a network when it was at the biggest.

82
00:04:28,280 --> 00:04:31,200
I don't know how big it is now, but at the biggest had like 30,

83
00:04:31,600 --> 00:04:34,280
40 million nodes in the network, like a P2P network that was massive.

84
00:04:35,260 --> 00:04:39,820
Imagine 40 million computers connected in a network that's like an insane

85
00:04:40,060 --> 00:04:42,580
amount that's probably bigger than the biggest data set out there.

86
00:04:43,080 --> 00:04:45,160
Everybody's sharing, giving a little bit of capacity to that network,

87
00:04:45,260 --> 00:04:47,180
which means that the total capacity is really, really big.

88
00:04:47,880 --> 00:04:51,580
And that's why these networks can keep existing and keep serving you.

89
00:04:51,800 --> 00:04:57,020
And it gives you this benefit of basically, like I said,

90
00:04:57,120 --> 00:05:00,740
no hidden stuff so like nobody's like doing surveillance behind the scenes or trying to

91
00:05:00,830 --> 00:05:05,060
data mine your data is your data is true you can kind of like make up your own rules at my company

92
00:05:05,090 --> 00:05:09,100
we make a chat app p2p is really good for that because then we can have like these unregulated

93
00:05:09,240 --> 00:05:14,160
conversations between each other where it's just between us and nobody else and not having to to

94
00:05:14,270 --> 00:05:19,160
worry about things like you know people you know that feeling when you're you know writing messages

95
00:05:19,320 --> 00:05:23,800
on whatsapp and you're talking about fridges and all of a sudden you get ads from fridges and stuff

96
00:05:23,920 --> 00:05:27,080
like that you don't need to worry about that in p2p networks because it's just actually truly

97
00:05:27,100 --> 00:05:31,700
it and stuff like that. So it's a really, really powerful thing and it's also been around for a

98
00:05:31,700 --> 00:05:37,540
while. But also it can be a little bit technical, I guess, which is why a lot of people can be a

99
00:05:37,550 --> 00:05:41,260
little bit confused by it. When did you get started with peer-to-peer technologies and how did that

100
00:05:41,480 --> 00:05:46,280
lead to where you guys are today? I tell the story a lot, which is like one of those very true stories

101
00:05:46,500 --> 00:05:53,560
that just affected my life a lot. So I actually started programming, so I'm a programmer now and

102
00:05:53,580 --> 00:05:57,940
And I started programming in my career, I guess, relatively late.

103
00:05:58,040 --> 00:06:02,860
I only started when I was at university because we had to do mandatory programming.

104
00:06:03,180 --> 00:06:07,400
I was studying math and they didn't want us to come out and be unemployed afterwards.

105
00:06:07,700 --> 00:06:10,460
So they were like, we need to do some real things also.

106
00:06:10,700 --> 00:06:14,200
And as part of that, I had to take a course in computer science.

107
00:06:15,180 --> 00:06:22,080
And that was very, very interesting to me because it unlocked this thing inside me that I think is very, very excited about computers in general,

108
00:06:22,220 --> 00:06:27,700
which is kind of like this extension of yourself as a person who wants to do things in your career,

109
00:06:28,130 --> 00:06:28,840
like entrepreneurship.

110
00:06:29,310 --> 00:06:31,880
All of a sudden you have a computer and now you can produce much more

111
00:06:31,930 --> 00:06:34,880
and you can make things open source and you can put them online

112
00:06:34,930 --> 00:06:38,260
and you have this like just real sense of the power of one.

113
00:06:39,140 --> 00:06:42,380
And that was really, really exciting for me as a young person

114
00:06:42,450 --> 00:06:44,860
that you can kind of like just be like, oh, the faster I work,

115
00:06:44,870 --> 00:06:47,360
the faster I can build things and the more impact I can do in the world.

116
00:06:47,700 --> 00:06:48,480
I don't need anybody else.

117
00:06:48,570 --> 00:06:49,840
I just have everything that I need.

118
00:06:50,660 --> 00:06:54,960
And I stopped feeling that a little bit when I learned about networking and deployment,

119
00:06:55,220 --> 00:06:59,460
because all of a sudden you had all these things where, sure, it was just me and my computer,

120
00:06:59,620 --> 00:07:05,080
but I had all this other stuff also going on where I had to buy servers or rent servers back then

121
00:07:05,620 --> 00:07:09,580
and get my credit card out and kind of stifled my development here.

122
00:07:09,660 --> 00:07:11,840
And you would make services online.

123
00:07:12,580 --> 00:07:14,120
I used to do that, made a couple of startups.

124
00:07:15,100 --> 00:07:17,180
And as they gained traction, they get more expensive to run.

125
00:07:17,240 --> 00:07:20,220
And then you would need to upfront think about business models to kind of cover that cost.

126
00:07:20,340 --> 00:07:22,640
just turned into a whole different creative system, I think.

127
00:07:22,680 --> 00:07:23,320
That was interesting.

128
00:07:23,580 --> 00:07:28,220
So as part of that, I started dabbling a little bit more with peer-to-peer.

129
00:07:28,740 --> 00:07:31,220
Because, again, back then, BitTorrent was really, really popular,

130
00:07:31,300 --> 00:07:32,140
so everybody knew about that.

131
00:07:32,200 --> 00:07:34,260
And I started reading about how that worked.

132
00:07:34,540 --> 00:07:38,720
And actually, as a programmer, started re-implementing a BitTorrent client,

133
00:07:38,840 --> 00:07:39,640
which was really fun.

134
00:07:39,860 --> 00:07:42,360
It actually unlocked that sense again in me where, like,

135
00:07:42,520 --> 00:07:44,360
oh, now I have this network, I made this software.

136
00:07:45,840 --> 00:07:48,160
And I can just distribute the software to people,

137
00:07:48,280 --> 00:07:49,440
and they can just run it.

138
00:07:50,090 --> 00:07:52,500
And we're all part of this bigger network,

139
00:07:52,740 --> 00:07:53,980
but nobody's really running it.

140
00:07:53,990 --> 00:07:54,660
So it's kind of like this.

141
00:07:54,790 --> 00:07:56,220
Every time I write a piece of code,

142
00:07:56,590 --> 00:07:57,960
that kind of unlocks more potential

143
00:07:58,050 --> 00:07:59,200
and more potential and more potential.

144
00:08:00,080 --> 00:08:03,420
And if it goes rival tomorrow, it's fine.

145
00:08:03,520 --> 00:08:04,580
It's going to scale really well.

146
00:08:05,100 --> 00:08:06,480
If somebody tries to shut it down

147
00:08:06,590 --> 00:08:07,380
because they don't like it,

148
00:08:07,720 --> 00:08:08,680
they're going to have a really hard time.

149
00:08:08,690 --> 00:08:10,100
So that also unlocks this power in you.

150
00:08:10,740 --> 00:08:13,740
So I basically unlocked that basically

151
00:08:13,920 --> 00:08:14,660
in a weekend, that feeling.

152
00:08:14,790 --> 00:08:16,940
And I didn't stop because I was like,

153
00:08:16,940 --> 00:08:18,240
wow, this is it.

154
00:08:18,260 --> 00:08:22,480
this is how things should be built because this is just so powerful as an individual, especially,

155
00:08:23,660 --> 00:08:27,680
that I've just been working on it ever since. This is now 10, 15 years ago, right? And I'm

156
00:08:27,820 --> 00:08:32,659
still dabbling it down. And obviously there's like a lot of things in between there and now,

157
00:08:32,760 --> 00:08:38,580
but that's the main thing. So I think it's really, really powerful for anybody who's

158
00:08:38,719 --> 00:08:42,580
interested in technology and like open source movements and things like that.

159
00:08:43,979 --> 00:08:47,020
Yeah. So you've brought up BitTorrent a lot. And I think the regular person,

160
00:08:47,280 --> 00:08:52,140
if they hear BitTorrent, maybe, especially if they've never used it before, kind of the common

161
00:08:52,360 --> 00:08:59,020
associations is it's illegal, it's not good, and also it's unregulated. I think people actually

162
00:08:59,940 --> 00:09:05,600
enjoy some of the perceived safety of having a company that they can trust to handle their data.

163
00:09:05,960 --> 00:09:10,100
So do you mind commenting on a bit of that association with peer-to-peer tech, as well as

164
00:09:10,520 --> 00:09:14,179
is it actually, like what's stopping someone from joining this network and doing something

165
00:09:14,200 --> 00:09:15,040
malicious on the network.

166
00:09:15,520 --> 00:09:18,120
That's also, I think that's some really good points in general.

167
00:09:19,600 --> 00:09:24,580
I think, so, you know, like I said, BitTorrent, I said BitTorrent a lot because I grew up with

168
00:09:24,680 --> 00:09:27,560
that and it was very big back then and also like a big technical inspiration.

169
00:09:27,970 --> 00:09:31,960
But BitTorrent was like a network where you made a peer-to-peer system that could be used

170
00:09:31,970 --> 00:09:32,520
to share media.

171
00:09:33,560 --> 00:09:38,460
And in the early 2000s, like for 10 years around that time, before these big streaming

172
00:09:38,640 --> 00:09:42,260
services we have today, this was a very popular way of sharing content.

173
00:09:42,420 --> 00:09:45,980
And obviously a lot of that content, I think, had copyright issues and stuff like that.

174
00:09:46,040 --> 00:09:48,660
A lot of people got in a lot of trouble for that back then.

175
00:09:49,400 --> 00:09:56,560
But one thing it really showed was that you can make technology where if there's a demand in the market.

176
00:09:57,300 --> 00:10:04,360
So back then there was no other way of, if you're in a small country like in Denmark or in many places in Europe or even I'm sure in the U.S. places,

177
00:10:04,490 --> 00:10:08,240
it was actually just really hard to get a lot of content, even if you wanted to pay for it.

178
00:10:08,490 --> 00:10:10,840
So there was a real market for like digital.

179
00:10:11,040 --> 00:10:12,480
That's still an issue nowadays.

180
00:10:12,740 --> 00:10:17,680
You know, Adobe, if you bought the lifetime license to an old Adobe product,

181
00:10:17,820 --> 00:10:19,640
they still remove the download links from their website.

182
00:10:19,860 --> 00:10:23,260
So the only way to download that software is to get things like BitTor.

183
00:10:24,500 --> 00:10:25,460
Yeah, just side note.

184
00:10:26,980 --> 00:10:32,220
So it's technically like a never-ending license, but you can't get it.

185
00:10:32,360 --> 00:10:33,640
That's classic.

186
00:10:35,600 --> 00:10:51,140
So, yeah, and also like I moved recently to Switzerland from Denmark and also here there's also a small country and then they limit what kind of like translations you can get and like subtitles because they think everybody speaks Italian in my region and stuff like that.

187
00:10:51,740 --> 00:10:57,460
So, I don't know, it's like there's a lot of really, really weird choices in content distribution in general that we can talk a lot about.

188
00:10:57,580 --> 00:11:03,140
But basically like back then it was even harder and there was a real demand in the market, right?

189
00:11:03,180 --> 00:11:12,080
And the thing that stepped up to fill that demand because companies weren't doing it, probably just a lot of reasons, were self-made products like BitTorrent.

190
00:11:12,280 --> 00:11:14,320
So, you know, products where you could just share these things.

191
00:11:14,660 --> 00:11:16,560
Obviously, there was a lot of legal issues with that.

192
00:11:16,860 --> 00:11:18,240
And they got very, very big.

193
00:11:18,660 --> 00:11:26,620
And they got the industry, media industry, got extremely scared because they're like, oh, they only saw the negative part of that, which, you know, I can to some degree understand.

194
00:11:26,900 --> 00:11:29,080
Like you're just seeing a lot of content being distributed for free.

195
00:11:29,420 --> 00:11:29,660
Fair enough.

196
00:11:29,760 --> 00:11:30,280
That's very scary.

197
00:11:30,620 --> 00:11:31,940
They could see their livelihood going away.

198
00:11:32,140 --> 00:11:32,200
Right.

199
00:11:32,340 --> 00:11:35,260
So they tried really, really hard back then to shut it down the network.

200
00:11:35,840 --> 00:11:40,460
And they realized over time that you can't shut down a P2P network.

201
00:11:40,650 --> 00:11:42,240
So they went on different strategies.

202
00:11:43,400 --> 00:11:49,200
Because when you try to shut down a P2P network, it's kind of like this whack-a-mole where you can spend a lot of time to shut down one node.

203
00:11:50,060 --> 00:11:53,260
But then another node pops up and shut down and then two other nodes pop up.

204
00:11:53,270 --> 00:11:54,660
And it's just basically impossible.

205
00:11:55,210 --> 00:11:59,880
Just when you hear those numbers, like 20, 30, 40 million nodes and everything is a process.

206
00:12:00,100 --> 00:12:01,300
It's basically impossible.

207
00:12:01,840 --> 00:12:11,720
The reason why BitTorrent then went down a little bit since then is because we got other alternatives today, like Netflix and things like that, to kind of help solve that demand in the market.

208
00:12:11,970 --> 00:12:19,640
And now they have a lot of the same issues, like we just discussed, like fragmentation and content not being available and being removed and stuff like that.

209
00:12:19,650 --> 00:12:21,360
So I'm sure it's going to go like this.

210
00:12:21,920 --> 00:12:28,040
But from a technical point of view, like peer-to-peer was the way to show that we can just do this without waiting for people.

211
00:12:28,100 --> 00:12:33,240
We can just do this with networks where we don't have to bear like insane amount of content costs to distribute things.

212
00:12:33,460 --> 00:12:36,980
Like there's no like one person who pays a bill and stuff.

213
00:12:37,160 --> 00:12:38,960
So really, really interesting, really, really powerful.

214
00:12:39,840 --> 00:12:46,240
Obviously, with this kind of like unregulation, like you said, there's also interesting things that happens because you can just share whatever you want, right?

215
00:12:46,520 --> 00:12:48,800
This was like in the Wild West period of the internet.

216
00:12:49,000 --> 00:12:51,880
but there's also a lot of people who just got bad copies of movies

217
00:12:51,990 --> 00:12:53,580
and stuff like that, I'm sure, and things like that.

218
00:12:53,720 --> 00:12:57,840
So definitely there's definitely not just a technological solution

219
00:12:57,910 --> 00:12:59,800
to something, and you still need to think about these other things

220
00:12:59,930 --> 00:13:00,500
also in these networks.

221
00:13:01,320 --> 00:13:04,100
But as with anything technology, you can always build something crazy

222
00:13:04,340 --> 00:13:06,420
and scary and bad, but you can also use the same technology

223
00:13:06,600 --> 00:13:11,580
to build powerful, simple apps to try to solve these things still

224
00:13:11,890 --> 00:13:14,680
because there's no reason why the technology can't be used for both.

225
00:13:15,240 --> 00:13:16,960
That's actually one of the things that I've been involved with

226
00:13:17,040 --> 00:13:17,560
my entire career.

227
00:13:17,800 --> 00:13:21,420
It's kind of like saying, what if we took the ideas that were so powerful in BitTorrent,

228
00:13:21,500 --> 00:13:24,420
but then try to not couple it too much to just kind of like to file sharing,

229
00:13:24,700 --> 00:13:28,360
but just kind of like say, these principles are clearly extremely powerful.

230
00:13:28,580 --> 00:13:32,240
How can we take these and make any kind of apps, any kind of content run with these ideas

231
00:13:32,930 --> 00:13:38,360
without just having to like disregard all the other things we know that are very needed for like app development?

232
00:13:38,480 --> 00:13:41,180
Like you said, like easy understanding of content.

233
00:13:41,290 --> 00:13:43,800
Like you don't want to search and have 50 versions of the same thing.

234
00:13:43,800 --> 00:13:45,380
You want to have some sort of ideas there.

235
00:13:45,760 --> 00:13:52,200
Some things do need some regulation if the app developers want, like, you know, kind of like in our chat app, we have a way for people to be moderators in chat rooms and stuff like that.

236
00:13:52,440 --> 00:13:56,580
You can make up your own rules, but like anybody can kind of like set up their own rules and stuff like that.

237
00:13:57,180 --> 00:14:03,600
But I kind of like still running on the principles of peer-to-peer so you can make these things, make them powerful and make them unstoppable.

238
00:14:04,180 --> 00:14:08,640
Nice. And yeah, I definitely want to touch on the Messenger and the other stuff that you guys are working on in a sec.

239
00:14:08,980 --> 00:14:12,820
But you've been bringing up some interesting stuff that I want to ask a little bit more about.

240
00:14:13,000 --> 00:14:16,100
So you mentioned the concept of not being able to easily shut it down.

241
00:14:16,190 --> 00:14:21,060
So can you comment a bit on censorship resistance of just P2P technologies in general?

242
00:14:21,860 --> 00:14:22,260
Yeah, sure.

243
00:14:22,520 --> 00:14:30,440
So it's basically like I'm sure there's some eloquent principle in this that I will find after this podcast and start quoting a lot.

244
00:14:30,450 --> 00:14:33,020
But it's this idea that, you know, everybody's the same, right?

245
00:14:33,090 --> 00:14:36,720
So it's kind of like this crowd mentality that's been working for humans for generations.

246
00:14:37,380 --> 00:14:44,140
Once you get to a critical mass of a movement, you can't shut down a movement because you can't, like, lock up everybody, basically, right, if you're being dramatic.

247
00:14:44,860 --> 00:14:50,440
So peer-to-peer really works in big networks because everybody's the same.

248
00:14:50,620 --> 00:14:54,440
There's literally no difference between nodes in a network when a peer-to-peer system is built correctly.

249
00:14:54,980 --> 00:14:59,880
Sure, some networks will be a little bit fatter, has more content than others, but the idea is the same, right?

250
00:15:01,040 --> 00:15:06,160
So it's completely unrealistic for once, just like by the law of numbers, once the networks get going.

251
00:15:07,660 --> 00:15:09,740
it becomes completely impossible to shut down.

252
00:15:11,199 --> 00:15:13,140
And again, if you look at stuff like Bitcoin,

253
00:15:13,260 --> 00:15:14,480
because it's just such a good case story.

254
00:15:14,720 --> 00:15:16,980
And actually, I'm surprised that not more has been written

255
00:15:17,180 --> 00:15:19,880
about just the implications of these networks,

256
00:15:20,120 --> 00:15:21,900
not so much in tech,

257
00:15:21,940 --> 00:15:23,800
but also just kind of like human behavior in these networks.

258
00:15:23,980 --> 00:15:24,980
Because I think it's very, very interesting.

259
00:15:25,900 --> 00:15:28,880
It's very interesting how also those networks

260
00:15:29,739 --> 00:15:31,380
from people who wanted to shut them down,

261
00:15:31,800 --> 00:15:33,020
that battle was fought.

262
00:15:33,240 --> 00:15:35,560
Because in the end, the thing that there was some success with,

263
00:15:35,780 --> 00:15:37,640
I think in BitTorrent, in terms of limiting these networks,

264
00:15:37,860 --> 00:15:41,100
was trying to attack the few centralized point of use on that.

265
00:15:41,270 --> 00:15:43,240
And I think that's actually very hard for normal people,

266
00:15:43,570 --> 00:15:44,800
like non-technical people, to understand.

267
00:15:46,020 --> 00:15:47,780
So in a network like BitTorrent,

268
00:15:48,980 --> 00:15:52,320
people were trying to find Torrent files back then through websites.

269
00:15:53,540 --> 00:15:56,380
And they would go to a website, they would find content there.

270
00:15:57,100 --> 00:16:00,780
And the way, in the end, that this war was also fought

271
00:16:00,790 --> 00:16:02,820
was trying to shut down those websites.

272
00:16:03,360 --> 00:16:05,100
A lot of times, very successfully,

273
00:16:05,240 --> 00:16:08,120
There's a lot of good documentaries around that with the pirate bay and things like that.

274
00:16:08,520 --> 00:16:12,600
By getting the websites delisted, and how are they getting delisted?

275
00:16:12,720 --> 00:16:16,300
By just attacking the centralized part of the internet, which is the DNS registry,

276
00:16:16,600 --> 00:16:18,700
like the thing that translates your name to a website.

277
00:16:19,640 --> 00:16:21,820
Because there you could just go with a normal process and be like,

278
00:16:21,870 --> 00:16:23,440
I don't want this website listed anymore.

279
00:16:23,640 --> 00:16:25,080
Here's a bunch of legal reasons why not.

280
00:16:25,190 --> 00:16:28,160
And then some legal process would say, yeah, that's correct.

281
00:16:28,300 --> 00:16:31,220
This is legally not okay or whatever, et cetera.

282
00:16:31,440 --> 00:16:36,960
And then users would go to that website and the browser would say, no, it doesn't exist anymore.

283
00:16:37,820 --> 00:16:39,420
So the network would still be running in the background.

284
00:16:39,800 --> 00:16:45,040
And people who knew how to still get access to listings or content would still work.

285
00:16:45,180 --> 00:16:51,540
But by attacking these things, the one piece of this network that was centralized, it was pretty effective on that part, I think.

286
00:16:51,720 --> 00:16:58,100
Also a bunch of learnings there, kind of like how just one piece of centralization kind of like tends to unravel you from a user's point of view.

287
00:16:58,400 --> 00:17:01,120
And how it can get very hard to understand from users really fast.

288
00:17:01,320 --> 00:17:07,680
So again, like really, really interesting use cases here and like things to learn also from my resilience point of view.

289
00:17:09,459 --> 00:17:13,880
Yeah. And then the last question before we touch a little bit more on what you guys are doing.

290
00:17:14,150 --> 00:17:17,459
You mentioned the concept of bad movies. This is something I've had to share as well.

291
00:17:17,459 --> 00:17:24,540
It's not an issue exclusive to peer-to-peer tech, but I feel like it is a little bit more of a Wild West.

292
00:17:24,810 --> 00:17:28,920
And it's maybe a little bit more likely for someone to download something that's malicious if they're not careful.

293
00:17:29,640 --> 00:17:32,940
So how does someone assess safety if something's peer-to-peer?

294
00:17:33,220 --> 00:17:35,480
Not just from making sure they download the correct thing,

295
00:17:35,780 --> 00:17:37,680
but I don't know if this is technically peer-to-peer.

296
00:17:38,220 --> 00:17:42,240
Jack Dorsey released his Messenger, which I believe uses a mesh network,

297
00:17:42,520 --> 00:17:44,120
but I don't know if that's technically peer-to-peer.

298
00:17:44,140 --> 00:17:47,280
But either way, when it was first launched, it's gotten much better since then.

299
00:17:47,480 --> 00:17:49,020
It had tons of vulnerabilities.

300
00:17:49,300 --> 00:17:50,760
It wasn't even using proper encryption.

301
00:17:51,140 --> 00:17:52,880
They themselves even came forward and said,

302
00:17:52,940 --> 00:17:55,100
you shouldn't be trusting this with anything sensitive.

303
00:17:55,780 --> 00:18:01,020
But something being peer-to-peer isn't alone any kind of metric of safety.

304
00:18:01,350 --> 00:18:07,020
So how can someone still assess safety when they're kind of responsible for their own safety on a peer-to-peer network?

305
00:18:07,860 --> 00:18:08,380
Yeah, for sure.

306
00:18:08,410 --> 00:18:12,900
I think actually an easier way to think about that is kind of like saying there's like the technological aspect of it,

307
00:18:12,950 --> 00:18:16,540
which is kind of like you have some content in a network and I want to access that content.

308
00:18:16,700 --> 00:18:17,600
Can we do that securely?

309
00:18:18,500 --> 00:18:23,000
And if we have no box in the software and we've done this for a while,

310
00:18:23,200 --> 00:18:25,800
that's actually the problem we've been solving for a long time.

311
00:18:25,850 --> 00:18:29,700
And it's a surmountable problem and very boring in some degree.

312
00:18:30,620 --> 00:18:32,480
But then the much more interesting question also becomes,

313
00:18:32,750 --> 00:18:34,560
also from a UX point of view, is kind of like,

314
00:18:35,440 --> 00:18:39,040
well, I can get a virus from you or some bad piece of software

315
00:18:39,110 --> 00:18:40,860
and I can get that cryptographically verified

316
00:18:41,110 --> 00:18:43,120
and it can be super secure to get it, but it's still a virus.

317
00:18:43,630 --> 00:18:45,060
So it's kind of like it doesn't really help me

318
00:18:45,140 --> 00:18:46,680
that the network is trying to make this really good.

319
00:18:47,540 --> 00:18:49,020
And what's the solution to that?

320
00:18:49,160 --> 00:18:55,200
Well, the solution to that is like, obviously there's a technological aspect of it, but it's also much like a product design thing.

321
00:18:55,340 --> 00:18:57,120
And like, how do we think about these things and products?

322
00:18:57,170 --> 00:19:00,720
So I think if we think about the content way, it's really good, right?

323
00:19:00,820 --> 00:19:07,580
Because it's like in a content app where you're sharing something that to some degree has a known origin, let's call that.

324
00:19:07,820 --> 00:19:13,960
So like, you know, let's say we were building like the Netflix of peer-to-peer and we had, you know, we're not trying to be pirates.

325
00:19:14,180 --> 00:19:17,420
We have the rights and we just want to do this this way because it's like distribution-wise,

326
00:19:17,800 --> 00:19:19,960
like much stronger model than putting it all on the server.

327
00:19:20,340 --> 00:19:24,480
Then you can still make systems in a P2P network where you add like a stamp of approval to content.

328
00:19:24,560 --> 00:19:31,180
So you can have like an index being served, like a search engine being served that is coming back to me saying,

329
00:19:31,480 --> 00:19:32,500
yeah, I approve of this index.

330
00:19:32,660 --> 00:19:33,920
So this is Mathias' index.

331
00:19:34,240 --> 00:19:36,260
This is what I say things should map to.

332
00:19:36,300 --> 00:19:39,100
So if you search for this thing, you can get some trust that if you trust me,

333
00:19:39,320 --> 00:19:42,500
you're not getting the content from me, but you're getting an idea what the correct content is.

334
00:19:42,720 --> 00:19:45,420
So you're getting that direction to get to your content.

335
00:19:45,780 --> 00:19:48,880
And we see this all the time in existing apps and social networks.

336
00:19:49,360 --> 00:19:52,720
Even in things like, if you think about recommendations, it's almost the same thing.

337
00:19:54,420 --> 00:19:58,980
I can't remember, there's this very popular recommendation app for movies that I can't remember to lay out right now,

338
00:19:59,200 --> 00:20:03,240
where you will search for things and it will say, oh, your friend likes this one, so you should probably watch it.

339
00:20:03,480 --> 00:20:05,140
And then you can go and find it on Netflix or whatever.

340
00:20:05,300 --> 00:20:06,060
It's kind of like the same thing.

341
00:20:06,400 --> 00:20:13,520
This idea that the people in your social group or even people you trust elsewhere can give content these stamps of approval.

342
00:20:14,260 --> 00:20:21,420
And then in a P2P network, you can just expand a little bit more and say, well, it's not just about approval of like, is this a good movie or not?

343
00:20:21,500 --> 00:20:24,340
It's also like, this is the right thing and this is the thing you should be looking for.

344
00:20:24,660 --> 00:20:30,320
The cool thing about it is that that actually is a really cheap thing to do in terms of like network effects and technical complexity.

345
00:20:30,480 --> 00:20:36,160
Because you're not really, that doesn't have to be tied together with the fact that I have all the rights for all the content.

346
00:20:36,360 --> 00:20:43,480
It just says that if these rights are distributed correctly, and that's obviously a thing, I will approve that this stamp of this file is correct.

347
00:20:43,820 --> 00:20:45,980
And then you can build some very strong networks like that.

348
00:20:46,560 --> 00:20:55,120
That's really, really powerful when used correctly because social proof and even extending that also to third-party validators is really, really powerful.

349
00:20:55,760 --> 00:20:58,200
And it's all over us in modern society.

350
00:20:58,360 --> 00:21:00,240
And I think we tend to forget that in general.

351
00:21:01,300 --> 00:21:04,180
It's kind of like back in the day when you could go to a blockbuster and buy a movie.

352
00:21:04,300 --> 00:21:05,180
That's how old I am.

353
00:21:05,680 --> 00:21:07,380
That's how I got my content in the early 2000s.

354
00:21:07,380 --> 00:21:10,200
You would also trust that the movie that Blockbuster has is the correct movie.

355
00:21:10,960 --> 00:21:15,140
Why? Because it's a big brand and you would trust that they're not switching the disks with something else.

356
00:21:16,060 --> 00:21:18,940
The same idea here that would just translate into a network where you say,

357
00:21:19,620 --> 00:21:25,800
I can have the digital version of that, but I can still have the content being distributed peer-to-peer afterwards.

358
00:21:26,100 --> 00:21:26,860
That's really, really powerful.

359
00:21:27,360 --> 00:21:28,920
Pivoting over to what you guys are doing.

360
00:21:29,320 --> 00:21:31,760
So I've tried the Messenger, Keet, I believe.

361
00:21:32,100 --> 00:21:32,680
K-E-T.

362
00:21:34,040 --> 00:21:40,080
Do you mind covering, I guess the first question I'm sure a lot of people are going to ask is, why another messenger?

363
00:21:40,720 --> 00:21:47,380
So maybe you want to expand on what you guys are doing that differentiates yourself and kind of how it's going so far.

364
00:21:48,400 --> 00:21:48,820
Yeah, for sure.

365
00:21:49,300 --> 00:21:53,940
So like I said, I've been working with peer-to-peer my entire career and I'm very, very invested in it.

366
00:21:54,060 --> 00:22:02,480
And around like four years ago, we decided to get really, really serious about peer-to-peer from not just a technical point of view,

367
00:22:02,580 --> 00:22:03,620
but also kind of like adoption.

368
00:22:03,900 --> 00:22:05,860
How can we get this ball rolling

369
00:22:06,120 --> 00:22:07,840
and get this technology out to everybody

370
00:22:08,600 --> 00:22:10,420
and try to disrupt the industry,

371
00:22:10,590 --> 00:22:12,260
both from a software development point of view,

372
00:22:12,270 --> 00:22:13,320
but also like a product point of view?

373
00:22:13,520 --> 00:22:15,440
Because like we already discussed,

374
00:22:15,550 --> 00:22:18,380
like peer-to-peer has been around cycles before,

375
00:22:18,600 --> 00:22:21,580
but been kind of tied to these use cases

376
00:22:21,800 --> 00:22:23,140
like piracy and things like that in the past.

377
00:22:23,190 --> 00:22:25,820
But like expand that and not just do that,

378
00:22:25,870 --> 00:22:27,640
but like, well, like not do it at all,

379
00:22:27,740 --> 00:22:29,820
but like build like real apps that do it.

380
00:22:30,160 --> 00:22:34,280
And so we founded our company, Holepunch, back then,

381
00:22:34,280 --> 00:22:37,760
and we were like, let's set a goal to make the hardest possible app

382
00:22:37,980 --> 00:22:41,760
that kind of encompasses everything in terms of what an app should do

383
00:22:41,800 --> 00:22:44,320
so we can both just solve a real use case

384
00:22:44,460 --> 00:22:47,580
and also validate that this thing works technically in every case.

385
00:22:47,700 --> 00:22:51,100
And we very quickly, after a brainstorm, decided that a messenger app

386
00:22:51,180 --> 00:22:53,240
is actually one of those apps that is incredibly simple.

387
00:22:53,560 --> 00:22:55,220
A messenger app is like you just type.

388
00:22:56,480 --> 00:22:58,820
But once you start going through the requirements you want from a messenger app,

389
00:22:58,900 --> 00:23:02,980
you quickly realize that it has all the requirements of every piece of software ever, right?

390
00:23:03,050 --> 00:23:05,180
It's kind of like you and I want to be able to chat,

391
00:23:05,430 --> 00:23:09,600
but we also want to be able to chat securely without surveillance and like in a private way.

392
00:23:09,600 --> 00:23:13,280
I want to be able to have a private chat with you and just send you what I actually think,

393
00:23:13,350 --> 00:23:18,200
what I'm thinking that if somebody reads this, that's not us, that this, you know, has consequences.

394
00:23:19,080 --> 00:23:20,940
Messengers also have file sharing, obviously, right?

395
00:23:21,010 --> 00:23:22,760
Because, you know, we send content all the time.

396
00:23:22,790 --> 00:23:24,160
It's a very natural way to send content.

397
00:23:24,340 --> 00:23:27,460
whenever I send, you know, movies and stuff like that,

398
00:23:27,560 --> 00:23:30,380
it's always to my parents of my kid and media and stuff like that.

399
00:23:30,380 --> 00:23:32,020
And that also ties into like, it should be private.

400
00:23:32,070 --> 00:23:34,500
It should be secure because I don't want that stuff to go anywhere else

401
00:23:34,600 --> 00:23:36,020
because it's private stuff.

402
00:23:36,200 --> 00:23:38,040
But it also has this like scalability aspect of it.

403
00:23:38,400 --> 00:23:42,860
If I wanted to share that for some reason with a very, very big chat group,

404
00:23:43,460 --> 00:23:44,960
like with thousands and thousands of people,

405
00:23:45,860 --> 00:23:47,060
it should still work and still be scalable.

406
00:23:47,380 --> 00:23:47,940
Check on that one.

407
00:23:47,970 --> 00:23:49,980
It's like a really high one and very, very important.

408
00:23:50,280 --> 00:23:53,200
And then also we've been seeing in the last, even before that,

409
00:23:53,280 --> 00:23:59,720
But especially in the last five years, just the world turned to a much, much darker place in terms of like the digital rights we have in these kind of apps.

410
00:24:00,120 --> 00:24:10,280
Like there's more and more stuff going on where both from like a data mining point of view, trying to like read our internal thoughts behind the scenes so we can get better advertisement and stuff like that and sell more products.

411
00:24:11,040 --> 00:24:25,980
But also just from a, for lack of a better word, control point of view, like, you know, having an idea of backdoors and surveillance, even in like pretty liberal places, traditionally liberal places like Europe, recently it's been turning very, very dark on that.

412
00:24:26,060 --> 00:24:29,500
So very quickly we identified this as like, oh, this is something we need to solve.

413
00:24:29,730 --> 00:24:31,440
And we decided to build a chat app.

414
00:24:31,640 --> 00:24:34,600
And it's been really, really exciting to build that out ever since.

415
00:24:34,680 --> 00:24:42,240
And like tackling all these problems up front and get it to scale and get it to run and like get it to run on devices.

416
00:24:42,440 --> 00:24:45,060
And again, without any infrastructure, just devices.

417
00:24:45,910 --> 00:24:50,120
So like no hidden, you know, server gets backed up to or anything like that.

418
00:24:50,280 --> 00:24:51,940
Just devices that can talk directly to each other.

419
00:24:53,000 --> 00:24:57,760
And then with a big, big UX caveat on top that the users should never really be aware of this.

420
00:24:58,120 --> 00:24:59,420
It should just work like any other app.

421
00:25:00,160 --> 00:25:02,260
We don't want it to be like a technical niche app.

422
00:25:02,260 --> 00:25:06,940
We want it to be like an everyday user app that just solves this from a user's point of view.

423
00:25:07,320 --> 00:25:08,140
So that's key.

424
00:25:08,340 --> 00:25:11,660
And we just shipped our latest version of it just before this podcast, actually.

425
00:25:11,900 --> 00:25:13,040
We're shipping like crazy.

426
00:25:13,200 --> 00:25:13,980
It's been really fun.

427
00:25:14,380 --> 00:25:15,100
And it's still really fun.

428
00:25:15,720 --> 00:25:18,580
And it's getting really good and really powerful.

429
00:25:18,700 --> 00:25:21,360
So when you make a peer-to-peer app, you don't really know about scale and stuff.

430
00:25:21,540 --> 00:25:25,180
Because, again, there's not a server I can log into and be like, how many users are online right now?

431
00:25:25,260 --> 00:25:26,020
And what's the scale?

432
00:25:26,220 --> 00:25:27,960
Because it's like just devices talking to each other.

433
00:25:28,660 --> 00:25:31,020
So it's kind of like you hear it through the grapevine.

434
00:25:31,120 --> 00:25:32,900
You hear like, oh, this is happening and this is happening.

435
00:25:33,000 --> 00:25:37,200
And you try to figure out what's happening to get a sense of like, is this going well?

436
00:25:37,320 --> 00:25:37,900
Is this going bad?

437
00:25:38,100 --> 00:25:38,460
What's working?

438
00:25:38,540 --> 00:25:38,900
What isn't?

439
00:25:39,040 --> 00:25:39,760
It's very, very social.

440
00:25:40,140 --> 00:25:41,060
You have to talk to people.

441
00:25:41,880 --> 00:25:47,100
But we recently had a big onboarding of new users due to links being shared in Eastern Europe.

442
00:25:47,300 --> 00:25:51,240
And it was really fun to see the app grow a lot and the network grow with that.

443
00:25:51,280 --> 00:25:56,220
and stuff like that. So it's been very exciting. Yeah, my assumption is you can probably see

444
00:25:57,140 --> 00:26:03,140
analytics from App Store and Google Play Store downloads and maybe on your site. And that's about

445
00:26:03,200 --> 00:26:09,540
it. And then we have a few public rooms in Keats that we have a link to that you can click on if

446
00:26:09,540 --> 00:26:13,820
you want to join and we get a sense of both community in that. But also, it's also been a

447
00:26:13,890 --> 00:26:17,479
very big learning that when you have a big room on a big network, just bringing the whole world

448
00:26:17,500 --> 00:26:21,560
into a single room can be very intense for sure, just with different cultures and stuff.

449
00:26:22,060 --> 00:26:23,700
And everything's open source, correct?

450
00:26:24,880 --> 00:26:27,240
So our entire stack is open source.

451
00:26:28,060 --> 00:26:34,520
Our key front end is closed right now, but 99% of our engine is available on GitHub.

452
00:26:36,120 --> 00:26:39,320
And if you're interested in P2P development in general, you should go check it out.

453
00:26:39,620 --> 00:26:42,560
It's really a beast of an engine these days with all kinds of stuff.

454
00:26:42,640 --> 00:26:46,659
Because like I said, we've been having to solve just so many things that you don't think

455
00:26:46,620 --> 00:26:51,700
about also when you start like, you know, getting devices to sync having the same state, getting

456
00:26:51,960 --> 00:26:55,820
files, getting big files to work, getting push notifications to work in a peer to peer

457
00:26:55,960 --> 00:26:59,420
environment is really hard on devices, getting them to run in the background, all this stuff.

458
00:27:00,020 --> 00:27:04,220
So if you have like a weekend where you're not doing anything, I would definitely start

459
00:27:04,250 --> 00:27:06,520
on GitHub and end at the other end of it.

460
00:27:06,820 --> 00:27:11,120
Here, I've quite a few questions to ask that came up.

461
00:27:11,170 --> 00:27:15,040
The first one is, can you explain the concept of something being serverless?

462
00:27:15,860 --> 00:27:27,140
Because even somebody who, I think there's this dangerous middle ground that a lot of people have fallen in, where they might know what a server is as a concept.

463
00:27:27,480 --> 00:27:34,400
They know it's maybe like the company has this thing, I'm talking to the company, and then the company sends a message to someone else.

464
00:27:34,780 --> 00:27:40,440
But the concept of cutting that out and you directly talking to somebody else is a bit different for people.

465
00:27:40,580 --> 00:27:44,060
So do you mind explaining how that works in something like Keet or just in general?

466
00:27:44,580 --> 00:27:45,040
Yeah, for sure.

467
00:27:45,300 --> 00:27:55,200
And also, it's even more confusing because I'm sure if you Google serverless, there was a term that was very popular like five years ago, four years ago about using servers for other things.

468
00:27:55,360 --> 00:27:56,820
So it's a confusing space.

469
00:27:57,600 --> 00:28:00,800
But basically, serverless now context here just means run things without servers.

470
00:28:00,950 --> 00:28:01,480
What does that mean?

471
00:28:01,610 --> 00:28:04,400
It means that we have a bunch of consumer devices these days.

472
00:28:04,580 --> 00:28:05,340
You know, I have a phone.

473
00:28:05,520 --> 00:28:06,200
I'm sure you have a phone.

474
00:28:06,340 --> 00:28:06,960
Everybody has a phone.

475
00:28:07,260 --> 00:28:08,400
I have a smartwatch.

476
00:28:08,600 --> 00:28:09,340
Some people have that also.

477
00:28:09,570 --> 00:28:10,100
I have a laptop.

478
00:28:10,460 --> 00:28:11,280
Some people have that also.

479
00:28:12,020 --> 00:28:21,200
And all of a sudden, us as consumers have accumulated a bunch of devices that over the last 20 years, 30 years have become incredibly powerful compared to what they used to be.

480
00:28:21,250 --> 00:28:29,280
So, you know, like my laptop and your phone like has, I don't even know how many magnitudes more power than we used to go to the moon in the 60s, right?

481
00:28:29,340 --> 00:28:34,600
It's like, you know, one of those ridiculously incredible numbers that just baffles the mind.

482
00:28:35,200 --> 00:28:38,640
So we just have a lot of compute power very close to us all the time.

483
00:28:39,560 --> 00:28:48,800
And we seldom use it because, you know, how often outside being very active on your phone spends most of the time being in your pocket or your desktop also be like idols most of the time.

484
00:28:49,400 --> 00:28:55,380
And they're also much more powerful than, you know, it's not like when you use your phone that is like just running at 100% powered 24 seven.

485
00:28:55,640 --> 00:28:58,240
So they have a lot of space and stuff and they're only getting better.

486
00:28:58,860 --> 00:29:18,120
So we have a lot of devices, but still as software developers and like people who think about products, we kind of still have this mental model of like, if we don't from back in the day, but we should, instead of like using more computer devices, we have external servers like data centers that does all the compute.

487
00:29:18,420 --> 00:29:29,560
And then, you know, when you and I in traditional apps would send data to each other, we would say, well, first of all, let's get it to that big server and then have the server do it and then have the server send it back to us later.

488
00:29:29,770 --> 00:29:32,240
So when we have no internet, things stop working.

489
00:29:32,660 --> 00:29:37,200
Or if we get blocked or banned or that the data center catches fire, things stop working.

490
00:29:37,300 --> 00:29:43,260
It creates these absurd situations a lot of the time where, you know, I mean, I have an office here.

491
00:29:44,039 --> 00:29:48,760
And when me and my co-founder sits in the office here, I sit at this table.

492
00:29:48,900 --> 00:29:50,940
He sits at a table like two meters next to me.

493
00:29:52,620 --> 00:29:57,000
When we use Slack and I send a message, if you just think about the travel of that message,

494
00:29:57,200 --> 00:30:02,020
it's like one of those big adventures in life where that message will go, even though there's only two meters to him,

495
00:30:02,880 --> 00:30:06,800
will go from my laptop to some data center somewhere, be backed up and maybe another data center.

496
00:30:06,820 --> 00:30:12,340
and on some servers, and it's probably crossed three or four countries by this stage,

497
00:30:13,580 --> 00:30:17,540
only to be dropped down on the other side of the computer, on the other side of the table,

498
00:30:18,260 --> 00:30:22,380
and then with a ton of still processing power, when in fact we could just take the direct line,

499
00:30:22,450 --> 00:30:23,760
which is just my device, to his device.

500
00:30:24,380 --> 00:30:26,580
So that's basically what peer-to-peer is trying to do.

501
00:30:27,380 --> 00:30:29,600
And it's also kind of interesting because it's how computing used to work.

502
00:30:29,860 --> 00:30:34,340
If you go back and think about original computing, this idea of a server is kind of made up, right?

503
00:30:34,400 --> 00:30:36,200
Because a server is just another computer.

504
00:30:36,460 --> 00:30:37,240
Everything is just computers.

505
00:30:37,920 --> 00:30:41,500
So P2P is just good old fashioned, cut out the middleman.

506
00:30:41,900 --> 00:30:42,980
There's just two things directly.

507
00:30:43,230 --> 00:30:50,120
And then the only other thing that's a little bit sophisticated is that obviously as you add like three, four, five, six computers, you don't want to have to talk to all of them.

508
00:30:50,130 --> 00:30:51,940
So you need to do a little bit of technology to make that smart.

509
00:30:52,820 --> 00:30:54,080
But at the end of the day, that's just technology.

510
00:30:54,520 --> 00:30:57,600
So cut out the middleman and make everything fast and simple.

511
00:30:59,180 --> 00:30:59,400
Nice.

512
00:30:59,610 --> 00:31:04,080
And then in regards to key, add a few more questions before we touch on other stuff you guys are working on.

513
00:31:04,300 --> 00:31:09,140
So you mentioned on the open source side of things, you have the open source stack, but then the closed front end.

514
00:31:09,270 --> 00:31:11,220
So why is it structured that way?

515
00:31:11,530 --> 00:31:12,060
Yeah, good question.

516
00:31:12,160 --> 00:31:16,420
It's also something we get asked, not a lot, but like obviously technical minded people have this question a lot.

517
00:31:16,520 --> 00:31:22,100
We're trying to make Keat as an app that your parents, you can use, my parents, myself, and anybody can use.

518
00:31:22,260 --> 00:31:31,300
Basically trying to take this very sophisticated piece of technology, which peer-to-peer at the end of the day is, behind the scenes, and make it work for real people.

519
00:31:31,660 --> 00:31:37,020
That requires also like kind of like going back to the thing we had in the beginning about like how do you got the right movie and stuff.

520
00:31:37,160 --> 00:31:39,300
It's the same for like crazy peer-to-peer apps.

521
00:31:39,300 --> 00:31:43,980
We need to make an experience that's really simple for people to understand.

522
00:31:44,170 --> 00:31:51,740
We need to have an app in the app store that's like always the latest app that's like easy to understand, that has a brand that people can go to as we bootstrap this network.

523
00:31:51,980 --> 00:31:55,820
So we don't kind of like get stuck in the small phase

524
00:31:55,970 --> 00:31:57,960
with like a thousand different clones of this app

525
00:31:58,140 --> 00:31:59,920
where every one of them is out of date

526
00:32:00,130 --> 00:32:01,580
because they all bundled the P2P app,

527
00:32:01,780 --> 00:32:03,400
but not the latest version.

528
00:32:03,720 --> 00:32:05,060
And like nothing really works

529
00:32:05,340 --> 00:32:08,780
because there's like too much proliferation too fast.

530
00:32:09,520 --> 00:32:11,340
So we're thinking a lot about that UX,

531
00:32:11,690 --> 00:32:15,100
how to make this like not a nerd technical product,

532
00:32:15,240 --> 00:32:16,380
but like kind of like a mainstream product.

533
00:32:16,410 --> 00:32:19,300
And that's a big reason why we try to keep the front end close

534
00:32:19,520 --> 00:32:20,858
so we can iterate really fast

535
00:32:20,860 --> 00:32:24,280
and have the experience, like everybody's up to date.

536
00:32:25,440 --> 00:32:29,040
If you try our Keet, this is the thing that the biggest complaint I get

537
00:32:29,060 --> 00:32:32,420
from my in-laws who uses Keet a lot, I talk to them in Ukraine a lot,

538
00:32:32,480 --> 00:32:34,780
which Keet works really well there because the networks are pretty bad.

539
00:32:35,700 --> 00:32:37,840
The biggest complaint I get is like every time Keet updates,

540
00:32:38,000 --> 00:32:40,720
it tells them to restart and get the latest one.

541
00:32:40,980 --> 00:32:41,900
And we update a lot.

542
00:32:41,900 --> 00:32:42,680
We update every two weeks.

543
00:32:44,039 --> 00:32:48,480
And the reason why we do that is because by doing that in this like bootstrapping phase,

544
00:32:49,040 --> 00:32:51,520
because, again, all the software you need to access the network

545
00:32:51,680 --> 00:32:52,480
is literally on your device.

546
00:32:52,860 --> 00:32:53,980
There's no other software somewhere.

547
00:32:54,270 --> 00:32:56,680
So, like, the full stack is on your device,

548
00:32:56,930 --> 00:32:58,120
which is kind of incredible to think about.

549
00:32:58,780 --> 00:33:00,940
So, by keeping everybody up to date in, like,

550
00:33:01,440 --> 00:33:02,760
in a bootstrapping phase and stuff like that

551
00:33:03,140 --> 00:33:05,880
makes it so much easier for the product to move fast

552
00:33:06,300 --> 00:33:08,060
and, again, go into this mission of, like,

553
00:33:08,680 --> 00:33:10,880
attack the mainstream, change the world.

554
00:33:11,280 --> 00:33:12,820
So, we're very, very focused on that

555
00:33:13,150 --> 00:33:16,120
and just keeping the front end closed and iteration heavy

556
00:33:16,300 --> 00:33:17,400
is a really, really big part of that.

557
00:33:17,900 --> 00:33:21,700
Now, I've written so much open source code in my career,

558
00:33:21,960 --> 00:33:22,960
like incredible amounts,

559
00:33:22,990 --> 00:33:24,980
because that's basically all I did for like 10 years,

560
00:33:25,200 --> 00:33:26,280
just produced open source code.

561
00:33:28,040 --> 00:33:29,600
And I've seen every aspect of it,

562
00:33:29,610 --> 00:33:30,880
but I'm a big, big believer of it.

563
00:33:30,880 --> 00:33:33,300
And that's why we didn't take literally that 99%

564
00:33:34,440 --> 00:33:37,200
that the rest, so people can review it and contribute to it.

565
00:33:37,200 --> 00:33:38,400
We have a lot of really good contributors

566
00:33:39,240 --> 00:33:42,320
and help push that part of the stack forward.

567
00:33:42,510 --> 00:33:44,760
It's not always the easiest thing to contribute to peer-to-peer

568
00:33:44,900 --> 00:33:47,018
because some parts of it can be tricky

569
00:33:47,060 --> 00:33:48,160
because it's like cryptography,

570
00:33:49,580 --> 00:33:51,940
but we do get a lot of good contributions and stuff.

571
00:33:53,080 --> 00:33:54,840
So yeah, so that's like the short answer,

572
00:33:54,970 --> 00:33:57,160
like long but short answer, I guess.

573
00:33:57,190 --> 00:33:59,320
It's like we're trying to make something

574
00:33:59,440 --> 00:34:00,140
that's truly mainstream.

575
00:34:00,370 --> 00:34:00,940
And by doing that,

576
00:34:00,970 --> 00:34:03,040
we need to be a little bit aggressive on these things.

577
00:34:03,200 --> 00:34:04,780
And that's why we do these things right now.

578
00:34:05,160 --> 00:34:06,980
When someone downloads the app update,

579
00:34:08,099 --> 00:34:10,520
is that download done via a server

580
00:34:11,020 --> 00:34:12,200
or is that done P2P?

581
00:34:12,639 --> 00:34:13,260
On the desktops,

582
00:34:13,360 --> 00:34:14,600
we have a desktop build and a mobile build.

583
00:34:14,629 --> 00:34:15,260
On mobile build,

584
00:34:16,000 --> 00:34:17,240
We can do a whole podcast of this.

585
00:34:17,379 --> 00:34:20,440
You're a bit more restricted because you're in the ecosystem of the app stores.

586
00:34:20,550 --> 00:34:25,940
And the app stores have the stuff that app stores have in terms of guidelines and rules.

587
00:34:26,739 --> 00:34:30,040
So you have to get some stuff from the app store always on update.

588
00:34:30,129 --> 00:34:32,980
But we try to do as much as we can update-wise there.

589
00:34:33,360 --> 00:34:35,820
Do you publish an APK on the Android side of things?

590
00:34:36,460 --> 00:34:38,260
We publish an APK on Keet.

591
00:34:38,409 --> 00:34:39,960
So we have Keet publishing the APK.

592
00:34:40,879 --> 00:34:43,139
So it's like CryptoCraftically Verified comes from us.

593
00:34:43,300 --> 00:34:47,000
So we have a chat room that's called the APK room that we maintain,

594
00:34:47,640 --> 00:34:50,300
and that implicitly everything is verifiable from there.

595
00:34:50,629 --> 00:34:57,139
And that we are published to Google's Play Store and the iOS one also.

596
00:34:57,440 --> 00:35:01,160
And on desktop, we have our peer-to-peer platform also,

597
00:35:01,170 --> 00:35:03,000
and that's fully peer-to-peer on the update.

598
00:35:03,260 --> 00:35:05,460
So everything on that running peer-to-peer,

599
00:35:05,540 --> 00:35:10,420
so truly mega unstoppable, nobody can take it down kind of situation on desktop.

600
00:35:10,610 --> 00:35:11,740
And we'll get there on mobile also.

601
00:35:11,880 --> 00:35:15,820
We have a big 10-year plan to kind of disrupt that thing also through various things.

602
00:35:16,020 --> 00:35:17,320
But I think it's really, really important.

603
00:35:17,440 --> 00:35:20,680
It's also very frustrating that you're a bit more limited on this side of mobile because there's no reason.

604
00:35:20,900 --> 00:35:22,620
We could do it tomorrow if we were allowed to.

605
00:35:23,100 --> 00:35:28,160
Yeah, I tested Keat only on desktop, and it was very clean.

606
00:35:28,440 --> 00:35:30,380
And I guess it depends what desktop you're running.

607
00:35:30,430 --> 00:35:34,580
If you're running a 24-7 desktop, it makes a lot of sense, especially with something peer-to-peer, because you're always online.

608
00:35:34,770 --> 00:35:35,720
You have a reliable network.

609
00:35:35,950 --> 00:35:37,360
I think it's kind of the best-case scenario.

610
00:35:37,790 --> 00:35:39,340
Do you want to speak a little bit about background sync?

611
00:35:39,480 --> 00:35:42,560
I assume on iOS, that's going to be a big challenge, or if it's not already.

612
00:35:43,000 --> 00:35:47,960
When you're your own peer, there's no server, so the device always has to be running in the background, I assume.

613
00:35:50,260 --> 00:35:52,580
So it's actually also equally hard on Android.

614
00:35:52,680 --> 00:35:58,440
It's actually funny you say this because literally three hours ago, we rolled out our first big part of background sync on iOS.

615
00:36:00,300 --> 00:36:02,040
That's exciting. How do you do that?

616
00:36:02,200 --> 00:36:06,420
Is that using the new iPad background sync, or is that also on iOS?

617
00:36:07,040 --> 00:36:10,840
So we do a variety of things because there's not really one solution on iOS.

618
00:36:11,150 --> 00:36:13,220
And we also don't run it 24-7 in the background.

619
00:36:13,930 --> 00:36:16,040
So just to dial it back a little bit.

620
00:36:16,180 --> 00:36:23,980
So a couple of years ago, one of the first big things with it was release this thing in KID where other people can help you maintain your network.

621
00:36:24,140 --> 00:36:25,460
It's called blind peering.

622
00:36:25,900 --> 00:36:34,200
So a peer can hold your data fully encrypted, can't see it, but that helps you in a network where you're a very small network.

623
00:36:34,420 --> 00:36:39,220
Like if you and I had a DM, that's a network of two people, which is the weakest peer-to-peer network.

624
00:36:39,940 --> 00:36:42,660
Because if one of us is offline, 50% of the network is offline.

625
00:36:42,950 --> 00:36:49,920
And like most of the time when you and I text each other, there's usually a device offline, a very high chance of a device offline.

626
00:36:49,970 --> 00:36:54,040
So you want to have a system where a very, very small network can introduce a third peer.

627
00:36:54,430 --> 00:36:57,680
Obviously, that's like fully private and just hold your data for a little bit.

628
00:36:57,750 --> 00:37:00,560
And then, you know, I come online, we can get this from there.

629
00:37:01,220 --> 00:37:02,500
So we did that a couple of years ago.

630
00:37:02,530 --> 00:37:03,620
It's really, really good for small networks.

631
00:37:03,740 --> 00:37:08,500
It's kind of ironic. I say this a lot, but like in peer-to-peer, the hardest problems is the small problems.

632
00:37:08,920 --> 00:37:12,400
So like in a centralized network, that problem is really easy because it's like, oh, you have a server.

633
00:37:12,400 --> 00:37:15,660
It has tons of capacity. So like two people, it's like tons of capacity.

634
00:37:15,860 --> 00:37:20,360
But then as that grows in a centralized network, it gets harder and harder and harder because the capacity runs out.

635
00:37:20,960 --> 00:37:23,340
In a peer-to-peer network, like if you're only two people, that's tricky.

636
00:37:23,600 --> 00:37:24,900
But then you had three people, now it's a lot better.

637
00:37:25,040 --> 00:37:26,340
And now you have four people, that's a lot better.

638
00:37:26,520 --> 00:37:29,180
And all of a sudden, when you're 10 people, all problems goes away.

639
00:37:29,460 --> 00:37:31,320
So it's like you want to have more capacity.

640
00:37:31,340 --> 00:37:37,180
So we have that in there, and it helps a lot with these kind of situations where, you know, you can pick somebody else from the network and help that hold a bit.

641
00:37:37,900 --> 00:37:40,580
And that's basically how small chats work.

642
00:37:40,900 --> 00:37:46,360
Then, obviously, you want to have as much backgrounding as possible because it just helps the entire network also.

643
00:37:46,720 --> 00:37:50,280
On iOS, we use, they have this general backgrounding API that can run once in a while.

644
00:37:50,380 --> 00:37:55,420
But also every time you get a notification, you can run a little bit of backgrounding on iOS and things like that.

645
00:37:55,420 --> 00:37:58,880
And you're also allowed to linger a bit in the background as you use the app.

646
00:37:59,320 --> 00:38:03,940
So all that stuff adds up and actually gives you a lot of compute because we don't need that much.

647
00:38:05,200 --> 00:38:08,780
It's kind of like you can imagine the data is on our side because there's many devices.

648
00:38:08,960 --> 00:38:11,120
So every time we add a little bit, the entire thing gets higher.

649
00:38:11,360 --> 00:38:12,260
So that works pretty well.

650
00:38:12,940 --> 00:38:13,720
But it's obviously a challenge.

651
00:38:14,020 --> 00:38:20,840
I actually find it personally really frustrating on phones because my phone is on all the time anyway.

652
00:38:21,320 --> 00:38:23,560
It's kind of like I can get a notification at any time.

653
00:38:24,040 --> 00:38:24,960
And I bought it.

654
00:38:25,000 --> 00:38:26,680
I literally paid lots of money for it.

655
00:38:27,180 --> 00:38:30,180
So why can't I, as a developer, do similar things?

656
00:38:30,420 --> 00:38:35,020
Because all the arguments basically come down to we don't want you to

657
00:38:35,260 --> 00:38:39,640
because we can do it in a way where it's as energy efficient

658
00:38:39,770 --> 00:38:42,080
as receiving a push notification because that's basically what it is,

659
00:38:42,930 --> 00:38:43,400
and stuff like that.

660
00:38:43,430 --> 00:38:46,540
So it's a little bit frustrating, but over time we'll get there on that.

661
00:38:46,890 --> 00:38:48,440
But it's not just a technical challenge.

662
00:38:48,940 --> 00:38:51,180
And then on Android we do similar things.

663
00:38:52,400 --> 00:39:02,920
Yeah, I guess what I've seen is apps like even Signal, Briar, if you don't have Google Play services on Android, they have this like always running 24-7.

664
00:39:03,260 --> 00:39:07,640
It drains up quite a bit of battery approach because there isn't really an easy alternative.

665
00:39:07,760 --> 00:39:16,080
I know Unified Push has been kind of getting a little bit more popular, but it seems like people don't really like the complexity of that either for end users.

666
00:39:16,900 --> 00:39:19,600
You really need a thing where you can hook into the systems,

667
00:39:20,040 --> 00:39:22,360
a low-level chip that says the network is running now

668
00:39:22,440 --> 00:39:23,120
and they run a little bit.

669
00:39:23,300 --> 00:39:25,460
That's a very good system, and they should just allow us to do that.

670
00:39:26,200 --> 00:39:27,300
So pivoting over to other things.

671
00:39:27,580 --> 00:39:30,480
So you guys are Holepunch, and I'll ask about your team

672
00:39:30,700 --> 00:39:31,980
and a little bit more about you guys.

673
00:39:32,260 --> 00:39:34,160
But what are some of the other things that you're working on?

674
00:39:34,440 --> 00:39:36,580
So we have quite a big team now.

675
00:39:36,820 --> 00:39:38,160
Like I said, we've been going on for like four years.

676
00:39:38,380 --> 00:39:40,280
Also, we're hiring developers.

677
00:39:40,520 --> 00:39:42,380
So if anybody's listening here is into programming,

678
00:39:42,520 --> 00:39:43,880
you should definitely go check it out.

679
00:39:43,940 --> 00:39:46,500
There's a lot of really fun and hard challenges to work with.

680
00:39:48,580 --> 00:39:49,900
But Tether is, sorry,

681
00:39:50,140 --> 00:39:52,340
Holepunch is a collaboration between Tether and us

682
00:39:52,460 --> 00:39:57,620
in terms of trying to do this big push to disrupt the status quo.

683
00:39:57,680 --> 00:40:00,420
If you don't know, Tether is this world's biggest stablecoin,

684
00:40:01,180 --> 00:40:03,880
which is kind of like digital dollars to send things back and forth,

685
00:40:04,140 --> 00:40:04,960
which is really, really cool.

686
00:40:05,220 --> 00:40:06,900
And it's really well with a P2P of things.

687
00:40:07,740 --> 00:40:12,180
So we're trying basically through that also to disrupt the entire industry

688
00:40:12,180 --> 00:40:15,220
of both how you share data

689
00:40:15,460 --> 00:40:17,520
and Tether does it on the financial side

690
00:40:17,560 --> 00:40:18,060
and stuff like that.

691
00:40:18,720 --> 00:40:19,860
Overlapping those things are very exciting.

692
00:40:20,080 --> 00:40:23,700
But we recently did a big push of other apps also

693
00:40:23,880 --> 00:40:26,960
to try to push the technology and just make,

694
00:40:27,040 --> 00:40:28,860
there's so many things to solve on these things

695
00:40:28,940 --> 00:40:29,620
that's really exciting.

696
00:40:30,240 --> 00:40:32,780
So right now we're also working on something

697
00:40:32,880 --> 00:40:34,620
in a collaboration with them called PairPass,

698
00:40:34,700 --> 00:40:36,980
which is a password manager app

699
00:40:37,340 --> 00:40:39,160
because that also I think fits the bill really well

700
00:40:39,160 --> 00:40:41,500
and these like simple but very powerful use cases

701
00:40:41,520 --> 00:40:46,060
of how can you take something that's extremely close to us right now,

702
00:40:46,380 --> 00:40:49,740
a lot of things still require passwords and secure notes

703
00:40:49,820 --> 00:40:52,940
and stuff like that, and keep it truly private and truly secure

704
00:40:53,720 --> 00:40:56,400
without having to rely on any kind of centralization.

705
00:40:56,600 --> 00:41:00,340
So we did a big push on that recently, trying to just take the stack,

706
00:41:01,140 --> 00:41:04,000
like 90% of the stack that's also running, keep, again, all open source.

707
00:41:04,960 --> 00:41:07,540
PairPess is fully open source to kind of show people also how to build things

708
00:41:08,040 --> 00:41:11,480
completely from the ground up because it doesn't have that big mainstream thing

709
00:41:11,500 --> 00:41:15,900
I just said earlier, it's kind of like it's more a normal thing.

710
00:41:17,080 --> 00:41:20,680
Hopefully, you're not going to send many chat messages in a password app.

711
00:41:20,690 --> 00:41:21,540
That would be kind of crazy.

712
00:41:21,710 --> 00:41:23,460
So that's rolling out really soon.

713
00:41:23,760 --> 00:41:25,320
Super, super excited to get that one out.

714
00:41:25,460 --> 00:41:26,700
I've been playing around with it a lot myself.

715
00:41:26,910 --> 00:41:28,320
I helped coordinate a bit of the code initially,

716
00:41:28,550 --> 00:41:30,500
but the team has really been cranking away on that.

717
00:41:30,580 --> 00:41:32,100
And it's just really, really powerful.

718
00:41:33,400 --> 00:41:34,720
Really, really simple at the end of the day.

719
00:41:34,920 --> 00:41:35,820
So super cool stuff.

720
00:41:36,180 --> 00:41:39,820
Yeah, I'm going to ask about that because password managers are an interesting one.

721
00:41:40,340 --> 00:41:48,220
I get a lot of people who leave comments and are concerned about the idea of a server holding their passwords,

722
00:41:48,480 --> 00:41:57,540
even though we can verifiably prove that it's encrypted and it's theoretically no different than if you were to encrypt it yourself and upload it on a server.

723
00:41:58,100 --> 00:42:02,380
And then I think the whole peer-to-peer aspect could be a bit scary for someone.

724
00:42:02,420 --> 00:42:04,740
But before I get to that, I just wanted to quickly ask about the stack.

725
00:42:04,940 --> 00:42:10,160
It sounds like the stack that you use for Keat can be repurposed to be used for many other things.

726
00:42:10,920 --> 00:42:18,360
So what exactly is the stack really just the ability for you as a device to be a peer to connect to other peers and transmit data?

727
00:42:18,570 --> 00:42:24,760
And then the actual data and the UX is kind of the only difference between any potential products?

728
00:42:25,320 --> 00:42:31,360
So like I said in the beginning, we tried to do this big mission of like let's basically disrupt software development, how you make apps and stuff like that.

729
00:42:31,480 --> 00:42:34,680
And so we quickly just put that into different categories.

730
00:42:34,970 --> 00:42:36,200
Like, what do you need when you make an app?

731
00:42:36,200 --> 00:42:36,920
You need like a database.

732
00:42:37,460 --> 00:42:38,460
You need some sort of connectivity.

733
00:42:38,890 --> 00:42:41,620
As in like, you know, kind of like right now we're recording a podcast.

734
00:42:41,850 --> 00:42:44,840
We have a stream together where we can see each other, like a call.

735
00:42:45,480 --> 00:42:46,900
So you need some sort of real-time communication.

736
00:42:47,070 --> 00:42:48,920
You need persistence databases.

737
00:42:49,150 --> 00:42:51,820
You need some sort of file sharing if you're doing stuff like that,

738
00:42:51,850 --> 00:42:52,880
or at least components for that.

739
00:42:53,540 --> 00:42:56,120
And the various other small and bigger components for that.

740
00:42:56,460 --> 00:42:59,520
And we made just software modules for each of them that kind of like,

741
00:42:59,840 --> 00:43:06,260
For a software developer, it has some normal-looking interfaces that makes it relatively familiar to make apps,

742
00:43:06,420 --> 00:43:11,540
and then packages that up into a bunch and bunch of small modules so you can pick and choose what you want,

743
00:43:11,740 --> 00:43:14,920
and then make that freely available for any kind of app that wants to be peer-to-peer.

744
00:43:15,040 --> 00:43:17,500
Like I said, that's all there, open source, available on GitHub.

745
00:43:17,760 --> 00:43:18,320
We have a website.

746
00:43:18,840 --> 00:43:21,940
That's the only website we have outside KIT.io called pairs.com,

747
00:43:22,060 --> 00:43:26,340
where we have a little documentation on how to work with this and make examples.

748
00:43:27,640 --> 00:43:32,420
So theoretically, I can download that stack, develop my own messenger using the same stack.

749
00:43:32,890 --> 00:43:38,340
Would that be its own network or would that actually still be part of the same network that everyone's using for something like Keap?

750
00:43:39,200 --> 00:43:41,220
It would be its own network because every app is its own network.

751
00:43:41,540 --> 00:43:45,260
We could then make a collaboration and try to bridge those networks if we wanted to.

752
00:43:45,540 --> 00:43:46,360
There's nothing wrong with that.

753
00:43:46,500 --> 00:43:50,640
But peer-to-peer, I think it's also good you bring that up because it can be a little bit hard to understand.

754
00:43:50,800 --> 00:43:52,060
Because peer-to-peer is not like one big network.

755
00:43:52,430 --> 00:43:55,320
It basically just means whatever you want.

756
00:43:55,680 --> 00:43:59,760
So normally you would just make that kind of like everything is a little network by itself

757
00:44:00,460 --> 00:44:02,640
and have your decisions kind of like encapsulate that.

758
00:44:02,750 --> 00:44:03,300
That makes a lot of sense.

759
00:44:03,410 --> 00:44:07,880
And also that's one of the reasons why we can just do this open sourcing for free

760
00:44:08,080 --> 00:44:10,060
because that doesn't cost us anything to run it.

761
00:44:10,070 --> 00:44:13,820
It's not like when you do that, like there's something we allocate on our end.

762
00:44:14,200 --> 00:44:17,600
It also means that there's nothing for us where we need to sell you something when you do it.

763
00:44:17,690 --> 00:44:18,980
So we can just have it be software.

764
00:44:19,170 --> 00:44:21,340
It's not like there's a token or something like that you have to buy

765
00:44:21,960 --> 00:44:24,580
and can invest in to kind of hope that helps the network.

766
00:44:24,880 --> 00:44:30,160
Because again, this is just between you and your devices, however you define it, and you can do whatever you want in a good way.

767
00:44:30,300 --> 00:44:32,600
So really simple infrastructural tech.

768
00:44:32,720 --> 00:44:41,380
We have this internal, I don't want to say mission because this sounds wrong, but it's kind of like this mantra of saying, if we go bankrupt tomorrow and we shut down the company, everything should still be running.

769
00:44:42,260 --> 00:44:44,040
So like everything is kind of like built with that mentality.

770
00:44:44,320 --> 00:44:46,160
So it's truly just peer-to-peer.

771
00:44:46,460 --> 00:44:48,000
So I don't want to say hosted.

772
00:44:48,200 --> 00:44:52,920
I'm trying to come up with a different word because this sounds wrong also, but it's like self-regulating networks, I guess.

773
00:44:53,320 --> 00:44:53,500
Yeah.

774
00:44:53,840 --> 00:44:54,940
And I guess one quick question.

775
00:44:55,040 --> 00:44:59,800
I know I kind of threw the password manager thing at you and then we quickly changed subjects.

776
00:45:00,120 --> 00:45:05,740
But on the topic of funding and Tether, let's say Tether decides we don't want to keep doing this anymore.

777
00:45:06,020 --> 00:45:06,920
What would happen to Holepunch?

778
00:45:07,220 --> 00:45:09,000
So is there a strong dependence there?

779
00:45:09,260 --> 00:45:15,020
So we have a big long-term traditional strategic partnership that we're very, very committed to, both of us.

780
00:45:15,260 --> 00:45:22,000
When we started doing Holepunch, like I said, we came into this with this idea of like, let's make technology that truly has no infrastructure.

781
00:45:22,180 --> 00:45:27,380
So it's a very interesting company because we actually don't have any infrastructure other than, you know, testing stuff here and there.

782
00:45:27,550 --> 00:45:30,900
And it's also a very interesting thing to talk about financially.

783
00:45:31,080 --> 00:45:38,260
I get asked this a lot on other podcasts, like how do you guys make money and what's the profitability on these things and stuff like that, which is very, very good questions.

784
00:45:39,120 --> 00:45:43,320
Because right now we've been very focused on the technological side of it.

785
00:45:43,540 --> 00:45:55,300
But something that's very interesting on that and also kind of like to answer your question is as the products scale and we add people, like I said, we're just onboarding a huge amount of new people that we think at least to keep recently, the company costs don't go up.

786
00:45:55,480 --> 00:45:59,260
So we have this like idea that we have, you know, we have budgets, we have money in the bank.

787
00:45:59,420 --> 00:46:03,300
We can kind of like look ahead and say, well, obviously we need to pay people salaries.

788
00:46:03,800 --> 00:46:04,900
That's how the world works.

789
00:46:05,020 --> 00:46:05,240
That's good.

790
00:46:05,580 --> 00:46:11,800
But like, there's not like hidden, oh, if there's overnight success, what do we need to do to like keep things running and stuff like that?

791
00:46:12,420 --> 00:46:19,520
And that's a whole different way of thinking about just both financial roadmaps and like profitability and like, and things like that.

792
00:46:19,800 --> 00:46:26,340
It's a much more almost like old school way of thinking of things because we can have this idea that we can make technology that can scale really fast.

793
00:46:26,960 --> 00:46:32,500
But at the same time, we can have the freedom to never really think about burn rate in that same sense because the burn rate is very flat.

794
00:46:33,500 --> 00:46:40,200
And that makes our life really, my life a lot easier because I can just look, you know, on the runway and be like, that's it.

795
00:46:40,400 --> 00:46:45,160
But also I can, when we make the products, focus on just like your product development.

796
00:46:45,340 --> 00:46:57,640
So like, for example, right now, something we're rolling out in Keet that we just rolled out a very early preview version of and the latest version of Keet is like big podcast-style calls like this one, where you can do like big calls.

797
00:46:58,320 --> 00:47:03,200
So normally if I was doing that on traditional product, I would be like, okay, so you and I are talking here.

798
00:47:03,580 --> 00:47:04,160
That's like bandwidth.

799
00:47:04,400 --> 00:47:05,140
That's going to cost money.

800
00:47:05,220 --> 00:47:08,800
So if we host that on our servers, what if that gets really popular?

801
00:47:09,000 --> 00:47:10,240
It's going to be a big bill coming in.

802
00:47:11,140 --> 00:47:12,900
And Keelig would just do it because we're like, ah, it doesn't matter.

803
00:47:13,100 --> 00:47:17,540
Because the network is paying for that by people just streaming themselves.

804
00:47:17,960 --> 00:47:18,840
They've already paid for the internet.

805
00:47:19,120 --> 00:47:20,600
So that just changes the equation completely.

806
00:47:20,860 --> 00:47:22,620
We're very, very excited in general to partner with Tether

807
00:47:22,690 --> 00:47:26,860
because Tether is such a beast in terms of financial kill bill.

808
00:47:27,700 --> 00:47:31,500
I don't know if you follow it closely, but it just grows bigger and bigger

809
00:47:31,550 --> 00:47:33,860
and bigger and bigger every month.

810
00:47:34,060 --> 00:47:38,180
And that's basically the same kind of mentality we have with peer-to-peer.

811
00:47:38,320 --> 00:47:43,960
We want to do something that impacts the world in truly an irreversible way and change the status quo.

812
00:47:44,200 --> 00:47:46,820
I think that's a really, really good synergy there.

813
00:47:48,000 --> 00:47:54,080
Yeah, with video streaming, I know there's still a centralized aspect to it because I still have to pay to host the videos on my server.

814
00:47:54,480 --> 00:47:54,960
There's still a server.

815
00:47:55,560 --> 00:48:03,440
But it reminds me a lot of PeerTube because when you go and watch a video, you're also streaming some of the bandwidth to someone else, and there's still a peer-to-peer aspect.

816
00:48:03,540 --> 00:48:07,080
And I'm going to ask you about the hybrid solutions towards the end.

817
00:48:07,140 --> 00:48:22,380
But I want to quickly double click on the password manager question I kind of threw you away earlier of the whole idea of potentially sharing password management, even if it's encrypted information with other peers on a network.

818
00:48:23,100 --> 00:48:26,520
So first of all, I think with password managers, I think there's my friend told me this analogy one.

819
00:48:26,600 --> 00:48:27,800
So I think it just fits really well.

820
00:48:27,940 --> 00:48:28,900
I'm sure he heard it from somebody else.

821
00:48:29,080 --> 00:48:39,060
But it's kind of like even with centralized password managers, if you look at something existing today where you have these apps that is like centralized solution, they all have very, very strong cryptography, I'm sure.

822
00:48:39,700 --> 00:48:42,000
And there's a lot of like decent ones out there.

823
00:48:42,520 --> 00:48:44,080
But my friend told me this thing that I always think about.

824
00:48:44,100 --> 00:48:51,060
It's kind of like, well, if you have the world's best scientists, right, and they all have to travel somewhere, do you put them all on the same plane?

825
00:48:51,420 --> 00:48:52,920
It's kind of like the plane is really safe, right?

826
00:48:53,020 --> 00:48:53,600
It never crashes.

827
00:48:54,200 --> 00:48:55,960
But like still, would you do it?

828
00:48:56,000 --> 00:48:59,560
And it's like, there's always this like slight risk of like, well, maybe something went wrong

829
00:48:59,600 --> 00:49:00,860
in the cryptography and things like that.

830
00:49:00,960 --> 00:49:06,000
So you want to have options where you can kind of like define your own thing.

831
00:49:06,060 --> 00:49:11,340
So in a peer-to-peer password manager, like Autopass, the true power, I think, is kind

832
00:49:11,340 --> 00:49:12,780
of like in that aspect of options.

833
00:49:13,800 --> 00:49:16,860
So the app itself has various settings you can choose.

834
00:49:16,980 --> 00:49:17,860
So you can basically choose.

835
00:49:18,040 --> 00:49:19,800
I just want to back this up with myself.

836
00:49:20,040 --> 00:49:25,600
It's obviously all super strong, mega encrypted at rest and in flight and all this stuff.

837
00:49:26,420 --> 00:49:29,320
that I, again, I'm sure also existing password managers have

838
00:49:30,030 --> 00:49:32,220
that would then go to one centralized place.

839
00:49:33,160 --> 00:49:33,760
Autopass doesn't.

840
00:49:34,440 --> 00:49:35,220
So you can choose there.

841
00:49:35,440 --> 00:49:36,980
I just want to have it between my own devices.

842
00:49:37,230 --> 00:49:39,020
And then if I lose all my devices, tough luck,

843
00:49:39,260 --> 00:49:40,040
my password's gone.

844
00:49:40,300 --> 00:49:40,680
That's a feature.

845
00:49:41,859 --> 00:49:44,940
Or I want to have it be backed up to my friends

846
00:49:45,630 --> 00:49:47,600
through their social backups.

847
00:49:48,720 --> 00:49:50,060
I'm sure we're missing a little bit of UX on that.

848
00:49:50,420 --> 00:49:53,579
Or I want to have it be in this general blind peer networks

849
00:49:53,600 --> 00:49:57,800
where people can kind of like, you know, anybody can help or choose these specific ones.

850
00:49:57,940 --> 00:50:00,400
And I think we have a lot of options in the app.

851
00:50:00,440 --> 00:50:03,880
I can't remember exactly what the final one looked like,

852
00:50:04,000 --> 00:50:07,660
but like where you can pick very specifically where things go and stuff like that.

853
00:50:07,860 --> 00:50:11,660
Because one of the powers of peer-to-peer is this idea that it doesn't really matter where things come from.

854
00:50:11,740 --> 00:50:15,300
So that makes it very, very easy to build these things out without having to think so much about it.

855
00:50:15,720 --> 00:50:19,680
Got it. So you're saying if I have three devices, let's say a desktop, a laptop, and a phone,

856
00:50:22,180 --> 00:50:25,580
they, you know, let's say I'm coming from KeePass,

857
00:50:25,880 --> 00:50:27,100
so I'm used to an offline experience.

858
00:50:27,900 --> 00:50:29,940
Can I just have an offline database

859
00:50:30,240 --> 00:50:32,600
that I can just manually, if I want,

860
00:50:32,880 --> 00:50:34,800
copy and paste essentially onto another device?

861
00:50:35,540 --> 00:50:36,800
Is that, I guess that's question one.

862
00:50:36,960 --> 00:50:38,180
And then question two is,

863
00:50:38,180 --> 00:50:41,200
it sounds like I can just have a sync chain

864
00:50:41,400 --> 00:50:43,200
that's peer-to-peer across just those three devices.

865
00:50:43,360 --> 00:50:44,700
It doesn't touch any other device.

866
00:50:45,240 --> 00:50:47,060
And then I can also extend it to other people

867
00:50:47,260 --> 00:50:48,680
and beyond if I want to.

868
00:50:49,220 --> 00:50:49,620
Exactly.

869
00:50:49,800 --> 00:50:51,580
So I think I called it Autopass before.

870
00:50:51,740 --> 00:50:53,400
That's because our module is called Autopass.

871
00:50:53,540 --> 00:50:59,340
The app itself is called PairPass, which rolls very well over an under-tongue PairPass.

872
00:51:00,760 --> 00:51:01,420
But exactly that.

873
00:51:02,000 --> 00:51:04,040
So you can build your own topology.

874
00:51:04,360 --> 00:51:06,460
Everything in PairPass is fully open source also.

875
00:51:06,500 --> 00:51:09,340
So you can even just also go in if you wanted to change something in that.

876
00:51:09,380 --> 00:51:10,260
You can go in and edit it.

877
00:51:10,780 --> 00:51:16,500
And the network will still work because the protocol itself, just peer-to-peer, is simple and super strong.

878
00:51:17,840 --> 00:51:18,840
So very powerful.

879
00:51:18,900 --> 00:51:24,640
But we also, we used this opportunity when we were making this to have it be audited by other people.

880
00:51:24,920 --> 00:51:31,420
So we also got a security auditor on it also that we'll be publishing with the app and stuff like that.

881
00:51:31,840 --> 00:51:36,380
That has been a good experience for us just to try to think through these questions that you say also,

882
00:51:36,440 --> 00:51:39,280
how can we make this feel comfortable to everybody and make it powerful?

883
00:51:40,820 --> 00:51:43,260
But it's really interesting to think about it that way.

884
00:51:43,380 --> 00:51:46,300
Because even me as somebody who's, again,

885
00:51:47,100 --> 00:51:48,700
understand the powers of encryption and stuff,

886
00:51:48,880 --> 00:51:52,620
I think just having it sync with myself is really powerful.

887
00:51:52,700 --> 00:51:54,740
I think that's a good redundancy factor

888
00:51:54,900 --> 00:51:57,240
in how I can be very comfortable with these things also.

889
00:51:58,060 --> 00:51:59,460
And the cool thing about a peer-to-peer network is

890
00:52:00,260 --> 00:52:02,060
you can do that while still having the comfort

891
00:52:02,260 --> 00:52:04,300
of a normal syncing system, if you know what I mean.

892
00:52:04,640 --> 00:52:07,520
I'm a big, big fan of KeePass, as you mentioned,

893
00:52:07,900 --> 00:52:10,240
but it can be a little bit cumbersome with the setups

894
00:52:10,580 --> 00:52:12,060
because that's basically the future.

895
00:52:12,060 --> 00:52:12,780
I moved away from it.

896
00:52:13,279 --> 00:52:18,180
Yeah, but it's basically, and it's not to say anything bad with it, because it's basically a feature of it.

897
00:52:18,240 --> 00:52:20,640
It's just, that's why it's so simple and powerful.

898
00:52:20,810 --> 00:52:24,440
But it's like, you also want to have this like, oh, now I got to switch my phone and stuff like that.

899
00:52:24,700 --> 00:52:28,280
So the combo is needed, I think.

900
00:52:29,100 --> 00:52:32,460
It's actually quite interesting, because, you know, unless I started using a centralized cloud provider,

901
00:52:32,670 --> 00:52:36,160
like if you just do manual syncing on your device using something like Dropbox,

902
00:52:36,280 --> 00:52:39,120
the cleanest experience I ever had with KeePass was using SyncThing,

903
00:52:41,080 --> 00:52:44,880
which I believe, I know it can work locally in your network,

904
00:52:44,990 --> 00:52:46,900
but I believe also has some kind of peer-to-peer aspect,

905
00:52:47,550 --> 00:52:48,240
if I'm not mistaken.

906
00:52:48,590 --> 00:52:53,120
And so you're essentially just making that all-in-one

907
00:52:53,650 --> 00:52:54,900
into the same password manager

908
00:52:55,540 --> 00:52:58,100
and kind of adding in the P2P side of it directly in there?

909
00:52:58,960 --> 00:53:01,480
Yeah, and I think it's actually a really good analogy

910
00:53:01,650 --> 00:53:04,120
because basically instead of just saying,

911
00:53:04,420 --> 00:53:06,840
hey, let's have things produce files

912
00:53:06,890 --> 00:53:08,740
and then sync them with some file-sharing network,

913
00:53:09,560 --> 00:53:13,980
What we're saying also with the peer-to-peer stack is saying, well, let's go a little bit deeper.

914
00:53:14,300 --> 00:53:18,120
So let's make the infrastructure in the apps do this, right?

915
00:53:18,280 --> 00:53:22,240
And then just have developers have the tools to make applications.

916
00:53:22,680 --> 00:53:27,640
So if you look at the software for Pear Pass, you'll notice that it's not really peer-to-peer.

917
00:53:27,660 --> 00:53:29,940
It's just kind of like interacting with a database, putting things in and out.

918
00:53:30,400 --> 00:53:32,760
And then the software then helps make that peer-to-peer after.

919
00:53:33,380 --> 00:53:36,280
So I think why that's really cool is kind of like the same idea you just described there.

920
00:53:36,280 --> 00:53:36,980
You just make an app.

921
00:53:37,180 --> 00:53:37,960
You make it look pretty.

922
00:53:38,160 --> 00:53:39,400
You make it look simple.

923
00:53:39,900 --> 00:53:45,220
and have it work locally and then let the peer-to-peer magic do its magic

924
00:53:45,480 --> 00:53:48,600
and have that make it multi-device and stuff like that.

925
00:53:48,860 --> 00:53:50,580
And that's where it gets really powerful because for me,

926
00:53:50,810 --> 00:53:53,100
that just shows you that anybody can do this

927
00:53:53,430 --> 00:53:55,940
and you don't have to have a PhD in networking or anything like that

928
00:53:56,100 --> 00:53:58,200
to make these very powerful distributed systems.

929
00:53:58,950 --> 00:54:01,980
So that's where I'm like, outside just having a really good password manager,

930
00:54:02,060 --> 00:54:04,660
which is really needed, I'm just personally very, very excited.

931
00:54:06,080 --> 00:54:13,300
Yeah, and I like that as well because I know I had this issue as well in sync thing where sometimes something wouldn't sync fully.

932
00:54:14,060 --> 00:54:18,260
And then I had something that would be corrupted or didn't sync the latest version.

933
00:54:18,380 --> 00:54:23,240
And so I feel like having everything being run in a similar environment would actually make a lot of sense.

934
00:54:23,640 --> 00:54:28,080
I'm sure also just to finish on that thought, because I'm sure also in an environment like that, if you had, you know,

935
00:54:28,360 --> 00:54:34,700
in something like a password manager where I have passwords to share with my wife and family and stuff like that for like joint things.

936
00:54:35,400 --> 00:54:39,620
So if you have kind of like a Jerry Rick solution, like syncing things like that, those passwords

937
00:54:39,710 --> 00:54:41,620
would get out of sync really fast in a system like that.

938
00:54:41,620 --> 00:54:45,480
So you need to have some technology that does this magic on that also.

939
00:54:45,940 --> 00:54:46,260
Nice.

940
00:54:46,460 --> 00:54:46,540
Yeah.

941
00:54:46,670 --> 00:54:48,060
And then a couple of questions here.

942
00:54:48,480 --> 00:54:49,760
I guess this also applies to Keat.

943
00:54:50,180 --> 00:54:51,080
Is Keat audited?

944
00:54:51,270 --> 00:54:54,000
And do you guys do consistent audits or is it just a one-time thing?

945
00:54:55,300 --> 00:54:58,900
So Keat is audited actually indirectly through this pair pass one because like I said, like

946
00:54:58,970 --> 00:55:00,880
literally 99% of the code is the same, right?

947
00:55:01,040 --> 00:55:02,120
So that's obviously stuff.

948
00:55:02,230 --> 00:55:04,800
So you're auditing the stack, not the individual product.

949
00:55:05,200 --> 00:55:16,560
And in Pear Pass also, we also ordered the product, but we explicitly went in and said, hey, we want to do an audit where we get into the mindset of doing it on the full stack because we want this to actually learn also.

950
00:55:16,920 --> 00:55:21,000
And we said very explicitly when we did it, we want to know the issues.

951
00:55:21,370 --> 00:55:22,600
We're not trying to just get a stamp.

952
00:55:22,650 --> 00:55:23,980
We actually want to see if there's any issues.

953
00:55:24,180 --> 00:55:24,940
Luckily, it went really well.

954
00:55:25,100 --> 00:55:26,060
So that's good.

955
00:55:26,070 --> 00:55:32,380
But even if there was something been flagged, that would have been success also because we're just trying to build the most secure product out here.

956
00:55:32,580 --> 00:55:36,080
Yeah, we want to do more ongoing reviews as we build things out.

957
00:55:36,720 --> 00:55:40,700
As anybody who's done intense deep tech will tell you,

958
00:55:40,890 --> 00:55:43,520
like doing an audit too early will be counterproductive

959
00:55:43,670 --> 00:55:44,860
because then like the next week you're like,

960
00:55:44,890 --> 00:55:47,100
well, all that is gone now and like here's the new version.

961
00:55:48,180 --> 00:55:51,660
So we had to get to a sense of like this is very stable now

962
00:55:51,750 --> 00:55:52,320
and we can do it.

963
00:55:52,340 --> 00:55:54,220
That's something we've reached in the last couple of years.

964
00:55:54,520 --> 00:55:57,620
So it's been very, very good for us, but definitely 100%.

965
00:55:57,680 --> 00:55:57,920
Great.

966
00:55:57,990 --> 00:56:01,740
And then I just wanted to verify you guys are also on Linux on both of those.

967
00:56:02,380 --> 00:56:04,220
We are on painfully many ones.

968
00:56:04,420 --> 00:56:08,320
So we are on most of the Linuxes, like the various distors,

969
00:56:08,730 --> 00:56:11,080
which as anybody who's working with Linux can tell you,

970
00:56:11,210 --> 00:56:12,220
sometimes it gets a little intense.

971
00:56:14,340 --> 00:56:17,099
Yeah, I mean, it's...

972
00:56:18,600 --> 00:56:19,260
I can't...

973
00:56:19,310 --> 00:56:20,780
I actually get very frustrated by it,

974
00:56:20,780 --> 00:56:23,860
and I wish the Linux community would have some simpler way to manage this

975
00:56:24,060 --> 00:56:25,460
because I can't even be mad.

976
00:56:26,080 --> 00:56:27,620
I am mad, for the record.

977
00:56:28,040 --> 00:56:31,499
I am mad, but I can't very easily publicly be mad

978
00:56:31,960 --> 00:56:34,440
at companies, organizations, I suppose, like Signal,

979
00:56:35,180 --> 00:56:37,540
because Signal just publishes a DEB.

980
00:56:38,180 --> 00:56:38,360
That's it.

981
00:56:38,420 --> 00:56:41,080
Yeah, I was going to say that's also the same thing to do.

982
00:56:41,380 --> 00:56:44,800
Yeah, and it's like, oh, there's this unofficial community flat pack

983
00:56:45,440 --> 00:56:46,880
for an end-to-end encrypted messenger.

984
00:56:47,470 --> 00:56:48,520
Like, okay, I know it's safe.

985
00:56:48,570 --> 00:56:52,800
It's been there for a long time, but I'm not going to use that.

986
00:56:52,910 --> 00:56:56,440
Like, that's just, like, I care a lot about where my software comes from.

987
00:56:57,460 --> 00:57:00,600
I like to verify, like, the hashes of where things come from,

988
00:57:00,820 --> 00:57:03,400
And so I'm not going to trust just some unofficial community flat pack.

989
00:57:04,179 --> 00:57:05,700
So it is a problem.

990
00:57:06,040 --> 00:57:10,440
And I'm glad that you guys are doing more than one thing, even though it's probably a pain in the ass.

991
00:57:10,870 --> 00:57:16,740
So it's interesting you say that because we try to solve this not by making another app store on Linux,

992
00:57:16,940 --> 00:57:18,680
because then they would have four app stores or whatever.

993
00:57:20,719 --> 00:57:26,060
But we have, so when you make like a pair app, which is what we call the peer-to-peer apps,

994
00:57:26,080 --> 00:57:27,660
that's why everything is called something with pair.

995
00:57:29,520 --> 00:57:34,100
Like I said, it's using 90% of this, between 90 and 99% of the same code always.

996
00:57:34,290 --> 00:57:39,400
And we have now tooling that targets all these different app stores and stuff.

997
00:57:40,400 --> 00:57:42,040
So that's how we distribute Keet.

998
00:57:42,200 --> 00:57:43,980
It's just like, it's a general pair app.

999
00:57:43,980 --> 00:57:50,740
And then we have a thing that produces whatever it needs to be in the Snap Store and an app image,

1000
00:57:50,910 --> 00:57:55,760
which is the old way and a flat pack that I don't know if we publish it, but we're going to publish and stuff like that.

1001
00:57:56,020 --> 00:57:58,420
But any kind of app built on the platform can do that

1002
00:57:58,480 --> 00:57:59,580
because an app in a peer-to-peer network

1003
00:57:59,740 --> 00:58:02,980
is actually just a cryptographic identifier of the app

1004
00:58:03,040 --> 00:58:05,060
and then the rest is pulled in by the network.

1005
00:58:06,880 --> 00:58:08,920
So if you're building and targeting things like that,

1006
00:58:08,980 --> 00:58:10,960
it actually can be really cool to do with peer-to-peer

1007
00:58:10,980 --> 00:58:12,360
because you get a lot of stuff for free.

1008
00:58:12,440 --> 00:58:14,740
It's almost like how when you make a website,

1009
00:58:14,960 --> 00:58:17,000
you don't really have to think so much about browsers

1010
00:58:17,280 --> 00:58:18,340
because you just know they exist.

1011
00:58:18,540 --> 00:58:19,580
And if you just have the link, it works.

1012
00:58:20,220 --> 00:58:21,440
That's kind of like how we're trying to do it

1013
00:58:21,440 --> 00:58:23,080
for peer-to-peer app development,

1014
00:58:23,240 --> 00:58:25,520
but it's also for native apps and stuff like that.

1015
00:58:26,000 --> 00:58:29,880
Kind of zooming back out a little bit and bringing everything together.

1016
00:58:30,370 --> 00:58:32,760
So I had a couple of questions come up as we were going.

1017
00:58:33,550 --> 00:58:40,740
So what are your thoughts on just companies in general who use P2P, but in a kind of hybrid, still centralized way?

1018
00:58:41,060 --> 00:58:49,900
So various examples, you know, some you did mention games earlier, but I still see it to this day how some Steam games will use peer-to-peer for app updates.

1019
00:58:50,240 --> 00:58:54,160
And actually, sometimes that can cause issues for people and they have to do things on the router.

1020
00:58:54,660 --> 00:58:55,900
And I'm sure that's a mess there.

1021
00:58:56,220 --> 00:59:01,180
But also even messengers, WhatsApp still has P2P for some calls.

1022
00:59:01,700 --> 00:59:03,940
And also Telegram does this, Signal does this.

1023
00:59:04,080 --> 00:59:08,600
A lot of these companies kind of pick and choose where to use P2P technology.

1024
00:59:09,240 --> 00:59:11,140
Do you see still an issue with that?

1025
00:59:11,190 --> 00:59:14,400
Do you think it's still good that they're embracing P2P in different places?

1026
00:59:14,550 --> 00:59:18,560
Or do you think a pure P2P approach is kind of the only way forward?

1027
00:59:18,860 --> 00:59:23,320
So I don't think there's a way to use P2P strictly wrongly.

1028
00:59:23,500 --> 00:59:26,520
It's a set of tools that you can kind of pick and choose.

1029
00:59:27,380 --> 00:59:32,500
I think the way I would describe most of the ways you said there,

1030
00:59:33,040 --> 00:59:35,220
to some degree or at least the vast majority of them,

1031
00:59:35,680 --> 00:59:38,700
is that it's cost optimization games.

1032
00:59:39,620 --> 00:59:42,500
So the reason why a lot of people do calls peer-to-peer

1033
00:59:42,520 --> 00:59:45,000
is because it's just very bandwidth-heavy to do a call.

1034
00:59:45,050 --> 00:59:49,680
So if you just put a dollar amount on what recording this podcast costs

1035
00:59:49,690 --> 00:59:52,980
in terms of bandwidth, it would be something that's like,

1036
00:59:53,300 --> 00:59:56,440
not bankrupt us, but it would be something where you're like, oh, that's interesting.

1037
00:59:58,539 --> 01:00:02,120
So there's some things where you just realistically have to try and do it,

1038
01:00:02,120 --> 01:00:06,920
and that's why a lot of people do it with calls and stuff like that.

1039
01:00:06,990 --> 01:00:10,700
The flip side of that is, I think, is that when you go extreme with it,

1040
01:00:11,020 --> 01:00:12,160
that's where the interesting things happen.

1041
01:00:12,510 --> 01:00:15,800
It's kind of like when you don't just do it for cost optimization,

1042
01:00:16,260 --> 01:00:19,540
but also start doing it into this unregulated, in a good way,

1043
01:00:19,900 --> 01:00:24,680
fusion of an app that can do all kinds of things that is like truly unscalable and unstoppable.

1044
01:00:25,290 --> 01:00:29,200
Then you start to think about this like cost of optimization in a whole different way,

1045
01:00:29,250 --> 01:00:33,480
like a concept before where like, well, if nothing costs anything, because everything

1046
01:00:33,620 --> 01:00:36,540
disappeared, you can also think about products in different ways because you can add interesting

1047
01:00:36,720 --> 01:00:41,940
things like why is, you know, a lot of services when I upload a file, it will be like, well,

1048
01:00:42,040 --> 01:00:45,240
it has to be 30 megabytes and everybody kind of just accepts that it's 30 megabytes.

1049
01:00:45,460 --> 01:00:48,160
And when I email something that's too big, my email will say, you can't do that.

1050
01:00:48,400 --> 01:00:51,000
And often you can even pay for it and it will be like, you still can't do that.

1051
01:00:51,260 --> 01:00:58,160
That's just kind of like this Stockholm syndrome we all have with centralization where we can't just say, oh, yeah, that's true.

1052
01:00:58,280 --> 01:01:01,560
And I guarantee you, I can even ask my parents, they will say, well, that's just how it is.

1053
01:01:02,340 --> 01:01:07,140
Because we're not thinking about this technology in like this unhinged way, which we need to do.

1054
01:01:07,890 --> 01:01:11,200
So once you start to go down the road, I think just much more interesting things start to happen.

1055
01:01:11,270 --> 01:01:12,780
And you just think about products in a whole different way.

1056
01:01:13,520 --> 01:01:18,760
And you also think about products in a way that's a bit more scary for companies, I think, to some degree,

1057
01:01:18,940 --> 01:01:22,980
because it's where you quickly optimize yourself out of the equation, which is why a lot of people don't do it.

1058
01:01:23,060 --> 01:01:26,640
Because if everything is distributed and peer-to-peer, then why do you exist?

1059
01:01:26,860 --> 01:01:29,400
Because the app can just, like I said, keep existing if you go bankrupt.

1060
01:01:29,860 --> 01:01:31,620
So yeah, but I don't think there's a wrong way of doing it.

1061
01:01:32,000 --> 01:01:35,840
I do think a lot of the stuff, messing around with your router and stuff,

1062
01:01:35,860 --> 01:01:39,700
is just because it's kind of tagged on and not fought into as a pure thing.

1063
01:01:39,920 --> 01:01:42,400
That's kind of where the technology starts to bubble up to the user.

1064
01:01:42,560 --> 01:01:43,120
That's not so good.

1065
01:01:43,820 --> 01:01:47,980
and there's like plenty of ways if you do like peer-to-peer right where you can avoid that but

1066
01:01:47,980 --> 01:01:52,740
yeah for sure you know are there any downsides especially you know when i think about in the

1067
01:01:53,100 --> 01:01:58,780
context of signal um one of the criticisms of signal is and telegram and whatsapp they all do

1068
01:01:58,780 --> 01:02:04,880
the same thing by default they do opt you in to this peer-to-peer aspect which also means that you

1069
01:02:04,980 --> 01:02:09,679
are exposing your ip address to the other person when you're doing a phone call and so if this is

1070
01:02:09,700 --> 01:02:13,680
something anyone's concerned about, you can just go into your signal account and just

1071
01:02:14,360 --> 01:02:19,340
toggle it on to always proxy it through the server. But my assumption is you can't do that with

1072
01:02:19,450 --> 01:02:24,020
something like heat or do you now have to use other P2P technologies like Tor and other things to

1073
01:02:24,170 --> 01:02:28,460
protect people's IP address? Yeah, P2P networks obviously inherently mean that we're connecting

1074
01:02:28,490 --> 01:02:34,620
to each other so we can, in some of those cases, see each other's addresses and stuff, also some

1075
01:02:34,790 --> 01:02:39,159
others. But I think it's one of those things where there's plenty of tools out there that are

1076
01:02:39,180 --> 01:02:43,400
pretty good, that layer pretty well, including VPNs, which are a good way

1077
01:02:43,460 --> 01:02:47,100
if you're very concerned about that, or even just normally concerned to

1078
01:02:47,600 --> 01:02:51,120
limit your exposure to anything. I would say

1079
01:02:51,500 --> 01:02:53,980
this is what I tell people also, or what I tell my parents,

1080
01:02:55,620 --> 01:02:58,040
if that's something where, in the context

1081
01:02:58,140 --> 01:03:01,920
of how you're using the apps and products, it's something you should be thinking about

1082
01:03:01,980 --> 01:03:05,120
in general, not pick and choose your features. I think that's a little bit dangerous.

1083
01:03:05,980 --> 01:03:09,360
So basically, if you're generally concerned about that, always use a VPN.

1084
01:03:10,400 --> 01:03:14,480
Because you're going to have IP exposure in the way you can't even imagine.

1085
01:03:14,630 --> 01:03:18,940
And it's kind of like it doesn't take a lot, you know, like tracking pixels, whatever, and things like that.

1086
01:03:19,520 --> 01:03:23,620
So in general, it's a good idea to be thinking about these things online.

1087
01:03:23,730 --> 01:03:25,240
And it's like there's plenty of scalable things.

1088
01:03:25,270 --> 01:03:26,560
We actually have a side project.

1089
01:03:26,630 --> 01:03:32,060
We're also working on a little peer-to-peer VPN for the same reasons because it's also a cool way to do it.

1090
01:03:34,600 --> 01:03:36,540
The opposite side of that is like in a P2P network,

1091
01:03:36,840 --> 01:03:37,780
you have more control.

1092
01:03:38,020 --> 01:03:39,260
So you can kind of like, for example,

1093
01:03:39,400 --> 01:03:41,040
when we talk about pair paths and stuff like that,

1094
01:03:42,400 --> 01:03:43,640
a network where you're sharing with yourself,

1095
01:03:44,000 --> 01:03:45,480
I would never think about it personally

1096
01:03:45,680 --> 01:03:46,980
because it's kind of like I'm just talking to myself.

1097
01:03:47,360 --> 01:03:47,880
It doesn't matter.

1098
01:03:49,180 --> 01:03:51,000
And like chat rooms with my family and stuff like that,

1099
01:03:51,000 --> 01:03:51,820
I also don't care.

1100
01:03:51,940 --> 01:03:54,000
And also me as a, you know, right now,

1101
01:03:54,579 --> 01:03:56,640
you can just kind of see my office and stuff

1102
01:03:56,700 --> 01:03:57,600
and we talked about where I am.

1103
01:03:57,640 --> 01:03:59,160
It's also like different kind of concerns.

1104
01:03:59,320 --> 01:03:59,940
So you kind of like, you know,

1105
01:04:00,380 --> 01:04:01,640
you need to use your brain a little bit,

1106
01:04:01,700 --> 01:04:04,020
but in general, there's plenty of really good tools out there.

1107
01:04:04,140 --> 01:04:09,640
like VPNs to ensure just that this is solved for everything you do online, which you should

1108
01:04:09,650 --> 01:04:10,200
be thinking about.

1109
01:04:12,240 --> 01:04:14,920
It's kind of like a consequence of how the protocols of the internet work, I guess.

1110
01:04:15,560 --> 01:04:15,700
Yeah.

1111
01:04:15,830 --> 01:04:20,140
So if two people are using KEEP, by default, they can see each other's IP address.

1112
01:04:20,700 --> 01:04:25,220
And then if they're concerned about that, then use a VPN or proxies.

1113
01:04:25,480 --> 01:04:25,720
Yeah.

1114
01:04:25,930 --> 01:04:27,700
I didn't mean not to say that.

1115
01:04:27,850 --> 01:04:27,940
Yeah.

1116
01:04:28,030 --> 01:04:28,720
So basically...

1117
01:04:28,720 --> 01:04:29,000
No, no, no.

1118
01:04:29,040 --> 01:04:30,060
I didn't really ask that.

1119
01:04:32,520 --> 01:04:35,660
The people you're talking to in a room could probably see your address if they knew what they were doing.

1120
01:04:35,760 --> 01:04:39,240
There were also plenty of ways in P2P networks where they don't have to do that.

1121
01:04:39,320 --> 01:04:42,180
Because actually in a P2P network, you don't have to connect directly.

1122
01:04:42,280 --> 01:04:44,360
You can do stuff where you route traffic through other people.

1123
01:04:44,380 --> 01:04:46,660
So you can build these crazy protocols that you want.

1124
01:04:47,840 --> 01:04:48,320
That's pretty cool.

1125
01:04:49,080 --> 01:04:49,980
So you have all the options.

1126
01:04:50,260 --> 01:04:52,680
But again, it's good to think about it in that way.

1127
01:04:52,780 --> 01:04:57,140
And there's definitely always a chance, depending on how the technology is put together.

1128
01:04:57,400 --> 01:04:57,860
So, yeah.

1129
01:04:58,620 --> 01:05:11,000
A very random question that came to me as we were talking is Apple's Find My Network, which uses Bluetooth between devices, technically P2P, or is that mesh? Is mesh different from P2P? Or am I?

1130
01:05:11,060 --> 01:05:27,240
So my definition of peer-to-peer is pretty broad because I think peer-to-peer to some degree is kind of like saying you, instead of relying on where data lives at a destination point of view, it's kind of like, you know, when I go to google.com, I'm putting in the destination, like the address of google, google.com.

1131
01:05:27,740 --> 01:05:30,180
And it's implying that I'm going to Google's server and doing something.

1132
01:05:30,330 --> 01:05:31,420
So that's not peer-to-peer for me.

1133
01:05:31,980 --> 01:05:34,400
But as soon as you take that coupling out of the equation and say,

1134
01:05:34,920 --> 01:05:37,440
it's not about where it is, it's about what it can prove,

1135
01:05:38,740 --> 01:05:40,460
then things start to become peer-to-peer for me

1136
01:05:40,530 --> 01:05:43,080
because then the rest, by definition, kind of comes from there,

1137
01:05:43,260 --> 01:05:44,420
like direct connection and stuff like that,

1138
01:05:44,430 --> 01:05:45,860
or even not because it doesn't matter.

1139
01:05:47,319 --> 01:05:51,220
So I don't know if Apple put on a bunch of specs on how that actually works,

1140
01:05:52,140 --> 01:05:53,860
but it's actually hard to answer.

1141
01:05:54,900 --> 01:06:04,820
The TLDR, as far as I don't know, I'm not an expert on this, but essentially any person with an iPhone that has Bluetooth on, their device is opted into this network.

1142
01:06:05,410 --> 01:06:08,720
And that's how AirTags work.

1143
01:06:09,070 --> 01:06:10,820
Because AirTags don't have GPS chips on them.

1144
01:06:11,140 --> 01:06:12,080
And all they have is a battery.

1145
01:06:12,190 --> 01:06:14,900
And it essentially is always pinging to see if it can find a phone.

1146
01:06:15,010 --> 01:06:18,180
And then that essentially functions as a way to track that device.

1147
01:06:18,800 --> 01:06:21,960
I would imagine that Apple does a bunch of cryptography things like that to try to make that private.

1148
01:06:22,320 --> 01:06:22,380
Yeah.

1149
01:06:22,600 --> 01:06:23,700
Generally what they try to do.

1150
01:06:23,720 --> 01:06:25,080
It's somewhat privacy respecting.

1151
01:06:25,580 --> 01:06:25,700
Yeah.

1152
01:06:25,880 --> 01:06:28,400
So I would, that's definitely a mesh network.

1153
01:06:28,520 --> 01:06:30,220
And I would also say, for my definition,

1154
01:06:30,580 --> 01:06:33,480
that's some, you know, variation of a P2P network in that sense

1155
01:06:33,620 --> 01:06:37,460
where, like, that's probably just a proof that it came from that device,

1156
01:06:37,720 --> 01:06:39,460
not where the device is address-wise.

1157
01:06:39,940 --> 01:06:41,640
So that's interesting.

1158
01:06:41,920 --> 01:06:44,520
I think it's also just worth noting on that, like,

1159
01:06:45,680 --> 01:06:48,960
for the same definition, you can also build not a centralized systems,

1160
01:06:49,020 --> 01:06:51,180
but you can build systems in the P2P world where, you know,

1161
01:06:51,340 --> 01:06:56,140
there is like a service running somewhere that you contact as long as you just, again, contact that

1162
01:06:56,220 --> 01:07:02,180
through some way where the service describes, you know, this is my data or like this is my

1163
01:07:02,540 --> 01:07:07,460
authentication versus like my address. So you can put all kinds of cool effects with that. But yeah,

1164
01:07:09,260 --> 01:07:13,660
sounds within the target, I think. Yeah. And I might have gotten some details

1165
01:07:13,820 --> 01:07:18,100
wrong. So if somebody wants to correct me, please do. I wanted to ask about environmental differences,

1166
01:07:18,520 --> 01:07:22,620
Because there's a lot of talk about centralized servers, especially now with AI.

1167
01:07:23,740 --> 01:07:29,940
And I'm seeing a lot more headlines and news coverage that even though we were finally moving in a renewable direction,

1168
01:07:30,580 --> 01:07:34,060
and we were saying, well, yeah, renewables are great.

1169
01:07:34,100 --> 01:07:40,400
We're starting to see coal uptick again because of a lot of the heavy demand that we're seeing for things like AI and these data servers.

1170
01:07:42,020 --> 01:07:46,300
So what's the environmental footprint difference, if any, with a peer-to-peer network?

1171
01:07:46,920 --> 01:07:50,120
Since it's distributed across many people, I guess I could see it going either way.

1172
01:07:50,360 --> 01:07:54,820
You know, if it's distributed equally across many people, maybe then it's lower energy usage.

1173
01:07:54,990 --> 01:07:59,220
But maybe having it centralized where things can be hyper-optimized is also better.

1174
01:07:59,350 --> 01:08:00,640
So do you know about this?

1175
01:08:00,890 --> 01:08:03,180
Is this something that has been studied at all?

1176
01:08:04,220 --> 01:08:07,220
I'm sure there is studies around the actual details of it.

1177
01:08:07,220 --> 01:08:08,780
I can't remember the exact things.

1178
01:08:09,340 --> 01:08:15,760
Also, I recently, it's actually funny because just before this call, somebody sent me an article about how much compute,

1179
01:08:16,440 --> 01:08:19,600
on average, like an AI generated image burns today and like put it in,

1180
01:08:19,839 --> 01:08:23,240
put it in context of like kilometers traveled in a car. And this,

1181
01:08:24,850 --> 01:08:27,759
I mean, I knew it was energy consuming, but it's surprisingly eyeopening.

1182
01:08:28,640 --> 01:08:33,000
But yes, definitely stuff to do there for whoever's working on that.

1183
01:08:33,259 --> 01:08:35,279
PHP networks is like, you know, by design,

1184
01:08:36,040 --> 01:08:39,080
cutting out the middleman pretty optimal because like you can build networks

1185
01:08:40,330 --> 01:08:42,660
where, especially in these kinds of environments,

1186
01:08:43,060 --> 01:08:49,359
like a chat where a lot of chat at the end of the day is very physically correlated also, right?

1187
01:08:49,440 --> 01:08:50,660
It's kind of like you chat a lot with your family.

1188
01:08:51,029 --> 01:08:52,600
Your family tends to be in the same places.

1189
01:08:54,660 --> 01:08:57,180
Cities have networks also, like your friends are usually in the same cities.

1190
01:08:57,270 --> 01:09:00,680
And then obviously there's these exceptions where you do these long random jumps everywhere.

1191
01:09:00,850 --> 01:09:02,640
But like things tend to be very clustered.

1192
01:09:03,960 --> 01:09:07,420
So just kind of like in terms of compute needs to be burned,

1193
01:09:07,569 --> 01:09:09,799
that network is very, very efficient.

1194
01:09:10,120 --> 01:09:11,520
Because again, we have the devices already.

1195
01:09:11,890 --> 01:09:12,880
And the device is already running.

1196
01:09:13,080 --> 01:09:22,359
And it's like, I've had people, especially in the early days of P2P, ask me concerns about like, well, if it's encrypted, then, you know, we need to run the encryption on the device.

1197
01:09:22,410 --> 01:09:25,240
And that sounds expensive in terms of energy and stuff.

1198
01:09:25,390 --> 01:09:31,859
But then when you're talking to servers today anyway, it's also in-flight encrypted because that's kind of like where the world moves.

1199
01:09:31,910 --> 01:09:32,779
So we're doing that anyway.

1200
01:09:32,930 --> 01:09:39,960
So it's actually the cost today is really, really small, as in like comparable on the transport.

1201
01:09:40,040 --> 01:09:43,020
but then we don't have to transport both not very far

1202
01:09:43,359 --> 01:09:45,839
and also not a lot because we try to be efficient.

1203
01:09:46,569 --> 01:09:48,940
So it can be built incredibly energy efficient,

1204
01:09:49,859 --> 01:09:51,120
which is really, really important.

1205
01:09:51,520 --> 01:09:54,380
Now, totally consider, I actually don't know the data on that.

1206
01:09:54,520 --> 01:09:55,980
There are some things that are obviously,

1207
01:09:56,290 --> 01:09:58,160
when you do it like big scale, it can be better,

1208
01:09:58,360 --> 01:10:00,220
but it tends to be more big compute things.

1209
01:10:00,900 --> 01:10:02,980
But also, like I said, you can also build variations

1210
01:10:03,180 --> 01:10:04,940
of P2P networks where you have services to do more.

1211
01:10:05,480 --> 01:10:08,819
So I think in general, you can just build P2P networks

1212
01:10:08,840 --> 01:10:10,480
in a way that can be extremely energy efficient

1213
01:10:10,570 --> 01:10:12,820
in a way where you just can't do it with centralized solution

1214
01:10:12,980 --> 01:10:15,600
just because the implication of the centralized solution

1215
01:10:15,800 --> 01:10:18,220
means that the stuff has to travel back and forth

1216
01:10:18,290 --> 01:10:19,800
and you need to have both the end devices

1217
01:10:20,020 --> 01:10:21,320
and the big things and stuff like that.

1218
01:10:22,240 --> 01:10:23,840
Whereas P2P just gives you more options.

1219
01:10:23,910 --> 01:10:26,420
But again, you can do variations of that,

1220
01:10:26,540 --> 01:10:28,560
but you can definitely make it very, very energy efficient

1221
01:10:28,980 --> 01:10:31,220
because otherwise also we couldn't do it on device.

1222
01:10:32,880 --> 01:10:34,040
So super, super interesting.

1223
01:10:34,130 --> 01:10:35,740
But I think it's also worth thinking about,

1224
01:10:35,750 --> 01:10:36,780
and we didn't really talk about that,

1225
01:10:36,880 --> 01:10:39,520
but also just in this context of like energy efficiency and data traveling,

1226
01:10:39,800 --> 01:10:40,740
even more than that also,

1227
01:10:41,660 --> 01:10:43,840
it's kind of like when things break,

1228
01:10:44,020 --> 01:10:45,920
like cables break or like, you know,

1229
01:10:46,700 --> 01:10:48,320
there's a natural disaster somewhere,

1230
01:10:48,980 --> 01:10:50,140
you know, the power goes out.

1231
01:10:51,020 --> 01:10:53,400
You really want these things to still work, right?

1232
01:10:53,500 --> 01:10:56,200
And so it's kind of like peer-to-peer is the only way for that

1233
01:10:56,400 --> 01:11:00,040
because otherwise this weakness also makes it very centralized,

1234
01:11:00,420 --> 01:11:01,940
just stops things really fast.

1235
01:11:02,040 --> 01:11:04,060
And there's been countless examples of that recently.

1236
01:11:04,320 --> 01:11:06,040
So, yeah, definitely.

1237
01:11:07,240 --> 01:11:12,160
Yeah, it seems like it just democratizes energy and accessibility a little bit more than a traditional system.

1238
01:11:12,620 --> 01:11:15,240
Yeah, we have tons of batteries over on our devices.

1239
01:11:15,430 --> 01:11:20,080
And if you ever looked at how much, it's actually a very interesting metric.

1240
01:11:20,560 --> 01:11:25,300
Because I remember I drive an electric car and at one time I was charging and I was kind of thinking,

1241
01:11:25,570 --> 01:11:30,260
I wonder just from a naive thought, how much power does my phone use compared to my car?

1242
01:11:30,520 --> 01:11:38,500
And then when you looked it up, you're like, holy moly, like your car is just like a bajillion times less efficient, a lot efficient by consuming.

1243
01:11:40,340 --> 01:11:45,160
So like running our chat app distributed is just so much more efficient than doing anything else in the world.

1244
01:11:45,270 --> 01:11:47,000
So like, yeah, 100%.

1245
01:11:47,040 --> 01:11:48,280
Yeah, I guess the final question.

1246
01:11:48,530 --> 01:11:57,760
So when Elon Musk goes on Twitter and says, hey, go download Signal, Signal goes down for hours because of the overwhelming number of people.

1247
01:11:58,220 --> 01:12:02,280
So if that were to happen to something like Keat, I assume, would the inverse happen?

1248
01:12:02,780 --> 01:12:04,880
Or would it just be stable?

1249
01:12:05,040 --> 01:12:07,580
Does the network get stronger when more people join?

1250
01:12:08,760 --> 01:12:08,960
Yeah.

1251
01:12:09,660 --> 01:12:12,940
So, I mean, it's like, the short answer is yes.

1252
01:12:13,660 --> 01:12:15,920
Like I said, we just recently had a big influx of users.

1253
01:12:15,960 --> 01:12:23,540
It's been very interesting to see because the things that were actually the hardest with having a big influx was just like we have some public rooms that started being very, very active.

1254
01:12:23,660 --> 01:12:27,220
So just kind of like the app was working, but the chat was running really fast.

1255
01:12:27,360 --> 01:12:30,360
So it's kind of like it's not very useful to be in that room, you know what I mean?

1256
01:12:30,410 --> 01:12:35,740
So it's kind of like there's a lot of these UX things we tend to forget sometimes that we're working really hard on.

1257
01:12:36,240 --> 01:12:40,260
But in general, yeah, it's like the network scales up as no people join.

1258
01:12:40,410 --> 01:12:44,320
And I tend to sleep pretty well at night thinking that because that makes my life a little bit easier.

1259
01:12:44,360 --> 01:12:46,280
It also makes it a little bit harder because it never goes down.

1260
01:12:46,410 --> 01:12:50,140
So there's very few breaks when you're like trying to do stuff.

1261
01:12:50,540 --> 01:12:52,260
But yeah, that's the future, I guess.

1262
01:12:52,740 --> 01:12:56,740
Yeah, and so if people want to check out what you guys are doing and try it out for themselves,

1263
01:12:57,380 --> 01:12:59,820
or at least look into the code or something like this, where can they find you guys?

1264
01:13:00,480 --> 01:13:04,980
So we have a website, like I said, our only website, two websites, sorry.

1265
01:13:05,040 --> 01:13:09,360
We have KID.io, which is our chat app, where you can go check out the chat app.

1266
01:13:09,520 --> 01:13:13,740
We have a bunch of very active development rooms on there also that's linked when you start the app,

1267
01:13:13,760 --> 01:13:15,840
so it gives you a suggestion to join these public rooms.

1268
01:13:16,140 --> 01:13:19,140
We have a lot of developers hanging in those and helping people building things

1269
01:13:19,180 --> 01:13:21,420
and just people sharing all kinds of crazy things. It's really fun.

1270
01:13:21,640 --> 01:13:22,500
So kit.io for that.

1271
01:13:23,380 --> 01:13:24,480
There you will download the app.

1272
01:13:24,510 --> 01:13:26,220
So you only go to the website to get the app

1273
01:13:26,220 --> 01:13:27,920
and then you'll be in the P2P network after that.

1274
01:13:28,520 --> 01:13:31,040
And then we have pairs.com like the fruit,

1275
01:13:32,620 --> 01:13:35,260
which is where we have our general development documentation

1276
01:13:35,560 --> 01:13:36,040
for our runtime.

1277
01:13:36,540 --> 01:13:38,640
And also we have a link there to pair pass.

1278
01:13:39,360 --> 01:13:42,720
And that link for that is pair pass.pares.com

1279
01:13:42,860 --> 01:13:43,960
or is it pass.pares.com?

1280
01:13:43,960 --> 01:13:44,300
I can't remember.

1281
01:13:44,450 --> 01:13:46,580
But it's linked from there and go check that out.

1282
01:13:46,640 --> 01:13:47,200
It's super cool.

1283
01:13:48,340 --> 01:13:51,160
And like I said, I'm on kit 24-7.

1284
01:13:51,460 --> 01:13:52,880
That's the problem with the peer-to-peer app

1285
01:13:53,000 --> 01:13:53,800
because it never shuts down,

1286
01:13:54,240 --> 01:13:55,440
because it never goes down.

1287
01:13:55,680 --> 01:13:58,180
So you can also ask me all the questions on there.

1288
01:13:58,340 --> 01:13:59,800
I'm very active on there as well.

1289
01:14:00,200 --> 01:14:00,500
Very cool.

1290
01:14:00,780 --> 01:14:01,760
All right, well, I'll leave links down below.

1291
01:14:02,160 --> 01:14:03,240
And I want to thank you for your time.

1292
01:14:03,680 --> 01:14:04,940
And it's been very interesting.

1293
01:14:05,180 --> 01:14:06,020
I don't think I've had anyone

1294
01:14:06,200 --> 01:14:07,160
who's talked about peer-to-peer tech

1295
01:14:07,680 --> 01:14:08,340
on the podcast yet.

1296
01:14:08,580 --> 01:14:09,840
So thank you.

1297
01:14:09,980 --> 01:14:10,380
Thanks for having me.

1298
01:14:10,560 --> 01:14:11,960
And that is the interview.

1299
01:14:12,140 --> 01:14:14,080
I want to thank Matias for taking the time

1300
01:14:14,260 --> 01:14:16,340
to explain a little bit more about his life,

1301
01:14:16,540 --> 01:14:18,140
but also the services he's working on,

1302
01:14:18,200 --> 01:14:19,919
as well as what things probably look like

1303
01:14:19,940 --> 01:14:21,740
for other messengers out there as well.

1304
01:14:22,240 --> 01:14:23,520
I want to thank you all for listening

1305
01:14:23,860 --> 01:14:24,860
and empowering yourself

1306
01:14:25,200 --> 01:14:27,000
by learning more about the services you use

1307
01:14:27,120 --> 01:14:27,740
and how they work

1308
01:14:27,940 --> 01:14:29,180
so that you can make better decisions

1309
01:14:29,640 --> 01:14:30,500
for your digital freedom.

1310
01:14:30,680 --> 01:14:32,300
I also wanted to ask for your support

1311
01:14:32,540 --> 01:14:34,020
in making these podcasts happen.

1312
01:14:34,500 --> 01:14:36,260
These podcasts are currently unsponsored.

1313
01:14:36,320 --> 01:14:38,460
We don't really have a real revenue model for them

1314
01:14:38,640 --> 01:14:39,620
outside of ad revenue.

1315
01:14:39,760 --> 01:14:40,960
And so if you like what we're doing

1316
01:14:41,160 --> 01:14:42,940
and want to see it grow and continue to expand,

1317
01:14:43,500 --> 01:14:44,900
you can do that by supporting Techlore.

1318
01:14:44,980 --> 01:14:46,520
We have free ways to support us

1319
01:14:46,680 --> 01:14:47,400
down in the description

1320
01:14:47,660 --> 01:14:48,559
as well as paid ways

1321
01:14:48,620 --> 01:14:50,180
via becoming a Techlorian.

1322
01:14:50,420 --> 01:14:52,500
Becoming a Techlorian comes with really cool access

1323
01:14:52,600 --> 01:14:54,600
to certain perks that we've developed for all of you,

1324
01:14:55,020 --> 01:14:56,780
and you get to support our mission in the process.

1325
01:14:57,080 --> 01:14:58,760
So check that all out down in the description,

1326
01:14:59,160 --> 01:15:01,260
and I'll see you all next time on Techlor.