1
00:00:00,000 --> 00:00:06,630
Oh, podcasting 2.0 for November
4 2022, episode 109 for geeks of

2
00:00:06,630 --> 00:00:11,670
knitting Hello everybody brand
new moms. Welcome to the

3
00:00:11,760 --> 00:00:15,900
official board meeting of
podcasting. 2.0 It's completely

4
00:00:15,900 --> 00:00:19,530
backwards compatible with your
1.0 thinking in apps don't worry

5
00:00:19,530 --> 00:00:22,380
about it. We're dragging along
into the future. Everything

6
00:00:22,380 --> 00:00:26,940
happening in podcasts index.org
The namespace for the podcast

7
00:00:26,940 --> 00:00:30,120
things and of course all that's
happening at podcast index dot

8
00:00:30,120 --> 00:00:32,430
social. I'm Adam curry here in
the heart of the Texas Hill

9
00:00:32,430 --> 00:00:36,450
Country and in Alabama, Mr.
Captain Frodo himself say hello

10
00:00:36,450 --> 00:00:39,270
to my friend on the other end
ladies and gentlemen, Mr. Dave

11
00:00:39,270 --> 00:00:40,320
Jones.

12
00:00:41,670 --> 00:00:45,420
I feel like Lieutenant proto
like what is his lieutenant

13
00:00:45,570 --> 00:00:48,210
bigger? Like is that higher than
a captain or less than a

14
00:00:48,210 --> 00:00:48,570
captain?

15
00:00:50,730 --> 00:00:52,770
I think you can private

16
00:00:52,770 --> 00:00:53,970
I feel like private Brodo

17
00:00:55,560 --> 00:00:57,690
Yeah, like radar. Basically he
was approached

18
00:00:59,010 --> 00:01:01,800
whoever that guy is on the Star
Trek awaiting that you know is

19
00:01:01,800 --> 00:01:02,340
gonna die.

20
00:01:04,530 --> 00:01:08,700
So you explain Captain proto to
us and I it's i i have a feeling

21
00:01:08,700 --> 00:01:12,120
you were kind of kind of digging
this. This thing this Captain

22
00:01:12,120 --> 00:01:12,930
proto deal.

23
00:01:14,220 --> 00:01:18,360
That was diggin until I actually
had to start coding and pulling

24
00:01:18,360 --> 00:01:22,350
my hair out. It's hard to suck.
It's not that it's not so much

25
00:01:22,350 --> 00:01:28,080
that is this the I've been
fighting my environment all

26
00:01:28,080 --> 00:01:32,430
week. It's this is hard. You
meet your your

27
00:01:32,430 --> 00:01:36,030
work environment, your
development environment or your

28
00:01:36,060 --> 00:01:36,660
wife.

29
00:01:37,169 --> 00:01:42,809
Now number two, number two, yes.
Oh, no, the wife environment is

30
00:01:42,809 --> 00:01:48,659
always fantastic. Number two,
hello. We all know this. Divide

31
00:01:48,659 --> 00:01:53,999
the development environment is
is wonky. And I just it's just

32
00:01:53,999 --> 00:01:59,909
driving me a little bit a little
bonkers because I'm windows with

33
00:02:01,979 --> 00:02:10,529
WsL Windows subsystem for Linux
running Ubuntu. and a bit WsL is

34
00:02:10,529 --> 00:02:15,509
really flaky when it comes to
networking, especially with a

35
00:02:15,509 --> 00:02:16,919
local host. It just,

36
00:02:17,460 --> 00:02:20,520
there's no there's some stuff
that just does not work, right.

37
00:02:20,520 --> 00:02:22,650
No matter what you do. I've run
into this myself.

38
00:02:23,070 --> 00:02:26,400
It doesn't it doesn't I mean,
it's like one to 7.0 dot 0.1

39
00:02:26,400 --> 00:02:30,840
should always just be one to one
to 700 to one, but somehow in

40
00:02:30,840 --> 00:02:34,530
Windows, it just magically
doesn't behave like localhost

41
00:02:34,530 --> 00:02:38,580
sometimes and you draw the I
need this Docker container

42
00:02:38,580 --> 00:02:42,960
running. That's got the new
socket, no technology in the new

43
00:02:42,960 --> 00:02:47,340
soccer socket code in it. And
it's running and is listening on

44
00:02:47,340 --> 00:02:54,210
localhost port 9999. And then
I'm connecting to it from the

45
00:02:54,210 --> 00:02:57,660
pod pain web front end, and it
just will not work and it's

46
00:02:57,660 --> 00:03:01,620
driving me bonkers. Yeah, but I
can't switch over to the only

47
00:03:01,620 --> 00:03:06,720
other machine dev machine I
have. Well, I've got the

48
00:03:06,720 --> 00:03:09,660
podcasting rig, which is a boon
to and then I've got an but I

49
00:03:09,660 --> 00:03:12,150
don't like working on it.
Because it's not in a good

50
00:03:12,150 --> 00:03:12,780
place.

51
00:03:12,990 --> 00:03:16,470
We know. We know all about your

52
00:03:17,520 --> 00:03:22,410
Yes. Three boots into the show.
You realize this is not rocking

53
00:03:22,410 --> 00:03:25,380
now. Yeah, yeah. The only other
machine I've got that I can

54
00:03:25,380 --> 00:03:28,110
really develop on pretty well is
that we need

55
00:03:28,110 --> 00:03:31,650
to get you to does this podcast
index need to get you a better

56
00:03:31,650 --> 00:03:33,570
machine? I mean, what do we need
to do here?

57
00:03:33,960 --> 00:03:37,530
Now I've got great machines they
just happen to be not neither

58
00:03:37,530 --> 00:03:42,120
one is. What I need is a Linux
machine. I'm about to honest.

59
00:03:42,120 --> 00:03:44,160
Okay, I'm about to ditch the
Mac.

60
00:03:44,790 --> 00:03:48,180
Oh, there he is. Come back to
the dark side. Dave, you can do

61
00:03:48,180 --> 00:03:49,560
it. We can have you

62
00:03:49,590 --> 00:03:56,850
here. If you're writing
websites, on the Mac, you're

63
00:03:56,850 --> 00:03:59,130
good to go. Right? Like if
you're writing like a you know,

64
00:03:59,130 --> 00:04:03,780
Ruby, or you know, whatever, you
probably fine. If you're doing

65
00:04:03,780 --> 00:04:07,800
anything that is at all with
compiled code, or anything a

66
00:04:07,800 --> 00:04:11,160
little bit lower level. You just
You just bang your head against

67
00:04:11,160 --> 00:04:13,920
the wall with all the in one
architecture problems. Oh,

68
00:04:13,920 --> 00:04:17,280
David podcasts index.org For all
your complaints about how he's

69
00:04:17,280 --> 00:04:18,060
wrong.

70
00:04:18,750 --> 00:04:20,040
I've got a folder for that.

71
00:04:23,040 --> 00:04:23,760
Exactly.

72
00:04:25,920 --> 00:04:29,910
Is it true? Is it true? Is the
rumor true that we we didn't

73
00:04:29,910 --> 00:04:35,940
even get a chapter on the latest
pod land? I mean, a 45 minute

74
00:04:35,940 --> 00:04:38,160
interview we didn't get we
didn't earn a chapter

75
00:04:38,250 --> 00:04:42,270
and we just take a look. So we
got a note from from Sam Sethi,

76
00:04:42,270 --> 00:04:45,510
and he's like, Hey, we're doing
the 100th and last episode of

77
00:04:45,510 --> 00:04:48,720
pod land. Now of course, we knew
this was a pathetic marketing

78
00:04:48,720 --> 00:04:55,140
ploy, but All right, we will go
along with it. And so we had a

79
00:04:55,140 --> 00:04:57,390
really nice interview, but I
thought it was gonna be a part

80
00:04:57,390 --> 00:05:01,650
of the show. And basically, they
did The show and then by the

81
00:05:01,650 --> 00:05:05,520
way, we chatted with Adam and
Dave. All right, then

82
00:05:05,580 --> 00:05:09,540
the last the last chapter is 48
minutes long and it says Sam and

83
00:05:09,540 --> 00:05:10,440
James's weak

84
00:05:15,450 --> 00:05:19,200
pod lead here. Let me check it
out for a second. I like it

85
00:05:19,200 --> 00:05:23,220
chapters. Here we go look at the
chapter. Oh, man. Yes, four

86
00:05:23,220 --> 00:05:27,210
chapters. Yeah. Oh, dude. Yeah.
40 minutes and 11 seconds.

87
00:05:29,070 --> 00:05:31,470
48 minutes of salmon. James's
week

88
00:05:31,620 --> 00:05:35,550
was hilarious. Anyway, I thought
we were dynamite on that, to be

89
00:05:35,550 --> 00:05:40,200
honest about it. Yeah, we're
always done. Now. I mean, yeah,

90
00:05:40,230 --> 00:05:43,200
it was nice. Because, you know,
we switch roles a little bit.

91
00:05:43,560 --> 00:05:46,620
There was I don't know, it was
just it was good. It felt you

92
00:05:46,620 --> 00:05:49,680
gave the the Genesis story. I
love hearing your version.

93
00:05:50,460 --> 00:05:54,300
Yeah, it's yeah, you've got a
standing rule that we don't ever

94
00:05:54,300 --> 00:05:55,980
appear on shows together.

95
00:05:57,480 --> 00:06:01,230
Anyone do it? Well, those guys
are a little different. Yeah.

96
00:06:01,230 --> 00:06:03,570
Oh, did you hear what James did?
He's smart, though. I'll give

97
00:06:03,570 --> 00:06:10,320
him that. So on pod news this
morning. He promotes the last

98
00:06:10,320 --> 00:06:12,690
pod land episode, which of
course is what you want to do.

99
00:06:12,720 --> 00:06:18,960
Obviously, the TC picks is me
going you know voices like

100
00:06:18,960 --> 00:06:23,190
yours. And, and and James
Kirkland. These are important in

101
00:06:23,190 --> 00:06:29,760
our industry. He's such as such
a war. I was laughing my ass

102
00:06:29,760 --> 00:06:33,480
off. Like I have all the things
we said in there of all the

103
00:06:33,480 --> 00:06:35,310
things in that 40 minutes.

104
00:06:35,670 --> 00:06:44,910
That was the most important to
him. I enjoyed it. Like, can I

105
00:06:44,910 --> 00:06:51,660
just just briefly divert into
topic du jour of Twitter?

106
00:06:52,620 --> 00:06:57,000
Well, under one under one
condition if we one time for the

107
00:06:57,000 --> 00:06:57,600
one time.

108
00:07:00,360 --> 00:07:07,020
100 fire. Okay. Can I just just
I just want to make as just a

109
00:07:07,740 --> 00:07:12,120
general comment about the entire
thing is I think it goes I think

110
00:07:12,120 --> 00:07:16,860
this all goes back. This is
Elon. This is not even really

111
00:07:16,860 --> 00:07:25,920
about about the specifics. But
Elon is the new version of what

112
00:07:26,610 --> 00:07:31,230
you called it. II called this a
long time ago with Trump. Oh, he

113
00:07:31,230 --> 00:07:34,860
lied. It would the Trump
derangement syndrome sort of

114
00:07:34,920 --> 00:07:38,580
sort of thing. One thing that no
but that people fail, always

115
00:07:38,580 --> 00:07:45,090
kept, kept failing to understand
about Trump is that when you

116
00:07:45,390 --> 00:07:49,230
interact with him, you are
unwittingly becoming a character

117
00:07:49,230 --> 00:07:53,520
in his television show. And
that's that feels like exactly

118
00:07:53,520 --> 00:07:56,430
the same thing that's happening
now. People that are interacting

119
00:07:56,430 --> 00:08:01,200
with Elon do not realize that
they are feeding the troll they

120
00:08:01,290 --> 00:08:06,060
they are becoming a character in
his TV show. They are they

121
00:08:06,060 --> 00:08:11,610
become the cast of a vast show
that he is creating. Like, if

122
00:08:11,610 --> 00:08:14,130
you don't like it, just stop it
just

123
00:08:14,700 --> 00:08:17,460
wow, that's very interesting.
It's a very interesting

124
00:08:17,460 --> 00:08:20,880
analysis. Yeah, that's true.
That's true. And

125
00:08:21,360 --> 00:08:23,760
it's what trolls do expert ones.
Yes. Yeah.

126
00:08:24,360 --> 00:08:27,570
Well, I, all I'm gonna say is I
believe that so far, my

127
00:08:27,570 --> 00:08:31,890
predictions have come true.
Forced authentication is on its

128
00:08:31,890 --> 00:08:36,840
way. And not that you probably
can't just be an unverified

129
00:08:36,840 --> 00:08:39,870
user, I'm sure there'll be fine,
you'll just be equal to a bot.

130
00:08:40,470 --> 00:08:44,010
So when you when a bot will I
saw a panel of a ver, the

131
00:08:44,010 --> 00:08:46,620
verified user, I don't have one
of the verified user panel

132
00:08:46,620 --> 00:08:51,960
changed. And so you can select
by all tweets do you want all

133
00:08:51,960 --> 00:08:55,950
that mention you so that's the
same. And the third one, which

134
00:08:55,950 --> 00:08:59,700
is verified only. So you can
just live in the verified world

135
00:08:59,730 --> 00:09:02,850
you don't see any of the other
stuff. So it's an auto feature.

136
00:09:03,060 --> 00:09:05,370
And that makes a lot of sense.
And so you have the elitist

137
00:09:05,370 --> 00:09:08,940
there and you have different
tiers and classes system. And

138
00:09:08,940 --> 00:09:11,490
now we can sit at the bottom
with the bots which I think is

139
00:09:11,520 --> 00:09:14,430
where I want to be plebs bots
all the same thing.

140
00:09:15,060 --> 00:09:17,130
Except live in the in the
dumpster and the Twitter

141
00:09:17,130 --> 00:09:17,790
dumpster.

142
00:09:17,880 --> 00:09:20,190
Except he took it one step
further. And I didn't expect

143
00:09:20,190 --> 00:09:23,940
that as he wants to KYC
everybody. Oh, shoot, I know

144
00:09:23,940 --> 00:09:26,940
where the payment like all the
crap. He's she's moving along at

145
00:09:26,940 --> 00:09:27,810
a clip there.

146
00:09:29,790 --> 00:09:33,480
The Yeah. The other thing about
did you see the thing about

147
00:09:33,480 --> 00:09:38,370
infrastructure? So he said he's
directed, Elon Musk has directed

148
00:09:38,370 --> 00:09:42,180
Twitter's Twitter links teams to
find up to 1 billion in annual

149
00:09:42,180 --> 00:09:45,420
infrastructure cost savings.
According to two sources

150
00:09:45,420 --> 00:09:49,680
familiar with the matter and an
internal slack OC, the company

151
00:09:49,680 --> 00:09:52,350
is aiming to find between one
and a half million and 3 million

152
00:09:52,350 --> 00:09:55,320
a day and savings from servers
and cloud services. So the

153
00:09:55,320 --> 00:09:59,430
slight message this this article
from Reuters is, is critical it

154
00:09:59,430 --> 00:10:03,720
takes the Roche that that by
cutting infrastructure costs to

155
00:10:03,720 --> 00:10:06,900
that degree that they're going
to is going to become crashy.

156
00:10:07,440 --> 00:10:09,510
And that they're not going to be
able to work with to handle the

157
00:10:09,570 --> 00:10:16,050
traffic. I disagree with this. I
don't think obviously this, you

158
00:10:16,050 --> 00:10:19,620
know, I know nothing about their
infrastructure. But the reason I

159
00:10:19,620 --> 00:10:21,450
can just I'm just not
disagreeing with this at have

160
00:10:21,450 --> 00:10:23,910
extensive knowledge of
infrastructure. I'm disagreeing

161
00:10:23,910 --> 00:10:28,860
with this out of knowledge of
the way that spending gets

162
00:10:28,860 --> 00:10:36,660
corrupted in a environment like
VC funded stuff, or, you know,

163
00:10:36,660 --> 00:10:39,570
which they come from that
lineage, because it's just like

164
00:10:39,570 --> 00:10:43,110
the military, military
industrial complex, the military

165
00:10:43,110 --> 00:10:45,780
industrial complex cannot, it
has ceased to be able to

166
00:10:45,780 --> 00:10:49,800
function in a market where the
prices are true or real and

167
00:10:49,800 --> 00:10:53,760
true. They only know how to
function. Now, within a

168
00:10:53,760 --> 00:10:57,240
government world where the
prices are inflated beyond

169
00:10:57,240 --> 00:11:00,180
belief with government spending.
The same thing happens in

170
00:11:00,180 --> 00:11:05,640
Silicon Valley, like they you
over time, you forget that you

171
00:11:05,640 --> 00:11:09,450
don't have to have, you know,
billions of dollars of

172
00:11:09,450 --> 00:11:13,140
infrastructure, you could
probably get by with a lot less

173
00:11:13,140 --> 00:11:17,520
if you did it smartly. And I
think that's probably what he's

174
00:11:17,730 --> 00:11:20,580
looking at. He's probably
looking around and saying, Oh,

175
00:11:20,580 --> 00:11:24,270
my God, we've got so much
infrastructure that we probably

176
00:11:24,270 --> 00:11:27,030
don't need, we could probably
cut a you know, that and

177
00:11:27,030 --> 00:11:29,310
typically you say, Oh, we knew
we need to cut a million and a

178
00:11:29,310 --> 00:11:32,340
half a day. You cut me say we
need to get three meals a day.

179
00:11:32,760 --> 00:11:35,760
And then they are balls, we can
only find a million. Okay,

180
00:11:35,760 --> 00:11:38,010
that's fine. You shoot high,

181
00:11:38,430 --> 00:11:43,080
you can get maybe I mean, I'm
I'm personally I'm more

182
00:11:43,080 --> 00:11:49,500
interested in the meta of it
all. And you know, I people talk

183
00:11:49,500 --> 00:11:54,960
about staying or leaving Twitter
as if it's like, some place. And

184
00:11:54,960 --> 00:11:59,310
also just the way they view that
in their mind's eye. And the

185
00:11:59,310 --> 00:12:04,830
total lack of unders I mean, the
way the if you hear mainstream,

186
00:12:04,950 --> 00:12:08,340
ie Kara Swisher, if you hear
mainstream people talking about

187
00:12:08,340 --> 00:12:15,300
it, it's as if they believe that
all of the only existence for

188
00:12:15,630 --> 00:12:21,060
human interaction and, and
entertainment and information

189
00:12:21,060 --> 00:12:24,540
should be in this regulated
world with regulated companies

190
00:12:24,540 --> 00:12:27,990
who are, quote, playing by the
rules, who understand how it's

191
00:12:27,990 --> 00:12:30,420
supposed to work. These are the
type of cut type of things she

192
00:12:30,420 --> 00:12:35,460
says, and I'm still just kind of
baffled, half percentage wise,

193
00:12:35,460 --> 00:12:39,810
how few people know that, you
know, when you're using your web

194
00:12:39,810 --> 00:12:44,250
browser, you're you're not in
Chrome. You're not inside

195
00:12:44,250 --> 00:12:47,400
Google. I mean, these are
metaphors that we understand.

196
00:12:47,400 --> 00:12:52,080
And we, we know, the freedom of
the web and the network itself.

197
00:12:52,440 --> 00:12:57,450
But it's been so not maybe not
even on purpose, but it just

198
00:12:57,450 --> 00:12:59,940
kind of well, yeah, the apps, I
think apps have made it into

199
00:12:59,940 --> 00:13:03,360
this place where by this this
web thing was, you know, you do

200
00:13:03,360 --> 00:13:08,190
that for certain things porn and
and the rest is all apps. And I

201
00:13:08,190 --> 00:13:12,300
think that that mentality,
that's what would also with the,

202
00:13:13,230 --> 00:13:16,470
with podcasting, and Apple, you
know, as they had to get on that

203
00:13:16,470 --> 00:13:20,400
app, you had to go through this
process, which of course, is

204
00:13:20,400 --> 00:13:23,430
kind of bull crap. It's the
antithesis of podcasting.

205
00:13:24,660 --> 00:13:29,340
Yeah. Yeah, I can see that.
That's, well, you know, the one

206
00:13:29,340 --> 00:13:32,040
good thing that's happened over
the last week is just lots of

207
00:13:32,040 --> 00:13:35,400
people getting getting over to
Mastodon, I don't know how many

208
00:13:35,400 --> 00:13:38,100
will stay, but a lot of people
entering the Fed averse and

209
00:13:38,100 --> 00:13:40,830
getting getting out of the
algorithms altogether, going

210
00:13:40,830 --> 00:13:43,770
back to just chronological
timelines. That's been good to

211
00:13:43,770 --> 00:13:44,130
see.

212
00:13:44,190 --> 00:13:46,320
I don't know how many people I
don't know how many people

213
00:13:46,320 --> 00:13:49,980
actually move. It's only the
survivors. You know, at the end

214
00:13:49,980 --> 00:13:52,620
of the day, when the rapture
comes, a lot of you will not be

215
00:13:52,620 --> 00:13:57,030
voted to stay on the island.
Trust me on this one.

216
00:13:58,410 --> 00:14:01,110
I deleted my Twitter account a
couple of years ago and my

217
00:14:01,170 --> 00:14:06,390
personal one, and I'll never
I'll never go back to that. I'll

218
00:14:06,390 --> 00:14:07,830
never get back to that bonanza.

219
00:14:07,949 --> 00:14:11,549
Yeah, I deleted my Facebook
account years and years ago

220
00:14:11,549 --> 00:14:16,529
along with Reddit kind of in the
same in the same week. And I

221
00:14:16,529 --> 00:14:20,819
don't miss any of that. No at
all my life is probably I mean

222
00:14:20,819 --> 00:14:23,339
maybe not a direct causation but
it has improved.

223
00:14:24,480 --> 00:14:30,540
Yeah, and then I turned off
notifications recently on tons

224
00:14:30,540 --> 00:14:36,090
of answers Yeah, you got to do
that. Oh, I got the Met Macedon.

225
00:14:36,360 --> 00:14:39,600
Even even onMessage like text
message I've turned off like

226
00:14:39,930 --> 00:14:44,220
everything and only only have to
go to it to check it. Yeah,

227
00:14:44,310 --> 00:14:47,700
that's been a nice, you know,
mental freedom there.

228
00:14:47,820 --> 00:14:51,030
It won't be long you'll be on
graphing OS soon enough for you.

229
00:14:51,600 --> 00:14:55,110
The walls are closing in on on
iOS. It's very obvious what

230
00:14:55,110 --> 00:15:01,140
they're doing. I love installing
for the suit. As sandboxed App

231
00:15:01,140 --> 00:15:05,790
Store on graphene OS, you can
really set granular level

232
00:15:05,820 --> 00:15:07,980
permissions and all kinds of
stuff.

233
00:15:09,929 --> 00:15:13,049
It's been so I've not been in
the Android world for so long, I

234
00:15:13,049 --> 00:15:16,829
had no idea what's going on over
there. The only thing I know

235
00:15:16,829 --> 00:15:20,519
about is from you didn't have to
rely on you to tell me what's

236
00:15:20,519 --> 00:15:23,129
going on, because nobody I know,
is on Android anymore.

237
00:15:25,230 --> 00:15:27,900
Well, at least you have a real
friend in the real world, Dave,

238
00:15:27,900 --> 00:15:28,200
John.

239
00:15:30,810 --> 00:15:33,030
What do you got? It's not even
really Android. I mean, you've

240
00:15:33,060 --> 00:15:36,270
you've got to know I mean, like,
once you get to graphene, you've

241
00:15:36,300 --> 00:15:37,890
you've really left the Android

242
00:15:38,430 --> 00:15:42,300
universe. You go to no agenda
phone.com The instructions are

243
00:15:42,300 --> 00:15:46,380
there. But and even the link to
the official way to do it was on

244
00:15:46,380 --> 00:15:52,470
graphene OS or whatever their
website is GitHub, and you buy a

245
00:15:52,470 --> 00:15:55,740
new Android blight and only
thing it only works on pixels.

246
00:15:55,740 --> 00:16:03,510
So you buy the pixel 43456 Or
seven is all supported. And then

247
00:16:04,110 --> 00:16:08,010
you do a couple of loops, you
plug it in and go to their

248
00:16:08,010 --> 00:16:11,580
website, and the website starts
to log in and manage your phone

249
00:16:11,580 --> 00:16:14,460
and it does all the all the
changeovers you kind of sit

250
00:16:14,460 --> 00:16:17,730
there watch and it comes up and
it's alive. You got graphy know

251
00:16:17,730 --> 00:16:20,730
us and there's even a way to go
back and restore to Android if

252
00:16:20,730 --> 00:16:21,420
you want it to.

253
00:16:23,550 --> 00:16:27,420
Nice and I am going to try it
out. I'm gonna give it a shot.

254
00:16:28,260 --> 00:16:32,010
And we pixel what pixel six
pixel? Which, which Why

255
00:16:33,210 --> 00:16:38,850
is the pixel six smaller than
the pixel six? A? I think so

256
00:16:38,850 --> 00:16:41,460
because I just got the six A's.
I just got the six, eight. And

257
00:16:41,460 --> 00:16:44,310
then I'm like, this thing is a
little too big.

258
00:16:45,270 --> 00:16:49,140
I don't like a big like I've
gone to the iPhone mini now I'm

259
00:16:49,140 --> 00:16:52,230
really done with big phones,
that I need the smallest one

260
00:16:52,230 --> 00:16:57,240
that got that wonder if that's
the pixel, which whichever small

261
00:16:57,240 --> 00:17:00,000
like if it's bigger than the
Mini, I want to start with that

262
00:17:00,000 --> 00:17:00,690
to begin with.

263
00:17:02,100 --> 00:17:07,110
Well, welcome to Tech, everybody
where we talk about phones, what

264
00:17:07,110 --> 00:17:09,510
the heck are we doing, I wanted
to mention one of the things

265
00:17:09,510 --> 00:17:11,370
before we bring our guests in
because we got a lot of

266
00:17:11,760 --> 00:17:19,020
namespace tags to discuss. And
as a friend of the show, I've

267
00:17:19,020 --> 00:17:23,100
been working with ibex, Ibex pay
for a back end,

268
00:17:23,640 --> 00:17:24,660
do you have an update?

269
00:17:24,839 --> 00:17:26,609
I do have an update? Well, first
of all, I learned a little bit

270
00:17:26,609 --> 00:17:33,479
more about the company, I think
it's a I don't know if it's El

271
00:17:33,479 --> 00:17:39,869
Salvadorian slash Mexicans slash
us Miami Corporation, I believe,

272
00:17:40,499 --> 00:17:44,909
and the family that owns the
company, they are one of the

273
00:17:44,909 --> 00:17:50,369
largest Western Union franchise
banks, I guess, in all in

274
00:17:50,369 --> 00:17:54,209
Central and South America with
8000. Western Union. So I didn't

275
00:17:54,209 --> 00:17:56,399
know it, but I guess it's a
franchise, you know, it's like,

276
00:17:56,579 --> 00:18:00,239
you set up shop, you're you I
guess you have some kind of sort

277
00:18:00,239 --> 00:18:04,079
of exchange license or whatever
that is, thank you know, you

278
00:18:04,079 --> 00:18:08,009
couldn't find Thank you
exchange, you know, banking

279
00:18:08,009 --> 00:18:11,189
license, and then you pay a
franchise fee. And then you're

280
00:18:11,189 --> 00:18:16,559
on the Western Union network.
And so the one of the one of the

281
00:18:16,559 --> 00:18:19,619
newer people in the family went
into the family. So look, we got

282
00:18:19,619 --> 00:18:22,709
to set this up. But we got to do
that we got to get lightning

283
00:18:22,709 --> 00:18:26,039
going. As you know, we really
have to move on this because we

284
00:18:26,039 --> 00:18:31,259
could be left behind. And so
their entire specialty is using

285
00:18:31,259 --> 00:18:35,189
Lightning and Bitcoin. And we
are both on chain and Lightning

286
00:18:35,189 --> 00:18:39,809
Network as the transport layer,
but you know, so you can put in

287
00:18:39,809 --> 00:18:44,909
euros on one side and get pesos
out the other side? Oh, okay. So

288
00:18:44,909 --> 00:18:47,399
for them, and this is something
they want it to do integrate

289
00:18:47,399 --> 00:18:52,889
with, with what we're doing. So
in essence, we're building and I

290
00:18:52,889 --> 00:18:55,379
say we because they're doing it
all. And I'm just saying, Hey,

291
00:18:55,379 --> 00:18:57,719
here's what we need for no
agenda. And here's how I would

292
00:18:57,719 --> 00:19:02,309
have to work which includes, you
know, HTTP URLs that you can

293
00:19:02,309 --> 00:19:05,519
encode with a preset amount that
you can just put it throw into a

294
00:19:05,519 --> 00:19:11,879
newsletter, of course, QR code
generator, you know, we have to

295
00:19:11,879 --> 00:19:15,119
capture certain data for for
value for value, which will be a

296
00:19:15,119 --> 00:19:20,129
name can be whatever, are they
an alias, and an A donation

297
00:19:20,129 --> 00:19:25,649
note. But then also, they're
going to work on timed

298
00:19:25,649 --> 00:19:30,599
subscriptions. So you can say x
amount per episode or per week

299
00:19:30,599 --> 00:19:36,569
or whatever. And and then, I
mean, basically everything that

300
00:19:36,569 --> 00:19:41,549
PayPal and Patreon do they'll be
doing that and and I don't think

301
00:19:41,549 --> 00:19:46,199
they'll want to be doing
statistics or anything. I don't

302
00:19:46,199 --> 00:19:50,219
think you know, that seems like
I only got one to talk about

303
00:19:50,219 --> 00:19:52,469
today. You know, there's there's
enough companies who have kind

304
00:19:52,469 --> 00:19:54,929
of figured that out. And as I
was thinking about it, it's so

305
00:19:54,929 --> 00:19:59,189
cool how you can easily switch
it to a provider of a different

306
00:19:59,189 --> 00:20:05,579
service. specifically for
statistics, by just adding a 1%

307
00:20:05,579 --> 00:20:09,449
split to your to your value
block. It's, it's like, Hey, let

308
00:20:09,449 --> 00:20:12,089
me test out this service boom,
oh, let me test out the boost

309
00:20:12,089 --> 00:20:14,879
bot. Oh, I can test that here. I
don't like it, I just take out

310
00:20:14,879 --> 00:20:18,839
the split. I mean, this is mind
blowing crap. This is this is

311
00:20:18,839 --> 00:20:25,169
this isn't a non developers API
dream, like I can connect to an

312
00:20:25,169 --> 00:20:28,319
API just by putting a split into
my value block.

313
00:20:29,430 --> 00:20:32,310
That makes me think about
whether or not there should be a

314
00:20:32,310 --> 00:20:35,040
specific split type.

315
00:20:36,540 --> 00:20:37,350
Where

316
00:20:37,710 --> 00:20:41,460
the, you know, you have a
specific value recipient type.

317
00:20:42,090 --> 00:20:46,740
That's sort of like sort of like
fee, but, but something that

318
00:20:46,740 --> 00:20:51,240
signifies this is just for stats
or linkage or something like

319
00:20:51,240 --> 00:20:55,560
that. And the idea there was it
was just add on that on that.

320
00:20:55,560 --> 00:20:58,440
I don't know if there's, I mean,
the whole idea is just, you

321
00:20:58,440 --> 00:21:02,190
know, just add one 1%. The
money's going and of course, it

322
00:21:02,190 --> 00:21:05,850
may be going towards a service
that that gives you statistics,

323
00:21:05,850 --> 00:21:12,030
but keeps the Satoshi why not.
Yeah. Yeah. If I if I, sorry, I

324
00:21:12,030 --> 00:21:15,030
just came up with a business
model. If I were the

325
00:21:16,500 --> 00:21:17,700
ps3 before breakfast,

326
00:21:17,730 --> 00:21:24,960
I know Hey, more cowbell, baby.
So here's an idea. You want to

327
00:21:24,960 --> 00:21:28,410
take advantage of this service?
So you put us in the split for

328
00:21:28,410 --> 00:21:32,880
X, whatever it is. And that's
how you get the service.

329
00:21:33,570 --> 00:21:35,880
And the SATs just disappear.
They get consumed? Yeah, but

330
00:21:35,880 --> 00:21:36,120
yeah,

331
00:21:37,290 --> 00:21:40,830
I just had on no agenda for the
first time I just, I just

332
00:21:40,830 --> 00:21:44,340
completed it now. The first
time. You know, we have a

333
00:21:44,340 --> 00:21:48,270
different piece of album art
every single time on the show,

334
00:21:48,270 --> 00:21:51,480
which and we just had no agenda
Art Generator, there's now 30,

335
00:21:51,480 --> 00:21:55,530
almost 30,000 individual pieces
of art. We've only done 1500

336
00:21:55,530 --> 00:22:01,050
episodes. So you can imagine how
much we have to choose from each

337
00:22:01,050 --> 00:22:06,240
time and finally and Nico Sime
key, and I'd asked artists to do

338
00:22:06,240 --> 00:22:11,550
that he put his get lb details
in his profile. And I put him in

339
00:22:11,550 --> 00:22:15,120
the split for that episode for
10 points. Oh.

340
00:22:16,710 --> 00:22:17,880
So how did that go over?

341
00:22:17,910 --> 00:22:21,060
Well, so unfortunately, I didn't
have the details until this

342
00:22:21,060 --> 00:22:24,090
morning. So he should be
receiving stuff as of now

343
00:22:24,090 --> 00:22:29,250
because as we were just going,
going lit here I got the details

344
00:22:29,250 --> 00:22:33,510
and I figured I'm gonna put it
in right away. So I'm not and

345
00:22:33,540 --> 00:22:36,450
this is a comic strip blogger
has been driving this, although

346
00:22:36,450 --> 00:22:40,680
he's always many, many artists
are very skeptical about

347
00:22:40,710 --> 00:22:47,160
Bitcoin. Alright? Don't Don't
Don't take any whatever it

348
00:22:49,230 --> 00:22:51,120
is zero is also an option. Yeah,

349
00:22:51,150 --> 00:23:01,980
so speaking of such contracts,
co n s hax popped up on nogen

350
00:23:01,980 --> 00:23:04,710
agenda, podcasts index dot
social.

351
00:23:05,430 --> 00:23:08,760
This seems to be an evolution of
the Saturn dashboard.

352
00:23:09,060 --> 00:23:13,950
I believe so I believe so. I'm
not I'm not sure exactly who's

353
00:23:13,950 --> 00:23:17,040
driving it. But there is deep
integration and discussion

354
00:23:17,040 --> 00:23:22,380
between the people behind the
contracts against EO n sh, a x

355
00:23:22,380 --> 00:23:34,200
dot app, and N lb. So this is a
very expanded statistics package

356
00:23:34,230 --> 00:23:40,020
really, for anything happening
in your Albea wallet for

357
00:23:40,020 --> 00:23:43,890
podcasts? I mean, I'm just
looking at the dashboard it has

358
00:23:44,370 --> 00:23:47,610
how many number of donations and
you can do it by so if I do for

359
00:23:47,610 --> 00:23:53,940
seven day overview here gives
you all time donations in this

360
00:23:53,970 --> 00:24:02,280
in this particular time period.
You go to burnings it has you

361
00:24:02,280 --> 00:24:07,020
know, total donated amount
number of supporters sat stream

362
00:24:07,050 --> 00:24:12,360
minutes, so 9901 minutes, and it
does the only thing is the

363
00:24:12,360 --> 00:24:15,270
problem is that you know, of
course, Adam shows up hey, let

364
00:24:15,270 --> 00:24:19,110
me try your shit. And then oh,
great. Well, we Yes, exactly. We

365
00:24:19,110 --> 00:24:22,590
never, we never expected to have
more than 100,000 transactions.

366
00:24:22,590 --> 00:24:26,700
I'm like, Yeah, hold my beer and
connect here. Like watch this.

367
00:24:28,050 --> 00:24:32,790
But it's really it's really
really pretty. I'm gonna get mo

368
00:24:34,050 --> 00:24:37,020
get him set up because this is
something you can actually look

369
00:24:37,020 --> 00:24:41,100
at this and say Holy crap, this
is useful. And there's a lot of

370
00:24:41,100 --> 00:24:45,570
useful information in here a lot
of easy ways to see the booster

371
00:24:45,570 --> 00:24:52,260
grams to really slice and dice
of ano in. They've got analytics

372
00:24:52,260 --> 00:24:55,950
we can look at total number of
supporters in the timeline so

373
00:24:55,950 --> 00:24:59,970
people actually listening that
goes up or down and then you can

374
00:25:00,000 --> 00:25:04,620
See the donation amounts in a
separate I mean, per episode for

375
00:25:04,620 --> 00:25:08,640
the whole, you know, for a whole
series. It's just really really

376
00:25:08,640 --> 00:25:13,680
cool. And I would say, you know,
take my Satoshi or whatever I

377
00:25:13,680 --> 00:25:14,460
have to send

378
00:25:15,300 --> 00:25:18,900
Yeah, so keep that luggage so I
haven't looked at this and then

379
00:25:18,900 --> 00:25:23,820
looked at the dashboard so is
this something how do you do the

380
00:25:23,820 --> 00:25:25,890
connection? Is it oh auth or do
you just say

381
00:25:26,520 --> 00:25:32,010
it does you do Oh hold on I'm
gonna log out this is the new

382
00:25:32,010 --> 00:25:36,480
thing that that I'll be a smart
about. So you hit contracts dot

383
00:25:36,480 --> 00:25:43,620
app. And it says contracts. Oh
man, look at this. Contracts

384
00:25:43,860 --> 00:25:49,140
value for value dashboard.
Stripes wrote your SAS Yeah,

385
00:25:49,140 --> 00:25:55,800
login without me here. So login
with Alby pops up the Alvie

386
00:25:55,800 --> 00:26:03,360
authorization pane authorize and
boom you're in and that's it.

387
00:26:03,360 --> 00:26:06,930
And it right away you can see
the purple dots as it's loading

388
00:26:06,930 --> 00:26:08,040
your transactions.

389
00:26:09,540 --> 00:26:11,790
It's doing that with me too. And
I'm wonder if

390
00:26:12,120 --> 00:26:14,370
maybe we just broke it because
oh, there it is. Now mine's

391
00:26:14,370 --> 00:26:15,780
loading now monopole? Yeah, Monk

392
00:26:15,780 --> 00:26:22,110
pulled up, missy. Yemen's pulled
up. So what? Okay, so this, I

393
00:26:22,110 --> 00:26:27,930
would challenge here, I would
challenge people. Somebody out

394
00:26:27,930 --> 00:26:34,350
there developers out there, too.
Do something like because this

395
00:26:34,350 --> 00:26:37,530
is all this is Oh, auth, which
is great. I mean, this is nice

396
00:26:37,530 --> 00:26:40,800
if you're in the ABI ecosystem.
But if you're not in the ABI

397
00:26:40,800 --> 00:26:43,500
ecosystem, you can't use this.

398
00:26:43,710 --> 00:26:46,350
Now, what does they have another
option? What is it? Oh, I guess

399
00:26:46,350 --> 00:26:49,410
they don't know, this is only
within the lbu ecosystem. You

400
00:26:49,410 --> 00:26:51,540
should be able to connect it to
your own node though.

401
00:26:52,560 --> 00:26:56,160
Yes, I mean, I guess you you
have a you have hella pad and

402
00:26:56,160 --> 00:26:58,920
things like that. So this is not
a criticism of Albie. I mean, if

403
00:26:58,920 --> 00:27:01,320
you're in the fountain
ecosystem, you're, you're gonna

404
00:27:01,320 --> 00:27:04,710
live you're gonna see fountains
stats, if you're in the abbey

405
00:27:04,710 --> 00:27:07,110
ecosystem, you're gonna see
Abbey stack, you know, if

406
00:27:07,110 --> 00:27:11,460
you're, if you're, you know,
cowboy and you run Iran, you're

407
00:27:11,460 --> 00:27:14,010
on horse, you're gonna do,
you're gonna have hella pat or

408
00:27:14,010 --> 00:27:17,520
whatever. But I would, it would
be nice if there was a thing

409
00:27:17,940 --> 00:27:21,150
that worked the way that we,
that you just described earlier,

410
00:27:21,150 --> 00:27:26,460
where you just simply give it a
split of some amount, 1%,

411
00:27:26,460 --> 00:27:31,350
whatever. In those set, those
sets get consumed by the by the

412
00:27:31,350 --> 00:27:34,860
dashboard service or the stats
service, and you just get the

413
00:27:34,860 --> 00:27:38,820
stats. That would be cool. And
where you don't have to even do

414
00:27:39,149 --> 00:27:42,629
a run or anything, run it by me
again, I just want to make sure

415
00:27:42,629 --> 00:27:43,319
I understand it.

416
00:27:43,860 --> 00:27:48,570
Yeah. So like it would be a
stats dashboard service, where

417
00:27:48,570 --> 00:27:53,010
you just throw the split in. And
you're not, you're not you're

418
00:27:53,010 --> 00:27:57,300
not sending to your to a wallet
you own. Right, usually you're

419
00:27:57,300 --> 00:27:58,620
just for the service. Yeah, you
just

420
00:27:58,620 --> 00:28:04,200
pay. Now, the only problem is
you're sending percentages, not

421
00:28:04,230 --> 00:28:10,620
not individual SATs. So it could
be modeled on the one in my mind

422
00:28:10,620 --> 00:28:13,380
is yeah, it's value for value.
So people have to understand

423
00:28:13,380 --> 00:28:16,080
you're going to be sending more
just just like any other split.

424
00:28:16,290 --> 00:28:19,320
But I think that's the way to
go. That's like immediate,

425
00:28:19,470 --> 00:28:23,430
immediate makes sense. When he
was really, podcasts index gets

426
00:28:24,540 --> 00:28:29,280
one 1%. Now, of course, when
you're under 100 SATs, we're

427
00:28:29,280 --> 00:28:34,050
still getting one Satoshi. So
it's not it's much more than 1%

428
00:28:34,080 --> 00:28:36,420
under the under the 100 sat
level.

429
00:28:36,810 --> 00:28:41,010
And that's dipping in that is
all depending on the way the app

430
00:28:41,010 --> 00:28:43,110
wants to handle that like they
need. Yeah, there's a

431
00:28:43,110 --> 00:28:46,500
lot of different ways but so
just from the traffic itself,

432
00:28:46,770 --> 00:28:50,160
you know, we're able to provide
nice liquidity you know, we've

433
00:28:50,160 --> 00:28:54,420
never added any Fiat or any
other external Bitcoin to the

434
00:28:54,420 --> 00:28:56,940
wallets and then the initial
amounts we put in.

435
00:28:57,960 --> 00:29:01,950
Yeah, the only thing I think the
only I think the only the only

436
00:29:01,950 --> 00:29:05,850
money we put into the node is
when we first built it. And we

437
00:29:05,850 --> 00:29:06,510
put what,

438
00:29:06,780 --> 00:29:09,570
like 100 bucks for 1500 bucks,
but I don't know, I don't

439
00:29:09,570 --> 00:29:13,410
remember what the what the
exchange was at the time.

440
00:29:14,100 --> 00:29:16,950
Yeah, yeah. So that and we
haven't had to add anything

441
00:29:16,950 --> 00:29:19,860
else. No, from Fiat since so
everything has been self

442
00:29:19,860 --> 00:29:23,760
sustaining. Yeah, I mean, that's
a real it's a real service. I

443
00:29:23,760 --> 00:29:27,630
mean, it could make it really
work. Yeah, just like to see

444
00:29:27,630 --> 00:29:30,240
that because he because that
gets you that it provides you

445
00:29:30,240 --> 00:29:33,510
have seen this outside of it's
like you don't have to be within

446
00:29:33,510 --> 00:29:37,710
fountain or Alby or or is not a
wallet provider. Do zoom in

447
00:29:37,710 --> 00:29:44,310
Yeah, no, I it's exactly this.
In fact, contracts dues I'll be

448
00:29:44,310 --> 00:29:47,640
your crazy if you don't do this,
turn it around right away. Right

449
00:29:47,640 --> 00:29:52,440
away. Allow that, you know, so
perfect. Such a perfect idea.

450
00:29:52,800 --> 00:29:55,830
It's the it's like having Hilah
pad but you don't have to run

451
00:29:55,830 --> 00:29:56,460
your own node.

452
00:29:56,490 --> 00:30:01,080
Right. Exactly. Exactly. And
that And that's worth a split.

453
00:30:01,860 --> 00:30:04,740
No, yeah. It's really, really
worth a split. And it's

454
00:30:04,740 --> 00:30:07,680
completely controllable. No
signup required. You know, it's

455
00:30:07,680 --> 00:30:10,620
like, Hey, you sent us that you
send us the money. We know where

456
00:30:10,620 --> 00:30:11,850
you're coming from your end.

457
00:30:12,420 --> 00:30:15,510
And since you get the original
SATs thing in there since since

458
00:30:15,510 --> 00:30:18,780
that property is within each
payment, yeah, you can, you

459
00:30:18,780 --> 00:30:21,630
could do things like calculate
taxes. At the end of the year,

460
00:30:21,630 --> 00:30:25,230
you can generate a sheet that
shows your income and all that

461
00:30:25,230 --> 00:30:28,950
stuff. When you fall in the hole
essentially gives you like a

462
00:30:28,950 --> 00:30:30,900
little 1099 type deal.

463
00:30:30,930 --> 00:30:33,270
Yeah, that's the only thing
current contracts hasn't done

464
00:30:33,270 --> 00:30:36,630
right. Yet. They don't I don't
think they understood. They

465
00:30:36,630 --> 00:30:37,170
haven't figured

466
00:30:37,470 --> 00:30:39,150
it comes down statement. That's
what should give you like little

467
00:30:39,150 --> 00:30:40,560
income state a whole p&l

468
00:30:40,560 --> 00:30:42,120
baby. The p&l

469
00:30:44,550 --> 00:30:46,770
should give you a p&l your
business off, actually,

470
00:30:46,770 --> 00:30:49,680
they know they do do that.
Right. Let me see. So Oh, cool.

471
00:30:49,680 --> 00:30:55,800
It says Your biggest supporter.
Okay, it's podcasting to I think

472
00:30:56,370 --> 00:30:59,370
you can now set it to load a
million transactions. But what

473
00:30:59,370 --> 00:31:02,430
is that for me? Like, a week? I
don't know. What about how many

474
00:31:02,430 --> 00:31:03,870
transactions come in?

475
00:31:04,260 --> 00:31:08,070
It's more than that. is more
than a week? It's? Yeah, I don't

476
00:31:08,070 --> 00:31:09,660
remember. I mean, I think I
think,

477
00:31:10,169 --> 00:31:13,469
because to look at it, it has
the biggest supporter, March

478
00:31:13,469 --> 00:31:20,849
elevens. 100. Now 100,000, we've
had much bigger than that. So

479
00:31:20,849 --> 00:31:22,799
I'm not quite sure why that's
showing that way.

480
00:31:23,790 --> 00:31:27,990
It's probably struggling to pull
that in. And we're just, we're,

481
00:31:28,080 --> 00:31:30,420
we're not the ideal use case for
this.

482
00:31:30,720 --> 00:31:34,620
No, yes or no, yes or no. But
regardless, it's fantastic. I

483
00:31:34,620 --> 00:31:37,890
want to go back to Ibex PE for a
second because then, so this,

484
00:31:37,920 --> 00:31:40,080
you know, I think there's 40
people in the company. So we'll

485
00:31:40,080 --> 00:31:43,740
company, there's a nice little
team who I have the pleasure of,

486
00:31:43,770 --> 00:31:47,130
of basically telling them what I
really want, and they're going

487
00:31:47,130 --> 00:31:49,620
to build it and they're going to
offer it and the way they work

488
00:31:49,620 --> 00:31:55,320
is 1% 1% of the transaction,
that's their fee, and they can

489
00:31:55,320 --> 00:32:00,000
send it straight into a
different currency. So you can

490
00:32:00,030 --> 00:32:02,520
end and you couldn't there's a
slider, you can say, well, I

491
00:32:02,520 --> 00:32:09,150
want like 80% in dollars and
keep 20% in Bitcoin Satoshis.

492
00:32:09,570 --> 00:32:12,480
You can you can slide that
dynamically wherever you want it

493
00:32:12,480 --> 00:32:17,460
to be anything. Once it's over
$50 they flush it right out to

494
00:32:17,460 --> 00:32:22,980
your to your bank through ACH.
So it's cool service now says

495
00:32:23,520 --> 00:32:26,700
they're doing something very
interesting. Something I said,

496
00:32:26,700 --> 00:32:29,130
Hey, you know, I'm not going to
be arrogant to say that. You

497
00:32:29,130 --> 00:32:31,590
know that you didn't come up
with this. But they did come up

498
00:32:31,590 --> 00:32:36,120
with this really cool thing to
do with SATs. So apparently,

499
00:32:36,120 --> 00:32:39,390
this is an Australian baseball
league. Are you aware of this?

500
00:32:39,840 --> 00:32:42,870
No. Yeah. So there's a real
another head baseball and

501
00:32:42,870 --> 00:32:43,830
Australian Yeah,

502
00:32:43,860 --> 00:32:46,440
I can't believe they're not in
constant fights with the with

503
00:32:46,440 --> 00:32:49,440
the cricket boys. Anyway, so
yeah, apparently there's an

504
00:32:49,440 --> 00:32:53,370
Australian baseball league. And
they play big venues because

505
00:32:53,370 --> 00:32:57,930
they got jumbotrons. And so now
they're they're going to do I'm

506
00:32:57,930 --> 00:33:01,320
not sure when or when this is
starting. But on the Jumbotron

507
00:33:01,320 --> 00:33:05,340
when when a batter is up,
they'll have stats for SATs for

508
00:33:05,340 --> 00:33:09,480
stats. So they'll have his
stats, you know, his RBIs, and

509
00:33:09,480 --> 00:33:12,720
whatever it is, and they'll have
a QR code. So you can scan it

510
00:33:12,720 --> 00:33:16,830
and send him SATs right then and
there on the spot. If he's in

511
00:33:16,830 --> 00:33:21,150
the stadium in the stadium, if
he screws up and makes an error,

512
00:33:21,180 --> 00:33:24,930
then the then they have a steal
the SAT. So the first 100 people

513
00:33:24,930 --> 00:33:30,330
to scan the QR code, get to take
money away from the player. I

514
00:33:30,330 --> 00:33:32,700
like that shit a lot, man,
because they're gonna do an ln

515
00:33:32,700 --> 00:33:38,220
URL. You know, withdrawal or
all? Yeah, withdraw. Limited to

516
00:33:38,220 --> 00:33:42,750
100 the first 100 I'm like, This
is great. It's a great idea. I

517
00:33:42,750 --> 00:33:44,460
love it. You got to put some,

518
00:33:44,610 --> 00:33:48,870
yeah, it's very, it's very
Australian to also give away to

519
00:33:48,870 --> 00:33:50,490
pin lesson, buddy. Right?

520
00:33:50,970 --> 00:33:53,850
So anyway, so you know, we also
talked a bit about music, and

521
00:33:53,850 --> 00:33:57,060
they were super interested in
that, because that's their whole

522
00:33:57,060 --> 00:34:01,950
thing. Their core mission is to
make sure that if you want to go

523
00:34:01,950 --> 00:34:06,930
from currency to Bitcoin, or
vice versa, that's what they do,

524
00:34:06,930 --> 00:34:10,890
and they want to facilitate it.
So getting over that hump for

525
00:34:10,890 --> 00:34:14,910
many, with, you know, just, I
just want a receipt, can I

526
00:34:14,910 --> 00:34:17,580
receive dollars this way? Does
it work as a whole unit? I

527
00:34:17,580 --> 00:34:23,280
don't, I don't want to go and
learn about it. lazy bums. This

528
00:34:23,280 --> 00:34:27,750
would get them started. Or if
they're worried about as in, in

529
00:34:27,750 --> 00:34:31,860
some cases, you know, IRS or tax
implications are other stuff

530
00:34:31,860 --> 00:34:35,640
just not comfortable with
Bitcoin on the balance sheet,

531
00:34:35,670 --> 00:34:39,120
etc. Yeah, so I'm really excited
about those guys doing that. I

532
00:34:39,120 --> 00:34:40,770
think it'd be a couple more
weeks. And of course, they're

533
00:34:40,770 --> 00:34:44,520
going to do a case and we're
gonna put it all together, man,

534
00:34:44,610 --> 00:34:45,600
it's gonna be fantastic.

535
00:34:45,990 --> 00:34:49,620
I can't wait to see it to see
how it works to see the first to

536
00:34:49,620 --> 00:34:52,530
see the first you know, the
beginnings of it as a first

537
00:34:52,530 --> 00:34:55,050
starts rolling that's going to
be fun to watch. And I think

538
00:34:55,050 --> 00:34:57,180
it's really I mean, it's really
a big experiment for you guys.

539
00:34:57,240 --> 00:35:00,660
Oh, it's a very big experiment
you want to know agenda can

540
00:35:00,660 --> 00:35:07,530
really do that. And we can do we
can start soliciting V for V in

541
00:35:07,560 --> 00:35:10,410
streams and, and booster grams.
Oh, yeah, it's gonna be

542
00:35:10,410 --> 00:35:11,130
dynamite.

543
00:35:11,460 --> 00:35:14,460
Yeah, cuz you're right, it makes
it makes the boost button within

544
00:35:14,460 --> 00:35:20,490
ABS much more accessible to
people who don't want to do who

545
00:35:20,490 --> 00:35:24,000
don't want to have that on on
their side on their end to

546
00:35:24,000 --> 00:35:25,590
podcasters that don't want to
have

547
00:35:25,620 --> 00:35:28,200
that don't wanna do that final
step. You know, it's like,

548
00:35:28,320 --> 00:35:33,870
imagine if you if you could just
use strike. You know, that would

549
00:35:33,870 --> 00:35:37,140
work but you know, strike, they
only have one kind of couple of

550
00:35:37,140 --> 00:35:40,260
ways of sending money in or out.
And this is a whole they of

551
00:35:40,260 --> 00:35:44,400
course, they have an API, you
can develop it yourself, but I

552
00:35:44,400 --> 00:35:48,720
couldn't motivate anybody. I
couldn't find anybody with any

553
00:35:48,720 --> 00:35:53,520
time. And helpers are lazy. No,
not really. And they jumped

554
00:35:53,520 --> 00:35:56,160
right in and said, No, no, we
want to do this. We want to get

555
00:35:56,160 --> 00:35:58,230
this set up. So

556
00:35:59,250 --> 00:36:01,410
anyway, I'm lazy about it.

557
00:36:02,970 --> 00:36:05,760
You are working hard, man.
That's what's going on with you.

558
00:36:05,790 --> 00:36:08,970
Hey, I told him we would bring
him in early and here I am.

559
00:36:09,120 --> 00:36:11,790
Still true to my word. It's
still early for a five hour

560
00:36:11,790 --> 00:36:16,110
show. Please welcome to the
boardroom. The former Silicon

561
00:36:16,110 --> 00:36:19,980
Valley insider now retired from
public life known as John

562
00:36:19,980 --> 00:36:20,670
Sparrow.

563
00:36:22,560 --> 00:36:24,450
Hey, guys, that's all right.
That's right. I was just

564
00:36:24,450 --> 00:36:27,180
following a Rogers Cadenhead
over on Twitter while you guys

565
00:36:27,180 --> 00:36:33,660
were talking. Shut up for Texas.
So he's from Dallas area, right

566
00:36:33,660 --> 00:36:34,620
next door. Yeah.

567
00:36:34,650 --> 00:36:36,630
Gee, okay. Yeah. Real nice guy.

568
00:36:39,630 --> 00:36:41,760
I'm getting a double dose for
you guys. Because I listened to

569
00:36:41,910 --> 00:36:45,180
pod land or whatever it's
called. Now this very long

570
00:36:45,180 --> 00:36:46,680
chapter. Very long chapter.

571
00:36:47,130 --> 00:36:51,090
Extremely long week for James
and, and Sam a

572
00:36:51,450 --> 00:36:53,220
very long week. Yeah,

573
00:36:53,250 --> 00:36:55,320
I like your guys interview
though. I like hearing the

574
00:36:55,380 --> 00:36:58,080
Genesis story. No matter how
many times I hear it. It's,

575
00:36:58,380 --> 00:37:00,900
there's always a new fact that
comes out there. So that's

576
00:37:01,140 --> 00:37:01,980
always good to hear that.

577
00:37:03,750 --> 00:37:07,440
I want to throw, I want to throw
something in and I jotted this

578
00:37:07,440 --> 00:37:12,360
down on the way to the office
this morning. Not while I was

579
00:37:12,360 --> 00:37:15,600
driving, but I thought of it and
Indra jotted it down when I got

580
00:37:15,600 --> 00:37:20,670
to the office. But there was, I
had printed this thing off a

581
00:37:20,670 --> 00:37:26,520
while back. That quote, I'm sure
you remember it. John, that

582
00:37:26,550 --> 00:37:31,650
quote from Marco Arment, where
he said cheap, sloppy, I think

583
00:37:31,650 --> 00:37:34,650
it was a tweet. He said cheap,
sloppy dynamic ad insertion and

584
00:37:34,650 --> 00:37:38,520
podcasts continues to degrade
the experience for listeners.

585
00:37:39,690 --> 00:37:44,520
And he went on he said more. He
continued it was it was a longer

586
00:37:44,520 --> 00:37:50,250
statement because he then went
into how people are blaming the

587
00:37:50,250 --> 00:37:56,610
podcast apps for bad dynamic ad
insertion. And that second part

588
00:37:56,610 --> 00:37:59,610
of what he said ended up
becoming the entire story within

589
00:37:59,610 --> 00:38:04,740
podcasting. It ended up becoming
a story about how bad dynamic ad

590
00:38:04,740 --> 00:38:09,750
insertion is making is ends up
blaming the apps listeners blame

591
00:38:09,750 --> 00:38:13,020
the apps. But really like the
first part is almost kind of

592
00:38:13,020 --> 00:38:16,020
lost the fact. And what I mean
by the first part is the fact

593
00:38:16,020 --> 00:38:18,810
that there even is cheap,
sloppy, dynamic ad insertion.

594
00:38:19,080 --> 00:38:23,910
And I would, I would go further
and say, more than just cheap,

595
00:38:23,910 --> 00:38:26,940
sloppy dynamic ad insertion, I
would say dynamic ad insertion

596
00:38:26,970 --> 00:38:33,600
at all. And so here's what I'm
trying to get to. I feel this

597
00:38:33,600 --> 00:38:39,030
comes up a lot, where you look
at things like chapters,

598
00:38:39,030 --> 00:38:45,630
transcripts, we know what have
you. And the question is, yeah,

599
00:38:45,630 --> 00:38:48,330
but that gets really complicated
and starts to break when you

600
00:38:48,330 --> 00:38:51,510
have dynamic ad insertion,
specifically when you have

601
00:38:51,510 --> 00:38:57,930
dynamic ad insertion that is
that is that takes the form of

602
00:38:58,290 --> 00:39:04,470
every GET request stitches
together a new mp3 file that

603
00:39:04,470 --> 00:39:10,290
didn't exist before, sometimes
with ads sometimes without, with

604
00:39:10,290 --> 00:39:17,190
various ad slots or Lyford
links. Yes. And so, I guess I

605
00:39:17,190 --> 00:39:23,790
just wanted to this, this feels
like what's the right way to say

606
00:39:23,790 --> 00:39:31,080
this, this feels like sort of a
bastardization of HTTP of the

607
00:39:31,080 --> 00:39:41,280
delivery of of the delivery of
files through HTTP. And it feels

608
00:39:41,280 --> 00:39:48,510
like this is all going to this
all rolls back to advertising

609
00:39:49,110 --> 00:39:53,790
being based on IP addresses and
geo locate that's why this in

610
00:39:53,790 --> 00:39:57,420
the in the context of op three
this this gives me in what

611
00:39:57,420 --> 00:40:01,110
you're doing makes sense to me.
There's this Whole, there's this

612
00:40:01,110 --> 00:40:06,870
whole construct that is now,
really in the last two years has

613
00:40:06,870 --> 00:40:11,730
really come to dominate podcast
delivery. And it's this idea

614
00:40:11,730 --> 00:40:17,460
that, you know, downloads are
king. IP geolocation is king,

615
00:40:18,300 --> 00:40:25,260
you know, met user information
based on IP addresses is

616
00:40:25,290 --> 00:40:30,390
legitimate. And so you've had
this entire construct that has

617
00:40:30,420 --> 00:40:35,160
grown in the last couple of
years really, for this

618
00:40:35,250 --> 00:40:40,950
dynamically stitched together on
the fly content, it's breaking

619
00:40:41,430 --> 00:40:44,820
things within podcasting, that
are good ideas and making that

620
00:40:44,820 --> 00:40:51,960
stuff difficult. And the real
problem is down the road, it

621
00:40:51,960 --> 00:40:55,260
feels like it's all gonna fall
apart anyway. Because IP,

622
00:40:55,890 --> 00:41:00,750
there's going to they're we're
moving towards a world where IP

623
00:41:00,930 --> 00:41:04,320
addresses are not going to be
reliable sources of that

624
00:41:04,320 --> 00:41:07,740
information anyway. So the whole
thing, just this whole on the

625
00:41:07,740 --> 00:41:11,130
fly dynamic stitching of
advertising into into audio

626
00:41:11,130 --> 00:41:16,830
enclosures, it feels like a
house of cards, that now that's

627
00:41:16,830 --> 00:41:20,670
a huge soliloquy that I'm now
going to turn over to you to

628
00:41:20,670 --> 00:41:21,240
reply to.

629
00:41:23,280 --> 00:41:28,530
I agree, it makes things more
difficult. But I don't see that

630
00:41:28,530 --> 00:41:30,750
changing. And in fact, if you
listen to a lot of the

631
00:41:30,750 --> 00:41:33,030
conversations that are going on,
I think you're gonna see it a

632
00:41:33,030 --> 00:41:37,050
lot more, as opposed to a lot
less going for because they are

633
00:41:37,050 --> 00:41:40,800
outsourcing. So these hosts are
outsourcing to third parties

634
00:41:40,800 --> 00:41:44,040
that do this, you know, for
them. So I think you're gonna

635
00:41:44,040 --> 00:41:47,280
see a lot more of it, I, I think
we need to figure out as a

636
00:41:47,280 --> 00:41:52,920
group, how to work in the world
where that's the case. So I

637
00:41:52,920 --> 00:41:56,010
think we should be able to tweak
I'm pretty optimistic that we

638
00:41:56,010 --> 00:41:59,790
can live in the world where
things are delivered that way,

639
00:41:59,820 --> 00:42:03,180
because even without the user
targeting, that's one of the

640
00:42:03,180 --> 00:42:06,120
things you mentioned, that might
make it less interesting in the

641
00:42:06,120 --> 00:42:09,570
future, they still have
inventory. So they, you know,

642
00:42:09,570 --> 00:42:13,860
you want to send the ad out 20
times and then stop, you know,

643
00:42:13,860 --> 00:42:16,680
no matter who's listening to it,
that's always going to be there.

644
00:42:17,220 --> 00:42:22,050
So even if they, a lot of hosts
will do that now after the fact.

645
00:42:22,050 --> 00:42:24,810
So they'll kind of like let it
run and then re stitch a static

646
00:42:24,810 --> 00:42:27,660
file. But ultimately, they're
all going to go towards the same

647
00:42:27,660 --> 00:42:30,870
thing where, you know, it's like
the old AdSense thing. Like

648
00:42:30,870 --> 00:42:35,070
we'll we'll just have some
programmatic way of buying stuff

649
00:42:35,070 --> 00:42:39,420
to stick in podcasts. And then a
way to stitch it on the back

650
00:42:39,420 --> 00:42:41,550
end. And if they don't build it
themselves, they'll definitely

651
00:42:41,550 --> 00:42:45,210
use a third party to do it like
blueberry. Right? That's someone

652
00:42:45,210 --> 00:42:47,790
that yeah, has a bunch of
development stuff on there. And

653
00:42:47,790 --> 00:42:51,810
but they are working with a
third party to do it. For their

654
00:42:51,840 --> 00:42:56,370
for their shows. And I see I see
it just getting, I don't want to

655
00:42:56,370 --> 00:42:58,650
say better or worse, but
definitely, like more prevalent

656
00:42:58,650 --> 00:43:01,530
going forward. So I would, I
would hope that we can come up

657
00:43:01,530 --> 00:43:05,070
with things that work in that
world, as opposed to trying to

658
00:43:05,070 --> 00:43:07,680
say, it's always going to be
static files forever.

659
00:43:08,910 --> 00:43:12,870
That is, I was it was really
hitting me hard because we were

660
00:43:12,870 --> 00:43:17,550
doing me and Alex are running
these parallel download things

661
00:43:17,550 --> 00:43:21,690
such as this taking. His thing
is taking weeks because like,

662
00:43:22,020 --> 00:43:24,420
you know, if you're going
through form and downloading 4

663
00:43:24,420 --> 00:43:28,890
million enclosures are over
that. Man, I hit a batch the

664
00:43:28,890 --> 00:43:35,040
other day, these enclosures were
huge. I mean, like four, five

665
00:43:35,040 --> 00:43:39,570
gigabytes in size. And it's just
not like all of a sudden my disk

666
00:43:39,570 --> 00:43:42,810
space when we know where we're
at now. Oh, wow, what just

667
00:43:42,810 --> 00:43:45,930
happened? And I started looking
through these things. And then

668
00:43:45,930 --> 00:43:48,180
it got me a little nervous. I'm
like, Okay, what am I actually

669
00:43:48,180 --> 00:43:54,270
download? Movies. They were,
they were not movies, they were

670
00:43:55,050 --> 00:43:59,910
like video blogs. Of like some
ladies like showing how to knit

671
00:43:59,910 --> 00:44:00,600
a hat. Oh,

672
00:44:00,600 --> 00:44:04,530
I uploaded the raw the raw
video, the raw files straight

673
00:44:04,530 --> 00:44:09,090
from from what is it? Adobe
starter kit,

674
00:44:09,450 --> 00:44:12,090
or something like that? Yeah, it
was like a it was like a five

675
00:44:12,090 --> 00:44:19,800
gig move dot mov file. It was in
like, you know, 10 ADP. And it's

676
00:44:19,800 --> 00:44:20,970
just her knitting knitting a
hat.

677
00:44:21,450 --> 00:44:23,070
That's cool, though. I mean,
that's the cool thing about

678
00:44:23,070 --> 00:44:25,800
podcasts eventually, you know,
there'll be players that can

679
00:44:25,830 --> 00:44:27,300
they can play that kind of
stuff. So I loved

680
00:44:28,020 --> 00:44:28,770
I loved it, but I was

681
00:44:30,270 --> 00:44:31,260
knitting It's

682
00:44:32,940 --> 00:44:36,660
Sunday, I was thinking, knitting

683
00:44:38,910 --> 00:44:43,560
that every one of these
downloads that I've requested

684
00:44:43,620 --> 00:44:48,030
and received in order to just
simply do analysis. I'm going to

685
00:44:48,030 --> 00:44:51,930
download the episode run an
analysis on it with the with a

686
00:44:51,930 --> 00:44:56,940
with the ML model and then toss
it every one of those in a

687
00:44:56,940 --> 00:45:02,880
dynamic ad insertion model I got
delivered in a head for that.

688
00:45:03,420 --> 00:45:09,990
And that ad was a complete waste
of, of money like this. This

689
00:45:10,020 --> 00:45:12,240
was yesterday, should they use
for it? Do

690
00:45:14,040 --> 00:45:16,320
I just use the podcast index
user agent? Yeah.

691
00:45:16,380 --> 00:45:20,040
Oh, it's not. It's not iOS. It's
not getting monetized. Yeah,

692
00:45:20,070 --> 00:45:22,470
exactly. Now, if you put
overcast in there, I would agree

693
00:45:22,470 --> 00:45:24,630
with you. I think they are
filtering that out. So they know

694
00:45:24,630 --> 00:45:26,880
they delivered it, but they're
not going to charge anyone for

695
00:45:26,880 --> 00:45:29,130
that as long as you use curl or
something like that.

696
00:45:29,520 --> 00:45:33,660
Sure. It just goes back to the
whole. I guess, I guess the

697
00:45:33,660 --> 00:45:36,900
concern I have is that there's a
front, it feels like there's a

698
00:45:36,900 --> 00:45:40,350
framework that there's going to
be answers to all of these

699
00:45:40,350 --> 00:45:42,690
things, everything I can throw
out, there's going to be

700
00:45:42,690 --> 00:45:44,460
something like, oh, yeah, well,
then, you know, they've already

701
00:45:44,460 --> 00:45:49,320
thought of it. And I agree, I do
agree, understand this. There. I

702
00:45:49,320 --> 00:45:51,660
guess in general, I can't kick
this feeling that there's been a

703
00:45:51,660 --> 00:45:56,220
framework built here on on a
little bit of shaky ground,

704
00:45:56,220 --> 00:45:59,370
which is sort of goes back to
what James and and Sam were

705
00:45:59,370 --> 00:46:02,190
talking about the other day
with. And sort of when, when

706
00:46:02,190 --> 00:46:05,160
we're thinking everybody is
still concentrated on downloads

707
00:46:05,160 --> 00:46:11,010
instead of listens. And, and I
think we do really have to move

708
00:46:11,430 --> 00:46:14,670
towards trying to think of
listens instead of downloads,

709
00:46:14,670 --> 00:46:19,170
because every download centric
model just makes everything is

710
00:46:19,170 --> 00:46:21,270
still very shaky and unstable.

711
00:46:21,420 --> 00:46:24,510
Okay, so here's, here's my idea.
I'm gonna have to give you my

712
00:46:24,510 --> 00:46:28,620
idea now for a second. Alright,
because it'll it'll take us into

713
00:46:28,680 --> 00:46:32,580
the hopefully into more
conversation. Can't we just

714
00:46:33,030 --> 00:46:40,860
create a podcast events
parameter that is returned my

715
00:46:41,400 --> 00:46:45,450
listening habits? And in some
cases, maybe the app gives you a

716
00:46:45,450 --> 00:46:49,110
Satoshi for it per minute or
whatever? I mean, isn't that

717
00:46:49,110 --> 00:46:53,220
just a simple way? We all know,
ultimately, it has to come from

718
00:46:53,220 --> 00:46:57,870
the player side. If the player
side utilizes podcast events,

719
00:46:57,900 --> 00:47:01,950
the podcast events tag in the
namespace? Can't one of the

720
00:47:01,950 --> 00:47:07,920
events be, you know, voluntarily
report. I mean, there's a lot of

721
00:47:07,920 --> 00:47:10,710
trust issues here. But we got to
start somewhere. I mean, that

722
00:47:10,710 --> 00:47:15,390
seems like a very elegant way to
do it. Because for 18 years,

723
00:47:15,390 --> 00:47:18,630
I've said you can't monetize the
network, this will never work,

724
00:47:18,630 --> 00:47:21,810
it's only going to get worse. If
this is the standard is just

725
00:47:21,810 --> 00:47:26,610
going to and I see the IAB
framework and apps and all kinds

726
00:47:26,610 --> 00:47:28,890
of shit. It's disgusting.

727
00:47:29,940 --> 00:47:32,310
And honestly, even from a tech
point of view, it's kind of

728
00:47:32,310 --> 00:47:37,200
dumb, because they would a good
player in a good system would

729
00:47:37,200 --> 00:47:41,280
cache a lot of this stuff. But
it's it's a business decision

730
00:47:41,280 --> 00:47:43,650
why they're not allowing
caching, right? Like all these

731
00:47:43,650 --> 00:47:47,280
hosters are like don't cache
whereas in any other world, they

732
00:47:47,280 --> 00:47:50,010
would be pleased cache because
you're not hitting our servers

733
00:47:50,010 --> 00:47:53,610
over and over. So the reason
they do that is because they

734
00:47:53,610 --> 00:47:58,620
need some level of info of
what's going on. So yeah, if

735
00:47:58,620 --> 00:48:00,600
there's another way of getting
that, but you

736
00:48:00,600 --> 00:48:04,350
know, what gets me that'll be
great. What gets me, John is,

737
00:48:04,710 --> 00:48:08,160
and by the way, we didn't really
intro John properly. But of

738
00:48:08,160 --> 00:48:10,980
course, one of the main things
he set up is Opie

739
00:48:10,980 --> 00:48:16,500
three.org to.org dot Dev, right,
dot dev Opie three dot Dev. And

740
00:48:16,500 --> 00:48:19,290
so and we need to delve into
that a little bit closer. So

741
00:48:19,290 --> 00:48:24,390
he's been really working on on
these data, you know, as what do

742
00:48:24,390 --> 00:48:30,270
you call it a prefix. Service.
It's not really a good name. But

743
00:48:30,270 --> 00:48:33,810
yeah, prefix analytics, stats
service. And

744
00:48:33,810 --> 00:48:37,320
what gets me is that I'm sitting
here, literally, May, I made

745
00:48:37,320 --> 00:48:40,770
three decisions. Here's the
decision I made based upon

746
00:48:40,770 --> 00:48:43,290
listening data. So this has
nothing to do with advertising.

747
00:48:43,290 --> 00:48:48,420
But so just just to keep it with
listens versus downloads. And I

748
00:48:48,420 --> 00:48:52,740
did this in the in the Saturn
analytics that's connected to

749
00:48:52,740 --> 00:48:56,760
Alby. And I saw that and we had
three shows planned for no

750
00:48:56,760 --> 00:49:01,680
agenda for our 15th anniversary.
The first Thursday was the

751
00:49:01,680 --> 00:49:05,490
actual 15th anniversary. Then we
had a Sunday in the middle, and

752
00:49:05,490 --> 00:49:10,650
we had a final Thursday, which
is episode 1500. And I decided

753
00:49:10,650 --> 00:49:14,370
to change the format, knowing
that donations will be large.

754
00:49:15,630 --> 00:49:18,600
And I thought it would spread
out over those three days. So

755
00:49:18,600 --> 00:49:21,120
instead of doing two breaks, we
did two and a half hours of

756
00:49:21,120 --> 00:49:24,180
show. And then we read for about
an hour and a half the first

757
00:49:24,180 --> 00:49:26,850
day, hour and a half the second
day, and I went back and I was

758
00:49:26,850 --> 00:49:30,360
looking at listening analytics.
And I could see the drop off was

759
00:49:30,360 --> 00:49:35,130
so dramatic, that I think people
who may be even we're listening

760
00:49:35,130 --> 00:49:38,550
to wait to hear their name or
their note or whatever, they

761
00:49:38,550 --> 00:49:41,580
might not have even heard it.
Now that's just a sample because

762
00:49:41,580 --> 00:49:45,660
all they have is stream
Satoshis. But I think if as long

763
00:49:45,660 --> 00:49:48,240
as you have a baseline, which I
have with the amount of data we

764
00:49:48,240 --> 00:49:51,810
have, you kind of got a good
idea. And so, you know, I made

765
00:49:51,810 --> 00:49:55,290
some decisions for our third
show based upon that. And here I

766
00:49:55,290 --> 00:49:59,280
was doing stuff that we're still
talking about 18 years later

767
00:49:59,280 --> 00:50:02,610
trying to figure You're out how
to implement it. Can it ever

768
00:50:02,610 --> 00:50:03,810
happen John Spurlock?

769
00:50:05,970 --> 00:50:08,070
I think we need to come up with
something that people do. I

770
00:50:08,070 --> 00:50:10,620
mean, if everyone used that
system right now, it would be

771
00:50:10,620 --> 00:50:13,860
amazing, right? So it's just
like getting something out there

772
00:50:13,860 --> 00:50:19,770
that people will adopt. And I
think the story behind events, I

773
00:50:19,770 --> 00:50:22,260
know, we're kind of going all
around here. But the one of the

774
00:50:22,260 --> 00:50:26,790
tags that's coming up, that I
proposed for the face six is a

775
00:50:26,790 --> 00:50:31,080
hopefully a very simple way for
just anyone out there like apps

776
00:50:31,110 --> 00:50:36,720
to send back trusted information
back to the podcaster. So if we

777
00:50:36,720 --> 00:50:41,910
take a step back, podcasting is
like broadcasting in a way, even

778
00:50:41,910 --> 00:50:44,220
though it's sort of you know,
there's feeds and all that if

779
00:50:44,220 --> 00:50:47,610
you take a step back, the
podcaster, is putting their

780
00:50:47,610 --> 00:50:51,600
creation out to the world. And
they're saying here, you know,

781
00:50:51,600 --> 00:50:55,350
just like a webpage your world
and it's on the internet, apps

782
00:50:55,350 --> 00:50:58,140
can go fetch it, and that's the
relationship, right? So it's a

783
00:50:58,140 --> 00:51:01,440
very broad castI sort of
relationship, if you look at the

784
00:51:01,830 --> 00:51:05,520
boxes and lines of it, right.
And so they are able to, and

785
00:51:05,520 --> 00:51:10,950
that's great. But there's no way
for the consumers of that the

786
00:51:10,950 --> 00:51:14,850
apps right now, the relationship
on that, and is pretty one way,

787
00:51:14,850 --> 00:51:18,750
it's like, thank you for this
content. I'll download it. And

788
00:51:18,750 --> 00:51:21,390
like as a side effect of
downloading it, you get some

789
00:51:21,390 --> 00:51:26,700
info. You know, Marco has a very
strong, you know, he has he has

790
00:51:26,850 --> 00:51:29,460
very strong principles of what
he like he thinks the right

791
00:51:29,460 --> 00:51:34,140
thing to do is, and when he's
fetching feeds, he's like, hey,

792
00:51:34,200 --> 00:51:36,330
I want to do right, by the
podcasters. I'm going to tell

793
00:51:36,330 --> 00:51:40,020
them how many people are
subscribed, right, for example,

794
00:51:40,200 --> 00:51:42,570
in the feeds, and that's great
info. I mean, that's something

795
00:51:42,570 --> 00:51:45,870
that you to your point, Adam,
you know, you do a baseline, and

796
00:51:45,870 --> 00:51:48,420
you say it's your went up or
went down or whatever. But

797
00:51:48,420 --> 00:51:52,590
people would love to get that
info, but he sticks it in a very

798
00:51:52,590 --> 00:51:55,260
forgettable channel, right? He
sticks it in the user agent,

799
00:51:55,740 --> 00:51:59,070
there's no way for him to even
if he wanted to do it, to send

800
00:51:59,070 --> 00:52:02,730
it. So I think the the events
tag was like meant to be

801
00:52:02,730 --> 00:52:06,750
literally just like an inbox,
right? It's like, here is a

802
00:52:07,110 --> 00:52:09,720
single channel. So we figure out
a way to get unforgivable

803
00:52:09,720 --> 00:52:13,380
requests in. And from there, we
can build these different

804
00:52:13,380 --> 00:52:18,810
payloads. So I've heard a ton of
different really good, really

805
00:52:18,810 --> 00:52:22,740
good ideas so far. So but
subscribers listens. That's

806
00:52:22,740 --> 00:52:24,030
obviously one of them. What

807
00:52:24,960 --> 00:52:28,770
I was, I was gonna ask you, what
is your, where's your focus

808
00:52:28,770 --> 00:52:32,760
going to be? And I asked this
specifically, because I just

809
00:52:32,760 --> 00:52:36,510
personally, don't feel very
motivated to help fix the

810
00:52:36,540 --> 00:52:40,500
dynamically insert inserted ad
business. I like what Dave said,

811
00:52:40,620 --> 00:52:44,460
which is, hey, this stuff is
breaking shit. So what is what

812
00:52:44,460 --> 00:52:47,940
is your driver? What do you what
would you like to achieve short

813
00:52:47,940 --> 00:52:48,690
term?

814
00:52:50,130 --> 00:52:52,830
I don't like to do anything. So
I'm lazy, right? So I just I

815
00:52:52,830 --> 00:52:58,620
just do this for a reason. And I
can't talk at like, in great

816
00:52:58,620 --> 00:53:01,470
detail about the reason but
let's say it like, so I had I

817
00:53:01,470 --> 00:53:04,500
had an interview on pod land a
while ago. And they were talking

818
00:53:04,500 --> 00:53:07,620
about op three, I think. But
that was the week that the I

819
00:53:07,620 --> 00:53:10,080
heart stuff came out. And so we
talked about that. And I think

820
00:53:10,080 --> 00:53:12,930
as as part of that I had a
comment like, hey, these players

821
00:53:12,930 --> 00:53:15,390
have this great information, but
I'm not holding my breath. And

822
00:53:15,390 --> 00:53:19,140
I'm sending it anywhere, anytime
soon. And that seemed like a

823
00:53:19,560 --> 00:53:22,680
pretty non controversial sort of
thing to say back then. But I

824
00:53:22,680 --> 00:53:23,130
got

825
00:53:24,360 --> 00:53:28,200
well, you you confuse me. So you
have a reason for this. But you

826
00:53:28,200 --> 00:53:33,870
you, you don't you don't want to
share that. Just the only thing

827
00:53:33,900 --> 00:53:36,660
that immediately makes me think
well hang on, I'm giving you all

828
00:53:36,660 --> 00:53:39,720
my data. What are you building
with my data, then is no

829
00:53:40,500 --> 00:53:44,010
different things to different
things. So yeah, so separate out

830
00:53:44,010 --> 00:53:49,650
op three from podcast events.
They're kind of sorry, I'm

831
00:53:49,650 --> 00:53:52,920
talking right now about podcast
events, which is, again, that's

832
00:53:52,920 --> 00:53:54,720
what that's what I'm doing. I
know

833
00:53:54,720 --> 00:53:57,870
what you do on your secret isn't
that's like the biggest known

834
00:53:57,870 --> 00:53:59,220
secret in the industry?

835
00:54:00,450 --> 00:54:03,030
Well, I think if you listen to
what you guys talked about in

836
00:54:03,030 --> 00:54:05,700
your in your show, too, I think
you know what, like, what's

837
00:54:05,700 --> 00:54:09,180
going on is messing with you.
But basically apps, it turns

838
00:54:09,180 --> 00:54:12,810
out, are very interested in
helping out this problem. And

839
00:54:12,810 --> 00:54:16,830
they are, they're willing to do
it. But they're tapping a bunch

840
00:54:16,830 --> 00:54:20,490
of people on the back and saying
like, how do we do this? And so

841
00:54:20,940 --> 00:54:23,670
my concern and what where I'm
coming from with all this is

842
00:54:23,670 --> 00:54:28,890
obviously not in any sort of
user privacy sort of backstop.

843
00:54:28,890 --> 00:54:32,460
Right. Ideally, we would this is
all summary information that

844
00:54:32,460 --> 00:54:34,590
would be sent. It's only
information that they already

845
00:54:34,590 --> 00:54:37,920
have. And they already give it
to podcasters at a at a summary

846
00:54:37,920 --> 00:54:40,980
level. And you know, there's
other administrative stuff that

847
00:54:40,980 --> 00:54:43,110
could go over this channel as
well. But our concern, my

848
00:54:43,110 --> 00:54:46,260
concern is that if we didn't
have something out there, like

849
00:54:46,260 --> 00:54:50,280
as a proposal as like the open
way to do it, as opposed to

850
00:54:50,669 --> 00:54:53,249
Yeah, it will get done in closed
walls. It's

851
00:54:53,250 --> 00:54:56,490
gonna be done point to point it
exactly. So I thought we need

852
00:54:56,490 --> 00:54:59,970
something. Yeah, exactly. It's
like and that makes a lot of

853
00:55:00,000 --> 00:55:02,490
sense, right? Because then they
can say, all right, like you can

854
00:55:02,490 --> 00:55:07,620
get stats from the Big Three
players. And that's enough. And

855
00:55:07,620 --> 00:55:11,250
I love the fact that, you know,
podcasting is not like that or

856
00:55:11,250 --> 00:55:14,190
has not been like that to date.
So if we can figure this out, I

857
00:55:14,190 --> 00:55:18,330
think I think people will be
willing to use it. But it's,

858
00:55:18,480 --> 00:55:22,140
it's also, it's also useful in a
variety of different contexts.

859
00:55:22,350 --> 00:55:25,620
So there is a tight rope, I
think, to some level. With

860
00:55:25,620 --> 00:55:28,980
events, it's like, hey, we now
we have this new channel, that

861
00:55:28,980 --> 00:55:33,270
is a trusted way for podcasters.
To get feedback from apps, you

862
00:55:33,270 --> 00:55:35,400
can think of a lot of
interesting stuff to send over

863
00:55:35,400 --> 00:55:38,280
there. And I think it's like
once it's like the namespace

864
00:55:38,280 --> 00:55:41,670
within a namespace thing, once
we establish that channel that

865
00:55:41,670 --> 00:55:45,060
everyone can trust, and I don't
know how Tech Tech you want to

866
00:55:45,060 --> 00:55:47,550
go, but we can talk about how
you can trust it all the way,

867
00:55:47,550 --> 00:55:50,970
then we can talk about the
payloads that go inside of it,

868
00:55:50,970 --> 00:55:53,580
right. And that's where I think,
Oh, here's the things I

869
00:55:53,580 --> 00:55:57,930
got one, I got one. I want one
to be a selfie of when what

870
00:55:57,930 --> 00:55:59,310
you're doing while you're
listening.

871
00:56:00,720 --> 00:56:03,210
Be the be real app. That's to be
real. There you go.

872
00:56:03,270 --> 00:56:06,900
Yeah, at this point in the show.
Yeah, the app could take a

873
00:56:06,900 --> 00:56:09,750
picture. Yeah, absolutely. I
mean, there's no bad ideas with

874
00:56:09,750 --> 00:56:12,630
this. It's just a channel that
doesn't exist right now. And

875
00:56:12,630 --> 00:56:15,840
honestly, the channel that does
exist is the email address. This

876
00:56:15,840 --> 00:56:19,260
is how people ping the
podcaster, they hunt for the

877
00:56:19,260 --> 00:56:22,410
email address, and they send
some inbound. And if you're

878
00:56:22,410 --> 00:56:25,290
smart, you filter all that out.
And it goes to spam. Right? So

879
00:56:25,290 --> 00:56:28,320
this is a, this is a mechanical
inbox, right? Where you can

880
00:56:28,320 --> 00:56:32,280
have, you can have structured
information coming back. And

881
00:56:32,280 --> 00:56:34,620
that works for you. Because you
have services that are

882
00:56:34,620 --> 00:56:38,130
presenting it to you. You could
even envision, like a lot of

883
00:56:38,130 --> 00:56:42,870
these are feed drops and stuff.
They're all about like, oh, you

884
00:56:42,870 --> 00:56:45,360
know, here's my offer to be on
your show, blah, blah, blah.

885
00:56:45,480 --> 00:56:48,600
That's all done with a with a
horrible email right now, right?

886
00:56:48,600 --> 00:56:52,860
But you can imagine, hey, I'll,
I'll send a structured request.

887
00:56:52,860 --> 00:56:56,340
And then on your side, you could
have a filter that says, once

888
00:56:56,340 --> 00:56:59,580
the request gets up to this
level from this venue, then I'll

889
00:56:59,580 --> 00:57:01,950
accept it right. So there's all
these things that we're doing

890
00:57:01,950 --> 00:57:05,430
manually in email right now,
that can use this channel, if it

891
00:57:05,430 --> 00:57:05,940
exists.

892
00:57:07,800 --> 00:57:11,640
Yeah, I like that a lot. What
will the transport mechanism be?

893
00:57:11,670 --> 00:57:14,070
I mean, we've talked about this,
I guess this doesn't matter.

894
00:57:14,070 --> 00:57:17,280
It's just a URL with an endpoint
to hit. Is that Is that what it

895
00:57:17,400 --> 00:57:17,580
was?

896
00:57:17,580 --> 00:57:20,520
I think, you know, it's gotta
be, it's gotta be JSON, right?

897
00:57:20,520 --> 00:57:21,060
It's got to be

898
00:57:23,910 --> 00:57:25,200
walked right into that.

899
00:57:26,700 --> 00:57:29,490
Right now, the idea is, it's
gotta be as simple as possible.

900
00:57:29,490 --> 00:57:33,600
So the proposal is literally
just a very simple JSON payload.

901
00:57:33,840 --> 00:57:35,790
But that's not the interesting
part. The interesting part is

902
00:57:35,790 --> 00:57:40,590
how you how you make sure that
that's, that's trustable. And

903
00:57:40,590 --> 00:57:42,480
fortunately, we don't have to
reinvent the wheel on that.

904
00:57:42,509 --> 00:57:47,369
So while you're using the Jade,
using the J WTS. Derive? It

905
00:57:47,369 --> 00:57:52,379
feels like a good approach to
that. And my question around. So

906
00:57:52,379 --> 00:57:56,249
if I understand the spec, it's
it's just a post body is just a

907
00:57:56,249 --> 00:58:05,819
JSON posted body? With, with the
J WT with the correct. With the

908
00:58:05,819 --> 00:58:08,789
correct add on with a column for
verbs, I'm not sure what those

909
00:58:08,789 --> 00:58:13,229
things are. In that, that you
that you constructed the so

910
00:58:13,259 --> 00:58:16,829
where are the site? Where are
the keys coming? Getting

911
00:58:16,829 --> 00:58:21,569
assigned at is that coming from?
I mean, like how if I'm, if I'm

912
00:58:23,369 --> 00:58:27,359
in days, okay, index, and I'm
gonna open up an endpoint for an

913
00:58:27,359 --> 00:58:32,189
inbox URL, how, how do I go
about do I need to give out keys

914
00:58:32,189 --> 00:58:33,809
to everybody I want to
authorize.

915
00:58:35,340 --> 00:58:39,180
So you would be on this site as
the podcast index, you probably

916
00:58:39,180 --> 00:58:42,600
want to be the sender, right? So
you want to send information I

917
00:58:42,600 --> 00:58:45,240
would be receiving the play, I
would be a receiver, I want to

918
00:58:45,240 --> 00:58:48,750
have a receiver endpoint for
let's just say our feed for your

919
00:58:48,750 --> 00:58:52,050
feed. Okay, so you set up a
endpoint, some sort of HTTP

920
00:58:52,050 --> 00:58:54,930
thing that listens, that can be
in Rust, or whatever you want to

921
00:58:54,930 --> 00:58:56,520
be? And

922
00:58:56,760 --> 00:59:00,870
you mocking me, John? I think so
too. I felt a lot. I feel very,

923
00:59:01,380 --> 00:59:03,390
now we're all going to be rust
developers at some point. I'm

924
00:59:03,390 --> 00:59:05,220
just You're, you're ahead of me
a little bit.

925
00:59:05,310 --> 00:59:07,170
That's what they've been telling
us for seven years. So.

926
00:59:08,610 --> 00:59:11,130
But um, yeah, you just set up an
endpoint just like any of your

927
00:59:11,130 --> 00:59:14,310
other API endpoints, and it
received JSON. So that's pretty

928
00:59:14,310 --> 00:59:18,000
easy. The tricky part is looking
at the authorization header and

929
00:59:18,930 --> 00:59:23,880
checking the signature. Now the
signature is based on URLs. So

930
00:59:23,880 --> 00:59:27,480
the sender when it sends the
info, it signs it with something

931
00:59:28,140 --> 00:59:32,370
that lives on a URL that they
own. So let's say Apple podcasts

932
00:59:32,370 --> 00:59:36,150
is sending you information. The
URL is actually in as part of

933
00:59:36,150 --> 00:59:38,550
the signature and it says like
this is coming from

934
00:59:38,550 --> 00:59:43,830
podcast.apple.com/keys.json or
whatever. So you see that it's

935
00:59:43,830 --> 00:59:47,160
signed with that. And then you
can decide and everyone can

936
00:59:47,160 --> 00:59:50,490
decide based on your policy,
like, whether you trust them or

937
00:59:50,490 --> 00:59:54,600
not. And you can look at what
what typically happens is Apple

938
00:59:54,600 --> 00:59:58,320
podcasts will on their support
page be like, Oh, this is our

939
00:59:58,350 --> 01:00:01,140
keys dot JSON file. If you see
stuff coming from this URL.

940
01:00:01,140 --> 01:00:04,950
That's us. And then you can have
a What's great about this is

941
01:00:04,950 --> 01:00:07,080
there's no meetings involved,
right? Like, you don't have to

942
01:00:07,080 --> 01:00:08,340
set up any sort of initial.

943
01:00:08,880 --> 01:00:11,310
That's my kind of business. No
meetings.

944
01:00:11,820 --> 01:00:16,590
Yeah, this is my mantra. But um,
you know, it's allows different

945
01:00:16,590 --> 01:00:19,440
people that have different
policies. So you could say, you

946
01:00:19,440 --> 01:00:21,120
know, if you're very
conservative, you can say only

947
01:00:21,120 --> 01:00:24,810
trust things that come from
Apple podcasts, but someone like

948
01:00:25,200 --> 01:00:28,260
podcasts index would probably
want to support you know, the

949
01:00:28,260 --> 01:00:30,990
longtail of everyone out there
and see what everyone's sending.

950
01:00:31,140 --> 01:00:34,560
So it's all based on a URL,
Apple are actually already does

951
01:00:34,560 --> 01:00:39,900
this for their that they're two
different API's that they had

952
01:00:39,900 --> 01:00:43,950
the App Store notifications and
put in their identity service.

953
01:00:44,310 --> 01:00:47,430
So it is kind of a solved
problem, like how to deal with

954
01:00:47,790 --> 01:00:50,850
authenticating people coming
from any random place on the

955
01:00:50,850 --> 01:00:53,580
internet and make sure that that
identity is stable over time. So

956
01:00:53,580 --> 01:00:56,550
it's the same sort of thing. I
it's not, you know, you have to

957
01:00:56,550 --> 01:01:00,000
do a one time setup on the
sender side, but on the receiver

958
01:01:00,000 --> 01:01:03,060
side, on your side, you just
need to write the code once and

959
01:01:03,060 --> 01:01:06,600
then decide in your if
statement, like, do I want to

960
01:01:06,840 --> 01:01:09,780
ingest further things that come
from this URL, and you could

961
01:01:09,780 --> 01:01:12,630
even put them in purgatory to
start out, you could say, I'll

962
01:01:12,630 --> 01:01:15,990
save the data, but I won't
process it until I look up this

963
01:01:15,990 --> 01:01:17,730
URL and see what's up with it.

964
01:01:19,230 --> 01:01:23,280
Yeah, makes purchases. So
there's, there's a, there's a

965
01:01:23,310 --> 01:01:27,750
there's a public URL somewhere
that lists essentially a public

966
01:01:27,750 --> 01:01:31,560
key. And they're gonna sign
there, you're gonna sign the JD

967
01:01:31,560 --> 01:01:35,070
btw, Senator, you can do it, you
can author you can authenticate

968
01:01:35,070 --> 01:01:40,800
it by by checking the signature
matches their public key, and

969
01:01:40,830 --> 01:01:44,070
then decide whether or not you
want to trust that entity or

970
01:01:44,070 --> 01:01:49,200
not. So here's let me give you a
real world scenario of something

971
01:01:49,200 --> 01:01:53,700
that is needed. And it's not
necessarily different than what

972
01:01:53,700 --> 01:01:56,520
we talked about just a second
ago. But maybe there's a little

973
01:01:56,520 --> 01:02:01,620
bit more flavor to it here. The
one thing that we talked about

974
01:02:01,620 --> 01:02:05,940
when whenever I talked to people
that want to use the index, for

975
01:02:05,940 --> 01:02:09,030
like, bigger things, you know,
if there's an accompany that

976
01:02:09,030 --> 01:02:12,750
wants to use the index for, you
know, putting podcast data into

977
01:02:12,750 --> 01:02:16,140
some device or something like
that. One of the things that we

978
01:02:16,140 --> 01:02:20,640
always that I always ask them
is, you know, hey, you know,

979
01:02:20,640 --> 01:02:26,040
this is free, the index is free,
use it, you know, have everyone.

980
01:02:26,730 --> 01:02:29,820
And, you know, if, if you're if
you make a lot of money off of

981
01:02:29,820 --> 01:02:34,080
it, consider a donation. But
also, part of the value that

982
01:02:34,380 --> 01:02:38,850
would be great to get back is,
can you send us back usage data,

983
01:02:39,450 --> 01:02:42,960
you know, anonymized or hair
summary, your I don't care what

984
01:02:42,960 --> 01:02:48,810
it is. I just need usage data.
Because what one thing that the

985
01:02:48,810 --> 01:02:54,120
index lacks severely is real
world data about who is

986
01:02:54,120 --> 01:02:56,880
listening to what shows. And
this is, this is a problem

987
01:02:56,880 --> 01:03:00,840
across all of podcasting. It's
pretty much what you described

988
01:03:00,840 --> 01:03:06,090
earlier, you have tons of
podcast apps, all with peep with

989
01:03:06,090 --> 01:03:11,520
dedicated user bases, the
listening to shows, and none of

990
01:03:11,520 --> 01:03:16,140
that data is coming back into
these, quote unquote, rankers

991
01:03:16,620 --> 01:03:18,990
except for the one that fountain
publishes,

992
01:03:19,590 --> 01:03:24,030
yes, that's other than that,
everybody is just like, you

993
01:03:24,030 --> 01:03:27,540
know, you have this void of this
void of information. So what you

994
01:03:27,540 --> 01:03:34,440
end up with is silos of, of, of
data, where you have, like, if I

995
01:03:34,440 --> 01:03:40,650
go into if I go into overcast
and, and hit where, okay, I'm

996
01:03:40,650 --> 01:03:43,500
gonna go, I want to go find a
show. And it comes up with their

997
01:03:43,500 --> 01:03:46,980
trending list, you know, the
there, the markers page that has

998
01:03:46,980 --> 01:03:49,590
all the different popular shows
that are currently popular in

999
01:03:49,590 --> 01:03:54,840
his system. It's all dominated
by things like accidental tech,

1000
01:03:54,840 --> 01:03:58,860
and but Is that wrong? No, no,
I'm not saying that's wrong. No,

1001
01:03:58,860 --> 01:04:02,130
I'm totally not saying at all
that that's wrong. What I'm

1002
01:04:02,130 --> 01:04:06,600
saying is, it would be really
nice, like, that's going to be

1003
01:04:06,600 --> 01:04:10,830
the case for his app, then
there's going to be fountains

1004
01:04:11,070 --> 01:04:14,520
list is going to look different.
The podcasts indexes list is

1005
01:04:14,520 --> 01:04:17,760
going to look different, like no
agenda is going to be up there,

1006
01:04:17,760 --> 01:04:20,940
podcasting. 2.0 is going to be
up there. So if you took all of

1007
01:04:20,940 --> 01:04:26,100
that data in, in aggregated it
together, you would smooth out

1008
01:04:26,100 --> 01:04:29,730
all of those silos and you would
have a much better view of

1009
01:04:29,730 --> 01:04:32,910
what's actually popular across
all of podcasting

1010
01:04:33,149 --> 01:04:37,259
am going to ask you and to what
end this is, this is the benefit

1011
01:04:37,259 --> 01:04:37,619
who

1012
01:04:38,280 --> 01:04:42,720
will because we're like, podcast
index. We're not. We're an

1013
01:04:42,720 --> 01:04:46,920
index, we're supposed to be
like, I want neutral data. I

1014
01:04:46,920 --> 01:04:50,940
don't want data that's been
affected by the fact that that

1015
01:04:50,940 --> 01:04:57,720
we did our show is our show is
artificially inflated in our own

1016
01:04:57,720 --> 01:04:58,560
statistics,

1017
01:04:58,950 --> 01:05:03,510
right. So our Are you saying we
would want to possibly integrate

1018
01:05:03,510 --> 01:05:09,570
some data from OPI three, four
as an example, or this adventure

1019
01:05:09,570 --> 01:05:12,540
data or this events data? I
mean, it's really no different

1020
01:05:12,540 --> 01:05:20,460
than then basically the Facebook
spy SDK except you ask people to

1021
01:05:20,490 --> 01:05:23,940
for permission to give the
information. And it's kind of

1022
01:05:23,940 --> 01:05:28,890
the quote unquote, ultimate
world where you can determine

1023
01:05:28,920 --> 01:05:31,260
what you want to share with who
is that what I'm hearing?

1024
01:05:31,860 --> 01:05:35,400
Yeah, but that's pretty much
exactly because you have, like

1025
01:05:35,400 --> 01:05:38,970
what John said a while ago,
that, you know, the the apps

1026
01:05:38,970 --> 01:05:43,410
don't peep. People act like the
apps don't want to give any data

1027
01:05:43,410 --> 01:05:46,440
away. And that's not the case,
like, like he mentioned, Marco

1028
01:05:46,440 --> 01:05:50,310
gives this away in the user
agent. But that's the so it's

1029
01:05:50,310 --> 01:05:53,430
not like it's some, I don't ever
want to give you my data. It's

1030
01:05:53,430 --> 01:05:56,760
not like that really is just
that there's no, there's no

1031
01:05:56,760 --> 01:06:01,920
decent way to do it in a private
way. That's not gross, and or

1032
01:06:01,920 --> 01:06:06,240
weird. And so if there's this
events tag, here's, here's what

1033
01:06:06,240 --> 01:06:09,750
I'm really saying. I want to
immediate, I want to immediately

1034
01:06:09,750 --> 01:06:13,050
take the events tag and
bastardize it beyond all belief,

1035
01:06:13,680 --> 01:06:17,520
to where it is to where I want
to know, I want to have an open

1036
01:06:17,520 --> 01:06:21,030
endpoint to where people can
just send me data without ever

1037
01:06:21,030 --> 01:06:22,620
even being in a feed. Like,
well,

1038
01:06:22,620 --> 01:06:26,700
that's Oh, without this feed,
either. Yeah. But then make a

1039
01:06:26,700 --> 01:06:30,510
decision. Yeah, but you Yeah, I
don't know, to me, I'm still all

1040
01:06:30,510 --> 01:06:33,540
about the podcaster should be in
control of that, like where the

1041
01:06:33,570 --> 01:06:36,030
their stats are going. But I
could, I can see this is not

1042
01:06:36,030 --> 01:06:37,260
stuff that might be useful.

1043
01:06:37,710 --> 01:06:40,500
This is not stats, though, John,
like this would be here's,

1044
01:06:40,710 --> 01:06:46,050
here's what I'm totally going
off the rails. The, here's what

1045
01:06:46,050 --> 01:06:54,720
I want, I want and I want
Buzzsprout. To periodically, I

1046
01:06:54,720 --> 01:07:01,860
want them to somehow publish or
send out a list of all the shows

1047
01:07:01,860 --> 01:07:06,690
on their system that are
currently popular. And I want

1048
01:07:07,320 --> 01:07:11,250
overcast to do the same thing.
And I want pod verse to do the

1049
01:07:11,250 --> 01:07:14,550
same thing. And I want rss.com
to do same thing, but in blue,

1050
01:07:14,550 --> 01:07:20,640
but I want everybody to somehow
publish or send around lists of

1051
01:07:20,670 --> 01:07:24,270
all of the shows that are
popular on their own systems.

1052
01:07:24,420 --> 01:07:27,450
And this is not privacy in any
way. This is just purely just a

1053
01:07:27,450 --> 01:07:33,180
list of popular podcast. That
way, we all have a real ranking

1054
01:07:33,180 --> 01:07:36,870
system to say, not ranking in
the gross sense where you're

1055
01:07:36,870 --> 01:07:39,030
like, you know, this one's
better than this other one, but

1056
01:07:39,030 --> 01:07:43,530
like actual usage, where it's
like, okay, on for my stats

1057
01:07:43,530 --> 01:07:49,620
within rss.com, the these 500
shows were the ones that ranked

1058
01:07:49,650 --> 01:07:54,360
top to bottom by most downloads.
That way, we can amalgamate that

1059
01:07:54,360 --> 01:07:59,070
data into one big ranking list
that everybody can share. And we

1060
01:07:59,070 --> 01:08:03,450
don't keep having to go back to
Apple and Spotify in scraping

1061
01:08:03,450 --> 01:08:08,370
their data. And to try to find
out what shows are actually

1062
01:08:08,370 --> 01:08:10,560
getting any listening at all.

1063
01:08:10,920 --> 01:08:14,670
I you're talking to someone that
loves lists. So like I love you

1064
01:08:14,670 --> 01:08:18,060
know, Letterman top 10 I've been
I'd actually do a ton of lists,

1065
01:08:18,090 --> 01:08:21,060
you know, the stupid Livewire
things? That's, that's a list

1066
01:08:21,060 --> 01:08:24,510
right of the top. I love lists.
So I probably love lists more

1067
01:08:24,510 --> 01:08:28,920
than you do. But I don't see to
me the ranking, like having some

1068
01:08:28,920 --> 01:08:33,690
massive ranking list across all
podcast is sort of uncompelled.

1069
01:08:33,690 --> 01:08:38,280
To me, I'm not sure who that
would be for, I'm not sure that

1070
01:08:38,310 --> 01:08:41,460
that would be podcasters would
love that maybe the ones that

1071
01:08:41,850 --> 01:08:44,460
are rising in the list would
love it for a few days until

1072
01:08:44,460 --> 01:08:47,880
they start falling. But I don't
see that as being like a target

1073
01:08:47,880 --> 01:08:51,330
that would get people excited
about hitting right, except for,

1074
01:08:51,330 --> 01:08:55,440
you know, extreme data nerds.
Like I think like Adam was

1075
01:08:55,440 --> 01:08:58,200
saying it's more of a relative
thing, right? It's like, here's

1076
01:08:58,200 --> 01:09:02,220
what I had yesterday. And here's
what I have today. And if you

1077
01:09:02,220 --> 01:09:05,520
can get that from a variety of
players, and the way we do that,

1078
01:09:05,520 --> 01:09:08,430
and the open world is to
establish a protocol for doing

1079
01:09:08,430 --> 01:09:11,790
that. I think then you have a
baseline in among yourself or

1080
01:09:11,790 --> 01:09:12,750
your own little group

1081
01:09:12,780 --> 01:09:16,770
ultimately from from it from a
data analytics perspective, the

1082
01:09:16,770 --> 01:09:21,960
only thing that messes it all up
is this incessant necessity and

1083
01:09:21,990 --> 01:09:26,820
obsession to equate download
with a person and a listen,

1084
01:09:26,850 --> 01:09:30,150
that's the problem. Otherwise,
all this stuff is working pretty

1085
01:09:30,150 --> 01:09:34,710
well. You know, it's like I'm,
I'm looking at all kinds of

1086
01:09:34,710 --> 01:09:37,170
different stats. And as long as
I don't care about the actual

1087
01:09:37,170 --> 01:09:39,720
number, and try to think that's
how many people are listening,

1088
01:09:39,720 --> 01:09:44,730
which is the entire fallacy,
because there's 10,000 podcasts

1089
01:09:44,730 --> 01:09:50,340
now using value for value. You
know, and using those apps. It's

1090
01:09:50,340 --> 01:09:54,990
a very successful 10,000 app
group success is there is

1091
01:09:55,050 --> 01:09:59,640
there's no necessity for those
communities. For it to be any

1092
01:09:59,640 --> 01:10:02,760
bigger They're already seeing a
mix. Yeah, they're satisfying

1093
01:10:02,760 --> 01:10:04,290
what they need to satisfy.

1094
01:10:04,350 --> 01:10:07,590
And you see graphs like that's
really what will grill will give

1095
01:10:07,590 --> 01:10:10,260
you value is like, you see
whether that trend line is going

1096
01:10:10,260 --> 01:10:12,960
up or like, hey, they're dropped
off at this point. And that's,

1097
01:10:13,200 --> 01:10:16,410
that's something that Opie three
or these other systems can do

1098
01:10:16,440 --> 01:10:19,470
for each individual podcaster.
But I don't see it as like a

1099
01:10:19,470 --> 01:10:24,240
huge goal to like, do that for
the entire podcast world. I'm

1100
01:10:24,240 --> 01:10:25,560
not sure who that would benefit.

1101
01:10:25,830 --> 01:10:29,820
What What I will say just just
because I look at different

1102
01:10:29,820 --> 01:10:34,860
podcasts, and this is in the, in
the lb stat system, or in

1103
01:10:34,860 --> 01:10:39,870
contracts, very interesting to
see that on podcasting 2.0, we

1104
01:10:39,870 --> 01:10:44,610
make much more, we have much
more income on boosts compared

1105
01:10:44,610 --> 01:10:48,990
to streaming amounts. On no
agenda. It's the inverse, we

1106
01:10:48,990 --> 01:10:54,300
have more income from streaming
sites than from boosts. And the

1107
01:10:54,360 --> 01:10:58,140
end, the most beautiful thing is
on no agenda, where we don't

1108
01:10:58,140 --> 01:11:02,190
have booster grams integrated
yet into the content, you see a

1109
01:11:02,190 --> 01:11:07,290
drop off in both donation
segments, podcasting 2.0 During

1110
01:11:07,290 --> 01:11:12,060
the donation segment, our income
actually goes up. Which is also

1111
01:11:12,060 --> 01:11:15,210
partially because we're doing it
live. And it's being solicited.

1112
01:11:17,100 --> 01:11:20,670
This, as long as we don't have
to worry about how many people

1113
01:11:20,670 --> 01:11:23,760
it is. And now I would love to
have some I mean, I'd love to

1114
01:11:23,760 --> 01:11:26,790
have all kinds of op three data
in there. I'm just saying as a

1115
01:11:26,790 --> 01:11:34,470
podcaster. Yeah, I'm different
because I'm not using inserted

1116
01:11:34,470 --> 01:11:38,610
advertising. I mean, I have more
data and excitement in front of

1117
01:11:38,610 --> 01:11:40,380
me than I've ever seen.

1118
01:11:41,460 --> 01:11:44,340
Yeah, exactly. But you saw the
OP through and I love the fact

1119
01:11:44,340 --> 01:11:47,400
that your shows are on op three
right now. Because it's a great

1120
01:11:47,400 --> 01:11:51,210
like way to see the just how
many different apps people

1121
01:11:51,210 --> 01:11:54,480
listen to your show on? Yeah,
very, very interesting. Totally.

1122
01:11:54,930 --> 01:11:56,610
Ton of Pocket Casts, right. I

1123
01:11:56,670 --> 01:11:59,550
like number three on the list or
something. Yeah, phrase Yeah,

1124
01:11:59,550 --> 01:12:00,750
phrase Exactly. And

1125
01:12:00,750 --> 01:12:03,540
I'll you know, as I'm working
through the three, I like, I'll

1126
01:12:03,540 --> 01:12:07,350
give you a nice way to look at
that later. But you would love I

1127
01:12:07,350 --> 01:12:09,870
think I don't wanna put words in
your mouth. I think as a

1128
01:12:09,870 --> 01:12:13,380
podcaster, you would love to see
the same sort of just

1129
01:12:13,380 --> 01:12:16,110
generalized, like, here's where
they trailed off. Like, here's

1130
01:12:16,140 --> 01:12:18,780
how many listens from Pocket
Casts, right? If they had a way

1131
01:12:18,780 --> 01:12:21,120
to give that to you, and then
you don't have to use that for

1132
01:12:21,120 --> 01:12:24,390
any decision making other than
what you're using it for now,

1133
01:12:24,390 --> 01:12:28,650
right? Which is kind of to give
you a sense of like, okay, like

1134
01:12:28,680 --> 01:12:31,740
my listeners on these types of
apps. Well, here's what I'm

1135
01:12:31,740 --> 01:12:34,080
gonna get a certain wave, but I
actually have more info now.

1136
01:12:34,110 --> 01:12:37,110
Here's what I'm gonna do. Cuz
Thank you. I just wrote a note

1137
01:12:37,110 --> 01:12:38,850
to myself a programming note.

1138
01:12:40,410 --> 01:12:41,160
Learn rust.

1139
01:12:44,220 --> 01:12:51,120
snappy? No, actually, I'm going
to talk about I'm going to tell

1140
01:12:51,120 --> 01:12:55,680
all the Pocket Cast listeners to
go go over there and kindly

1141
01:12:55,680 --> 01:12:59,070
request some podcasting 2.0
features from their open source

1142
01:12:59,070 --> 01:12:59,430
app.

1143
01:13:00,570 --> 01:13:02,100
Why no congratulations, by

1144
01:13:02,100 --> 01:13:05,370
the way. Yeah, you guys and
congratulations on getting

1145
01:13:05,460 --> 01:13:08,670
getting that was a quick merge
to that didn't take long.

1146
01:13:09,299 --> 01:13:11,429
What is this? I don't know. What
are we talking about?

1147
01:13:12,900 --> 01:13:17,010
Real trivia, but there's a new
on Apple platforms. There's a

1148
01:13:17,010 --> 01:13:22,350
new official way to send down.
Oh, yes, yes, yeah. So I just

1149
01:13:22,350 --> 01:13:24,840
had I had this lightbulb moment
that went off the other morning.

1150
01:13:24,840 --> 01:13:27,990
I'm like, Oh, I could just make
the change in the

1151
01:13:31,290 --> 01:13:32,820
car. They merged your car

1152
01:13:32,820 --> 01:13:36,090
commercial. So it'll go out in
the end of November? I think so

1153
01:13:36,150 --> 01:13:39,570
I think they're the first ones
to use it. Because Apple podcast

1154
01:13:39,570 --> 01:13:44,430
still doesn't even use it. So
I'm free to do you know, free

1155
01:13:44,430 --> 01:13:45,360
development work.

1156
01:13:46,770 --> 01:13:49,740
After all, he is he is semi
retired from the corporate

1157
01:13:49,740 --> 01:13:52,080
research fully retired from the
corporate life.

1158
01:13:52,830 --> 01:13:56,040
But it is, it is a good example
to show now too, because their

1159
01:13:56,070 --> 01:13:59,100
their codebase is actually
really good. And it's a good

1160
01:13:59,100 --> 01:14:03,450
example. So as in last in less
people, some people learn via

1161
01:14:03,450 --> 01:14:06,600
blog posts or documentation, but
sometimes it's just easy to say,

1162
01:14:06,990 --> 01:14:09,330
look at this file, look what
they do here. It's not that, you

1163
01:14:09,330 --> 01:14:12,240
know, it's not that much work.
So I thought that was really

1164
01:14:12,240 --> 01:14:14,760
cool them to go ahead and merge
it

1165
01:14:15,090 --> 01:14:17,880
to Hell yeah, I didn't even
realize this. That's fantastic.

1166
01:14:17,880 --> 01:14:18,780
So we need more.

1167
01:14:19,500 --> 01:14:21,660
Yeah, it's nice to see that
they're living the that they're

1168
01:14:21,660 --> 01:14:24,510
like living the open source
lifestyle, instead of just

1169
01:14:24,510 --> 01:14:27,420
saying, Oh, here's the code and
never really interacting with

1170
01:14:27,420 --> 01:14:30,450
it. They actually, they're
actually being stewards. You

1171
01:14:30,450 --> 01:14:31,590
know, that's good to see.

1172
01:14:31,650 --> 01:14:34,020
That's really good. Anything is
pure client side from the

1173
01:14:34,020 --> 01:14:37,980
podcast namespace tags. That
would be a good like, first PR

1174
01:14:37,980 --> 01:14:41,280
for for that project. Because
they Oh, they only open really

1175
01:14:41,280 --> 01:14:44,820
the client side. Right. So
anything that requires any sort

1176
01:14:44,820 --> 01:14:49,050
of server interaction is going
to be more difficult, but things

1177
01:14:49,050 --> 01:14:50,280
like chapters even

1178
01:14:52,320 --> 01:14:56,310
there's, like fun, like the
funding tag did yeah. Stuff like

1179
01:14:56,310 --> 01:14:57,780
that. That's just you I work you
know.

1180
01:14:58,200 --> 01:15:00,630
Exactly, exactly. So yeah,
that's I thought that was

1181
01:15:00,630 --> 01:15:01,470
really, really cool.

1182
01:15:01,830 --> 01:15:05,490
Did you look around in? I
haven't looked at the code base

1183
01:15:05,490 --> 01:15:09,210
at all? Did you look around
enough to see whether or not? Is

1184
01:15:09,210 --> 01:15:14,490
it a pure client side download
and download and parse style

1185
01:15:14,490 --> 01:15:19,140
system? Or is it getting your
feed info from or the feeds

1186
01:15:19,140 --> 01:15:22,890
being parsed? And then all the
broken apart feed elements

1187
01:15:22,920 --> 01:15:25,560
handed back to the app through
their server side?

1188
01:15:26,070 --> 01:15:28,470
Well, as we established, I'm
lazy. So I did not look through

1189
01:15:28,470 --> 01:15:30,420
the entire No, but

1190
01:15:32,910 --> 01:15:36,210
that means this is a bad this is
a lazy battle, because I was

1191
01:15:36,210 --> 01:15:38,670
hoping you would tell me so I
don't have to go look myself.

1192
01:15:38,910 --> 01:15:43,050
Yeah, lazy understands lazy
here. Yes, yes, I do know,

1193
01:15:43,080 --> 01:15:45,720
having gone back and forth with
someone else working through a

1194
01:15:45,720 --> 01:15:50,100
podcast and Pocket Casts issue.
I do, it does look like most of

1195
01:15:50,100 --> 01:15:53,610
their stuff is server side. So
even if you put in a custom URL,

1196
01:15:54,150 --> 01:15:57,300
there, their backend actually
parses that. So it's not

1197
01:15:57,300 --> 01:16:00,690
something that's on the client
side, Apple podcast actually is

1198
01:16:00,690 --> 01:16:03,780
old school, they do if you put
in a custom URL, like they will

1199
01:16:03,780 --> 01:16:07,590
hit it from the client app, even
if their servers blow up. So

1200
01:16:07,590 --> 01:16:10,710
then, so that's kind of a
different model. But yeah, so

1201
01:16:10,710 --> 01:16:14,010
anything like chapters, ideally,
you probably do want to do that

1202
01:16:14,010 --> 01:16:18,960
on a central server, do it once,
but I don't know you, there's

1203
01:16:18,960 --> 01:16:22,110
some things that can be done
there. Or maybe we have an open

1204
01:16:22,110 --> 01:16:25,530
source back end for Pocket
Casts, but just these, it's like

1205
01:16:25,530 --> 01:16:27,510
a gradient, right, there's some
of these things that we can get

1206
01:16:27,510 --> 01:16:30,060
in there that are QuicKutz. And
some that are going to take a

1207
01:16:30,060 --> 01:16:33,810
little longer to, to get in
there. But the fact that Pocket

1208
01:16:33,810 --> 01:16:38,970
Casts is still such a big deal.
And it's open, that's like

1209
01:16:38,970 --> 01:16:39,720
really exciting.

1210
01:16:42,390 --> 01:16:47,550
On the on the on the advanced
tag, and these really good that

1211
01:16:47,550 --> 01:16:51,780
you put in a proof of concept
working, working back end for

1212
01:16:51,780 --> 01:16:55,980
that, because this is very much
the type of of tag that needs

1213
01:16:55,980 --> 01:17:01,140
working code to people can, can
write against these these sorts

1214
01:17:01,140 --> 01:17:07,440
of things that are this is a,
this is less of a tag in more of

1215
01:17:07,440 --> 01:17:12,450
a I don't know what you would
call it like a like a, a

1216
01:17:12,450 --> 01:17:15,840
framework for how to do a thing.
And whenever you have something

1217
01:17:15,840 --> 01:17:18,930
that's that conceptual, you
really you really had to put

1218
01:17:18,930 --> 01:17:21,390
feet on it, or else everybody's
just gonna, their eyes are gonna

1219
01:17:21,390 --> 01:17:23,880
glaze over, and they're not
going to do anything exact. So

1220
01:17:23,940 --> 01:17:27,240
yeah, I think that's that's the
way I mean, just like a piece,

1221
01:17:27,240 --> 01:17:29,670
right? I mean, you can propose
it all day long. But unless you

1222
01:17:29,670 --> 01:17:32,760
have some in it, unless you just
build it, people are not going

1223
01:17:32,760 --> 01:17:35,880
to do anything. So I think
that's definitely

1224
01:17:35,880 --> 01:17:38,910
open for proposals, like if you
need like, if you go through it

1225
01:17:38,940 --> 01:17:42,480
as a as the sender or the
receiver. And it's not clear

1226
01:17:42,480 --> 01:17:44,820
about something or it's like,
Hey, I would love something to

1227
01:17:44,820 --> 01:17:47,340
test this. Because that's the
other thing, you get something

1228
01:17:47,340 --> 01:17:50,040
implemented. It's like, Who do I
talk to? Because no one speaks

1229
01:17:50,040 --> 01:17:55,110
the language yet. I do have I do
have, I think a tester for the

1230
01:17:55,500 --> 01:17:57,960
sender side. So if you're an
app, and you want to send

1231
01:17:57,960 --> 01:18:00,690
something to an endpoint, like I
have an endpoint that will

1232
01:18:01,050 --> 01:18:05,160
validate your, your payload, but
I don't think I have a test yet.

1233
01:18:05,160 --> 01:18:07,950
If you're a server, and you're
looking for just like, What

1234
01:18:07,950 --> 01:18:10,380
would app calls look like? So I
could definitely get that in

1235
01:18:10,380 --> 01:18:10,530
there

1236
01:18:10,530 --> 01:18:17,280
as well. Can I kind of raise my
hand? Sure. So here's here's a

1237
01:18:17,280 --> 01:18:22,140
successful formula. Thank you.
Here's a successful formula is

1238
01:18:22,260 --> 01:18:28,290
let's come up with an event. I
don't know how he's feeling he's

1239
01:18:28,290 --> 01:18:31,170
been rather quiet. I hope he's
okay. But Stephen B is the kind

1240
01:18:31,170 --> 01:18:38,940
of guy who can really quickly
whip up an event to jam into one

1241
01:18:38,940 --> 01:18:42,930
of my jam and into the no agenda
feed. And let's test it with a

1242
01:18:42,930 --> 01:18:46,080
real audience. Because you know,
no agenda nation, man, you can

1243
01:18:46,080 --> 01:18:47,160
get them do anything.

1244
01:18:48,840 --> 01:18:50,640
But it may not work in dog
catcher though.

1245
01:18:52,560 --> 01:18:56,100
I'm on your side, J S. I'm
trying to help your ship man's

1246
01:18:56,100 --> 01:18:56,280
like,

1247
01:18:57,630 --> 01:19:00,210
Hey, this is backwards
compatible with podcast. 1.0.

1248
01:19:00,210 --> 01:19:00,870
I'm like, except

1249
01:19:05,340 --> 01:19:08,460
that's not 1.0 That's like 0.9
So let's just be fair.

1250
01:19:10,230 --> 01:19:12,660
I see it a bunch and Opie three
actually, people are still using

1251
01:19:12,660 --> 01:19:12,870
it.

1252
01:19:13,139 --> 01:19:18,629
Yeah. Oh, you know, it was quite
a number of, of people who, who

1253
01:19:18,659 --> 01:19:23,009
ultimately wound up switching.
So weird, man. It's like, it's

1254
01:19:23,819 --> 01:19:26,639
kind of what what's up with that
Dev, but it just wasn't quite

1255
01:19:26,909 --> 01:19:28,859
wasn't quite gelling. Somehow.
He didn't quite,

1256
01:19:29,099 --> 01:19:32,069
but I totally agree with you.
Anyone that wants to implement

1257
01:19:32,069 --> 01:19:36,359
either side? Yeah, let's, let's
run with some scissors here. And

1258
01:19:36,839 --> 01:19:39,149
there's nothing there's nothing
more that flushes out like, Oh,

1259
01:19:39,149 --> 01:19:41,909
this is actually difficult. Or,
you know, this doesn't make

1260
01:19:41,909 --> 01:19:46,379
sense. Other than working code,
ultimately. And I think once you

1261
01:19:46,379 --> 01:19:48,749
have a straw man out there, then
it's like it focuses the

1262
01:19:48,749 --> 01:19:51,809
conversation on like, oh, what
would your this secure all that

1263
01:19:51,809 --> 01:19:54,689
kind of stuff. The only thing I
would mention, Adam is that it's

1264
01:19:54,689 --> 01:19:58,649
is a server to server protocol.
So whoever sending this info, it

1265
01:19:58,649 --> 01:20:01,949
can't be a client app. So it has
to be something where the client

1266
01:20:01,949 --> 01:20:04,679
app sends it to it some sort of
server and the server has to

1267
01:20:04,679 --> 01:20:05,399
send it over.

1268
01:20:05,850 --> 01:20:09,570
Because it's a trusted server,
because you need to survive

1269
01:20:09,570 --> 01:20:11,760
it key. Yeah, I think that
should work in that case. But I

1270
01:20:11,760 --> 01:20:13,500
just want to say like, what
would you like? That's the

1271
01:20:13,500 --> 01:20:13,980
requirement?

1272
01:20:13,980 --> 01:20:19,530
What would your dream first test
event be? Close your eyes. Think

1273
01:20:19,530 --> 01:20:23,340
about it. Don't answer right
away. I want you to dream big is

1274
01:20:23,340 --> 01:20:25,800
tapped your heels together three
times.

1275
01:20:26,130 --> 01:20:30,390
I think podcasters would be very
interested in how many

1276
01:20:30,390 --> 01:20:33,060
subscribers do you have on the
platform, like who clicked

1277
01:20:33,060 --> 01:20:36,840
follow or whatever the language
is for that app? What that is

1278
01:20:36,840 --> 01:20:41,280
over time, and then also some
sort of way of who's listening?

1279
01:20:41,280 --> 01:20:44,490
Like how far did they go at an
aggregated level on this show?

1280
01:20:45,930 --> 01:20:48,270
How many listeners did it get?
As opposed to how many

1281
01:20:48,270 --> 01:20:51,660
downloads? I think those would
be two good first steps. You can

1282
01:20:51,660 --> 01:20:54,150
also do ratings this way. I
think James was interested in

1283
01:20:54,150 --> 01:20:56,670
that. I think that's another
cool thing to do as well, that's

1284
01:20:56,670 --> 01:21:00,570
more real time. But if it were
me, and it were to pick two, it

1285
01:21:00,570 --> 01:21:05,340
would be I guess, boring, but it
would be subscriptions, info and

1286
01:21:05,340 --> 01:21:05,940
listens.

1287
01:21:06,180 --> 01:21:10,560
Okay, those two things I'm not
interested in, in ratings at

1288
01:21:10,560 --> 01:21:13,830
all. It's one star or five
stars, PRs, everyone gets three

1289
01:21:13,830 --> 01:21:14,910
stars. That's it.

1290
01:21:15,720 --> 01:21:24,780
So here's, here's a. Here's a
layout. So if I'm, if I'm a

1291
01:21:25,410 --> 01:21:31,860
seriously simple podcasting
plugin user, and I want to know

1292
01:21:31,860 --> 01:21:37,860
how many followers I have, I
could use this. And let's just

1293
01:21:37,860 --> 01:21:42,630
say that there's a followers
event. I'm trying to use the

1294
01:21:42,630 --> 01:21:45,390
term followers and not
subscribers. There's a followers

1295
01:21:45,390 --> 01:21:53,760
event that is opened up on my
WordPress instance. And now,

1296
01:21:53,940 --> 01:21:58,380
excuse me, there's an inbox URL
and event hook on my install on

1297
01:21:58,380 --> 01:22:02,880
my WordPress instance. And it
goes into the podcast events tag

1298
01:22:03,300 --> 01:22:06,990
within the seriously simple
podcasting plugin. And now I

1299
01:22:06,990 --> 01:22:15,090
begin to get a follower counts
delivered to my, to my WordPress

1300
01:22:15,090 --> 01:22:20,190
instance, from overcast and
cast, ematic, and fountain and

1301
01:22:20,190 --> 01:22:24,330
breeze and all these all these
apps. So then, there can be a

1302
01:22:24,330 --> 01:22:29,940
dashboard, somewhere within the
plugin, this shows me, hey, you

1303
01:22:29,940 --> 01:22:35,220
have you know, 400 followers on
overcast, you have 300 followers

1304
01:22:35,220 --> 01:22:37,800
on this. And these are, these
are not download numbers, these

1305
01:22:37,800 --> 01:22:41,640
are actual just calculated
subscriber counts from the apps

1306
01:22:41,640 --> 01:22:46,140
themselves, these are, these are
real numbers, rather than

1307
01:22:46,140 --> 01:22:47,730
exactly decipher,

1308
01:22:47,910 --> 01:22:49,980
is enough of a back end that
they could implement it

1309
01:22:49,980 --> 01:22:54,810
themselves. So you know, I plan
on having op three or some sort

1310
01:22:54,810 --> 01:22:57,240
of system that will be a back
end that people can just stick

1311
01:22:57,240 --> 01:23:00,630
it in their feed. And, you know,
we'll do all the hard work for

1312
01:23:00,630 --> 01:23:02,790
them. If you don't own a
backhand, but WordPress, you

1313
01:23:02,790 --> 01:23:06,330
could probably make the plugin
serve as the as the back end. So

1314
01:23:06,330 --> 01:23:08,610
yeah, you're right, they could
create a simple little thing

1315
01:23:08,610 --> 01:23:13,080
that says, Thank you very much.
And here's, you know, an

1316
01:23:13,080 --> 01:23:15,720
aggregated view of that over
time, for sure. For sure.

1317
01:23:16,950 --> 01:23:20,520
Yeah, that would be something
that I thought specifically

1318
01:23:20,520 --> 01:23:24,450
about those two, about power
press. And seriously simple

1319
01:23:24,450 --> 01:23:28,260
because they're two examples of
a of, you know, highly

1320
01:23:28,260 --> 01:23:31,980
distributed, turning your own
domain into your own web hosting

1321
01:23:31,980 --> 01:23:36,150
company. And that, and they
already do things like web sub,

1322
01:23:36,150 --> 01:23:40,590
and they do, you know, they do a
lot of a lot of stuff there on

1323
01:23:40,590 --> 01:23:44,730
the on the private hosting
level. So I feel like that is

1324
01:23:44,730 --> 01:23:49,860
sort of a good way to, if you
visualize that even they could

1325
01:23:49,860 --> 01:23:54,030
do this exact ad to me makes it
make a little, it's like, okay,

1326
01:23:54,030 --> 01:23:58,140
this is doable. All the way
down. Yeah, the protocol to

1327
01:23:58,140 --> 01:24:01,140
extend down to the level of I
could actually, you know, spend

1328
01:24:01,140 --> 01:24:03,720
a weekend on this and do it. So
that was actually part of the

1329
01:24:03,720 --> 01:24:07,260
reason for me doing a proof of
concept. I didn't use any third

1330
01:24:07,260 --> 01:24:10,020
party libraries. I'm like, How
simple would this be to do just

1331
01:24:10,020 --> 01:24:13,710
with the primitives of a
language and it's, it's fairly

1332
01:24:13,710 --> 01:24:17,430
easy to do. Hey, here's Now I
wouldn't I'm not planning on

1333
01:24:17,430 --> 01:24:20,910
doing the work for WordPress. So
sign up for that, but it is it's

1334
01:24:20,910 --> 01:24:22,020
not impossible.

1335
01:24:22,320 --> 01:24:25,470
I have a weird question about
podcast events. Because you

1336
01:24:25,470 --> 01:24:27,570
know, it's a very different kind
of a technical episodes

1337
01:24:27,570 --> 01:24:33,000
interesting. Could I not
technically, just do a comment

1338
01:24:33,000 --> 01:24:35,820
through this system, if it's
going to an authenticated server

1339
01:24:35,820 --> 01:24:36,510
anyway.

1340
01:24:37,710 --> 01:24:41,760
You could, you could and in
fact, I had a meeting with Sam

1341
01:24:41,760 --> 01:24:46,680
so he is working on a top secret
thing that it's basically think

1342
01:24:46,680 --> 01:24:54,960
of it like, like podcast meets
Groupon or not Groupon, but um,

1343
01:24:55,740 --> 01:24:56,730
swinger party.

1344
01:24:57,600 --> 01:25:00,450
What was the app that like you
become the mayor of and that

1345
01:25:00,450 --> 01:25:02,100
sort of Kibo.

1346
01:25:03,510 --> 01:25:04,740
Are you talking about
Foursquare?

1347
01:25:05,310 --> 01:25:08,490
Foursquare? Yeah. So you
envision, like, Okay, so the

1348
01:25:08,490 --> 01:25:13,440
show is the venue. And so I want
to know, as a podcast, or what

1349
01:25:13,440 --> 01:25:17,400
are people doing, you know, at
at the event, so he would send

1350
01:25:17,400 --> 01:25:19,950
down like, oh, you know, so so
and so like the it's like a

1351
01:25:19,950 --> 01:25:23,550
wall. So every every wall event,
you know, the old school way of

1352
01:25:23,550 --> 01:25:26,610
thinking about along, would be
sent down. And what's cool about

1353
01:25:26,610 --> 01:25:29,580
the events thing is it doesn't
have to be aggregated. So if, if

1354
01:25:29,610 --> 01:25:33,390
like something is blowing up
right now, this is a real time

1355
01:25:33,390 --> 01:25:35,430
protocol, right. So this is
something that could be surfaced

1356
01:25:35,430 --> 01:25:39,240
like right away, and you get a
ping, or, or as soon as you get

1357
01:25:39,240 --> 01:25:41,850
featured on a particular
platform, they can send you a

1358
01:25:41,850 --> 01:25:44,730
thing, and you would you could
know instantly. So that's the

1359
01:25:44,730 --> 01:25:47,460
other thing I'm really excited
about is it does support

1360
01:25:47,970 --> 01:25:50,190
aggregated events, which is
probably what you'd want to do

1361
01:25:50,190 --> 01:25:54,090
for listings, right? A huge app
like Apple podcasts is not going

1362
01:25:54,090 --> 01:25:56,580
to send real time listened to
and nor would we want them to

1363
01:25:56,580 --> 01:26:00,870
write because that's, that would
break the privacy thing. But for

1364
01:26:00,870 --> 01:26:02,790
things like real time, like,
hey, there's something wrong

1365
01:26:02,790 --> 01:26:05,520
with your feed, you actually do
want to know that fairly

1366
01:26:05,520 --> 01:26:08,220
quickly. So it does support both
models.

1367
01:26:08,670 --> 01:26:12,120
So somebody like somebody like
pod chaser could send back an

1368
01:26:12,120 --> 01:26:19,950
event to transistor, saying that
this podcast on your platform,

1369
01:26:20,160 --> 01:26:26,280
just this podcast, that somebody
on pod chaser just just rated

1370
01:26:26,460 --> 01:26:31,830
this show, which is on your
which you're the hosting company

1371
01:26:31,830 --> 01:26:34,890
for don't say, four stars,

1372
01:26:34,950 --> 01:26:37,950
don't say this is what I hate,
because you know, what's next, I

1373
01:26:37,950 --> 01:26:42,870
can already see the proposal.
Label is not safe for work,

1374
01:26:42,990 --> 01:26:49,470
label, racist, labeled as anti
trans label as anti climate

1375
01:26:49,470 --> 01:26:50,280
change.

1376
01:26:51,720 --> 01:26:54,120
It's tricky. Yeah. And that's
actually a lot of what we talked

1377
01:26:54,120 --> 01:26:58,170
about with Sam is, you know what
to user than in that mode,

1378
01:26:58,170 --> 01:27:00,930
because like, every user is
different every platform. So it

1379
01:27:00,930 --> 01:27:05,220
does, and it does tend to look
like activity pub, or I don't

1380
01:27:05,220 --> 01:27:07,260
know if it had Dave, have you
looked at the new blue sky

1381
01:27:07,260 --> 01:27:12,510
stuff, they've actually started
to publish some actual code. And

1382
01:27:12,510 --> 01:27:15,810
it looks really interesting,
honestly. So I think it's still

1383
01:27:15,810 --> 01:27:19,800
early days, like this big to do
is like to do authentication.

1384
01:27:20,490 --> 01:27:22,830
But I could see that protocol,
especially now with Twitter

1385
01:27:22,830 --> 01:27:27,030
blowing up becoming something a
lot of people are working on. So

1386
01:27:27,270 --> 01:27:29,730
either way, as long as there's
some distributive way of saying

1387
01:27:29,730 --> 01:27:34,020
like, This is who a user is on
this platform. I think we keep

1388
01:27:34,020 --> 01:27:36,570
it pretty semi structured, and
just say, here are all the

1389
01:27:36,570 --> 01:27:39,510
things this app sends. And here
are all the things this app says

1390
01:27:39,510 --> 01:27:40,800
and I think that can be useful
to.

1391
01:27:42,480 --> 01:27:46,230
Man, it must be fro so
frustrating to sit at Apple as

1392
01:27:46,230 --> 01:27:50,310
an engineer. And think, Man, I
can't I can't implement any of

1393
01:27:50,310 --> 01:27:55,860
this. Apple won't let me do it.

1394
01:27:56,100 --> 01:28:00,750
Why did they get to have all the
fun on this show? We got a we

1395
01:28:00,750 --> 01:28:04,920
have we make a billion dollars a
day? Why can't we do this fun

1396
01:28:04,920 --> 01:28:05,190
stuff.

1397
01:28:05,730 --> 01:28:08,100
Speaking of billions of dollars
a day, shall we thank a few

1398
01:28:08,100 --> 01:28:11,880
people. As we go to a buck and a
half on today's show. I think we

1399
01:28:11,880 --> 01:28:15,210
should have a board meeting. So
these have come in during our

1400
01:28:15,210 --> 01:28:19,650
live show we are live. This has
value for value. So everything

1401
01:28:19,650 --> 01:28:23,520
you're hearing is all kind of
supported financially, all the

1402
01:28:23,520 --> 01:28:27,330
systems that are on the podcast
index side, as well as what we

1403
01:28:27,330 --> 01:28:29,940
talked about earlier with a node
with liquidity for anyone who

1404
01:28:29,940 --> 01:28:34,320
needs to pass payments cheaply
back and forth, is provided by

1405
01:28:34,320 --> 01:28:37,650
you. So if there's if you get
value out of this in any way,

1406
01:28:37,890 --> 01:28:41,730
feel free to go to podcast
index.org You can still send us

1407
01:28:41,760 --> 01:28:47,400
a Fiat fun coupons through
PayPal. Or if you don't have a

1408
01:28:47,400 --> 01:28:50,310
boost button on your app. You're
using an old one. You need to

1409
01:28:50,310 --> 01:28:54,480
get a new one at nude podcast
apps.com And go ahead and boost

1410
01:28:54,480 --> 01:28:59,880
this boomy. 50,000 SATs. He says
Happy Friday high five. Of

1411
01:28:59,880 --> 01:29:03,210
course, it's a Friday evening
over there in Deutschland. So

1412
01:29:03,210 --> 01:29:08,130
thank you very much. Oost Thank
you Bumi a Steven B is alive. I

1413
01:29:08,130 --> 01:29:11,160
have proof he didn't he didn't
boost us but I saw 100 SATs must

1414
01:29:11,160 --> 01:29:14,130
be a test on the no agenda
episode so I'm thinking he's

1415
01:29:14,130 --> 01:29:16,560
alive. So that's good news. I
haven't seen him on the in the

1416
01:29:16,560 --> 01:29:19,530
chat room today. I'm concerned
man. He was in the hospital.

1417
01:29:21,000 --> 01:29:24,180
The hippie Okay, Steven Yeah.
Blueberries just just send up a

1418
01:29:24,180 --> 01:29:27,630
red flag every now and then let
us know your blueberry is

1419
01:29:27,660 --> 01:29:33,480
getting in on the promotion
angle. 17,776 a big fan of

1420
01:29:33,510 --> 01:29:38,370
Patriot boost. This Sunday sees
the culmination of 30.3 hours of

1421
01:29:38,370 --> 01:29:43,740
pure uncut high octane
douchebaggery 72 contestants in

1422
01:29:43,740 --> 01:29:47,100
total now the eight winners go
toe to toe it's battle of the

1423
01:29:47,100 --> 01:29:51,090
douchebags nine I would love to
introduce boosts. How would

1424
01:29:51,090 --> 01:29:54,510
y'all work in booths for
bracketed style matches?

1425
01:29:55,800 --> 01:29:59,610
Toe Lord does that mean that you
know the tournament that's the

1426
01:29:59,610 --> 01:29:59,970
douchebag

1427
01:30:00,000 --> 01:30:03,390
No I'm seeing how do you work in
it's the bracketed style matches

1428
01:30:03,390 --> 01:30:03,780
that I don't

1429
01:30:04,560 --> 01:30:07,140
know that the bright you know
bracket is style like you

1430
01:30:08,880 --> 01:30:11,610
this one because are they
already using boosts for this?

1431
01:30:12,660 --> 01:30:16,080
I don't know. I haven't listened
to the show. Do I know of the

1432
01:30:16,080 --> 01:30:17,010
show but I haven't listened to

1433
01:30:17,100 --> 01:30:22,500
well, we got a little work on
that. Eric p p a big row of

1434
01:30:22,500 --> 01:30:27,570
ducks. 22,222 Thank you very
much, Eric. No other notes. Mike

1435
01:30:27,570 --> 01:30:33,540
Newman 54,333. SAS greetings
boardroom. He says no jingles no

1436
01:30:33,540 --> 01:30:36,750
karma. Just a boost. We got that
for you and we'll give you a

1437
01:30:37,080 --> 01:30:43,320
boost boost than we had. Let me
see tone wrecker trying to

1438
01:30:43,320 --> 01:30:46,170
orange so many of my artists
slash creator friends as well.

1439
01:30:46,170 --> 01:30:48,480
The struggle is real. Yes, I
hear you.

1440
01:30:48,930 --> 01:30:52,200
Yeah, Tameka is doing the work.
He's doing his own music and

1441
01:30:52,230 --> 01:30:55,260
it'll really be in the bushes
about me. Yeah, about V for V

1442
01:30:55,260 --> 01:30:55,920
music. Yep.

1443
01:30:56,010 --> 01:31:01,650
Nice. Nice. Alright, we're
relaxed male 22,222 finally

1444
01:31:01,650 --> 01:31:04,230
hitting a live show y'all sound
a bit stone because I normally

1445
01:31:04,230 --> 01:31:08,970
listen to 1.5 Speed go
podcasting? Yes, here we go. Go

1446
01:31:10,410 --> 01:31:13,890
stir Yeah, you need to stop the
one and a half speed is not good

1447
01:31:13,890 --> 01:31:14,400
for your brain.

1448
01:31:14,430 --> 01:31:21,300
Do you jog past the Mona Lisa
you heathen servo 3333 boosting

1449
01:31:21,300 --> 01:31:26,010
from crontab Thank you very much
Dave oh he were wearing no

1450
01:31:26,040 --> 01:31:30,000
that's it. I think we got him
all those the pre boosts that we

1451
01:31:30,000 --> 01:31:32,310
had thank you all very much.
That's people who are also

1452
01:31:32,310 --> 01:31:38,160
sitting in the chat room which
you can be alerted to with POD

1453
01:31:38,160 --> 01:31:42,450
verse that the live stream is
live and curio caster you can

1454
01:31:43,080 --> 01:31:49,110
hit the live chat and the stream
simultaneously. It's all it's

1455
01:31:49,110 --> 01:31:52,050
all part of the next phase and I
still haven't got I still

1456
01:31:52,050 --> 01:31:56,730
haven't gotten the live pod ping
from Todd Cochran so I wish said

1457
01:31:56,730 --> 01:31:59,940
about this and then I'm sure he
is as well.

1458
01:32:00,570 --> 01:32:04,290
Yeah, I feel like we have
there's something that's just

1459
01:32:04,290 --> 01:32:07,800
not working with sovereign fades
dashboard for him. We're gonna

1460
01:32:07,800 --> 01:32:11,760
have to set up the I'm gonna
have to make an something for

1461
01:32:11,760 --> 01:32:16,530
you. Like you know, I mean, like
not for you like something like

1462
01:32:16,650 --> 01:32:19,590
the one you use like, like the
hook we need to get me to give

1463
01:32:19,590 --> 01:32:23,190
him a hook where he can get on
this train. Working as fast as I

1464
01:32:23,190 --> 01:32:27,210
can to get the podcast pod
paying cloud live functionality

1465
01:32:27,210 --> 01:32:31,170
going. We're getting there. I'm
getting getting closer.

1466
01:32:31,470 --> 01:32:34,740
Actually. You know, why don't I
take one quick look new media

1467
01:32:34,740 --> 01:32:39,840
show why don't just take a look
real quick at his cars you know,

1468
01:32:39,840 --> 01:32:45,720
in in sovereign feeds, I can pop
right in into here, I can bring

1469
01:32:45,720 --> 01:32:49,350
his feet up. So is this purely a
pod ping issue he's having I

1470
01:32:49,350 --> 01:32:50,970
guess then I think

1471
01:32:50,970 --> 01:32:55,800
something with Steven B's pod. I
think it's something with his

1472
01:32:55,800 --> 01:33:00,480
pod ping writer is not working
right. It's not sending out the

1473
01:33:00,480 --> 01:33:05,310
live reason code or something is
just not whenever whenever Todd

1474
01:33:05,310 --> 01:33:08,400
hits it, there's just nothing,
nothing happens. It doesn't emit

1475
01:33:08,730 --> 01:33:09,450
a pod being

1476
01:33:09,510 --> 01:33:16,380
because I use the same. The same
system with a manual manual pod

1477
01:33:16,380 --> 01:33:21,060
ping page for no agenda and it
works. Just weird. Something's

1478
01:33:21,060 --> 01:33:21,450
weird.

1479
01:33:21,480 --> 01:33:25,320
Something's not right. Yeah, I
don't understand it. It must.

1480
01:33:25,350 --> 01:33:30,660
Well, if it's working for you,
then it's not. Oh, oh, wait,

1481
01:33:30,660 --> 01:33:33,870
wait, wait, wait. I'm sending
the pod paying for no agenda.

1482
01:33:34,140 --> 01:33:35,910
Not not sovereign fee,

1483
01:33:35,970 --> 01:33:38,520
since we're gonna use sending
the pod ping for no agenda.

1484
01:33:38,790 --> 01:33:39,600
Because you have

1485
01:33:39,630 --> 01:33:45,990
us You have my web hook set as
your as your web hook URL.

1486
01:33:46,020 --> 01:33:49,320
You but I never used that
because I can't the RSS feed is

1487
01:33:49,320 --> 01:33:50,040
not there.

1488
01:33:51,300 --> 01:33:55,440
So I'm sorry. Oh, you're not
you're not hitting that button

1489
01:33:55,440 --> 01:33:55,890
here. You

1490
01:33:55,950 --> 01:33:59,820
know, I was waiting for you to
tell me it was working. Did you

1491
01:34:00,090 --> 01:34:04,050
set that up with Mark so I can
publish this? So wasn't working.

1492
01:34:05,190 --> 01:34:06,150
I'm not doing it.

1493
01:34:07,650 --> 01:34:10,110
This is an indication that there
are way too many moving parts

1494
01:34:10,110 --> 01:34:13,950
within this system. And no idea
what yeah,

1495
01:34:13,980 --> 01:34:16,230
you could just be tied to
official button pusher. So

1496
01:34:16,890 --> 01:34:19,830
stream and URL in there.

1497
01:34:20,160 --> 01:34:24,390
All I do, man. I just push
buttons. It's all but next

1498
01:34:24,390 --> 01:34:26,400
to me when you need a lot of
time. Yeah, and

1499
01:34:26,400 --> 01:34:34,110
Todd Todd. Also just get on Alby
man. I know you want or send a

1500
01:34:34,110 --> 01:34:37,200
majority of the split to Alabama
so you can get some when you see

1501
01:34:37,200 --> 01:34:40,710
the stats from Albie, you're
gonna you're gonna melt

1502
01:34:43,860 --> 01:34:47,850
as Oscar said, as he mentioned
whether or not like if he's

1503
01:34:47,850 --> 01:34:50,670
getting close to doing the live
notifications with fountain.

1504
01:34:51,059 --> 01:34:54,389
Interesting you asked that I
asked him this specifically and

1505
01:34:54,389 --> 01:34:59,009
he said yes, they were finishing
up the player code and we have a

1506
01:34:59,009 --> 01:35:01,559
chat scheduled for Monday, so

1507
01:35:02,160 --> 01:35:06,330
Oh, cool, sweet. That's a big
benefit for them because there's

1508
01:35:06,360 --> 01:35:09,270
there's a lot of those value for
value shows. Oh, yeah.

1509
01:35:09,480 --> 01:35:13,110
I said, Hey, man, are you
working on lit? So? I know man

1510
01:35:13,110 --> 01:35:15,570
when whenever a guy like asked
us Hey, do you have time to

1511
01:35:15,570 --> 01:35:19,080
talk? Oh my gosh, it's
something's wrong. run out of

1512
01:35:19,080 --> 01:35:24,990
money as he's going on. I'm just
hoping for the best now. But I

1513
01:35:24,990 --> 01:35:28,950
asked him specifically I do have
lit on the on the roadmap. So

1514
01:35:28,950 --> 01:35:33,060
yeah, it's on the way this week.
It's a lot of work man doing an

1515
01:35:33,060 --> 01:35:36,240
app it's a heck of a lot of work
to create it.

1516
01:35:36,660 --> 01:35:43,560
And Oscar moves fast he he's put
stuff in so fast. Yeah. You want

1517
01:35:43,560 --> 01:35:47,490
to do some pay pals? Yeah, I
think we should. We got a we've

1518
01:35:47,490 --> 01:35:51,450
got one. Pay Pal this week.

1519
01:35:51,629 --> 01:35:53,999
We have really transitioned,
haven't we?

1520
01:35:55,590 --> 01:36:00,720
But this is a big one. Okay.
It's from our buddies. John, And

1521
01:36:03,060 --> 01:36:10,050
gosh, I'm drawn to blank. John
Buddha and over transistor.

1522
01:36:11,310 --> 01:36:12,780
What? Why can I not remember?

1523
01:36:13,560 --> 01:36:16,830
You asking me I don't know any
name is Justin Jackson. Justin.

1524
01:36:16,860 --> 01:36:19,830
There you go. John and Justin.
Yes, John. And Justin.

1525
01:36:19,830 --> 01:36:23,640
I just totally drew blank. Thank
you, John. Transit they sent us

1526
01:36:23,640 --> 01:36:25,350
$500 And I forgot his name.

1527
01:36:25,380 --> 01:36:26,100
Oh.

1528
01:36:27,810 --> 01:36:30,540
Nice blades. Only him Paula.

1529
01:36:33,570 --> 01:36:37,290
Night. Thank you so much. They
have they don't think they've

1530
01:36:37,410 --> 01:36:39,660
they've supported us this way
before have they?

1531
01:36:40,080 --> 01:36:42,300
Yeah, not that I know. I think
this is their first donation.

1532
01:36:43,200 --> 01:36:46,320
Yeah. And so John and John
Buddha and Justin Jackson. And

1533
01:36:46,320 --> 01:36:49,500
he says, John and I are big fans
of what you're doing. Thanks so

1534
01:36:49,500 --> 01:36:50,790
much for everything you do.

1535
01:36:51,179 --> 01:36:54,869
Thank you. Thank you so much. I
love how the hosting community

1536
01:36:54,869 --> 01:36:58,949
and I will call them a
community. They get it? Yeah,

1537
01:36:59,129 --> 01:37:02,279
yeah, by the way, most of the
Bitcoin people they don't get

1538
01:37:02,279 --> 01:37:02,489
it.

1539
01:37:03,210 --> 01:37:05,010
Don't ever send us anything.

1540
01:37:05,820 --> 01:37:09,180
I never see a Bitcoin Maxy
saying, hey, you know what,

1541
01:37:09,180 --> 01:37:11,790
let's support these guys over
here. Let's send the medicine of

1542
01:37:11,790 --> 01:37:18,780
some some boosts never. Yeah,
no, no, no, no. Yes. complain.

1543
01:37:19,260 --> 01:37:23,130
Thank you, Justin. And yeah,
Justin was real. What prompted

1544
01:37:23,130 --> 01:37:26,070
that donation was the TX T tag
because they're really good.

1545
01:37:26,670 --> 01:37:29,370
Mover on that. They jumped on
it. They've already got it in

1546
01:37:29,370 --> 01:37:33,240
their UI as far as I can. Like
he's posted. Dynamite. Oh, cool.

1547
01:37:33,240 --> 01:37:36,450
Yeah, yeah. Yeah, appreciate
those guys a lot. Thank you,

1548
01:37:36,450 --> 01:37:41,550
Justin. And we've got Dells, it
does pay pal so it gets boosts

1549
01:37:41,580 --> 01:37:46,350
what a transition how we went
from 100% Pay Pal to like one

1550
01:37:46,800 --> 01:37:53,970
one. Roi scheinfeld 54321

1551
01:37:54,420 --> 01:37:57,990
ROI always they're always there
for us.

1552
01:37:59,010 --> 01:38:02,280
From the breeze app sitting in
the tub with milk and rose

1553
01:38:02,280 --> 01:38:02,790
petals.

1554
01:38:03,660 --> 01:38:07,500
And honey in honey milk and rose
petals and Honey Do you think he

1555
01:38:07,500 --> 01:38:12,810
has like little nymphs around
him? You know just at his at his

1556
01:38:12,840 --> 01:38:18,810
every beck and call just float
around little pixies

1557
01:38:19,170 --> 01:38:21,060
they missed lavender in the air

1558
01:38:25,230 --> 01:38:29,220
Your Highness Your Highness
missed some lavender for you,

1559
01:38:29,549 --> 01:38:36,059
sir scheinfeld Mike my Newman
again we just mentioned my name

1560
01:38:36,059 --> 01:38:39,839
that back again. 2112 Rush boost
through pod verse. Nice. Thank

1561
01:38:39,839 --> 01:38:43,079
you my he says How about using
some of the some of these

1562
01:38:43,079 --> 01:38:48,059
proposals together like remote
item and events? Producer A is

1563
01:38:48,059 --> 01:38:51,719
the playlist DJ with a remote
item pointing to one of the

1564
01:38:52,139 --> 01:38:57,239
producer B's items. Yes finally
Adam got it. Events can link

1565
01:38:57,269 --> 01:39:01,289
these things B can always check
AES feed to check that the

1566
01:39:01,289 --> 01:39:07,079
remote item registered to A by A
to B is there still are still

1567
01:39:07,079 --> 01:39:10,859
there ah payload payload of
event could provide the links

1568
01:39:11,039 --> 01:39:13,829
these tags proposals make
beautiful music together team

1569
01:39:13,829 --> 01:39:14,639
repo Mike.

1570
01:39:15,030 --> 01:39:19,560
Hey, that's interesting. So you
could have an event that is a

1571
01:39:19,560 --> 01:39:27,750
dynamically generated remote
Item No, I'm saying

1572
01:39:28,860 --> 01:39:34,800
that dynamic. No. So an event
could dynamically generated

1573
01:39:34,800 --> 01:39:35,190
which would

1574
01:39:35,190 --> 01:39:41,880
mean that the the remote item is
not predetermined? Yeah, I don't

1575
01:39:41,880 --> 01:39:45,120
know. I don't know. I think I
need to smoke more drugs.

1576
01:39:45,150 --> 01:39:46,470
Yeah, my coffee is wearing off.

1577
01:39:48,210 --> 01:39:51,360
Let's just keep moving on
sometimes. That was a crash and

1578
01:39:51,360 --> 01:39:52,110
burn sorry.

1579
01:39:55,740 --> 01:40:00,900
Okay. James Crillon 1001 SATs
through fountain He says remote

1580
01:40:00,900 --> 01:40:05,580
item, agree that I would not use
it for an episode drop. But

1581
01:40:05,580 --> 01:40:08,280
perhaps I could produce a new
podcast trailers feed wholly

1582
01:40:08,280 --> 01:40:11,700
using remote items. Again, I
can't make them consistent. But

1583
01:40:11,700 --> 01:40:14,760
I reckon I can do that perhaps.
And I think he did, as he must

1584
01:40:14,760 --> 01:40:15,720
have done just that he did

1585
01:40:15,720 --> 01:40:19,830
just that. And I heard him kind
of walking through that

1586
01:40:19,830 --> 01:40:22,890
particular tag. And I just want
to say, again, it was designed

1587
01:40:22,890 --> 01:40:25,980
with music in mind, let's be
honest about it's not like a

1588
01:40:25,980 --> 01:40:29,460
completely intuitive thing for
all podcasters.

1589
01:40:29,970 --> 01:40:32,070
Oh, one thing I want to say
about that, because I heard him

1590
01:40:32,070 --> 01:40:34,110
describing it, he was like,
Well, I think most of the time,

1591
01:40:34,110 --> 01:40:35,820
you just want to put the
enclosure in there and be done

1592
01:40:35,820 --> 01:40:42,120
with it. That's it. I think he
may be missing the bigger point

1593
01:40:42,120 --> 01:40:47,550
here, which is you with a remote
item, you link to the entire

1594
01:40:47,550 --> 01:40:51,030
item, which means that you, you
all you get the benefit of the

1595
01:40:51,030 --> 01:40:54,510
absorbing all of its proper all
the data, all the metadata.

1596
01:40:54,780 --> 01:40:58,680
Yeah, the value blocks, the
sound bytes, the all that stuff,

1597
01:40:58,800 --> 01:41:02,370
like you pull the chapters, the
transcript, all that stuff comes

1598
01:41:02,370 --> 01:41:06,570
with it, when you link to it.
And you can still add your own

1599
01:41:06,570 --> 01:41:11,730
stuff to it, but you also absorb
it's like recursion. It's like

1600
01:41:11,730 --> 01:41:12,660
sub classing.

1601
01:41:12,900 --> 01:41:14,820
Yeah, right. Right. Right. So

1602
01:41:14,850 --> 01:41:17,580
you know, you're just you're
like extending a class, almost,

1603
01:41:17,580 --> 01:41:20,280
you're absorbing its properties.
And you can add more properties.

1604
01:41:20,280 --> 01:41:23,190
But again, the practical use
case and I've never understood

1605
01:41:23,190 --> 01:41:26,910
fee drops and takeovers and all
that. It's like no, use my feet

1606
01:41:26,910 --> 01:41:28,800
is mine. I'm not putting
anything else there. But in the

1607
01:41:28,800 --> 01:41:33,660
context of music and making
playlists, using the index and

1608
01:41:33,660 --> 01:41:37,890
the namespace, infrastructure
and architecture. That is really

1609
01:41:37,890 --> 01:41:38,820
where it's going to shine.

1610
01:41:40,020 --> 01:41:44,910
Mere Mortals podcast 11 111.
They found and it says, this bar

1611
01:41:44,910 --> 01:41:48,150
buddy car and he says this
remote item talk sounds like it

1612
01:41:48,150 --> 01:41:51,450
would work well with clips that
you guys play. So not only is it

1613
01:41:51,450 --> 01:41:54,270
applicable to music playlists,
but also referencing other

1614
01:41:54,270 --> 01:41:55,050
podcasts.

1615
01:41:55,140 --> 01:41:59,310
Yeah. He went exactly the
opposite of the other one. Yeah,

1616
01:41:59,370 --> 01:42:01,680
I love it. Nice.

1617
01:42:02,730 --> 01:42:07,740
Let's see Jay Cole McCormick.
3333. Through fountain epi says

1618
01:42:07,740 --> 01:42:11,190
in need of jobs karma. I quit my
job at the Weed Shop because

1619
01:42:11,190 --> 01:42:14,070
they were stealing 15% of my
tips and giving it to managers.

1620
01:42:14,400 --> 01:42:16,890
I'm confident the future is
awesome. If I lean into value

1621
01:42:16,890 --> 01:42:18,840
for value and double down on
podcasting,

1622
01:42:18,900 --> 01:42:24,060
jobs, jobs, jobs and jobs, let's
vote for jobs.

1623
01:42:26,040 --> 01:42:29,220
You've got karma wrong show but
okay.

1624
01:42:31,800 --> 01:42:35,670
Okay, James Crillon back again
1001 sets the fountain Hey, man,

1625
01:42:35,670 --> 01:42:41,400
what is this? 1001 It's like he
knows the cut off is 1000 It was

1626
01:42:41,400 --> 01:42:44,280
just doing the extra like just a
while. Give these boys little

1627
01:42:44,280 --> 01:42:47,880
extra. Take a sad boys

1628
01:42:47,910 --> 01:42:51,780
whooshed just peeking over the
wall. Right early picking

1629
01:42:51,780 --> 01:42:53,370
they're like barely.

1630
01:42:54,630 --> 01:42:56,610
Vision is to be second last
every week.

1631
01:42:59,100 --> 01:43:03,030
What you've just described there
is an EPG an electronic Yeah.

1632
01:43:03,030 --> 01:43:06,150
brandguide. Yes. Which most
radio stations produced these

1633
01:43:06,150 --> 01:43:08,220
days anyway, for their apps. It
works. Well.

1634
01:43:08,490 --> 01:43:11,580
Thank you. Thank you, James.
That was dynamite. I saw this

1635
01:43:11,580 --> 01:43:15,690
booster Graham come in. I this
was based upon our conversation

1636
01:43:15,720 --> 01:43:21,840
of hitting pod paying when a new
show starts on 100%. Retro,

1637
01:43:22,050 --> 01:43:25,320
which is still up. And I'm now
adding episodes, which are

1638
01:43:25,320 --> 01:43:29,610
basically promos for the week.
And when he said that, oh, yes,

1639
01:43:29,610 --> 01:43:33,540
of course, this this actually is
a document that they they make

1640
01:43:33,540 --> 01:43:38,670
to send out to themselves
internally, externally, etc. And

1641
01:43:38,850 --> 01:43:41,850
so I said right away, I said,
Hey, I need an EPG from you

1642
01:43:41,850 --> 01:43:44,850
guys. It needs to be structured.
So it needs to be something that

1643
01:43:44,850 --> 01:43:48,690
can be automatically read in by
computer and they will get that

1644
01:43:48,690 --> 01:43:50,550
to me. So we're on our way.

1645
01:43:51,540 --> 01:43:54,120
And I will say that putting is
going to get even broader in

1646
01:43:54,120 --> 01:43:57,150
scope and better. Me and Alex
had been brainstorming a bunch

1647
01:43:57,150 --> 01:44:00,840
of stuff this week. And we get
there'll be more news on that

1648
01:44:00,840 --> 01:44:03,600
front in the future, but it will
be it's going to become even

1649
01:44:03,600 --> 01:44:09,360
more universal. Nice. Gene
Everett 33,000 sets he says

1650
01:44:09,510 --> 01:44:10,560
boost boost boost.

1651
01:44:12,120 --> 01:44:14,580
Boost boost boost something like
that.

1652
01:44:15,059 --> 01:44:18,029
Karen from the mirror morals
podcast back again with a row

1653
01:44:18,029 --> 01:44:21,569
611 111 He says there's nobody I
trust more than Dave to willy

1654
01:44:21,569 --> 01:44:28,289
nilly around in the namespace.
That's so inappropriate. Karen

1655
01:44:29,249 --> 01:44:35,129
SLC sent 1776 SAS and he says
not just value for value

1656
01:44:35,129 --> 01:44:38,939
playlists but also V for V for
end of show mixes that split

1657
01:44:38,939 --> 01:44:40,169
Yeah, all the same. Same. Yeah,

1658
01:44:40,200 --> 01:44:42,450
they use Yes, yes. Yes.

1659
01:44:42,870 --> 01:44:46,680
intergalactic boom boss gets
splits every time I boost. Yep,

1660
01:44:46,860 --> 01:44:52,830
exactly right. Sourced send us
elite 1337 sets it through pod

1661
01:44:52,830 --> 01:44:54,300
verse and he says go podcasting

1662
01:44:54,690 --> 01:44:55,740
go podcast.

1663
01:44:58,440 --> 01:45:03,150
First lb boost from podcast.
ers. Nice. Max burns and his

1664
01:45:03,150 --> 01:45:06,630
40,000 SAS through fountaining
and as you drain the wallet, the

1665
01:45:06,630 --> 01:45:09,150
entire community behind
podcasting 2.0 We're doing

1666
01:45:09,150 --> 01:45:12,870
important work and doing it well
really love all the new apps and

1667
01:45:12,870 --> 01:45:16,620
features this enables. Thank
you, Scott and Jalbert sir Scott

1668
01:45:16,650 --> 01:45:21,540
on the other show, Instagram.
Billy Bones sent us 3333 through

1669
01:45:21,540 --> 01:45:29,340
fountain no note 6969 from Hey,
citizen, through pod verse, he

1670
01:45:29,340 --> 01:45:32,700
says, I'd just like to interject
for a moment, what you're

1671
01:45:32,700 --> 01:45:36,960
referring to as value is in fact
value for value, or as I've

1672
01:45:36,960 --> 01:45:41,490
recently taken to calling it
value plus value. The value for

1673
01:45:41,490 --> 01:45:44,280
value is not content unto
itself, but rather another free

1674
01:45:44,280 --> 01:45:47,610
component of a fully functioning
podcasting system made useful by

1675
01:45:47,610 --> 01:45:51,300
the creators, dudes named Ben
and vital producers comprising a

1676
01:45:51,300 --> 01:45:54,690
full p 2.0 system as defined by
the namespace.

1677
01:45:55,410 --> 01:45:58,650
So what is he saying that we
need to name it differently?

1678
01:45:59,580 --> 01:46:03,870
I think he's just saying that
it's it's a broad it's even

1679
01:46:03,870 --> 01:46:05,550
broader in scope than we even

1680
01:46:05,640 --> 01:46:08,070
Oh, okay. Yes. Thank you. Hey,
citizen.

1681
01:46:08,580 --> 01:46:13,170
Thank you, Franco. Celerio, the
genius developer behind Cass

1682
01:46:13,170 --> 01:46:18,570
91107. No note, send a note next
time frame now Frank, I missed

1683
01:46:18,570 --> 01:46:23,730
you. Dave Jackson Hall of Famer
send us 2428 through systematics

1684
01:46:23,760 --> 01:46:30,990
Hall of Famer. Boom, no note. I
get Dave Jackson, fellow Hall of

1685
01:46:30,990 --> 01:46:31,620
Famer

1686
01:46:31,770 --> 01:46:36,480
fellow. I can't say that you
have to say,

1687
01:46:36,510 --> 01:46:40,140
oh, Dave, you're gonna get your
award man. You're gonna get

1688
01:46:41,430 --> 01:46:43,380
into 2019

1689
01:46:44,100 --> 01:46:46,800
These things this weird the way
that works, you'll get an award

1690
01:46:46,800 --> 01:46:47,400
and watch

1691
01:46:47,820 --> 01:46:53,790
MIT lion 11 111 They row sticks
their breeze, it says just

1692
01:46:53,790 --> 01:46:59,580
streamed 111 k sets a minute for
10 minutes also in brief, so you

1693
01:46:59,580 --> 01:47:03,660
can see if those appears boosts
or not. I did see that. And it

1694
01:47:03,660 --> 01:47:05,400
did. I see. And it came through.

1695
01:47:05,400 --> 01:47:10,620
Yes. And I also You were right.
Whoever it was was sending 3033

1696
01:47:10,620 --> 01:47:13,560
sets a minute for quite a while
the other day.

1697
01:47:14,010 --> 01:47:16,050
Yeah. And it's funny you
mentioned that because he's next

1698
01:47:16,050 --> 01:47:17,610
on my list is Auburn citadel.

1699
01:47:17,970 --> 01:47:23,430
And he shows up Auburn Citadel
Hold on. As Wait, let me look at

1700
01:47:23,430 --> 01:47:31,080
my dashboard. He I think he's
one of the top supporters across

1701
01:47:31,110 --> 01:47:36,060
all the podcasts that I have.
With a piece going to Alby which

1702
01:47:36,060 --> 01:47:39,390
is basically everything he's
like, like the top Yeah, he's

1703
01:47:39,390 --> 01:47:43,140
like 2.2 million SATs or
something totally sent to the

1704
01:47:43,260 --> 01:47:44,910
podcast I'm involved in.

1705
01:47:45,389 --> 01:47:48,989
Holy crap. The whale you get a
whale

1706
01:47:50,010 --> 01:47:56,580
we've got a whale we got
ourselves a value for value

1707
01:47:56,580 --> 01:47:57,510
whale.

1708
01:47:58,890 --> 01:48:05,370
Our Citadel and totals up last
episode once 173,316 sets. Thank

1709
01:48:05,370 --> 01:48:10,320
you overstated? How much did he
send? 173,316

1710
01:48:11,790 --> 01:48:15,600
Sakala 20 is blades on am Paula

1711
01:48:15,630 --> 01:48:16,500
means that

1712
01:48:20,250 --> 01:48:27,600
5000 SATs from Bumi and he says
well who? back get your movie

1713
01:48:28,920 --> 01:48:31,830
20 I'm sorry, how much

1714
01:48:32,340 --> 01:48:41,670
2125. Oh, contracts center since
one 100,021 says friend through

1715
01:48:41,670 --> 01:48:45,270
fountain Nene says check out
contracts dot app for stats

1716
01:48:45,270 --> 01:48:49,710
about your stats stats about
your SATs. Weight. So the app

1717
01:48:49,920 --> 01:48:52,500
this is the contract apps and us
as

1718
01:48:55,680 --> 01:48:57,450
the contract app itself

1719
01:48:58,260 --> 01:49:02,100
this it's clearly achieved
sentience and is now sending out

1720
01:49:02,100 --> 01:49:03,030
mood booster grams.

1721
01:49:03,450 --> 01:49:09,060
Is it draining my wallet? This
is interesting. I will maybe you

1722
01:49:09,060 --> 01:49:10,440
can send stuff here. I don't

1723
01:49:10,440 --> 01:49:12,180
know. And it's sending them
through fountain.

1724
01:49:13,200 --> 01:49:13,950
So okay.

1725
01:49:14,700 --> 01:49:21,660
Right. Brian of London in the
hive Dao send us 47,331 SATs

1726
01:49:21,690 --> 01:49:30,030
Thank you Brian. Okay, this is
this is song lyrics. And when

1727
01:49:30,030 --> 01:49:33,330
the elegance escapes me the
logic ties me up and race me dee

1728
01:49:33,330 --> 01:49:36,180
doo doo did oh, that's the
police to

1729
01:49:37,500 --> 01:49:43,050
do all I want to do for you to
do to lead it's called the dee

1730
01:49:43,050 --> 01:49:46,830
dee doo doo doo doo doo. That's
the name. The DD Duchamp was

1731
01:49:46,830 --> 01:49:47,340
asked from

1732
01:49:47,340 --> 01:49:56,760
us synchronicity to think like
that referee who is the 11,211

1733
01:49:56,760 --> 01:50:00,810
SATs he's for the creator behind
ours is blue. He says question,

1734
01:50:01,290 --> 01:50:05,940
what is the significance of
this? palindromic boost? Answer?

1735
01:50:06,270 --> 01:50:10,980
I need to refill my fountain
wallet 11211 Thank you Dobby

1736
01:50:10,980 --> 01:50:11,940
does appreciate that.

1737
01:50:11,970 --> 01:50:12,750
Here it is day.

1738
01:50:13,140 --> 01:50:15,060
Oh, oh what a great song.

1739
01:50:15,330 --> 01:50:18,840
It's new doo dee da da

1740
01:50:19,530 --> 01:50:21,390
da da da da da

1741
01:50:22,770 --> 01:50:23,910
da da da.

1742
01:50:24,720 --> 01:50:33,660
Okay, I'm never going to
remember that. Great drummer he

1743
01:50:33,660 --> 01:50:36,270
used to doubler on his drums,
which always made it sound like

1744
01:50:36,270 --> 01:50:39,750
it had a little bit of a delay.
And like a little delay effect

1745
01:50:39,810 --> 01:50:44,730
he has he has a very interesting
way of drumming. Yeah, phrasing

1746
01:50:44,730 --> 01:50:47,370
just looking at him. Like how
many arms do you have?

1747
01:50:48,030 --> 01:50:52,530
Wasn't he on? Am I crazy? Or was
he on like one of those Tonight

1748
01:50:52,530 --> 01:50:55,560
Show? bands for a while?

1749
01:50:55,590 --> 01:51:00,390
No, no, I don't think so. For
like a short stint. Maybe Max

1750
01:51:00,390 --> 01:51:03,690
Weinberg? Maybe he was in that
first second. That would be the

1751
01:51:03,690 --> 01:51:05,340
only place I could imagine him.

1752
01:51:05,640 --> 01:51:08,940
I think he may have sat in for
Max Weinberg a few times that

1753
01:51:08,940 --> 01:51:09,720
Oh,

1754
01:51:09,750 --> 01:51:14,520
in fact, I think you're right.
Yeah, yeah. Did Max Max Weinberg

1755
01:51:14,520 --> 01:51:15,750
get get canceled?

1756
01:51:16,770 --> 01:51:18,780
Oh, I don't know. This is needed
me. Oh my god.

1757
01:51:18,780 --> 01:51:21,660
This is way before canceling.
Okay,

1758
01:51:21,690 --> 01:51:22,500
what did he do

1759
01:51:24,030 --> 01:51:27,750
for Conan? Because I think he
left when Conan kinda got kicked

1760
01:51:27,750 --> 01:51:32,760
off a TBS, but he was there for
like tons of like, lot. I don't

1761
01:51:32,760 --> 01:51:34,470
know, several years before that.

1762
01:51:34,860 --> 01:51:39,780
But he he leaves. I there was
there was something maybe he did

1763
01:51:39,780 --> 01:51:41,070
he just leave.

1764
01:51:42,600 --> 01:51:43,860
I don't know that.

1765
01:51:43,860 --> 01:51:47,250
I don't remember. What they went
back on tour, I think. I don't

1766
01:51:47,250 --> 01:51:50,130
know. I think he was having a
hard I used to watch Conan all

1767
01:51:50,130 --> 01:51:54,030
the time. I think he just found
it hard to do both at a certain

1768
01:51:54,030 --> 01:51:57,690
point after 20 years. Right.
Yeah, you're a Cohen's ban.

1769
01:52:00,000 --> 01:52:03,690
Comic Strip blogger, the
delimiter. There 1033 sets

1770
01:52:03,690 --> 01:52:06,810
through fountain and he says,
dearest Adam and Dave, you're

1771
01:52:06,810 --> 01:52:10,080
smart cookie producers are
invited to put AI dot cooking

1772
01:52:10,260 --> 01:52:13,980
into any web browser or podcast
app to enjoy the infotainment on

1773
01:52:13,980 --> 01:52:17,610
offer. Please allow them to be
soothed by the silky smooth

1774
01:52:17,610 --> 01:52:21,660
tones of former BBC BBC actor
and TV Show Developer Gregory

1775
01:52:21,660 --> 01:52:25,410
Forman whilst becoming informed
about artificial intelligence.

1776
01:52:25,500 --> 01:52:25,980
Yo.

1777
01:52:32,040 --> 01:52:35,490
Thank you all for hitting that
boost button. And thanks for the

1778
01:52:35,490 --> 01:52:37,770
big boosts. And we have some
monthlies

1779
01:52:37,950 --> 01:52:42,390
guests in monthlies again, Chad
Pharoah $20.22 Thank you, Chad.

1780
01:52:42,750 --> 01:52:50,460
Scott Jalbert $12 Mark, gram $1
New Media $1. David Mitas $10.

1781
01:52:50,460 --> 01:52:54,660
Thank you, David. Appreciate
that. And Joseph maraca $5. And

1782
01:52:54,660 --> 01:52:58,800
that was, yeah, that's really
appreciate transistor coming in,

1783
01:52:58,800 --> 01:53:03,360
because we lost about $50 a
month and Pay Pal and all that

1784
01:53:03,360 --> 01:53:06,510
we did that we did that. Yeah.
So that that really helps. Yeah,

1785
01:53:07,140 --> 01:53:07,500
that's it.

1786
01:53:07,920 --> 01:53:12,990
I was just reading Ice Cube soup
in the chat with a feature

1787
01:53:12,990 --> 01:53:14,820
request, which I thought was
really interesting, because we

1788
01:53:14,820 --> 01:53:18,090
were just talking about these,
these high level streaming sat,

1789
01:53:18,870 --> 01:53:22,380
payments, feature request
streaming boosts level

1790
01:53:22,410 --> 01:53:28,530
elevation, with deadman switch
functions like this streaming

1791
01:53:28,530 --> 01:53:31,830
boost rate is elevated after you
push the button and stays

1792
01:53:31,830 --> 01:53:35,010
elevated until the app notice
that you haven't reaffirmed your

1793
01:53:35,010 --> 01:53:38,820
intent in the last 10 minutes.
That's kind of an interesting

1794
01:53:38,820 --> 01:53:39,360
idea.

1795
01:53:40,260 --> 01:53:43,080
I don't understand. Like, so you

1796
01:53:43,080 --> 01:53:46,080
can decide okay, I'm next I'm
going to send 5000 SATs a minute

1797
01:53:46,080 --> 01:53:49,410
for as long as I'm listening
However, every 10 minutes the

1798
01:53:49,410 --> 01:53:53,490
app is going to ask me if I if I
if I'm still here or it will

1799
01:53:53,490 --> 01:53:54,090
stop

1800
01:53:56,520 --> 01:54:01,650
like like a crow's which Oh, I
see I see. Oh, you fall

1801
01:54:01,650 --> 01:54:02,820
asleep listening to a podcast

1802
01:54:02,820 --> 01:54:07,800
Exactly. Like you want it like
it's highly rated but you you do

1803
01:54:07,800 --> 01:54:11,280
want to I don't know. I don't
know. I guess you just empty

1804
01:54:11,280 --> 01:54:14,220
your wallet and booster gram to
us. That's all that's that's the

1805
01:54:14,220 --> 01:54:19,320
best, the best the most fun you
can have. And if it's above $100

1806
01:54:19,320 --> 01:54:23,400
In Fiat fun coupons, we will
send you an official t shirt,

1807
01:54:24,030 --> 01:54:28,440
which is not available anywhere
except through donations on the

1808
01:54:28,440 --> 01:54:31,440
show. Am I correct? Do we still
have access to this great deal?

1809
01:54:31,980 --> 01:54:37,890
We do. We do? Is it set one for
danger for dare No. Just the

1810
01:54:37,890 --> 01:54:38,310
other day.

1811
01:54:39,000 --> 01:54:42,570
Thank you again for supporting
podcasting 2.0 the podcasts for

1812
01:54:42,570 --> 01:54:45,420
supporting the infrastructure
for the project. And of course

1813
01:54:45,420 --> 01:54:49,380
it's time talent and treasure.
So so many of you are doing

1814
01:54:49,380 --> 01:54:53,880
things that are just including
John Spurlock doing amazing work

1815
01:54:53,880 --> 01:54:58,920
to to to make the circle of
scissor running even wider

1816
01:55:00,000 --> 01:55:02,640
which is appreciate you guys
it's it's always fun being on

1817
01:55:02,640 --> 01:55:05,670
and Dave, I love the fact that
like we don't have to have

1818
01:55:06,510 --> 01:55:09,330
communication meetings like we
just have the asynchronous

1819
01:55:09,360 --> 01:55:12,390
Mastodon I love when you bring
up a, you know, a proposal or

1820
01:55:12,390 --> 01:55:15,420
something you've completely
integrated it like, you know, I

1821
01:55:15,420 --> 01:55:18,870
never have to yell at the radio
and say, you know, it's like

1822
01:55:18,870 --> 01:55:21,630
this because you get it. And I
think that's really cool that

1823
01:55:21,630 --> 01:55:24,030
like, we have a project where
people can kind of do their own

1824
01:55:24,030 --> 01:55:28,080
thing. But everyone kind of
understands the goal here. So I

1825
01:55:28,080 --> 01:55:29,160
think that that's really cool.

1826
01:55:29,580 --> 01:55:32,370
Yeah. Oh, thanks for that. And I
think you're right. I think

1827
01:55:32,370 --> 01:55:36,090
that's the one of the strengths
of this project is probably not

1828
01:55:36,090 --> 01:55:39,930
like a lot of others that I've
seen is that everybody is very,

1829
01:55:39,930 --> 01:55:44,280
it's loose, so it doesn't feel
oppressive, but it's also

1830
01:55:44,610 --> 01:55:48,210
everybody at the same time gets
everybody we have a shared

1831
01:55:48,210 --> 01:55:51,360
vision. A really life. This
feels really good. It's not been

1832
01:55:51,360 --> 01:55:53,190
like anything I've ever
experienced before.

1833
01:55:53,640 --> 01:55:57,120
Even Elon Musk could not hire
this team. That's the way I see.

1834
01:55:57,360 --> 01:56:01,230
No, effing way. No way. All
right, Dave, you good man. You

1835
01:56:01,230 --> 01:56:02,520
good for the weekend. Everything
cool.

1836
01:56:03,150 --> 01:56:06,360
Yep. Yeah, I'm good, man. I'm
gonna head back to the office

1837
01:56:06,360 --> 01:56:09,990
and finish out the day and then
and then memory for the weekend.

1838
01:56:10,019 --> 01:56:12,239
John Spurlock back to the
penthouse.

1839
01:56:13,980 --> 01:56:19,830
Back to the OP three dungeon to
actually work here. So anyone

1840
01:56:19,830 --> 01:56:20,130
that wants

1841
01:56:20,130 --> 01:56:21,270
to take lots of meat.

1842
01:56:23,160 --> 01:56:27,090
Take ad op 3d or feeds folks.
Thanks. We'll have something to

1843
01:56:27,090 --> 01:56:27,960
show in a few weeks.

1844
01:56:28,019 --> 01:56:30,899
Thanks again for your time,
John. Really appreciate it. Yep,

1845
01:56:30,899 --> 01:56:33,089
thanks. Yeah, absolutely.
Anytime, and everybody in the

1846
01:56:33,089 --> 01:56:35,189
chat room. Thank you very much
for being with us here on this

1847
01:56:35,189 --> 01:56:40,709
last episode podcasting.
2.1 2.1 2.0 no meetings except

1848
01:56:40,709 --> 01:56:43,619
for one the board meeting every
Friday Friday. We'll see you

1849
01:56:43,619 --> 01:56:44,819
here next week. Bye bye.

1850
01:57:01,470 --> 01:57:06,030
You have been listening to
podcasting 2.0 Visit podcast

1851
01:57:06,030 --> 01:57:08,610
index.com. For more information