1
00:00:00,510 --> 00:00:05,820
podcasting 2.0 for December
18 2020, Episode 16 and we're in

2
00:00:05,820 --> 00:00:07,050
the fourth quarter Batman.

3
00:00:09,929 --> 00:00:15,089
Got to add a little baby to it.
It is Friday once again Time for

4
00:00:15,089 --> 00:00:21,569
a board meeting of podcast
index.org reviewing the week's

5
00:00:21,569 --> 00:00:26,519
happenings in podcasting 2.0 I'm
Adam curry in Austin, Texas and

6
00:00:26,519 --> 00:00:29,969
now the man who put Frederick's
podcast on the map Mr. Southern

7
00:00:29,969 --> 00:00:32,489
bred himself, James Jones.

8
00:00:33,780 --> 00:00:34,740
Hey, guys.

9
00:00:34,770 --> 00:00:38,070
Hey, guys. Have you been?

10
00:00:39,450 --> 00:00:42,570
Yeah, I've got a complete new
direction for the show. We're

11
00:00:42,570 --> 00:00:43,770
gonna fix this show.

12
00:00:44,249 --> 00:00:46,739
And we're gonna we're gonna
start by saying Hey, guys.

13
00:00:47,010 --> 00:00:50,010
Yes. So we're gonna turn this
we're gonna turn this into a six

14
00:00:50,010 --> 00:00:55,260
figure podcast. overnight. Start
with Hey, guys.

15
00:00:55,260 --> 00:00:56,550
Hey, guys. Yeah,

16
00:00:56,580 --> 00:00:59,850
in five minutes of talking
inside baseball, just about

17
00:00:59,850 --> 00:01:01,980
stuff that people don't
understand about ourselves.

18
00:01:02,310 --> 00:01:06,060
Yeah, then 10 minutes of talking
about what we're going to talk

19
00:01:06,060 --> 00:01:09,000
about. Yeah, and then and then
an ad roll.

20
00:01:09,540 --> 00:01:10,080
Mid roll.

21
00:01:10,950 --> 00:01:14,280
Mid roll. Yeah. Then Then the
content which only maybe like

22
00:01:14,280 --> 00:01:20,070
maybe five minutes. In essence a
bunch of times for people to

23
00:01:20,070 --> 00:01:21,060
subscribe.

24
00:01:21,180 --> 00:01:23,160
Yeah, we can't really point to
the bottom the screen because

25
00:01:23,160 --> 00:01:26,250
it's smash that subscribe
button, guys.

26
00:01:26,670 --> 00:01:30,000
Yes, smash. Smash the subscribe
button. You got to do that at

27
00:01:30,000 --> 00:01:30,420
least.

28
00:01:33,180 --> 00:01:37,020
If I might say asking people to
boost the podcast on Sphinx chat

29
00:01:37,020 --> 00:01:41,220
is not much different from
asking. Smash subscribe. is

30
00:01:41,220 --> 00:01:45,480
pretty douchey it's in the same
league. And definitely. Yeah.

31
00:01:45,480 --> 00:01:46,170
How are you doing, man?

32
00:01:46,830 --> 00:01:51,090
I'm pretty good. Yeah, good. Um,
I'm feeling good. This is a good

33
00:01:51,090 --> 00:01:51,540
Friday.

34
00:01:52,049 --> 00:01:52,949
Oh, well, that's nice.

35
00:01:53,700 --> 00:01:55,380
It's just the two of us. No
guests.

36
00:01:55,470 --> 00:01:59,040
Yeah. And it's hard to catch up
when we when we have a guest.

37
00:01:59,040 --> 00:02:02,430
And I guess any of the guests
are hanging because, you know, I

38
00:02:02,430 --> 00:02:05,820
don't have a production
assistant who could who could

39
00:02:05,820 --> 00:02:10,500
dial them in when appropriate.
So I'm very, you know, I'm very

40
00:02:10,500 --> 00:02:13,260
aware that just sitting there
listening along, going. Okay,

41
00:02:13,260 --> 00:02:14,190
what is our turn?

42
00:02:14,520 --> 00:02:18,000
She's saying that song. Just the
two of the just

43
00:02:18,029 --> 00:02:21,839
the winners. The winners. Okay.
That's right. I

44
00:02:21,840 --> 00:02:24,930
was thinking in my head. I was
thinking Billy ocean? No, no.

45
00:02:26,490 --> 00:02:29,280
The Fabulous Bill Withers he
passed away this year.

46
00:02:30,029 --> 00:02:32,189
Yeah, like, was in March or
something like that in March?

47
00:02:32,969 --> 00:02:35,339
During the Rona. I think,

48
00:02:35,369 --> 00:02:38,579
yeah. Yeah. Everybody's posting
old pictures of him, like from

49
00:02:38,579 --> 00:02:42,269
the 70s. And I'm like, that's a
good looking man right there.

50
00:02:43,979 --> 00:02:45,629
You know, he's, he had it going
on. He

51
00:02:45,630 --> 00:02:52,440
was the 70s kind of guy. And he
had it all going on. Exactly. So

52
00:02:52,440 --> 00:02:58,080
I hope you well, things are
good. It's been really busy with

53
00:02:58,080 --> 00:03:01,080
no agenda, obviously, just, you
know, tracking all the stuff

54
00:03:01,080 --> 00:03:04,200
that's happening right now. But
in the meantime, I made a very

55
00:03:04,200 --> 00:03:09,930
brave move, and decided to
really give graphene OS a go as

56
00:03:09,930 --> 00:03:11,070
my daily driver.

57
00:03:11,880 --> 00:03:15,450
Yeah, yeah. Tell me about that.
Because you were you were

58
00:03:15,480 --> 00:03:16,920
texting me saying this is great.

59
00:03:17,130 --> 00:03:21,150
Yeah, there's only one
processor. It's loaded. One of

60
00:03:21,210 --> 00:03:26,370
one of our producers loaded this
on a pixel two. Now I had

61
00:03:26,370 --> 00:03:30,270
replaced the battery. And I knew
that the previous battery was

62
00:03:30,270 --> 00:03:34,620
completely crap, it would run
down in like 45 minutes. And I

63
00:03:34,620 --> 00:03:36,870
had the battery replaced, I
shouldn't say I replace it how

64
00:03:36,870 --> 00:03:40,500
to replace because you have to
be cracked open. And I think

65
00:03:40,530 --> 00:03:43,170
even had to replace it wasn't
worth it in the last class to

66
00:03:43,170 --> 00:03:47,010
replace the screen and and get a
new battery. And it works never

67
00:03:47,010 --> 00:03:47,640
works, right?

68
00:03:47,670 --> 00:03:50,730
Isn't it like it? Well, it
works, right? But when you crack

69
00:03:50,730 --> 00:03:53,730
a phone open and have to like re
glue it and all that jazz yet.

70
00:03:53,880 --> 00:03:57,780
Like it never fits back together
exactly the way it did for the

71
00:03:57,780 --> 00:03:58,350
factory.

72
00:03:58,469 --> 00:04:01,409
Well, I just didn't i didn't
have it from the factory. I

73
00:04:01,409 --> 00:04:07,259
can't speak. But but the but the
battery still runs down pretty

74
00:04:07,259 --> 00:04:09,659
quickly. And it didn't because I
had this thing in the drawer

75
00:04:09,659 --> 00:04:12,869
just laying around. I'd messed
around with it. And I decided

76
00:04:12,869 --> 00:04:14,549
you know what, I'm going to give
it a real go. I'm going to

77
00:04:14,549 --> 00:04:17,309
customize it. I'm going to
install stuff, see if it'll

78
00:04:17,309 --> 00:04:23,069
work. And I'm I'm blown away by
how fast it is. How intuitive

79
00:04:23,069 --> 00:04:28,649
Some things are much more
intuitive than than iOS. And for

80
00:04:28,649 --> 00:04:31,349
the first time I can really use
some of the web apps, the

81
00:04:31,349 --> 00:04:35,129
progressive web apps that are
podcasting 2.0 compliant, not

82
00:04:35,129 --> 00:04:38,999
that I couldn't use them on iOS,
but now you play it and you just

83
00:04:38,999 --> 00:04:42,239
put it in the background or you
lock the lock the device and it

84
00:04:42,239 --> 00:04:45,029
keeps playing. That's really
nice.

85
00:04:46,080 --> 00:04:50,610
What's the screen is it never
had a pixel. I don't know what

86
00:04:51,300 --> 00:04:54,420
it's not to be like, Is it a big
one? No, no, no, no, no, it's

87
00:04:54,420 --> 00:04:57,210
the size of the iPhone seven.
Actually. It's just a little bit

88
00:04:57,210 --> 00:04:57,990
bigger than that.

89
00:04:58,619 --> 00:05:01,859
That's a good size. The gigantic
No, I

90
00:05:01,860 --> 00:05:06,600
had those. It doesn't work out.
It's like an after you've had a

91
00:05:06,630 --> 00:05:09,510
smaller phone for a while and
you put one of those big ones in

92
00:05:09,510 --> 00:05:13,080
your hands like what was I
thinking? Yeah, why not? Yeah.

93
00:05:13,110 --> 00:05:14,610
Why did I ever want this?

94
00:05:15,000 --> 00:05:16,980
Especially if you have to take a
phone calls like holding them.

95
00:05:17,010 --> 00:05:18,540
It's like holding a laptop to
your head.

96
00:05:19,620 --> 00:05:25,320
And iPad. Exactly, yeah. But
it's, that's, that's really been

97
00:05:25,440 --> 00:05:26,250
pleasant

98
00:05:26,850 --> 00:05:30,870
to have. Cuz you can't hook it
up to a screen though. Right? He

99
00:05:30,870 --> 00:05:34,410
said, You have to get like a.
Yeah. hook it up to like a

100
00:05:34,410 --> 00:05:34,920
monitor.

101
00:05:34,950 --> 00:05:39,210
Yes. So it has full on keyboard
and mouse support out of the box

102
00:05:39,210 --> 00:05:45,720
through Bluetooth, which is very
interesting. Using I use the K

103
00:05:45,720 --> 00:05:49,800
nine email app, which is open
source has been around forever,

104
00:05:49,980 --> 00:05:53,640
but it has all the key commands,
the shortcuts already pre

105
00:05:53,640 --> 00:05:58,170
programmed. So you hit r goes to
reply, you know, even Alt Tab

106
00:05:58,170 --> 00:06:01,950
works if you want to switch
between applications. This is

107
00:06:02,070 --> 00:06:05,640
surprisingly good. Yeah, it's
really that's well, it's quite

108
00:06:05,640 --> 00:06:09,360
cool. And so in the three and
the four, I guess, the five, but

109
00:06:09,360 --> 00:06:13,590
the graphene is not been adapted
for the five yet, nor do I want

110
00:06:13,590 --> 00:06:19,710
a 5g handset. Apparently, the
HDMI out works and they have

111
00:06:19,710 --> 00:06:23,700
floating windows. So you can
drag windows around on your

112
00:06:23,730 --> 00:06:27,420
secondary monitor on a phone.
That's pennis. I

113
00:06:27,419 --> 00:06:28,289
mean, now now

114
00:06:28,290 --> 00:06:30,750
you're getting very close to
what I was trying to do with a

115
00:06:30,750 --> 00:06:34,500
Linux phone. Because you know,
you can you can, there's all

116
00:06:34,500 --> 00:06:37,560
kinds of apps that give you a
command line, and I guess it's

117
00:06:37,560 --> 00:06:42,090
some really minimalistic Linux
install, you can get some stuff

118
00:06:42,090 --> 00:06:45,990
working, you know. So we'll see.
It's fun. And I mean,

119
00:06:46,260 --> 00:06:50,100
even if you used it for just a
remote, like, if you had another

120
00:06:50,100 --> 00:06:53,310
machine set up, let's just say
you had your desktop running as

121
00:06:53,310 --> 00:06:56,820
a cloud, you know, like a VM and
a cloud somewhere. And then you

122
00:06:56,820 --> 00:07:00,120
just use right here like remote
access and sure thing from

123
00:07:00,120 --> 00:07:02,460
wherever you were, yes, cool.
Yeah, I

124
00:07:02,460 --> 00:07:05,100
already have that I have a
remote machine that that updates

125
00:07:05,100 --> 00:07:08,160
automatically with whatever I
have in mind, my Linux laptop.

126
00:07:09,840 --> 00:07:11,970
And that works really well. So
you just you know, you're

127
00:07:11,970 --> 00:07:16,020
outside, just SSH in good to go.
That works surprisingly well.

128
00:07:16,020 --> 00:07:20,610
I'm in and what was beautiful is
after so within one week after

129
00:07:20,610 --> 00:07:24,420
speaking about some features
that I would love to see from

130
00:07:24,600 --> 00:07:30,360
from all of our apps that Martin
had already integrated my my top

131
00:07:30,360 --> 00:07:34,500
two, which was a latest
episodes, which is working

132
00:07:34,500 --> 00:07:38,280
beautifully. So I don't have to
you know, I can see what

133
00:07:38,280 --> 00:07:41,010
podcasts update he kind of
already had that. But now hey,

134
00:07:41,010 --> 00:07:44,640
here's all the new episodes in
chronological order. That's very

135
00:07:44,640 --> 00:07:50,310
handy. And the Share, share with
the time code. And today we

136
00:07:50,310 --> 00:07:55,830
discovered that he didn't even
know about the the share panel

137
00:07:55,830 --> 00:07:58,830
that apparently can be accessed
with I guess some CSS or

138
00:07:58,830 --> 00:08:02,670
something. So it's really
becoming an incredibly

139
00:08:02,670 --> 00:08:05,430
functional app. Because now I
mean, I have all the things I

140
00:08:05,430 --> 00:08:08,550
want all the almost I think
everything that overcast does,

141
00:08:08,790 --> 00:08:12,390
and of course, overcast I don't
have it on this phone. And so

142
00:08:12,390 --> 00:08:14,430
right now pod friend is looking
pretty good.

143
00:08:15,990 --> 00:08:19,500
So it's a pw a so you can just
pin it right to your home screen

144
00:08:19,500 --> 00:08:21,900
like a regular app. Exactly.
Yeah. In fact, I've

145
00:08:21,900 --> 00:08:26,610
little folder of all of all of
the 2.0 app because each one has

146
00:08:26,610 --> 00:08:32,430
something a little different. So
I like was it pod verse has the

147
00:08:33,330 --> 00:08:34,560
a lot of clips.

148
00:08:36,420 --> 00:08:38,130
Yeah, I got a clip for barbers
today.

149
00:08:39,000 --> 00:08:39,840
Which one is it?

150
00:08:41,069 --> 00:08:46,019
Uh, it is. Well, gosh, what
would you ask me? It's the one

151
00:08:46,019 --> 00:08:49,619
that I think is clip. Done. And
this is say something about

152
00:08:49,619 --> 00:08:56,909
dynamic ads. A clip to clip.
One, maybe? podcasts are cool.

153
00:09:00,060 --> 00:09:03,960
That's not necessarily the one
but who are these podcasts and

154
00:09:03,960 --> 00:09:07,110
Mama knows Oh, mama knows best
ads? Yeah, no, it's

155
00:09:07,110 --> 00:09:09,840
not. No, it's not that one. It's
the other one. Okay. It's what

156
00:09:09,840 --> 00:09:11,760
are these podcasts? That's it.
All right, hold

157
00:09:11,760 --> 00:09:12,420
on a second. Here.

158
00:09:12,420 --> 00:09:16,770
We're saying they also of
course, have tons of

159
00:09:16,770 --> 00:09:20,880
advertising. The advertising is
off the charts on the shoulder.

160
00:09:20,880 --> 00:09:23,160
But what am I mean, it's it's
funny you talk about the

161
00:09:23,160 --> 00:09:25,590
advertising because I don't know
if you listened to the cats

162
00:09:25,590 --> 00:09:29,070
episode. Maybe you did. I did. I
did. It's It's nearly two hours

163
00:09:29,070 --> 00:09:32,370
long. Yeah. So they play this
little stingers when ads will

164
00:09:32,370 --> 00:09:34,800
play and I'm wondering if they
might be in trouble because

165
00:09:34,800 --> 00:09:38,550
listen to what they left in this
show, play my number 12 they

166
00:09:38,550 --> 00:09:45,960
have to add breaks. Can I just
bring up one thing here too? Hot

167
00:09:45,960 --> 00:09:46,320
airberlin.

168
00:09:48,960 --> 00:09:50,400
Let's get to the questions here
from the crowd

169
00:09:50,400 --> 00:09:54,930
because I'm glad you could edit
that stuff out. Like No, no, no,

170
00:09:54,930 --> 00:09:57,750
no. I'm glad you picked up on
this because I'll tell you

171
00:09:57,750 --> 00:10:00,720
what's happening here. This is a
newer funnel. Now we're gonna

172
00:10:00,720 --> 00:10:04,080
see more and more as we start to
review these shows what the feed

173
00:10:04,080 --> 00:10:06,870
that you get is different than
the feed that I get. I listened

174
00:10:06,870 --> 00:10:10,740
to it through my app. And that
was what I heard as well. And

175
00:10:10,740 --> 00:10:13,980
then I downloaded it from Apple
podcasts in order to clip it.

176
00:10:14,160 --> 00:10:17,010
And there was an ad in there.
It's dynamic insertion. So

177
00:10:17,010 --> 00:10:20,040
they're putting in timestamps.
And then if there is an ad to

178
00:10:20,040 --> 00:10:22,590
serve to somebody based on who
you are, they'll put an ad in

179
00:10:22,590 --> 00:10:25,290
there if there isn't, that's
really a weird, obnoxious thing,

180
00:10:25,290 --> 00:10:26,910
where it's just like this empty
ad spot.

181
00:10:27,090 --> 00:10:31,500
Oh, my goodness. I wonder, I
wonder who's, who's selling that

182
00:10:31,500 --> 00:10:33,720
I wonder who's doing the dynamic
insertion?

183
00:10:34,560 --> 00:10:36,870
I don't know. wasn't clear from
what they were saying. But like,

184
00:10:36,870 --> 00:10:41,340
you can see the he can see the
danger of putting the stinger on

185
00:10:41,340 --> 00:10:44,400
either side of your ad of your
ad roll. And then there's no ad.

186
00:10:44,430 --> 00:10:48,870
It's, like, mentally jarring
thing. Whoa, what just happened?

187
00:10:48,870 --> 00:10:49,320
Yeah.

188
00:10:49,890 --> 00:10:53,430
So so. And I've been thinking
about this. And you know, the

189
00:10:53,430 --> 00:10:59,250
conversation is everywhere. Is
there a way that we can do

190
00:10:59,250 --> 00:11:09,330
anything with the index to make
this easier or to benefit? to

191
00:11:09,330 --> 00:11:14,850
benefit anybody who wants to do
ads? I don't want if there's a

192
00:11:14,850 --> 00:11:17,400
way for the index to help if
there's something that can be

193
00:11:17,400 --> 00:11:21,570
provided, that would make stuff
easier? And I'm just throwing it

194
00:11:21,570 --> 00:11:26,490
out there. I mean, I don't want
to add the whole idea of Bitcoin

195
00:11:26,490 --> 00:11:31,530
lightning is perpendicular to
that, but I want to stay open to

196
00:11:31,530 --> 00:11:34,650
being able to help. Well,
there's something about stats.

197
00:11:35,220 --> 00:11:36,330
Was there something you were
telling me

198
00:11:36,330 --> 00:11:40,620
that was going on about stats?
Yeah, we've been telling you

199
00:11:40,620 --> 00:11:45,210
that I had had conversations, a
couple conversations this past

200
00:11:45,570 --> 00:11:49,440
two weeks with some posters, and
they were both just expressing

201
00:11:49,440 --> 00:11:55,800
frustration about stats about
just the whole IBC process. And

202
00:11:56,940 --> 00:12:00,840
how that how difficult it is and
how stupid expensive it is.

203
00:12:01,350 --> 00:12:02,010
Well, that's,

204
00:12:02,040 --> 00:12:04,410
that's, that's how it works.
That's I mean, that's the

205
00:12:04,410 --> 00:12:07,920
Nielsen model is come up with
the standard, get everybody to

206
00:12:07,920 --> 00:12:10,710
buy in, and then have them pay
you to be member of the

207
00:12:10,710 --> 00:12:13,380
standards group that so you get
the reports, right.

208
00:12:14,160 --> 00:12:17,310
Yeah, I mean, that's totally
what this is. And you if you're

209
00:12:17,310 --> 00:12:20,610
a host of any size, you're
paying well into five figures.

210
00:12:21,330 --> 00:12:25,680
Wow. I don't know how high that
goes. Is it based on on your

211
00:12:26,339 --> 00:12:27,989
What? How do they base that?

212
00:12:28,770 --> 00:12:33,750
I hadn't really had no idea.
And, you know, I don't I don't

213
00:12:33,750 --> 00:12:36,900
want to give any real, real
fate. Well,

214
00:12:38,070 --> 00:12:41,190
we can't we can't even ask any
of our hosting buddies about

215
00:12:41,190 --> 00:12:44,340
this publicly, because I'm sure
it's all sensitive.

216
00:12:46,260 --> 00:12:53,190
Yeah, yeah. But they were. They
were like, Well, you know, the

217
00:12:53,220 --> 00:12:56,460
guys are talking to is like,
it's just, it's just kind of the

218
00:12:56,460 --> 00:13:00,060
whole thing is a little bit
disconcerting, because for what

219
00:13:00,060 --> 00:13:05,520
you get, it's like, what you get
for the money? Is, is kind of

220
00:13:05,520 --> 00:13:10,830
not. And let me let me stop. I
don't I don't I'm not throwing a

221
00:13:10,830 --> 00:13:13,680
baby or any nest. I mean, I
don't know when even enough

222
00:13:13,680 --> 00:13:19,140
about it. I'm still making my
way through the IB. spec. So I

223
00:13:19,140 --> 00:13:24,630
mean, I'm not going to speak
competently enough to criticize

224
00:13:24,630 --> 00:13:29,040
or anything like that. But, you
know, we know already. So I'm

225
00:13:29,040 --> 00:13:33,450
coming at it from a couple of
standpoints. We know from recent

226
00:13:33,450 --> 00:13:37,950
experience, that standard by
standards bodies and working

227
00:13:37,950 --> 00:13:45,420
groups in podcasting, or slow
roll, and they never get much

228
00:13:45,420 --> 00:13:52,170
accomplished. Yeah, it's fairly
obvious. Yeah. Yes. And I think

229
00:13:52,170 --> 00:13:55,500
there's not I think there's a
very good reason for that. It's,

230
00:13:56,160 --> 00:13:58,680
whenever you put together a
standards body, and especially

231
00:13:58,680 --> 00:14:01,380
when there's money involved, a
lot of money involved, and

232
00:14:01,380 --> 00:14:05,160
there's memberships and all
these sorts of things. There's a

233
00:14:05,160 --> 00:14:10,830
natural tendency for gatekeeping
Mm hmm. And the gatekeeper. When

234
00:14:10,830 --> 00:14:15,180
you start gatekeeping, you have
older established players that

235
00:14:15,180 --> 00:14:17,340
are in that market. They're
usually the ones who are on

236
00:14:17,340 --> 00:14:20,040
these boards and these working
grants, they are experts

237
00:14:20,040 --> 00:14:20,880
at gatekeeping.

238
00:14:21,390 --> 00:14:24,450
experts in every field, this is
not just podcasting, every

239
00:14:24,450 --> 00:14:30,810
industry is this way. And once
you have a group of sort of old

240
00:14:30,810 --> 00:14:33,750
established gatekeepers that are
running these these nonprofits

241
00:14:33,750 --> 00:14:36,930
and these working groups and
that kind of thing. There's

242
00:14:36,930 --> 00:14:41,580
really not that much impetus for
progress. Because they're kind

243
00:14:41,580 --> 00:14:46,020
of steering the whole the ship
and so the young, the sort of

244
00:14:46,020 --> 00:14:51,120
younger and more in smaller and
more aggressive competitors in

245
00:14:51,120 --> 00:14:54,000
that in whatever market that's
in, they're always going to want

246
00:14:54,000 --> 00:14:58,320
to move faster. But they can't
you know, because the the sort

247
00:14:58,320 --> 00:15:02,760
of whales are in or driving the
ship. And so I think I mean,

248
00:15:02,790 --> 00:15:06,660
podcasting is is, is prominent
that just like every industry is

249
00:15:06,660 --> 00:15:11,190
there's going to be large
working groups that take forever

250
00:15:11,190 --> 00:15:15,840
to make decisions. I mean, you,
you know, with the namespace,

251
00:15:15,840 --> 00:15:20,310
it's, we're, you know, half
halfway to phase two already.

252
00:15:20,310 --> 00:15:23,340
And that's something that
probably would have taken

253
00:15:23,340 --> 00:15:25,260
Working Group, you know, five
years.

254
00:15:25,500 --> 00:15:29,190
Well, no, it took working groups
multiple years. And that didn't

255
00:15:29,190 --> 00:15:35,760
happen. And I've been told in
confidence. So I, I don't want

256
00:15:35,760 --> 00:15:39,000
to bust anybody. But it'll be
news eventually, that another

257
00:15:39,000 --> 00:15:45,540
large podcast host is going to
jump on board and add in support

258
00:15:45,540 --> 00:15:47,220
all of the namespace tags.

259
00:15:47,880 --> 00:15:48,960
Now, that's great. Yeah.

260
00:15:49,320 --> 00:15:53,850
So so we know, that's the kind
of stuff where

261
00:15:55,140 --> 00:15:57,510
we already have almost 100,000
feeds out there in the wild that

262
00:15:57,510 --> 00:16:01,380
are supporting the namespace
tags. So another big host jumps

263
00:16:01,380 --> 00:16:03,600
on board. I mean, that's just
you're talking about now you're

264
00:16:03,690 --> 00:16:05,340
on that roll, you know, momentum
rolling.

265
00:16:05,400 --> 00:16:10,170
Exactly. And and then it's up to
any podcast developer, whether

266
00:16:10,170 --> 00:16:14,250
you're doing a progressive web
app, or whether you're Apple,

267
00:16:14,670 --> 00:16:17,700
and honestly, Spotify, but I
don't think that that nimble

268
00:16:17,700 --> 00:16:20,100
that they're trying to figure
out the ad stuff, make that all

269
00:16:20,100 --> 00:16:25,260
work trying to get the audience
side working. Yeah. Which brings

270
00:16:25,260 --> 00:16:28,530
me back to my community
features, because that's where

271
00:16:28,530 --> 00:16:33,210
we're going to crush it. Once we
have that, we can really, really

272
00:16:33,210 --> 00:16:37,470
crush it if we can figure out
how that would work. Did Did you

273
00:16:37,470 --> 00:16:38,010
see that?

274
00:16:38,040 --> 00:16:42,030
Did you read that article? Has
independent podcasting. Pete,

275
00:16:42,090 --> 00:16:42,720
did you read that?

276
00:16:43,170 --> 00:16:47,730
I skimmed it. I the minute I saw
it, I was like, what's the

277
00:16:47,760 --> 00:16:48,990
what's the gist? Yeah.

278
00:16:49,320 --> 00:16:51,480
Well, I mean, it's probably what
you think goes

279
00:16:51,810 --> 00:16:54,960
to the money go to the money's
Don't Don't be independent.

280
00:16:56,460 --> 00:16:59,430
It's not it's not No, it's not
that bad. It's it's not that bad

281
00:16:59,430 --> 00:17:03,600
really isn't? It's, it's more.
It's something that caught my

282
00:17:03,810 --> 00:17:09,030
attention was, he says in here
in the podcasting ecosystem, has

283
00:17:09,030 --> 00:17:12,090
enormous strengths. It's open,
it's flexible, it could easily

284
00:17:12,090 --> 00:17:15,870
become interactive. And I think
that's what we're trying to do.

285
00:17:15,900 --> 00:17:18,510
We're trying to make it
interactive. And whether it's

286
00:17:18,540 --> 00:17:21,990
lightning or whether it's just
something as simple as chapters

287
00:17:21,990 --> 00:17:24,930
and all that kind of stuff. The
interactivity has always been

288
00:17:24,930 --> 00:17:27,660
there. It's nice to see
somebody, you know, write that

289
00:17:27,660 --> 00:17:29,370
in print in a way that's clear.

290
00:17:30,600 --> 00:17:35,430
Did I see someone on podcast
index post about some, some idea

291
00:17:35,490 --> 00:17:40,800
of sending input data from one
app to the other?

292
00:17:42,480 --> 00:17:45,720
I think what Yeah, okay, if
you're talking about how you

293
00:17:45,720 --> 00:17:49,560
talk about like, x, or not
exporting, but like, where you

294
00:17:49,560 --> 00:17:54,120
are in a podcast, if you're, if
you've listened to 30 minutes of

295
00:17:54,120 --> 00:17:57,750
this podcast, to a different
app, pick it up? Yeah.

296
00:17:58,260 --> 00:18:01,770
Well, if we have no, we have if
we have that, how does that

297
00:18:01,770 --> 00:18:02,700
mechanism work?

298
00:18:04,080 --> 00:18:09,060
I have no idea. Like, that's
work, you just got to figure it

299
00:18:09,060 --> 00:18:09,660
out, you know?

300
00:18:10,230 --> 00:18:12,330
Well, somewhere you're gonna
we're gonna need services.

301
00:18:12,330 --> 00:18:15,090
Correct. We're gonna need a
service. If you want to have

302
00:18:15,570 --> 00:18:19,740
community chapters that can be
input to from any app, you're

303
00:18:19,740 --> 00:18:22,710
gonna need some some service
that does something in the

304
00:18:22,710 --> 00:18:28,740
middle. Mm, link linkers. Link
blink services like glue, a way

305
00:18:28,740 --> 00:18:32,010
to glue things together. Okay,
just had I had a brain fart,

306
00:18:32,010 --> 00:18:41,010
here you go. All right. Daniel
J, pay attention. Isn't this

307
00:18:41,700 --> 00:18:47,820
something that would be new,
that would make sense to create

308
00:18:47,820 --> 00:18:52,860
some kind of standard? Maybe
it's a tag, I don't know. But

309
00:18:52,860 --> 00:18:57,330
it's a community server. And
maybe this community server is

310
00:18:57,330 --> 00:19:04,530
no more than Here comes a JSON
file. That that has pointers to

311
00:19:04,530 --> 00:19:08,400
a whole bunch of different
things. So for instance, I

312
00:19:08,400 --> 00:19:12,300
believe it will be incredibly
simple. Here's this is Adams

313
00:19:12,300 --> 00:19:19,650
dumb thinking, if I had a web
app, a web podcast web app, I

314
00:19:19,650 --> 00:19:25,260
would probably fire up an IRC
server, which means I have a lot

315
00:19:25,260 --> 00:19:28,050
of experience using them not
setting them up and not running

316
00:19:28,050 --> 00:19:33,870
them. That could literally have
a different channel for each

317
00:19:33,870 --> 00:19:38,580
individual podcast. And there's
so much web code available for

318
00:19:38,580 --> 00:19:43,350
IRC that you could easily create
and, or someone could host

319
00:19:43,350 --> 00:19:48,060
themselves, an IRC server that
you tie every single app into.

320
00:19:48,780 --> 00:19:51,930
And that could be referenced or
you know, whatever data you need

321
00:19:51,930 --> 00:19:55,980
that might come from one
external JSON that is like

322
00:19:55,980 --> 00:19:59,520
third, third parties, third
services or something, we need a

323
00:19:59,520 --> 00:20:05,730
way to create communicate, how
to tie into something that can

324
00:20:05,760 --> 00:20:10,710
that can make these
dysfunctionality happen. So

325
00:20:10,710 --> 00:20:16,260
whether it's an IRC server or a
Sphinx chat tribe, it shouldn't

326
00:20:16,260 --> 00:20:20,700
matter the feature or something
should be able to tell an app.

327
00:20:20,730 --> 00:20:22,560
Okay, here's how we do chat.

328
00:20:24,390 --> 00:20:31,200
Oh, okay. So your light cross,
so I can have I guess I threw

329
00:20:31,200 --> 00:20:36,210
in all the JSON crap, just for
effect, but I guess you don't

330
00:20:36,210 --> 00:20:39,570
really need it. But you
understand what I'm saying? It's

331
00:20:39,570 --> 00:20:43,800
like an act. I think I do IRC is
the is the simplest, anybody can

332
00:20:43,800 --> 00:20:47,010
set one up, you can rent them
everywhere, you can set it up on

333
00:20:47,010 --> 00:20:53,970
a crappy ass box that runs on
five bucks a month. And it's

334
00:20:53,970 --> 00:20:58,140
universal interface into it,
which any app developer can

335
00:20:58,950 --> 00:21:04,740
modify. I mean, for me, I mean,
and it has registration. There's

336
00:21:05,160 --> 00:21:06,600
all these benefits to it.

337
00:21:08,040 --> 00:21:12,090
So that, okay, so on, that I
know, we're getting off topic of

338
00:21:12,240 --> 00:21:17,490
any sort of topic. But I don't
understand why slack took over

339
00:21:18,060 --> 00:21:23,130
rcma. slack is basically IRC. I
don't I guess I really just

340
00:21:23,130 --> 00:21:25,980
don't understand why slack
became what it is when you work

341
00:21:26,220 --> 00:21:26,520
as a

342
00:21:27,630 --> 00:21:34,860
UX. It's all it's all the user
experience. I mean, why? Why did

343
00:21:35,190 --> 00:21:40,170
follow, take off over subscribe?
Pam is better is just a much

344
00:21:40,170 --> 00:21:43,860
better understanding. Oh, I get
it. I'm following that, when of

345
00:21:43,860 --> 00:21:46,110
course, you're actually doing
something completely different?

346
00:21:47,310 --> 00:21:50,430
Well, if that's the case, and I
think what you're talking about,

347
00:21:51,180 --> 00:21:56,130
is this ability for multiple
apps to coordinate their

348
00:21:56,130 --> 00:22:01,290
experience their podcast user
experience, together, Mm hmm. So

349
00:22:01,290 --> 00:22:07,500
that you have so that I know, as
an app, the, you know, there's,

350
00:22:07,530 --> 00:22:11,910
as I know, there's a pod verse,
I can somehow look at this feed,

351
00:22:12,120 --> 00:22:17,760
and see that that pod friend,
excuse me, is pod verse and look

352
00:22:17,760 --> 00:22:20,430
at the feet and say, okay,
they're chat servers here. So

353
00:22:20,430 --> 00:22:22,860
then pod friend can also look at
their feet and say, the chat,

354
00:22:22,890 --> 00:22:25,230
you know, the chat servers
there. Exactly. They can both be

355
00:22:25,230 --> 00:22:29,370
feeding back to the same thing
from within the app. Yes. Okay.

356
00:22:29,520 --> 00:22:33,360
And and if anyone needs me to
set up an IRC server to test

357
00:22:33,360 --> 00:22:37,980
this, let me know. I'm just
saying that it's universal. I

358
00:22:37,980 --> 00:22:42,840
mean, all of these chat type
apps have a form of web hook

359
00:22:42,840 --> 00:22:46,680
into it. So you know, you can,
you can always create a an

360
00:22:46,680 --> 00:22:48,900
interface around the
functionality as long as and

361
00:22:48,900 --> 00:22:52,110
maybe it's a tag that has to be,
or that should be in the system.

362
00:22:52,290 --> 00:22:56,610
But that's why I'm saying maybe
we do need some kind of cool, I

363
00:22:56,610 --> 00:22:58,710
don't know what belongs in the
in the feet and what doesn't, I

364
00:22:58,710 --> 00:23:01,050
don't know how that works. Some
things are there. Some things

365
00:23:01,050 --> 00:23:01,380
aren't?

366
00:23:01,950 --> 00:23:05,340
Well, you can't eat all these
things have cost games anyway.

367
00:23:05,340 --> 00:23:10,020
So you're, it's like IRC colon
slash slash, win. Right? Right.

368
00:23:10,110 --> 00:23:12,360
You know, and that tells you
Okay, it's an IRC server, or if

369
00:23:12,360 --> 00:23:17,070
it gotcha, maybe Sphinx, thinks
chat, colon slash, Lina. Uh huh.

370
00:23:18,450 --> 00:23:22,020
That just that data in a link,
tell you what you need. Okay.

371
00:23:22,680 --> 00:23:26,760
Well, something like that back.
You know, I can see that being.

372
00:23:26,820 --> 00:23:29,910
And that's just one. That's one
step. You know, now you've

373
00:23:29,910 --> 00:23:33,120
created a connection between all
these app now you've created

374
00:23:33,120 --> 00:23:38,220
something that Apple and Spotify
probably will never do.

375
00:23:40,260 --> 00:23:41,040
I can't know. Okay.

376
00:23:42,120 --> 00:23:45,990
But yeah, no, I mean, and no, I
just don't think that they,

377
00:23:46,050 --> 00:23:49,290
they. I mean, they can do
anything they want, but I don't

378
00:23:49,290 --> 00:23:53,100
think they'll ever focus on
that. And this is, and this is

379
00:23:53,100 --> 00:23:59,490
big. I mean, for no agenda.
There's the troll room. No

380
00:23:59,490 --> 00:24:04,890
agenda stream.com. And that's
just a really bad page that I

381
00:24:04,890 --> 00:24:07,440
just created with the freedom
controller is nothing there and

382
00:24:07,440 --> 00:24:12,300
just has a link and you can open
up a, a web interface to the

383
00:24:12,330 --> 00:24:16,170
chat room. It has a little
player for the live stream. So

384
00:24:16,170 --> 00:24:19,920
it's no different, you know,
just take that code, or take

385
00:24:19,920 --> 00:24:24,630
those those that pointer to that
IRC channel and log them in.

386
00:24:26,400 --> 00:24:32,160
Yeah, I mean, I think that chat
rooms have become like an

387
00:24:32,160 --> 00:24:36,120
integral part of a lot of
podcasts. So I don't see that

388
00:24:36,120 --> 00:24:40,920
it's necessarily such a stretch
to have a task, some sort of tag

389
00:24:40,920 --> 00:24:46,140
for that. Because you've like, I
mean, I can probably there's

390
00:24:46,140 --> 00:24:49,410
probably five I can name off top
my head that have chat rooms.

391
00:24:50,130 --> 00:24:54,360
And if you had some, I guess we
get to a certain size and you

392
00:24:54,360 --> 00:24:58,680
want to have a chat room. You
just spin up an IRC somewhere

393
00:24:58,680 --> 00:25:02,310
and then you just stick it in
Your feed? I don't know where it

394
00:25:02,310 --> 00:25:06,150
would go or how it would be
present. But it seems that seems

395
00:25:06,150 --> 00:25:08,430
like a good deal to me. I mean,
it seems like a worthwhile thing

396
00:25:08,430 --> 00:25:11,550
to me. All right, at least you
have everybody in it, because

397
00:25:11,610 --> 00:25:14,760
because there's our C apps on
phones. So you have, you know,

398
00:25:14,760 --> 00:25:17,880
if you tap the little chat room
chat room link on your podcast

399
00:25:17,880 --> 00:25:20,910
app, it could kick you over to
the IRC for that room.

400
00:25:21,030 --> 00:25:25,980
And here's another Adam Curry
idea. If you are an IRC app

401
00:25:25,980 --> 00:25:31,020
developer, consider baking some
podcast into your IRC app, you

402
00:25:31,020 --> 00:25:37,380
can reverse the process and some
lightning. Yeah, well, I'm on

403
00:25:37,380 --> 00:25:42,060
the lightning. And this is for
streaming, streaming payments,

404
00:25:42,990 --> 00:25:48,510
streaming value for value. We've
had some interesting preliminary

405
00:25:48,510 --> 00:25:52,770
conversations. And I think we're
going to wind up with I don't

406
00:25:52,770 --> 00:25:58,020
know, the timeframe or whatever,
is a way to lightening of phi,

407
00:25:58,620 --> 00:26:03,390
almost any podcast app, really
with just a couple of API calls?

408
00:26:04,470 --> 00:26:06,180
Am I am I correct in saying
that?

409
00:26:06,360 --> 00:26:09,540
Yeah, I think is so what what
it'll what it'll be if this

410
00:26:09,540 --> 00:26:14,460
works out the way we think it
will, will, what it'll be is a

411
00:26:14,460 --> 00:26:17,040
lightning app, there's, let's
give me a lightning wallet

412
00:26:17,070 --> 00:26:22,530
provided by a wallet provide a
lightning wallet provider. And

413
00:26:22,530 --> 00:26:27,330
so then there's an API that you
could hook into, that just says,

414
00:26:27,780 --> 00:26:31,110
the key that just tells you
tells the add the podcast, app

415
00:26:31,110 --> 00:26:34,440
basics, some basic stuff about
what's in the wallet, like your

416
00:26:34,440 --> 00:26:39,000
balance, your you know, an
address, book type deal, just as

417
00:26:39,000 --> 00:26:43,290
a couple of bare bones things is
really all the podcast app would

418
00:26:43,290 --> 00:26:48,570
have to do is just call the API,
maybe set up a new Wallet for

419
00:26:48,570 --> 00:26:50,580
somebody who doesn't have one.
And these are all just some

420
00:26:50,580 --> 00:26:52,830
simple API calls. And all the
heavy lifting is done on the

421
00:26:52,830 --> 00:26:57,720
provider side, then, so when
then all the app is doing the

422
00:26:57,720 --> 00:27:02,160
podcast app is doing is as you
listen, it just pings

423
00:27:02,160 --> 00:27:06,090
periodically to the wallet
provider and says, Hey, this

424
00:27:06,090 --> 00:27:12,390
person's wallet needs to send
this mini SATs to these, these

425
00:27:12,420 --> 00:27:16,920
these, these addresses. Or
probably what's going to happen

426
00:27:16,920 --> 00:27:21,720
more likely is it will say here
is there needs to be a send and

427
00:27:21,720 --> 00:27:23,940
this is what I was thinking
about over the weekend. There

428
00:27:23,940 --> 00:27:27,510
needs to be ascend, ascend needs
to happen or excuse me, like a

429
00:27:27,510 --> 00:27:31,320
payout needs to happen. And you
will, you know, you call it

430
00:27:31,320 --> 00:27:36,510
something like you there's an
API pain that where you will

431
00:27:37,620 --> 00:27:41,640
wear that podcast app says,
okay, trigger the trigger a

432
00:27:41,640 --> 00:27:47,670
payout, a permanent payout for
this feed ID. And then the the

433
00:27:47,670 --> 00:27:53,100
lightning wallet provider has
linkage to the podcast index,

434
00:27:53,580 --> 00:27:56,970
which will say okay, that feed
ID represents these addresses

435
00:27:57,090 --> 00:28:00,840
running it does the payout,
right, because what you don't

436
00:28:00,840 --> 00:28:06,210
want? Okay, well, let me step
back. Because what you further

437
00:28:06,210 --> 00:28:10,410
from the podcast apps developed
the app developer side. This

438
00:28:10,410 --> 00:28:12,570
makes it where they don't have
to bake any lightning stuff in

439
00:28:12,690 --> 00:28:14,220
right? sake.

440
00:28:14,699 --> 00:28:17,699
It's just it's a it's a two
day's worth of work.

441
00:28:19,980 --> 00:28:23,250
Yeah, yeah, pretty much. Yeah.
It's just the the user interface

442
00:28:23,370 --> 00:28:26,310
will be harder than the natural
implementation of the lightning

443
00:28:26,310 --> 00:28:31,170
stuff side. Right. So and then
the reason it would not do

444
00:28:31,170 --> 00:28:41,010
DIRECT address sins from the
app? And is because the podcast

445
00:28:41,040 --> 00:28:44,850
index has all the addresses and
everything in there. Because

446
00:28:44,850 --> 00:28:48,060
we're aggregating the actual
fee, we have we have the the

447
00:28:48,060 --> 00:28:50,190
current split split information.

448
00:28:50,850 --> 00:28:54,720
Yeah, exactly. And we're doing
some verification, like, we

449
00:28:54,720 --> 00:29:00,090
don't take value blocks from
feeds that aren't HTTPS, right?

450
00:29:00,120 --> 00:29:04,290
Things like that. Because so
we're, we're, we're sort of

451
00:29:04,290 --> 00:29:08,880
like, what you want as a trusted
source, so that you make sure

452
00:29:08,880 --> 00:29:13,470
that an app is not going to go
rogue, and just decide to drain

453
00:29:13,470 --> 00:29:17,760
your wallet to some God knows
where, right. So really, the

454
00:29:17,760 --> 00:29:23,040
only action the app can take is
to tell the lightning wallet

455
00:29:23,040 --> 00:29:29,550
provider to send a payment into
this feed. And then at that

456
00:29:29,550 --> 00:29:35,010
point, that feed gets verified
that that is legit, and that the

457
00:29:35,010 --> 00:29:39,060
address is match what we have
and then it triggers it. I think

458
00:29:39,060 --> 00:29:40,590
that's the safest way to do it.
I

459
00:29:40,590 --> 00:29:43,410
like how you know you thought
about that. You've been thinking

460
00:29:43,410 --> 00:29:45,900
about that. That's good. I like
it. Yeah, there

461
00:29:45,900 --> 00:29:48,930
was so we're talking about it
last weekend, you know, when

462
00:29:48,930 --> 00:29:51,570
this came up, and there's
something that was bugging me

463
00:29:51,570 --> 00:29:53,730
about it because I kept drawing
it out on paper trying to figure

464
00:29:53,730 --> 00:29:56,400
out how the linkage was would
work. And I think that's the

465
00:29:56,400 --> 00:29:59,880
missing piece is that I think
the thing that was bugging me is

466
00:29:59,880 --> 00:30:03,510
this There's too much potential
control on the app side to do

467
00:30:03,510 --> 00:30:08,190
what they want. Right? Which you
really, you know, that's, that's

468
00:30:08,190 --> 00:30:09,030
sketchy.

469
00:30:09,660 --> 00:30:13,170
It can it can be Yeah, it can be
I like this. I like how you

470
00:30:13,170 --> 00:30:17,370
separated this in from just from
the user experience side, the

471
00:30:17,370 --> 00:30:22,020
way it will probably work is,
you know, you you bring up a

472
00:30:22,020 --> 00:30:27,540
page or something. There would
be a, there's a better way to do

473
00:30:27,540 --> 00:30:30,660
it on mobile, I think. But in
general, you'd have this

474
00:30:30,840 --> 00:30:35,400
lightning provider wallet, you
scan a QR code, and immediately

475
00:30:35,400 --> 00:30:40,500
you've verified and linked your
lightning wallet to that app.

476
00:30:42,240 --> 00:30:44,970
And then you could start using
the the interface and we can

477
00:30:44,970 --> 00:30:46,440
also do boost then as well.

478
00:30:47,850 --> 00:30:48,780
Oh, that'd be great. Yeah.

479
00:30:49,139 --> 00:30:52,109
Yeah, super easy. Yeah, super
easy. And we can send in the

480
00:30:52,109 --> 00:30:53,879
memo field, you send the
timecode.

481
00:30:55,290 --> 00:31:00,480
Yeah, in that netlist, you have
it. So for people who may not be

482
00:31:00,480 --> 00:31:03,240
following all of this, but you
understand the whole Sphinx

483
00:31:03,240 --> 00:31:07,560
model, think about things in the
way it's set up. So currently,

484
00:31:07,710 --> 00:31:11,700
if you have a Sphinx tribe, and
you host a podcast, they're

485
00:31:11,700 --> 00:31:17,340
yours. Thanks, tribe. By
default, your thinks node is the

486
00:31:17,340 --> 00:31:20,640
receive receiver of all the
permitted sass that you stream,

487
00:31:20,700 --> 00:31:26,490
right. So this would make it
where let's just say you have a

488
00:31:26,490 --> 00:31:29,520
Sphinx tribe. And you that's
your node that's thinks that

489
00:31:29,520 --> 00:31:34,020
thinks tribe is your thinks
lightning node is your node, you

490
00:31:34,020 --> 00:31:37,530
don't have your own personal
one, off, off off site

491
00:31:37,530 --> 00:31:43,260
somewhere, you could then just
list your list your sinks node,

492
00:31:44,040 --> 00:31:46,680
in your value block in your
feed, right, and then these

493
00:31:46,710 --> 00:31:50,280
other apps that are out there
that are straight, and that are

494
00:31:51,330 --> 00:31:53,760
going to become lightning
enabled this other way that we

495
00:31:53,760 --> 00:31:57,300
were talking about, they can
they can see because the index

496
00:31:57,300 --> 00:32:00,960
lists that they can see that
happen in in all those payments

497
00:32:01,050 --> 00:32:03,480
from these other apps will just
continue to go back to your

498
00:32:03,480 --> 00:32:06,780
things node. Because this makes
node really is just a lightning

499
00:32:06,780 --> 00:32:11,160
node. And it can accept
payments. So you're having you

500
00:32:11,160 --> 00:32:14,220
can sort of keep your home based
on things if you like that with

501
00:32:14,220 --> 00:32:17,160
your tribe and your chat and all
that jazz. And that's that's

502
00:32:17,160 --> 00:32:19,650
sort of the best the beauty of,
of the lightning network is that

503
00:32:19,650 --> 00:32:23,040
you any, any node can can talk
to each other, there's no

504
00:32:23,040 --> 00:32:27,720
barriers. They're just siloing.
So you could you could move your

505
00:32:27,720 --> 00:32:30,120
note off site if you wanted to.
But you could also just exempt

506
00:32:30,120 --> 00:32:32,580
status. Thanks. You've already
got maybe, you know, 100

507
00:32:32,580 --> 00:32:34,530
followers on your thanks, tribe.
I mean, you don't want to ditch

508
00:32:34,530 --> 00:32:37,710
that and go to some other
provider for your notes. So you

509
00:32:37,710 --> 00:32:39,780
just stay there and then
redirect everything that yours.

510
00:32:39,780 --> 00:32:43,620
Thanks, note, and this other app
now is streaming back to that

511
00:32:43,620 --> 00:32:48,840
too. And that also may, if you
had if this is this Thanks, guys

512
00:32:48,840 --> 00:32:54,450
would do integration with chat.
Maybe they maybe somehow that

513
00:32:54,450 --> 00:32:55,650
could link back in

514
00:32:56,820 --> 00:32:58,230
bridge, a bridge?

515
00:32:58,710 --> 00:32:59,970
Yeah, like an IRC bridge

516
00:33:00,030 --> 00:33:06,030
with the with the relay with a
relay software. Yeah. I love

517
00:33:06,030 --> 00:33:10,410
this. And you know, we have we
have such a forward motion we

518
00:33:10,410 --> 00:33:13,650
got we got momentum on this. And
I love seeing, you know, people

519
00:33:13,650 --> 00:33:17,190
collaborating and thinking about
it. So you know, here we go.

520
00:33:18,450 --> 00:33:21,780
There's a lot of work left to be
done. And and we can do whatever

521
00:33:21,780 --> 00:33:24,360
the hell we want. We can turn
left or right whenever we want.

522
00:33:25,110 --> 00:33:31,500
Yeah, it's fun. It's it's fun
it. I wonder if they would if

523
00:33:31,500 --> 00:33:34,620
they could do that, because he
thinks could easily integrate

524
00:33:34,620 --> 00:33:37,950
with our senior. I don't mean to
say easily. I don't mean that

525
00:33:37,950 --> 00:33:38,310
unless

526
00:33:39,450 --> 00:33:41,520
you had your developer hat on.
Yeah, I heard you

527
00:33:41,550 --> 00:33:47,310
write. You know, a bit a bit.
That'd be a fun project for

528
00:33:47,310 --> 00:33:51,030
somebody. Definitely write a
write some sort of bridge over

529
00:33:51,120 --> 00:33:55,290
over there to that. Mm hmm. And
then then you're then you're

530
00:33:55,320 --> 00:33:58,680
basically you have a window into
into, into your things? Well, I

531
00:33:58,680 --> 00:34:01,410
mean, I know there's encryption
and all that good stuff. I'm

532
00:34:01,410 --> 00:34:01,950
just dreaming.

533
00:34:02,070 --> 00:34:08,040
Well, to bring it all around to
is independent, podcasting.

534
00:34:08,580 --> 00:34:09,240
peaking?

535
00:34:09,989 --> 00:34:11,669
No, we were talking about stats
where we

536
00:34:11,760 --> 00:34:15,540
Yeah, well. So a, we're just
getting started on it just

537
00:34:15,540 --> 00:34:19,320
getting started. So I don't
think so at all. And the only

538
00:34:19,320 --> 00:34:23,430
thing we've been missing is
great app experiences and value

539
00:34:23,430 --> 00:34:27,060
flow. So we're solving these
issues. And once we have this if

540
00:34:27,060 --> 00:34:33,120
we can we get one of these
wallet providers integrated. It

541
00:34:33,120 --> 00:34:35,670
can scale pretty quick. And then
it's just a matter of saying,

542
00:34:35,670 --> 00:34:40,530
Oh, hey, do this. You know, the
swing swing stuff is fantastic

543
00:34:40,530 --> 00:34:45,510
for that. I see that as a lot of
future in there. I'm very

544
00:34:45,510 --> 00:34:48,780
enamored with running stuff over
the blockchain and no secret

545
00:34:48,780 --> 00:34:52,470
there. Yeah. But we can scale up
and get people going really

546
00:34:52,470 --> 00:34:56,580
quick. And yeah, if there were
an IRC bridge from the Sphinx

547
00:34:56,580 --> 00:34:59,490
chat, oh my goodness but

548
00:35:01,559 --> 00:35:04,559
I was messaging you about the
sad stat stuff the other day.

549
00:35:04,559 --> 00:35:07,709
And you said, your spouse was
like, he can't spell stats

550
00:35:07,709 --> 00:35:08,579
without SATs.

551
00:35:08,610 --> 00:35:11,850
Yeah, exactly. Well, and that
that's the other thing is if we

552
00:35:11,850 --> 00:35:17,460
just come around to the, to the
stats talk. What a great

553
00:35:17,460 --> 00:35:23,100
anonymous. Well, it's kind of an
attribution tracking system. But

554
00:35:23,100 --> 00:35:26,940
it's completely anonymous, which
for real, completely anonymous.

555
00:35:27,510 --> 00:35:31,650
Yeah, but caveats for,
obviously, because there's all

556
00:35:31,650 --> 00:35:34,770
kinds of ways to track people
doing all kinds of stuff. But in

557
00:35:34,770 --> 00:35:38,790
general, and having an actual
listen time, and having an

558
00:35:38,820 --> 00:35:43,410
individualized by each listener
is incredibly valuable.

559
00:35:44,610 --> 00:35:51,870
No, yeah. No. 100%. And that's,
you know, it's probably easier

560
00:35:51,870 --> 00:35:57,480
with the API method from an app.
And it is Oh, yeah, even with

561
00:35:57,480 --> 00:36:01,050
things because then you have,
you know, then the apps, how

562
00:36:01,050 --> 00:36:02,850
about this thing? Wait about?
Yeah,

563
00:36:02,849 --> 00:36:06,359
the app could provide stats to
the to the feed owner.

564
00:36:07,590 --> 00:36:11,430
Okay, well, that's a good way to
get. That's, that's a good segue

565
00:36:11,430 --> 00:36:14,820
into into this idea.

566
00:36:14,880 --> 00:36:15,690
Okay, good.

567
00:36:17,130 --> 00:36:23,070
I'm actually I brought the ABS
sheet here.

568
00:36:24,539 --> 00:36:27,659
By the way, for those of you
who've been following our sexy

569
00:36:27,659 --> 00:36:31,889
namespace talk and talk of
Bitcoin ever since we started

570
00:36:31,889 --> 00:36:38,879
this, Bitcoin is now effectively
doubled. Yeah, it surged 23,000.

571
00:36:38,909 --> 00:36:41,429
I mean, it's it's no coincidence
that this is because of

572
00:36:41,429 --> 00:36:45,539
podcasting. It is. out there,
just putting it out there.

573
00:36:46,470 --> 00:36:55,140
Yeah, I need a GIF of us on top
of a Bitcoin. Precisely. So this

574
00:36:55,200 --> 00:36:59,730
is I'm looking at the ib 2.1.
spec, like I said, or like I

575
00:36:59,730 --> 00:37:05,970
began to say earlier, I'm not,
this has nothing to do. I'm not

576
00:37:05,970 --> 00:37:09,030
criticizing it at all. And we
got just not. That's not the

577
00:37:09,030 --> 00:37:14,340
goal here. But the definite it
says, I just kind of some stuff

578
00:37:14,340 --> 00:37:19,680
stood out to me. This is a
podcast advertisers, this gives

579
00:37:19,680 --> 00:37:23,310
me a podcast offer advertisers,
a hyper focused audience that

580
00:37:23,310 --> 00:37:26,460
chooses to listen to the content
podcast listeners, have been

581
00:37:26,460 --> 00:37:29,490
shown to be the most loyal and
engaged audience of any digital

582
00:37:29,490 --> 00:37:31,470
medium. That's 100%. Right.

583
00:37:31,500 --> 00:37:32,490
I believe that's true.

584
00:37:33,000 --> 00:37:41,310
Yeah. And so the the IB spec,
and this is 2.1 that I'm looking

585
00:37:41,310 --> 00:37:47,220
at, says this document offers a
set of metrics that establish a

586
00:37:47,220 --> 00:37:53,250
mutual understanding in podcast
advertising negotiations. To see

587
00:37:53,310 --> 00:37:58,770
and for the foreseeable future,
log based log based measurement

588
00:37:58,770 --> 00:38:01,740
is the only way to achieve
comprehensive measurement of all

589
00:38:01,740 --> 00:38:06,210
podcast usage. So that's, that's
the way this that's the way this

590
00:38:06,210 --> 00:38:10,890
stuff works. This is all these
podcasts, stats, download

591
00:38:10,890 --> 00:38:13,470
metrics, and those kind of
things are all done based on

592
00:38:13,710 --> 00:38:14,850
basically grip and the locks.

593
00:38:16,409 --> 00:38:20,999
Very little has changed in 25
years. We're still grepping, the

594
00:38:20,999 --> 00:38:22,019
logs everybody.

595
00:38:22,140 --> 00:38:27,300
It's just the regex is are
different. Yeah. It's it. It

596
00:38:27,300 --> 00:38:32,760
says, currently, less than 3% of
the market share enables client

597
00:38:32,760 --> 00:38:35,610
side tracking, as it exists in
other forms in digital

598
00:38:35,610 --> 00:38:41,430
advertising. So you essentially
have less than 3% of the podcast

599
00:38:41,670 --> 00:38:46,050
application of the podcast apps.
Have any sort of client side

600
00:38:46,050 --> 00:38:49,410
tracking exposed back to
advertisers? Sure. Essentially,

601
00:38:49,410 --> 00:38:50,040
zero. Yeah,

602
00:38:50,039 --> 00:38:53,849
I mean, Apple App, Apple's the
only one that I know that that

603
00:38:53,849 --> 00:38:54,749
does any of that.

604
00:38:56,579 --> 00:39:02,189
Yeah. So you have, see, what you
have is a is a is a system where

605
00:39:04,110 --> 00:39:07,560
very, there's hardly any stats
to be given back from the player

606
00:39:07,560 --> 00:39:13,230
side. And then, so what you're
left with is trying to grip

607
00:39:13,770 --> 00:39:19,830
stats out of the logs. And this
gives you a situation where

608
00:39:21,660 --> 00:39:28,560
people gamify it, like crazy. So
you if you go from if you move

609
00:39:28,560 --> 00:39:31,530
your pie, and these are some
some of this, I'm not going to

610
00:39:31,530 --> 00:39:35,490
talk about who I talked to this
past couple weeks. But if you

611
00:39:35,490 --> 00:39:41,310
move from host to host, let's
say you're you started out at

612
00:39:41,340 --> 00:39:45,000
Lipson and then you moved your
podcast, you lose all that

613
00:39:45,000 --> 00:39:47,670
debate and then you moved it to
blueberry. Well, you not only

614
00:39:47,670 --> 00:39:51,510
lose your stats, this you don't
just lose them. They're

615
00:39:51,510 --> 00:39:52,560
completely different.

616
00:39:53,190 --> 00:39:56,310
Oh, yeah. So presentation
everything. Yeah, of course.

617
00:39:56,789 --> 00:40:02,009
The numbers, the numbers say
okay, Let's say that you took,

618
00:40:02,639 --> 00:40:09,569
you know, for a fact that you
moved 99 99% of your audience

619
00:40:09,599 --> 00:40:15,419
from, from your home from your
feed at a cast over to your feed

620
00:40:15,419 --> 00:40:19,649
at at Lipson. When you made the
move, you know that your

621
00:40:19,649 --> 00:40:24,749
audience followed you. But for
some reason, your stats show

622
00:40:25,109 --> 00:40:28,919
completely different numbers now
than they did on the previous on

623
00:40:28,919 --> 00:40:32,669
the previous host. is because
they track numbers differently

624
00:40:32,699 --> 00:40:37,199
even between IB compliant hosts.
The stats don't come across

625
00:40:37,199 --> 00:40:39,239
right all the time. They don't
come across matching.

626
00:40:40,260 --> 00:40:42,390
That doesn't surprise me
obviously.

627
00:40:44,099 --> 00:40:50,789
Yeah. And so. And the reason is
because everybody treats things

628
00:40:50,819 --> 00:40:57,749
slightly different. So, for
instance, there are some bots

629
00:40:57,749 --> 00:41:01,859
out there that download a lot of
mp3. Do you know this because

630
00:41:01,859 --> 00:41:05,369
the show notes gets hammered all
the time. So there's bots out

631
00:41:05,369 --> 00:41:08,099
there that are constantly
downloading this stuff? Well, if

632
00:41:08,099 --> 00:41:11,669
a bot happens to parse your feed
and downloads it in the user

633
00:41:11,669 --> 00:41:16,229
agent string is something like
FFmpeg or some Yeah, some mod.

634
00:41:16,289 --> 00:41:23,609
Right. You, you could there's
hosts that do count that as a as

635
00:41:23,609 --> 00:41:25,169
a an eye Bay compliant download.

636
00:41:25,170 --> 00:41:27,810
Wow. Okay, I can see the
discrepancies and where they

637
00:41:27,810 --> 00:41:28,380
come from.

638
00:41:28,860 --> 00:41:32,370
Yeah. And so then there's other
hosts that say, That's not

639
00:41:32,370 --> 00:41:34,380
legitimate traffic. So we're
going to exclude that from the

640
00:41:34,380 --> 00:41:38,190
stats. So then, so each host is
making their own decisions about

641
00:41:38,760 --> 00:41:44,850
within the confines of the AI
based ads, rules. There's lots

642
00:41:44,850 --> 00:41:49,080
of leeway to make those
decisions. And then to separate

643
00:41:49,110 --> 00:41:51,780
what is an apple podcast
download? What is apple core

644
00:41:51,780 --> 00:41:53,670
media? What's an Android
download all these kinds of

645
00:41:53,670 --> 00:41:59,100
things, right? So um, and here's
another way, it was explained to

646
00:41:59,100 --> 00:42:05,400
me, let's just say that you have
an office building with view and

647
00:42:05,400 --> 00:42:10,290
five of your buddies all sitting
in a cave together. And you all

648
00:42:10,290 --> 00:42:12,690
listen to the same, same one

649
00:42:12,690 --> 00:42:17,220
one na t address? Exactly.
You're gonna guess always been

650
00:42:17,220 --> 00:42:17,820
the problem?

651
00:42:18,450 --> 00:42:25,230
Yeah. So how do you
differentiate this? And the I

652
00:42:25,260 --> 00:42:35,400
this the idea? We came up that
the fix for this, and I think

653
00:42:35,400 --> 00:42:41,910
it's brilliant. is for podcast
downloads for podcast apps, to

654
00:42:41,910 --> 00:42:45,330
put an extra query parameter on
the end of the URL when they

655
00:42:45,330 --> 00:42:52,920
download the file. Oh, yeah.
Yeah. Okay, we're doing

656
00:42:52,920 --> 00:42:56,910
something similar with with
appending. A, because we had,

657
00:42:56,940 --> 00:43:00,270
there's a similar problem with
web apps. So like, pod friend,

658
00:43:00,930 --> 00:43:04,800
when pod friend or pod verse
shows up in a download stats and

659
00:43:04,800 --> 00:43:09,690
a log for a podcast, they show
up as like Firefox or

660
00:43:09,750 --> 00:43:11,910
Chrome, right? Mm hmm.

661
00:43:12,239 --> 00:43:18,059
So what what we've had to do is
put in an extra query parameter

662
00:43:18,059 --> 00:43:22,859
on the end of the download, it
says, it's like underscore from

663
00:43:22,889 --> 00:43:26,819
equal pod friend got it that
that way, it shows up in the

664
00:43:26,819 --> 00:43:31,379
logs that this is not Chrome,
this is actually a web app. This

665
00:43:31,379 --> 00:43:33,809
is something similar, but it
works a little bit different.

666
00:43:34,499 --> 00:43:36,749
What you would put on the end of
the query, as you'd put an

667
00:43:36,749 --> 00:43:39,749
additional query parameter on
the end of the download, that

668
00:43:39,749 --> 00:43:44,609
would be something like
underscore, Gu ID God equals

669
00:43:44,639 --> 00:43:50,609
such and such. And I've, I've
already implemented this on the

670
00:43:51,209 --> 00:43:55,529
podcast index website, website,
player. So if you go to the

671
00:43:55,529 --> 00:43:59,819
podcast index, play website and
click on any and just search for

672
00:43:59,819 --> 00:44:04,079
podcasts and click play it, it
is already doing this. It is

673
00:44:04,079 --> 00:44:09,089
attaching the underscore gu ID
to the end of the download URL.

674
00:44:09,899 --> 00:44:13,769
So like James Cridland, if you
go check your logs right now,

675
00:44:13,919 --> 00:44:17,969
for pod news or pod land, you
should be able to find some

676
00:44:17,969 --> 00:44:21,929
downloads in your logs with the
underscore gu ID parameter on

677
00:44:21,929 --> 00:44:26,399
the end of it. Right, and the
underscore get parameter is made

678
00:44:26,399 --> 00:44:32,969
this way. When some when a when
an app wants to play or download

679
00:44:33,119 --> 00:44:38,699
a file. You just create a random
gu ID. It doesn't matter. It

680
00:44:38,699 --> 00:44:40,829
doesn't have to be based on
anything. It doesn't have to be

681
00:44:40,829 --> 00:44:46,469
the hash of anything. Just
create a sufficiently random RFC

682
00:44:46,469 --> 00:44:56,309
compliant gu ID string. Then you
pin it to that download. He pin

683
00:44:56,309 --> 00:44:57,239
it to that URL.

684
00:44:57,420 --> 00:44:58,590
I see so

685
00:44:59,219 --> 00:45:05,549
every time That app plays that
your plays that URL or downloads

686
00:45:05,549 --> 00:45:10,859
that URL. It always has the same
gu ID attached to it. That tells

687
00:45:10,859 --> 00:45:17,849
you that tells you exactly how
many times each person, each

688
00:45:17,849 --> 00:45:23,249
specific person downloaded or
played that that episode. But

689
00:45:23,249 --> 00:45:28,109
without ever, ever compromising
any sort of privacy because the

690
00:45:28,109 --> 00:45:30,059
value is completely random and
made up.

691
00:45:30,149 --> 00:45:31,319
Yeah. And it goes away.

692
00:45:32,190 --> 00:45:35,520
Yeah. So I, for instance, so

693
00:45:35,969 --> 00:45:39,989
let me ask you a question.
Because if I come back, and I

694
00:45:39,989 --> 00:45:46,469
play that podcast again, does it
maintain my that, that, that ID

695
00:45:46,469 --> 00:45:49,619
that that we're sending? was to
create a new one for a new

696
00:45:49,619 --> 00:45:50,189
session?

697
00:45:51,030 --> 00:45:53,130
No, it creates the same one
every time.

698
00:45:53,160 --> 00:45:55,710
Okay, no matter what podcasts
you as long as you

699
00:45:57,599 --> 00:46:03,869
know, that note note, this is
per, per, per, per enclosure?

700
00:46:04,019 --> 00:46:06,389
Ah, perfect. Okay. Yeah, that's
great.

701
00:46:07,230 --> 00:46:13,410
Yeah, so if my if every time I
play Episode 14 of podcasting,

702
00:46:13,410 --> 00:46:19,320
2.0. Me Dave Jones, every time I
play that from pod friend, it's

703
00:46:19,320 --> 00:46:27,240
gonna send the exact same good
to, to our, to our CDN, to get

704
00:46:27,240 --> 00:46:30,240
that thing. So if you play the
same episode, it's gonna be a

705
00:46:30,240 --> 00:46:33,900
completely different good. And
when you when you start playing

706
00:46:33,900 --> 00:46:37,620
Episode 15, you'll get a new
good, yeah, it'll always be the

707
00:46:37,620 --> 00:46:39,060
same for that episode, too.

708
00:46:39,300 --> 00:46:43,050
So so what you need now is you
just need all apps to adhere to

709
00:46:43,050 --> 00:46:43,440
that.

710
00:46:44,430 --> 00:46:48,150
Yes, you need all the apps to
begin to epin to do that

711
00:46:48,150 --> 00:46:53,340
technique and append that
string. And then instantly, you

712
00:46:53,340 --> 00:47:01,560
have perfect stats. And there's
nice No, it. So here, and here's

713
00:47:01,560 --> 00:47:03,480
the way that it's implemented
for the developers, if you want

714
00:47:03,480 --> 00:47:08,070
to kind of help me jumpstart the
things through on this is that,

715
00:47:08,490 --> 00:47:13,770
so what we're doing is, I've
made it where, when you when you

716
00:47:13,770 --> 00:47:17,730
begin, when you hit the play
button on the download on, on

717
00:47:17,730 --> 00:47:20,430
the website, we hit the play
button on an episode on the

718
00:47:20,430 --> 00:47:25,800
website, it will create a random
gu ID and then save it in

719
00:47:25,830 --> 00:47:33,210
browser local storage. With,
with the key being a hash of the

720
00:47:33,210 --> 00:47:37,260
URL, that's being that's being
played just the enclosure URL,

721
00:47:37,410 --> 00:47:39,840
just to make this hashing it
just to make sure that no funky

722
00:47:39,840 --> 00:47:43,200
characters get in there. Because
Rocky, right, he take is going

723
00:47:43,200 --> 00:47:47,730
to make a hat makes a Sha 256
hash, saves that into browser

724
00:47:47,730 --> 00:47:52,200
local storage. and the value is
that good. So every time you

725
00:47:52,200 --> 00:47:56,880
play an episode, it checks first
in local storage to see if that

726
00:47:56,880 --> 00:47:59,640
value exists. If it does, it
just grabs it out of local

727
00:47:59,640 --> 00:48:03,120
storage and sticks it on the
end, if it if no value exists,

728
00:48:03,270 --> 00:48:05,970
it creates a new wind it sticks
it on the end and saves that one

729
00:48:05,970 --> 00:48:07,080
in local storage for the future.

730
00:48:07,109 --> 00:48:08,519
Oh, nice.

731
00:48:08,610 --> 00:48:11,400
I like it. So that's how this
works. And the only the only

732
00:48:11,400 --> 00:48:14,130
time that would ever get screwed
up is if somebody clears their

733
00:48:14,130 --> 00:48:19,260
local storage, which is not,
which is not frequent enough to

734
00:48:19,260 --> 00:48:24,420
really put that big of a margin
of error on it. Right? That

735
00:48:25,080 --> 00:48:33,900
this, this is to me. In in as we
go forward out, I would like to

736
00:48:33,900 --> 00:48:36,420
push this as we go forward.

737
00:48:38,460 --> 00:48:42,900
The person who outlined this
technique to me he's gonna write

738
00:48:42,900 --> 00:48:44,490
a white paper about it and that
kind of thing.

739
00:48:46,440 --> 00:48:50,430
And so it'll it'll become a
fleshed out more. This technique

740
00:48:50,430 --> 00:48:56,670
to me. I think it solves stats.
100% is completely anonymous.

741
00:48:57,840 --> 00:49:02,130
It's not it to me, it's it's, it
is the proper fix.

742
00:49:03,420 --> 00:49:06,480
Why has no one come up with this
before? It seems simple,

743
00:49:06,510 --> 00:49:09,360
elegant, easily easy to
implement?

744
00:49:11,400 --> 00:49:13,800
I don't know. That's a good
question. And

745
00:49:13,800 --> 00:49:17,820
will I be look at this and say,
Hey, finally we got something

746
00:49:17,820 --> 00:49:18,720
good or?

747
00:49:19,709 --> 00:49:20,129
Oh,

748
00:49:20,190 --> 00:49:21,510
well, we'll find out I guess.

749
00:49:22,200 --> 00:49:26,610
Yeah, I hope they will. I mean,
because to me this this belongs

750
00:49:26,670 --> 00:49:29,850
sort of in the world of the open
podcast, analytics Working

751
00:49:29,850 --> 00:49:35,130
Group. Yeah. I feel like those
guys would read would be the

752
00:49:35,130 --> 00:49:40,680
proper place for this stuff to
land. So the only the question

753
00:49:40,710 --> 00:49:46,950
the the natural question that
comes up to me is it's not a

754
00:49:46,950 --> 00:49:52,350
question. They see how to
express this. What I think is

755
00:49:52,350 --> 00:49:57,420
probably obvious to most people,
hopefully it is. It there are

756
00:49:57,450 --> 00:50:02,730
there are plenty of podcasters
out there. They're don't want

757
00:50:02,730 --> 00:50:09,930
accurate stats, right? Because
their own the beneficial side of

758
00:50:09,930 --> 00:50:12,330
bad stats. Yeah,

759
00:50:12,329 --> 00:50:16,469
this is you're nailing it with
this. Yeah, not everybody wants

760
00:50:16,469 --> 00:50:18,659
to actually have the real
numbers. It may be

761
00:50:18,659 --> 00:50:20,819
disappointing. Yes.

762
00:50:21,840 --> 00:50:23,850
Yeah. And this is this,

763
00:50:23,849 --> 00:50:28,019
by the way is always the issue.
This is why all these systems

764
00:50:28,019 --> 00:50:33,419
exist and why they're closed
loop and closely guarded and

765
00:50:33,419 --> 00:50:37,019
protected because no one wants
to know the actual numbers.

766
00:50:37,679 --> 00:50:43,499
No, no. Okay. Play does play the
mama Knows Best thing. But in

767
00:50:43,500 --> 00:50:46,770
this episode, we're talking
about adjusting to fame. We'll

768
00:50:46,770 --> 00:50:49,830
discuss when it all started, how
we've dealt with it as a family

769
00:50:49,830 --> 00:50:52,350
and some of the pitfalls that
have come along the way. Let's

770
00:50:52,350 --> 00:50:52,860
get into it.

771
00:50:53,940 --> 00:50:57,420
Before this episode, a quick
question, how do you spend an

772
00:50:57,450 --> 00:51:01,440
urn at the same time with Chase
freedom unlimited 3% of

773
00:51:01,440 --> 00:51:05,730
drugstores and 3% on dining
including takeout and eligible

774
00:51:05,730 --> 00:51:07,920
delivery services? Plus 5%.

775
00:51:08,400 --> 00:51:09,960
Does it just keep going with the
Add?

776
00:51:10,590 --> 00:51:12,960
Yeah, keep keep gravel purchase
through Chase.

777
00:51:13,019 --> 00:51:17,009
Chase. Make more of what's
yours. Learn more at chase calm

778
00:51:17,009 --> 00:51:18,479
slash mama knows best.

779
00:51:19,889 --> 00:51:23,519
Okay, wow, the interesting. This
is my favorite. This is my new

780
00:51:23,519 --> 00:51:27,899
favorite pot. My new favorite
not a podcast on Spotify. Yes.

781
00:51:28,679 --> 00:51:35,969
Yeah. So number one, because
it's it's so bad. You know, but,

782
00:51:36,269 --> 00:51:42,089
but I like hearing the ad. So
they had an ad for Chase Bank.

783
00:51:42,119 --> 00:51:46,859
Yeah. And followed by Folgers
followed by McDonald's at

784
00:51:47,280 --> 00:51:48,180
three in a row.

785
00:51:48,869 --> 00:51:54,359
Yeah. So as the as the resident
podcast advertising expert.

786
00:51:55,649 --> 00:51:59,849
Well, what does that say? Who is
your audience when you have an

787
00:51:59,849 --> 00:52:03,269
ad when you have three ads when
you have Chase Bank, Folgers and

788
00:52:03,269 --> 00:52:06,089
McDonald's? Who exactly is your
audience?

789
00:52:07,980 --> 00:52:14,040
She's Folgers? Yeah, well, these
are? That's a good question.

790
00:52:15,360 --> 00:52:18,780
Clearly, they have some data on
you, Dave, since you're the one

791
00:52:18,780 --> 00:52:23,220
that got it. You obviously eat
McDonald's you drink Folgers

792
00:52:23,220 --> 00:52:25,110
coffee and you use Chase Bank

793
00:52:25,949 --> 00:52:29,969
as three the the only one of
those three I've ever done is

794
00:52:29,969 --> 00:52:38,489
McDonald's. So like this is a
podcast about chicks promise

795
00:52:38,489 --> 00:52:44,909
this doesn't just apply cast.
About a tick tock superstar like

796
00:52:44,909 --> 00:52:48,149
this this 19 year old girl who's
the like number two around take

797
00:52:48,149 --> 00:52:55,799
time? Why is there a Folgers add
in there? I don't get it.

798
00:52:56,939 --> 00:52:57,689
Somebody

799
00:52:57,780 --> 00:53:01,530
that could be that they're just
filling up the inventory that

800
00:53:01,530 --> 00:53:05,340
they promised to put out there.
This is what I had. This is just

801
00:53:05,550 --> 00:53:06,510
randomness.

802
00:53:06,599 --> 00:53:09,479
Yeah, well, just the same thing
with political ads. During this

803
00:53:09,479 --> 00:53:12,329
last cycle. The kids were
getting a five year old kids

804
00:53:12,329 --> 00:53:18,509
were getting Joe Biden
commercials for their little,

805
00:53:18,509 --> 00:53:24,959
uh, you know, Sesame Street or
something. The the trickery

806
00:53:24,959 --> 00:53:28,079
works on all ends. I mean, I've
been in that business long

807
00:53:28,079 --> 00:53:31,169
enough to know if we can shove
some stuff into someone else.

808
00:53:31,169 --> 00:53:34,289
And it won't really get noticed
as not being the demographic to

809
00:53:34,289 --> 00:53:34,859
do it.

810
00:53:35,849 --> 00:53:44,429
So here's my pitch. The
obviously there is I'm canceling

811
00:53:44,459 --> 00:53:48,029
obviously, because it's not it's
not that obvious. It's not that

812
00:53:48,029 --> 00:53:55,949
obvious. Here. My pitch is if
the open podcast ecosystem has

813
00:53:56,699 --> 00:54:04,109
accurate stats, it may hurt
initially. It may suck for some

814
00:54:04,109 --> 00:54:08,879
podcasts where all of a sudden
they're reporting, you know, 10

815
00:54:08,879 --> 00:54:12,269
million downloads, and now
they've, they've actually got to

816
00:54:12,269 --> 00:54:15,569
fess up and report two and a
half million. Mm hmm. I don't

817
00:54:15,569 --> 00:54:23,369
know. It may hurt. But the
alternative for advertisers is

818
00:54:23,369 --> 00:54:27,629
that advertisers are in a closed
system with with somebody like

819
00:54:27,629 --> 00:54:33,569
Spotify, where there's potential
skullduggery going on and what

820
00:54:34,289 --> 00:54:38,489
you don't exactly know what
you're you don't exactly know

821
00:54:38,489 --> 00:54:41,819
what you're getting. I mean,
like can you trust those

822
00:54:41,819 --> 00:54:42,629
numbers?

823
00:54:42,750 --> 00:54:46,290
I'm shocked Yeah,

824
00:54:47,849 --> 00:54:51,029
like so I guess what I'm trying
to say in a roundabout ways that

825
00:54:51,299 --> 00:54:54,179
this could be a way with
accurate stats. I know people

826
00:54:54,179 --> 00:54:57,149
are making a lot of money. Some
people are making a lot of money

827
00:54:57,149 --> 00:55:01,019
on bogus stats probably. But
with actual Curious stats, it

828
00:55:01,019 --> 00:55:04,799
can make the podcast, the open
podcast ecosystem more

829
00:55:04,799 --> 00:55:06,869
attractive to advertisers
because they feel like they're

830
00:55:06,869 --> 00:55:09,449
getting a better, they feel like
they're getting a better deal

831
00:55:09,570 --> 00:55:13,170
or even direct relationships
podcasters have with sponsors

832
00:55:13,170 --> 00:55:16,680
for live host reads, which I
think is still a lot of the

833
00:55:16,680 --> 00:55:24,450
power of a podcast is how you
can promote a product. And you

834
00:55:24,450 --> 00:55:28,350
can do it quite transparently.
But to be able to say, Okay,

835
00:55:28,350 --> 00:55:31,110
here's how many people are
actually listening to that

836
00:55:31,110 --> 00:55:34,770
segment, that part of it. Not
fast forwarding, this has always

837
00:55:34,770 --> 00:55:39,360
been a big issue. I think it's a
great idea. We should we should

838
00:55:39,360 --> 00:55:43,470
push this, we need to give it a
name. Give it a name and push it

839
00:55:43,470 --> 00:55:46,080
and it's open. I put their link
in the show notes. Is it the

840
00:55:46,080 --> 00:55:49,740
open podcast? analytics working
group? Yeah, they're

841
00:55:50,010 --> 00:55:52,470
that dia James. And about and a
bunch of the hosts are involved.

842
00:55:52,500 --> 00:55:54,930
I smell James all over this.

843
00:55:55,469 --> 00:55:55,979
Yeah.

844
00:55:57,179 --> 00:55:57,839
I'd like it.

845
00:55:58,320 --> 00:56:03,780
Another thing that in the end, I
mean, as the index i think we

846
00:56:04,260 --> 00:56:08,430
because yes, we are committed to
a feature. Without we are

847
00:56:08,430 --> 00:56:10,770
committed to the value for value
model a feature without

848
00:56:10,770 --> 00:56:16,080
advertising. We want because we
we, we definitely see that as a

849
00:56:16,080 --> 00:56:18,840
feature. We see advertising is
censorship, all of that, you

850
00:56:18,840 --> 00:56:23,160
know that. But also, I mean, I
think there's a realization and

851
00:56:23,160 --> 00:56:25,560
there's a bridge that has to
happen between how do I get

852
00:56:25,560 --> 00:56:30,000
from, from where I'm at now to
there, and you can't necessarily

853
00:56:30,000 --> 00:56:32,160
just cut it off. And so people
are, there's gonna be a

854
00:56:32,160 --> 00:56:36,090
coexistence that needs to happen
in the podcast industry is

855
00:56:36,090 --> 00:56:42,570
better if the stats aren't a
bunch of shenanigans. And, you

856
00:56:42,570 --> 00:56:45,960
know, like at the end of that,
that mama knows best thing that

857
00:56:45,960 --> 00:56:49,950
was playing. So here's, again,
here's Spotify, who's supposed

858
00:56:49,950 --> 00:56:54,060
to have, you know, surgical
precision, advertising and

859
00:56:54,060 --> 00:56:57,900
light, and they're supposed to
have all the stats. Yeah.

860
00:56:58,650 --> 00:57:01,350
Well, now now remember that,
that what they're doing is

861
00:57:01,350 --> 00:57:04,800
they're linking their user
profiles to the stats. So yeah,

862
00:57:04,800 --> 00:57:07,680
so yeah, and they know a lot
about a user's musical

863
00:57:07,680 --> 00:57:10,860
preference, which they claim
tells them a lot about a person,

864
00:57:10,860 --> 00:57:14,790
which I believe, I don't know
how they break it down. But

865
00:57:14,940 --> 00:57:18,510
yeah, so you know, they they
have all kinds of cross

866
00:57:18,510 --> 00:57:21,990
references to know what's going
in there. I've never liked that.

867
00:57:21,990 --> 00:57:24,390
I've never liked programmatic
ads for this very reason.

868
00:57:26,340 --> 00:57:29,400
Most of my question is, why did
they have to throw at the end?

869
00:57:29,580 --> 00:57:33,060
On the Chase Bank commercial?
What did they have to throw at

870
00:57:33,060 --> 00:57:37,890
the very end of that? Find out
more at Chase Bank, blah, blah,

871
00:57:37,890 --> 00:57:40,950
blah, slash mama knows best.
What do they have to get the

872
00:57:40,950 --> 00:57:46,380
follow up confirmation there? Do
they not trust this? Oh, that's

873
00:57:46,380 --> 00:57:49,470
a good point. Yeah, it's a good
point. You're saying that? Well,

874
00:57:50,460 --> 00:57:54,090
I guess that's for conversion? I
mean, you can you get the stats,

875
00:57:54,090 --> 00:57:58,380
but the conversion to an actual
someone going to a service?

876
00:57:59,489 --> 00:58:03,839
Which is there separate deal
there that the conversions pay

877
00:58:03,839 --> 00:58:04,139
more?

878
00:58:04,590 --> 00:58:08,310
Yes. If so if someone hears the
ad, that's one thing. If they

879
00:58:08,310 --> 00:58:11,280
convert, and they go there, and
they identify, they heard it on

880
00:58:11,280 --> 00:58:16,320
slash radio or slash tv or slash
mama knows best? Yeah, that's

881
00:58:16,320 --> 00:58:20,160
the conversion fee. And that's,
that's better. And we're clear

882
00:58:20,160 --> 00:58:32,190
reasons. Well, yeah, I like, I
like this idea a lot. Okay. And

883
00:58:32,190 --> 00:58:34,350
I wouldn't mind having it just
for myself. But this doesn't

884
00:58:34,350 --> 00:58:37,170
have to be an advertising play.
I just like to know for myself

885
00:58:37,170 --> 00:58:40,260
who's listening where I mean,
I've seen stats on Apple, I

886
00:58:40,260 --> 00:58:42,930
enjoyed looking at those. But
let's blanket it. Let's get

887
00:58:42,930 --> 00:58:45,720
everybody to implement this.
This is This seems relatively

888
00:58:45,720 --> 00:58:48,840
easy, something we can all do.
And we'll push it really hard.

889
00:58:48,990 --> 00:58:52,230
And if he doesn't like it, then
we'll start our own alternative

890
00:58:52,230 --> 00:58:53,700
advertising agency.

891
00:58:54,360 --> 00:58:57,960
Yeah, the PA baby united
podcast.

892
00:59:00,000 --> 00:59:08,880
podcasters. United pee the poo.
poo. And and as an addition, if,

893
00:59:08,940 --> 00:59:12,780
if app developers would consider
looking at some of these

894
00:59:12,780 --> 00:59:17,970
community chapters, this is the
main reason I use pod friend is

895
00:59:17,970 --> 00:59:20,910
that's a whole additional piece
of content. If you say hey,

896
00:59:20,910 --> 00:59:25,860
visit, visit the website, Chase
bank.com. Slash mama knows best.

897
00:59:25,950 --> 00:59:28,950
That would pop right up in a
chapter window with a URL link.

898
00:59:28,950 --> 00:59:31,440
Click it right there. Click it,
tap it, whatever you want to do.

899
00:59:32,160 --> 00:59:32,850
Yeah, these

900
00:59:32,850 --> 00:59:34,170
these conversion, these

901
00:59:34,169 --> 00:59:34,859
things work.

902
00:59:34,890 --> 00:59:39,150
I mean, it really works. that
converts right in your face,

903
00:59:39,150 --> 00:59:42,510
man. It's like boom, and you
can't get any easier than ever

904
00:59:42,510 --> 00:59:45,420
convert than that. I mean, is it
because it's right there on the

905
00:59:45,420 --> 00:59:45,990
screen.

906
00:59:46,769 --> 00:59:54,119
Interestingly, the podcast app
can also start to create his own

907
00:59:54,119 --> 00:59:57,509
statistics for things like
conversion

908
01:00:00,000 --> 01:00:04,020
Yeah, true. Because it's because
it knows because it's right

909
01:00:04,050 --> 01:00:10,920
knows it knows the conversion.
Yeah. It knows. You got some guy

910
01:00:10,920 --> 01:00:12,360
in Denmark, who knows?

911
01:00:13,980 --> 01:00:17,820
There's either like there's a
lot of there's, there's, I think

912
01:00:17,820 --> 01:00:20,790
that the market, that piece of
the market that overcast and

913
01:00:20,790 --> 01:00:28,560
podcast addict has carved out
for themselves are based on a

914
01:00:28,560 --> 01:00:32,580
few things, and one of which is
privacy. And they're very

915
01:00:32,580 --> 01:00:35,970
privacy focused. And that's,
that's good. I mean, that's

916
01:00:35,970 --> 01:00:39,270
fantastic. Yes, that's
absolutely a good thing. And for

917
01:00:39,270 --> 01:00:44,010
that reason, they have resisted
the constant calls for them to

918
01:00:44,010 --> 01:00:48,810
open up their their stats. So
this would be a way for those

919
01:00:48,810 --> 01:00:52,410
guys not to open up their stats,
but still give meaningful

920
01:00:52,980 --> 01:00:57,900
intelligence to other
podcasters. They don't have to

921
01:00:57,900 --> 01:01:01,740
open up anything at all. They
just tack that string on the

922
01:01:01,740 --> 01:01:07,140
end. It's completely anonymized.
And that shares in this system

923
01:01:07,140 --> 01:01:10,620
so that other podcasts so that
their fellow podcasters can

924
01:01:10,620 --> 01:01:14,550
benefit from it. Yeah. But
without without breaking their

925
01:01:14,550 --> 01:01:19,290
own, you know, without breaking
their own private policy, you

926
01:01:19,290 --> 01:01:20,250
know, their own

927
01:01:20,639 --> 01:01:22,529
whatever you privacy. Privacy
Policy.

928
01:01:22,740 --> 01:01:25,620
Yeah, without violating their
integrity. Yeah, there you go.

929
01:01:25,680 --> 01:01:33,240
Yeah. It's I think it's in, you
know, I've already done it. It

930
01:01:33,240 --> 01:01:36,690
took me seriously, like less
than less than 30 minutes. Well,

931
01:01:36,690 --> 01:01:36,840
we're

932
01:01:36,840 --> 01:01:38,700
calling it anybody. Can we have
a name?

933
01:01:38,729 --> 01:01:41,039
It's the open podcast
statistics. We're calling it

934
01:01:41,069 --> 01:01:41,639
ops.

935
01:01:43,380 --> 01:01:46,320
Ops. I just made that up to do
it. That's the parameter. Yes.

936
01:01:46,320 --> 01:01:46,680
Good.

937
01:01:46,710 --> 01:01:51,270
The ops good, which has been
determined by the Pooh as

938
01:01:51,450 --> 01:01:52,740
podcasters united.

939
01:01:53,309 --> 01:01:55,169
Is that the show title ops do it
by the

940
01:01:56,579 --> 01:02:00,119
I put fourth quarter in there
dumb dumb enough. I come up with

941
01:02:00,119 --> 01:02:02,339
my titles beforehand for this
show. trying something

942
01:02:02,339 --> 01:02:04,169
different. sad about it now?

943
01:02:04,710 --> 01:02:06,360
No, I like it. When you talk
sports. It's great.

944
01:02:09,150 --> 01:02:11,820
Hey, let's think it was thanks
some people unless yet

945
01:02:11,820 --> 01:02:13,530
to say the ad stuff makes me
feel

946
01:02:13,590 --> 01:02:16,230
gross. Yeah, dirty. So now let's
thank some people. This is a

947
01:02:16,230 --> 01:02:20,400
value for value podcast. The
entire project podcast index has

948
01:02:20,400 --> 01:02:25,920
value for value. outfall, there
will be enough for Dave and I

949
01:02:25,920 --> 01:02:29,430
and anyone to take a salary.
Although it would be great as we

950
01:02:29,430 --> 01:02:32,490
move forward. In the meantime,
we like keeping everything

951
01:02:32,490 --> 01:02:36,030
running. And the way it works is
if you get any value out of this

952
01:02:36,030 --> 01:02:40,350
podcast, but out of what podcast
index is doing, as we continue

953
01:02:40,350 --> 01:02:43,200
to preserve podcasting as a
platform for free speech and

954
01:02:43,200 --> 01:02:47,250
retool it into a plat platform
of value for all participants

955
01:02:47,250 --> 01:02:50,490
for the entire ecosystem. And I
should say uninterruptable

956
01:02:50,490 --> 01:02:56,430
value, we need help, then we
need help by you supporting the

957
01:02:56,430 --> 01:02:58,830
entire project. And you can do
that by going to podcast

958
01:02:58,830 --> 01:03:02,250
index.org. Scroll down to the
bottom there's a big red Donate

959
01:03:02,250 --> 01:03:08,160
button you can also donate to a
lightning app. And well, we had

960
01:03:08,160 --> 01:03:10,110
a sad puppy on the last show.

961
01:03:11,010 --> 01:03:13,170
The sad Puppy was gold. I mean
it was

962
01:03:14,369 --> 01:03:18,749
so yeah, in our when we were
talking about only two donations

963
01:03:18,779 --> 01:03:24,209
that came in boom up on the on
the chapter image is a sad puppy

964
01:03:24,269 --> 01:03:26,159
giving giving us that look like
Oh

965
01:03:26,159 --> 01:03:32,489
no. Sad puppy send a trimmer
through the forest. And yeah,

966
01:03:32,789 --> 01:03:35,999
there's like so many donations
this week. It's been fantastic.

967
01:03:35,999 --> 01:03:36,599
Oh, cool.

968
01:03:36,779 --> 01:03:39,269
Oh, it works. Oh my goodness.
Well, this is Yeah, that you

969
01:03:39,269 --> 01:03:41,759
just need to remind people it's
what I always say. Just need to

970
01:03:41,759 --> 01:03:42,539
remind people.

971
01:03:43,469 --> 01:03:47,369
Okay, whenever look, people
whenever donations go down.

972
01:03:47,909 --> 01:03:49,499
You're gonna get the guilty
puppy. That's

973
01:03:50,159 --> 01:03:53,849
just gonna pop out. Yeah, now we
need a little Tinker Bell who's

974
01:03:53,849 --> 01:03:56,549
happy and flying around. We have
donations.

975
01:03:56,909 --> 01:04:01,859
Oh, yeah, we get a lot of some
good ones too. So the first one

976
01:04:01,919 --> 01:04:06,989
is from RSS calm. And Benjamin
Richardson. Oh, who

977
01:04:06,989 --> 01:04:10,769
helped us already with a with a
pod news sponsorship, which was

978
01:04:10,769 --> 01:04:11,549
fantastic.

979
01:04:11,909 --> 01:04:18,239
Yet while he followed it up in a
big way. $1,075 donation and

980
01:04:18,239 --> 01:04:25,019
Whoa, whoa. Holy moly. That that
is that doesn't deserve a

981
01:04:25,019 --> 01:04:26,579
podcast or cool person.

982
01:04:27,869 --> 01:04:28,769
does deserve what?

983
01:04:29,219 --> 01:04:31,289
The podcasts are cool. I so I
mean, I

984
01:04:31,320 --> 01:04:33,600
know. Yes. We go

985
01:04:33,630 --> 01:04:34,710
podcasts are cool.

986
01:04:35,909 --> 01:04:40,769
podcasts are cool. Wow. Did you
have a note? He say anything?

987
01:04:41,039 --> 01:04:43,349
Yeah, he's got a note. Yeah.
Yeah. And I made sure it was

988
01:04:43,349 --> 01:04:45,749
okay to read. He said, David
Adam, this is given an

989
01:04:45,749 --> 01:04:49,319
appreciation for the hard work
and foresight podcast index

990
01:04:49,319 --> 01:04:52,319
represents. We're excited for
the future because of the work

991
01:04:52,319 --> 01:04:55,409
being done in the present. Thank
you for your leadership and

992
01:04:55,409 --> 01:04:58,319
dedication. A special thanks to
all those folks in the trenches

993
01:04:58,319 --> 01:05:02,609
making it happen without the
time and talent of Martin, James

994
01:05:02,639 --> 01:05:07,979
Tom CSB. Kevin and many others.
We know this wouldn't be in.

995
01:05:08,099 --> 01:05:12,719
This wouldn't be anywhere. Oh
2021 and all the possibility it

996
01:05:12,719 --> 01:05:16,349
holds your friends@rss.com ps we
put some extra money in there so

997
01:05:16,349 --> 01:05:18,359
you guys can have a drink on us.
You deserve it.

998
01:05:18,900 --> 01:05:24,780
75 bucks for drinkin. Yeah.
That's really nice. That is

999
01:05:24,780 --> 01:05:27,000
that's humbling. I really
appreciate that.

1000
01:05:27,240 --> 01:05:30,540
Yeah, me too. I emailed him
back. I was like, hey, like,

1001
01:05:30,840 --> 01:05:31,170
this is your

1002
01:05:33,300 --> 01:05:34,920
fat finger. This What happened?
Yeah.

1003
01:05:35,700 --> 01:05:38,370
Like, we want to buy you a
drink. Let's make that happen.

1004
01:05:38,969 --> 01:05:42,749
Thank you. Thank you for the
very kind. Thank you. So rss.com

1005
01:05:44,309 --> 01:05:46,049
Yeah, and we're happy. We're
gonna have those guys on the

1006
01:05:46,049 --> 01:05:47,129
show in January.

1007
01:05:47,190 --> 01:05:50,970
Yeah. So the booking you're like
producing this thing now, man.

1008
01:05:52,290 --> 01:05:55,590
Now I'm doing everything. You
got the crumble notes. You could

1009
01:05:55,590 --> 01:05:59,970
use booking the guests. You're,
you've got the one liners up,

1010
01:05:59,970 --> 01:06:00,450
man.

1011
01:06:01,019 --> 01:06:02,579
You need me at least some stuff
for you.

1012
01:06:03,600 --> 01:06:05,910
Okay, I hit record. Let's

1013
01:06:08,250 --> 01:06:12,750
see. Let's see. We got another
one. This is from Dred Scott.

1014
01:06:13,230 --> 01:06:14,490
Oh, my goodness.

1015
01:06:14,940 --> 01:06:18,360
And he said his note was
answering the call Keep up the

1016
01:06:18,360 --> 01:06:20,820
great work. And he donated 333.

1017
01:06:22,019 --> 01:06:24,959
Dred Scott, he's doing chapters
for us already. He's doing

1018
01:06:24,959 --> 01:06:28,169
chapters for no agenda. I mean,
this guy's phenomenal.

1019
01:06:28,530 --> 01:06:31,020
Do we have them in? Don't we're
gonna get him like a Sphinx

1020
01:06:31,020 --> 01:06:33,030
node. So you can get some some
cut in?

1021
01:06:33,240 --> 01:06:38,310
Yeah, I'm getting a whole bunch
of Sphinx node codes from Paul,

1022
01:06:38,310 --> 01:06:41,190
so I can start handing them out
that they're working on spinning

1023
01:06:41,190 --> 01:06:43,410
up a crap ton of nodes.

1024
01:06:44,519 --> 01:06:47,579
And tried to create one this
morning. And is that delayed?

1025
01:06:47,610 --> 01:06:51,270
No, it's all too late. And it's
probably a bad time right now.

1026
01:06:52,890 --> 01:06:56,190
starting up these nodes channels
have to be created. So it takes

1027
01:06:56,220 --> 01:07:03,930
some some on chain off chain
processing. Okay. And that cost

1028
01:07:03,960 --> 01:07:08,400
cost a little much now with the
the fees are high at this

1029
01:07:08,400 --> 01:07:08,820
moment.

1030
01:07:09,659 --> 01:07:10,799
Oh, yeah. Like,

1031
01:07:11,610 --> 01:07:14,310
there's a lot of a lot of stuff
in the mempool. He said sounding

1032
01:07:14,310 --> 01:07:15,960
like he knows what the hell he's
talking about.

1033
01:07:18,210 --> 01:07:19,800
I don't even know what a mempool
is.

1034
01:07:19,829 --> 01:07:21,479
Yeah, trust me. You don't?

1035
01:07:22,019 --> 01:07:24,749
That's that's the backlog of
transactions waiting to take

1036
01:07:24,749 --> 01:07:25,349
place. Right?

1037
01:07:25,500 --> 01:07:27,810
Well, it's stuff competing to
get into the block.

1038
01:07:28,769 --> 01:07:31,109
That's right. Okay. So it's
back. The higher the higher the

1039
01:07:31,109 --> 01:07:33,869
mempool backlog, the higher the
transaction fees, because people

1040
01:07:33,869 --> 01:07:34,469
are wanting Yes,

1041
01:07:34,499 --> 01:07:35,969
they want to get it. Exactly.

1042
01:07:36,000 --> 01:07:39,450
Yeah. Okay. Yeah. So that's Dred
Scott. Thanks.

1043
01:07:39,659 --> 01:07:43,679
Thank you very much dread. And
he's doing the chapters and

1044
01:07:43,679 --> 01:07:48,899
doing a great job. I just,
that's what I saw. Someone else

1045
01:07:48,899 --> 01:07:51,119
was trying to integrate or
something else?

1046
01:07:51,209 --> 01:07:51,629
I don't know.

1047
01:07:52,679 --> 01:07:56,669
Anyway, I got to catch up and
show you I get so behind one on

1048
01:07:56,669 --> 01:07:59,549
Thursday. I just can't catch up.
Because I'm doing the show. And

1049
01:07:59,549 --> 01:08:02,099
and I get behind like, oh, man,
what's been going on

1050
01:08:02,099 --> 01:08:09,899
we talking about? Yeah, it's you
get lost? Yeah. Let's see. This

1051
01:08:09,899 --> 01:08:16,199
one is. Okay. So what's what's
the naming protocol here? If you

1052
01:08:16,199 --> 01:08:21,839
got a C this is from sir dude
named Ben defender of megawatts

1053
01:08:21,899 --> 01:08:25,619
this donation is from Shai uses
real name to produce keep him

1054
01:08:25,619 --> 01:08:27,539
sir. Yes, sir. Do name Ben.

1055
01:08:27,600 --> 01:08:28,620
Yeah, that's probably better.

1056
01:08:29,430 --> 01:08:35,040
All right. So this is from sir
dude named Ben $100. And he

1057
01:08:35,040 --> 01:08:38,670
says, keep free speech alive. We
need it now. More than ever,

1058
01:08:38,670 --> 01:08:41,400
sir. dude named Ben, defender of
megawatts. Ah,

1059
01:08:41,430 --> 01:08:44,340
thank you. The megawatts feel
good. Yeah.

1060
01:08:47,550 --> 01:08:52,350
Yeah, that this is a good. It's
just it makes you just makes you

1061
01:08:52,350 --> 01:08:55,470
feel good. When everybody jumps
in there and just gives you it's

1062
01:08:55,470 --> 01:08:57,480
not just the donations. It's the
nose,

1063
01:08:57,510 --> 01:09:02,310
nose. Yeah. Of course. It's the
beauty of the model, man. And

1064
01:09:03,060 --> 01:09:06,960
you could be reading a note that
goes by gold now.

1065
01:09:08,579 --> 01:09:10,109
Or motherfucking

1066
01:09:10,110 --> 01:09:12,270
cashapp. Or

1067
01:09:15,060 --> 01:09:17,610
Casper mattress Ed says right?
Hey,

1068
01:09:17,640 --> 01:09:22,020
hey, you know, for Christmas. I
got David pair of Tommy John's.

1069
01:09:23,790 --> 01:09:25,950
Because I want Dave to be
comfortable when he's

1070
01:09:25,950 --> 01:09:26,760
podcasting.

1071
01:09:27,000 --> 01:09:30,360
It's Yeah, I'm wearing them all
the time. It's my favorite. It's

1072
01:09:30,360 --> 01:09:34,500
my favorite underwear now or
whatever. Yeah. I forget See,

1073
01:09:34,500 --> 01:09:37,170
that's the part of my model I
forget to put in here. We need

1074
01:09:37,170 --> 01:09:40,560
to change the podcast we get to
throw in a native ad once in a

1075
01:09:40,560 --> 01:09:46,890
while got to do it. Got to do it
that we don't disclose. Yes. So

1076
01:09:47,760 --> 01:09:54,600
Benjamin Bellamy from caste
departure, sir donation. $45.70.

1077
01:09:54,750 --> 01:09:56,610
Thank you. Thank you very much.
Yeah, he

1078
01:09:56,610 --> 01:09:59,730
says congratulations for what
you've accomplished in 2020.

1079
01:10:00,000 --> 01:10:04,050
blocked funding transcript
chapters sound bright sound by

1080
01:10:04,080 --> 01:10:08,160
previous URL ID value and cast a
pod has them all. Yeah,

1081
01:10:08,160 --> 01:10:11,280
I was gonna say cast the pot is
a very interesting product. If

1082
01:10:11,280 --> 01:10:14,940
you want to sell hosts, that's
the way to go, man. That's the

1083
01:10:15,330 --> 01:10:18,930
badass dashboard. And he would
probably be interested in in the

1084
01:10:18,930 --> 01:10:20,520
stats conversation as well.

1085
01:10:21,120 --> 01:10:24,240
And knowing how fast he puts
stuff in there is probably going

1086
01:10:24,240 --> 01:10:25,500
to be done by the end of today.

1087
01:10:25,950 --> 01:10:28,980
That's the crazy thing is like,
when you're dealing with, I'll

1088
01:10:28,980 --> 01:10:32,100
just call them the web guys.
They're able to do stuff so

1089
01:10:32,100 --> 01:10:32,670
quickly.

1090
01:10:33,420 --> 01:10:34,110
Yeah, because, you

1091
01:10:34,110 --> 01:10:39,330
know, like with hyper capture,
which I really like that app, I

1092
01:10:39,330 --> 01:10:42,480
think it's of the app apps. It's
very advanced, certainly with

1093
01:10:42,480 --> 01:10:47,070
its chapters and and the
feedback loop, which I love. You

1094
01:10:47,070 --> 01:10:49,710
know, he's got, he's got to put
it in for another update. And

1095
01:10:49,710 --> 01:10:52,500
it's just painful.

1096
01:10:52,860 --> 01:10:57,090
Yeah, I had a couple guys,
buddy, say dinner with on

1097
01:10:57,090 --> 01:11:01,230
Wednesday, and hadn't seen in a
while, too. We're catching up.

1098
01:11:01,230 --> 01:11:03,780
And I was telling him about the
index and the wild stuff we were

1099
01:11:03,780 --> 01:11:08,100
doing. And they're both Android
guys. And so they were like,

1100
01:11:08,400 --> 01:11:13,920
what the one of my one of these
guys runs podcast. And I said,

1101
01:11:13,920 --> 01:11:16,530
Well, you know, you need to get
on Sphinx. And I was, you know,

1102
01:11:16,530 --> 01:11:19,710
I said, I'll set you up a node
and all this stuff. And here's a

1103
01:11:19,710 --> 01:11:24,120
what, what podcast app should I
be using as my main app or

1104
01:11:24,120 --> 01:11:26,550
whatever? So what do you have
now? You like stitcher?

1105
01:11:27,480 --> 01:11:28,500
Oh, no,

1106
01:11:29,370 --> 01:11:30,810
no, no. Get off.

1107
01:11:31,710 --> 01:11:33,750
You need to go to upgrade.

1108
01:11:34,050 --> 01:11:38,340
Yeah, so I get and had him go
get hyper catcher. Yeah. They

1109
01:11:38,340 --> 01:11:40,410
were like, Oh, this is cool.
I'll show them the chapters and

1110
01:11:40,410 --> 01:11:45,300
all that stuff. Oh, nice. To me,
and I'm just I'm sorry. Not

1111
01:11:45,300 --> 01:11:45,900
hyper catcher.

1112
01:11:46,650 --> 01:11:49,140
podcast addict. Okay. Also,
guys.

1113
01:11:49,290 --> 01:11:53,100
Yeah. applicators only on iOS.
Yeah. They're both Android guys.

1114
01:11:54,240 --> 01:11:59,550
But let's see. Benjamin said.
Congratulations, what you

1115
01:11:59,550 --> 01:12:02,220
accomplished in 2020 locked
funding transcript chapters,

1116
01:12:02,220 --> 01:12:06,690
soundbite previous URL, Id value
and cast a pod has them all.

1117
01:12:06,990 --> 01:12:09,990
We're already working on podcast
location. I can't wait to see

1118
01:12:09,990 --> 01:12:14,010
you guys. What do you guys will
bring in 2021. We have a few

1119
01:12:14,010 --> 01:12:17,190
surprises for you as well. Oh,
okay. All right.

1120
01:12:17,220 --> 01:12:20,220
Nice. surprises like we'd like
surprises.

1121
01:12:20,850 --> 01:12:23,460
A says thank you. Really. I mean
it from cast upon.

1122
01:12:24,090 --> 01:12:26,520
Thank you. Casta pod Benjamin.
Fantastic. Thank you.

1123
01:12:32,340 --> 01:12:32,850
We had

1124
01:12:33,870 --> 01:12:37,410
a reminder, for those of you on
savings chat. If you haven't

1125
01:12:37,410 --> 01:12:41,430
pegged that value slider you
better do it right now. All the

1126
01:12:41,430 --> 01:12:45,750
way up all the all the way to
the top please. A th

1127
01:12:48,029 --> 01:12:57,149
Okay, so we got a donation from
see Cameron. Cameron white, he

1128
01:12:57,149 --> 01:12:59,999
says for $33.33 and just says no
note.

1129
01:13:00,900 --> 01:13:03,480
I thank you very much magic
numbers all around love it.

1130
01:13:04,290 --> 01:13:07,140
That that exclamation point was
not actually in there. That was

1131
01:13:07,140 --> 01:13:17,160
an editorial. Let's see. Make
sure there's no that's not a

1132
01:13:17,160 --> 01:13:23,250
moment. Okay. So David Langford
gives doll $20 and two cent

1133
01:13:23,250 --> 01:13:27,090
donation. Oh, and a palindrome
the next Yeah. The next one is

1134
01:13:27,090 --> 01:13:31,200
$20. So he barely edged out the
next donation. He did this. He

1135
01:13:31,200 --> 01:13:34,560
did it. He did it. Yeah. It's
like he knew it. It's like he

1136
01:13:34,560 --> 01:13:35,280
knew what he was doing.

1137
01:13:35,400 --> 01:13:35,940
Was there no.

1138
01:13:36,690 --> 01:13:44,070
Yes. Yes. Yes. long note. I want
to see this is David David

1139
01:13:44,070 --> 01:13:47,250
Langford. I wonder if maybe
you're thinking too small with

1140
01:13:47,250 --> 01:13:50,220
podcasting. 2.0 I've been
listening to and you're gonna

1141
01:13:50,220 --> 01:13:54,210
tell me if you recognize any of
these names, because I've been

1142
01:13:54,210 --> 01:13:58,170
listening to an indie pop singer
songwriter, Mindy Gledhill.

1143
01:13:58,890 --> 01:14:05,190
ringabel know, me. I've been
listening to an indie pop singer

1144
01:14:05,190 --> 01:14:09,270
songwriter Mindy Gledhill a lot
lately. Her rabbit hole album

1145
01:14:09,270 --> 01:14:12,210
has been helping me go through
my faith crisis turned

1146
01:14:12,210 --> 01:14:17,220
existential crisis turned to
divorce. Yes, I had already paid

1147
01:14:17,220 --> 01:14:21,000
the $12 for her mp3 album from
amazon music, but I wanted to

1148
01:14:21,000 --> 01:14:23,910
send her some extra value for
the value of her music and her

1149
01:14:23,910 --> 01:14:27,390
value her music has been given
to me. Guess what? There's no

1150
01:14:27,390 --> 01:14:29,490
mechanism to give music artists
more money.

1151
01:14:30,150 --> 01:14:31,590
Ah, there you go.

1152
01:14:32,250 --> 01:14:36,240
And they aren't touring right
now. I had to. I had to internet

1153
01:14:36,240 --> 01:14:41,430
stock her and send her a check
in the mail. I hope it's the

1154
01:14:41,430 --> 01:14:46,620
correct address. Well, but I was
thinking about your lightning

1155
01:14:46,620 --> 01:14:50,130
Bitcoin payment system for
podcasters. Couldn't you do the

1156
01:14:50,130 --> 01:14:52,470
same thing for musicians? Yes.

1157
01:14:52,980 --> 01:14:57,390
Yes. And and to reiterate, I
think this is where this whole

1158
01:14:57,390 --> 01:15:00,450
value block comes in. If we look
at the basic mechanism Have an

1159
01:15:00,450 --> 01:15:04,980
RSS feed in an odd way. If you
put an album in there and we had

1160
01:15:04,980 --> 01:15:09,660
the per episode splits, you
could actually do the royalty

1161
01:15:09,660 --> 01:15:12,930
payments for anyone who worked
on the song The writing the

1162
01:15:12,930 --> 01:15:16,950
composing down to musicians down
to the tape op if you want the

1163
01:15:16,980 --> 01:15:20,340
engineer and they can get
payments for every single time

1164
01:15:20,340 --> 01:15:25,050
someone listens to it.
Absolutely. I track Yeah, I see

1165
01:15:25,050 --> 01:15:29,160
a lot. A lot of possibility for
this system. It is not in my

1166
01:15:29,160 --> 01:15:33,120
mind. None of it is regulated to
it has to be a show or anything

1167
01:15:33,120 --> 01:15:37,200
like that. And you want to use
this mechanism, please. It's

1168
01:15:37,200 --> 01:15:38,160
perfect for it.

1169
01:15:39,240 --> 01:15:40,890
Yeah, I mean, you could go per
track.

1170
01:15:41,280 --> 01:15:43,680
And you could do your bonuses.
You know, you can move some

1171
01:15:43,680 --> 01:15:48,150
extra extra SATs like ah like
this, this actual this this

1172
01:15:48,150 --> 01:15:50,790
lyric in the song I like this
boost it right there.

1173
01:15:51,510 --> 01:15:54,840
I didn't know evidently Dolly
Parton has like the greatest

1174
01:15:54,840 --> 01:15:57,900
publicist ever because she is
all over the place right now.

1175
01:15:59,460 --> 01:16:03,180
harden is an American
institution.

1176
01:16:04,200 --> 01:16:07,170
Yeah, I mean, like she there's a
PR push for her going on right

1177
01:16:07,170 --> 01:16:08,520
now. This is off the train. Oh,

1178
01:16:08,520 --> 01:16:09,930
she probably has a Christmas
special.

1179
01:16:11,220 --> 01:16:14,910
Yeah, so a documentary of her a
few weeks ago, and I didn't

1180
01:16:14,910 --> 01:16:19,110
realize that one of her big
songs where she's first sort of

1181
01:16:19,110 --> 01:16:23,130
broke out a country and went
crossover. I came into the night

1182
01:16:23,130 --> 01:16:29,190
it's a it's the core spot and
popular but Jolene, know when

1183
01:16:29,190 --> 01:16:32,940
Jolene, because she wrote that
one. This is one that she didn't

1184
01:16:32,940 --> 01:16:36,810
write, but people think nine to
five. Now she wrote that one

1185
01:16:36,810 --> 01:16:37,200
too.

1186
01:16:37,950 --> 01:16:40,200
I was gonna say there's not a
lot of songs I know that she

1187
01:16:40,200 --> 01:16:41,040
didn't write.

1188
01:16:41,970 --> 01:16:44,460
That's what I drew attention to
this one is because this

1189
01:16:44,460 --> 01:16:47,880
particular song everybody thinks
she wrote it, but she didn't. It

1190
01:16:47,880 --> 01:16:52,020
was somebody else. That she
picked it because it was like

1191
01:16:52,620 --> 01:16:59,820
her first crossover non country
hit. And so she specifically

1192
01:16:59,820 --> 01:17:04,410
chose it to kind of get a feel
for what that would be like. And

1193
01:17:04,440 --> 01:17:09,030
oh, okay, okay, I'm reading I'm
reading through the Wikipedia

1194
01:17:09,030 --> 01:17:14,670
now all I can do was the album
and let's see what was the big

1195
01:17:14,670 --> 01:17:19,920
hit from that she had Sandy
gallon as her manager Sandy

1196
01:17:19,920 --> 01:17:23,700
gallon is a living legend it now
that's that's not a publicist.

1197
01:17:23,700 --> 01:17:25,470
But Sandy Gallin knows
everybody.

1198
01:17:26,550 --> 01:17:27,900
That's the guy from New York,
right?

1199
01:17:28,620 --> 01:17:34,590
I even know the guy or gal.
Honestly, the name is super,

1200
01:17:34,590 --> 01:17:39,030
super well known. trying to
think what was it? Was it No, it

1201
01:17:39,030 --> 01:17:43,350
wasn't the stuff she did with
Emily Emmylou Harris.

1202
01:17:43,680 --> 01:17:49,350
Huh? No, wasn't that this was?
Gosh, this was maybe late, my

1203
01:17:49,350 --> 01:17:49,890
girl

1204
01:17:49,890 --> 01:17:56,520
higher and higher. No. 76
probably. heartbreaker

1205
01:17:56,550 --> 01:17:59,910
heartbreaker. Here you come
again. How about that one? Yeah,

1206
01:17:59,910 --> 01:18:00,600
that's it. Come

1207
01:18:00,600 --> 01:18:01,650
again.

1208
01:18:01,950 --> 01:18:05,220
You go. That's it? That's
exactly right. Yeah, it was that

1209
01:18:05,220 --> 01:18:09,930
one was not written by her. Ah,
so this is a long way of saying,

1210
01:18:10,140 --> 01:18:17,220
yeah. You could give royalties
to the writer. per, per track.

1211
01:18:17,250 --> 01:18:21,030
Mm hmm. You know, you split that
thing out anyway. Anyway, you

1212
01:18:21,030 --> 01:18:24,690
want to? That was a long way of
talking about lightning. I'm

1213
01:18:24,690 --> 01:18:26,880
glad we did that, though. Yeah.

1214
01:18:28,980 --> 01:18:34,650
See More, more from David
Langford. He says, Can you do

1215
01:18:34,650 --> 01:18:37,950
the same thing for musicians?
Yes, you can treat each artist

1216
01:18:37,950 --> 01:18:40,080
like a podcast and each song
like an episode.

1217
01:18:40,110 --> 01:18:42,930
You bet each season like an
album. Yep.

1218
01:18:43,260 --> 01:18:46,080
I think you should fly to Provo,
Utah and have a meeting with

1219
01:18:46,080 --> 01:18:48,810
Mindy about getting indie pop
artists on board with music

1220
01:18:48,810 --> 01:18:52,410
streaming. 2.0. Love your main
David Langford. wildon.

1221
01:18:52,500 --> 01:18:56,760
Love you mean it. And thanks for
the note, man. I hope

1222
01:18:57,060 --> 01:19:00,030
everything's okay. I'm glad I
was able to help you through the

1223
01:19:00,030 --> 01:19:03,030
hard times. That's what music
does podcasts do it too for lots

1224
01:19:03,030 --> 01:19:03,540
of people.

1225
01:19:04,200 --> 01:19:10,110
If anybody wants to fly me to
Provo, Utah game, just say I

1226
01:19:10,110 --> 01:19:15,000
want to turn it down. Okay. Do
you know the beautiful the state

1227
01:19:15,000 --> 01:19:17,460
with the highest percentage of
swingers in the whole country?

1228
01:19:17,970 --> 01:19:21,390
Yes, that has been a no agenda
topic. Thanks for reminding me.

1229
01:19:22,260 --> 01:19:22,920
Oh, is it?

1230
01:19:25,350 --> 01:19:28,290
For ACC knows these kinds of
stats for some reason I'm not

1231
01:19:28,290 --> 01:19:28,980
sure why.

1232
01:19:29,730 --> 01:19:33,870
Also very always very well
represented on the Pornhub stats

1233
01:19:33,870 --> 01:19:42,300
to break it down. by state. It's
true. Let's see. The last one is

1234
01:19:42,330 --> 01:19:47,370
anonymous, a single donation for
$20. And he just says no shout

1235
01:19:47,370 --> 01:19:49,530
out native just want to support
your efforts. Thank you for your

1236
01:19:49,530 --> 01:19:50,010
courage. Thank

1237
01:19:50,010 --> 01:19:53,610
you. We appreciate it. Thank you
for your courage, great value

1238
01:19:53,610 --> 01:19:56,580
for value. That's how it works.
All you got and we're pretty

1239
01:19:56,580 --> 01:20:00,240
darn transparent. There's
There's our income. It's been a

1240
01:20:00,240 --> 01:20:02,820
good week though this was
fantastic, especially with the

1241
01:20:03,150 --> 01:20:10,740
with the Benjamin at RSS calm.
Yeah, very very much appreciated

1242
01:20:10,740 --> 01:20:13,620
but doesn't matter how much it
is, is the value that you

1243
01:20:13,620 --> 01:20:16,920
attribute to it that we
appreciate. And for the entire

1244
01:20:16,920 --> 01:20:23,490
podcast index.org project which
as Benjamin already alluded to,

1245
01:20:23,490 --> 01:20:25,980
in this note, it's a whole lot
of people contributing their

1246
01:20:25,980 --> 01:20:28,800
time, their talent and their
treasure. If you got some

1247
01:20:28,800 --> 01:20:32,040
treasure to part with and we
really appreciate it, podcast

1248
01:20:32,040 --> 01:20:34,590
index.org scroll down to the
bottom, there's the big red

1249
01:20:34,590 --> 01:20:40,110
Donate button. Yes, smash that.
And I think also if you have a

1250
01:20:40,140 --> 01:20:44,730
funding tag compliant what
podcasting 2.0 compliant podcast

1251
01:20:44,730 --> 01:20:48,060
app, there should be a little
Donate button in the app right

1252
01:20:48,060 --> 01:20:53,460
now. Which pops up smash that to
smash it, smash that

1253
01:20:54,600 --> 01:21:02,400
we get for this. For the time
being we are making more revenue

1254
01:21:02,400 --> 01:21:07,350
on this podcast than Harry
Prince Harry and Megan. Because

1255
01:21:07,350 --> 01:21:08,130
they had started they're

1256
01:21:09,360 --> 01:21:13,800
not even they're not allowed to
use the the Royal Highness

1257
01:21:13,800 --> 01:21:17,400
monikers. But I think Spotify is
ignoring that and just using it.

1258
01:21:17,400 --> 01:21:20,460
We'll see. We'll see how long
before that just like the

1259
01:21:20,460 --> 01:21:24,390
Michelle Obama podcast has to be
opened up and will show up in

1260
01:21:24,390 --> 01:21:27,030
the index. Yeah, it won't take
long. There was a guardian

1261
01:21:27,030 --> 01:21:29,730
article that I just wanted to
touch on briefly called sinister

1262
01:21:29,730 --> 01:21:34,530
sounds. podcasts are becoming
the new medium of misinformation

1263
01:21:34,770 --> 01:21:36,420
with a big picture of Joe Rogan

1264
01:21:40,110 --> 01:21:45,180
insinuation that the guilt by
association is so gross.

1265
01:21:45,810 --> 01:21:50,940
It truly is and and what this
article is saying. And they

1266
01:21:50,940 --> 01:21:54,300
highlight a couple of podcasts
something I listened to

1267
01:21:54,330 --> 01:21:57,510
coincidentally. And they say
well, this is a problem here. We

1268
01:21:57,510 --> 01:22:00,090
don't have this. They're
literally saying and who wrote

1269
01:22:00,090 --> 01:22:00,840
this article.

1270
01:22:03,270 --> 01:22:04,020
Hey, why don't

1271
01:22:04,980 --> 01:22:11,970
Ariel Bogle Ariel mogul is
really calling for more

1272
01:22:11,970 --> 01:22:16,530
gatekeepers and more ways to
shut people down who's who speak

1273
01:22:16,530 --> 01:22:21,840
bad. It is the antithesis of
this entire project and go to

1274
01:22:21,840 --> 01:22:23,040
the what should be done.

1275
01:22:28,140 --> 01:22:32,070
better and more moderation is
only a partial answer to a more

1276
01:22:32,070 --> 01:22:39,930
difficult question. They don't
really have an area doesn't

1277
01:22:39,930 --> 01:22:42,180
really have a conclusion.
They're about what really should

1278
01:22:42,180 --> 01:22:45,720
it be done. But it's about
moderate. But ultimately, it's

1279
01:22:45,720 --> 01:22:48,750
about the content has to be
moderated. We have to have

1280
01:22:48,900 --> 01:22:54,390
trusted sources to moderate
moderate the content. Well, I

1281
01:22:54,420 --> 01:22:57,420
disagree. I mean, we are the
trusted source. So you know that

1282
01:22:57,600 --> 01:23:01,920
what shows up in podcast
index.org is 100% not moderated.

1283
01:23:02,550 --> 01:23:06,840
That's what you want to know.
And if you want to create some

1284
01:23:06,840 --> 01:23:10,950
moderated thing, then go to
podcast index.org sign up sign

1285
01:23:10,950 --> 01:23:16,290
up as a developer and created a
query so you get only the thing

1286
01:23:16,290 --> 01:23:20,160
that podcasts that you approve,
or an exclusionary one if you if

1287
01:23:20,160 --> 01:23:23,670
you need any extra API calls,
we'll help you out. But man

1288
01:23:23,670 --> 01:23:27,600
you're selling yourself short.
You really are selling yourself

1289
01:23:27,600 --> 01:23:28,200
short.

1290
01:23:29,880 --> 01:23:32,070
If you want to if you want to
screw over your customers and

1291
01:23:32,070 --> 01:23:34,770
they will help you do it I guess
but yeah, I mean it's not gonna

1292
01:23:34,770 --> 01:23:39,120
be any fun. My answer to that
whole thing is that Matt a BS

1293
01:23:39,150 --> 01:23:41,970
article Do you read his article
about the YouTube ban? No, I

1294
01:23:41,970 --> 01:23:42,990
didn't know I missed it

1295
01:23:43,920 --> 01:23:47,700
was really good and he's the his
his comment was you know because

1296
01:23:48,090 --> 01:23:48,570
you know

1297
01:23:48,660 --> 01:23:51,600
oh it was Oh yeah, I did see
come through and substack it was

1298
01:23:51,630 --> 01:23:53,910
it was all about canceling
wasn't it wasn't just about

1299
01:23:53,910 --> 01:23:55,050
YouTube was about

1300
01:23:55,710 --> 01:23:58,080
it was about YouTube's blog post
where they said they were gonna

1301
01:23:58,080 --> 01:24:01,950
write in in you know, any was it
ban any election and

1302
01:24:01,950 --> 01:24:03,420
misinformation about that the

1303
01:24:03,420 --> 01:24:04,920
vaccine any of that?

1304
01:24:04,950 --> 01:24:10,230
Yeah, so his this line got me
said if you want a population of

1305
01:24:10,230 --> 01:24:13,050
people to start thinking and
election was stolen from stolen

1306
01:24:13,050 --> 01:24:16,590
from them, it's hard to think of
a worse method than ordering a

1307
01:24:16,590 --> 01:24:20,250
news blackout there's just been
demonstrated that the last major

1308
01:24:20,250 --> 01:24:24,870
blackout was a fraud he's
absolutely right. Well, you want

1309
01:24:24,870 --> 01:24:27,990
to pay if you want people to
stop believing that you like

1310
01:24:27,990 --> 01:24:30,990
your if you think there's a
certain category of information

1311
01:24:30,990 --> 01:24:34,830
that is that is quote unquote,
misinformation. The worst thing

1312
01:24:34,830 --> 01:24:40,440
to do to try to fix it is to do
is to moderate it and then add

1313
01:24:40,470 --> 01:24:44,010
or remove it. It's like trying
to sit tell your daughter that

1314
01:24:44,010 --> 01:24:46,170
she can't date somebody some
gas.

1315
01:24:46,200 --> 01:24:49,050
Yeah, that always works. Yeah,
that works out.

1316
01:24:49,080 --> 01:24:53,790
Yeah. Me and your mom disapprove
of john, you know, or whatever.

1317
01:24:53,790 --> 01:24:56,040
I mean, it's usually been going
off with john immediately. Yeah.

1318
01:24:57,090 --> 01:25:03,090
Out the window. Yeah. Well,
we're against that. That's why

1319
01:25:03,090 --> 01:25:06,840
we created it. Mission number
one, very much achieved.

1320
01:25:07,500 --> 01:25:10,350
Preserve podcasting as a
platform for free speech.

1321
01:25:10,860 --> 01:25:15,390
There's no feed that that we is
no feed that will that will push

1322
01:25:15,390 --> 01:25:19,620
out. Everything is welcome. All
as long as it's valid, valid

1323
01:25:19,620 --> 01:25:24,450
XML. We're good to go on all
that. And we continue our quest

1324
01:25:24,450 --> 01:25:29,880
in retooling podcasting, as an
uninterruptible supply of value

1325
01:25:29,880 --> 01:25:34,380
to the entire ecosystem. And
we'll have more next week. No

1326
01:25:34,380 --> 01:25:37,050
doubt there'll be all kinds of
maybe it's next week. Is that

1327
01:25:37,050 --> 01:25:37,710
Christmas?

1328
01:25:38,790 --> 01:25:43,890
Yeah, we're, uh, we're, we're
gonna be recording early so that

1329
01:25:43,890 --> 01:25:47,220
we can, so we can do a drop on
Christmas Day.

1330
01:25:47,250 --> 01:25:49,410
What are we doing again? Do I
have that in Mike, do I have

1331
01:25:49,410 --> 01:25:52,020
that? Uh, do I have you on my
schedule? Let me see.

1332
01:25:52,739 --> 01:25:55,439
Yeah, I'm so busy. With your
guy. Yeah. Let

1333
01:25:55,440 --> 01:25:58,050
me see. I have a week.

1334
01:25:58,680 --> 01:26:02,640
Early with James and Sam sets
set the I think,

1335
01:26:02,670 --> 01:26:03,540
yeah, what do we do?

1336
01:26:04,770 --> 01:26:09,000
I think it's Tuesday. Tuesday.
22nd.

1337
01:26:12,300 --> 01:26:17,940
Well, I'll make sure I have any
mic. Maybe I'd maybe I got

1338
01:26:17,940 --> 01:26:20,850
confused. Well, we'll make sure
it happens. Because that's

1339
01:26:20,850 --> 01:26:24,690
the one we're doing his time
zones Australia. So he's, we're

1340
01:26:24,690 --> 01:26:28,410
gonna be right. Yeah, okay.
Yeah. But it'll be the 23rd for

1341
01:26:28,410 --> 01:26:29,130
him. Yes.

1342
01:26:29,160 --> 01:26:32,400
Yeah. The 23rd of 2021. He's
actually a whole year ahead.

1343
01:26:32,400 --> 01:26:33,600
It's crazy, though. So

1344
01:26:36,000 --> 01:26:38,940
we're gonna we're gonna record
with him. And then he wants us

1345
01:26:38,940 --> 01:26:41,670
to stick around for a bit and
record. They want to interview

1346
01:26:41,670 --> 01:26:46,440
us for pod land. sex. Yeah.
Okay. Yeah. But we'll do that.

1347
01:26:46,440 --> 01:26:50,070
We're doing that one on. And
then that'll come out on the

1348
01:26:51,000 --> 01:26:55,290
Christmas Day. And then we'll do
the next week is New Year's Day.

1349
01:26:55,350 --> 01:26:56,010
Yeah. Oh, we

1350
01:26:56,010 --> 01:26:56,880
got doing okay.

1351
01:26:57,090 --> 01:26:59,400
So we're gonna do another
another Tuesday.

1352
01:27:00,510 --> 01:27:04,440
I'm excited. I'm excited to talk
with James. I'm very excited to

1353
01:27:04,470 --> 01:27:05,790
see what he's got going on.

1354
01:27:11,040 --> 01:27:12,840
We don't stop for Christmas,
folks.

1355
01:27:14,610 --> 01:27:19,110
We we really don't do just keep
pushing ahead. What, what to see

1356
01:27:19,110 --> 01:27:22,260
what else is on deck? Do we have
any other any other business to

1357
01:27:22,260 --> 01:27:26,490
take care of any other namespace
talk just as well. Before I do

1358
01:27:26,490 --> 01:27:29,550
anything, please tell us where
we could find Frederick's

1359
01:27:29,550 --> 01:27:33,390
podcast that is featuring the
one and only Mr. Dave Jones,

1360
01:27:33,480 --> 01:27:36,660
because I say Frederick's
podcast, but I should actually

1361
01:27:36,660 --> 01:27:39,870
put it in the show notes. What's
it called? podcast?

1362
01:27:41,279 --> 01:27:46,889
Cut snack. cod snack. Yeah. KOD
s ma ck. Yeah. Christopher I

1363
01:27:46,889 --> 01:27:49,679
seen posted what it meant, but I
can't remember what he said.

1364
01:27:49,859 --> 01:27:53,309
Like he's Swedish like a little
snack. Is that what it is?

1365
01:27:53,729 --> 01:27:54,659
I thought so.

1366
01:27:55,620 --> 01:27:58,020
It sounds good to me. Let's go
with that. No, yeah,

1367
01:27:58,080 --> 01:28:01,170
I saw the translation somewhere
as well. Okay, could snack. I'm

1368
01:28:01,170 --> 01:28:05,040
gonna put that in right now.
Good snack, make sure that's in

1369
01:28:05,040 --> 01:28:10,500
the show notes. I'd love I'd
really love the is this a

1370
01:28:10,500 --> 01:28:12,690
change? Is this something
different that happened to the

1371
01:28:12,690 --> 01:28:13,350
website?

1372
01:28:14,729 --> 01:28:16,199
For what, when we noticed

1373
01:28:16,200 --> 01:28:19,470
did? I don't know. It just seems
spiffy Etsy. And maybe it's

1374
01:28:19,470 --> 01:28:20,880
because I'm on desktop right
now.

1375
01:28:20,910 --> 01:28:27,390
It looks so good. Oh, it does
look good. Yeah, we did. We did

1376
01:28:27,390 --> 01:28:31,560
some changes to her, I say we
don't plan to do some changes to

1377
01:28:31,560 --> 01:28:34,380
it and push it he just
restructured the back end to

1378
01:28:34,380 --> 01:28:38,490
make it easier to maintain going
forward. And it was it did make

1379
01:28:38,490 --> 01:28:41,520
it a lot better. Because I made
those changes with the good, the

1380
01:28:41,520 --> 01:28:46,500
stats good. And it was a lot
easier to handle. So I'm

1381
01:28:46,500 --> 01:28:48,900
thankful he did that. It didn't
change the way it looks or

1382
01:28:48,900 --> 01:28:52,080
functions. But on the backside.
It made it a lot easier to deal

1383
01:28:52,080 --> 01:28:52,320
with.

1384
01:28:52,380 --> 01:28:54,930
I just think it's kick ass
looking. I like the whole thing.

1385
01:28:55,470 --> 01:28:57,930
It looks great. And we get to
make the developer site look

1386
01:28:57,930 --> 01:29:00,990
like that because the API dev
site looks like garbage.

1387
01:29:01,560 --> 01:29:02,940
Let me see developer.

1388
01:29:03,750 --> 01:29:06,960
Yeah, they API podcast.
index.org. Looks like it's

1389
01:29:06,960 --> 01:29:13,380
not much there. Is there? Any
man. All right. Anything else I

1390
01:29:13,380 --> 01:29:15,840
can do for you, Dave? How can I
make your life easier?

1391
01:29:16,740 --> 01:29:22,080
Oh, no, I'm good. I just I'm
having fun just thinking about

1392
01:29:22,080 --> 01:29:24,210
dance. I'm having fun

1393
01:29:24,210 --> 01:29:29,700
thinking about SATs. Set. Hello,
everybody. I made that. He can't

1394
01:29:29,700 --> 01:29:33,990
spell stats. Without SATs. You
got it. That's right. Special

1395
01:29:33,990 --> 01:29:42,330
thanks to Ruth rofi who created
a little end of show mix for us.

1396
01:29:43,439 --> 01:29:44,459
He does Casco for Trent

1397
01:29:45,120 --> 01:29:49,050
MCs. I'm sorry Brophy does cast
covers cast coverage.com which

1398
01:29:49,170 --> 01:29:55,740
also has rotating chapter
images. We saw a demo of that

1399
01:29:55,740 --> 01:29:57,360
the other day. It looks very
cool.

1400
01:29:58,319 --> 01:30:02,309
Yeah, and He's a jazz we got
some in the show next.

1401
01:30:02,340 --> 01:30:06,450
Yeah, he's got too much time on
his hands. I really it's

1402
01:30:06,450 --> 01:30:09,780
fantastic. I love this. All
right, everybody. We will be

1403
01:30:09,780 --> 01:30:13,680
back again, with the Friday
show. It'll be done a little bit

1404
01:30:13,680 --> 01:30:16,050
earlier, as you heard and we'll
have James Cridland on from pod

1405
01:30:16,050 --> 01:30:19,230
news. So that should be that
should be super exciting. And

1406
01:30:19,230 --> 01:30:21,480
we'll have lots of things to
talk about. We'll unveil which

1407
01:30:21,480 --> 01:30:24,690
host is supporting the tags this
week. Everything all coming up.

1408
01:30:24,690 --> 01:30:27,120
And Dave have yourself a great
weekend, man.

1409
01:30:27,599 --> 01:30:29,969
I mean, you haven't ever built
one.

1410
01:30:30,029 --> 01:30:33,689
Yes. As we get ready for
Christmas. We're continue to

1411
01:30:33,689 --> 01:30:37,199
work on podcasting, podcasting.
2.0 We'll see you next week

1412
01:30:37,199 --> 01:30:39,179
everybody right here Till then
bye bye.

1413
01:30:55,020 --> 01:31:00,000
You have been listening to
podcasting 2.0 podcast in this

1414
01:31:00,000 --> 01:31:02,280
dialogue for more information.

1415
01:31:03,270 --> 01:31:05,910
Play cast coverage, I'm not
ashamed

1416
01:31:10,200 --> 01:31:11,910
of the gospel nice.

1417
01:31:15,120 --> 01:31:16,890
I'm not ashamed of the gospel.

1418
01:31:19,740 --> 01:31:28,050
Did a drop, drop, drop, drop,
drop, drop, drop, drop, drop,

1419
01:31:28,830 --> 01:31:29,190
drop.

1420
01:31:30,930 --> 01:31:31,920
Cut it up man.

1421
01:31:42,420 --> 01:31:43,350
fast

1422
01:31:47,790 --> 01:31:49,530
fast fast.

1423
01:31:52,410 --> 01:31:53,250
Fast

1424
01:31:54,479 --> 01:32:02,279
drip, drip, drip, drip, drip,
drip, drip, drip, drip, drip,

1425
01:32:02,909 --> 01:32:03,239
drip.

1426
01:32:05,700 --> 01:32:12,420
Laser precision surgical. Staff
man laser procedures surgical

1427
01:32:12,600 --> 01:32:16,710
drop. Top to bottom we get the
full stack man laser precision

1428
01:32:16,710 --> 01:32:26,070
surgical drop. Man laser
precision surgical laser

1429
01:32:26,070 --> 01:32:46,050
precision surgical laser
precision surgical laser

1430
01:32:46,050 --> 01:32:47,400
precision surgical.

1431
01:32:48,300 --> 01:32:51,330
We have to be fearless and we
have to move ahead with big

1432
01:32:51,330 --> 01:32:52,320
brass balls.

1433
01:32:53,460 --> 01:32:54,450
Brass balls,

1434
01:32:55,979 --> 01:32:59,459
brass balls, brass balls.

1435
01:33:00,960 --> 01:33:03,030
Brass balls. Drop.

1436
01:33:03,390 --> 01:33:04,440
pockets are cool.