1
00:00:00,000 --> 00:00:14,280
Hi. Hi. Hi. Hi, everyone. Can you hear me? Yes. Yeah, fine. Thanks. I'm not sure what

2
00:00:14,280 --> 00:00:22,400
I'm going to talk about. So you probably should just ask questions. How do you make money?

3
00:00:22,400 --> 00:00:38,240
Oh, I don't. Thank you. Oh, good. Do you know what he's created? No. Do I want to know?

4
00:00:38,240 --> 00:00:48,440
Yeah, of course, man. He actually has a crazy nice Micrap. Bruegman is one of the most important

5
00:00:48,440 --> 00:00:59,920
creators on Oster based on the the many services that the microservices that he's he's provided.

6
00:00:59,920 --> 00:01:11,200
He provides an API for search that some of the most popular clients use. What? What? What?

7
00:01:11,200 --> 00:01:19,400
What kind of framework do you build your APIs in, sir? I don't have a framework. It's all

8
00:01:19,400 --> 00:01:32,440
homegrown stuff. So. But what any specific language? C++. It is. Shit, bro. This guy's

9
00:01:32,440 --> 00:01:46,080
writing APIs and C++ in 2023. Let's go. Oh, well, don't forget. He he also copied the

10
00:01:46,080 --> 00:01:56,240
Nostra plebs description for Nip zero five. And that's OK. That's OK. Oh, people have

11
00:01:56,240 --> 00:02:08,240
Derek H.O. Did I know Derek doesn't hate Derek loves everybody. But you did. But that's fine.

12
00:02:08,240 --> 00:02:16,200
Everybody did. Derek, do you do you own word? Do you own words now? I do. I'm the Nostra

13
00:02:16,200 --> 00:02:26,720
CEO for words. He has the order. OK, owns it. Derek, are you trying to describe the

14
00:02:26,720 --> 00:02:38,880
end at all? Fuck ordinals, man, like. Listen, I'm OK. You have an inscribed DN. I'm OK

15
00:02:38,880 --> 00:02:43,560
with people using ordinals because nobody should be able to tell anybody else what they

16
00:02:43,560 --> 00:02:51,080
can do with Bitcoin. Generally speaking, fuck ordinals, though. I just I need you to ask

17
00:02:51,080 --> 00:02:57,760
me what's DN so I can say these nuts. I just I've already I've already inscribed an actual

18
00:02:57,760 --> 00:03:04,280
picture of my nuts on. Let's go find it. I'm not even joking. It's literally just it's

19
00:03:04,280 --> 00:03:15,400
not my dick. Don't get too. It's just my. So so our art. I mean, let's get back on topic.

20
00:03:15,400 --> 00:03:27,400
Let's get back on top of it. Zero five aside, Archer has provided great, great services,

21
00:03:27,400 --> 00:03:38,080
analytics that that like analytics that everybody uses search that everybody uses. Snort Snort

22
00:03:38,080 --> 00:03:44,800
and Amethyst, two of the most popular clients, use his services. Everybody should absolutely

23
00:03:44,800 --> 00:03:52,400
love what he I receive them brought. I was used to. Yeah. So three of the four most popular

24
00:03:52,400 --> 00:03:59,000
services use his search API. It's amazing. Like we should all be very, very thankful

25
00:03:59,000 --> 00:04:05,000
for what British does. I mean, he called me. Why are you chastising him for using fucking

26
00:04:05,000 --> 00:04:12,240
word? He caught he copied my zero five ID. But we get it, man. You love you. You love

27
00:04:12,240 --> 00:04:18,560
your nips. And just I love my. Oh, yeah. Listen, I'm a guy. Give the guy. I'm allowed to love

28
00:04:18,560 --> 00:04:23,480
what he's done and give him a little shit from time to time. Right. Derek, Derek, you

29
00:04:23,480 --> 00:04:29,320
don't own the goddamn English language. OK, this is I know that for a fact because I own

30
00:04:29,320 --> 00:04:36,360
it. I did think so. I saw those copyrighted. You and Craig Wright, actually. Craig Wright

31
00:04:36,360 --> 00:04:41,560
actually invented art. Archer, Archer, listen, man. I love you, man. You do great work. Why

32
00:04:41,560 --> 00:04:49,160
did you copy my verbiage? No, I'm kidding. I'm kidding. Derek's been drinking. Yeah,

33
00:04:49,160 --> 00:04:58,960
we're part of that. We had a couple of years. No, no, no problem. I noticed. No, no. Honestly,

34
00:04:58,960 --> 00:05:05,440
Archer, you're great. Thank you for your work. Like three, three of the four major clients

35
00:05:05,440 --> 00:05:12,000
couldn't do what they do without you. Thank you. And you helped me out also a couple of

36
00:05:12,000 --> 00:05:18,840
months ago whenever I wasn't aware that Ellen Bitz, whenever you are, I wasn't aware when

37
00:05:18,840 --> 00:05:26,680
you signed in a NOSTER.com or Enigma that it overwrote your lightning address. And you

38
00:05:26,680 --> 00:05:38,640
helped me out via your your search tool on profiles. So thank you for everything you've

39
00:05:38,640 --> 00:05:44,880
done. Thank you. You're welcome. Derek, please don't be so sincere moving forward. It's a

40
00:05:44,880 --> 00:05:54,920
little weird. And you know what? And to find out Cassie was a fraud, I went to NOSTER.band

41
00:05:54,920 --> 00:06:01,680
and I looked at the profile for Cassie and I saw that Cassie's first fucking day on NOSTER,

42
00:06:01,680 --> 00:06:08,000
her name was Zeeboob. So wait, wait, wait, wait, wait. What? What? Oh, did you see the

43
00:06:08,000 --> 00:06:14,880
creation date? How was like three days? For her first no. Yes. It was April 24th. April

44
00:06:14,880 --> 00:06:22,160
24th. It was Zeeboob. The profile, the Nip05 and the lightning address because they signed

45
00:06:22,160 --> 00:06:28,560
up for they signed up via current and current provides those services. But the name was

46
00:06:28,560 --> 00:06:35,120
Zeeboob for three fucking days, two and a half days before they changed it to Cassie.

47
00:06:35,120 --> 00:06:46,720
But it's all it's all because of Archer's service. He has anyone image search that EFP?

48
00:06:46,720 --> 00:06:53,040
It's a look at the because that's just seems like the easiest way to figure this out. No,

49
00:06:53,040 --> 00:06:58,240
look at the image, man. The images from this pro this image does not exist. This person

50
00:06:58,240 --> 00:07:06,320
does not exist dot com. Look at it. It's a generated image. Wait, did you actually did

51
00:07:06,320 --> 00:07:12,360
you did you image search on Google? Yes, I am researches on Google. So it is actually

52
00:07:12,360 --> 00:07:18,440
from this person is not a good dot com. And I mean, I knew it. Wait, no, is it Derek or

53
00:07:18,440 --> 00:07:23,640
are you just saying this? The image doesn't exist anywhere else. But that's fine. We've

54
00:07:23,640 --> 00:07:30,200
all taken pictures that have never existed online anywhere else. But look at the picture.

55
00:07:30,200 --> 00:07:35,800
Is the dude that she's sitting beside a Shakespeare wearing a Shakespeare costume? It doesn't

56
00:07:35,800 --> 00:07:44,600
exist. I'm sorry. It's not real. Cassie shows up in the nest right now. All right. So this

57
00:07:44,600 --> 00:07:50,840
is our listen. This is Arthur Brugman's space. His nest. Yeah. Yeah. We're done talking about

58
00:07:50,840 --> 00:07:57,880
Cassie Derek. Shut up. He's amazing and provide services for the entire Nostra community.

59
00:07:57,880 --> 00:08:01,240
And let me guess. Let me guess. He took your name right here.

60
00:08:01,240 --> 00:08:06,040
Yeah. Magoo, fuck you for a little bit. OK, we're going to talk about how he's awesome.

61
00:08:06,040 --> 00:08:14,440
Here we go again. I really want to ask about the RSS feed because I'm super interested

62
00:08:14,440 --> 00:08:21,320
about that. I actually tried it out the other day. But yeah, Archer, I fucking love Nostra

63
00:08:21,320 --> 00:08:24,760
that band. I literally use it all the time. Magoo, if you want to ever find a fucking

64
00:08:24,760 --> 00:08:29,960
note that you've done and no client wants to show it to you, this guy right here, man,

65
00:08:29,960 --> 00:08:36,040
you can literally put in any keyword inside that search with whatever nipple fiber, you

66
00:08:36,040 --> 00:08:39,000
know, whatever fucking name. You don't even have to have the nipple fiber. You just put

67
00:08:39,000 --> 00:08:43,800
their like the name that they have and you'll see that note no matter how old it is. And

68
00:08:43,800 --> 00:08:48,600
no client is going to show it to you, but you'll find it in there. I need to. Yeah.

69
00:08:49,640 --> 00:08:57,240
I do actually have a legitimate question for Archer. So myself and several other

70
00:08:57,240 --> 00:09:10,360
Nostra Nip zero five ID providers are working on a document to ask people to do two different

71
00:09:10,360 --> 00:09:20,280
things. One, to stop referring to Nip zero five ID as identification. I'm sorry,

72
00:09:20,280 --> 00:09:28,120
verification, verification. And two, to stop referring to it as Nip zero five ID, because

73
00:09:28,120 --> 00:09:34,440
nobody knows what that is. But we understand as a people, we understand lightning address.

74
00:09:35,400 --> 00:09:41,160
We understand email address. So we should start calling this Nostra address. But the main

75
00:09:41,160 --> 00:09:50,600
proposal is to have clients in Nip zero five ID providers as such as Nostra plebs and such as

76
00:09:50,600 --> 00:10:00,840
Nostra.band and others to not have them refer to these things as a verification. To just

77
00:10:00,840 --> 00:10:09,160
refer to them as just a Nostra address. So far it's Nostra plebs and Nostra check and

78
00:10:09,160 --> 00:10:15,720
Bitcoin Nostra. But we would like to get multiple people on board because you know as well as I do

79
00:10:16,280 --> 00:10:23,400
is that it's not verification of anything besides somebody that enters a public key into a forum.

80
00:10:23,400 --> 00:10:31,560
Right. So I think we should stop referring to these things as verification. We shouldn't do that.

81
00:10:31,560 --> 00:10:38,760
So we're going to try to get as many people on board with this as we can.

82
00:10:40,680 --> 00:10:49,480
Yeah, I agree. And actually the word verification is mentioned just once verified in quotes

83
00:10:50,040 --> 00:10:58,120
on my site. So yeah, I totally agree. If we switch to the name Nostra address,

84
00:10:58,120 --> 00:11:04,680
then I will happily do that. Yeah, well that makes sense, right? Because it's not verification.

85
00:11:04,680 --> 00:11:18,040
Whereas Jack at cache app, cache dot app, Jack at cache dot app. There's no difference than that

86
00:11:18,040 --> 00:11:32,360
person than Jack dot, like Jack Shikani, whatever his website is, like Jack at Nostraplebs.com or

87
00:11:32,360 --> 00:11:41,800
jack dot Nostra dot band. Everybody's verified as at Jack. Right. So Derek, that means if you

88
00:11:41,800 --> 00:11:46,840
change the nomenclature, though, he's no longer plagiarizing you. So I think you just need to

89
00:11:46,840 --> 00:11:55,720
like retire that argument. Yeah, absolutely. Like, so just just a little inside baseball here.

90
00:11:56,360 --> 00:12:05,720
Preston, back in December, messaged me and said, Hey, Derek, I own Nostraverified.com. I would like

91
00:12:05,720 --> 00:12:13,320
to start having Nostraplebs and Nostraverified being the same website. Wait, Preston owns that?

92
00:12:13,320 --> 00:12:19,960
Yes. That son of a bitch. Yes. So Preston, if you're ever listening to this, use sultry son of a gun.

93
00:12:20,600 --> 00:12:28,840
So Preston messaged me and I said, Sure, here's our website, point Nostraverified.com to

94
00:12:28,840 --> 00:12:35,960
Nostraplebs.com. And he did. He pointed it there for a week or two. And then after a week or two,

95
00:12:35,960 --> 00:12:46,360
he said, Hey, we want to do verifications. And semi and I said, Well, what's verification? What

96
00:12:46,360 --> 00:12:52,360
does verification mean? Like, it verification doesn't mean anything. It just means the person

97
00:12:52,360 --> 00:12:57,880
that bought it at that domain. That's all that it means. It's just like an email address. So we had

98
00:12:57,880 --> 00:13:04,600
a conversation and we were back and forth and we didn't feel right doing verifications because that

99
00:13:05,800 --> 00:13:11,000
it's just not what we wanted to do. So he said, Hey, I want to

100
00:13:11,000 --> 00:13:21,960
unpoint our domain to Nostraplebs.com and do it on myself. And I told him, That's great. Yeah, go

101
00:13:21,960 --> 00:13:27,160
ahead and do it yourself. That's awesome. That's great. And he did. And then Preston started

102
00:13:27,160 --> 00:13:34,120
messaging all his buddies and saying, Hey, I created this website to say Nostraverified and

103
00:13:34,120 --> 00:13:39,560
you can go here to get verified and blah, blah, blah. I already created it for you. And he said,

104
00:13:39,560 --> 00:13:43,720
Well, I already created it for you. And that's cool because everybody's allowed to do whatever

105
00:13:43,720 --> 00:13:54,120
the fuck they want. And that just led to the problem that verification existed when it does not.

106
00:13:55,080 --> 00:14:02,200
It's more of an association. Do you think it was the name Nostraverified that gave it that impression?

107
00:14:02,200 --> 00:14:13,640
No, because the clients Coracle and Astral.Ninja in the beginning

108
00:14:15,640 --> 00:14:24,760
immediately started to display the name verified and they added the check mark and everybody

109
00:14:24,760 --> 00:14:31,000
followed suit because they did. And I understand it because for the past two decades, we've been

110
00:14:31,000 --> 00:14:37,000
around, we've seen the check mark, we know what the check mark means. It means verified.

111
00:14:38,760 --> 00:14:47,560
I understand why it was done, but it doesn't really mean verification. It should be an association

112
00:14:47,560 --> 00:14:56,040
more than anything. I'm with you on that. That was a long-winded way, Derek, to tell everyone

113
00:14:56,040 --> 00:15:07,000
that you don't like Preston. No, no, no. No, I like Preston. Fuck you. I've been drinking a lot of

114
00:15:07,000 --> 00:15:15,000
beer all night long. So let's keep it civil, Magoo. This is Archer's hour.

115
00:15:17,080 --> 00:15:23,800
Guys, also, I do got a dip. I hope to be able to talk to you more in the future,

116
00:15:23,800 --> 00:15:30,040
but Walker needs to go take care of his dog right now. Cheers to you all. Thank you so much for

117
00:15:30,040 --> 00:15:35,320
having me. All of you, Sleepy, Tenelle, appreciate you guys very much. Derek, go fuck yourself.

118
00:15:36,040 --> 00:15:42,360
Magoo, you seem all right. You know what, Walker? I'm going to. Walker, if we're not singing...

119
00:15:42,360 --> 00:15:47,720
No, don't take my exit. This is my exit. Can you not just take over? Jesus.

120
00:15:47,720 --> 00:15:54,520
All right. Walker, if we're not singing Blink 182, if we're not singing Blink 182 in a month,

121
00:15:54,520 --> 00:16:02,200
we've done... He left. I'm not singing Blink with him. Fuck, Walker. I'm not singing Blink.

122
00:16:02,200 --> 00:16:09,480
I probably will. Derek, what hotel are you staying at? Let me look at my email here.

123
00:16:09,480 --> 00:16:18,120
I don't know. I bought the flight. My buddy bought the hotel room. I don't know. I have to

124
00:16:18,120 --> 00:16:26,280
look it up here. Search for an S. That's all I know. Let's see. I was spying on you, Derek,

125
00:16:26,280 --> 00:16:31,000
and you didn't even know it. I mean, I'm not going to lie. You probably were, you fucking dick.

126
00:16:31,000 --> 00:16:43,480
I seen you. I seen you. You just have no idea where I seen you. Where did my friend book it at?

127
00:16:47,240 --> 00:16:54,760
Archer, I wanted to know about your Noster story. How did you find Noster and what made you stay?

128
00:16:54,760 --> 00:17:09,240
Okay. Well, the first time I heard about it was maybe a year ago from Ben Ark's podcast.

129
00:17:10,360 --> 00:17:17,320
He mentioned it and I looked it up and I kind of liked what was written by Theodjieff,

130
00:17:17,320 --> 00:17:25,640
the description of it and the reasons of why it might work. But then I tried several clients and

131
00:17:26,680 --> 00:17:34,200
it was completely empty place and there was no one there. So, it felt like a great initiative,

132
00:17:34,200 --> 00:17:44,280
but I had no idea how to like this could get off the ground. And so, I forgot about it. And then

133
00:17:44,280 --> 00:17:54,200
I launched a project that is called Real Search. It was a web search where you'd have to pay with

134
00:17:54,200 --> 00:18:00,920
lightning to access the search results. I launched it in November and I posted it on

135
00:18:00,920 --> 00:18:11,080
Stacker News and et cetera and got like some comments, but no real, not really any users.

136
00:18:11,080 --> 00:18:22,840
And then a couple of weeks later, the Jack Dorsey exploded Noster and I saw that so many people are

137
00:18:22,840 --> 00:18:30,600
joining and there's a lot of buzz and there's no search there. So, I just added search over Noster

138
00:18:30,600 --> 00:18:42,120
in a couple of days. And then it started to work, like people started using and then I just

139
00:18:43,320 --> 00:18:55,560
decided to focus on Noster after that. And I didn't really like have any strong opinion about

140
00:18:55,560 --> 00:19:02,760
like why we should rebuild Twitter or something like that. Like I understand what the problems are

141
00:19:02,760 --> 00:19:13,720
with Twitter, but it's just not like my kind of thing to try to solve that. But what Noster

142
00:19:13,720 --> 00:19:19,640
actually is today, like if you saw me posting stuff recently, I've got much more

143
00:19:19,640 --> 00:19:25,880
excitement about Noster now because it really isn't about Twitter. It's more about like open and

144
00:19:25,880 --> 00:19:33,880
centralized internet and that's way more interesting. So, that's kind of the short story.

145
00:19:35,880 --> 00:19:42,920
Now, I couldn't agree more, man. Yeah, that's a really good enough reason to actually stay.

146
00:19:42,920 --> 00:19:48,680
Because yeah, I could definitely see why. Because I've never been like a super like, social media is

147
00:19:48,680 --> 00:19:58,120
not my whole life. It's a big part of it, but it's not my whole life. And I see the potential for

148
00:19:59,160 --> 00:20:06,120
so many things on this protocol, especially because it's open source and permissionless.

149
00:20:06,120 --> 00:20:14,120
And people here are just so kind and willing to actually work together to make it work.

150
00:20:15,080 --> 00:20:20,360
Something I don't see anywhere else where developers actually are trying to be on the same

151
00:20:20,360 --> 00:20:28,520
page about things. And if they're not, they tend to actually find some sort of common ground along

152
00:20:28,520 --> 00:20:37,160
the way. Backwards compatibility, however, whatever it may look like. But it's not a stagnant

153
00:20:38,200 --> 00:20:45,000
development where it'll take you like months just to figure something small out and work it out.

154
00:20:46,440 --> 00:20:47,480
It's fresh, baby.

155
00:20:50,920 --> 00:20:54,120
Yeah, I find it hard to find a way to do that.

156
00:20:54,120 --> 00:21:03,160
It's fresh, baby. Yeah, I fucking love it, to be honest. And I want to ask you, what do you see

157
00:21:04,520 --> 00:21:11,880
yourself really focusing on for the next couple months on here? Any plans?

158
00:21:14,520 --> 00:21:21,880
That's a difficult question, because like the every week, and maybe even more often,

159
00:21:21,880 --> 00:21:29,480
like the priorities change, it seems, because there are some new ideas that I get or other people get.

160
00:21:30,360 --> 00:21:39,080
I've got like four podcast episodes open that I would like to listen to because like I get new

161
00:21:39,080 --> 00:21:48,520
ideas from them every time from like, those are from David King or G sovereignty or like

162
00:21:48,520 --> 00:22:01,720
this kind of stuff. And so right now I'm thinking a lot about lists and how people could create

163
00:22:02,360 --> 00:22:11,560
created lists of people. And then if clients start supporting them that if clients start supporting

164
00:22:11,560 --> 00:22:20,680
following of lists, then lists becomes like a different home feed or topical feed, if you will.

165
00:22:21,560 --> 00:22:29,160
And then we could like try start solving the problem of discovery on master because

166
00:22:30,920 --> 00:22:35,960
like hashtag is cool, but anyone can post with a hashtag and that becomes like this.

167
00:22:35,960 --> 00:22:45,480
They can hijack the thread, they can spam the this like space. But if you build a list, then

168
00:22:47,160 --> 00:22:53,320
someone who built it kind of curated people. And since the list is like a first

169
00:22:55,800 --> 00:23:01,240
citizen on master event, you could potentially like zap it, comment it, etc.

170
00:23:01,240 --> 00:23:07,160
And so some lists will be more popular than others. And you could share it, you could embed it.

171
00:23:08,840 --> 00:23:15,880
So yeah, that's what I'm gonna work like this next week. But what comes next? I'm not sure yet.

172
00:23:17,080 --> 00:23:25,320
That's awesome. We actually spoke to very, very like a couple hours ago, and he's super excited for

173
00:23:25,320 --> 00:23:32,280
this as well. And he was actually talking about it. It's something that clients should start

174
00:23:32,280 --> 00:23:38,040
implementing more so we could definitely have a more personalized experience when it comes to our

175
00:23:38,040 --> 00:23:45,640
feeds. And it's basically like having your own personalized algorithm. In a sense, it's fucking

176
00:23:45,640 --> 00:23:53,480
amazing. And if you're able to share that list and others, then you can share it with your clients.

177
00:23:53,480 --> 00:23:59,240
Share that list and others could also, you know, like how you said, zap it and find value from,

178
00:23:59,240 --> 00:24:03,880
you know, actually receiving a list that's complete signal. If you have a whole list that's just

179
00:24:03,880 --> 00:24:09,560
developers, that's incredible. And you could also have a list that's just memers and ship posters,

180
00:24:09,560 --> 00:24:15,640
because maybe it's that time of the day where you just want to wind down. So I agree with you 100%

181
00:24:15,640 --> 00:24:20,920
lists are definitely something that we should all be looking forward to and working on.

182
00:24:20,920 --> 00:24:36,360
I think the list NIP51 is what we need to focus on, because it'll allow our list to go from

183
00:24:40,040 --> 00:24:47,480
client to client and be client agnostic. So it doesn't matter which client we're using to edit

184
00:24:47,480 --> 00:24:54,360
it and manipulate our lists, they'll work no matter which client we're using.

185
00:24:56,600 --> 00:25:05,240
Yeah, of course, it's all about NIP51 lists. And I will also mention that some people are like

186
00:25:06,920 --> 00:25:13,160
developers and post stuff about developing sometimes and other times they just

187
00:25:13,160 --> 00:25:21,560
just mean talk. And so you could potentially also include like a person and a hashtag in a list.

188
00:25:22,360 --> 00:25:31,480
And so that like only the hashtag stuff is pulled up from that person. So like with lists,

189
00:25:31,480 --> 00:25:42,200
we could really have like sophisticated curations. And those are all like not algorithms that nobody

190
00:25:42,200 --> 00:25:50,760
understands, but like the real person sort of moderating it. So I think it's a much nicer way

191
00:25:51,320 --> 00:26:01,800
for like the near term to add more discovery. And then if clients start to like suggest

192
00:26:01,800 --> 00:26:08,520
these lists somehow to new people, it would be great because like I've tried to onboard myself

193
00:26:08,520 --> 00:26:14,280
on Amethyst recently like to try from scratch. And it's all like a blank screen after you like

194
00:26:15,080 --> 00:26:23,480
confirm your new pop key. You literally land on an empty home feed. And I have no idea what to do.

195
00:26:23,480 --> 00:26:31,160
Like, who should I follow? Where should I click? Like nothing. And that's a huge problem, I guess.

196
00:26:31,160 --> 00:26:40,120
And most clients are in like sort of similar position. Not maybe that bad, but similar.

197
00:26:41,960 --> 00:26:47,960
And if onboarding is made better, then more people will stay here and find value here.

198
00:26:47,960 --> 00:26:57,560
I honestly couldn't agree more.

199
00:27:01,800 --> 00:27:13,320
Yeah. My bad. I was actually outside and I'm trying to like change my phone real quick.

200
00:27:13,320 --> 00:27:19,240
Give me what's up. You know, sometimes your phone does things you don't want it to do.

201
00:27:20,920 --> 00:27:27,720
And sometimes you got to chase it. Like sometimes you don't want it to run. And it does.

202
00:27:28,920 --> 00:27:37,720
It's like phone, fuck you, come back. Oh, man. Okay. I'm back on the laptop. Apologies for that.

203
00:27:37,720 --> 00:27:45,880
Yeah. Ethan, you're up here in case you had any questions for our friend.

204
00:27:46,920 --> 00:27:51,880
Yeah. First of all, thanks for being here. I mean, he has one of the best searching engine

205
00:27:51,880 --> 00:27:56,920
right now on Noster. I mean, I really want to understand how it really gets the data.

206
00:27:56,920 --> 00:28:02,360
Is it aggregating all the relays? How you are, you know, making sure it's not duplicating the data?

207
00:28:02,360 --> 00:28:09,800
How you are cleaning the data and how accurate is that data? I really wanted to know that.

208
00:28:09,800 --> 00:28:20,760
Well, yeah, I just subscribe. My crawler subscribes to all known relays and it starts pulling

209
00:28:21,720 --> 00:28:29,880
the data, all the data from them. And then there are like 10 to 20 duplicates of every event,

210
00:28:29,880 --> 00:28:40,600
not usually. So I just throw the copies away and only store like the unique stuff in the database.

211
00:28:40,600 --> 00:28:47,880
And that's how it is. And when I see new relays in like contact lists or in tags,

212
00:28:47,880 --> 00:29:03,000
then I just add them to the list and start listening to them too.

213
00:29:06,120 --> 00:29:11,720
By any chance, Archer, you okay if I open up the... Go ahead, Ethan, your reply.

214
00:29:11,720 --> 00:29:21,960
Yeah. Okay. Okay. I just wanted to see if anybody on the audience...

215
00:29:22,840 --> 00:29:24,440
Yeah, I have some more questions.

216
00:29:24,440 --> 00:29:25,080
Okay, go ahead.

217
00:29:25,080 --> 00:29:31,560
That project. Yeah. Yeah. So I was creating a project using your API. I'm planning to create

218
00:29:31,560 --> 00:29:36,440
a project where if anybody's entering their public key, they should get some kind of profile,

219
00:29:36,440 --> 00:29:42,600
some kind of profile of themselves, some kind of chart also, maybe how many zaps they got past week,

220
00:29:42,600 --> 00:29:48,040
how many zaps they got this week. Can you tell us more about what is a business model for that API?

221
00:29:48,040 --> 00:29:52,600
I mean, that is one of the most sophisticated API on Nostr right now. So what is the business

222
00:29:52,600 --> 00:29:57,480
model for that right now? Is there going to be a development here? So what is the plan for that?

223
00:29:57,480 --> 00:30:11,480
Well, I think I've got the same plan that any back end service provider has here, like relay

224
00:30:11,480 --> 00:30:22,680
operators mainly. And the plan I would say is that we wait until there's enough effort put into

225
00:30:22,680 --> 00:30:30,680
making payments part of the protocol where the clients could stream sets to this relays and

226
00:30:31,320 --> 00:30:40,360
API providers that they use. I don't see really any other way for the back end services to scale

227
00:30:40,360 --> 00:30:48,920
and to grow and to sustain themselves. And right now, some operators just, they do like this.

228
00:30:48,920 --> 00:30:58,440
Like some operators just, they do like paid relays. Some are like maybe living on donations.

229
00:30:58,440 --> 00:31:05,960
Some are just doing it as a hobby. And right now I just provide it for free because it just

230
00:31:05,960 --> 00:31:13,880
too much work to try to like organize the collection of tiny amounts of sets from

231
00:31:13,880 --> 00:31:23,000
anyone that use the API. But eventually it will come to Nostr. And I think every

232
00:31:25,880 --> 00:31:31,160
client and every user will have to pay somehow one way or another for their back end services.

233
00:31:32,920 --> 00:31:38,840
So when that comes, there will be some business models sustained. And then the

234
00:31:38,840 --> 00:31:45,880
maybe there is going to be some more advanced features that you would have to pay for somehow.

235
00:31:47,400 --> 00:31:52,280
But I haven't really spent too much time thinking about it at this point. Like

236
00:31:53,720 --> 00:32:01,800
really, aside from search API, no one, almost no one uses these. So it's not

237
00:32:01,800 --> 00:32:08,920
too costly for me to have them. Okay. Okay. I understand. So it is going to more like that

238
00:32:08,920 --> 00:32:13,240
model OpenAI is doing right now. They are providing the API to everyone. Yeah. You can pay for what

239
00:32:13,240 --> 00:32:17,960
you are using and you just have to build the front end and fine tuning that kind of stuff, right?

240
00:32:20,280 --> 00:32:23,400
Yeah. Maybe, maybe something like this. Yeah. Something like that. I think it's

241
00:32:23,400 --> 00:32:31,960
very early and nobody knows how to make money here. Like it's, I think it's in principle by

242
00:32:31,960 --> 00:32:38,200
definition much harder to make money here because like in any other like

243
00:32:40,120 --> 00:32:45,560
IT startup, you have, you should have some kind of a model that you can use to make money.

244
00:32:45,560 --> 00:32:54,520
Like extract value out of like your clients, et cetera. But here it's all decentralized and

245
00:32:55,480 --> 00:33:02,840
everyone can switch. You can get a complete competitor like very easily. And so

246
00:33:04,600 --> 00:33:10,360
I think there are much less possibilities for you to make money here.

247
00:33:10,360 --> 00:33:16,360
I think there are much less possibilities to make money, much less.

248
00:33:19,080 --> 00:33:26,200
At least legacy business models are applicable here. And I don't think anyone has figured

249
00:33:26,200 --> 00:33:33,320
out like how to make money on Nostr. So we will just, we should probably just keep building and

250
00:33:33,320 --> 00:33:42,120
trying stuff and figure that. I mean, I completely agree with you. We have to create some kind of

251
00:33:42,120 --> 00:33:47,880
sustainable business model for Nostr. I think it's not impossible. I mean, we are creating the apps,

252
00:33:47,880 --> 00:33:52,200
we are creating new projects. We can also create some kind of sustainable business model

253
00:33:52,200 --> 00:33:57,640
where people are using that service and they're also paying for that service. As it gets more

254
00:33:57,640 --> 00:34:01,960
sophisticated, I'm thinking maybe paper use model that will be very interesting to see.

255
00:34:01,960 --> 00:34:09,960
So I'm really fascinated with your project. That's one of the best projects on Nostr. I really believe that.

256
00:34:09,960 --> 00:34:15,960
So we are looking forward to it. And can you tell us last question from you? The recent update you

257
00:34:15,960 --> 00:34:23,560
make, I saw your post about the lot of updates you made on Nostr. What were those updates

258
00:34:23,560 --> 00:34:32,200
specifically? Is there any update for API also and any recommendation how we should use that API?

259
00:34:32,200 --> 00:34:40,440
Sorry, can you repeat please the question about which update about the lists? Yeah, the recent update,

260
00:34:40,440 --> 00:34:45,720
I saw your post. I also maybe respond to that. There were a lot of updates on

261
00:34:47,080 --> 00:34:51,000
Nostr.Bank and we were talking about you said there was the same list on

262
00:34:51,000 --> 00:34:59,000
Twitter also. So what was that update exactly? Recent update? The recent update was about the

263
00:34:59,000 --> 00:35:05,640
lists feature. So basically there's a people search on Nostr.Bank and if you

264
00:35:07,800 --> 00:35:14,360
search for some people by keyword hashtag or maybe you're looking at the following of somebody,

265
00:35:14,360 --> 00:35:20,360
then there are buttons like group action buttons where you can click to follow everyone on the list

266
00:35:20,360 --> 00:35:32,360
or unfollow them. And that's probably more convenient way to find, to build your following list.

267
00:35:32,360 --> 00:35:41,720
But then that's what's working today. But the idea here is that lists contact list is just a special

268
00:35:41,720 --> 00:35:51,160
case of NIP-51 lists. And so the list editing feature, batch editing feature will come next

269
00:35:51,160 --> 00:36:00,760
where you can build people lists on the Nostr.Bank faster than in other places because there's search

270
00:36:00,760 --> 00:36:11,240
and various ways to filter through profiles. And so then the further ideas that the Nostr.Bank

271
00:36:11,240 --> 00:36:17,720
has is that those lists could then be, as I said, used like topical feeds by people and people could

272
00:36:17,720 --> 00:36:28,200
subscribe to your list etc. So yeah, like the update itself is not too big but I think the

273
00:36:28,200 --> 00:36:40,920
implications of having an easy way to edit lists of people might do a lot of good for Nostr today.

274
00:36:43,320 --> 00:36:48,840
Yeah, I think it was also a groundwork for what you were describing before. You are creating a list

275
00:36:48,840 --> 00:36:54,280
and other things so clients can just implement that groundwork for that. Thank you. Thank you.

276
00:36:54,280 --> 00:37:00,920
Daniel, do you have any questions? I actually just brought up somebody from the audience.

277
00:37:00,920 --> 00:37:06,840
I believe Normy had his hand raised and he wanted to ask a question. Sage is yours.

278
00:37:11,240 --> 00:37:20,840
Normy, you had your hand up for a while. Hi, can you hear me? Yes. Yes. Yeah. Okay. Thank you so

279
00:37:20,840 --> 00:37:27,400
much for creating Nostr.Bank because whenever I see an end pub, I just tend to copy it there and

280
00:37:27,400 --> 00:37:32,280
find out some force of the people. It's much easier than using my client search in fact. And

281
00:37:33,240 --> 00:37:42,920
finding people to follow basic basis keywords or something. It's been super easy thanks to Nostr.Bank.

282
00:37:42,920 --> 00:37:51,640
I just had a question with respect to how you exactly define the high quality pub keys, right?

283
00:37:51,640 --> 00:37:58,840
Because you do post graphs, bases, that. So a bit more insight into how you came to define that.

284
00:38:01,800 --> 00:38:07,560
Yeah, so at this page at the top of it, there is a link that describes,

285
00:38:07,560 --> 00:38:32,520
there is a sentence that says high quality pub keys are pub keys with non-zero trust rank. And there is a link describing what trust rank is. And it's essentially, if you know what page rank is, Google's page rank that they use to rank web pages. And the algorithm of it is open.

286
00:38:32,520 --> 00:38:45,000
And so I do basically the same thing for Nostr events where if you follow someone, that's a link. If you

287
00:38:46,120 --> 00:38:55,160
like someone's post, it's a link to that post, et cetera. And I calculate the page rank based on this graph.

288
00:38:55,160 --> 00:39:13,720
And then some accounts have like zero trust rank, which means that nobody really interacted with their content. And some accounts get like non-zero trust rank and some accounts get huge trust rank.

289
00:39:13,720 --> 00:39:25,640
And so here on the stats page specifically, the high quality pub keys are ones with non-zero trust rank.

290
00:39:27,080 --> 00:39:39,960
And I also use the same metric to like find to rank people in the trending section, posts in the trending section, et cetera.

291
00:39:39,960 --> 00:39:50,440
It's pretty hard to gain this number because like if you're a bot, if you're building a bot or bot farm,

292
00:39:51,960 --> 00:40:02,760
you could easily gain the number of followers and number of likes by just making bots follow each other or making bots like each other's posts.

293
00:40:02,760 --> 00:40:11,400
But all of those are going to get like zero trust rank because nobody outside of their like this small farm is interacting with their stuff.

294
00:40:13,800 --> 00:40:30,200
And yeah, so it's kind of useful to filter out useless stuff, but it's not perfect. And it needs to be like improved.

295
00:40:30,200 --> 00:40:51,400
I think from what I see today, because I'm not sure how well it, like I'm not sure if I have a diverse selection of people, like for instance on the homepage.

296
00:40:51,400 --> 00:41:02,200
I think it is kind of diverse, but you can't really know without like digging deeper and reading manually through lots of new profiles.

297
00:41:03,560 --> 00:41:07,000
So yeah, that's how it works.

298
00:41:09,480 --> 00:41:15,400
And just another question, especially because the graphs that are there on Noster.Ban, right?

299
00:41:15,400 --> 00:41:23,960
You see people posting it on Twitter and talking about Noster not getting enough new users or not growing bases those graphs, right?

300
00:41:23,960 --> 00:41:32,360
How do you exactly feel about that? Because I mean, people just see it and interpret it as at the face value, like not filtering out the high quality.

301
00:41:32,360 --> 00:41:47,560
They just look at the overall trends and don't filter it out, even though you have provided the filters. How do you exactly feel about your graph being used to create a completely different narrative elsewhere?

302
00:41:49,240 --> 00:41:56,600
Look, I think the narratives, like especially on Twitter, I actually follow them like regularly.

303
00:41:56,600 --> 00:42:03,960
And first of all, those are like very niche, like some random person posted and it doesn't matter.

304
00:42:06,680 --> 00:42:18,040
But overall, I believe that this Noster ecosystem is built on transparency and the data is all here.

305
00:42:18,040 --> 00:42:26,280
Like if you want to see raw data like daily pop keys, writing events, like I mean all of them, the graph is here.

306
00:42:26,280 --> 00:42:35,560
You can look at it. And if you don't like my high quality thing metric, you can turn it off and only look at the raw data.

307
00:42:36,440 --> 00:42:47,400
And I build this stuff for myself, like at first, the first user. I want to know if Noster is growing or not.

308
00:42:47,400 --> 00:42:53,400
I want to have like a way, a good way to measure that. That's the best way I could come up with.

309
00:42:53,400 --> 00:42:59,240
If it works for me, if it doesn't work for someone else, I'm fine with that.

310
00:42:59,240 --> 00:43:04,040
Like if someone suggests a better version of it, I'm cool with that.

311
00:43:04,040 --> 00:43:18,040
And I think the problem would be if like the data is wrong, like if there really is more than like 10,000 daily active users, like way more.

312
00:43:18,040 --> 00:43:23,880
And if it was growing, but my numbers were shown that it didn't, that's a problem.

313
00:43:23,880 --> 00:43:33,320
But from what I see from other metrics that are not really like correlated with my trust rank,

314
00:43:34,840 --> 00:43:42,920
I would say that other metrics show the same picture. Like the number of zaps is pretty constant.

315
00:43:42,920 --> 00:43:51,400
The number of other things that show some kind of like high quality interaction with the network.

316
00:43:51,400 --> 00:44:01,320
Those are also like not growing. And I think it works pretty well.

317
00:44:01,320 --> 00:44:07,000
And if someone wants to create a narrative and like misinterpret the graph,

318
00:44:07,000 --> 00:44:14,520
if someone doesn't want to spend enough time to understand what's on the graph and they post shit about it, it's their problem.

319
00:44:14,520 --> 00:44:37,960
Like they will do it anyway. They had the agenda probably. I don't think like I can do anything about it.

320
00:44:37,960 --> 00:44:46,360
Incredible. Any last words, Normie, for Archer?

321
00:44:46,360 --> 00:44:55,880
No, I mean, that was, I mean, what I completely agree with what he was saying about the narratives being created.

322
00:44:55,880 --> 00:45:02,040
I don't think at the end of the day, he can control who is saying what basis is his graphs.

323
00:45:02,040 --> 00:45:09,960
And I mean, the point that he made that he creates them for himself as the audience first.

324
00:45:09,960 --> 00:45:16,280
That is very interesting. I never thought about it that way. So that's nice. Thank you so much, Archer.

325
00:45:17,480 --> 00:45:18,760
You're welcome.

326
00:45:18,760 --> 00:45:24,440
I agree. Ethan? You good?

327
00:45:24,440 --> 00:45:24,940
Yeah.

328
00:45:26,520 --> 00:45:29,160
Any last words before we close up?

329
00:45:29,160 --> 00:45:35,160
Yeah. Thank you so much for having me. Thank you, Arthur. Thank you for being here. It was a very, very good conversation.

330
00:45:35,160 --> 00:45:41,720
I learned a lot. Thank you. Thank you, Sleepy. Thank you, Turner. Thank you. Thanks for what we are doing right now.

331
00:45:41,720 --> 00:45:43,720
You're doing a great job. Thank you.

332
00:45:43,720 --> 00:45:52,120
Thank you, Ethan. Thank you for being here, man. I appreciate you for taking such a long, so much of your time to be here with us.

333
00:45:52,120 --> 00:45:55,000
It was a pleasure, my friend. It was a pleasure.

334
00:45:55,000 --> 00:45:57,000
Appreciate you so much, man.

335
00:45:57,000 --> 00:45:57,560
Thank you.

336
00:45:57,560 --> 00:46:00,520
Thank you. Absolutely amazing to have you with us.

337
00:46:01,240 --> 00:46:12,680
Archer, we've had so much fun having you on here, man. It's been a great time, man. I really appreciate you being here with us and spending time with us, hanging out, answering our questions.

338
00:46:13,640 --> 00:46:21,960
I can't tell you enough how much I love Nasheedah Band. You've got literally like, I think it definitely is my favorite micro app.

339
00:46:21,960 --> 00:46:41,640
It's the best search that there is. And yeah, I feel like more people have to use it. It's just so useful. I use it multiple times throughout my day. It's crazy. I use it more than any other micro app. It's super useful. Freaking love it.

340
00:46:41,640 --> 00:46:43,640
Thank you very much.

341
00:46:43,640 --> 00:46:57,000
Yeah. Thank you very much. Appreciate you, man. I really would love to have you on a second time so we can speak more deep into other features that you have on the app currently that I'm super curious about.

342
00:46:57,000 --> 00:47:03,080
And I didn't have time to ask. Tanel, do you have any last words, man?

343
00:47:03,080 --> 00:47:28,280
I'm just so appreciative to have you with us, man. Because Nasheedah Band is such a huge part of my daily activity. And Nasheedah interacting with all the notes, seeing all the new users that are joining and gathering more and more followers and getting all the stats and everything. It's absolutely amazing the job that you do. And the community here really appreciates you. So thank you. Thank you so much.

344
00:47:28,280 --> 00:47:41,400
Yeah. Thank you everyone for inviting me and asking nice questions. And I hope to join you again someday to discuss more interesting stuff.

345
00:47:41,400 --> 00:47:51,160
I appreciate you so much, man. And we'll catch you very soon, man. Talk to you very soon.

346
00:47:51,160 --> 00:47:53,160
Thanks. Bye everyone.

347
00:47:53,160 --> 00:47:55,160
Bye.

348
00:47:55,160 --> 00:47:59,160
Closing out the recording now.