WEBVTT

1
00:00:01.760 --> 00:00:03.759
- Join us as we gather around the hedge,

2
00:00:03.759 --> 00:00:05.139
- where we dig into technology,

3
00:00:05.440 --> 00:00:08.160
- business, and culture with the finest minds in

4
00:00:08.160 --> 00:00:09.139
- computer networking.

5
00:00:20.974 --> 00:00:23.774
- Good morning, Tom. It's very sunny there for

6
00:00:23.774 --> 00:00:24.835
- this time of morning.

7
00:00:25.375 --> 00:00:26.754
- Yeah. Yeah. It is.

8
00:00:27.690 --> 00:00:29.630
- Crazy. And how is Audrey doing?

9
00:00:30.010 --> 00:00:32.429
- Audrey's doing good. She's loving the sun.

10
00:00:32.810 --> 00:00:34.750
- Audrey is the plant. Yeah.

11
00:00:36.969 --> 00:00:39.229
- We have named Tom's plant.

12
00:00:39.765 --> 00:00:42.484
- That's crazy. I know. Alright. And this morning,

13
00:00:42.484 --> 00:00:44.804
- we are joined by Constant. Constant, where are

14
00:00:44.804 --> 00:00:45.545
- you physically?

15
00:00:46.245 --> 00:00:46.905
- The Netherlands.

16
00:00:47.524 --> 00:00:50.085
- The Netherlands. Alright. Cool. It's not not sunny

17
00:00:50.085 --> 00:00:52.390
- over here, right, currently. So No. No. No.

18
00:00:52.390 --> 00:00:53.829
- No. No. It's the wrong time of year

19
00:00:53.829 --> 00:00:56.149
- for sunny in Netherlands. It's just gonna

20
00:00:57.109 --> 00:00:59.989
- it's it's it's just stereotypical rainy over here,

21
00:00:59.989 --> 00:01:02.630
- so it's normal. Oh, okay. Alright. I know

22
00:01:02.630 --> 00:01:04.069
- a couple of other folks who live in

23
00:01:04.069 --> 00:01:06.015
- The Netherlands. I don't... I think I've been

24
00:01:06.015 --> 00:01:08.415
- to Holland a couple of times, and... But

25
00:01:08.415 --> 00:01:09.935
- most of my time in that kind of

26
00:01:09.935 --> 00:01:10.435
- region

27
00:01:10.814 --> 00:01:13.774
- has been more spent in Greenland, believe it

28
00:01:13.774 --> 00:01:16.174
- or not, and Iceland. So it's a little...

29
00:01:16.174 --> 00:01:17.555
- That's that's a little different

30
00:01:17.935 --> 00:01:20.194
- than where you are, I think.

31
00:01:21.109 --> 00:01:22.490
- Greenland tends to be

32
00:01:23.030 --> 00:01:23.770
- much more,

33
00:01:25.030 --> 00:01:25.530
- snow

34
00:01:26.150 --> 00:01:27.609
- and much more wind

35
00:01:28.150 --> 00:01:30.490
- and not much in the way of rain,

36
00:01:30.630 --> 00:01:33.049
- it seems. It seems that you get more

37
00:01:33.974 --> 00:01:35.974
- high high winds. I remember sitting in the

38
00:01:35.974 --> 00:01:38.155
- hotel and watching the windows

39
00:01:38.614 --> 00:01:40.694
- in the office building across the street from

40
00:01:40.694 --> 00:01:42.055
- the hotel or down the street from the

41
00:01:42.055 --> 00:01:45.254
- hotel actually blowing in and out from the

42
00:01:45.254 --> 00:01:47.674
- wind speed. Like, the windows were actually bending

43
00:01:48.250 --> 00:01:51.049
- in and out. It's like, I wonder how

44
00:01:51.049 --> 00:01:53.709
- long that's gonna last before those windows just

45
00:01:53.849 --> 00:01:54.590
- pop out.

46
00:01:55.129 --> 00:01:56.030
- It was crazy.

47
00:01:57.049 --> 00:01:57.549
- Alright.

48
00:01:58.009 --> 00:02:00.250
- So this morning or this afternoon for you,

49
00:02:00.250 --> 00:02:02.329
- isn't it afternoon kind of for you? It

50
00:02:02.329 --> 00:02:04.605
- is. Yeah. Yeah. It's afternoon for you. Yeah.

51
00:02:04.765 --> 00:02:05.905
- We're gonna talk about.

52
00:02:07.484 --> 00:02:09.245
- And so I think the best thing to

53
00:02:09.245 --> 00:02:10.865
- do is to start with

54
00:02:11.485 --> 00:02:13.025
- some definition of what

55
00:02:13.564 --> 00:02:15.344
- is and what it does

56
00:02:16.030 --> 00:02:17.870
- because this is a little bit different of

57
00:02:17.870 --> 00:02:18.530
- a technology.

58
00:02:18.830 --> 00:02:21.969
- It's not network centric. It's it's a thing

59
00:02:22.349 --> 00:02:22.849
- that

60
00:02:23.150 --> 00:02:25.629
- I think we need to understand better because,

61
00:02:25.629 --> 00:02:27.550
- of course, we live in this world now

62
00:02:27.550 --> 00:02:28.689
- of social media

63
00:02:29.150 --> 00:02:29.650
- and,

64
00:02:31.685 --> 00:02:34.564
- public identity and and distributed identity and stuff

65
00:02:34.564 --> 00:02:37.044
- like that. So let's start there, Constant. How

66
00:02:37.044 --> 00:02:38.344
- would you describe Noster?

67
00:02:38.805 --> 00:02:39.784
- Sure. So,

68
00:02:41.604 --> 00:02:43.685
- I guess the the the the opening line

69
00:02:43.685 --> 00:02:46.185
- of the the the paper that introduced Noster,

70
00:02:46.485 --> 00:02:48.300
- is actually a pretty good description. The the

71
00:02:48.300 --> 00:02:49.500
- thing is I don't have it in front

72
00:02:49.500 --> 00:02:50.939
- of me, but, it's,

73
00:02:51.659 --> 00:02:54.060
- it's something along the lines of the the

74
00:02:54.060 --> 00:02:54.560
- simplest

75
00:02:54.860 --> 00:02:55.360
- possible

76
00:02:55.740 --> 00:02:56.240
- protocol

77
00:02:56.780 --> 00:02:57.520
- for open,

78
00:02:58.939 --> 00:03:01.040
- within Bracken social network

79
00:03:01.419 --> 00:03:01.919
- possible.

80
00:03:03.115 --> 00:03:05.194
- And then it goes into... So it's,

81
00:03:05.594 --> 00:03:08.414
- it uses signatures, so it's temper proof.

82
00:03:10.634 --> 00:03:12.794
- It doesn't, it's not it's not peer to

83
00:03:12.794 --> 00:03:13.935
- peer, so it works,

84
00:03:14.395 --> 00:03:15.599
- and a couple of other things.

85
00:03:16.159 --> 00:03:17.599
- What what it is, it's an it's an

86
00:03:17.599 --> 00:03:18.900
- open protocol for,

87
00:03:19.840 --> 00:03:20.340
- identity

88
00:03:20.719 --> 00:03:21.460
- and publication.

89
00:03:22.400 --> 00:03:22.900
- And,

90
00:03:24.159 --> 00:03:26.879
- from there, you can actually start to doing

91
00:03:26.879 --> 00:03:27.854
- a a lot of things.

92
00:03:28.574 --> 00:03:31.215
- It stands for notes and notes and other

93
00:03:31.215 --> 00:03:33.854
- stuff transmitted by Relay. So that's notes, n

94
00:03:33.854 --> 00:03:35.155
- o t e s.

95
00:03:36.655 --> 00:03:38.655
- So these are your publications. Right? So so

96
00:03:38.655 --> 00:03:40.974
- so it's, notes. There could be, like, tweets

97
00:03:40.974 --> 00:03:41.474
- initially,

98
00:03:41.909 --> 00:03:43.689
- but it could be all sorts of things.

99
00:03:44.949 --> 00:03:47.669
- And they're they're transmitted by relays. And in

100
00:03:47.669 --> 00:03:49.189
- in a nutshell, because you're... You have a

101
00:03:49.189 --> 00:03:52.009
- technical audience, it's it's signed JSON over WebSockets.

102
00:03:52.870 --> 00:03:54.709
- That... That's it. That... That's that's what it

103
00:03:54.709 --> 00:03:57.655
- is. It's just signed JSON over over WebSockets.

104
00:03:58.435 --> 00:03:59.334
- And it,

105
00:03:59.875 --> 00:04:00.375
- identified

106
00:04:00.754 --> 00:04:01.254
- that,

107
00:04:01.875 --> 00:04:03.474
- although there are a lot of problems with

108
00:04:03.474 --> 00:04:05.634
- with the web currently, and I guess you

109
00:04:05.634 --> 00:04:07.875
- can also venture into the Internet more broadly.

110
00:04:07.875 --> 00:04:09.439
- But let... Let's stick for the web right

111
00:04:09.439 --> 00:04:09.939
- now,

112
00:04:10.319 --> 00:04:12.480
- where we started to use platforms. Right? We

113
00:04:12.480 --> 00:04:14.800
- initially... We had the Internet. We we we

114
00:04:14.800 --> 00:04:17.439
- started to set up websites, but, apparently, setting

115
00:04:17.439 --> 00:04:18.879
- up your own website was too much of

116
00:04:18.879 --> 00:04:21.439
- a hassle, so we started to get accounts

117
00:04:21.439 --> 00:04:23.939
- on particular websites and set up pages there.

118
00:04:24.634 --> 00:04:26.715
- And from there, so this is MySpace on

119
00:04:26.715 --> 00:04:28.014
- later later Facebook.

120
00:04:28.795 --> 00:04:30.254
- And from there, we,

121
00:04:30.715 --> 00:04:33.835
- started to adopt platforms for basically everything that

122
00:04:33.835 --> 00:04:34.735
- we're doing.

123
00:04:35.514 --> 00:04:37.754
- So it'd be that YouTube for videos. Everything

124
00:04:37.754 --> 00:04:39.529
- has its its its vertical niche. Right? You

125
00:04:39.529 --> 00:04:42.189
- have your taxis that's done via Uber or,

126
00:04:42.889 --> 00:04:45.449
- I... And so on and so on. So

127
00:04:45.449 --> 00:04:47.389
- what Nostra does, it it basically

128
00:04:48.009 --> 00:04:50.110
- dissolves this this platform based,

129
00:04:51.814 --> 00:04:52.555
- web paradigm

130
00:04:53.014 --> 00:04:54.634
- and introduces a new paradigm,

131
00:04:56.375 --> 00:04:58.454
- that is actually a lot better. So it's

132
00:04:58.454 --> 00:05:00.535
- it's not just, the the point of it

133
00:05:00.535 --> 00:05:03.035
- initially is, like, to create, like, censorship resistant,

134
00:05:04.375 --> 00:05:05.354
- social networking.

135
00:05:06.620 --> 00:05:08.379
- That would be, like, the the the brand

136
00:05:08.379 --> 00:05:08.879
- phrase.

137
00:05:09.819 --> 00:05:10.319
- But

138
00:05:11.100 --> 00:05:13.100
- what it actually does, it it just,

139
00:05:13.580 --> 00:05:16.300
- introduces a a a better system altogether in

140
00:05:16.300 --> 00:05:18.319
- order to organize ourselves on the web,

141
00:05:18.699 --> 00:05:19.759
- not using platforms.

142
00:05:20.474 --> 00:05:23.514
- Right. And, the... It does so using sign

143
00:05:23.514 --> 00:05:24.574
- JSON over WebSockets.

144
00:05:25.194 --> 00:05:27.354
- Okay. So if we back up, I think

145
00:05:27.354 --> 00:05:27.854
- that

146
00:05:28.154 --> 00:05:30.314
- if I were to describe the current web,

147
00:05:30.314 --> 00:05:31.854
- we started out with the idea

148
00:05:32.235 --> 00:05:33.854
- of having open transport,

149
00:05:34.899 --> 00:05:36.759
- but not open application

150
00:05:38.100 --> 00:05:39.800
- transport. Right? Like, open

151
00:05:40.259 --> 00:05:43.139
- data marshaling, open transport in the sense of

152
00:05:43.139 --> 00:05:44.199
- TCP, UDP,

153
00:05:44.660 --> 00:05:47.699
- even HTTP to some degree, and now quick

154
00:05:47.699 --> 00:05:48.839
- and blah blah blah.

155
00:05:49.220 --> 00:05:49.720
- And...

156
00:05:50.144 --> 00:05:50.644
- But

157
00:05:51.024 --> 00:05:53.985
- not in the way information itself is marshaled.

158
00:05:53.985 --> 00:05:55.764
- We didn't have an open presentation

159
00:05:56.064 --> 00:05:58.464
- layer, if you will. If you wanna go

160
00:05:58.464 --> 00:05:59.824
- to the USI model, which I'm not really

161
00:05:59.824 --> 00:06:01.904
- crazy about the USI model, but if that's

162
00:06:01.904 --> 00:06:04.019
- kind of the path you wanna take in

163
00:06:04.019 --> 00:06:06.339
- in describing it, that seems to be where

164
00:06:06.339 --> 00:06:07.079
- we started.

165
00:06:07.860 --> 00:06:09.800
- And where that developed was

166
00:06:10.180 --> 00:06:11.800
- even with things like email,

167
00:06:12.899 --> 00:06:14.439
- we ended up... It ended up being

168
00:06:15.379 --> 00:06:16.199
- too complex

169
00:06:16.579 --> 00:06:19.555
- over time to some degree and too troublesome

170
00:06:20.254 --> 00:06:22.814
- for people to run their own servers of

171
00:06:22.814 --> 00:06:23.555
- all kinds.

172
00:06:24.175 --> 00:06:25.314
- Like, DNS

173
00:06:25.694 --> 00:06:27.294
- was one of the first things to be

174
00:06:27.294 --> 00:06:27.794
- centralized,

175
00:06:28.654 --> 00:06:31.214
- because DNS became complex, and people didn't wanna

176
00:06:31.214 --> 00:06:33.870
- deal with it. And email was another one.

177
00:06:34.189 --> 00:06:34.689
- Right?

178
00:06:35.069 --> 00:06:35.569
- Like,

179
00:06:35.949 --> 00:06:38.350
- if you try... It's very bizarre. If you

180
00:06:38.350 --> 00:06:39.810
- try to get support

181
00:06:40.829 --> 00:06:43.169
- for open email standards today,

182
00:06:44.430 --> 00:06:45.810
- go find services

183
00:06:46.189 --> 00:06:47.169
- and applications

184
00:06:47.709 --> 00:06:48.370
- that run

185
00:06:48.845 --> 00:06:49.904
- on true SMTP

186
00:06:51.084 --> 00:06:51.985
- and etcetera,

187
00:06:52.604 --> 00:06:55.004
- and you will find that it's actually very

188
00:06:55.004 --> 00:06:55.504
- difficult.

189
00:06:56.285 --> 00:06:58.544
- There are no... There's no open calendaring.

190
00:06:59.004 --> 00:07:01.745
- There's no open... An email is largely

191
00:07:02.459 --> 00:07:04.560
- service based. You log in to a website.

192
00:07:05.180 --> 00:07:07.120
- If there's a client, it's proprietary.

193
00:07:08.139 --> 00:07:10.079
- So this is kind of where we've gone.

194
00:07:10.379 --> 00:07:11.899
- And the same thing, like you said, with

195
00:07:11.899 --> 00:07:13.759
- social media, the same thing with

196
00:07:14.139 --> 00:07:15.040
- even information

197
00:07:16.145 --> 00:07:19.285
- publication. We started out with websites and RSS

198
00:07:19.345 --> 00:07:22.064
- feeds. But I guess RSS feeds are too

199
00:07:22.064 --> 00:07:24.545
- hard for people, so they ended up going

200
00:07:24.545 --> 00:07:25.045
- to

201
00:07:25.904 --> 00:07:28.725
- x or Twitter and Facebook and

202
00:07:29.105 --> 00:07:31.045
- and all these other sites

203
00:07:31.504 --> 00:07:33.189
- and said, I'm gonna get all my information

204
00:07:33.189 --> 00:07:35.529
- feeds from them. Even going to individual

205
00:07:36.389 --> 00:07:37.850
- news sites or blogs

206
00:07:38.709 --> 00:07:40.729
- became, like, some kind of a burden.

207
00:07:41.509 --> 00:07:43.029
- And so we ended up with this kind

208
00:07:43.029 --> 00:07:44.169
- of very fragmented,

209
00:07:45.654 --> 00:07:48.295
- not really fragmented, but but fragmented as in

210
00:07:48.295 --> 00:07:51.194
- the terms of AOL versus CompuServe fragmentation

211
00:07:52.375 --> 00:07:53.995
- and all of these very proprietary

212
00:07:54.295 --> 00:07:56.535
- platforms. Well, I I would say we we...

213
00:07:56.535 --> 00:07:58.615
- It's not so so much fragmented as it

214
00:07:58.615 --> 00:08:01.050
- is centralized and siloed. So so we have

215
00:08:01.050 --> 00:08:02.750
- a cup Yeah. Okay. A bunch of silos

216
00:08:03.449 --> 00:08:04.750
- with with walls in between.

217
00:08:05.209 --> 00:08:05.709
- Right.

218
00:08:06.009 --> 00:08:06.750
- And so

219
00:08:07.209 --> 00:08:09.930
- what you're trying to do with in store

220
00:08:09.930 --> 00:08:12.810
- is you're trying to reverse that. Right? And,

221
00:08:12.810 --> 00:08:15.310
- basically, you're trying to move up the stack

222
00:08:15.944 --> 00:08:16.925
- and go beyond

223
00:08:18.105 --> 00:08:20.925
- TCP, UDP, and say, here is a standardized

224
00:08:21.305 --> 00:08:22.125
- data format

225
00:08:22.985 --> 00:08:24.604
- over which you can send anything.

226
00:08:25.865 --> 00:08:27.944
- Right? So... Yeah. So it's it's,

227
00:08:28.584 --> 00:08:29.964
- basically, the the conclusion.

228
00:08:30.949 --> 00:08:31.449
- So

229
00:08:31.910 --> 00:08:34.629
- the the analysis is basically what what you

230
00:08:34.629 --> 00:08:35.450
- already presented,

231
00:08:37.190 --> 00:08:37.690
- where,

232
00:08:38.470 --> 00:08:39.129
- a complexity

233
00:08:39.509 --> 00:08:41.450
- results in a lack of implementation.

234
00:08:43.365 --> 00:08:45.524
- And then it doesn't matter if your standard

235
00:08:45.524 --> 00:08:46.884
- is open or not, if you only have,

236
00:08:46.884 --> 00:08:49.125
- like, a handful of implementations or worse yet

237
00:08:49.125 --> 00:08:50.904
- only one dominant implementation.

238
00:08:52.164 --> 00:08:54.085
- Then it doesn't matter if your standard is

239
00:08:54.085 --> 00:08:56.245
- open because there's one party that's actually dictating

240
00:08:56.245 --> 00:08:57.465
- the de facto standard.

241
00:08:57.870 --> 00:08:58.370
- So,

242
00:08:59.470 --> 00:08:59.970
- the...

243
00:09:00.830 --> 00:09:03.090
- This this observation was made and therefore,

244
00:09:03.629 --> 00:09:06.289
- basically, the quest for the simplest possible protocol

245
00:09:06.350 --> 00:09:06.509
- was,

246
00:09:07.789 --> 00:09:08.610
- was initiated.

247
00:09:09.149 --> 00:09:11.389
- And the the the result here, that I

248
00:09:11.389 --> 00:09:12.850
- propose is is Nasser,

249
00:09:14.524 --> 00:09:15.024
- where,

250
00:09:17.004 --> 00:09:20.044
- it's three standards. Right? The the conclusion was,

251
00:09:20.044 --> 00:09:22.945
- okay. We need a a standard for cryptography,

252
00:09:24.284 --> 00:09:25.320
- in order to,

253
00:09:25.720 --> 00:09:28.519
- have these digital signatures and and verify them

254
00:09:28.519 --> 00:09:30.840
- and and some hashing going on in order

255
00:09:30.840 --> 00:09:31.980
- for the the

256
00:09:32.279 --> 00:09:33.019
- the data,

257
00:09:33.480 --> 00:09:34.700
- like, the the

258
00:09:35.240 --> 00:09:37.399
- data... What... What's it called? It's, like, against

259
00:09:37.399 --> 00:09:40.424
- temper proofing and the data validity, let's say,

260
00:09:40.504 --> 00:09:41.804
- and identity validity.

261
00:09:42.904 --> 00:09:45.705
- We need a standard for the data construct

262
00:09:45.705 --> 00:09:47.865
- itself. Okay. This is JSON. So for the

263
00:09:47.865 --> 00:09:50.345
- the cryptography, it ended up it ended up

264
00:09:50.345 --> 00:09:52.504
- borrowing what Bitcoin does, so it it uses

265
00:09:52.504 --> 00:09:53.325
- Schnorr signatures,

266
00:09:53.929 --> 00:09:55.629
- and SHA-two 56 for the hashing.

267
00:09:56.329 --> 00:09:57.230
- It it

268
00:09:57.610 --> 00:09:59.929
- took JSON for the data structure because it's

269
00:09:59.929 --> 00:10:02.889
- like, okay. This is, a fairly simple human

270
00:10:02.889 --> 00:10:05.850
- legible. Everybody... Most people sort of understand it's

271
00:10:05.850 --> 00:10:08.095
- it's it's widely known thing. We'll we'll pick

272
00:10:08.095 --> 00:10:09.934
- JSON. Could be anything else. Right? That's not...

273
00:10:09.934 --> 00:10:11.615
- The point is not the fact that you...

274
00:10:11.615 --> 00:10:13.774
- That it is JSON for the most part.

275
00:10:13.774 --> 00:10:15.695
- It's just we need to depict something, so,

276
00:10:15.695 --> 00:10:17.855
- okay, we'll just use JSON. And we don't

277
00:10:17.855 --> 00:10:20.654
- pick a a a binary encoding because nobody

278
00:10:20.654 --> 00:10:22.820
- on Earth is actually gonna read or understand

279
00:10:22.820 --> 00:10:25.059
- what's actually going on when we do that

280
00:10:25.059 --> 00:10:26.500
- despite the fact that it might be a

281
00:10:26.500 --> 00:10:27.879
- lot more efficient or whatever.

282
00:10:28.419 --> 00:10:30.500
- And then the last part is we need,

283
00:10:30.500 --> 00:10:32.980
- like, for the transport layer, we need some

284
00:10:32.980 --> 00:10:33.315
- some

285
00:10:34.995 --> 00:10:35.735
- that ended up being,

286
00:10:36.754 --> 00:10:39.414
- WebSockets with a very basic query language.

287
00:10:40.434 --> 00:10:42.615
- And those are the three standards, and

288
00:10:42.995 --> 00:10:43.495
- that's,

289
00:10:44.274 --> 00:10:47.075
- from a protocol perspective, that's what Nostra is.

290
00:10:47.075 --> 00:10:48.455
- So it's just those

291
00:10:48.799 --> 00:10:49.620
- three definitions.

292
00:10:50.639 --> 00:10:52.019
- And then on top of that,

293
00:10:52.799 --> 00:10:54.959
- it's like a free for all, in the

294
00:10:54.959 --> 00:10:58.339
- ability of creating whatever standard it is to...

295
00:10:58.559 --> 00:11:00.639
- For whatever application or use case it it

296
00:11:00.639 --> 00:11:02.399
- happened... It it happens to be that you're

297
00:11:02.399 --> 00:11:02.899
- solving.

298
00:11:04.324 --> 00:11:06.084
- And this is what we call NIPS, so

299
00:11:06.084 --> 00:11:06.904
- n I p.

300
00:11:07.524 --> 00:11:10.565
- And this is a Nasser implementation possibility. So

301
00:11:10.565 --> 00:11:12.245
- n I p number one is that the

302
00:11:12.245 --> 00:11:15.365
- base protocol spec, everybody is, supposed to follow

303
00:11:15.365 --> 00:11:15.865
- that.

304
00:11:16.725 --> 00:11:19.419
- And that's deliberately simple enough. So it's not

305
00:11:19.419 --> 00:11:20.959
- complicated to create whatever,

306
00:11:21.819 --> 00:11:24.139
- implementation you wanna write. And then you can

307
00:11:24.139 --> 00:11:24.959
- add whatever,

308
00:11:25.740 --> 00:11:28.059
- other nips on top of that, depending on

309
00:11:28.059 --> 00:11:29.679
- what it is that you're trying to do.

310
00:11:30.485 --> 00:11:32.325
- So what are the... What are some of

311
00:11:32.325 --> 00:11:33.144
- the applications

312
00:11:33.524 --> 00:11:35.684
- here? I mean, social networking seems to be

313
00:11:35.684 --> 00:11:37.625
- one of them, but what's the

314
00:11:38.164 --> 00:11:40.424
- what's the the valuable thing that,

315
00:11:41.044 --> 00:11:42.804
- that we would... That that people would use

316
00:11:42.804 --> 00:11:44.565
- this for instead of just, like, publishing a

317
00:11:44.565 --> 00:11:45.225
- web page?

318
00:11:46.440 --> 00:11:47.419
- So let's...

319
00:11:47.799 --> 00:11:48.620
- So initially,

320
00:11:49.480 --> 00:11:52.519
- the idea was because of how this, came

321
00:11:52.519 --> 00:11:55.259
- to be, it... It's very inspired by,

322
00:11:57.320 --> 00:11:58.860
- now it escapes me the protocol.

323
00:12:01.044 --> 00:12:03.465
- ScuttleBot. It wasn't very much inspired by ScuttleBot,

324
00:12:04.004 --> 00:12:07.065
- and the the reason for creating it was,

325
00:12:07.605 --> 00:12:09.365
- the problems going on with Twitter at the

326
00:12:09.365 --> 00:12:10.345
- time and censorship.

327
00:12:10.804 --> 00:12:11.304
- So,

328
00:12:12.019 --> 00:12:14.259
- the first application was very much Twitter like,

329
00:12:14.259 --> 00:12:16.600
- what... Which we... The general case called microblogging.

330
00:12:18.500 --> 00:12:19.000
- So

331
00:12:19.460 --> 00:12:21.860
- people created these these nips, these,

332
00:12:22.500 --> 00:12:24.340
- these standards for the stuff you need for

333
00:12:24.340 --> 00:12:27.735
- microblogging. So it's replying and reposting and likes

334
00:12:27.735 --> 00:12:28.235
- and,

335
00:12:28.774 --> 00:12:29.915
- all this type of stuff.

336
00:12:31.174 --> 00:12:31.995
- And then,

337
00:12:33.575 --> 00:12:35.495
- it started to evolve from there. And I

338
00:12:35.495 --> 00:12:37.595
- think a very good example of,

339
00:12:38.134 --> 00:12:38.634
- that

340
00:12:39.100 --> 00:12:41.179
- illustrates the power of Nostra because it's... Like

341
00:12:41.179 --> 00:12:42.860
- I said, it stands for notes and other

342
00:12:42.860 --> 00:12:44.299
- stuff. So this notes thing is like the

343
00:12:44.299 --> 00:12:46.220
- microblogging thing. Okay. So what is this other

344
00:12:46.220 --> 00:12:48.779
- stuff? Well, an... Another example of the other...

345
00:12:48.779 --> 00:12:50.480
- Of an example of the other stuff,

346
00:12:51.100 --> 00:12:53.524
- is what we're actually currently doing with, Git.

347
00:12:53.524 --> 00:12:55.144
- So we have Nostra Git,

348
00:12:56.245 --> 00:12:56.745
- where,

349
00:12:57.924 --> 00:13:00.084
- the the point here is that, okay, Git

350
00:13:00.084 --> 00:13:02.825
- has also been captured by platforms called GitHub.

351
00:13:05.589 --> 00:13:08.570
- Git itself is is already a, open,

352
00:13:09.429 --> 00:13:11.129
- and potentially decentralized,

353
00:13:11.750 --> 00:13:13.129
- or distributed system,

354
00:13:13.669 --> 00:13:16.230
- in how you run Git servers. But who's

355
00:13:16.230 --> 00:13:18.085
- gonna run a Git server? And then there's

356
00:13:18.085 --> 00:13:20.664
- a lot of coordination problems around git servers,

357
00:13:21.125 --> 00:13:23.605
- of finding the actual repository that you're looking

358
00:13:23.605 --> 00:13:25.125
- for depending on what what it is that

359
00:13:25.125 --> 00:13:26.024
- you're looking for.

360
00:13:26.965 --> 00:13:29.125
- And what Nasr does there, it just... So

361
00:13:29.125 --> 00:13:32.059
- it's not it's not running git with signed

362
00:13:32.059 --> 00:13:33.279
- JSON over WebSockets.

363
00:13:33.899 --> 00:13:35.500
- It it lets git be git, so you

364
00:13:35.500 --> 00:13:37.039
- just run a git server.

365
00:13:37.419 --> 00:13:38.639
- But all the actions,

366
00:13:39.580 --> 00:13:42.220
- for running the git server are done, over

367
00:13:42.220 --> 00:13:42.720
- Nostr.

368
00:13:43.580 --> 00:13:45.759
- And you also have these benefits, like, okay.

369
00:13:46.004 --> 00:13:48.165
- So now you have to, I'm I'm gonna

370
00:13:48.165 --> 00:13:49.605
- stack a couple of things. Right? So we

371
00:13:49.605 --> 00:13:50.884
- so we also have an app store where

372
00:13:50.884 --> 00:13:52.264
- you publish your your applications.

373
00:13:53.205 --> 00:13:55.705
- So now I'm gonna stack these things. You...

374
00:13:55.845 --> 00:13:57.445
- The identity on Nostr is based on a

375
00:13:57.445 --> 00:13:58.965
- key pair. So you just generate a key

376
00:13:58.965 --> 00:14:00.850
- pair on the fly. Okay. So now this

377
00:14:00.850 --> 00:14:02.470
- is my identity. I publish,

378
00:14:03.570 --> 00:14:05.029
- my... The... My first publication

379
00:14:05.490 --> 00:14:05.990
- is,

380
00:14:06.529 --> 00:14:08.629
- an event. We call these publications events.

381
00:14:09.169 --> 00:14:11.490
- My first publication is my name, my bio,

382
00:14:11.490 --> 00:14:13.274
- and my profile picture. Right? Okay.

383
00:14:13.835 --> 00:14:15.915
- And my declaration here is that I'm a

384
00:14:15.915 --> 00:14:18.894
- super cool developer. So mister super cool developer

385
00:14:18.955 --> 00:14:20.975
- now has a, has an identity,

386
00:14:21.355 --> 00:14:22.254
- on this protocol.

387
00:14:22.955 --> 00:14:23.455
- And,

388
00:14:23.835 --> 00:14:24.735
- what... Subsequently,

389
00:14:25.115 --> 00:14:27.355
- this super cool identity, spins up a git

390
00:14:27.355 --> 00:14:27.855
- server,

391
00:14:28.340 --> 00:14:30.100
- and this git server is now tied to

392
00:14:30.100 --> 00:14:32.019
- this to this key pair. So all the

393
00:14:32.019 --> 00:14:34.019
- changes and merges and stuff that happens is

394
00:14:34.019 --> 00:14:34.820
- gated by,

395
00:14:35.460 --> 00:14:36.740
- the fact that it has to be signed

396
00:14:36.740 --> 00:14:38.259
- by this key pair, or all the policy

397
00:14:38.259 --> 00:14:40.420
- rules that happens on this, git server are

398
00:14:40.420 --> 00:14:42.920
- gated by the, by by this key pair.

399
00:14:43.085 --> 00:14:45.404
- So now this this super cool developer, he

400
00:14:45.404 --> 00:14:47.884
- starts to create software that's that... That's now

401
00:14:47.884 --> 00:14:50.144
- hosted on this, on this Git server repository

402
00:14:50.684 --> 00:14:52.144
- and then decides to,

403
00:14:52.764 --> 00:14:55.004
- publish his app on the actual App Store,

404
00:14:55.004 --> 00:14:55.904
- which is also

405
00:14:56.429 --> 00:14:57.809
- just an assigned event.

406
00:14:58.190 --> 00:14:59.889
- So now... And then,

407
00:15:01.309 --> 00:15:03.230
- does a tweet about the... Like a Nostra

408
00:15:03.230 --> 00:15:04.529
- tweet, like a note, a

409
00:15:05.149 --> 00:15:07.789
- publication on on declaring. So I made this

410
00:15:07.789 --> 00:15:10.110
- I made this thing. So from the outside

411
00:15:10.110 --> 00:15:11.490
- looking in, I now have

412
00:15:11.804 --> 00:15:12.544
- one identity

413
00:15:13.004 --> 00:15:13.504
- that

414
00:15:13.884 --> 00:15:16.125
- directly is tied to both the code in

415
00:15:16.125 --> 00:15:18.044
- the code base on the repository on a

416
00:15:18.044 --> 00:15:18.784
- git server.

417
00:15:19.164 --> 00:15:22.205
- It is directly tied to the the the

418
00:15:22.205 --> 00:15:24.365
- APK for the the Android app that was

419
00:15:24.365 --> 00:15:25.335
- published on the,

420
00:15:27.139 --> 00:15:29.620
- on the on the App Store and directly

421
00:15:29.620 --> 00:15:32.759
- tied to the tweet that announces this thing,

422
00:15:33.139 --> 00:15:35.059
- to the world and maybe also directly tied

423
00:15:35.059 --> 00:15:37.059
- to the long form article that has, like,

424
00:15:37.059 --> 00:15:39.075
- a long description of whatever is going on.

425
00:15:39.394 --> 00:15:41.075
- So now you can start to understand. It's

426
00:15:41.075 --> 00:15:43.075
- like you ins... Because in the old model,

427
00:15:43.075 --> 00:15:45.475
- right, in the platform model, we have GitHub

428
00:15:45.475 --> 00:15:48.054
- with a GitHub account, and we have

429
00:15:48.514 --> 00:15:50.355
- Twitter with a Twitter account or an x

430
00:15:50.355 --> 00:15:52.750
- account. Right? And we have... What what else

431
00:15:52.750 --> 00:15:54.029
- do we have? We have a Substack with

432
00:15:54.029 --> 00:15:55.629
- a Substack account, and we have we have

433
00:15:55.629 --> 00:15:57.470
- all these different platforms, and they're all separate

434
00:15:57.470 --> 00:15:59.790
- accounts. Those accounts are not actually the same

435
00:15:59.790 --> 00:16:01.889
- thing. They're all they're all in these silos,

436
00:16:02.110 --> 00:16:04.675
- these segregated silos. So instead of having these

437
00:16:04.675 --> 00:16:06.615
- segregated silos, we have one identity

438
00:16:07.075 --> 00:16:09.715
- that all it did was just publish signed

439
00:16:09.715 --> 00:16:10.215
- JSON

440
00:16:10.915 --> 00:16:13.555
- to, to relays. We'll get into the relays

441
00:16:13.555 --> 00:16:14.055
- later.

442
00:16:14.754 --> 00:16:15.254
- But,

443
00:16:15.715 --> 00:16:18.434
- just made these publications, and I, from the

444
00:16:18.434 --> 00:16:20.215
- outside, I just follow this

445
00:16:20.809 --> 00:16:22.830
- I follow this this this developer.

446
00:16:23.450 --> 00:16:26.330
- And if I'm interested in his tweets, I

447
00:16:26.330 --> 00:16:28.649
- use an app that renders tweets, right, that

448
00:16:28.649 --> 00:16:30.570
- fetches tweets and just, like, okay. I see

449
00:16:30.570 --> 00:16:32.330
- the tweets, or I use an app that

450
00:16:32.330 --> 00:16:34.669
- renders and loads the the long form article

451
00:16:34.865 --> 00:16:37.024
- or an app that loads the the the,

452
00:16:37.424 --> 00:16:39.345
- the app that was published, which is an

453
00:16:39.345 --> 00:16:42.144
- App Store app or etcetera or, like,

454
00:16:42.784 --> 00:16:43.764
- a a a Git interface.

455
00:16:44.225 --> 00:16:47.259
- So now these... The identity is its thing

456
00:16:47.259 --> 00:16:49.339
- on its own. What the identity does, it

457
00:16:49.339 --> 00:16:50.399
- creates these publications.

458
00:16:50.860 --> 00:16:52.639
- And then these apps are just

459
00:16:53.019 --> 00:16:53.519
- whatever,

460
00:16:55.019 --> 00:16:56.879
- these apps just fetches these publications,

461
00:16:57.339 --> 00:16:59.975
- can interpret them locally and render them for

462
00:16:59.975 --> 00:17:01.654
- you and verify that it was actually from

463
00:17:01.654 --> 00:17:05.275
- the, from the particular source. And I have,

464
00:17:05.335 --> 00:17:07.335
- like, about eight different apps for just, like,

465
00:17:07.335 --> 00:17:09.255
- the Twitter use case on my phone, and

466
00:17:09.255 --> 00:17:11.894
- they're all interchangeable. There's zero friction in in

467
00:17:11.894 --> 00:17:13.654
- changing these apps because they're all doing the

468
00:17:13.654 --> 00:17:14.714
- exact same thing.

469
00:17:16.160 --> 00:17:18.160
- But they they... They're different in kind of

470
00:17:18.160 --> 00:17:19.920
- certain ways. Right? One are more focused on

471
00:17:19.920 --> 00:17:21.140
- the long form, maybe.

472
00:17:21.599 --> 00:17:23.779
- Some have some other features that others don't.

473
00:17:24.480 --> 00:17:24.980
- But,

474
00:17:25.920 --> 00:17:28.660
- we... We've now segregated this ident... We segregated

475
00:17:28.799 --> 00:17:29.299
- the

476
00:17:29.835 --> 00:17:32.875
- identity from the apps and from the servers

477
00:17:32.875 --> 00:17:34.494
- where all this stuff is actually hosted.

478
00:17:35.755 --> 00:17:38.154
- Does this make sense, Ross? Yeah. Yeah. May...

479
00:17:38.154 --> 00:17:39.835
- Yeah. It makes perfect sense. And I can

480
00:17:39.835 --> 00:17:42.174
- actually see a lot of applications for this,

481
00:17:42.474 --> 00:17:45.829
- not just in the open world, but also,

482
00:17:45.829 --> 00:17:46.889
- like, in companies.

483
00:17:47.669 --> 00:17:50.970
- Right? Sure. Yeah. Exactly. To to replace like,

484
00:17:51.029 --> 00:17:53.029
- oh, I have email. I have Slack. I

485
00:17:53.029 --> 00:17:55.369
- have an internal blog. I have an internal

486
00:17:55.429 --> 00:17:58.565
- Git. Oh, I can just have each developer

487
00:17:58.625 --> 00:18:01.125
- or each network engineer or each whatever,

488
00:18:02.144 --> 00:18:04.384
- you know, system admin or whatever. They have

489
00:18:04.384 --> 00:18:06.785
- their own identity with their own channel. And

490
00:18:06.785 --> 00:18:08.625
- as they do stuff, it gets published. And

491
00:18:08.625 --> 00:18:10.005
- if you're interested in

492
00:18:10.799 --> 00:18:13.920
- changes to a particular project, you subscribe to

493
00:18:13.920 --> 00:18:16.080
- those changes, and you get them from all

494
00:18:16.080 --> 00:18:16.820
- the developers

495
00:18:17.519 --> 00:18:18.019
- working

496
00:18:18.480 --> 00:18:20.320
- on that project or whatever it is you

497
00:18:20.320 --> 00:18:22.259
- want to subscribe to that kind of content,

498
00:18:23.325 --> 00:18:26.144
- in that particular realm. Now there are some

499
00:18:26.204 --> 00:18:27.825
- interesting questions there around,

500
00:18:28.365 --> 00:18:31.565
- like, I assume that the applications are able

501
00:18:31.565 --> 00:18:32.944
- to tag the data

502
00:18:33.244 --> 00:18:35.644
- as I just said. Right? I can actually

503
00:18:35.644 --> 00:18:36.144
- say

504
00:18:36.519 --> 00:18:38.599
- this is a channel or this is data

505
00:18:38.599 --> 00:18:39.819
- that's related to

506
00:18:40.119 --> 00:18:42.539
- a particular project, not just a particular

507
00:18:43.240 --> 00:18:43.740
- format.

508
00:18:44.359 --> 00:18:46.059
- Right? You can actually subdivide.

509
00:18:46.679 --> 00:18:48.599
- Yeah. So, I mean, this is a nice

510
00:18:48.599 --> 00:18:50.534
- nice technical audience, so we can we can

511
00:18:50.534 --> 00:18:51.335
- get into that.

512
00:18:51.734 --> 00:18:53.355
- So let's get into the JSON.

513
00:18:54.855 --> 00:18:56.634
- What is this JSON thing? So

514
00:18:57.095 --> 00:18:57.994
- it's basically,

515
00:18:59.494 --> 00:19:00.234
- just content

516
00:19:00.615 --> 00:19:03.174
- that we've split up in two things. So

517
00:19:03.174 --> 00:19:04.855
- we have content which we,

518
00:19:06.509 --> 00:19:07.549
- for which we use,

519
00:19:08.190 --> 00:19:10.110
- human readable stuff. Right? So these are your

520
00:19:10.110 --> 00:19:12.930
- words, and then we have the the tags,

521
00:19:12.990 --> 00:19:15.789
- and those are mostly for the, for the

522
00:19:15.789 --> 00:19:17.710
- computers to interpret. But that's actually the the

523
00:19:17.710 --> 00:19:19.234
- content of whatever is published.

524
00:19:19.934 --> 00:19:21.234
- And on top of that, we,

525
00:19:21.694 --> 00:19:22.914
- have a couple of,

526
00:19:23.694 --> 00:19:26.414
- standard metadata tags, and all of those things

527
00:19:26.414 --> 00:19:30.035
- just is what a basic Noster publication is.

528
00:19:30.095 --> 00:19:32.734
- So we start out with the the name.

529
00:19:32.734 --> 00:19:33.539
- Right? The...

530
00:19:36.820 --> 00:19:40.200
- Public key. Then we have the, the published

531
00:19:40.740 --> 00:19:41.880
- time. So,

532
00:19:42.340 --> 00:19:43.880
- this is just your time stamp,

533
00:19:44.180 --> 00:19:45.559
- on on when it was published.

534
00:19:45.944 --> 00:19:47.724
- What we then have is a kind,

535
00:19:48.184 --> 00:19:50.424
- and this is just a a number, an

536
00:19:50.424 --> 00:19:50.924
- integer.

537
00:19:51.944 --> 00:19:53.865
- And there are no rules on, on this

538
00:19:53.865 --> 00:19:56.265
- integer. It's just there to define what type

539
00:19:56.265 --> 00:19:57.884
- of, thing it is. So,

540
00:19:58.585 --> 00:20:00.204
- when I mentioned you,

541
00:20:01.430 --> 00:20:03.430
- declare what your your name and your profile

542
00:20:03.430 --> 00:20:05.210
- and your bio is, that's kind zero.

543
00:20:05.910 --> 00:20:07.609
- And if you do a tweet,

544
00:20:07.910 --> 00:20:10.230
- that's kind one. Right? That's the the standard

545
00:20:10.230 --> 00:20:12.070
- node. And if you do a long form

546
00:20:12.070 --> 00:20:14.970
- article, it's like kind 30,000 something.

547
00:20:15.894 --> 00:20:18.315
- It's just a way to differentiate to inform,

548
00:20:19.015 --> 00:20:21.035
- the system and allow you for querying,

549
00:20:22.295 --> 00:20:23.734
- what it is that you're actually looking for

550
00:20:23.734 --> 00:20:24.934
- and what it is that you need to

551
00:20:24.934 --> 00:20:25.434
- render.

552
00:20:26.934 --> 00:20:28.454
- So we have the the name. We have

553
00:20:28.454 --> 00:20:30.075
- the time. We have the kind.

554
00:20:30.869 --> 00:20:33.109
- Then we have the tags that I, that

555
00:20:33.109 --> 00:20:34.890
- I mentioned where we can go into,

556
00:20:35.269 --> 00:20:37.670
- and then the content. And I think I

557
00:20:37.670 --> 00:20:37.990
- should,

558
00:20:38.549 --> 00:20:40.150
- I have all of them by now. And

559
00:20:40.150 --> 00:20:41.210
- then we have the,

560
00:20:41.670 --> 00:20:44.005
- event ID, which is just a hash of

561
00:20:44.005 --> 00:20:44.505
- whatever,

562
00:20:44.964 --> 00:20:46.805
- of all the things we we just described.

563
00:20:46.805 --> 00:20:47.305
- Right?

564
00:20:48.085 --> 00:20:50.424
- Ensuring that we now have a unique identifier

565
00:20:50.565 --> 00:20:51.065
- for,

566
00:20:51.605 --> 00:20:52.345
- this publication.

567
00:20:52.884 --> 00:20:55.924
- And then that event ID is signed by

568
00:20:55.924 --> 00:20:56.424
- the,

569
00:20:57.619 --> 00:20:59.799
- by the key pair resulting in a signature.

570
00:21:00.100 --> 00:21:01.640
- So that's your publication.

571
00:21:02.660 --> 00:21:05.059
- And when you want to do a query,

572
00:21:05.059 --> 00:21:07.220
- so this simple query language in relation to

573
00:21:07.220 --> 00:21:07.880
- the relays,

574
00:21:09.539 --> 00:21:10.200
- it has,

575
00:21:10.740 --> 00:21:13.065
- you can query based on the the the

576
00:21:13.065 --> 00:21:13.565
- public

577
00:21:13.944 --> 00:21:16.684
- key. You can query based on the kind.

578
00:21:17.544 --> 00:21:18.664
- You can also query,

579
00:21:19.144 --> 00:21:21.065
- based on the date, of course, right, the

580
00:21:21.065 --> 00:21:23.464
- the the time that, that it was. You

581
00:21:23.464 --> 00:21:26.024
- can... And you can query based on the

582
00:21:26.024 --> 00:21:26.524
- tags.

583
00:21:27.119 --> 00:21:27.599
- And,

584
00:21:27.920 --> 00:21:29.759
- as for the tags, it's an open space.

585
00:21:29.759 --> 00:21:31.619
- You can create whatever tags that you want.

586
00:21:32.799 --> 00:21:35.039
- But there are a handful of tags that

587
00:21:35.039 --> 00:21:36.880
- are... And these are the single letter,

588
00:21:37.519 --> 00:21:39.279
- key pair values. So it's like the single

589
00:21:39.279 --> 00:21:39.974
- letter keys.

590
00:21:41.494 --> 00:21:44.134
- And those are assumed to be indexed by

591
00:21:44.134 --> 00:21:46.454
- every relay. And then outside of that, they're

592
00:21:46.454 --> 00:21:48.214
- not assumed to be indexed by relays, but

593
00:21:48.214 --> 00:21:50.054
- they can happen to be indexed by relays.

594
00:21:50.054 --> 00:21:51.654
- So if you're running this on a corporate

595
00:21:51.654 --> 00:21:53.859
- environment and you're you're... You've created a bunch

596
00:21:53.859 --> 00:21:55.619
- of standards for whatever use case it is

597
00:21:55.619 --> 00:21:56.759
- that you're you're running,

598
00:21:57.700 --> 00:21:59.940
- then you can also... For running this Relay

599
00:21:59.940 --> 00:22:01.700
- or this server, you can start indexing this

600
00:22:01.700 --> 00:22:03.619
- stuff. And you can also do text search.

601
00:22:03.619 --> 00:22:05.779
- Right? You can start indexing the actual content,

602
00:22:06.375 --> 00:22:08.535
- and do text based search. Right? That... That's

603
00:22:08.535 --> 00:22:09.194
- all open.

604
00:22:09.815 --> 00:22:11.674
- Okay. So does this make sense for us?

605
00:22:11.815 --> 00:22:13.994
- Yeah. Sure does, actually. And

606
00:22:14.375 --> 00:22:16.934
- a couple of other questions, like... So when

607
00:22:16.934 --> 00:22:19.015
- you talk about public private key pairs, are

608
00:22:19.015 --> 00:22:19.914
- you using...

609
00:22:20.740 --> 00:22:22.500
- What are those? Are those x five zero

610
00:22:22.500 --> 00:22:24.039
- nine? Are those PGP?

611
00:22:24.659 --> 00:22:27.140
- Like, what what... They're snore. Okay. So so

612
00:22:27.140 --> 00:22:30.339
- they they directly... They're directly borrowed from, from

613
00:22:30.339 --> 00:22:30.839
- Bitcoin.

614
00:22:31.220 --> 00:22:33.460
- So it's exactly it's exactly the same thing.

615
00:22:33.460 --> 00:22:35.779
- So, technically, your Nostra identity is directly,

616
00:22:36.815 --> 00:22:38.434
- Bitcoin address at the same time.

617
00:22:38.894 --> 00:22:41.134
- Okay. The encoding... The the the encoding that

618
00:22:41.134 --> 00:22:42.815
- is done for, like, a Nasr public key

619
00:22:42.815 --> 00:22:44.734
- is different, but the the underlying value, it's

620
00:22:44.734 --> 00:22:45.875
- exactly the same.

621
00:22:46.255 --> 00:22:46.755
- Okay.

622
00:22:47.055 --> 00:22:47.555
- Interesting.

623
00:22:49.259 --> 00:22:49.759
- Alright.

624
00:22:50.059 --> 00:22:52.859
- So that also ties it. So there's no

625
00:22:52.859 --> 00:22:55.599
- blockchain element here, though. Right? No. Nothing. Nothing

626
00:22:55.900 --> 00:22:58.539
- about it. Correct. Nothing about it's blockchain. So

627
00:22:58.539 --> 00:23:00.960
- you're not actually adding to a public record

628
00:23:01.420 --> 00:23:03.599
- this was sent. Can you validate...

629
00:23:04.515 --> 00:23:07.095
- So you can validate who sent something, obviously.

630
00:23:07.795 --> 00:23:08.775
- Can you validate

631
00:23:09.075 --> 00:23:10.535
- that it was sent?

632
00:23:11.075 --> 00:23:13.795
- Like, you don't have a record like you

633
00:23:13.795 --> 00:23:14.775
- would with a blockchain

634
00:23:15.394 --> 00:23:17.714
- of this being sent by that or whatever

635
00:23:18.035 --> 00:23:20.339
- No. No. Over time. Right. There are zero

636
00:23:20.339 --> 00:23:20.839
- guarantees

637
00:23:21.220 --> 00:23:24.440
- or promises on anything, Russ. Okay. Right. Yeah.

638
00:23:24.500 --> 00:23:26.740
- Okay. That's fine. So I was just trying

639
00:23:26.740 --> 00:23:28.420
- to, you know, make sure Sure. So that...

640
00:23:28.420 --> 00:23:28.920
- Okay.

641
00:23:29.380 --> 00:23:31.880
- So that also means that

642
00:23:32.545 --> 00:23:33.525
- you should not,

643
00:23:33.904 --> 00:23:35.365
- in this kind of a system,

644
00:23:35.904 --> 00:23:38.164
- face the kind of Byzantine attack

645
00:23:38.625 --> 00:23:41.204
- that Radio Proman worries so much about

646
00:23:41.585 --> 00:23:42.325
- with Bitcoin

647
00:23:42.785 --> 00:23:44.880
- type solution. Sure. Because there there is no...

648
00:23:44.960 --> 00:23:46.559
- This is what we... This... We have this

649
00:23:46.559 --> 00:23:48.500
- phrase in us that there is no global.

650
00:23:48.720 --> 00:23:50.720
- Right? We're we're not concerned with state at

651
00:23:50.720 --> 00:23:51.220
- all.

652
00:23:51.920 --> 00:23:53.839
- I mean, state is a lie. Right? Global

653
00:23:53.839 --> 00:23:55.279
- state is a lie. The the the whole

654
00:23:55.279 --> 00:23:56.559
- point is, like, what we're saying is, like,

655
00:23:56.559 --> 00:23:58.674
- global state is a lie already. The fact

656
00:23:58.674 --> 00:24:00.595
- that you you assume... Because one of the

657
00:24:00.595 --> 00:24:02.275
- first complaints that we have with the social

658
00:24:02.275 --> 00:24:02.775
- application

659
00:24:03.234 --> 00:24:04.914
- is, like, there is no global feed. And

660
00:24:04.914 --> 00:24:06.755
- what we tried to communicate to these people

661
00:24:06.755 --> 00:24:08.515
- complaining about the fact that there's no global

662
00:24:08.515 --> 00:24:11.714
- field that feed feed that they were, familiar

663
00:24:11.714 --> 00:24:13.095
- with with Twitter or

664
00:24:13.440 --> 00:24:15.919
- on, or whatever social platform that there is

665
00:24:15.919 --> 00:24:18.000
- this global feed that everybody's looking at. It's

666
00:24:18.000 --> 00:24:19.919
- like, no. You don't understand. It's like you're

667
00:24:19.919 --> 00:24:22.159
- just looking at this siloed feed. There's no

668
00:24:22.159 --> 00:24:25.039
- global. There... You... If you're looking at Twitter,

669
00:24:25.039 --> 00:24:26.720
- you're now not looking at what's going on

670
00:24:26.720 --> 00:24:28.319
- in Reddit, and you're now not look look...

671
00:24:28.319 --> 00:24:30.105
- Going on what's, like, on all kinds of

672
00:24:30.105 --> 00:24:32.125
- fora or whatever. There's no global feed.

673
00:24:32.664 --> 00:24:34.904
- So so we're... And and in all certain,

674
00:24:34.904 --> 00:24:37.085
- either. There... There's no global feed there either.

675
00:24:37.384 --> 00:24:38.904
- What you do have, you can you can

676
00:24:38.904 --> 00:24:40.424
- have a relay feed. You can connect to

677
00:24:40.424 --> 00:24:42.345
- a particular server and just ask to that

678
00:24:42.345 --> 00:24:44.269
- server, which we call the server,

679
00:24:44.730 --> 00:24:45.230
- relays,

680
00:24:45.690 --> 00:24:47.470
- for reasons that we can go into.

681
00:24:48.330 --> 00:24:50.090
- You can ask that relay. It's like, okay.

682
00:24:50.090 --> 00:24:51.690
- Just give me whatever it is that you

683
00:24:51.690 --> 00:24:52.190
- have,

684
00:24:52.809 --> 00:24:55.289
- and not query something in particular. Just query

685
00:24:55.289 --> 00:24:56.430
- just based on the location.

686
00:24:57.375 --> 00:24:59.535
- And that's the the the quote, unquote global

687
00:24:59.535 --> 00:25:00.515
- feed for whatever,

688
00:25:00.974 --> 00:25:02.434
- is happening on that server.

689
00:25:02.894 --> 00:25:04.894
- But other than that, no. We're we're not,

690
00:25:05.615 --> 00:25:07.714
- coordinating on a particular state at all.

691
00:25:08.255 --> 00:25:09.775
- Yeah. I wanted to I wanted to go

692
00:25:09.775 --> 00:25:12.630
- into relays then. What's the what's the architecture

693
00:25:12.630 --> 00:25:14.549
- there? How's the... How do they fit into

694
00:25:14.549 --> 00:25:15.210
- the system?

695
00:25:15.830 --> 00:25:18.170
- So the the idea behind,

696
00:25:18.710 --> 00:25:22.150
- Noster is... And it's, because in a tagline

697
00:25:22.150 --> 00:25:24.630
- that I mentioned earlier is the, there's this

698
00:25:24.630 --> 00:25:27.265
- quip about it's not based on peer to

699
00:25:27.265 --> 00:25:28.404
- peer, so it works,

700
00:25:30.305 --> 00:25:33.365
- where the observation is, like, okay. We... Because,

701
00:25:34.705 --> 00:25:36.945
- the the person that built this, or designed

702
00:25:36.945 --> 00:25:39.029
- this was a Bitcoiner. The the people that

703
00:25:39.349 --> 00:25:41.590
- went into this first were, a bunch of

704
00:25:41.590 --> 00:25:42.090
- Bitcoiners.

705
00:25:43.750 --> 00:25:44.250
- And,

706
00:25:44.950 --> 00:25:46.950
- you know, the... We're we're, like, with the

707
00:25:46.950 --> 00:25:48.090
- cypherpunk background,

708
00:25:49.029 --> 00:25:50.789
- we we do have, like, a tendency to

709
00:25:50.789 --> 00:25:52.970
- look like... For... Look for the holy grail

710
00:25:53.375 --> 00:25:55.715
- of... And the holy grail is, like, obviously,

711
00:25:56.174 --> 00:25:58.035
- some magical peer to peer thing.

712
00:25:59.134 --> 00:26:01.555
- The observation here or the the the conclusion

713
00:26:01.695 --> 00:26:04.275
- by by Fijaf, who who designed this system,

714
00:26:05.389 --> 00:26:07.649
- was it's okay. That's... That that doesn't work,

715
00:26:08.269 --> 00:26:10.669
- but servers do work. So let's just use

716
00:26:10.669 --> 00:26:11.169
- servers.

717
00:26:12.589 --> 00:26:13.089
- And,

718
00:26:14.029 --> 00:26:16.349
- but just use them for whatever they're actually

719
00:26:16.349 --> 00:26:20.049
- good for. So because we sign every publication,

720
00:26:20.984 --> 00:26:22.125
- you now introduced

721
00:26:22.424 --> 00:26:22.924
- a,

722
00:26:23.464 --> 00:26:24.365
- trust minimization

723
00:26:24.664 --> 00:26:27.384
- in relation to the server. So in the

724
00:26:27.384 --> 00:26:31.164
- platform paradigm, both your account and your publications

725
00:26:31.384 --> 00:26:33.929
- are directly tied to the platform. So an

726
00:26:33.929 --> 00:26:36.569
- Instagram post is only an Instagram post because

727
00:26:36.569 --> 00:26:37.849
- it came from instagram.com.

728
00:26:37.849 --> 00:26:39.690
- The only way to verify that an Instagram

729
00:26:39.690 --> 00:26:41.609
- post was actually real is to go to

730
00:26:41.609 --> 00:26:42.809
- instagram.com

731
00:26:42.809 --> 00:26:44.589
- and ask instagram.com,

732
00:26:44.809 --> 00:26:46.889
- does this account even exist? And this... Did

733
00:26:46.889 --> 00:26:49.230
- did this account actually post this thing?

734
00:26:49.575 --> 00:26:50.634
- And all authority

735
00:26:51.174 --> 00:26:52.394
- rests with that server.

736
00:26:52.855 --> 00:26:55.974
- Because we are signing every publication and we're

737
00:26:55.974 --> 00:26:58.694
- doing the verification of that locally, we're not

738
00:26:58.694 --> 00:27:00.774
- trusting the server on any of this. So

739
00:27:00.774 --> 00:27:02.774
- that also means that the location is not

740
00:27:02.774 --> 00:27:05.640
- relevant anymore. Whether my publication came from server

741
00:27:05.640 --> 00:27:07.900
- a or server b is completely irrelevant.

742
00:27:08.279 --> 00:27:10.599
- This means that it... Now my publications are

743
00:27:10.599 --> 00:27:11.099
- liberated,

744
00:27:11.400 --> 00:27:13.880
- not just in a sense of space of

745
00:27:13.880 --> 00:27:15.480
- what server they came from, but also in

746
00:27:15.480 --> 00:27:16.539
- the sense of time.

747
00:27:16.845 --> 00:27:18.845
- So server a can... So my... If my

748
00:27:18.845 --> 00:27:20.924
- stuff was hosted on server a, server a

749
00:27:20.924 --> 00:27:22.384
- can go down. I can retroactively

750
00:27:23.085 --> 00:27:25.244
- reupload it to server b, and that's fine.

751
00:27:25.244 --> 00:27:27.345
- Right? My audience that follows me,

752
00:27:28.204 --> 00:27:29.900
- when they start fetching it from server b,

753
00:27:29.900 --> 00:27:31.420
- they're not in fact... Inflicted by the fact

754
00:27:31.420 --> 00:27:32.880
- that it came from a different server.

755
00:27:33.900 --> 00:27:36.059
- So that's the reason why they were called

756
00:27:36.059 --> 00:27:40.079
- relays because they're, quote, unquote, dumb systems that

757
00:27:40.380 --> 00:27:42.559
- the only thing... They have three responsibilities

758
00:27:42.859 --> 00:27:43.394
- left, and those

759
00:27:44.434 --> 00:27:47.555
- three responsibilities are to, get the data. Right?

760
00:27:47.555 --> 00:27:50.414
- So the... To receive publications, to retain publications,

761
00:27:50.414 --> 00:27:54.035
- and then to hand out publications to whenever

762
00:27:54.035 --> 00:27:55.095
- they ask for it.

763
00:27:56.035 --> 00:27:56.195
- The,

764
00:27:57.150 --> 00:27:58.849
- the thing here is is that

765
00:27:59.230 --> 00:28:01.470
- because they are in charge of these three

766
00:28:01.470 --> 00:28:03.970
- things, they can actually leverage that position,

767
00:28:04.830 --> 00:28:05.650
- for utility.

768
00:28:05.950 --> 00:28:07.170
- So they can decide

769
00:28:07.950 --> 00:28:09.009
- from whom and,

770
00:28:09.390 --> 00:28:11.924
- what type of what type of publications and

771
00:28:12.005 --> 00:28:12.744
- from whom

772
00:28:13.125 --> 00:28:13.625
- and,

773
00:28:14.164 --> 00:28:16.404
- whether it's full moon or not or whatever

774
00:28:16.404 --> 00:28:18.965
- arbitrary reason that they have, whether they accept

775
00:28:18.965 --> 00:28:22.505
- data. They can have whatever arbitrary rules on,

776
00:28:23.125 --> 00:28:25.285
- how they retain data, and they can have

777
00:28:25.285 --> 00:28:26.744
- whatever arbitrary rules

778
00:28:27.320 --> 00:28:29.480
- on to whom they'd actually distribute or hand

779
00:28:29.480 --> 00:28:31.099
- out the data. So

780
00:28:31.720 --> 00:28:33.960
- they have that power... They have that position.

781
00:28:33.960 --> 00:28:35.019
- They have those responsibilities,

782
00:28:36.119 --> 00:28:37.960
- and they can be leveraged to the fullest

783
00:28:37.960 --> 00:28:40.974
- extent because on a user side, I'm not

784
00:28:40.974 --> 00:28:43.075
- dependent on any particular relay anymore.

785
00:28:44.414 --> 00:28:45.075
- So the...

786
00:28:45.534 --> 00:28:48.174
- This relationship between user and server, there's now

787
00:28:48.174 --> 00:28:50.034
- a liberation on both sides happening

788
00:28:50.335 --> 00:28:52.014
- because of the use of this... Because of

789
00:28:52.014 --> 00:28:52.994
- the use of signatures

790
00:28:53.454 --> 00:28:53.954
- where

791
00:28:54.789 --> 00:28:57.430
- the server can have whatever policy that it

792
00:28:57.430 --> 00:28:59.930
- wants, and I, as a user, am not...

793
00:28:59.990 --> 00:29:02.329
- I... I'm flexible enough to go to whatever

794
00:29:02.789 --> 00:29:05.529
- server or relay it is that has policies

795
00:29:05.670 --> 00:29:08.630
- that fit my fit my liking. Or, I

796
00:29:08.630 --> 00:29:11.414
- can host my own. Because, ultimately, a relay

797
00:29:11.414 --> 00:29:13.494
- is basically the simplest type of server that

798
00:29:13.494 --> 00:29:15.914
- you can run. So whatever,

799
00:29:17.654 --> 00:29:20.375
- barrier there is to running a server, at

800
00:29:20.375 --> 00:29:20.875
- least

801
00:29:21.335 --> 00:29:23.494
- for running a... Not so relay, the barriers

802
00:29:23.494 --> 00:29:25.289
- is as low as it can possibly be.

803
00:29:25.529 --> 00:29:26.269
- So you can

804
00:29:26.650 --> 00:29:27.150
- always,

805
00:29:27.850 --> 00:29:29.609
- go ahead and and run your own relay

806
00:29:29.609 --> 00:29:29.930
- if,

807
00:29:30.650 --> 00:29:32.650
- if the... If that use case requires it.

808
00:29:32.650 --> 00:29:33.869
- From a censorship position

809
00:29:34.570 --> 00:29:35.070
- or,

810
00:29:36.009 --> 00:29:38.410
- from a a data integrity position or whatever

811
00:29:38.410 --> 00:29:40.090
- the reason is, you can also always run

812
00:29:40.090 --> 00:29:40.910
- your own relay.

813
00:29:41.744 --> 00:29:43.845
- Yeah. And I think that's really important because

814
00:29:44.785 --> 00:29:46.224
- what we see in the real world is

815
00:29:46.224 --> 00:29:48.144
- people... Even when you talk about global feed

816
00:29:48.144 --> 00:29:49.204
- on something like

817
00:29:49.585 --> 00:29:52.865
- x or TikTok or what... Take any service

818
00:29:52.865 --> 00:29:55.319
- you want to. There's still no really a

819
00:29:55.319 --> 00:29:58.680
- global feed there. What actually happens is is

820
00:29:58.680 --> 00:29:59.180
- that

821
00:30:00.759 --> 00:30:03.259
- users upload so much content

822
00:30:04.200 --> 00:30:06.220
- on these services so quickly

823
00:30:07.204 --> 00:30:09.945
- that the service itself can choose.

824
00:30:11.365 --> 00:30:13.924
- This is why these services become publishers in

825
00:30:13.924 --> 00:30:15.765
- the eyes of the law even though people

826
00:30:15.765 --> 00:30:18.085
- don't understand this. So, like... But each user

827
00:30:18.085 --> 00:30:21.639
- contributed content, The the the service is not

828
00:30:21.639 --> 00:30:22.139
- publishing

829
00:30:22.599 --> 00:30:23.419
- because they're

830
00:30:23.880 --> 00:30:26.299
- not actually creating the content. No.

831
00:30:26.839 --> 00:30:27.819
- I can take

832
00:30:28.359 --> 00:30:29.980
- a random noise generator,

833
00:30:30.679 --> 00:30:33.259
- enough of them, put them into a box,

834
00:30:33.639 --> 00:30:34.305
- and put

835
00:30:35.184 --> 00:30:37.265
- a a a Bach filter on the random

836
00:30:37.265 --> 00:30:38.485
- noise noise generator

837
00:30:38.865 --> 00:30:40.565
- and end up with the fifth symphony.

838
00:30:41.025 --> 00:30:43.825
- Right. Right? Like, if I get enough random

839
00:30:43.825 --> 00:30:45.845
- noise on the input side of a filter,

840
00:30:46.384 --> 00:30:48.144
- I can make the output anything I want

841
00:30:48.144 --> 00:30:49.445
- to by shaping the filter.

842
00:30:50.000 --> 00:30:51.840
- And this is where people don't seem to

843
00:30:51.840 --> 00:30:55.279
- understand a lot how the... Where the the

844
00:30:55.279 --> 00:30:58.080
- complexity of understanding whether these are publishers or

845
00:30:58.080 --> 00:31:00.180
- not and all this other stuff comes in.

846
00:31:00.400 --> 00:31:01.380
- In this case,

847
00:31:01.920 --> 00:31:04.100
- if you can run your own relay,

848
00:31:04.865 --> 00:31:05.924
- you can control

849
00:31:06.305 --> 00:31:08.085
- what those filters look like,

850
00:31:08.465 --> 00:31:10.865
- or you can turn that control over to

851
00:31:10.865 --> 00:31:12.404
- somebody you trust.

852
00:31:12.865 --> 00:31:13.365
- Right?

853
00:31:13.825 --> 00:31:16.065
- Right. You you can actually say, okay. Well,

854
00:31:16.065 --> 00:31:17.664
- I don't wanna spend the time building the

855
00:31:17.664 --> 00:31:19.630
- filters. I'll just let somebody else build the

856
00:31:19.630 --> 00:31:21.950
- filters for me. But now I have a

857
00:31:21.950 --> 00:31:23.890
- trust level. I can turn them off

858
00:31:25.470 --> 00:31:27.490
- in theory and see the full feed

859
00:31:27.789 --> 00:31:29.169
- if I want to.

860
00:31:29.470 --> 00:31:29.970
- Now

861
00:31:30.349 --> 00:31:32.049
- there would be problems with that.

862
00:31:32.674 --> 00:31:34.994
- You know, you start looking you start looking

863
00:31:34.994 --> 00:31:36.855
- at... What is it? YouTube gets,

864
00:31:37.154 --> 00:31:39.714
- I don't know, twenty hours of video every

865
00:31:39.714 --> 00:31:42.275
- minute uploaded or some stupid... The the numbers

866
00:31:42.275 --> 00:31:46.099
- are stupid. Like, you can't watch or read

867
00:31:46.099 --> 00:31:48.440
- or listen to all the content.

868
00:31:48.980 --> 00:31:51.059
- It's it's a it's a million, a ten

869
00:31:51.059 --> 00:31:54.039
- ten million, or 4,000,000,000 to one problem

870
00:31:54.500 --> 00:31:56.679
- in terms of content creation and consumption.

871
00:31:57.605 --> 00:31:58.105
- So

872
00:31:58.404 --> 00:32:01.065
- there there is some balance there that is,

873
00:32:03.045 --> 00:32:05.845
- hard sometimes to figure out what that balance

874
00:32:05.845 --> 00:32:08.005
- looks like. Yeah. And in terms of, like,

875
00:32:08.005 --> 00:32:09.765
- deciding what it is that you wanna look

876
00:32:09.765 --> 00:32:10.079
- at.

877
00:32:10.720 --> 00:32:11.119
- Right.

878
00:32:11.679 --> 00:32:13.839
- Within, like, this Nasr paradigm, that can happen

879
00:32:13.839 --> 00:32:15.700
- on a couple of different level... Levels.

880
00:32:16.480 --> 00:32:19.200
- So it can happen on the the the

881
00:32:19.200 --> 00:32:20.980
- relay level where you just...

882
00:32:21.759 --> 00:32:24.914
- So in Nasr, we... I... How I generally

883
00:32:24.914 --> 00:32:26.914
- describe is, like, we have two modes of

884
00:32:26.914 --> 00:32:29.315
- operation of, like, serving the web, this Nasr

885
00:32:29.315 --> 00:32:29.815
- web.

886
00:32:30.194 --> 00:32:30.914
- So the,

887
00:32:32.595 --> 00:32:33.974
- one mode is,

888
00:32:34.914 --> 00:32:36.595
- and they they relate to how you how

889
00:32:36.595 --> 00:32:38.329
- you relate to the relays. So

890
00:32:38.710 --> 00:32:40.789
- the the the one that's closest to the

891
00:32:40.789 --> 00:32:42.950
- current paradigm is what we... What I mentioned,

892
00:32:42.950 --> 00:32:45.349
- like, these relay feeds. So you're just... Based

893
00:32:45.349 --> 00:32:47.609
- on the location, you just ask the server,

894
00:32:47.829 --> 00:32:49.589
- just give me whatever it is that you

895
00:32:49.589 --> 00:32:51.049
- want to hand over to me.

896
00:32:52.115 --> 00:32:53.954
- And that's that's what we call a relay

897
00:32:53.954 --> 00:32:56.774
- feed. And there, the location is,

898
00:32:57.394 --> 00:32:58.694
- the determining factor.

899
00:32:59.075 --> 00:32:59.815
- So maybe,

900
00:33:00.914 --> 00:33:01.414
- I...

901
00:33:01.875 --> 00:33:03.875
- There's a there's a server where a bunch

902
00:33:03.875 --> 00:33:04.200
- of,

903
00:33:04.679 --> 00:33:07.079
- astronomers... All all all the astronomers, they go

904
00:33:07.079 --> 00:33:09.500
- to a particular server, have discussions there,

905
00:33:10.279 --> 00:33:12.039
- and I connect to that survey if I

906
00:33:12.039 --> 00:33:13.899
- wanna... If I'm interested in astronomy,

907
00:33:14.359 --> 00:33:15.500
- content. Right?

908
00:33:16.759 --> 00:33:18.779
- The thing is there is also this other,

909
00:33:19.544 --> 00:33:20.684
- mode of operating

910
00:33:21.065 --> 00:33:22.524
- where the censorship resistance,

911
00:33:23.704 --> 00:33:25.085
- that is within Noster,

912
00:33:26.024 --> 00:33:28.585
- comes to the front. Where... Okay. Now, I'm

913
00:33:28.585 --> 00:33:30.505
- on this astronomy relay. I see a bunch

914
00:33:30.505 --> 00:33:31.164
- of discussions,

915
00:33:33.029 --> 00:33:35.590
- from astronomers. I decide to follow one of

916
00:33:35.590 --> 00:33:37.670
- the astronomers. So I hit the follow button

917
00:33:37.670 --> 00:33:39.130
- on my on my app.

918
00:33:39.430 --> 00:33:41.509
- The moment I do that, what my client

919
00:33:41.509 --> 00:33:43.430
- starts doing or what it's... My client is

920
00:33:43.430 --> 00:33:45.590
- supposed to start doing is to start looking,

921
00:33:45.590 --> 00:33:47.350
- okay, what is going on with this person?

922
00:33:47.350 --> 00:33:48.410
- This person declared

923
00:33:48.924 --> 00:33:51.585
- what relays they're actually using for their publications.

924
00:33:51.964 --> 00:33:54.365
- So one of those relays is this astronomy

925
00:33:54.365 --> 00:33:55.964
- relay, but he also... He's also using a

926
00:33:55.964 --> 00:33:57.565
- bunch of other relays. Maybe he has his

927
00:33:57.565 --> 00:33:59.805
- own relay as a backup. He uses a

928
00:33:59.805 --> 00:34:00.625
- very large,

929
00:34:01.244 --> 00:34:03.180
- commodity relay, whatever it is.

930
00:34:03.900 --> 00:34:06.320
- And whenever I... Instead of

931
00:34:06.779 --> 00:34:07.259
- my,

932
00:34:07.740 --> 00:34:10.239
- feed determined by a particular relay,

933
00:34:10.619 --> 00:34:12.539
- I just want to see my follow feed,

934
00:34:12.539 --> 00:34:15.500
- right, my regular Twitter style follow feed. What

935
00:34:15.500 --> 00:34:17.744
- my client just does is then, okay, this

936
00:34:17.744 --> 00:34:19.025
- is my follow list, so these are the

937
00:34:19.025 --> 00:34:21.105
- people that I follow. I know where each

938
00:34:21.105 --> 00:34:23.744
- of those people publish their stuff. So what

939
00:34:23.744 --> 00:34:25.204
- my client just does, it goes

940
00:34:25.505 --> 00:34:27.424
- past all of those relays and just asks

941
00:34:27.424 --> 00:34:29.424
- them. It's, like, queries them for I want

942
00:34:29.424 --> 00:34:32.190
- this... The latest stuff between now and two

943
00:34:32.190 --> 00:34:34.289
- days ago from this particular author,

944
00:34:35.070 --> 00:34:37.550
- and then starts to construct that feed based

945
00:34:37.550 --> 00:34:38.690
- off all those distributed,

946
00:34:39.070 --> 00:34:39.570
- relays,

947
00:34:40.109 --> 00:34:42.269
- and gives me gives me that relay feed.

948
00:34:42.269 --> 00:34:44.510
- So whenever a discussion is happening on the

949
00:34:44.510 --> 00:34:45.570
- astronomy relay,

950
00:34:46.235 --> 00:34:48.655
- and one of the astronomers gets banned,

951
00:34:49.275 --> 00:34:50.894
- if I follow that astronomer

952
00:34:51.275 --> 00:34:51.775
- myself,

953
00:34:53.195 --> 00:34:54.875
- that's... I I don't lose sight of that

954
00:34:54.875 --> 00:34:57.515
- astronomer because I already follow that astronomer. I

955
00:34:57.515 --> 00:34:59.210
- just get him into my follow feed. I

956
00:34:59.210 --> 00:35:01.550
- already know the other places where he's publishing.

957
00:35:01.769 --> 00:35:03.769
- The fact that he's publishing in a place

958
00:35:03.769 --> 00:35:04.909
- where he's now banned

959
00:35:05.289 --> 00:35:05.789
- isn't

960
00:35:06.250 --> 00:35:08.589
- isn't actually restricting me from,

961
00:35:09.130 --> 00:35:10.349
- interacting or associating

962
00:35:10.650 --> 00:35:12.589
- with, with a particular person.

963
00:35:13.094 --> 00:35:14.474
- So you can either,

964
00:35:15.494 --> 00:35:17.734
- so it's either based on the location, and

965
00:35:17.734 --> 00:35:19.815
- then it's based on this relay feed, or

966
00:35:19.815 --> 00:35:21.974
- it's based on the particular person that you're

967
00:35:21.974 --> 00:35:24.534
- following. And now you're... Now the relays don't

968
00:35:24.534 --> 00:35:26.375
- matter anymore. You're just... The only thing that

969
00:35:26.375 --> 00:35:27.829
- matters is what

970
00:35:28.130 --> 00:35:30.050
- relays they happen to use at a particular

971
00:35:30.050 --> 00:35:31.650
- time, and then you just connect to those

972
00:35:31.650 --> 00:35:33.010
- and you get whatever content,

973
00:35:33.329 --> 00:35:34.390
- you get the content.

974
00:35:34.769 --> 00:35:36.769
- And the person can be flexible. So you

975
00:35:36.769 --> 00:35:38.849
- either query based on the m pop or

976
00:35:38.849 --> 00:35:41.010
- you you you query based on the, on

977
00:35:41.010 --> 00:35:42.469
- the locations of the relay.

978
00:35:43.065 --> 00:35:44.045
- Does this make

979
00:35:44.344 --> 00:35:46.785
- sense? Yep. Makes sense to me. I Yep.

980
00:35:46.905 --> 00:35:49.244
- I I I wonder a lot about

981
00:35:50.105 --> 00:35:50.605
- implementation,

982
00:35:52.264 --> 00:35:53.244
- why people...

983
00:35:54.425 --> 00:35:57.144
- I mean, what's the motivation for running one

984
00:35:57.144 --> 00:35:58.125
- of these relays

985
00:35:58.789 --> 00:36:00.710
- other than just doing a good thing for

986
00:36:00.710 --> 00:36:01.369
- the community?

987
00:36:02.070 --> 00:36:04.230
- What is the motivation to run any server,

988
00:36:04.230 --> 00:36:04.730
- Ross?

989
00:36:05.429 --> 00:36:06.969
- So so are there commercial...

990
00:36:07.349 --> 00:36:10.309
- Like, would there be commercial gains to somebody

991
00:36:10.309 --> 00:36:11.769
- doing something like this?

992
00:36:12.070 --> 00:36:13.349
- Sure. There are,

993
00:36:13.750 --> 00:36:15.125
- I I use,

994
00:36:15.744 --> 00:36:16.244
- two

995
00:36:16.945 --> 00:36:18.324
- paid relays, actually.

996
00:36:19.824 --> 00:36:22.304
- So... And the reason... The motivation for me

997
00:36:22.304 --> 00:36:22.804
- to,

998
00:36:23.344 --> 00:36:24.965
- pay for a relay is because,

999
00:36:26.144 --> 00:36:27.985
- the other relays, there are... There aren't any

1000
00:36:27.985 --> 00:36:29.940
- guarantees, so they might just shut down their

1001
00:36:29.940 --> 00:36:31.239
- server, and that happens.

1002
00:36:32.260 --> 00:36:34.099
- Okay. When I pay for it, the odds

1003
00:36:34.099 --> 00:36:36.980
- of them just shutting down the, the server

1004
00:36:36.980 --> 00:36:39.880
- and not communicating about it at least, right,

1005
00:36:41.219 --> 00:36:43.699
- are are are vastly diminished. So just for,

1006
00:36:44.765 --> 00:36:46.525
- for for that sake, I I pay for

1007
00:36:46.525 --> 00:36:48.285
- the relay, and they provide that service, and

1008
00:36:48.285 --> 00:36:51.105
- that... That's going on. If you are a,

1009
00:36:51.965 --> 00:36:53.425
- what's the reason for,

1010
00:36:54.364 --> 00:36:56.925
- a lot of businesses to run servers because

1011
00:36:56.925 --> 00:36:59.280
- they have a business. Right? It's not their,

1012
00:36:59.519 --> 00:37:01.519
- like, it's just part of the... They also

1013
00:37:01.519 --> 00:37:03.280
- have an office. Right? We're not we're not

1014
00:37:03.280 --> 00:37:05.199
- asking, like, the question is, like, who's gonna

1015
00:37:05.199 --> 00:37:06.719
- pay for the offices? It's, like, no. They

1016
00:37:06.719 --> 00:37:08.400
- have a business, and they need they need

1017
00:37:08.400 --> 00:37:09.760
- an office, and they need they need a

1018
00:37:09.760 --> 00:37:11.460
- storefront or whatever it is.

1019
00:37:12.159 --> 00:37:14.579
- So that's why they, why they run the,

1020
00:37:14.985 --> 00:37:17.085
- run the relay. So so you would envision,

1021
00:37:17.305 --> 00:37:19.405
- like like, DNS today

1022
00:37:19.865 --> 00:37:21.565
- is a service you get

1023
00:37:22.025 --> 00:37:22.525
- theoretically

1024
00:37:23.385 --> 00:37:25.865
- when you buy... You pay an Internet service

1025
00:37:25.865 --> 00:37:26.365
- provider.

1026
00:37:26.909 --> 00:37:28.989
- Right? Right. So you would you would say,

1027
00:37:28.989 --> 00:37:29.730
- okay. Well,

1028
00:37:30.829 --> 00:37:34.190
- ISPs or access providers... I say ISPs, but

1029
00:37:34.190 --> 00:37:35.489
- really access providers,

1030
00:37:36.109 --> 00:37:38.750
- people like AT and T or Comcast in

1031
00:37:38.750 --> 00:37:40.130
- The US or Iran

1032
00:37:40.644 --> 00:37:42.644
- would just stand these servers up as a

1033
00:37:42.644 --> 00:37:43.465
- part of,

1034
00:37:44.085 --> 00:37:46.885
- you know, you buy my Internet service. I...

1035
00:37:46.885 --> 00:37:49.525
- Part of that Internet service is having access

1036
00:37:49.525 --> 00:37:50.825
- to this set of Nasr

1037
00:37:51.364 --> 00:37:52.265
- relay servers,

1038
00:37:52.565 --> 00:37:54.505
- and we just maintain those. Right?

1039
00:37:55.000 --> 00:37:57.320
- Sure. And that that, yeah, that could be.

1040
00:37:57.320 --> 00:37:59.000
- That that that could that could be a

1041
00:37:59.000 --> 00:37:59.500
- way.

1042
00:38:00.680 --> 00:38:02.840
- The same way people pay for their email.

1043
00:38:02.840 --> 00:38:03.320
- Right?

1044
00:38:04.599 --> 00:38:05.660
- Or or whatever,

1045
00:38:06.280 --> 00:38:08.680
- service are provided. Or if I'm if I'm

1046
00:38:08.680 --> 00:38:09.500
- running the,

1047
00:38:10.985 --> 00:38:14.184
- the Hatch fan club website. Right? Yeah. I...

1048
00:38:14.184 --> 00:38:15.625
- I'll I'll just do it because for for

1049
00:38:15.625 --> 00:38:16.985
- the love of it, and it's only... It's

1050
00:38:16.985 --> 00:38:17.805
- very cheap.

1051
00:38:18.664 --> 00:38:20.364
- Especially when we're talking about,

1052
00:38:20.905 --> 00:38:23.965
- because Nostra itself, it's just, it's just JSON.

1053
00:38:25.019 --> 00:38:26.460
- It's just a bunch of text at the

1054
00:38:26.460 --> 00:38:28.880
- end of the day. It's not extremely expensive

1055
00:38:29.019 --> 00:38:31.340
- to run a server that handles a couple

1056
00:38:31.340 --> 00:38:32.239
- thousand users,

1057
00:38:33.260 --> 00:38:33.760
- and

1058
00:38:34.059 --> 00:38:35.280
- and however many publications,

1059
00:38:35.820 --> 00:38:37.565
- in a month. That's that's fine. It's it's

1060
00:38:37.565 --> 00:38:39.585
- not it's not expensive to do these things.

1061
00:38:40.204 --> 00:38:41.344
- So there are actually,

1062
00:38:41.885 --> 00:38:43.744
- a whole lot of relays already,

1063
00:38:44.525 --> 00:38:46.125
- running on the network for a whole bunch

1064
00:38:46.125 --> 00:38:47.105
- of various reasons.

1065
00:38:47.885 --> 00:38:48.784
- And now

1066
00:38:49.340 --> 00:38:51.260
- when you talk about running a relay or

1067
00:38:51.260 --> 00:38:51.840
- a server,

1068
00:38:52.219 --> 00:38:54.300
- automatically, what a lot of IT people are

1069
00:38:54.300 --> 00:38:56.960
- gonna think is I have a physical server

1070
00:38:57.659 --> 00:38:58.159
- located.

1071
00:38:58.539 --> 00:38:59.440
- But in reality,

1072
00:39:00.059 --> 00:39:02.239
- this could be something that you go to

1073
00:39:02.300 --> 00:39:02.800
- DigitalOcean

1074
00:39:03.420 --> 00:39:05.155
- or some Oh, yeah. It could be a

1075
00:39:05.155 --> 00:39:07.554
- VBS. Could be. Yeah. Sure. And you could

1076
00:39:07.554 --> 00:39:10.034
- just go to their app store and say,

1077
00:39:10.034 --> 00:39:11.815
- stand me up a Nostra server

1078
00:39:12.594 --> 00:39:15.315
- or Sure. Nostra Relay if that were available.

1079
00:39:15.315 --> 00:39:17.519
- I don't know if that's available today. And

1080
00:39:17.519 --> 00:39:19.599
- boom. It just runs, and they just bill

1081
00:39:19.599 --> 00:39:20.739
- you based on usage

1082
00:39:21.679 --> 00:39:22.420
- for whatever.

1083
00:39:22.960 --> 00:39:24.480
- Yeah. Or you do or you do it

1084
00:39:24.480 --> 00:39:26.239
- on your Raspberry Pi. I mean, you're you're

1085
00:39:26.239 --> 00:39:27.679
- you're gonna have to do some some some

1086
00:39:27.679 --> 00:39:29.280
- stuff in your router, but it it... It's

1087
00:39:29.280 --> 00:39:32.000
- like everything in between. Sure. Yeah. Okay. So

1088
00:39:32.000 --> 00:39:32.660
- what about,

1089
00:39:33.724 --> 00:39:35.324
- a lot of... Everything we've been talking about

1090
00:39:35.324 --> 00:39:36.065
- is content,

1091
00:39:36.364 --> 00:39:39.085
- produced by humans. What about machine to machine

1092
00:39:39.085 --> 00:39:41.885
- communication? Are there any novel use cases there,

1093
00:39:41.885 --> 00:39:43.485
- or is it now it's just JSON? There's

1094
00:39:43.485 --> 00:39:45.344
- no there's no special thing here?

1095
00:39:47.900 --> 00:39:50.539
- Well, the nice thing about Nasr is it

1096
00:39:50.539 --> 00:39:51.839
- runs on key pairs.

1097
00:39:52.219 --> 00:39:53.819
- And the nice thing about a key pair

1098
00:39:53.819 --> 00:39:55.980
- is that a computer has no issue in

1099
00:39:55.980 --> 00:39:58.059
- generating a key pair. Like, an AI has

1100
00:39:58.059 --> 00:39:59.819
- no problem in generating a key pair and

1101
00:39:59.819 --> 00:40:00.319
- start

1102
00:40:00.835 --> 00:40:01.335
- publicizing,

1103
00:40:02.515 --> 00:40:03.974
- using his own signed content.

1104
00:40:05.554 --> 00:40:06.054
- So,

1105
00:40:06.675 --> 00:40:08.855
- AIs are first citizens, in Nasser.

1106
00:40:09.715 --> 00:40:12.594
- And it's something interest... A lot of people

1107
00:40:12.594 --> 00:40:13.920
- are already working on this.

1108
00:40:14.480 --> 00:40:16.159
- And one of those people is actually Jack

1109
00:40:16.159 --> 00:40:17.460
- Dorsey with Block,

1110
00:40:18.079 --> 00:40:20.159
- and they recently came out with an app

1111
00:40:20.159 --> 00:40:20.900
- called Buzz,

1112
00:40:22.079 --> 00:40:22.579
- where

1113
00:40:22.960 --> 00:40:23.460
- they...

1114
00:40:23.839 --> 00:40:25.460
- So it's like it's like Slack,

1115
00:40:27.184 --> 00:40:28.965
- where... And which is just,

1116
00:40:29.744 --> 00:40:31.344
- in this case, it's just a a NASA

1117
00:40:31.344 --> 00:40:34.385
- relay where you... You're you're running your your

1118
00:40:34.385 --> 00:40:35.284
- chats on.

1119
00:40:36.144 --> 00:40:39.344
- And because there is no distinction between a

1120
00:40:39.344 --> 00:40:40.324
- human or

1121
00:40:41.259 --> 00:40:44.079
- a machine, it's just key pairs publicizing things.

1122
00:40:44.859 --> 00:40:45.359
- You...

1123
00:40:46.139 --> 00:40:48.699
- Within Buzz, you just run a Slack channel

1124
00:40:48.699 --> 00:40:50.699
- where your your agents are present, and you

1125
00:40:50.699 --> 00:40:52.844
- can have multiple people and multiple agents,

1126
00:40:54.844 --> 00:40:55.664
- cooperating right there,

1127
00:40:56.525 --> 00:40:57.585
- within this space.

1128
00:40:58.125 --> 00:41:00.465
- So there... There's already stuff happening there.

1129
00:41:01.324 --> 00:41:02.925
- And, you know, the same thing, it's like...

1130
00:41:02.925 --> 00:41:04.385
- It it doesn't need to

1131
00:41:04.764 --> 00:41:06.869
- get an account at GitHub. It's just exact

1132
00:41:06.869 --> 00:41:08.309
- the exact same thing is, like, with the

1133
00:41:08.309 --> 00:41:10.710
- with the the Nasr Git stuff. It's like,

1134
00:41:10.710 --> 00:41:13.349
- okay. It can run-in my my, quote, unquote,

1135
00:41:13.349 --> 00:41:15.110
- Slack channel, and it can ask you to

1136
00:41:15.110 --> 00:41:17.269
- do things, and it will just automatically connect

1137
00:41:17.269 --> 00:41:19.349
- to the to the to the repo... To

1138
00:41:19.349 --> 00:41:20.090
- the Git repo

1139
00:41:20.484 --> 00:41:22.964
- and do whatever updates it has. And, as

1140
00:41:22.964 --> 00:41:25.045
- long as it has the permissions and whether

1141
00:41:25.045 --> 00:41:27.445
- it has or doesn't have those permissions or

1142
00:41:27.445 --> 00:41:30.425
- just based on... Can it... Whatever the policies

1143
00:41:30.484 --> 00:41:32.025
- are on the on on the server.

1144
00:41:32.724 --> 00:41:35.045
- And if it can produce the signature that

1145
00:41:35.045 --> 00:41:36.900
- it, then it's an okay. And if it

1146
00:41:36.900 --> 00:41:37.639
- can't, right,

1147
00:41:38.659 --> 00:41:39.400
- then not.

1148
00:41:39.780 --> 00:41:42.119
- So that's how those policies are gated. And,

1149
00:41:42.980 --> 00:41:45.139
- it can just do stuff. Whatever I can

1150
00:41:45.139 --> 00:41:46.900
- do as a human, a machine can just

1151
00:41:46.900 --> 00:41:49.925
- do, just as well. So those are the

1152
00:41:49.985 --> 00:41:52.065
- the the two things. So, like, it's a

1153
00:41:52.065 --> 00:41:52.785
- double sided,

1154
00:41:53.825 --> 00:41:55.605
- like, there are two edges right here.

1155
00:41:56.704 --> 00:41:58.864
- It it opens up, and it frees up

1156
00:41:58.864 --> 00:42:00.885
- these agents and humans to do whatever.

1157
00:42:01.640 --> 00:42:03.739
- That also means that we have to face

1158
00:42:03.800 --> 00:42:06.199
- the... All the, like, the downsides or the

1159
00:42:06.199 --> 00:42:08.760
- problems or the issues that can happen when

1160
00:42:08.760 --> 00:42:09.420
- you introduce,

1161
00:42:09.800 --> 00:42:11.180
- robots into your system.

1162
00:42:12.039 --> 00:42:14.140
- We have to face them head on. So,

1163
00:42:15.480 --> 00:42:17.724
- and, you know, we have we have all

1164
00:42:17.724 --> 00:42:20.204
- the the the ideas and means, in order

1165
00:42:20.204 --> 00:42:21.344
- to tackle those issues,

1166
00:42:21.885 --> 00:42:24.284
- but we don't have to trust, one company

1167
00:42:24.284 --> 00:42:25.505
- to come up with a solution

1168
00:42:25.964 --> 00:42:28.625
- that has to, gatekeep at the front door,

1169
00:42:30.320 --> 00:42:32.320
- because that's ultimately the only thing that there's...

1170
00:42:32.320 --> 00:42:34.079
- That they can do. Right? They they they

1171
00:42:34.079 --> 00:42:35.360
- have to sit in in front of their

1172
00:42:35.360 --> 00:42:37.679
- front door, and that's not also introducing a

1173
00:42:37.679 --> 00:42:39.920
- friction for the robot. It's also introduce... Introducing

1174
00:42:39.920 --> 00:42:41.780
- a friction for the, for the human.

1175
00:42:42.204 --> 00:42:43.804
- One of the one of the services the

1176
00:42:43.804 --> 00:42:46.704
- platform provides, I would say, is content discovery.

1177
00:42:47.085 --> 00:42:48.764
- If you don't know exactly what you want

1178
00:42:48.764 --> 00:42:50.684
- or exactly where it is, you know, they

1179
00:42:50.684 --> 00:42:52.444
- give you a way to... It's just simple

1180
00:42:52.444 --> 00:42:53.264
- search. But,

1181
00:42:53.724 --> 00:42:55.264
- how is content discovery

1182
00:42:55.644 --> 00:42:58.579
- accomplished? Is it just your community already knows

1183
00:42:58.579 --> 00:43:00.900
- which relays to use? Or is there... Are

1184
00:43:00.900 --> 00:43:03.079
- there any services that try... Attempt to catalog

1185
00:43:03.380 --> 00:43:04.199
- the content,

1186
00:43:04.739 --> 00:43:05.239
- published?

1187
00:43:05.699 --> 00:43:07.780
- Yeah. So before I answer that question, I'll

1188
00:43:07.780 --> 00:43:09.559
- just do a a reiteration,

1189
00:43:11.364 --> 00:43:13.364
- of this this mental model that I have,

1190
00:43:13.765 --> 00:43:16.405
- that ends exactly on on this point. So

1191
00:43:16.405 --> 00:43:17.385
- the old paradigm,

1192
00:43:18.724 --> 00:43:19.625
- of these platforms...

1193
00:43:20.085 --> 00:43:22.344
- What a platform ultimately does, it

1194
00:43:23.460 --> 00:43:23.960
- facilitates

1195
00:43:24.340 --> 00:43:27.139
- broadly three things. So it facilitates identity and

1196
00:43:27.139 --> 00:43:29.619
- and network, so... Or social graph. So these

1197
00:43:29.619 --> 00:43:31.460
- are... There's your account and the the connections

1198
00:43:31.460 --> 00:43:33.300
- you have, like your friends, and the people

1199
00:43:33.300 --> 00:43:34.280
- you follow, etcetera.

1200
00:43:34.980 --> 00:43:37.784
- The second thing is hosting. Right? So just

1201
00:43:38.025 --> 00:43:40.284
- hosting the actual content and making that available.

1202
00:43:40.505 --> 00:43:42.344
- And then the third part is indexing, and

1203
00:43:42.344 --> 00:43:43.065
- that's what you're,

1204
00:43:43.944 --> 00:43:46.025
- what you're asking about. So what in in

1205
00:43:46.025 --> 00:43:46.525
- Nostr,

1206
00:43:48.344 --> 00:43:50.025
- because it runs on these key pairs, it

1207
00:43:50.025 --> 00:43:53.259
- already separated the the identity part. And the

1208
00:43:53.259 --> 00:43:54.699
- the social graph is just a very simple

1209
00:43:54.699 --> 00:43:57.339
- address book. So that... We already took that

1210
00:43:57.339 --> 00:43:58.799
- away from from the platform.

1211
00:43:59.179 --> 00:43:59.679
- So,

1212
00:44:00.299 --> 00:44:02.559
- the hosting is done on these relays.

1213
00:44:03.099 --> 00:44:04.994
- As I already described, you have this this

1214
00:44:04.994 --> 00:44:07.255
- flexibility as to where you host things,

1215
00:44:08.434 --> 00:44:10.134
- and you can switch and and whatever.

1216
00:44:10.994 --> 00:44:13.255
- And then lastly, in terms of the indexing,

1217
00:44:15.714 --> 00:44:17.920
- that that is like a space where that

1218
00:44:17.920 --> 00:44:19.059
- I already partly,

1219
00:44:20.000 --> 00:44:22.239
- went into in, like, these two modes of

1220
00:44:22.239 --> 00:44:24.019
- operation where either you,

1221
00:44:25.679 --> 00:44:26.820
- trust a location,

1222
00:44:28.079 --> 00:44:29.920
- to give you a particular answer. So I

1223
00:44:29.920 --> 00:44:31.974
- connect to a relay because... And then then

1224
00:44:31.974 --> 00:44:34.375
- he relay hands over stuff that I might

1225
00:44:34.375 --> 00:44:34.875
- apparently,

1226
00:44:35.655 --> 00:44:38.214
- find interesting or whatever it is. Or I

1227
00:44:38.214 --> 00:44:40.054
- can start to do a whole bunch of

1228
00:44:40.054 --> 00:44:42.135
- things based on smart querying that I can

1229
00:44:42.135 --> 00:44:42.635
- do.

1230
00:44:42.934 --> 00:44:43.434
- And,

1231
00:44:44.539 --> 00:44:46.300
- the answer in terms of, like, the indexing

1232
00:44:46.300 --> 00:44:48.639
- is that and everything in between. So,

1233
00:44:49.420 --> 00:44:51.599
- there is a service that does

1234
00:44:51.980 --> 00:44:52.480
- indexing

1235
00:44:52.780 --> 00:44:53.260
- of,

1236
00:44:53.659 --> 00:44:54.159
- identities.

1237
00:44:54.859 --> 00:44:56.480
- And then if there is, like,

1238
00:44:56.940 --> 00:44:59.099
- if you... If Russ White has, like, an

1239
00:44:59.099 --> 00:44:59.599
- identity,

1240
00:44:59.954 --> 00:45:01.795
- it will do a bunch of, weapon trust

1241
00:45:01.795 --> 00:45:02.614
- type of analysis,

1242
00:45:03.075 --> 00:45:05.075
- to figure out, it's like, okay, who's probably

1243
00:45:05.075 --> 00:45:07.795
- the real Russ Wright. Right? So what what

1244
00:45:07.795 --> 00:45:10.835
- key pair, is associated with what is probably

1245
00:45:10.835 --> 00:45:13.160
- the real Russ White? And I can just

1246
00:45:13.160 --> 00:45:15.320
- search there and then probably find what,

1247
00:45:15.960 --> 00:45:17.500
- the real Russ White pretty easily.

1248
00:45:18.280 --> 00:45:20.140
- And the same thing for content.

1249
00:45:21.320 --> 00:45:23.000
- And there are, like, a thousand different ways

1250
00:45:23.000 --> 00:45:24.680
- that you can approach this problem, Tom. I

1251
00:45:24.680 --> 00:45:26.059
- mean, you can do the,

1252
00:45:27.614 --> 00:45:29.155
- what's the Google method called?

1253
00:45:29.775 --> 00:45:32.414
- It escapes me. The scatter gather and what

1254
00:45:32.414 --> 00:45:33.315
- you're talking about.

1255
00:45:33.695 --> 00:45:34.195
- No.

1256
00:45:35.614 --> 00:45:37.295
- Page rank. So you can do the page

1257
00:45:37.295 --> 00:45:37.934
- rank thing.

1258
00:45:38.414 --> 00:45:40.175
- And there is a party that does page

1259
00:45:40.175 --> 00:45:41.474
- rank on top of Gnastr.

1260
00:45:43.210 --> 00:45:45.130
- You can do the web of trust,

1261
00:45:45.450 --> 00:45:48.170
- route where, okay, I filter based on my

1262
00:45:48.170 --> 00:45:48.829
- own network.

1263
00:45:49.210 --> 00:45:51.230
- And because my social graphs are,

1264
00:45:51.769 --> 00:45:53.610
- are not stuck within a silo. Right? I

1265
00:45:53.610 --> 00:45:54.170
- can just,

1266
00:45:54.570 --> 00:45:56.570
- leverage my social graph and the social graph

1267
00:45:56.570 --> 00:45:57.390
- of other people,

1268
00:45:57.755 --> 00:46:00.655
- within particular domains. So if I have relevant

1269
00:46:00.715 --> 00:46:02.094
- social graph for,

1270
00:46:03.114 --> 00:46:05.914
- chefs, right, cooking chefs, because I... That happens

1271
00:46:05.914 --> 00:46:07.675
- to be a domain of interest for me,

1272
00:46:07.675 --> 00:46:09.594
- I can start to leverage that in the

1273
00:46:09.594 --> 00:46:11.860
- context of looking for a restaurant in a

1274
00:46:11.860 --> 00:46:12.360
- particular,

1275
00:46:12.980 --> 00:46:14.199
- in a particular place.

1276
00:46:15.699 --> 00:46:18.019
- So there are whole different ways in which

1277
00:46:18.019 --> 00:46:19.300
- you can tackle this,

1278
00:46:19.860 --> 00:46:20.519
- this problem.

1279
00:46:21.780 --> 00:46:23.464
- So there's no one answer there, Tom. I

1280
00:46:23.464 --> 00:46:24.585
- mean, it's a it's a it's a hard

1281
00:46:24.585 --> 00:46:26.505
- problem. There's no silver bullet to this, so

1282
00:46:26.505 --> 00:46:28.265
- we'll just throw everything in the kitchen sink

1283
00:46:28.265 --> 00:46:29.565
- at it and see what sticks.

1284
00:46:30.824 --> 00:46:32.844
- Yeah. Yeah. It makes sense. So

1285
00:46:33.945 --> 00:46:35.769
- if people wanted to get involved in this,

1286
00:46:35.769 --> 00:46:37.610
- I see there's a git repository. It doesn't

1287
00:46:37.610 --> 00:46:39.690
- look very active. Maybe I'm not looking at

1288
00:46:39.690 --> 00:46:40.510
- the right one.

1289
00:46:42.410 --> 00:46:43.869
- Nostril protocol. Anyway,

1290
00:46:44.490 --> 00:46:47.230
- if people want to get involved with this,

1291
00:46:48.275 --> 00:46:50.355
- I assume there's two sides to this. First

1292
00:46:50.355 --> 00:46:50.855
- is

1293
00:46:51.235 --> 00:46:53.635
- the side of helping to develop things, to

1294
00:46:53.635 --> 00:46:55.875
- develop the protocol and do stuff. And I

1295
00:46:55.875 --> 00:46:57.575
- assume there must be a,

1296
00:46:58.594 --> 00:47:00.614
- like, relay server for that

1297
00:47:01.315 --> 00:47:01.815
- work,

1298
00:47:02.780 --> 00:47:04.400
- as well as the GitHub repository.

1299
00:47:06.780 --> 00:47:08.940
- Like, no. The the the answer the answer

1300
00:47:08.940 --> 00:47:10.239
- is no, Ross. So,

1301
00:47:11.019 --> 00:47:12.159
- Nasr is an idea

1302
00:47:12.460 --> 00:47:14.875
- that one dude came up with, and that's

1303
00:47:14.875 --> 00:47:17.035
- it. So there's no organization. I mean, you're

1304
00:47:17.035 --> 00:47:18.394
- looking at a website. I don't know what

1305
00:47:18.394 --> 00:47:20.315
- website you're looking at, but there's no the

1306
00:47:20.315 --> 00:47:22.795
- Nostra website. There just happened to be websites

1307
00:47:22.795 --> 00:47:23.454
- about Nostra.

1308
00:47:25.195 --> 00:47:27.119
- Well, there's a nostra.org.

1309
00:47:27.200 --> 00:47:28.640
- Yeah. So the... If if I were sent

1310
00:47:28.640 --> 00:47:30.480
- to... Send people to some place, I would

1311
00:47:30.480 --> 00:47:31.920
- send them to nostra.org.

1312
00:47:32.559 --> 00:47:33.940
- And most of the,

1313
00:47:35.280 --> 00:47:36.500
- information and,

1314
00:47:38.000 --> 00:47:40.880
- additional resources and stuff, you can, find from

1315
00:47:40.880 --> 00:47:41.744
- find from there.

1316
00:47:42.945 --> 00:47:44.545
- So is there not a is there not

1317
00:47:44.545 --> 00:47:47.045
- a primary steward of the of the protocols?

1318
00:47:47.105 --> 00:47:48.945
- It's just everybody, like, how does... What do

1319
00:47:48.945 --> 00:47:49.525
- you mean?

1320
00:47:50.065 --> 00:47:52.405
- Who who who who stewards the idea?

1321
00:47:52.865 --> 00:47:55.960
- Maintains, I guess, from a code perspective, who

1322
00:47:55.960 --> 00:47:58.280
- maintains Yeah. Someone has to write code. Decides

1323
00:47:58.280 --> 00:48:00.619
- what... Who who decides what gets pushed.

1324
00:48:01.079 --> 00:48:03.079
- If somebody random just comes up with an

1325
00:48:03.079 --> 00:48:05.000
- idea and pushes it to code and it

1326
00:48:05.000 --> 00:48:07.000
- breaks everything, is there somebody who actually

1327
00:48:07.480 --> 00:48:08.869
- Breaks what? Reviews.

1328
00:48:09.284 --> 00:48:10.344
- Well The implementation.

1329
00:48:10.804 --> 00:48:11.464
- The implementation.

1330
00:48:11.764 --> 00:48:13.364
- At some point, it has to be compiled.

1331
00:48:13.364 --> 00:48:14.744
- Right? What what implementation?

1332
00:48:16.644 --> 00:48:19.464
- Okay. The apps that use... Yeah. Yeah.

1333
00:48:19.924 --> 00:48:21.364
- I mean, you can have an app. You

1334
00:48:21.364 --> 00:48:23.784
- can... It's it's like saying who's gonna,

1335
00:48:24.329 --> 00:48:26.510
- like, who's in charge of the Internet? Because,

1336
00:48:27.610 --> 00:48:29.050
- we have a bunch of browsers, and we

1337
00:48:29.050 --> 00:48:31.530
- need some control of Somebody's in charge of

1338
00:48:31.530 --> 00:48:32.030
- HTTP.

1339
00:48:32.489 --> 00:48:34.090
- There is someone in charge of that. So

1340
00:48:34.090 --> 00:48:35.309
- who's in charge of Nostr?

1341
00:48:35.690 --> 00:48:37.530
- I mean... Okay. And my answer would be

1342
00:48:37.530 --> 00:48:39.070
- Google is in charge of HTTP.

1343
00:48:39.724 --> 00:48:42.684
- So it's like... So be... Because Chrome Chrome...

1344
00:48:42.684 --> 00:48:44.844
- Whoever developing Chrome is in charge of whatever

1345
00:48:44.844 --> 00:48:46.765
- web standards that we're we're we're having right

1346
00:48:46.765 --> 00:48:48.605
- now. And that that... That's the point with

1347
00:48:48.605 --> 00:48:50.445
- Nasr is, like, we don't... There's there's NIPRO

1348
00:48:50.445 --> 00:48:52.364
- one. There's nothing gonna change about NIPRO one.

1349
00:48:52.364 --> 00:48:54.284
- There... There's a protocol, and nothing's gonna change

1350
00:48:54.284 --> 00:48:56.840
- about the base protocol. And everything else on

1351
00:48:56.840 --> 00:48:58.360
- top of it is just... It's it's,

1352
00:48:58.840 --> 00:49:01.019
- it's a free for all. It's completely permissionless.

1353
00:49:01.640 --> 00:49:03.480
- I mean, in practice, there is a Git

1354
00:49:03.480 --> 00:49:03.980
- repository

1355
00:49:04.440 --> 00:49:05.660
- of of,

1356
00:49:06.519 --> 00:49:09.184
- stuff that people are coordinating around. But it's

1357
00:49:09.184 --> 00:49:11.045
- a mirage. It's not real, Tom.

1358
00:49:11.344 --> 00:49:12.784
- You can find you can find the git

1359
00:49:12.784 --> 00:49:15.184
- repository to everybody. It's not real. There's nothing

1360
00:49:15.184 --> 00:49:17.525
- real. The only thing real is nipo one

1361
00:49:17.664 --> 00:49:20.065
- is we use Schnorr signatures in shot two

1362
00:49:20.065 --> 00:49:22.710
- fifty six. We do it over JSON with

1363
00:49:23.030 --> 00:49:24.289
- the the,

1364
00:49:24.869 --> 00:49:27.349
- the public key, the date, the kind, the,

1365
00:49:27.750 --> 00:49:30.170
- the the tags, the content, the signature,

1366
00:49:30.869 --> 00:49:33.109
- and we do it over WebSockets. And we

1367
00:49:33.109 --> 00:49:35.510
- have, here's a handful of queries that we,

1368
00:49:35.829 --> 00:49:38.755
- expect you to respond to or understand when

1369
00:49:38.755 --> 00:49:41.414
- you're communicating with the relay. And that's it.

1370
00:49:42.755 --> 00:49:44.755
- Okay. But if you wanted to add a

1371
00:49:44.755 --> 00:49:46.295
- new query, for instance,

1372
00:49:46.914 --> 00:49:49.255
- there must be a community someplace that

1373
00:49:50.760 --> 00:49:51.640
- that decides

1374
00:49:52.039 --> 00:49:54.619
- Discusses it or Discusses it or whatever.

1375
00:49:55.320 --> 00:49:55.800
- Yeah.

1376
00:49:57.160 --> 00:49:59.079
- You... What you do... What you probably do...

1377
00:49:59.079 --> 00:50:00.840
- Like, the easiest way is just to download

1378
00:50:00.840 --> 00:50:01.800
- a NoStar client

1379
00:50:02.599 --> 00:50:04.360
- Okay. For your phone or or or for

1380
00:50:04.360 --> 00:50:05.019
- your desktop.

1381
00:50:05.614 --> 00:50:06.815
- There are there are a whole bunch of

1382
00:50:06.815 --> 00:50:07.315
- them.

1383
00:50:07.694 --> 00:50:08.194
- And,

1384
00:50:09.295 --> 00:50:12.494
- then those... The client will probably introduce you

1385
00:50:12.494 --> 00:50:12.994
- to,

1386
00:50:13.375 --> 00:50:15.054
- some follow packs or,

1387
00:50:15.694 --> 00:50:16.914
- people you could follow.

1388
00:50:18.599 --> 00:50:20.599
- And then you'll you'll see a bunch of

1389
00:50:20.599 --> 00:50:22.680
- discussion, and you'll you'll you'll you'll browse a

1390
00:50:22.680 --> 00:50:24.360
- lot... You browse around. You surf a little

1391
00:50:24.360 --> 00:50:26.039
- bit, and you figure out, okay, who's are

1392
00:50:26.039 --> 00:50:27.480
- the... Who are the... Who are the people

1393
00:50:27.480 --> 00:50:28.619
- developing on Noster.

1394
00:50:29.320 --> 00:50:30.200
- And then you,

1395
00:50:31.755 --> 00:50:33.594
- cover the landscape a bit, and then you,

1396
00:50:34.315 --> 00:50:36.394
- start to join in somewhere, and you start

1397
00:50:36.394 --> 00:50:38.155
- to do stuff. You can just go ahead

1398
00:50:38.155 --> 00:50:40.635
- and do things yourself. Right? So you would

1399
00:50:40.635 --> 00:50:42.554
- say the easiest or the best way to

1400
00:50:42.554 --> 00:50:45.114
- get involved in Nostr is to simply become

1401
00:50:45.114 --> 00:50:46.335
- a Nostr user

1402
00:50:47.139 --> 00:50:49.300
- and then find the the groups of users

1403
00:50:49.300 --> 00:50:50.519
- who are doing development

1404
00:50:51.380 --> 00:50:53.940
- Sure. Over time. Okay. That's how I said,

1405
00:50:53.940 --> 00:50:56.260
- like, what is a practical step for people

1406
00:50:56.260 --> 00:50:58.199
- who want to get involved with this

1407
00:50:58.659 --> 00:51:00.579
- to go get involved in it? Because there...

1408
00:51:00.579 --> 00:51:02.099
- I mean, there are people listening who will

1409
00:51:02.099 --> 00:51:03.885
- say, this is really cool. What do I

1410
00:51:03.885 --> 00:51:05.485
- do? You know, how do I do this?

1411
00:51:05.485 --> 00:51:06.925
- It's the only thing... So so a bit

1412
00:51:06.925 --> 00:51:09.164
- of honesty here is, like, in in terms

1413
00:51:09.164 --> 00:51:11.005
- of, like, how many users are there on

1414
00:51:11.005 --> 00:51:11.505
- Lostr,

1415
00:51:12.765 --> 00:51:15.539
- the only group that we've had success with

1416
00:51:15.539 --> 00:51:19.140
- in actually attracting and retaining are developers. So

1417
00:51:19.140 --> 00:51:21.219
- it's just... So that's the... Also, the other

1418
00:51:21.219 --> 00:51:23.300
- part of the answer is, like, well, everybody

1419
00:51:23.300 --> 00:51:25.460
- on Noster is probably gonna be, the odds

1420
00:51:25.460 --> 00:51:27.380
- are that most people you're gonna find are

1421
00:51:27.380 --> 00:51:28.360
- are actually developers.

1422
00:51:28.855 --> 00:51:30.454
- And most of the discussion that you're gonna

1423
00:51:30.454 --> 00:51:32.315
- find is either beyond Nostra or,

1424
00:51:32.934 --> 00:51:33.735
- to be honest, on,

1425
00:51:34.535 --> 00:51:35.355
- on Bitcoin,

1426
00:51:35.815 --> 00:51:38.055
- because that that was the initial group that,

1427
00:51:38.295 --> 00:51:39.974
- came in. But that doesn't mean that there

1428
00:51:39.974 --> 00:51:42.795
- is only discussion about Nostra or only Bitcoiners

1429
00:51:42.855 --> 00:51:44.280
- or only these people. There,

1430
00:51:44.760 --> 00:51:46.280
- there are more people and there are more

1431
00:51:46.280 --> 00:51:47.960
- discussions going on. You're just gonna have to

1432
00:51:47.960 --> 00:51:49.640
- look for it because the the initial thing

1433
00:51:49.640 --> 00:51:51.659
- that you're gonna encounter is probably that.

1434
00:51:52.280 --> 00:51:54.140
- You just have to understand is that

1435
00:51:54.679 --> 00:51:56.599
- there is nothing... There is no place here.

1436
00:51:56.599 --> 00:51:58.920
- Right? There's a method. There's a method called

1437
00:51:58.920 --> 00:52:01.135
- Nostr, and you're just encountering a bunch of

1438
00:52:01.135 --> 00:52:03.054
- people that are using that method. And there

1439
00:52:03.054 --> 00:52:05.135
- are also other people, and everybody is able

1440
00:52:05.135 --> 00:52:05.635
- to,

1441
00:52:06.734 --> 00:52:07.635
- free to,

1442
00:52:08.014 --> 00:52:09.474
- to start using this method.

1443
00:52:10.894 --> 00:52:11.875
- So, yeah, just,

1444
00:52:12.769 --> 00:52:14.449
- just... You can just go ahead there. It's

1445
00:52:14.449 --> 00:52:16.469
- it's permissionless. You can just do things.

1446
00:52:16.929 --> 00:52:18.389
- Okay. Alright. Cool.

1447
00:52:18.769 --> 00:52:20.690
- Alright. So I think that pretty much covers

1448
00:52:20.690 --> 00:52:23.429
- it. So we'll wrap up. So, Constant, do

1449
00:52:24.210 --> 00:52:26.625
- you have a blog or anything where you...

1450
00:52:26.704 --> 00:52:29.125
- People can follow what you've been working on,

1451
00:52:30.385 --> 00:52:31.605
- anything like that?

1452
00:52:32.945 --> 00:52:34.625
- As for as for me, no. I'm not

1453
00:52:34.625 --> 00:52:36.304
- set up well enough, but I'm not important,

1454
00:52:36.304 --> 00:52:37.125
- Russ. So

1455
00:52:37.505 --> 00:52:38.784
- just let people go to,

1456
00:52:39.344 --> 00:52:41.125
- people can go to, to,

1457
00:52:41.664 --> 00:52:42.599
- nostril.org.

1458
00:52:43.720 --> 00:52:46.519
- Okay. And, there is a... I've done a

1459
00:52:46.519 --> 00:52:47.739
- presentation on Fosdem,

1460
00:52:48.200 --> 00:52:50.519
- last year, and it's linked there, and you

1461
00:52:50.519 --> 00:52:50.920
- can,

1462
00:52:51.720 --> 00:52:53.880
- for for developer minded people, they can,

1463
00:52:54.280 --> 00:52:55.099
- watch that.

1464
00:52:55.775 --> 00:52:57.535
- And then I go basically over all the,

1465
00:52:57.775 --> 00:52:59.454
- all the stuff again, but in a bit

1466
00:52:59.454 --> 00:53:00.675
- more organized manner.

1467
00:53:01.855 --> 00:53:04.094
- And then, you know, if they they look

1468
00:53:04.094 --> 00:53:06.255
- around and they come across a constant, it's

1469
00:53:06.255 --> 00:53:09.855
- probably me. So... Okay. Cool. Alright. Tom, where

1470
00:53:09.855 --> 00:53:11.880
- can people find you? LinkedIn.

1471
00:53:13.380 --> 00:53:13.880
- Boo.

1472
00:53:17.059 --> 00:53:19.380
- So I've never been booed before on this

1473
00:53:19.380 --> 00:53:21.780
- podcast. That's not the answer. You, Tom. I'm

1474
00:53:21.780 --> 00:53:22.599
- booing LinkedIn.

1475
00:53:22.900 --> 00:53:25.139
- I'm booing all the all the things. It's

1476
00:53:25.139 --> 00:53:27.055
- like, is this thing a is this thing

1477
00:53:27.055 --> 00:53:29.055
- a Spotify? Of course, this this podcast is

1478
00:53:29.055 --> 00:53:29.715
- on Spotify.

1479
00:53:30.255 --> 00:53:32.255
- Right? You could... We already have we already

1480
00:53:32.255 --> 00:53:34.815
- have RSS and, like, an open podcasting standard.

1481
00:53:34.815 --> 00:53:36.414
- But where is this podcast? Of course, it's

1482
00:53:36.414 --> 00:53:38.035
- on Spotify. It's on the platform.

1483
00:53:39.519 --> 00:53:42.320
- So Actually, this this this podcast is actually

1484
00:53:42.320 --> 00:53:43.059
- on Blueberry.

1485
00:53:43.680 --> 00:53:45.119
- That's why I publish it, and it just

1486
00:53:45.119 --> 00:53:48.079
- gets cross posted to everything else. I tried

1487
00:53:48.079 --> 00:53:50.640
- hosting my own podcast files for a while,

1488
00:53:50.640 --> 00:53:52.559
- and it just turned out to be a

1489
00:53:52.559 --> 00:53:54.980
- pain to figure out how to get on

1490
00:53:55.815 --> 00:53:58.614
- all the other services, basically. It's it's not

1491
00:53:58.614 --> 00:54:00.454
- the hosting of the files. It's not... That's

1492
00:54:00.454 --> 00:54:02.635
- not the hard part. The hard part is,

1493
00:54:02.695 --> 00:54:05.275
- oh, you wanna get your content on Amazon

1494
00:54:05.494 --> 00:54:05.994
- Podcast?

1495
00:54:06.695 --> 00:54:08.679
- Oh, well, there's 5,000

1496
00:54:08.679 --> 00:54:11.559
- hoops you've gotta jump through. Right. Basically, you

1497
00:54:11.559 --> 00:54:13.160
- end up paying a service just to jump

1498
00:54:13.160 --> 00:54:14.760
- through the hoops and get you on all

1499
00:54:14.760 --> 00:54:16.840
- the... Get you in all the right feeds

1500
00:54:16.840 --> 00:54:18.679
- is what you end up doing, which is

1501
00:54:18.679 --> 00:54:21.000
- kinda crazy. But like you said before, that's

1502
00:54:21.000 --> 00:54:22.545
- kind of the world we live in. Right?

1503
00:54:22.545 --> 00:54:24.065
- That's Yeah. Noster is here to save you,

1504
00:54:24.065 --> 00:54:25.844
- Russ. It's gonna be okay.

1505
00:54:27.425 --> 00:54:29.264
- The cavalry cavalry is coming. So

1506
00:54:30.385 --> 00:54:31.984
- Alright. Well, I'm Russ White. You can find

1507
00:54:31.984 --> 00:54:33.744
- me here at The Hedge on all the

1508
00:54:33.744 --> 00:54:35.984
- usual social kind of places every now and

1509
00:54:35.984 --> 00:54:38.010
- again whenever I do feel like logging in,

1510
00:54:38.010 --> 00:54:40.170
- which isn't all that often or all that

1511
00:54:40.170 --> 00:54:42.250
- common, but I still do from time to

1512
00:54:42.250 --> 00:54:42.750
- time.

1513
00:54:43.130 --> 00:54:44.650
- And we know we live in an attention

1514
00:54:44.650 --> 00:54:46.969
- driven economy, so we thank you for listening

1515
00:54:46.969 --> 00:54:48.329
- all the way to the bitter end of

1516
00:54:48.329 --> 00:54:50.355
- this episode of the episode of The Hedge,

1517
00:54:50.594 --> 00:54:51.894
- and we will catch you

1518
00:54:54.594 --> 00:54:55.094
- next.