1
00:00:00,000 --> 00:00:04,800
Oh, podcasting 2.0 for September
25 2020, this is episode number

2
00:00:04,800 --> 00:00:11,400
four. And we're making headway
trying to stick with the

3
00:00:11,400 --> 00:00:14,700
nautical terms for a little bit,
see how that goes. Full speed

4
00:00:14,700 --> 00:00:20,430
ahead underway. And allow me to
introduce my partner and co

5
00:00:20,430 --> 00:00:26,610
founder of podcasts. index.org.
The one and only Dave Jones was

6
00:00:26,610 --> 00:00:28,020
a it was a

7
00:00:31,800 --> 00:00:34,140
I did did the work. I did the
work.

8
00:00:34,320 --> 00:00:37,560
You've been doing the work my
friend, no one does the work

9
00:00:37,560 --> 00:00:39,780
like you do. Holy crap. Am.

10
00:00:40,410 --> 00:00:41,790
I did eyebrow clips.

11
00:00:41,880 --> 00:00:45,030
Oh, wait, you did even more
work. You did more work than

12
00:00:45,030 --> 00:00:48,450
just the work you're doing. You
brought clips. Nice. I did work

13
00:00:48,450 --> 00:00:54,060
and work. I guess I should thank
the folks over at Spotify for

14
00:00:55,110 --> 00:00:57,870
the timing of proving our point.

15
00:00:58,230 --> 00:01:00,330
What does it feel like to beat
the platform?

16
00:01:02,190 --> 00:01:06,270
It's really interesting. No, not
at all. What you know,

17
00:01:06,270 --> 00:01:09,090
obviously, I know that we're
just one app, click away from

18
00:01:09,090 --> 00:01:12,300
somewhere else. But what I liked
the most is that without even

19
00:01:12,300 --> 00:01:17,490
discussing it, and when we don't
need to, I guess, my my partner

20
00:01:17,490 --> 00:01:20,160
Dvorak. He's like, Yeah, we
don't even belong there. What

21
00:01:20,160 --> 00:01:24,270
the hell, of course, you know,
so I'm glad we're off that. But

22
00:01:24,270 --> 00:01:27,030
for those who haven't heard the
story was quite interesting.

23
00:01:27,630 --> 00:01:33,570
Where he a few weeks back, I I
inquired with Spotify, and also

24
00:01:33,570 --> 00:01:37,230
Amazon who were sending out
emails to the owner emails and

25
00:01:37,230 --> 00:01:41,070
RSS feeds clearly saying, hey,
come in, and, you know, manage

26
00:01:41,070 --> 00:01:44,100
your podcasts in our in our
portal. And I know I hadn't

27
00:01:44,100 --> 00:01:48,240
submitted. So Amazon, we're not
they're not submitted. That's

28
00:01:48,240 --> 00:01:51,150
good. And I think I tried to
Stitcher, they never respond.

29
00:01:51,150 --> 00:01:54,960
There's no way to do that to
black humans there at all.

30
00:01:54,960 --> 00:01:58,320
There's nothing going on there.
And Spotify said, hey, you know,

31
00:01:58,530 --> 00:02:01,530
it's not associated with my
account. This is my emails been

32
00:02:01,530 --> 00:02:04,470
my email forever. So I don't
know how that got in there. And

33
00:02:04,470 --> 00:02:07,410
then they sent me an email after
I filled out the form and said,

34
00:02:07,410 --> 00:02:12,150
Well, you go to this link, and
from this link, you can submit a

35
00:02:12,150 --> 00:02:15,600
copyright infringement claim and
the end the link right there

36
00:02:15,600 --> 00:02:18,900
says Do not fill out this form
without lawyer link. Okay, so

37
00:02:18,930 --> 00:02:25,080
But no, I forgot that. And it's
my belief that they are getting

38
00:02:25,080 --> 00:02:27,930
ready to roll out ads. I have
some examples that I played on

39
00:02:27,930 --> 00:02:30,600
the no agenda show where they
definitely and they they made a

40
00:02:30,600 --> 00:02:34,380
big deal of this in January,
about their, you know, their

41
00:02:34,380 --> 00:02:38,070
podcast, automatic dynamic,
systematic hydromatic ad

42
00:02:38,070 --> 00:02:40,860
insertion, which means they're
rolling out there since it's

43
00:02:40,860 --> 00:02:42,930
streaming they stream to their
player.

44
00:02:44,880 --> 00:02:47,820
I've got I've got a perfect
example of what the future of

45
00:02:47,820 --> 00:02:49,350
podcast advertising looks like.

46
00:02:49,380 --> 00:02:51,030
Oh do tell when she got

47
00:02:51,420 --> 00:02:53,970
clip. Clip to AP report.

48
00:02:54,180 --> 00:02:57,510
I Mike Rossi are reporting to
Republican led Senate Committees

49
00:02:57,510 --> 00:03:00,420
release a report on Hunter
Biden's work in Ukraine.

50
00:03:00,900 --> 00:03:03,990
Republican Senator Ron Johnson
of Wisconsin, the chairman of

51
00:03:03,990 --> 00:03:06,630
the Senate Homeland Security and
Governmental Affairs Committee

52
00:03:06,720 --> 00:03:09,870
says the probe into Hunter
Biden's affairs in Ukraine was a

53
00:03:09,870 --> 00:03:13,230
good investigation and it was
not politically motivated. On

54
00:03:13,230 --> 00:03:16,200
Wednesday, Johnson's Committee
and the Senate Finance Committee

55
00:03:16,230 --> 00:03:19,290
released their report, which
concludes Hunter Biden's paid

56
00:03:19,290 --> 00:03:22,140
board position with the
Ukrainian gas company Burisma

57
00:03:22,170 --> 00:03:25,020
created conflict of interest
concerns for the Obama

58
00:03:25,020 --> 00:03:28,290
administration at the time Vice
President Joe Biden was in

59
00:03:28,290 --> 00:03:31,680
charge of administration policy
with Ukraine. The Biden campaign

60
00:03:31,680 --> 00:03:35,130
immediately pan to the report
Mike cross the Washington

61
00:03:35,190 --> 00:03:35,850
remember the

62
00:03:35,850 --> 00:03:39,150
best time of your life has been
eating Arby's pecan chicken

63
00:03:39,150 --> 00:03:43,020
salad Wait a minute so did you
get this from Spotify? Where

64
00:03:43,019 --> 00:03:47,069
did you get this? Oh, no, I got
this off the carousel on the

65
00:03:47,069 --> 00:03:51,959
podcast index homepage. Oh, like
this was so I saw AP report

66
00:03:52,109 --> 00:03:54,269
right on there they have
evidently they have like this

67
00:03:54,269 --> 00:03:54,659
little

68
00:03:55,500 --> 00:03:59,490
like It's like Ford or something
that comes out? Yeah, yes. Just

69
00:03:59,520 --> 00:04:03,360
like in each one of them is like
a minute and a half right? And

70
00:04:03,360 --> 00:04:07,920
45 seconds of it. You're kidding
is the report and the other 45

71
00:04:07,920 --> 00:04:10,950
seconds of it is add fresh in
your memory.

72
00:04:11,070 --> 00:04:15,060
You got the sliced grapes. And
then what do you sit there and

73
00:04:15,060 --> 00:04:17,070
wait to see if something else
comes? Is there something I

74
00:04:17,070 --> 00:04:17,580
guess

75
00:04:18,360 --> 00:04:22,110
we have the meats and I'm
thinking okay, next report. But

76
00:04:22,110 --> 00:04:25,380
no, no, just when deciding how
and when to another.

77
00:04:26,010 --> 00:04:28,890
Another ad for this time is for
IBM Watson.

78
00:04:29,099 --> 00:04:31,619
And the thing that that Spotify
is knowings from the way I

79
00:04:31,619 --> 00:04:33,719
understand it, it first of all,
it's highly targeted. They're

80
00:04:33,719 --> 00:04:37,079
building the Facebook of ads for
podcasts, and that's what they

81
00:04:37,079 --> 00:04:39,869
say and that's fine. I have
nothing against it. Obviously.

82
00:04:41,399 --> 00:04:44,249
It'll be streaming so you can't
fast forward. So non

83
00:04:44,249 --> 00:04:48,959
interruptible ads, obviously.
Although this format that APA

84
00:04:48,959 --> 00:04:51,299
just showed you know that's an
easy one. Once you've listened

85
00:04:51,299 --> 00:04:53,399
to the report, you bail and
everyone will know

86
00:04:53,400 --> 00:04:56,490
it. Yeah. How can that even with
that can't work that's not a

87
00:04:56,490 --> 00:04:58,290
sustainable ad model. I come

88
00:04:58,290 --> 00:05:01,770
from the advertising business.
So I Understand and I, I know

89
00:05:01,770 --> 00:05:03,810
what they're going to do and how
they're doing it and what this

90
00:05:03,810 --> 00:05:06,780
will mean. And it'll mean
something for a while. But the

91
00:05:06,780 --> 00:05:10,290
tracking is really what they're
touting over at Spotify, the

92
00:05:10,290 --> 00:05:16,740
targeted by demographic by race,
age, gender, sex, religion,

93
00:05:16,740 --> 00:05:19,530
probably that you can learn a
lot from looking at someone's

94
00:05:19,530 --> 00:05:23,760
music collection, and oh they
associate with. So they do have

95
00:05:23,760 --> 00:05:26,580
a lot of a lot of data and of
course, what podcasts you listen

96
00:05:26,580 --> 00:05:34,410
to. So anyway, long story short
on that, is they pulled us down,

97
00:05:34,410 --> 00:05:36,480
I believe, because they're
shoring up all of their

98
00:05:36,480 --> 00:05:40,020
contracts to make sure they have
the right to do this. And it

99
00:05:40,020 --> 00:05:43,890
would make sense looking at the
terms and conditions. For a

100
00:05:43,890 --> 00:05:48,090
podcast, you basically admits
your typical worldwide, US

101
00:05:48,510 --> 00:05:52,530
exclude worldwide license you
give to them fully paid, it even

102
00:05:52,530 --> 00:05:56,820
says fully paid, which means $0
are actually you paid on a

103
00:05:56,820 --> 00:06:02,280
monthly basis you're paying. And
they can do anything they want,

104
00:06:02,310 --> 00:06:07,860
which includes copying, editing,
creating, creating derivative

105
00:06:07,860 --> 00:06:11,280
works. So that's all a non
starter, as Devorah would say.

106
00:06:11,280 --> 00:06:14,430
It's kind of the dummy contract.
But we got a lot of dummies who

107
00:06:14,490 --> 00:06:17,400
people don't read that. People
just Oh, read the Terms of

108
00:06:17,400 --> 00:06:18,030
Service. And

109
00:06:18,090 --> 00:06:20,520
I mean, if you're a podcaster,
you're making it and you've

110
00:06:20,550 --> 00:06:25,590
you're in like episode 125. And
you've never made more than five

111
00:06:25,590 --> 00:06:28,980
bucks off of Patreon, right? I
mean, you probably gonna sign

112
00:06:28,980 --> 00:06:30,060
whatever they put in front of
you.

113
00:06:30,450 --> 00:06:33,120
Yeah. And there's a big draw, of
course, like, oh, maybe it'll be

114
00:06:33,120 --> 00:06:36,780
discovered. And but quite
honestly, what I don't see is

115
00:06:36,780 --> 00:06:39,960
them sharing any of the revenue,
which they'll have to do

116
00:06:39,960 --> 00:06:43,950
something like that. Because the
Amazon will do it, and Google

117
00:06:43,950 --> 00:06:47,460
will do it. And it's just going
to be it. It's kind of making it

118
00:06:47,460 --> 00:06:52,530
easy for us. Because, you know,
yeah, there's all kinds of

119
00:06:53,010 --> 00:06:56,190
endorsements and ads and all
kinds of podcasts. But we're not

120
00:06:56,190 --> 00:07:00,810
a structural outside of these
walls, you know, so it's in

121
00:07:00,810 --> 00:07:03,270
podcasts that you listen to,
without advertising will not

122
00:07:03,270 --> 00:07:06,930
you'll be forced to listen to at
least an ad I believe, before it

123
00:07:06,930 --> 00:07:08,760
starts. And so

124
00:07:08,760 --> 00:07:12,060
the only, you know, the problem
with the AP, like the AP report

125
00:07:12,060 --> 00:07:14,730
and stuff that you just played
and all the automatic insertion

126
00:07:15,000 --> 00:07:20,760
is that it's so crude like, jar.
Jar. Yes. Yes. Because that, you

127
00:07:20,760 --> 00:07:25,140
know, it was like, you know, the
Biden campaign immediately panda

128
00:07:25,140 --> 00:07:30,030
report boom at Arby's, I mean,
not even a second. Yeah, was and

129
00:07:30,030 --> 00:07:31,740
you're like, you're like, Whoa,
what just happened.

130
00:07:31,860 --> 00:07:36,630
So when I started pod show, back
in 2006, I think we did all

131
00:07:36,630 --> 00:07:39,780
this, we experimented with all
this, we had the automatic

132
00:07:39,780 --> 00:07:44,880
insertions, tons of stuff, we I
think the thing that I would

133
00:07:44,880 --> 00:07:48,600
most proud of, is across the
network of shows we had

134
00:07:48,600 --> 00:07:51,090
something called the golden
ticket, you can already imagine

135
00:07:51,120 --> 00:07:54,960
what it refers to, yeah, it's
anvil Monty, then it would be an

136
00:07:54,960 --> 00:08:00,090
insertion into an X number of
shows, at a predetermined spot,

137
00:08:00,090 --> 00:08:03,120
by the way. So every one every
every, everyone within our

138
00:08:03,120 --> 00:08:05,460
network knew who was going to
show up. And they actually had a

139
00:08:05,460 --> 00:08:09,000
way to tag that where it would
fall in their in their program,

140
00:08:09,000 --> 00:08:11,730
we'd automatically insert if
someone had won a golden ticket

141
00:08:11,730 --> 00:08:14,310
or not. And there were some
prize attached to that. And that

142
00:08:14,310 --> 00:08:19,860
was a cool use of, of insertion
technology. But everything else

143
00:08:20,580 --> 00:08:23,760
kind of failed. And, and the
main reason is there's no

144
00:08:23,760 --> 00:08:26,940
statistics. And this is what
Spotify wants to solve. This is

145
00:08:26,940 --> 00:08:30,120
obviously what Amazon wants to
do. This is what Google wants to

146
00:08:30,120 --> 00:08:33,630
do. And that's all fine. I just
feel and I think I define this

147
00:08:33,630 --> 00:08:39,960
on on podcast, index dot social.
A podcast has an RSS feed that

148
00:08:39,960 --> 00:08:45,030
you can access. An a podcast app
allows you to, at minimum,

149
00:08:45,120 --> 00:08:51,150
manually add a feed. And and if
Spotify would be very different

150
00:08:51,150 --> 00:08:52,830
to me if they allowed you to do
that

151
00:08:53,670 --> 00:08:58,830
is not a podcast, if you if it's
not publicly available through a

152
00:08:58,830 --> 00:09:04,260
fee to more to multiple apps, if
it's just a you know, that goes

153
00:09:04,260 --> 00:09:07,740
back to the I remember at the
beginning of podcasting, when,

154
00:09:08,130 --> 00:09:11,670
like one of the first apps I
ever wrote that had anything to

155
00:09:11,670 --> 00:09:17,070
do with RSS, or podcasting or
anything like that was a there's

156
00:09:17,070 --> 00:09:19,770
a radio show out of California
called standard raising that I

157
00:09:19,770 --> 00:09:25,080
listened to all the time. And it
was very hard to get to get that

158
00:09:25,080 --> 00:09:28,080
show out here. So this was I
don't remember what year this

159
00:09:28,080 --> 00:09:33,300
was maybe 2005. And when they
jumped on board, the the the

160
00:09:33,330 --> 00:09:37,230
downloadable show, train and so
this was before they had a

161
00:09:37,230 --> 00:09:41,550
podcast, they would just post
their mp3. So I created this and

162
00:09:41,550 --> 00:09:44,100
then we'll about a few months
later after they did that they

163
00:09:44,100 --> 00:09:48,120
turned it into an XML feed with
full blown podcast feed. Oh, so

164
00:09:48,180 --> 00:09:54,150
I wrote this Windows program in
assembly language that would it

165
00:09:54,150 --> 00:09:56,640
was crazy. I still got it. I've
still got all my sources. It's

166
00:09:56,640 --> 00:09:59,220
weird to look at it now. But
this thing that would parse the

167
00:09:59,220 --> 00:10:02,250
feed and down Look at the
download at all, and I'm gonna

168
00:10:02,250 --> 00:10:06,330
jazz. But you know the thing,
the thing about that is back

169
00:10:06,330 --> 00:10:09,780
then there was quite a few
things like that where people

170
00:10:09,780 --> 00:10:12,960
would have an app or make an app
or a script that would just

171
00:10:12,960 --> 00:10:17,400
handle one show. And so I
remember, radio shows would do

172
00:10:17,400 --> 00:10:21,750
that to like, think Glenn Beck
at the time, or one of the I

173
00:10:21,750 --> 00:10:25,140
don't remember who it is one of
the right wing talkers, would

174
00:10:25,200 --> 00:10:27,960
they they had an app for their
show. And you could it was a

175
00:10:27,990 --> 00:10:30,810
quote unquote, podcast, but you
could only get it through their

176
00:10:30,810 --> 00:10:34,800
app. It feels like that's what
you know, that's what we're

177
00:10:34,800 --> 00:10:38,490
going back to. In a sense, it's
like we're coming back around to

178
00:10:38,490 --> 00:10:41,430
where people are making cific
apps for specific shows.

179
00:10:41,459 --> 00:10:45,449
I was thinking about that. And
there's something to be said,

180
00:10:45,449 --> 00:10:48,059
I've been reading a lot about
progressive web apps. And mainly

181
00:10:48,059 --> 00:10:54,059
because a story came out.
Believe it or not on the verge,

182
00:10:54,059 --> 00:10:57,149
I think, let me just see if I
can find it. I didn't prepare

183
00:10:57,149 --> 00:11:01,649
for this. The Verge by the way,
I found is the website that

184
00:11:01,679 --> 00:11:07,379
developers go to to see how much
bandwidth they can use on one

185
00:11:07,379 --> 00:11:11,879
page. Apparently, the verd most
trackers, the most ads the most

186
00:11:11,879 --> 00:11:15,149
everything of all like, hey, I
want to see some performance of

187
00:11:15,149 --> 00:11:17,459
your machine. Yeah, let's go to
the verge.

188
00:11:17,760 --> 00:11:21,510
Like uBlock Origin is good. Just
quit. Like it just stops when it

189
00:11:21,510 --> 00:11:22,890
is like nah, can't handle this.

190
00:11:23,550 --> 00:11:30,480
It was it was gaming. Here we
go. I think it's Amazon's Luna.

191
00:11:32,100 --> 00:11:35,340
The gaming is lame. Note that
it's a gaming cloud service.

192
00:11:35,790 --> 00:11:39,000
Oh, all this? Yeah. Like I like
x cloud and stadia,

193
00:11:39,390 --> 00:11:42,960
right. But what they've done is
instead of because of the apple

194
00:11:42,960 --> 00:11:45,660
penalty of if you want to make
money or charge money through

195
00:11:45,660 --> 00:11:49,500
the App Store, then you have to
pay the 30% Vig. So what they

196
00:11:49,500 --> 00:11:54,720
did is they built a progressive
web app. Because apparently, I

197
00:11:54,720 --> 00:11:57,090
guess has been known for a long
time, you can really stream

198
00:11:57,090 --> 00:11:59,760
anything you need. I mean, the
the web, the Progressive Web,

199
00:11:59,760 --> 00:12:04,080
app architecture is apparently
so good that you can really

200
00:12:04,140 --> 00:12:07,110
build an app like experience
with it. And you can even Of

201
00:12:07,110 --> 00:12:10,830
course, you know, put a an icon
on the launcher of your phone.

202
00:12:11,520 --> 00:12:15,000
So it looks just like an app
behaves, as they say just like

203
00:12:15,000 --> 00:12:17,250
an app. And that's for gaming.
If gaming is doing it, then it's

204
00:12:17,250 --> 00:12:19,740
got to be, it's got to be pretty
good. So what that led me to

205
00:12:19,740 --> 00:12:24,930
think about is, I liked the
simple player, so much Martin

206
00:12:24,930 --> 00:12:27,480
simple player, and we got to
talk about this thing is great.

207
00:12:27,870 --> 00:12:32,640
There's nothing I have nothing
against the concept of you being

208
00:12:32,640 --> 00:12:37,200
able to go to a template and
say, Here's my show, here's the

209
00:12:37,230 --> 00:12:41,460
artwork, and I just want a
simple one click app for people

210
00:12:41,460 --> 00:12:43,590
to put on their phone that is
just so they can catch up with

211
00:12:43,590 --> 00:12:45,870
my show you what I mean?

212
00:12:47,190 --> 00:12:48,180
Yeah, I could see that.

213
00:12:48,210 --> 00:12:52,440
I can see people wanting to have
that. So yeah, it's not a full

214
00:12:52,440 --> 00:12:57,390
blown podcast player. But it's a
totally valid use of it. So I

215
00:12:57,390 --> 00:13:01,260
don't really mind that. Why not?

216
00:13:01,770 --> 00:13:06,540
Wait, we already pull images.
The you know, so a feed, you get

217
00:13:06,540 --> 00:13:08,160
the down, you get the mp3? Well,
that's

218
00:13:08,160 --> 00:13:11,070
my point is you could do that
yourself. That could be a

219
00:13:11,070 --> 00:13:14,040
template where and if you just
wanted that for yourself for

220
00:13:14,040 --> 00:13:17,190
your show, that you want people
to use that just for your show.

221
00:13:17,190 --> 00:13:18,450
That's also possible.

222
00:13:19,140 --> 00:13:22,530
Well could could you deliver the
pieces of the web app in the

223
00:13:22,530 --> 00:13:27,630
feed as well? Like, I don't, I'm
not up on amount up to speed on

224
00:13:27,630 --> 00:13:30,660
all of the progressive web apps
I know is basically I just think

225
00:13:30,660 --> 00:13:33,540
it works like a web browser.
Yeah. It's like you

226
00:13:33,540 --> 00:13:35,850
deconstructed the web browser.
Yeah, put the parts of it in

227
00:13:35,850 --> 00:13:35,940
that

228
00:13:36,330 --> 00:13:39,840
just launches in its own in its
own environment, I guess. So

229
00:13:39,840 --> 00:13:40,710
it's just thinking,

230
00:13:40,890 --> 00:13:44,970
you're delivering the image. And
in the end, the mp3 already in

231
00:13:44,970 --> 00:13:49,290
the feed, you can probably
deliver other parts of the app.

232
00:13:49,410 --> 00:13:50,370
Interesting there too.

233
00:13:50,580 --> 00:13:55,350
Well, so we're kind of jumping
ahead, but I did want to Well,

234
00:13:55,380 --> 00:13:59,760
since we're talking about it, I
need to have a list and you've

235
00:13:59,760 --> 00:14:03,030
already started to help me day.
And I'm thinking maybe we get

236
00:14:03,030 --> 00:14:07,770
drunk playdough involved in this
drunken or drunk things drunk

237
00:14:07,770 --> 00:14:11,220
play No, I don't remember drunk
playdough is doing a version of

238
00:14:11,220 --> 00:14:16,710
the homepage which I've seen the
the mock up of it looks really

239
00:14:16,710 --> 00:14:17,160
good.

240
00:14:17,430 --> 00:14:20,670
Oh, yes. Beautiful. Drunk.
Drunken I think is known as No

241
00:14:20,670 --> 00:14:24,450
sir your restaurant play drunk
play? Yes. Oh, so pretty. And he

242
00:14:24,450 --> 00:14:26,580
keeps teasing me with
screenshots and like give it to

243
00:14:26,580 --> 00:14:27,480
me, let me have it.

244
00:14:27,510 --> 00:14:32,070
So on this, whatever he's
building, I'd love to obviously

245
00:14:32,070 --> 00:14:34,950
have a place where we can say
Oh, and here's all the different

246
00:14:34,950 --> 00:14:38,700
people who are using the index
and I'd like to have the apps

247
00:14:38,700 --> 00:14:41,700
there I'd want to have you know,
whatever publishing systems just

248
00:14:41,700 --> 00:14:45,270
all we need a page or something
where that's up there and and

249
00:14:45,270 --> 00:14:48,960
honestly, where if someone puts
it on there so that I don't

250
00:14:48,960 --> 00:14:52,080
forget about it because I'm
notoriously bad at this stuff.

251
00:14:53,340 --> 00:14:56,610
Because we need to be promoting
all these different, all these

252
00:14:56,610 --> 00:15:00,120
different initiatives. And what
he looks like he's Korea. Seeing

253
00:15:00,120 --> 00:15:02,430
some functionality on the
homepage itself, you know, we've

254
00:15:02,430 --> 00:15:07,290
got all of this. Just need to be
able to push more people from it

255
00:15:07,350 --> 00:15:08,490
to other places.

256
00:15:09,690 --> 00:15:13,410
Yeah, I agree that I like that I
like his direction for this

257
00:15:13,410 --> 00:15:18,240
design, because it's not. It's
just basically, you know, the

258
00:15:18,330 --> 00:15:21,990
pieces we already have, but
they, they look better. He's not

259
00:15:21,990 --> 00:15:24,810
like, okay, let's, you know,
we're not our thing has been,

260
00:15:24,810 --> 00:15:27,990
we're not going to compete with
with app developers and that

261
00:15:27,990 --> 00:15:30,870
kind of thing. So I like this,
it just preserves the

262
00:15:30,870 --> 00:15:34,320
simplicity, the existing
components, were just okay,

263
00:15:34,530 --> 00:15:38,250
here's what we got, here's what
you can do. And that's it. But

264
00:15:38,250 --> 00:15:42,690
it's, but it's so much more, you
know, easy on the eyes to look

265
00:15:42,690 --> 00:15:42,870
at,

266
00:15:42,900 --> 00:15:46,770
oh, well, he's he actually has
some design skills. And like you

267
00:15:46,770 --> 00:15:47,580
and I, I guess,

268
00:15:48,000 --> 00:15:51,420
agree that it would be so it'd
be so easy to just add an extra

269
00:15:52,740 --> 00:15:55,920
piece on this where it just
lists all that. And we can pull

270
00:15:55,920 --> 00:15:59,850
that dynamically out of the law?
Exactly. Exactly. Exactly.

271
00:15:59,850 --> 00:16:01,980
Nobody has to touch it. Oh, I

272
00:16:01,980 --> 00:16:07,560
love automation. Yes. So the
last time we spoke, you declared

273
00:16:07,560 --> 00:16:12,030
heads down for the week, you
were working on the shoring

274
00:16:12,030 --> 00:16:17,040
things up infrastructure, load
balancing servers. And of

275
00:16:17,040 --> 00:16:20,430
course, the place where most
people can follow along is

276
00:16:21,120 --> 00:16:26,370
podcast index dot social. I also
follow the GitHub for that what

277
00:16:26,370 --> 00:16:31,230
I understand seems like you kind
of have like a 6040 mix of 60

278
00:16:31,230 --> 00:16:35,430
infrastructure and 40% still
working on different different

279
00:16:35,460 --> 00:16:38,520
things to pull out of the you
know, to expose in the API.

280
00:16:39,810 --> 00:16:44,820
Yeah, so as usual, what I say
that I'm going to do in advance

281
00:16:44,820 --> 00:16:51,300
is only slightly related to what
actually gets done. You just

282
00:16:51,450 --> 00:16:54,510
pretty much have to take the
take my aims with a grain of

283
00:16:54,510 --> 00:16:58,740
salt, but the what, what I'd
spent a lot of time on earlier

284
00:16:58,740 --> 00:17:03,570
in the week is loading, some is
loading an extra batch of feeds

285
00:17:03,570 --> 00:17:07,500
that Mike had sent to us, Mike,
on the note,

286
00:17:07,829 --> 00:17:11,669
this, if this is interesting,
I've seen, I think multiple

287
00:17:11,669 --> 00:17:16,319
people show up and say, Hey,
I've got a database of this,

288
00:17:16,349 --> 00:17:19,379
I've got a database of that. And
it's not all the same stuff. Is

289
00:17:19,379 --> 00:17:21,539
it? What do you what do you see?
Well, I

290
00:17:21,540 --> 00:17:25,620
had to write a, I had to write a
script, and they would import

291
00:17:25,620 --> 00:17:30,540
that and do it in a way that
was, you know, kind of sane. And

292
00:17:30,540 --> 00:17:34,410
so the script just looked, you
know, looks to make sure that

293
00:17:34,410 --> 00:17:37,770
it's not that it's not something
we already have all the all the

294
00:17:37,770 --> 00:17:40,410
stuff you would expect. And so
that just took a while to get

295
00:17:40,410 --> 00:17:45,210
that constructed, but then, you
know, and also a way to import

296
00:17:45,210 --> 00:17:49,320
it. And it's not going to do it
in mass in a way that's going to

297
00:17:49,440 --> 00:17:53,370
hurt performance on the side. So
that's all run in. And it's just

298
00:17:53,370 --> 00:17:57,690
important. It's been importing
since Monday. So we're at about,

299
00:17:58,020 --> 00:18:00,630
it's Eastern, it's like one and
a half million feet.

300
00:18:00,900 --> 00:18:03,240
And where did he get these from?
You just collected them over the

301
00:18:03,240 --> 00:18:04,680
years? Yeah, he's got

302
00:18:04,680 --> 00:18:08,190
he's, he's got his own project
that he's been working on for a

303
00:18:08,190 --> 00:18:12,900
while. And, you know, just he
saw, like, you know, like minded

304
00:18:12,900 --> 00:18:15,900
like, and he was like, Hey,
let's, let's swap databases. And

305
00:18:15,900 --> 00:18:18,960
I'm like, Yeah, sure. I'm gonna
post our database anyway. So

306
00:18:18,960 --> 00:18:21,030
he's like, Well, here you go.
Here's a here's my database.

307
00:18:21,810 --> 00:18:25,500
So part of the philosophy is we
want people sending stuff in so

308
00:18:25,500 --> 00:18:29,970
we can send it out. So he gets
this back in multiple ways he is

309
00:18:29,970 --> 00:18:33,390
he is integrating. Is he using
this using the index?

310
00:18:33,660 --> 00:18:36,180
I'm not sure I hadn't heard from
him in about a week or so. So

311
00:18:36,180 --> 00:18:40,620
I'm not sure what he's doing on
as far as hooking into the API

312
00:18:40,650 --> 00:18:45,450
if he's doing any of that yet.
But, like, right before, this,

313
00:18:45,450 --> 00:18:51,000
maybe an hour ago, I posted our
first download to archive.org,

314
00:18:51,000 --> 00:18:53,730
which is just our faces our
feeds table. Yeah, I saw that.

315
00:18:53,730 --> 00:18:57,870
Very cool. Yeah. So that's every
feed we've got, whether it's

316
00:18:58,860 --> 00:19:01,710
garbage or not, or anything like
that. It's the full thing. It's

317
00:19:01,710 --> 00:19:05,910
about a little over 1.2 million
feeds. Yeah.

318
00:19:07,530 --> 00:19:10,110
1123. Yeah.

319
00:19:10,710 --> 00:19:14,370
Yeah, that's as of right now. So
I was wanting to originally wait

320
00:19:14,370 --> 00:19:19,890
until, until we got everything
imported from Mike's batch,

321
00:19:19,890 --> 00:19:21,750
because I was like, Well, it'd
be more complete that way by

322
00:19:21,750 --> 00:19:24,120
laying it down. But I'm just
procrastinate too long on that.

323
00:19:24,120 --> 00:19:26,700
So we went ahead and did it. And
then I'll just do another, you

324
00:19:26,700 --> 00:19:28,470
know, I'll do another dump next
week. I mean, takes five

325
00:19:28,470 --> 00:19:32,190
minutes. Right? And, you know,
it'll, we'll just begin to

326
00:19:32,190 --> 00:19:37,800
update that. Hopefully, at least
once or twice a month would be

327
00:19:37,800 --> 00:19:40,620
it. If I can automate it. I
will. And then it'll just be a

328
00:19:40,620 --> 00:19:43,710
thing that just happens on a
regular basis. Nice. That'd be

329
00:19:43,710 --> 00:19:46,740
great. Yeah, but that is just
the fees for now. It's not the

330
00:19:46,740 --> 00:19:52,920
episodes because the episodes
table is about 25 gigs. So I'm

331
00:19:52,920 --> 00:19:55,140
just gonna have to figure it
out. I'm not even sure if

332
00:19:55,140 --> 00:19:59,850
archive.org lets you do that to
the side. I think you can but I

333
00:19:59,850 --> 00:20:02,040
think Ain't they want you to go
a different route with that?

334
00:20:02,070 --> 00:20:05,340
Okay, I gotta look into that.
But I would like to because I

335
00:20:05,340 --> 00:20:09,540
think that's valuable
information. But you know, it

336
00:20:09,540 --> 00:20:14,010
takes Well, other than other
than that work. The other part

337
00:20:14,010 --> 00:20:16,140
of, of what I've been doing
really a lot this week is

338
00:20:16,140 --> 00:20:19,800
categories. And I think, you
know, we've got, I think we've

339
00:20:19,800 --> 00:20:22,020
got that pretty much nailed at
this point, anything

340
00:20:22,020 --> 00:20:24,510
different from what we discussed
on the last show, but the

341
00:20:24,510 --> 00:20:28,230
categories, which is, I guess,
in essence, one big flat list?

342
00:20:29,280 --> 00:20:32,430
Yeah, one big flat list, which
is basically a deconstructed

343
00:20:32,430 --> 00:20:36,990
version of the iTunes category
list. And you can there's an

344
00:20:37,020 --> 00:20:42,300
there's an API, did you see the
current list in that? Category

345
00:20:42,300 --> 00:20:46,020
slash list? Oh, it will just
give you every category with its

346
00:20:46,080 --> 00:20:47,400
with its category ID

347
00:20:47,430 --> 00:20:49,710
that was that nailed down? Does
that mean That's it no more

348
00:20:49,710 --> 00:20:52,590
categories? Is there ever going
to be an addition? Or how does

349
00:20:52,590 --> 00:20:53,070
that work?

350
00:20:53,070 --> 00:20:57,450
So I don't think it's, I don't
think it's, it's a once and for

351
00:20:57,450 --> 00:21:03,150
all thing with it can be added
to but since everybody puts only

352
00:21:03,210 --> 00:21:08,130
iTunes categories in their feed,
we're not the way the way that

353
00:21:08,370 --> 00:21:11,910
the system is picking up the
categories for each podcast, is

354
00:21:11,910 --> 00:21:17,160
it's pulling the existing iTunes
category tags out of the feed,

355
00:21:17,610 --> 00:21:21,600
and then breaking them apart and
finding where they're positioned

356
00:21:21,600 --> 00:21:24,090
in that flat list. So you're
never going to get anything much

357
00:21:24,090 --> 00:21:28,320
more than that, right? Anyway,
unless somebody manually adds

358
00:21:28,320 --> 00:21:31,710
it, or we pick up new namespaces
that may have other categories.

359
00:21:32,040 --> 00:21:36,480
Can you explain the namespaces
for people who love to listen

360
00:21:36,480 --> 00:21:39,180
along and aren't quite exactly
sure. Because, you know, you

361
00:21:39,180 --> 00:21:44,070
read stuff about well, this RSS,
and we can expand it with a

362
00:21:44,070 --> 00:21:45,060
namespace.

363
00:21:46,590 --> 00:21:50,970
Yeah, so namespaces come from
XML. And it's just a way to

364
00:21:50,970 --> 00:22:00,360
define which tags are valid
within that XML. Document. You

365
00:22:00,360 --> 00:22:04,410
so the namespace, it's a way to,
you know, if you want to change

366
00:22:04,410 --> 00:22:12,390
an XML document, the right way,
what you do is you define a DTD,

367
00:22:12,390 --> 00:22:18,240
which is a date, something
trend. Something to add on to

368
00:22:18,420 --> 00:22:21,060
that I forgot what the acronym
stands for. But it's basically

369
00:22:21,060 --> 00:22:25,710
just it says, here's the way we
expect this document to look.

370
00:22:26,190 --> 00:22:30,630
And then if you want to add, but
you can namespace it. And it's

371
00:22:30,630 --> 00:22:32,880
easier, because you don't have
to go through the whole process

372
00:22:32,880 --> 00:22:37,350
of defining the document
definition. So basically, then

373
00:22:37,350 --> 00:22:40,650
you just at the top of the of
the XML document, you add that

374
00:22:40,650 --> 00:22:42,330
namespace link, and

375
00:22:42,360 --> 00:22:45,750
then okay, so you're telling
you're telling the machine

376
00:22:45,750 --> 00:22:48,780
readable part, you're saying,
Okay, if you see this tag, this

377
00:22:48,780 --> 00:22:50,820
is it's valid, and here's why.

378
00:22:51,330 --> 00:22:56,220
Yeah, okay. Yeah. And those are
always appended with a colon. So

379
00:22:56,370 --> 00:23:02,250
iTunes, colon, whatever the
attribute name is, and whatever

380
00:23:02,250 --> 00:23:05,640
the element name is, and that's
part of the iTunes namespace and

381
00:23:05,640 --> 00:23:07,380
it just lays over the top as far
as,

382
00:23:07,710 --> 00:23:10,470
okay, okay, I see, we handle

383
00:23:10,470 --> 00:23:16,620
about, we handle probably six or
seven different spaces, freedom

384
00:23:16,650 --> 00:23:21,630
in the freedom controller? Yeah,
no, no, in, in podcast index, we

385
00:23:21,630 --> 00:23:24,360
only handle that in his
namespace and the Media

386
00:23:24,690 --> 00:23:29,880
namespace currently. But I would
like to, I'd like to handle

387
00:23:29,880 --> 00:23:33,030
others. But I don't want to go
down that rabbit hole until we

388
00:23:33,600 --> 00:23:37,230
get a good idea of right of
which ones we want. And whether

389
00:23:37,230 --> 00:23:40,980
it's valuable because they that
does take time. That's a various

390
00:23:40,980 --> 00:23:44,760
kind of tedious work is to is to
troubleshoot. Once you get your

391
00:23:44,760 --> 00:23:48,510
XML parser working well, then
you start throwing new things at

392
00:23:48,510 --> 00:23:50,400
it. It wants to barf all the
time.

393
00:23:50,850 --> 00:23:55,140
What you've come up with a lot
of new endpoints, I think

394
00:23:55,140 --> 00:23:58,980
they're called on the API, which
to me is like, that's the thing

395
00:23:58,980 --> 00:24:03,030
that works. Yeah. That's the
thing you talk to and it gives

396
00:24:03,030 --> 00:24:03,870
you something back.

397
00:24:04,140 --> 00:24:07,680
Yeah, yeah. This is the URL. So
the new endpoints just a new

398
00:24:07,680 --> 00:24:13,050
URL. And the ones that we have
currently, I guess, I don't

399
00:24:13,050 --> 00:24:15,480
remember if we talked about this
last year, it was the recent,

400
00:24:15,810 --> 00:24:18,930
right, we didn't talk slash new
feeds. Okay. Yeah, that's the

401
00:24:18,930 --> 00:24:24,060
outbound pipe, that's the fire
hose. And then the newest one

402
00:24:24,060 --> 00:24:27,390
was yes, it was categories, that
category slash list. And then

403
00:24:27,390 --> 00:24:31,950
there's also the one I posted
yesterday. I've been using this

404
00:24:31,950 --> 00:24:36,300
one as sort of the beta test for
the category work, and it's

405
00:24:36,510 --> 00:24:40,800
recent slash fees. So we've had
recent slash episodes where you

406
00:24:40,800 --> 00:24:43,350
can just get the newest
episodes, but this one is

407
00:24:43,350 --> 00:24:46,110
basically the same idea but with
fees. So these are just the

408
00:24:46,110 --> 00:24:48,330
newest fees that have updated in
a certain

409
00:24:48,360 --> 00:24:50,460
timespan updated or added
updated

410
00:24:51,510 --> 00:24:56,820
you the most recent phase that
have added a show pocket. So if

411
00:24:56,820 --> 00:25:02,160
they're still in the way did it
looks for that is by looking at

412
00:25:02,160 --> 00:25:08,010
the looking at the episodes
table to see which show which

413
00:25:08,040 --> 00:25:14,340
feeds have shows that have just
published. So that's if, if the

414
00:25:14,340 --> 00:25:17,880
feed itself declares that it has
updated, but it didn't actually

415
00:25:17,880 --> 00:25:19,110
post a new episode.

416
00:25:20,640 --> 00:25:24,570
I see okay. You all were down to
that level. That's pretty good.

417
00:25:24,600 --> 00:25:26,580
That's pretty. That's, that's
pretty fast.

418
00:25:26,580 --> 00:25:29,340
The only way to do it another
way to do it really, because

419
00:25:29,340 --> 00:25:36,810
fees are so untrustworthy. And
wrangling a world to cats damage

420
00:25:36,810 --> 00:25:44,280
you. That so in? Well, I've got
in honor of Brene Brown's new

421
00:25:44,280 --> 00:25:45,630
exclusive podcast. So

422
00:25:45,630 --> 00:25:48,870
yeah, she signed with that. She
also she spends time with

423
00:25:49,500 --> 00:25:54,090
Spotify. Right. I think Spotify?
Yeah, I think so. Is it Spotify?

424
00:25:54,150 --> 00:25:55,980
Yeah. Spotify. Yeah.

425
00:25:56,820 --> 00:26:03,000
The since you mentioned cats do
a clip for Brene. Brown. So

426
00:26:03,270 --> 00:26:08,460
you're not crazy. You're a
goddamn cheetah. We're using

427
00:26:08,460 --> 00:26:13,200
Brene. Brown now for developer
motivation. Yeah. That's the

428
00:26:13,200 --> 00:26:13,680
index.

429
00:26:14,700 --> 00:26:18,450
That's the you know, I mean,
it's a beautiful day, we've

430
00:26:18,450 --> 00:26:23,550
we've lost another podcaster to
Isalo. So we have to honor honor

431
00:26:23,550 --> 00:26:24,330
her memory.

432
00:26:25,830 --> 00:26:28,110
Oh, man. That's too funny.

433
00:26:28,500 --> 00:26:33,570
So the that but that if you got
time for this, I want to make I

434
00:26:33,570 --> 00:26:39,810
want to have a discussion and
get your opinion on exactly what

435
00:26:40,980 --> 00:26:49,320
constitutes a podcast this worth
keeping. Okay. So some of the

436
00:26:50,100 --> 00:26:55,050
discussion that happened this
week, I posted a had a reply.

437
00:26:55,680 --> 00:27:00,090
And a little bit of a back and
forth with Daniel J. Lewis, on

438
00:27:00,120 --> 00:27:03,570
the read on a Reddit thread. And
they were just talking about

439
00:27:04,470 --> 00:27:10,290
seems like a nice guy. They were
just talking about like numbers.

440
00:27:10,620 --> 00:27:13,290
Okay, he was mentioning that,
you know, when the podcast

441
00:27:13,290 --> 00:27:17,640
index, as it as it was about a
week or so ago, was about

442
00:27:17,670 --> 00:27:21,180
300,000 Short podcasts.

443
00:27:22,139 --> 00:27:25,709
And he was short of what short
of his his short of his

444
00:27:25,710 --> 00:27:29,520
numbers short of his question.
Yeah. So everything seems to be

445
00:27:29,520 --> 00:27:38,430
in that 1.3 to 1.5 million
range. And so and we were at

446
00:27:38,430 --> 00:27:42,840
like one point, just shy of 1.1.
And I knew that we have many

447
00:27:42,840 --> 00:27:46,290
people that had donated other
batches of feeds, as well, I'm

448
00:27:46,290 --> 00:27:50,490
not too worried about this. So
we started adding those feeds.

449
00:27:50,490 --> 00:27:53,400
And then, you know, just was
thinking, you know, as I'm

450
00:27:53,400 --> 00:27:57,870
adding them, what I'm seeing
show up is things like sermon

451
00:27:57,870 --> 00:28:02,880
audio keyword feeds, to where,
okay, so the in the first place

452
00:28:02,880 --> 00:28:07,320
that showed up was in the
recent, the recent episodes API.

453
00:28:07,950 --> 00:28:10,110
I'm looking at the recent
episodes API and watching what

454
00:28:10,110 --> 00:28:15,240
it returns. And it's returning
what looks like 10 copies of the

455
00:28:15,240 --> 00:28:20,040
same episode. I'm like, this is
weird. So I'll start looking and

456
00:28:20,040 --> 00:28:23,550
they're all different feed IDs.
Will they was there 10 episodes

457
00:28:23,550 --> 00:28:26,610
coming from 1010 different
feeds? Do we have Do we have a

458
00:28:26,610 --> 00:28:28,560
duplicate problem? Well,

459
00:28:29,070 --> 00:28:32,790
let me guess. Someone
misunderstood how it works and

460
00:28:32,790 --> 00:28:35,580
thought they had to do a new RSS
feed for every episode.

461
00:28:36,420 --> 00:28:38,790
No. Okay. So sermon audio,

462
00:28:39,120 --> 00:28:42,480
yet, which I see a lot of we've
all seen sermon audio pop up.

463
00:28:42,840 --> 00:28:46,860
Okay. See, I want to have a
discussion about whether to even

464
00:28:46,860 --> 00:28:49,830
purge sermon audio from the
entire like, I'm not, you know,

465
00:28:49,860 --> 00:28:54,330
I'm a Christian guy. But I got
my limits. Okay. So

466
00:28:54,330 --> 00:28:56,250
what's what do you think they're
doing? What's going on with

467
00:28:56,250 --> 00:28:57,630
these? Well, I know what they're
doing. So

468
00:28:57,630 --> 00:29:06,630
they they have they have keyword
feeds, where so they'll have one

469
00:29:06,630 --> 00:29:11,610
like, for instance, they'll have
one on faith. And so the key

470
00:29:11,610 --> 00:29:12,330
word is faith.

471
00:29:12,360 --> 00:29:16,530
I already know what's going on.
They're trying to spam the

472
00:29:16,530 --> 00:29:20,820
index. Well, they're they're
spamming. That's why I mean that

473
00:29:20,820 --> 00:29:23,010
to show up in search, it's
exactly

474
00:29:23,010 --> 00:29:26,820
what they're doing. And every
one of the there's I looked at

475
00:29:26,820 --> 00:29:31,530
it and there was 800, sermon
audio feeds that were just pure

476
00:29:31,530 --> 00:29:32,550
keyword feeds.

477
00:29:32,730 --> 00:29:35,280
Now, when you say just pure
keyword, that means

478
00:29:35,850 --> 00:29:40,770
that means across all of their
shows on their platform. If you

479
00:29:40,770 --> 00:29:45,780
search for the term, let's just
say faith, yeah, and it returns

480
00:29:46,740 --> 00:29:51,060
all the all the feed all the
episodes that have that in the

481
00:29:51,060 --> 00:29:53,910
title or that in the
description, right, but it

482
00:29:53,910 --> 00:29:58,260
returns it as an RSS feed. So
then they add that

483
00:29:59,250 --> 00:30:00,630
oh my good This.

484
00:30:01,020 --> 00:30:04,200
So you have the original show
that posted and then you have

485
00:30:04,230 --> 00:30:08,550
every other keyword that hits
actually ends up being a hit on

486
00:30:08,550 --> 00:30:13,710
that. And they all post the same
show at the same moment. And so

487
00:30:13,710 --> 00:30:19,170
you end up with mass duplication
of episodes across across all

488
00:30:19,170 --> 00:30:24,660
these and every one of them as a
as a valid, unique iTunes ID. So

489
00:30:24,660 --> 00:30:29,220
that they're all in iTunes as
separate podcasts. Hmm. But

490
00:30:29,220 --> 00:30:30,690
they're not. Yeah.

491
00:30:32,280 --> 00:30:35,430
And basically everything is a
duplicate except for the keyword

492
00:30:35,430 --> 00:30:36,840
in each individual feed.

493
00:30:37,710 --> 00:30:44,580
Yeah, yeah. So if, if I don't
know who's a big preacher these

494
00:30:44,580 --> 00:30:49,980
days, but you know, is it just
say that Rick Warren posts, you

495
00:30:49,980 --> 00:30:53,340
know, some something on you
know, and it's got 10 different

496
00:30:53,340 --> 00:30:57,120
keywords, we could possibly show
up in 10 Different sermon audio

497
00:30:57,150 --> 00:31:00,870
podcasts at the same that one
episode at the same time. Right.

498
00:31:00,900 --> 00:31:05,100
Right. Which, which just sucks
when you like, I don't want I

499
00:31:05,100 --> 00:31:07,440
don't want that in there. But I
don't know how you feel about

500
00:31:07,440 --> 00:31:08,190
stuff like that?

501
00:31:08,489 --> 00:31:12,299
Well, first, I think we should
pray for them no matter what.

502
00:31:13,259 --> 00:31:18,779
Yeah. And I am not really
mocking that. Not really, no,

503
00:31:18,779 --> 00:31:21,989
I'm a little older nowadays. And
like, I pray for you, I pray for

504
00:31:21,989 --> 00:31:26,729
everybody. So let's look at what
they're trying to achieve. What

505
00:31:26,729 --> 00:31:32,729
they're trying to achieve is, is
exposure through searches. And

506
00:31:32,729 --> 00:31:36,389
they have obviously a very wide
range. I mean, I don't really

507
00:31:36,389 --> 00:31:39,299
know how many categories they
could be, they've got to be

508
00:31:39,299 --> 00:31:42,149
duping categories to if they're
doing this across, how many did

509
00:31:42,149 --> 00:31:44,279
you say how many different
feeds? Are they creating?

510
00:31:44,669 --> 00:31:49,199
800? There's eight in as of two
days ago, in the pot in our

511
00:31:49,199 --> 00:31:53,249
index, there's 800 unique iTunes
IDs that are that are sermon,

512
00:31:53,249 --> 00:31:54,299
audio, keyword fate.

513
00:31:55,740 --> 00:32:04,290
And of the 800 Is it like, is it
so it's 800 feeds, but but they

514
00:32:04,290 --> 00:32:08,130
don't all have 800 different
keywords is all different

515
00:32:08,130 --> 00:32:10,860
combinations of keywords, we
find different combinations,

516
00:32:12,270 --> 00:32:15,240
though the duplications of the
combos, just different order,

517
00:32:15,900 --> 00:32:19,710
as well. And yet, they're all
different keyword combinations.

518
00:32:20,130 --> 00:32:25,110
And I think the individual shows
span the key words so that they

519
00:32:25,110 --> 00:32:30,450
show up in all the fields, or
the individuals, sermons or

520
00:32:30,450 --> 00:32:31,710
whatever you want to call it
those things?

521
00:32:32,220 --> 00:32:35,040
Well, let's just the way I read,
let's start with the result,

522
00:32:35,220 --> 00:32:38,040
what would be the correct way
for them to get the same

523
00:32:38,040 --> 00:32:47,100
results? I don't think I follow.
So if the result they're looking

524
00:32:47,100 --> 00:32:50,790
for is that they show up in
searches. That's why that was

525
00:32:50,790 --> 00:32:55,500
done. Right. Right. Right. So
what can they do differently

526
00:32:56,100 --> 00:32:59,070
that will achieve the same
result for them that when they

527
00:32:59,400 --> 00:33:03,060
when someone types in certain
combo of key words that they at

528
00:33:03,060 --> 00:33:09,480
least show up? Nothing, it just
works is

529
00:33:10,830 --> 00:33:13,440
my what I want to say is they
could just not be a douche and

530
00:33:13,440 --> 00:33:15,810
don't do well. But here's what

531
00:33:15,810 --> 00:33:19,200
I'm feeling. I'm feeling that
this is possibly a consultant.

532
00:33:20,820 --> 00:33:24,120
You know, consultant came in and
said, Hey, like it's like SEO,

533
00:33:24,120 --> 00:33:27,660
you know, this feels very SEO
consultant like to me, like

534
00:33:27,689 --> 00:33:31,259
I get sermonaudio maybe
sermonaudio told them to do it

535
00:33:31,259 --> 00:33:31,949
themselves.

536
00:33:33,120 --> 00:33:36,270
But maybe sermonaudio doesn't
doesn't know what the what they

537
00:33:36,270 --> 00:33:36,930
agreed to

538
00:33:38,250 --> 00:33:39,150
house right now.

539
00:33:39,750 --> 00:33:43,110
But beyond that, what is the
solution?

540
00:33:45,330 --> 00:33:47,850
Yeah, that's what and that's
what I don't know. And that's

541
00:33:47,850 --> 00:33:52,860
what, okay, so it's a broader
topic, because there's not just,

542
00:33:53,730 --> 00:33:58,350
here's the way I think about
this, and tell me what you think

543
00:33:58,380 --> 00:34:05,340
is when if you walk up and say,
podcast to anybody, what's your

544
00:34:05,340 --> 00:34:10,440
favorite podcast? What podcasts?
Are you thinking about these

545
00:34:10,440 --> 00:34:14,010
days, blah, blah, blah. If you
say that to anybody, there's one

546
00:34:14,400 --> 00:34:19,230
thing that comes to mind. And
it's, it's an independently

547
00:34:19,230 --> 00:34:27,240
produced show that has, that
anybody can listen to from

548
00:34:27,240 --> 00:34:36,690
multiple places. And so and it's
typically free. So if you think

549
00:34:36,690 --> 00:34:39,420
about it like that, there are
lots of things that are in

550
00:34:39,450 --> 00:34:44,670
iTunes and in podcast indexed by
default, that don't fit what

551
00:34:44,700 --> 00:34:48,750
anybody considers to be an
actual podcast, thinking

552
00:34:49,050 --> 00:34:54,060
sermons. Okay, yes, it's in a
feed blah, blah, blah. Yeah, but

553
00:34:54,210 --> 00:34:58,140
isn't it it's, it's not what
anybody thinks of as a podcast.

554
00:34:58,590 --> 00:35:02,340
That another one is you
drivetime radio, a lot of those

555
00:35:02,370 --> 00:35:05,790
shows are putting their stuff
into a podcast feed after the

556
00:35:05,790 --> 00:35:10,080
fact like morning radio, sports
radio, they're doing you know,

557
00:35:10,080 --> 00:35:17,520
all those kinds of things are
being put in there. They the AP

558
00:35:17,520 --> 00:35:21,960
report, things like that. And so
there becomes, I don't know how

559
00:35:21,960 --> 00:35:28,770
you define like, My instinct is
to say, I don't want a bunch of

560
00:35:28,770 --> 00:35:34,260
crap in there this like okay,
I'll give you I'll give you a an

561
00:35:34,260 --> 00:35:38,070
example. There was one that
popped up in the carousel the

562
00:35:38,070 --> 00:35:41,880
other day a podcast from East
Side Church of Christ in

563
00:35:41,880 --> 00:35:45,450
Singapore. Now, now isa Church
of Christ and Singapore. Now

564
00:35:45,450 --> 00:35:53,190
their parishioners may may want
that. But there is it is rare.

565
00:35:53,370 --> 00:35:59,820
If If not, is rare. If a if a
churchgoer listens to a sermon

566
00:35:59,820 --> 00:36:04,200
from a note from some other
local church, that rarely if

567
00:36:04,200 --> 00:36:09,690
ever happens. And you so it's
valuable to the people who want

568
00:36:09,690 --> 00:36:19,080
it. But is it valid? Is is
having 75,000 local church

569
00:36:19,080 --> 00:36:25,950
sermons available as podcasts in
a podcast index? Is that

570
00:36:26,520 --> 00:36:31,500
valuable to a large number of
people? And I'm not I don't know

571
00:36:31,500 --> 00:36:34,020
the answer to this, I'm just
kind of broaching the topic.

572
00:36:34,230 --> 00:36:34,740
Yes.

573
00:36:37,470 --> 00:36:44,070
I'll take that one. I believe
anything that is an RSS feed.

574
00:36:44,910 --> 00:36:49,590
And I really don't, I would like
it to be media only as well as

575
00:36:49,590 --> 00:36:54,150
in audio, video, and not to PDF
or anything like that. But you

576
00:36:54,150 --> 00:36:59,820
know, attachment, a, what we
call a media attachment to be

577
00:36:59,820 --> 00:37:08,430
valid. And I completely
understand that you do not want

578
00:37:08,460 --> 00:37:13,890
a podcast app experience. That
gives you what you don't want.

579
00:37:14,220 --> 00:37:17,880
So if you're searching for
something, and for whatever

580
00:37:17,880 --> 00:37:22,140
reason, in your results, show up
sermons that you don't care

581
00:37:22,140 --> 00:37:26,820
about lectures from professors
that you don't care about cat

582
00:37:26,820 --> 00:37:30,810
videos, that whatever it is you
don't care about, then that is a

583
00:37:30,810 --> 00:37:36,030
function of a bad search, in my
mind, not a bad index, I would

584
00:37:37,080 --> 00:37:42,270
personally never want to say any
group is too small for their

585
00:37:42,270 --> 00:37:46,830
content to be in the index. One
person who makes it one person

586
00:37:46,830 --> 00:37:49,560
who listens is good enough for
me. In fact, one person who

587
00:37:49,560 --> 00:37:53,190
makes it know people who listen
is good for me. And if you look

588
00:37:53,190 --> 00:37:57,510
at the mission of podcasts,
index.org. And I think we're

589
00:37:57,510 --> 00:38:00,510
already, we're already kind of
down this path. And it comes

590
00:38:00,510 --> 00:38:02,970
back to what I was saying
before, and I don't think you

591
00:38:02,970 --> 00:38:06,270
quite are on the same frequency
as me that it's not bad, by the

592
00:38:06,270 --> 00:38:12,690
way, about about a podcast app
that does something specific. So

593
00:38:12,690 --> 00:38:18,330
I would love in my vision.
wishes may not be shared. But I

594
00:38:18,330 --> 00:38:27,000
believe the ability for a church
or a group or a religious group,

595
00:38:27,570 --> 00:38:33,690
to have their own podcast app
that filters from the index in a

596
00:38:33,690 --> 00:38:37,440
way that they get results that
they want and is relevant to

597
00:38:37,440 --> 00:38:43,920
their listeners. I want that I
that is exactly what I want. And

598
00:38:43,950 --> 00:38:48,030
And as we're sitting here going,
oh, man, not another sermon

599
00:38:48,030 --> 00:38:52,470
audio. There's someone over
somewhere else going, man, not

600
00:38:52,470 --> 00:38:58,170
another NYT not another PBS not
another NPR thing, you know. So

601
00:38:58,410 --> 00:39:02,250
that's very, very subjective.
And that's that's what I keep

602
00:39:02,250 --> 00:39:06,390
coming back to is we don't nest
a my mind. We don't necessarily

603
00:39:06,390 --> 00:39:10,560
have to have, every podcast app
has to have every podcast

604
00:39:10,560 --> 00:39:14,820
displayed. The index should give
everybody the capability to

605
00:39:14,820 --> 00:39:18,480
slice and dice whatever the hell
they want. It's not about

606
00:39:18,480 --> 00:39:23,910
promotion. It's not about reach.
I do not confuse search with

607
00:39:25,470 --> 00:39:30,990
exposure or promotion. Although
completely valid. Our job is to

608
00:39:30,990 --> 00:39:36,600
have it all so people can get it
out. And I know I predict that

609
00:39:36,600 --> 00:39:40,800
now that we've made it so easy
to create a podcast listening

610
00:39:40,800 --> 00:39:45,750
experience that will if I cared
and if I could, I would make the

611
00:39:45,750 --> 00:39:48,660
Catholic podcast app, the
Christian podcast app, the

612
00:39:48,660 --> 00:39:53,340
Jewish podcast app, and curated
but curated with the help with

613
00:39:53,340 --> 00:39:57,870
the help of the index. So the
index can give me what I want.

614
00:39:58,410 --> 00:39:58,770
So you're

615
00:39:58,770 --> 00:40:03,540
saying that And I think I'm
Javon with you. You're saying,

616
00:40:04,020 --> 00:40:09,780
if you have for me, if I'm going
to be curating, let's just say

617
00:40:09,780 --> 00:40:12,450
I'm doing get recent episodes,
and I'm, and I'm filtering, and

618
00:40:12,450 --> 00:40:16,800
I put in to filter out category
65, which is religion,

619
00:40:16,800 --> 00:40:20,460
spirituality. Yeah, if I put
that on there, you're saying

620
00:40:20,460 --> 00:40:22,860
there's also going to be
somebody somewhere else who's

621
00:40:22,860 --> 00:40:25,380
going to do the same search? And
they're going to filter and say,

622
00:40:25,380 --> 00:40:26,820
show me only categories?

623
00:40:26,880 --> 00:40:31,950
Yes, I would hope so. I really
hope so. Now, I really, really

624
00:40:31,950 --> 00:40:32,430
hope so.

625
00:40:32,670 --> 00:40:36,930
I think I jive with you. What
about, what about the keyword

626
00:40:36,930 --> 00:40:42,240
spammy stuff, though? That's,
that's the same podcast being

627
00:40:42,240 --> 00:40:45,840
delivered in 800 different
feeds? And I don't like that.

628
00:40:45,870 --> 00:40:46,290
No, no,

629
00:40:46,290 --> 00:40:53,820
I understand. And I also think
that I mean, in a funny way. You

630
00:40:53,820 --> 00:40:57,480
know, giving them exactly what
they asking for is almost kind

631
00:40:57,480 --> 00:41:00,990
of perfect medicine. Like, if
you're asking for this, and this

632
00:41:00,990 --> 00:41:03,780
is what you're doing. You should
get your 800 results back in

633
00:41:03,780 --> 00:41:06,450
your favor. Yeah. But yeah, so

634
00:41:09,060 --> 00:41:11,430
I don't want that Diego. No, no,
no, no, just podcasts

635
00:41:12,060 --> 00:41:16,890
are really important. I think
that the easiest way is to reach

636
00:41:16,890 --> 00:41:19,920
out and say, Hey, why are you
guys doing this? How can we help

637
00:41:19,920 --> 00:41:22,860
you? Now we can't do this for
every person who comes up with

638
00:41:22,860 --> 00:41:29,160
some search scam ID in the first
place. But I think we can

639
00:41:29,160 --> 00:41:31,650
probably say, hey, you know, why
are you doing this help us

640
00:41:31,650 --> 00:41:36,210
understand, so we can make it
better for you. Because what

641
00:41:36,210 --> 00:41:41,970
they want to achieve, if anyone
thinks that because you have 800

642
00:41:41,970 --> 00:41:46,710
different keyword feeds feeds,
in the in the index at Apple or

643
00:41:46,710 --> 00:41:49,650
in podcasts, index.org or
anywhere, that you're going to

644
00:41:49,650 --> 00:41:53,100
save souls and convert people to
Christ, you got another thing

645
00:41:53,100 --> 00:41:56,670
coming. So that's just not
that's not helpful. If you

646
00:41:56,670 --> 00:41:59,940
however, I just don't think so.
You know, I mean, I've been

647
00:41:59,940 --> 00:42:01,950
trying to convince people to
stuff for a long time, it

648
00:42:01,950 --> 00:42:06,330
doesn't work very well, that
way. But if you say, Hey, here's

649
00:42:06,360 --> 00:42:10,350
a website, here's an app you can
get from the App Store. Here's a

650
00:42:10,350 --> 00:42:13,590
web app that you can use on your
phone, just like an app, and it

651
00:42:13,590 --> 00:42:17,490
has our sermons and other
sermons, and we're curating it,

652
00:42:17,760 --> 00:42:22,590
without having to do all the
bullcrap of curating. All you

653
00:42:22,590 --> 00:42:26,250
have to do is look, you know, do
your your endpoints on the API,

654
00:42:26,520 --> 00:42:28,890
put an exception if you don't
like something that's coming

655
00:42:28,890 --> 00:42:36,060
through, and Bob's your uncle.
That's really interesting,

656
00:42:36,060 --> 00:42:38,610
because I have the same
conversation with Tina, when my

657
00:42:38,610 --> 00:42:42,750
wife say, Well, if everyone's
doing the same thing, then you

658
00:42:42,750 --> 00:42:45,510
know, so what's the
differentiator to well, there's

659
00:42:45,510 --> 00:42:49,800
always UI and concepts, but I
think pretty much everybody

660
00:42:50,160 --> 00:42:53,880
comes down to some basic
concepts. It's like an inbox.

661
00:42:53,880 --> 00:42:57,810
You know, it's, it's what RSS
kind of the default is, there's

662
00:42:57,810 --> 00:43:00,510
not a lot of out of the box
thinking, and maybe there's not

663
00:43:00,510 --> 00:43:05,910
out of the box designed to be
made with that. But features, I

664
00:43:05,910 --> 00:43:09,360
still use overcast for the Share
feature which shares a link or

665
00:43:09,360 --> 00:43:13,740
you can create a clip, I think
that's incredibly helpful. So

666
00:43:13,770 --> 00:43:18,570
it's different feeding a wire
people loyal to podcast attic,

667
00:43:18,570 --> 00:43:21,690
you know, that for whatever
features it could be, it could

668
00:43:21,690 --> 00:43:24,690
be just the dark mode for you
know, it's really weird things

669
00:43:24,690 --> 00:43:27,750
that people get attracted to
have learned over time. But

670
00:43:28,290 --> 00:43:32,220
getting the proper results and
having the things displayed that

671
00:43:32,220 --> 00:43:36,900
you want displayed, I think is
number one. And yes, we all want

672
00:43:36,900 --> 00:43:42,090
some serendipity. I can just see
I want 10s of 1000s of apps and

673
00:43:42,090 --> 00:43:44,700
people being able to create
their experiences for their own.

674
00:43:44,880 --> 00:43:51,090
Why wouldn't we have a Antifa
app? Why wouldn't we have a

675
00:43:51,090 --> 00:43:55,080
proud boys app? I don't care. I
think that's that's what it

676
00:43:55,080 --> 00:43:58,320
should be. And then build, build
your and build community

677
00:43:58,320 --> 00:44:01,980
features into it. If we don't,
if we're all going to sit here

678
00:44:01,980 --> 00:44:05,880
and build radios, then there's
going to be one radio guy left

679
00:44:05,880 --> 00:44:07,980
at the end and he'll be some
kind of winner and there'll be a

680
00:44:07,980 --> 00:44:11,700
couple of also RANS. It makes no
sense to compete with each other

681
00:44:11,700 --> 00:44:15,210
on building the exact same
thing. So for instance, I get

682
00:44:15,210 --> 00:44:18,600
the randomizer. You know, the
what is it called? It's not

683
00:44:18,600 --> 00:44:22,770
called the randomizer. It's
called the cast coverage cast in

684
00:44:22,770 --> 00:44:28,260
Rofi. And its design is much yet
there. But it's really simple.

685
00:44:28,260 --> 00:44:32,100
It's like, you want to just like
find a random guess what? Yes,

686
00:44:32,160 --> 00:44:33,780
everyone does. You want to find

687
00:44:34,410 --> 00:44:37,560
this was starting in the middle
of starting at random locations

688
00:44:37,560 --> 00:44:43,200
in the podcast. That was great.
I did, I was like, Oh, that's

689
00:44:43,200 --> 00:44:44,730
weird, man. But he's actually
kind

690
00:44:44,730 --> 00:44:46,890
of cool. It's like a needle
drop. This is a needle drop

691
00:44:46,890 --> 00:44:49,860
right in the middle of a
podcast. So that to me is like

692
00:44:49,860 --> 00:44:54,960
wow. And maybe he pairs that
down and says or select this

693
00:44:54,960 --> 00:44:59,460
flag and only get random German
podcasts. So now we're cooking

694
00:45:00,000 --> 00:45:04,320
Now we're thinking that we're
all and this is so normal. It's

695
00:45:04,320 --> 00:45:07,860
just to me, I've studied media,
and I don't think coding is much

696
00:45:07,860 --> 00:45:10,680
different, really than any other
kind of media, we all get stuck

697
00:45:10,680 --> 00:45:13,380
in these patterns, you know, and
it's like, okay, it should be

698
00:45:13,380 --> 00:45:16,170
this. And this is how it should
work. And this is how a player

699
00:45:16,170 --> 00:45:21,420
works. And this is no, of
course, there's the, the Silicon

700
00:45:21,420 --> 00:45:25,860
Valley's good at doing the, you
know, the exact weirdness of

701
00:45:25,860 --> 00:45:29,010
that and creating some kind of
swiping thing you got to do and

702
00:45:29,010 --> 00:45:31,770
it's, you know, that stuff
either catches or not, but just

703
00:45:31,800 --> 00:45:38,070
in general, to have a, I call
them listening experiences or

704
00:45:38,070 --> 00:45:42,270
viewing experiences. You know,
there's no reason why you

705
00:45:42,270 --> 00:45:47,730
couldn't create some so Apple,
here's an example. Apple, I

706
00:45:47,730 --> 00:45:53,520
guess they bought some company
that that is that makes radio

707
00:45:53,520 --> 00:45:55,830
stations out of podcast feeds.

708
00:45:56,400 --> 00:45:57,750
Yeah. What do you think about
that? That's

709
00:45:58,620 --> 00:46:03,480
because I've done all this. I
did this. 14 years ago, I've

710
00:46:03,510 --> 00:46:06,540
been through this loop. Now I
did it with less bandwidth, less

711
00:46:06,570 --> 00:46:10,320
coders, less understanding, just
less of everything,

712
00:46:10,530 --> 00:46:13,620
unfortunately, with a shitload
of money, which is a very bad

713
00:46:13,620 --> 00:46:17,610
combination. Just the money.
Yeah, the money got spent, but I

714
00:46:17,610 --> 00:46:20,160
don't think we ever got close to
what we wanted to see. Burn it.

715
00:46:21,150 --> 00:46:23,850
What's your burn rates on God?
I'm glad we're not doing that

716
00:46:23,850 --> 00:46:29,880
anymore. Oh, I was gonna say,
because now you got me on.

717
00:46:29,910 --> 00:46:33,840
I gotta go. Sorry. The radio,
the record. Okay.

718
00:46:33,840 --> 00:46:38,610
But yeah, so the idea. And I was
doing it with OPML feeds, which

719
00:46:38,610 --> 00:46:41,430
is kind of interesting, since
that popped up on the no agenda,

720
00:46:41,460 --> 00:46:44,130
or podcast, index dot social.

721
00:46:44,940 --> 00:46:48,630
Christopher, I seen, I think
that's cool stuff. But

722
00:46:48,630 --> 00:46:51,540
yeah, so the idea of an OPML
feed. In this case, if you have

723
00:46:51,540 --> 00:46:57,030
an OPML feed that has RSS nodes
in it, then you could arrange.

724
00:46:57,420 --> 00:47:00,870
And I did many different
versions of this at pod show.

725
00:47:01,290 --> 00:47:03,810
You could say, Okay, I want
this, this this and, and I

726
00:47:03,810 --> 00:47:07,320
actually helped create little
buckets for people said, Okay,

727
00:47:07,350 --> 00:47:13,140
so your daily commute? Cars
coming back to me, here's how we

728
00:47:13,140 --> 00:47:16,920
did it. Your daily commute is
how long? One hour? Okay, what

729
00:47:16,920 --> 00:47:19,410
do you like to hear, I like to
hear a little bit of news,

730
00:47:19,560 --> 00:47:23,700
little to show business and a
little bit of, oh, I want a

731
00:47:23,700 --> 00:47:28,350
little bit, I want a latest
church sermon. And now that's

732
00:47:28,350 --> 00:47:34,350
and then I want to know, at
least start on a new episode of

733
00:47:34,350 --> 00:47:38,370
Joe Rogan. Because I know that's
a three hour show. And you would

734
00:47:38,370 --> 00:47:42,060
arrange those in that order,
which I call a format. This is

735
00:47:42,060 --> 00:47:48,420
where it looks just like radio.
So the top would be, and I'm

736
00:47:48,420 --> 00:47:51,690
just this is just single
choices. So single choice is AP

737
00:47:51,690 --> 00:47:56,130
news feed. Now with commercials.
The second one would be like the

738
00:47:56,130 --> 00:48:00,000
daily tech news show or some
shorter version of that. And so

739
00:48:00,000 --> 00:48:05,940
what happens is, that renders
and it creates a single feed,

740
00:48:06,930 --> 00:48:12,390
synthetic face, yeah, of feed it
in order. And that's the key in

741
00:48:12,390 --> 00:48:17,640
order that you placed it so you
get the aid the latest AP first,

742
00:48:17,670 --> 00:48:21,960
then you get the latest tech
news podcast, and it kind of

743
00:48:21,960 --> 00:48:25,680
flows one into the next, if you
have that. Now, I think today's

744
00:48:25,680 --> 00:48:29,070
podcast apps don't really allow
for that anymore. But there's

745
00:48:29,100 --> 00:48:32,100
there's nothing to say that you
couldn't then just convert that

746
00:48:32,100 --> 00:48:35,460
into a stream of bits, you know,
it's all, it's all the same, but

747
00:48:35,460 --> 00:48:39,960
you give the you give the
listener control over the type

748
00:48:39,960 --> 00:48:42,690
of stuff they'd like to hear
that type of sources it would

749
00:48:42,690 --> 00:48:46,260
come from, and the order in
which they want to hear it. And

750
00:48:46,260 --> 00:48:50,700
then from then on, you basically
flip the switch, let it run, and

751
00:48:50,700 --> 00:48:55,530
you see what happens. And it
should, in theory, create an

752
00:48:55,530 --> 00:48:59,430
hour long commute podcast that
exactly the type of content from

753
00:48:59,430 --> 00:49:03,540
the type of shows you want. Now,
there's a lot of shit that goes

754
00:49:03,540 --> 00:49:07,320
along with that. And what we
didn't have at the time, is any

755
00:49:07,320 --> 00:49:11,700
kind of real deep knowledge of
algorithms, machine learning,

756
00:49:11,880 --> 00:49:15,720
this is the kind of stuff that I
think can can play beautifully

757
00:49:15,720 --> 00:49:20,670
alongside of the index is
figuring out what people want,

758
00:49:21,030 --> 00:49:25,440
and then putting it into maybe
even new feeds just for them.

759
00:49:25,440 --> 00:49:28,380
Not necessarily that that feed
goes into the index. You know

760
00:49:28,380 --> 00:49:28,950
what I'm saying?

761
00:49:29,070 --> 00:49:31,890
Yeah, what's cool about what
you're saying, I think is that

762
00:49:32,730 --> 00:49:38,850
there's a lot of time spent
around around figuring out what

763
00:49:39,030 --> 00:49:44,490
content people want, and not the
way they want it. And so like

764
00:49:44,490 --> 00:49:49,320
the for the the content itself.
You can slice and dice that a

765
00:49:49,320 --> 00:49:52,560
million ways you can cat you can
do categories, you can do you

766
00:49:52,560 --> 00:49:58,170
know, AI, you know, figuring it
out based on transcript. You can

767
00:49:58,170 --> 00:50:00,480
slice and dice that a million
different ways. I think Spotify

768
00:50:00,480 --> 00:50:02,910
is doing something where they're
trying to, you know, they're

769
00:50:02,910 --> 00:50:06,060
opening up parts of their
database for machine learning

770
00:50:06,060 --> 00:50:10,020
people don't remember it did.
Yeah. Somebody posted that in

771
00:50:10,020 --> 00:50:15,120
the social guests. Yeah, and
social. And, but, but there's

772
00:50:15,120 --> 00:50:18,570
really no time being spent
trying to figure out how you

773
00:50:18,570 --> 00:50:19,620
want it delivered

774
00:50:19,680 --> 00:50:22,920
and how you want it. Yeah. And
how you want it to displayed?

775
00:50:23,490 --> 00:50:27,450
Yeah, that's what you're saying
is like, it's like, I know, I

776
00:50:27,450 --> 00:50:31,830
kind of know already what I
want. But I don't really know

777
00:50:31,830 --> 00:50:35,370
how maybe I don't even know how
I want it delivered. And if you

778
00:50:35,370 --> 00:50:39,630
have, if you have 50 different
apps that are all doing

779
00:50:39,810 --> 00:50:44,100
experimentation, with different
with different delivery formats,

780
00:50:44,130 --> 00:50:48,120
like, like the needle drop, you
know, cast coverage. I never

781
00:50:48,120 --> 00:50:50,370
knew that that was a thing that
I was interested in. But now I

782
00:50:50,370 --> 00:50:54,060
do. I think it's cool. I think
then I'll go ahead and hit it. I

783
00:50:54,060 --> 00:50:58,860
hit it about once a day. Just to
see, it's like, you know, drop

784
00:50:58,860 --> 00:51:00,690
the book open to see what page
you land. I

785
00:51:00,690 --> 00:51:03,840
think that that should be a
little quote on the page. Dave

786
00:51:03,840 --> 00:51:08,790
Jones, I hit it at least once a
day. That's a quote right there.

787
00:51:09,240 --> 00:51:12,840
And he also in and by the way,
he hates sermons.

788
00:51:14,160 --> 00:51:21,630
So well, that's yeah. So I think
the fallacy is that there's it

789
00:51:21,630 --> 00:51:24,870
really started with the with
with the Apple index, and

790
00:51:24,870 --> 00:51:29,010
Spotify, it's very blatant.
People believe that by being

791
00:51:29,010 --> 00:51:34,440
searchable, you're going to gain
audience, I am here to tell you

792
00:51:34,440 --> 00:51:41,190
after 16 years, bull crap, the
amount of times that someone

793
00:51:41,190 --> 00:51:45,690
will actually use the search and
randomly find you and think

794
00:51:45,690 --> 00:51:49,830
holy, this is the podcast for
me, I'd say is 0.1.

795
00:51:51,060 --> 00:51:53,610
Typically, that's why I didn't
care that much about categories

796
00:51:53,610 --> 00:51:56,400
at the beginning, because I'm
like, nobody, nobody clicks on

797
00:51:56,610 --> 00:51:59,610
tech, and just randomly chooses
a podcast. I don't

798
00:51:59,640 --> 00:52:03,840
Well, I think it's more than
just searched like, what am I

799
00:52:03,840 --> 00:52:06,330
going to find today? That's why
I like cast coverage of the

800
00:52:06,330 --> 00:52:10,890
randomizers. Like, okay, and
even every day, I always hit the

801
00:52:10,890 --> 00:52:14,460
carousel at podcast index.org.
And I, and I listen to these

802
00:52:14,460 --> 00:52:17,190
funky podcasts, you know, and
see if there's anything there.

803
00:52:17,520 --> 00:52:19,740
And there's something to be said
for that experience. You know,

804
00:52:19,740 --> 00:52:23,880
it's not right yet, but who
knows what, what would drink

805
00:52:23,880 --> 00:52:27,690
Plato will come up with. But
this is this is exactly that. So

806
00:52:28,080 --> 00:52:33,600
what here's what is missing on
our player? Our carousel is the

807
00:52:33,630 --> 00:52:40,980
immediate way to subscribe to
that. So I just found a podcast.

808
00:52:41,010 --> 00:52:44,340
Oh, this is pretty funny. Yeah,
I want to subscribe to that. I

809
00:52:44,340 --> 00:52:47,400
can't do that right now. There's
no link. Right? So that's,

810
00:52:47,430 --> 00:52:50,640
that's what I was telling
roofie. For, for the randomizer

811
00:52:50,880 --> 00:52:54,270
to the number one feature people
are asking for is I want to be

812
00:52:54,270 --> 00:52:59,460
able to download that mp3 and or
subscribe to it when I see it. I

813
00:52:59,460 --> 00:53:02,280
don't don't make me go and
search for it somewhere, which

814
00:53:02,280 --> 00:53:05,640
is what's happening. So how do
people find podcasts? Number one

815
00:53:05,640 --> 00:53:08,640
place? Number one, it's going to
surprise you Google.

816
00:53:10,110 --> 00:53:12,300
Okay, because I was going to ask
you about that. I've got them.

817
00:53:12,840 --> 00:53:17,550
Head. Literally, oh, my notes
here. How do you how do we find

818
00:53:17,550 --> 00:53:22,830
podcasts? I always search. Like
I don't typically go hunting for

819
00:53:22,830 --> 00:53:23,550
podcasts.

820
00:53:23,610 --> 00:53:27,510
You hear from somebody else? You
hear podcasts. And then you go

821
00:53:27,510 --> 00:53:30,930
into your podcast app, search it
subscribe done. That's the

822
00:53:30,930 --> 00:53:37,410
typical use. Yeah, we have
failed at coming up with any

823
00:53:37,410 --> 00:53:42,570
other ideas. And so it's not
just, oh, I'm looking for a tech

824
00:53:42,570 --> 00:53:49,470
podcast. It's more like the
randomizer. Where I just hit

825
00:53:49,470 --> 00:53:54,630
that. And oh, it's also how can
someone else? How can we create

826
00:53:54,660 --> 00:54:00,420
a widget that I that I can put
on my WordPress blog of my

827
00:54:00,420 --> 00:54:04,470
podcast, my favorite Podcast,
the podcast I love like how can

828
00:54:04,470 --> 00:54:07,200
I have something that is
actually functional, not just a

829
00:54:07,200 --> 00:54:11,400
dumb player that plays my feed.
But that allows me someone who

830
00:54:11,400 --> 00:54:15,270
I'm sharing that width on my
page, find other things or

831
00:54:15,270 --> 00:54:19,380
subscribe to it or join or you
know, there's there's just none

832
00:54:19,380 --> 00:54:23,310
of that thinking has happened in
over a decade because we all got

833
00:54:25,170 --> 00:54:29,430
kind of subdued into this.
Here's how it works. The simple

834
00:54:29,430 --> 00:54:30,900
player from Martin

835
00:54:32,220 --> 00:54:33,450
everything is so good.

836
00:54:33,480 --> 00:54:37,500
I got I got people who follow me
on on Twitter and stuff. So I

837
00:54:37,500 --> 00:54:40,290
get a pretty good gauge of what
people are thinking of

838
00:54:40,290 --> 00:54:44,520
something. And what I felt
immediately was people saying

839
00:54:44,520 --> 00:54:51,000
holy crap on it's fast and it's
on a website. They do not

840
00:54:51,000 --> 00:54:54,930
understand and they have been
already conditioned from birth.

841
00:54:55,350 --> 00:54:59,820
Podcasts happens in an app man.
That's a complicated business as

842
00:54:59,820 --> 00:55:03,150
go going on in there, you know
that's an app and the app is

843
00:55:03,150 --> 00:55:05,850
doing something I don't know.
It's, it's doing something

844
00:55:05,850 --> 00:55:09,000
really important. And that's it.
I can't live without that. So

845
00:55:09,000 --> 00:55:11,970
when they see it on a webpage,
and wait a minute, there's code,

846
00:55:11,970 --> 00:55:15,240
I can spin this up myself, I
can, I can do this on my own

847
00:55:15,240 --> 00:55:17,430
little thing, and I can
customize it. Thank you, Martin,

848
00:55:17,430 --> 00:55:20,850
by the way, for adding the
GitHub link. That's phenomenal.

849
00:55:21,510 --> 00:55:24,510
And people are responding that
way, like, Oh, crap, this is

850
00:55:24,510 --> 00:55:26,220
kind of cool. I can do so

851
00:55:26,220 --> 00:55:28,800
glad that he made that public
that open source because that

852
00:55:28,800 --> 00:55:31,140
means people would just fork
that thing and just go go to

853
00:55:31,140 --> 00:55:31,530
town.

854
00:55:33,270 --> 00:55:40,440
So to bring it around. I believe
that anything is valid. And I'd

855
00:55:40,440 --> 00:55:44,610
really prefer media URLs if you
can't hear it, or, or see moving

856
00:55:44,610 --> 00:55:50,700
images, and it becomes kind of
difficult, but I personally

857
00:55:51,420 --> 00:55:57,870
subscribe to one or two. Well, I
think one is different sermons

858
00:55:59,310 --> 00:56:03,630
from Ministry like is funny.
Now, do I listen all the time?

859
00:56:03,630 --> 00:56:06,630
No, do I listen to Joe Rogan all
the time? No, on the podcast,

860
00:56:06,660 --> 00:56:12,060
we'll roll in. I, I think we
said in one of the first

861
00:56:12,060 --> 00:56:16,560
episodes, I want a professor to
be able to say, Okay, I'm going

862
00:56:16,560 --> 00:56:19,590
to put this on a feed right now.
And my students can subscribe to

863
00:56:19,590 --> 00:56:22,620
it. And all I have to do is
publish and it's working. I

864
00:56:22,620 --> 00:56:26,970
don't have to figure out Apple,
I don't have to do all this

865
00:56:26,970 --> 00:56:30,360
stuff. I can just do it and put
it up and it's working within an

866
00:56:30,360 --> 00:56:33,600
hour and I can see it show up.
And it's I can tell my students

867
00:56:33,600 --> 00:56:36,930
to use whatever they want to
use. Why wouldn't a university

868
00:56:37,140 --> 00:56:43,890
create their own player
environment of Sir of, of their

869
00:56:43,890 --> 00:56:47,940
professors, lecturers, or the
president of the University

870
00:56:47,940 --> 00:56:52,320
speech and just have it work
like a normal podcast player

871
00:56:52,320 --> 00:56:55,380
would be limited to certain
categories, or certain fields

872
00:56:55,380 --> 00:56:58,290
that they want to do this into?
It's completely valid. And they

873
00:56:58,290 --> 00:57:00,660
could make a beautiful
experience without any of the

874
00:57:00,660 --> 00:57:04,770
hassle? No, Webmaster has to
update the player and all that,

875
00:57:04,770 --> 00:57:08,400
oh, oh, I'm putting it on the
shared drive. I know how this

876
00:57:08,400 --> 00:57:11,550
works in these companies. By the
way company, another perfect

877
00:57:11,550 --> 00:57:16,710
example. I've always said, you
know, the the idea of not then

878
00:57:16,710 --> 00:57:20,010
this is a whole different level
of stuff when you get into Okay,

879
00:57:20,010 --> 00:57:24,480
so what if I want to have a feed
of best dogs, you know, then you

880
00:57:24,480 --> 00:57:28,470
get into a whole whole nother
whole nother? Barrel of Monkeys

881
00:57:28,470 --> 00:57:28,920
really?

882
00:57:29,250 --> 00:57:31,020
Yeah, that's kind of like the
keyword fades thing.

883
00:57:31,380 --> 00:57:35,250
Right. So yeah, so the keywords,
it's, I think that they're

884
00:57:35,250 --> 00:57:40,830
trying to achieve something that
and a valiant effort, obviously

885
00:57:40,830 --> 00:57:45,450
on doing it. Whereas, hey, you
know what, you don't need to

886
00:57:45,450 --> 00:57:50,010
spam every index everywhere. But
what is your audience who you

887
00:57:50,010 --> 00:57:53,700
trying to reach? And you just
want to make it easy for them to

888
00:57:53,880 --> 00:57:59,490
find your sermons in their
podcast app? Why don't we help

889
00:57:59,490 --> 00:58:03,960
you create a little podcast app
for yourself? That has all that

890
00:58:03,960 --> 00:58:07,830
in there? Because now you don't
have to? Imagine this. You're a

891
00:58:07,830 --> 00:58:11,730
church. You are multi. In fact,
you can imagine very well, I

892
00:58:11,730 --> 00:58:15,060
know you've you've worked on
lots of podcasts for sermons,

893
00:58:15,060 --> 00:58:20,850
etc. So wouldn't it be beautiful
just to have a player that works

894
00:58:20,850 --> 00:58:25,080
for that? And and if you want,
Oh, and here's the other Parish,

895
00:58:25,080 --> 00:58:26,820
and you can add their feed to
it?

896
00:58:27,540 --> 00:58:32,760
Well, perfect, perfect example
would be like, podcast player

897
00:58:32,760 --> 00:58:37,020
that only searches for it only
returns results for sermons.

898
00:58:37,020 --> 00:58:38,730
Let's just say sermons from
Alabama.

899
00:58:38,759 --> 00:58:44,789
Hello, kid friendly podcast
apps. I mean, hello, apps. Wha?

900
00:58:45,599 --> 00:58:49,829
Hey, grandma. You want to Yeah,
I got my phone. I find it all

901
00:58:49,829 --> 00:58:54,359
kind of confusing. I'd like to
listen to, you know, to NPR. And

902
00:58:54,359 --> 00:58:56,729
I'd like to listen to these
shows will click the clickety

903
00:58:56,729 --> 00:58:59,309
clack clock, here you go.
There's no confusion. There's no

904
00:58:59,309 --> 00:59:02,159
stuff buzzing around flying
around. It's cheap. Now. It's

905
00:59:02,159 --> 00:59:06,509
cheap to make it we were doing
the shit on the back end. So you

906
00:59:06,509 --> 00:59:07,289
don't have to.

907
00:59:08,190 --> 00:59:13,140
Yeah, and in, in regards to
that. I think these categories

908
00:59:13,170 --> 00:59:16,230
are the category stuff is going
to really help with

909
00:59:16,230 --> 00:59:20,520
prioritizing. And well not
prioritizing, but it's going to

910
00:59:20,520 --> 00:59:23,670
help with segregating the
workload on the aggregators as

911
00:59:23,670 --> 00:59:27,660
well. I've even thought about
taking those sort of top level

912
00:59:27,660 --> 00:59:30,330
categories and assigning each
one of them to a specific

913
00:59:30,330 --> 00:59:34,380
aggregator interesting, I think
it does help because when you

914
00:59:35,010 --> 00:59:36,450
you know so

915
00:59:36,480 --> 00:59:39,030
well you know that on Sunday or
you're going to need some extra

916
00:59:39,030 --> 00:59:42,000
aggregation power right that for
for exactly

917
00:59:42,000 --> 00:59:44,640
that reason exactly what you're
talking about. You're you're

918
00:59:44,640 --> 00:59:47,580
gonna get you're gonna get an
onslaught on Sunday and Monday

919
00:59:47,610 --> 00:59:52,890
of sermon podcast going out out
of all the 1000s of churches. So

920
00:59:53,160 --> 00:59:56,940
you just segregate that off and
say okay for for the duration of

921
00:59:56,940 --> 01:00:01,170
Sunday and Monday, this this
agreat specific one or two

922
01:00:01,170 --> 01:00:03,270
aggregators are going to handle
this load, and it's going to

923
01:00:03,270 --> 01:00:05,760
just be best effort. So it's
gonna let you know, we're not

924
01:00:05,760 --> 01:00:07,980
going to try to hit them every
five seconds, as soon as they

925
01:00:07,980 --> 01:00:08,520
come out,

926
01:00:08,550 --> 01:00:11,610
right? Well, this kind of flows
into another topic that we were

927
01:00:11,610 --> 01:00:15,360
going to get to today. And that
is really the time based

928
01:00:15,360 --> 01:00:21,390
aggregation, understanding when
a feed updates, and what

929
01:00:21,390 --> 01:00:25,260
frequency and kind of sniffing
and being ready for when it's

930
01:00:25,260 --> 01:00:27,720
expected to do so am I saying
that right?

931
01:00:27,840 --> 01:00:32,520
Yeah, that's right. And, and I
would like to get other people's

932
01:00:32,520 --> 01:00:37,800
input on the mastodon server, or
wherever, on how best to go

933
01:00:37,800 --> 01:00:40,560
about doing something like that.
I don't know if it's going to, I

934
01:00:40,560 --> 01:00:43,920
don't know if it's purely I can
imagine ways to do it, that

935
01:00:43,920 --> 01:00:45,900
don't involve like machine
learning and that kind of thing.

936
01:00:45,900 --> 01:00:48,150
But maybe it's easier with
machine learning. I don't know,

937
01:00:48,450 --> 01:00:51,600
I just don't know enough about
that. But it would be nice to

938
01:00:51,600 --> 01:00:54,540
look at the history of a
podcast, without having to be

939
01:00:54,540 --> 01:00:59,010
told in the feed is in the feed
and XML itself, when it updates

940
01:00:59,040 --> 01:01:03,090
to be able to look at his update
history and say, Okay, this,

941
01:01:03,420 --> 01:01:10,260
this podcast, clearly updates on
Thursdays and Sundays. So

942
01:01:10,260 --> 01:01:13,410
I see that as an external, I
think it would be perfect

943
01:01:13,410 --> 01:01:16,200
actually an external machine
language, or what do you want to

944
01:01:16,200 --> 01:01:21,750
call AI ml project that takes
the firehose and analyzes that

945
01:01:21,750 --> 01:01:24,720
for a week, or a month or
whatever, and then starts to

946
01:01:24,750 --> 01:01:26,400
spit back some ideas.

947
01:01:27,300 --> 01:01:30,360
Yeah, and we can put an A, we
can put an endpoint in there

948
01:01:30,360 --> 01:01:31,470
that just except,

949
01:01:31,530 --> 01:01:33,810
you know, you know, where this
is going. I mean, I can tell, I

950
01:01:33,810 --> 01:01:37,110
can already tell you where this
is gonna go. Ultimately,

951
01:01:37,260 --> 01:01:40,440
someone's going to figure out a
way to ping us, which means

952
01:01:40,470 --> 01:01:43,950
aggregate now. Yeah, I mean,
that's, that's ultimately what's

953
01:01:43,950 --> 01:01:44,610
going to happen.

954
01:01:45,390 --> 01:01:50,790
Yeah, and see, that's why we
have the, we have the API

955
01:01:50,790 --> 01:01:54,180
permissions level, so we can
give trusted parties, that

956
01:01:54,180 --> 01:01:57,870
ability to give us trusted data
like that. So they can say,

957
01:01:58,050 --> 01:02:01,020
okay, ping, ping now, but I'm
not just going to randomly

958
01:02:01,020 --> 01:02:04,470
accept everybody in the world
saying, okay, ping me now, you

959
01:02:04,470 --> 01:02:08,670
know, so it's like, if we have
people that or somebody pops up

960
01:02:08,760 --> 01:02:12,420
and says, I want to do this, I
want to do this service for you.

961
01:02:12,420 --> 01:02:15,900
I want to tell you, Okay, paying
these things now, because this

962
01:02:15,900 --> 01:02:21,120
is what my, you know, software
is, is showing, give, give them

963
01:02:21,120 --> 01:02:25,440
a readwrite key and republish
give me a publisher key, and let

964
01:02:25,440 --> 01:02:29,400
them let them do that for us.
Yeah, it'd be great. That way,

965
01:02:29,400 --> 01:02:31,710
we don't have to do Oh, we don't
have to run all that horsepower.

966
01:02:32,190 --> 01:02:33,360
We'll do that yourself.

967
01:02:33,390 --> 01:02:39,570
So I would say the quote when
when, say who was pinging us now

968
01:02:39,570 --> 01:02:42,240
what hosters are pinging us the
rss.com? Guys?

969
01:02:43,980 --> 01:02:46,170
Yes, yeah. Since you think I
sent you.

970
01:02:46,980 --> 01:02:49,470
Yeah, I have it here. And you
sent me a lot of signal.

971
01:02:50,490 --> 01:02:56,880
And know that pod. podcast,

972
01:02:57,270 --> 01:03:02,790
we have station. Okay, we have
pod news Captivate fireside

973
01:03:02,820 --> 01:03:08,340
rss.com, add my podcast. Now
they're adding feeds. But

974
01:03:08,550 --> 01:03:13,710
they they're all adding feeds
and pod. You get them adding

975
01:03:13,710 --> 01:03:16,470
feeds, and then you have some
that are are integrating doing

976
01:03:16,470 --> 01:03:17,490
search with us.

977
01:03:17,970 --> 01:03:24,840
So when we. So do you know, is
blueberry integrating with us or

978
01:03:24,840 --> 01:03:25,440
not yet?

979
01:03:25,740 --> 01:03:29,160
I haven't seen anything coming
from them yet. Because

980
01:03:29,490 --> 01:03:32,490
that would be the way to do it
is hey, when someone publishes

981
01:03:32,850 --> 01:03:36,930
on your hosting platform, then
you send us a ping and we'll

982
01:03:37,830 --> 01:03:39,090
we'll parse right away.

983
01:03:39,630 --> 01:03:42,540
Yeah, yeah. And that's, that's
the whole idea behind poke, you

984
01:03:42,540 --> 01:03:50,190
know, well. But the thing is,
they're just not not all the

985
01:03:50,190 --> 01:03:54,660
services and platforms, do it?
Sure. So you end up having to,

986
01:03:54,660 --> 01:03:57,360
and this is the same reason why,
you know, the independent

987
01:03:57,570 --> 01:04:01,020
aggregator guys that have
infrastructure backing their

988
01:04:01,020 --> 01:04:05,910
apps, they they had to fall back
to this as well is because they

989
01:04:05,910 --> 01:04:08,730
just, it's just not a real lot.
The Pub Sub stuff is not

990
01:04:08,730 --> 01:04:11,250
reliable enough to purely depend
on it, you're

991
01:04:12,270 --> 01:04:14,400
always gonna be aggregating,
always gonna be doing that,

992
01:04:14,400 --> 01:04:17,160
well, well aggregate for as long
as we have to, and for

993
01:04:17,160 --> 01:04:22,740
whatever's needed that speaking
of such, this entire project is

994
01:04:22,740 --> 01:04:28,140
built under the value for value
philosophy. And that goes for

995
01:04:28,140 --> 01:04:32,280
everything. So we look for time,
talent and treasure, whatever

996
01:04:32,280 --> 01:04:36,030
you put into the database,
that's your value, you're going

997
01:04:36,030 --> 01:04:38,130
to get it out and if you don't,
then you'll just stop putting

998
01:04:38,130 --> 01:04:42,300
stuff in so we understand how
that system works. The same for

999
01:04:42,300 --> 01:04:44,760
the work that Dave and I are
doing that all the other devs

1000
01:04:44,760 --> 01:04:50,370
are doing. This is you know,
it's something that needs to be

1001
01:04:50,370 --> 01:04:54,630
done. It's clear that a lot of
people saw that it had to be

1002
01:04:54,630 --> 01:04:57,780
done. They've witnessed the
people showing up with with feed

1003
01:04:57,780 --> 01:05:01,170
databases, but when it gets down
to and you're running what? What

1004
01:05:01,170 --> 01:05:04,440
are you running now? 1112
servers. What do we have spun

1005
01:05:04,440 --> 01:05:04,710
up?

1006
01:05:04,920 --> 01:05:08,010
Yeah. 11 servers right now. And
we'll what's our what's our

1007
01:05:08,010 --> 01:05:08,520
current?

1008
01:05:08,790 --> 01:05:11,730
What's our current run rate for
costs like 300 a month now?

1009
01:05:12,630 --> 01:05:16,470
It's about it's still about 250?
Well, it's not including backup.

1010
01:05:16,470 --> 01:05:20,160
So it's about it's about 270.
Okay,

1011
01:05:20,190 --> 01:05:25,770
so donations have dropped off a
cliff. Yes. Appreciate the I

1012
01:05:25,770 --> 01:05:29,250
think someone showed up today
with a $6.66. And monthly

1013
01:05:29,250 --> 01:05:32,400
donation. Beelzebub, we
appreciate it. We feel good

1014
01:05:32,400 --> 01:05:33,030
about that.

1015
01:05:35,190 --> 01:05:37,080
We always love doing the dark
work here.

1016
01:05:37,110 --> 01:05:40,740
Yeah. Well, I saw it as two
times 333. So I just I just

1017
01:05:40,740 --> 01:05:42,720
stripped that down into what
makes me feel good.

1018
01:05:43,080 --> 01:05:45,330
Maybe it's appropriate that we
had a discussion about not

1019
01:05:45,330 --> 01:05:45,870
having pot.

1020
01:05:47,940 --> 01:05:52,560
Hey, we've been influenced, oh,
my Yes. Oh, boy. Look up. So

1021
01:05:52,620 --> 01:05:58,830
obviously, support is, is highly
appreciated and necessary.

1022
01:05:59,040 --> 01:06:01,080
Again, it's the time your
talent, your treasure, not

1023
01:06:01,080 --> 01:06:04,020
everyone can support
financially. We have a lot of

1024
01:06:04,020 --> 01:06:06,960
people showing up with their
talent and their time, but also

1025
01:06:06,960 --> 01:06:10,440
spreading the word. You know,
I'm seeing more and more people

1026
01:06:10,440 --> 01:06:14,430
tweeting about it. And we will,
just on I mean, that's all the

1027
01:06:14,430 --> 01:06:19,680
social media monetarily, except
for the mastodon stuff. Having

1028
01:06:19,950 --> 01:06:23,730
well, we'll have a better page
when people go to so when they,

1029
01:06:24,000 --> 01:06:26,490
they land there, and then like,
okay, I can, at least they

1030
01:06:26,490 --> 01:06:29,700
should kind of understand what
it does. And also, that page

1031
01:06:29,700 --> 01:06:32,760
should immediately send people
somewhere else. So I don't want

1032
01:06:32,760 --> 01:06:36,780
people coming to podcast
index.org and going, Oh, yeah.

1033
01:06:36,810 --> 01:06:42,090
Okay, cool. Thanks. I want them
to add something to do. If even

1034
01:06:42,090 --> 01:06:47,490
if it is search for something or
hit the hit the carousel, I want

1035
01:06:47,490 --> 01:06:50,640
them to go somewhere else. I
want them to play with an app, I

1036
01:06:50,640 --> 01:06:54,660
want them to find a random
podcast, I want them to maybe

1037
01:06:54,810 --> 01:06:58,350
look at a player that they could
customize and make their own. We

1038
01:06:58,350 --> 01:07:02,160
need places to send them. And
all you and all y'all out there

1039
01:07:02,160 --> 01:07:06,960
need to do is send me emails and
links of what you got and and

1040
01:07:06,960 --> 01:07:10,680
what the link is. And we'll send
them we that is that has to be

1041
01:07:10,680 --> 01:07:13,230
the point of the index is
sending people away.

1042
01:07:14,130 --> 01:07:17,880
We've got a few different people
that have now done subscriptions

1043
01:07:17,880 --> 01:07:23,730
for like 10 bucks a month. Now,
which is which is fantastic.

1044
01:07:23,730 --> 01:07:29,250
Because those types of things.
Yes. Just to sustain like $10 a

1045
01:07:29,250 --> 01:07:33,870
month, pay a one of our each of
our crawlers, each of the

1046
01:07:33,870 --> 01:07:36,870
aggregator servers is $10 a
month. There you go. You're

1047
01:07:36,870 --> 01:07:38,970
spawning bucks a month gives you
an aggregator

1048
01:07:39,000 --> 01:07:40,770
Yes. And we'll put your name on
it.

1049
01:07:42,510 --> 01:07:45,990
Here it is. I don't know how we
want to peerage this thing. If

1050
01:07:45,990 --> 01:07:48,690
you if you donate five bucks a
month do you get Are you like a

1051
01:07:48,690 --> 01:07:54,540
thumb drive? If it's like 20,
you upgrade it to like a like a

1052
01:07:54,570 --> 01:07:55,260
Raspberry Pi or

1053
01:07:56,160 --> 01:07:58,140
something like that. Yeah,
you're paying. That's funny. I

1054
01:07:58,140 --> 01:08:02,580
like that paying for servers. So
speaking of such an which, and

1055
01:08:02,580 --> 01:08:07,380
then last time, we talked about
the mean IO Server for the

1056
01:08:07,380 --> 01:08:11,310
images and one for the feeds.
Yeah. So where are we at?

1057
01:08:12,000 --> 01:08:18,600
Nowhere. Okay, it's just not
just no time is just not dropped

1058
01:08:18,600 --> 01:08:19,140
off. Okay.

1059
01:08:20,310 --> 01:08:23,820
Yeah, I've had to get these
category things out of the way.

1060
01:08:23,850 --> 01:08:28,530
And I'm still refining that if
the category stuff is really

1061
01:08:28,530 --> 01:08:32,790
part of the of a bigger. I'm
saying that I'm working on

1062
01:08:32,790 --> 01:08:37,200
categories. But what it really
is, is a RE is a refactoring of

1063
01:08:37,200 --> 01:08:41,130
the way filtering works across
the API. That includes

1064
01:08:41,130 --> 01:08:46,230
categories and language, right?
And timing. So basically, once,

1065
01:08:46,560 --> 01:08:50,100
once this quote unquote,
category stuff gets fully baked,

1066
01:08:50,100 --> 01:08:53,940
which is, it almost is I'm kind
of finishing it up right now.

1067
01:08:54,570 --> 01:09:01,140
Then, though, the way you call
that, that recent feeds API,

1068
01:09:02,040 --> 01:09:05,130
with all the way you can filter
that will be applied to

1069
01:09:05,130 --> 01:09:10,080
everything. So then we can just,
you know, you can. So it's a

1070
01:09:10,080 --> 01:09:13,590
bigger project than just
categories. As I'm refactor, I'm

1071
01:09:13,590 --> 01:09:17,490
just going to refactor all that
stuff to match. And then the end

1072
01:09:17,490 --> 01:09:20,790
it'll it'll solve some of the
issues that developers are

1073
01:09:20,790 --> 01:09:25,620
running into, like the recent
episodes API. Sometimes you go

1074
01:09:25,620 --> 01:09:30,450
back and you hit a wall, where
it just stops. And it's because

1075
01:09:31,350 --> 01:09:34,920
it's because there's, there's
gaps. If anybody you know,

1076
01:09:34,980 --> 01:09:39,510
there's guys out there familiar
with, with databases know that

1077
01:09:39,510 --> 01:09:43,740
when you have an auto index, an
auto indexing ID, every time you

1078
01:09:43,740 --> 01:09:47,430
insert a record in increments,
the auto ID number, for that

1079
01:09:47,430 --> 01:09:50,640
record, it just goes up by one.
Well, there's a lot there's lots

1080
01:09:50,640 --> 01:09:54,900
of different ways that you can
get gaps in that. And one of the

1081
01:09:54,900 --> 01:09:59,190
ways that we were inserting item
episodes into the database

1082
01:10:00,000 --> 01:10:06,180
initially, was with a, what's
called an on duplicate key

1083
01:10:06,420 --> 01:10:09,930
update. And so you try to you
try to put a new episode in

1084
01:10:09,930 --> 01:10:13,920
there if the episode already
exists, right? Then you just you

1085
01:10:13,920 --> 01:10:16,680
say normally it would fail and
say it's a dupe is already in

1086
01:10:16,680 --> 01:10:20,580
there. But you can say on
duplicate key update. Now wait,

1087
01:10:20,580 --> 01:10:24,150
it'll update key certain, it'll
say, okay, it exists. So I'm

1088
01:10:24,150 --> 01:10:27,030
just going to change it. And
it'll update certain key

1089
01:10:27,030 --> 01:10:30,030
information about that record.
And we're doing that in order to

1090
01:10:30,030 --> 01:10:32,640
pick up some metadata that we
were not initially getting.

1091
01:10:32,880 --> 01:10:39,720
Okay? Like, for instance, we
were not initially pulling in

1092
01:10:40,200 --> 01:10:42,900
iTunes episode type. So that's
the one where it's like

1093
01:10:42,900 --> 01:10:46,770
episodic, or serial or whatever.
So we added that and so I

1094
01:10:46,770 --> 01:10:50,610
started doing an update on that,
well, every time you if you use

1095
01:10:50,610 --> 01:10:56,640
the own duplicate key update
function, then it auto allocates

1096
01:10:56,970 --> 01:11:02,910
a new record ID every time and
if he if it doesn't update, it

1097
01:11:02,910 --> 01:11:05,760
just discards it. So what you
would end up with is you would

1098
01:11:05,760 --> 01:11:10,920
end up with episodes, being
incrementally ID up till let's

1099
01:11:10,920 --> 01:11:14,580
just say 1,000,030 5 million,
and then the net and then it

1100
01:11:14,580 --> 01:11:19,830
jumps from 35 million to 36 575.
To You know, it's gonna jumps

1101
01:11:19,830 --> 01:11:24,720
huge heart gap. So anyway, this,
that's a long way of saying that

1102
01:11:24,900 --> 01:11:28,200
the the category work, the
reason it's taking so much time

1103
01:11:28,200 --> 01:11:31,410
is because it's encompassing
more than is encompassing all of

1104
01:11:31,410 --> 01:11:35,220
these issues. So that can just
fix it all at once. What and

1105
01:11:35,220 --> 01:11:35,880
then move on,

1106
01:11:35,940 --> 01:11:39,690
what could you specifically use
help with right now?

1107
01:11:43,500 --> 01:11:50,310
At this very moment, not much,
but once there's a couple of

1108
01:11:50,310 --> 01:11:54,690
people that have offered help on
on infrastructure. So they've

1109
01:11:54,690 --> 01:11:58,500
offered help with Docker rising
some stuff. Good, cool. Yeah.

1110
01:11:58,530 --> 01:12:01,410
Yeah. That's going to be very
valuable. And I'm going to

1111
01:12:01,410 --> 01:12:05,040
follow up with those guys. As
soon as I get to that, and

1112
01:12:05,040 --> 01:12:05,280
that's,

1113
01:12:05,310 --> 01:12:07,860
and it's valuable, because we
can easily move infrastructure

1114
01:12:07,860 --> 01:12:10,380
from server to server or
wherever. Yeah, that's totally

1115
01:12:10,380 --> 01:12:13,950
Yeah. Yeah. Makes recovery
easier. All that kind of jazz.

1116
01:12:14,730 --> 01:12:18,600
Yeah, no, Docker. Docker is
awesome. And it's just not the

1117
01:12:18,810 --> 01:12:20,610
something we did from the
beginning. So we're gonna have

1118
01:12:20,610 --> 01:12:24,240
to bake it in after the fact?
Where

1119
01:12:24,240 --> 01:12:28,470
do you think we are in the
process of being somewhere where

1120
01:12:28,470 --> 01:12:31,230
you can sit back and say, Okay,
today, I'm just gonna watch how

1121
01:12:31,230 --> 01:12:31,980
it runs?

1122
01:12:35,130 --> 01:12:40,800
I think we're, I feel like we're
probably a month or so away from

1123
01:12:40,800 --> 01:12:47,070
that. And then maybe that's
optimistic. But I feel as well,

1124
01:12:47,070 --> 01:12:52,020
I feel like just based on
progress. In the one, well, I'll

1125
01:12:52,020 --> 01:12:55,500
tell you another area of help
this directly related to that is

1126
01:12:58,110 --> 01:13:02,730
look, looking at the database,
and sanitizing it somewhat just

1127
01:13:02,730 --> 01:13:06,120
just kind of what related to
what we talked about earlier. It

1128
01:13:06,120 --> 01:13:09,480
would be nice, it's a now if
posted the feeds list. It would

1129
01:13:09,480 --> 01:13:13,980
be nice to have people look at
it in and play with, with those

1130
01:13:14,850 --> 01:13:20,490
with that list and see, take a
crack at finding stuff that's

1131
01:13:20,520 --> 01:13:25,050
just garbage. And there's going
to be plenty of that in their

1132
01:13:25,679 --> 01:13:30,719
feeds that are garbage or just
or yeah stations or like the 800

1133
01:13:31,169 --> 01:13:33,059
sermon, audio feed stuff like

1134
01:13:33,570 --> 01:13:36,120
well, that those will be good to
know. But I'm thinking more

1135
01:13:36,120 --> 01:13:39,630
specifically, like I saw my
first fraud feed yesterday in

1136
01:13:39,630 --> 01:13:44,400
the index. Ah, and it was Scott
Adams, somebody cloned Scott

1137
01:13:44,400 --> 01:13:49,110
Adams podcast on Anchor. All
this stuff always comes through

1138
01:13:49,110 --> 01:13:53,130
anchor. Yeah. And they clone
this is feed on anchor and put

1139
01:13:53,130 --> 01:13:56,940
like some kind of donation link
up. What did they and they

1140
01:13:56,940 --> 01:13:59,670
called it the real Scott Adams
podcast.

1141
01:14:00,419 --> 01:14:02,699
So how did you catch it just by
seeing it?

1142
01:14:03,210 --> 01:14:08,010
I searched for I was doing some
timing stuff, trying to figure

1143
01:14:08,010 --> 01:14:11,400
out where the aggregator was.
And I was just searching for

1144
01:14:11,400 --> 01:14:14,160
random stuff that was coming to
my mind and I searched for Scott

1145
01:14:14,160 --> 01:14:17,730
Adams to check his part because
I know he does an almost daily

1146
01:14:17,730 --> 01:14:21,900
podcast and it just came up in
the results there was another

1147
01:14:21,900 --> 01:14:22,350
one there.

1148
01:14:22,889 --> 01:14:28,709
So again, this is something that
we could use AI or AI or ml

1149
01:14:29,099 --> 01:14:34,559
external to us with HMI human
human intelligence. Oh okay. So

1150
01:14:35,489 --> 01:14:38,909
from I know you'd like to so
there's nothing that says that

1151
01:14:38,909 --> 01:14:41,819
we can't have a page that shows
the version of the fire hose

1152
01:14:41,819 --> 01:14:44,429
that people can look at and say
hey, that looks bogus. Let me

1153
01:14:44,429 --> 01:14:47,879
take a look and then could tag
it flag it market whatever.

1154
01:14:48,419 --> 01:14:49,649
I would love that

1155
01:14:49,650 --> 01:14:52,470
well that's just just brother
make a page I'll promote the

1156
01:14:52,470 --> 01:14:56,310
crap out of it. And people love
sitting there personally, that

1157
01:14:56,310 --> 01:14:59,160
was always see you made the
carousel which was never my

1158
01:14:59,190 --> 01:15:03,210
vision but I I love it. My
vision was literally I want to

1159
01:15:03,210 --> 01:15:09,360
see almost like a, like an IRC
chat, I just want to see line

1160
01:15:09,390 --> 01:15:13,260
line line line, as I see part
witness coming in this updated

1161
01:15:13,260 --> 01:15:19,590
this updated. I mean, give me an
SSH or whatever, you know, give

1162
01:15:19,590 --> 01:15:20,700
me a terminal to do that.

1163
01:15:20,940 --> 01:15:23,220
And I like the dashboard, your
dashboard.

1164
01:15:23,730 --> 01:15:27,510
I'm not a douchey dashboard guy.
I'm a command line guy these

1165
01:15:27,510 --> 01:15:30,690
days. So I really like I have a
Twitter client, that's Command

1166
01:15:30,690 --> 01:15:34,590
Line. You know, I like oh, I
just love it, you know, because

1167
01:15:34,590 --> 01:15:40,170
I just logs. I love watching
that stuff come in. So for me, I

1168
01:15:40,170 --> 01:15:42,360
look at that. And if I say hey,
wait a minute, here's something

1169
01:15:42,360 --> 01:15:45,690
that's three of the same in a
row. I'd flag it. Yeah, and we'd

1170
01:15:45,690 --> 01:15:49,140
go somewhere. And so that's the
human intelligence. I see no

1171
01:15:49,140 --> 01:15:53,880
reason why you couldn't hang
some kind of reader off of the

1172
01:15:55,410 --> 01:15:59,190
off of our endpoint for the
hose. Oh, God, I'm speaking the

1173
01:15:59,190 --> 01:16:00,300
lingo. Not for

1174
01:16:00,780 --> 01:16:04,410
endpoint hang, hanging, hanging
it off the hose. Yeah, I'm

1175
01:16:04,410 --> 01:16:06,600
hanging off the endpoint for the
hose. I'm sipping,

1176
01:16:07,590 --> 01:16:12,300
clip the clip, clip three Brene
Brown Assa God,

1177
01:16:12,330 --> 01:16:16,860
I just got goosebumps from head
to toe. You I love you came

1178
01:16:16,860 --> 01:16:21,300
prepared. I'm doing the work. Or
you know, someone who just has

1179
01:16:21,630 --> 01:16:26,070
some AI looking at it some algo
and says, Hey, I saw this I saw

1180
01:16:26,070 --> 01:16:30,840
that come in. And that stuff. By
the way, no one can compete with

1181
01:16:30,840 --> 01:16:34,590
us on Apple can't compete.
Spotify can't compete.

1182
01:16:34,830 --> 01:16:39,270
Obviously, anchor FM can't
compete. And why wouldn't we

1183
01:16:39,270 --> 01:16:43,110
make that list public to the
world? Why wouldn't we say? Why

1184
01:16:43,110 --> 01:16:45,600
wouldn't we put it out there and
say everybody was running an

1185
01:16:45,600 --> 01:16:48,090
index? Here's what we found, you
may want to update

1186
01:16:48,510 --> 01:16:51,990
it. That's exactly what I want.
I would love for somebody be

1187
01:16:51,990 --> 01:16:57,570
analyzing every every feed in
the database sort of constantly.

1188
01:16:57,870 --> 01:17:00,510
And as soon as they find
something that looks fishy and

1189
01:17:00,510 --> 01:17:03,840
fraudulent. It just they just
paying it back to us. And then

1190
01:17:03,840 --> 01:17:07,830
we and we publish that list. We
publish? I don't know call it,

1191
01:17:08,400 --> 01:17:10,080
you know, suspicious that

1192
01:17:10,080 --> 01:17:13,470
problematic last year
problematic. problematic. Yes.

1193
01:17:15,390 --> 01:17:18,210
You made it to the problematic
list. That's right, I guess

1194
01:17:18,210 --> 01:17:25,020
index. Me that'll see that, that
that's a service do is everybody

1195
01:17:25,020 --> 01:17:25,770
needs? Yes.

1196
01:17:25,770 --> 01:17:30,030
And if anybody can participate,
why wouldn't it be? Look, if I

1197
01:17:30,030 --> 01:17:35,970
go right now to our search,
which I love. Right? Okay. Now,

1198
01:17:35,970 --> 01:17:38,640
let me just see, I kind of kind
of liked that idea that you were

1199
01:17:38,640 --> 01:17:44,160
using Scott Adams as an example.
So if I put Scott Adams in hold

1200
01:17:44,160 --> 01:17:47,400
on it. I'm a developer, right.
Get in here. Oh, yeah. Come on

1201
01:17:47,400 --> 01:17:55,440
developer API. Yeah. Here we go.
Search. So I do Scott Adams.

1202
01:17:55,440 --> 01:17:59,910
Let's see what pops up. So I've
got Scott Adams show which is

1203
01:17:59,910 --> 01:18:03,000
apparently some different Scott
Adams real coffee with Scott

1204
01:18:03,000 --> 01:18:07,410
Adams coffee with so real coffee
with Scott Adams is an anchor FM

1205
01:18:07,440 --> 01:18:08,940
podcast looks both fraud

1206
01:18:08,940 --> 01:18:11,640
fake? It's a fraud. It's that's
the fraud fee. That's the one.

1207
01:18:12,150 --> 01:18:17,130
Yep. And like you can tell
because it says support this

1208
01:18:17,130 --> 01:18:21,390
podcast, anchor FM blah, blah,
blah, slash support. And so like

1209
01:18:21,390 --> 01:18:24,750
that's, they were talking about
this on the new media show, I

1210
01:18:24,750 --> 01:18:25,080
think.

1211
01:18:26,010 --> 01:18:28,860
Yeah, this is this is a big
problem. Is this fraud? Yeah,

1212
01:18:28,889 --> 01:18:30,419
exactly. It's all coming from in

1213
01:18:30,509 --> 01:18:34,559
a lot of his drop from anchor,
Rob. Yeah, yeah,

1214
01:18:34,590 --> 01:18:38,040
he was saying that. The reason
is, so that is such a bad

1215
01:18:38,040 --> 01:18:41,850
problem on on Anchor is because
they allow one person to set it

1216
01:18:41,850 --> 01:18:45,120
to buy an account and create as
many phases they want to off one

1217
01:18:45,120 --> 01:18:47,910
account. And you can just
directly link back and get

1218
01:18:47,910 --> 01:18:51,450
support for your, you know, that
way, and so it doesn't cost you,

1219
01:18:51,600 --> 01:18:54,630
you can just dump a million
things in there, and it doesn't

1220
01:18:54,630 --> 01:18:59,370
cost you anything. So if it's
just like the it's like the spam

1221
01:18:59,550 --> 01:19:04,350
payback scenario, if you you
know, if, if it's if sending

1222
01:19:04,650 --> 01:19:08,220
8000 spams cost you just the
same amount is sending a

1223
01:19:08,250 --> 01:19:12,420
million, then there's no
deterrent. So So what you're

1224
01:19:12,420 --> 01:19:13,230
saying the decimal?

1225
01:19:14,520 --> 01:19:16,080
Go ahead. Yeah, I was gonna

1226
01:19:16,080 --> 01:19:18,600
say what would it say that
that's why that exists? Yeah.

1227
01:19:18,630 --> 01:19:23,640
Why? So what is the appropriate
action? Here? Since okay, we're

1228
01:19:23,640 --> 01:19:27,390
looking at this, we're pretty
sure it's a scam, feed, spam

1229
01:19:27,390 --> 01:19:31,830
feed, everything points towards
it. There's no evidence that is

1230
01:19:31,830 --> 01:19:36,990
actually Scott Adams property
other than his property is being

1231
01:19:36,990 --> 01:19:42,090
ripped off. So what should we
what do you feel the appropriate

1232
01:19:42,090 --> 01:19:43,140
action is?

1233
01:19:44,790 --> 01:19:48,570
Well, you know what, one thing
that I could say is if we had

1234
01:19:49,320 --> 01:19:55,380
the problematic feed, where we
were pumping out things that

1235
01:19:55,380 --> 01:20:00,120
look problematic, then each
individual podcaster could To

1236
01:20:00,300 --> 01:20:06,150
filter for just themselves, and
then be looking themselves for

1237
01:20:06,150 --> 01:20:07,350
things that pop up.

1238
01:20:09,030 --> 01:20:13,590
So it's almost like a UBL, black
block list.

1239
01:20:15,030 --> 01:20:18,480
Well, I was thinking, I could
see that. What I was thinking

1240
01:20:18,480 --> 01:20:23,820
though, in my head was that if
I'm Scott Adams, and I just

1241
01:20:23,820 --> 01:20:31,440
subscribed to the problematic
feed with a Scott Adams terms in

1242
01:20:31,440 --> 01:20:34,980
it, and I know what it always
looks like, if a new one pops

1243
01:20:34,980 --> 01:20:39,840
up, check it out. Like I just
refresh, you know, or not

1244
01:20:39,840 --> 01:20:43,080
refresh, but I subscribe to it.
Maybe I subscribe to it as an

1245
01:20:43,080 --> 01:20:47,550
RSS feed. And if anything ever
comes up with a new, like,

1246
01:20:47,550 --> 01:20:50,910
there's always the same five
results in the index for Scott

1247
01:20:50,910 --> 01:20:54,660
Adams. And there's mine and
maybe a few others that are

1248
01:20:54,660 --> 01:20:54,960
other.

1249
01:20:55,800 --> 01:20:59,820
Okay. Oh, so I think what you're
saying is, so for no agenda, I

1250
01:20:59,820 --> 01:21:05,040
would, I would have a feed or
some place, I can see what pops

1251
01:21:05,040 --> 01:21:09,480
up continuously on new no
agenda. And if something pops

1252
01:21:09,480 --> 01:21:12,300
up, it's like, Oh, hold on a
second. That's bullshit. And

1253
01:21:12,300 --> 01:21:16,980
then I can take some action,
supposedly, that the, if

1254
01:21:16,980 --> 01:21:19,890
you're subscribed, yeah. And if
you're subscribing to it on a

1255
01:21:19,890 --> 01:21:22,500
regular, you know, on a regular
basis, and where you can see all

1256
01:21:22,500 --> 01:21:26,910
the time, then, you know, you're
subscribing to the problematic

1257
01:21:26,910 --> 01:21:29,970
feed and some new no agenda
thing pops up. And you can see

1258
01:21:30,000 --> 01:21:32,460
quickly, you can just eyeball
and say, well, that's just a

1259
01:21:32,460 --> 01:21:35,460
name collision, that's not a big
deal. And then, three weeks

1260
01:21:35,460 --> 01:21:37,380
later, another one pops up.
Well, that's

1261
01:21:37,530 --> 01:21:41,070
okay. So here's something that
somebody can create right away,

1262
01:21:41,070 --> 01:21:43,830
then I think this would be very
helpful, particularly since it's

1263
01:21:43,830 --> 01:21:46,800
an industry wide problem.
Everyone's bitching about it,

1264
01:21:46,800 --> 01:21:55,110
I'd like to do something, let's
let's create this functionality.

1265
01:21:56,130 --> 01:22:03,960
So that when a spam feed shows
up, we can publicly expose that.

1266
01:22:04,140 --> 01:22:07,290
And privately Of course, we say,
hey, anchor, you know, I don't

1267
01:22:07,290 --> 01:22:10,230
know if we have any contact or
not. But we have to have the

1268
01:22:10,230 --> 01:22:18,060
whole the whole podcasting. I
don't, I can't bring myself to

1269
01:22:18,060 --> 01:22:20,730
say space, because it just makes
me want to shoot myself.

1270
01:22:21,690 --> 01:22:26,760
Ecosystem, know that this is
going on. And you'll maybe see

1271
01:22:26,760 --> 01:22:30,420
this, why come back to the
almost like a block list, we

1272
01:22:30,420 --> 01:22:34,200
have to have a way that people
can say, hey, I'm tagging this,

1273
01:22:34,230 --> 01:22:38,160
this looks fake, I'm really sure
it's fake, a way to propagate

1274
01:22:38,160 --> 01:22:40,050
that and a way for people to
take action.

1275
01:22:41,280 --> 01:22:44,490
It See, this is what I was
saying on on Reddit the other

1276
01:22:44,490 --> 01:22:52,350
day when I was talking with
Daniel is that I feel like so

1277
01:22:52,770 --> 01:22:57,600
James critten. On the saying
this, too, he's he said that

1278
01:22:57,600 --> 01:23:01,110
Apple is so their iTunes
database has tons of junk in it.

1279
01:23:01,110 --> 01:23:03,690
And there must be some special
relationship between iTunes and

1280
01:23:03,690 --> 01:23:07,770
anchor. Because if you can, you
can find all over iTunes, you

1281
01:23:07,770 --> 01:23:11,310
can find test feeds that come
from anchor, and I see him in

1282
01:23:11,310 --> 01:23:14,910
our index as well. It'll just
say it'll be like, as a list of

1283
01:23:14,970 --> 01:23:18,870
of A's, it'd be like six A's as
the title of the podcast, you

1284
01:23:18,870 --> 01:23:23,670
know, we'll have one episode in
a dish called test. And like,

1285
01:23:23,700 --> 01:23:29,100
you find that all over the
place. So those kinds of things.

1286
01:23:29,700 --> 01:23:34,650
I feel like if we create the
proper linkage back and forth

1287
01:23:34,680 --> 01:23:39,240
with the other platforms and
other podcast networks, so that

1288
01:23:39,600 --> 01:23:44,160
all of them are feeding in or
feeding to us and in and then we

1289
01:23:44,160 --> 01:23:49,080
feed back out. So that in that
makes it enough in effect, where

1290
01:23:49,080 --> 01:23:52,080
everybody's linking to each
other, then what what you

1291
01:23:52,080 --> 01:23:58,500
develop is a humongous platform
that is more trustworthy, single

1292
01:23:58,500 --> 01:24:04,500
entity. Everybody can police.
But because when live, you know

1293
01:24:04,500 --> 01:24:08,340
lips, Lipson can look at its
podcast, and they can be

1294
01:24:08,340 --> 01:24:11,910
monitoring the problematic feed
or whatever, and when and they

1295
01:24:11,910 --> 01:24:15,750
can automate, being able to
detect when something pops up,

1296
01:24:15,900 --> 01:24:17,160
it's a clone of their stuff.

1297
01:24:18,030 --> 01:24:22,050
So then ultimately, we're not
ever really going to delete

1298
01:24:22,050 --> 01:24:26,430
something necessarily from the
index, but we have very clear

1299
01:24:26,430 --> 01:24:29,160
ways to filter out what is
bogus.

1300
01:24:29,760 --> 01:24:33,720
Yeah, and well, hanging off of
that whole idea would be like,

1301
01:24:34,620 --> 01:24:37,740
what I would love to eventually
get to would be like a quorum.

1302
01:24:38,190 --> 01:24:43,350
And you say, Okay, three other
podcast networks and also my

1303
01:24:43,350 --> 01:24:46,470
guys. Like it's like a Bitcoin
confirmation.

1304
01:24:46,890 --> 01:24:52,230
Yeah, yeah, exactly. Hit prove
you, you give. There's this

1305
01:24:52,230 --> 01:24:54,570
thing just popped up in the
problematic feed because you got

1306
01:24:54,570 --> 01:24:56,880
this guy over here who's
analyzing it all as it comes

1307
01:24:56,880 --> 01:25:00,300
through. And he's pinging back
and saying, Okay, thank you. My

1308
01:25:00,300 --> 01:25:04,680
system says this thing looks
like it may be bogus. And then

1309
01:25:04,680 --> 01:25:08,280
you give it you give that
problematic entry and Id maybe

1310
01:25:08,280 --> 01:25:10,920
it will say whatever. And then
everybody else looks at it and

1311
01:25:10,920 --> 01:25:13,650
says, Well, yeah, I think that's
bogus, too. Well, then you just,

1312
01:25:13,890 --> 01:25:18,600
you just block it. Right and
take it off. Or we take it off.

1313
01:25:19,200 --> 01:25:23,550
Yeah, right, either from search
or what? Are we put a confirmed

1314
01:25:23,700 --> 01:25:28,140
problematic tag flag on that
feel? Yeah. Yeah, that's a good

1315
01:25:28,140 --> 01:25:30,690
way to do it. And everyone can
make their own make their own

1316
01:25:30,690 --> 01:25:32,010
decision what they want to do.

1317
01:25:32,550 --> 01:25:34,560
That's a great, yeah, I like
that better, like putting the

1318
01:25:34,560 --> 01:25:35,490
problematic tag,

1319
01:25:35,670 --> 01:25:39,090
just put it exactly. put a tag
on it. Yeah. Because then you

1320
01:25:39,090 --> 01:25:39,360
didn't

1321
01:25:39,360 --> 01:25:41,850
everybody else's apps can choose
to not show it.

1322
01:25:42,120 --> 01:25:45,180
And we're the, we're the perfect
place to facilitate that. And

1323
01:25:45,180 --> 01:25:47,970
this is, this is another one,
those beautiful things that I

1324
01:25:47,970 --> 01:25:51,810
think that we can really, really
make work. If people are willing

1325
01:25:51,810 --> 01:25:55,440
to step up, and put that
together, we certainly have most

1326
01:25:55,440 --> 01:25:58,350
of the pieces. And if you think
you know somebody who can help

1327
01:25:58,350 --> 01:26:00,420
with this, let's solve this real
problem. By the way, you know,

1328
01:26:00,420 --> 01:26:03,930
anchor is Spotify. I mean,
that's, that is,

1329
01:26:04,290 --> 01:26:07,440
seems to be another company that
it's like, teachers like there's

1330
01:26:07,440 --> 01:26:09,480
nobody that actually works
there. It's just a robot.

1331
01:26:09,510 --> 01:26:12,300
Oh, yes, well, I know that
they're integrated on the back

1332
01:26:12,300 --> 01:26:16,740
end with a lot of the hosters. I
don't know if we discussed this,

1333
01:26:16,800 --> 01:26:22,950
maybe last year, or the show
before. It, there's all kinds of

1334
01:26:23,520 --> 01:26:28,020
requirements for a hosting
company, I know one or two, but

1335
01:26:28,020 --> 01:26:30,570
I don't want to call them out by
name, because I don't know. It's

1336
01:26:30,600 --> 01:26:33,360
their business. I know if it was
told in confidence or not. But

1337
01:26:33,360 --> 01:26:37,080
you have to actually host your
media file on the hoster

1338
01:26:37,080 --> 01:26:41,970
servers. Because there's a
process that goes from them

1339
01:26:42,210 --> 01:26:45,840
direct to anchor, and anchor
does something and it goes

1340
01:26:45,840 --> 01:26:48,810
directly to Spotify. That's
basically it. And I have a

1341
01:26:48,810 --> 01:26:54,090
feeling that and this will be
very typical for what are they

1342
01:26:54,090 --> 01:27:02,160
calling corporate relationship
management, CRM, for Spotify, to

1343
01:27:02,160 --> 01:27:06,030
have sat down at the you know,
in the smoky room with the Apple

1344
01:27:06,030 --> 01:27:10,260
guys and said, Hey, you trust
us? We're big, and we got lots

1345
01:27:10,260 --> 01:27:14,370
of money, right? Yeah, you got a
look, we got this ingest system

1346
01:27:14,370 --> 01:27:18,180
where, you know, we, we checked
everything. What do we got? We

1347
01:27:18,180 --> 01:27:21,000
got paper and all these people.
It's all good. So you'll just

1348
01:27:21,030 --> 01:27:24,540
take our submissions sight
unseen, right? That's probably

1349
01:27:24,540 --> 01:27:25,230
what's happening.

1350
01:27:26,010 --> 01:27:30,300
That's That's what, that's what
James was saying that it's clear

1351
01:27:30,300 --> 01:27:33,390
that that's happening to some
degree, but you know, just

1352
01:27:33,390 --> 01:27:36,420
nobody's. Everybody just acts
like it's not Yeah,

1353
01:27:36,450 --> 01:27:41,370
but but we so and this can be
expanded to your player, if you

1354
01:27:41,370 --> 01:27:45,240
have a podcast player, and in
search, something shows up, let

1355
01:27:45,240 --> 01:27:47,820
your users tag it like, Hey, I
think this might be a problem.

1356
01:27:48,300 --> 01:27:52,770
And this could feed right back
into Apple. Let's give Apple

1357
01:27:52,770 --> 01:27:56,730
this beautiful news. And g
Hello, Google. I know there's no

1358
01:27:56,730 --> 01:27:59,730
one there. I know. It's just a
black box. But you could you

1359
01:27:59,730 --> 01:28:02,220
could take our feed that says,
hey, you might want to look at

1360
01:28:02,220 --> 01:28:05,520
these you know, for spam. You
want to make your search good.

1361
01:28:06,240 --> 01:28:09,210
What was it always the biggest
companies that make the most

1362
01:28:09,210 --> 01:28:12,390
money? are the ones that are
impossible to get a human being

1363
01:28:12,390 --> 01:28:14,340
to answer the phone? Well, like,

1364
01:28:14,520 --> 01:28:17,820
Well, Dave, look at where all
the religious podcasts are

1365
01:28:17,820 --> 01:28:20,640
showing up. They're showing up
with us clearly the devil the

1366
01:28:20,640 --> 01:28:21,780
devil is on their side.

1367
01:28:24,060 --> 01:28:25,710
Hey, we're getting sick, sick,
sick, delicious.

1368
01:28:28,110 --> 01:28:30,660
Man, some soon someone was
telling us to do something.

1369
01:28:30,660 --> 01:28:34,080
Okay. So to summarize for this
for this next week.

1370
01:28:35,190 --> 01:28:36,810
To summarize, we solved
podcasting.

1371
01:28:36,839 --> 01:28:41,789
We saw podcasting is very good
is there so we kind of know what

1372
01:28:41,909 --> 01:28:46,529
what you would find helpful. I
really love the idea of, well,

1373
01:28:47,009 --> 01:28:50,069
I'll work I'll work with drunk
playdough. And make sure we know

1374
01:28:50,069 --> 01:28:52,649
when he's ready. We'll get all
the right stuff on the homepage

1375
01:28:52,649 --> 01:28:57,029
and get some of these lists up.
Get all that going. And

1376
01:28:57,269 --> 01:29:00,479
hopefully, we've inspired
someone to come up with some

1377
01:29:00,539 --> 01:29:03,959
some something that does some of
what we've looked to solve. So

1378
01:29:03,959 --> 01:29:09,539
whether it's the the problematic
lists, whether it's different

1379
01:29:09,539 --> 01:29:13,799
kinds of filtered players and
examples is what we need. That's

1380
01:29:13,949 --> 01:29:16,379
again, that's why I love with
the simple player and cast

1381
01:29:16,379 --> 01:29:19,709
coverage. Do they show great
examples of what you can do?

1382
01:29:19,859 --> 01:29:23,699
That is not your typical, hey,
here's a podcast radio receiver.

1383
01:29:23,849 --> 01:29:28,319
And here's where you turn the
dial. Here's where you know, and

1384
01:29:28,319 --> 01:29:32,849
by the way just thinking of
that, I mean, why couldn't you

1385
01:29:32,849 --> 01:29:35,999
have the randomizer like oh
press this button for something

1386
01:29:35,999 --> 01:29:39,689
from tech press this button from
something from God casts or

1387
01:29:39,689 --> 01:29:42,509
press this button for something
for something else. And after

1388
01:29:42,509 --> 01:29:45,479
you've done that, here's your
breadcrumb trail here's what you

1389
01:29:45,479 --> 01:29:47,759
checked out. Do you want to
subscribe to any of these do you

1390
01:29:47,759 --> 01:29:50,369
want to recommend any of these?
I can go on forever.

1391
01:29:50,700 --> 01:29:54,450
Oh, yeah, you know, don't get
Adam stories. Here's the idea.

1392
01:29:54,720 --> 01:29:57,720
The idea machine. It did just
come out it's rollout.

1393
01:29:57,750 --> 01:30:01,650
I'm long on ideas and short on
code, my friend And I guess

1394
01:30:01,650 --> 01:30:05,970
champagne wishes and beer money
is all part of the same problem.

1395
01:30:06,869 --> 01:30:13,949
Give me Give me clip, clip five
Brene Brown NASA. Oh my god, the

1396
01:30:13,949 --> 01:30:16,079
polar bear Holy

1397
01:30:16,080 --> 01:30:22,470
crap, that's good for no agenda,
I'm using that one. Alright,

1398
01:30:22,500 --> 01:30:24,240
we got we lost one. So this is,

1399
01:30:25,260 --> 01:30:28,920
well, we'll be playing these
shows that we lose as we go

1400
01:30:28,920 --> 01:30:31,560
along. And remember, this is
just phase one of the mission

1401
01:30:31,560 --> 01:30:34,920
everybody. This is preserving
podcasting as a platform for

1402
01:30:34,920 --> 01:30:37,380
free speech, that message has
gotten out that message is

1403
01:30:37,380 --> 01:30:40,410
propagating, keep that message
in mind and keep telling that

1404
01:30:40,410 --> 01:30:42,660
that's what we're doing. We're
trying to fix all these horrible

1405
01:30:42,660 --> 01:30:46,020
things, trying to make it better
for everybody. And one of these

1406
01:30:46,020 --> 01:30:49,110
days, we'll get into phase two,
which is retooling podcasting

1407
01:30:49,110 --> 01:30:52,740
into a platform of value. I'm
very excited about that part,

1408
01:30:52,740 --> 01:30:56,160
Dave, and I have some ideas. So
we know the timeline is a month,

1409
01:30:56,160 --> 01:30:58,590
something maybe longer,
whatever, there's no rush,

1410
01:30:59,100 --> 01:31:02,070
there's no payroll, all we need
to do is keep the servers

1411
01:31:02,070 --> 01:31:05,730
running and keep a keep us sane.
And I'm looking at you in

1412
01:31:05,730 --> 01:31:10,560
particular Dave, make sure you
take your days off. And so

1413
01:31:10,560 --> 01:31:16,080
please 12 Plenty of bt 12 d3,
please consider supporting the

1414
01:31:16,080 --> 01:31:20,610
open and freely available and
just beautiful project that is

1415
01:31:20,610 --> 01:31:24,930
the podcast index podcast
index.org There's a Donate

1416
01:31:24,930 --> 01:31:29,460
button there and I'm I'm gonna
get a BTC pay server or

1417
01:31:29,490 --> 01:31:33,570
lightning link on there. I've
been playing around. We've got a

1418
01:31:33,570 --> 01:31:38,940
full node now I'm I'm learning
lightning and Bitcoin and it's

1419
01:31:38,940 --> 01:31:42,660
been fun just to watch bits fly
around and understand how this

1420
01:31:42,660 --> 01:31:45,420
stuff works, which is the
opposite of everything you've

1421
01:31:45,420 --> 01:31:49,140
learned about money. But once
you understand digital money, oh

1422
01:31:49,140 --> 01:31:51,300
my god, it's a whole new
ballgame.

1423
01:31:51,780 --> 01:31:54,420
You keep explaining it to me and
I keep forgetting it to five

1424
01:31:54,420 --> 01:31:55,410
minutes after you explain it.

1425
01:31:56,520 --> 01:31:59,790
Alright, Dave, I'll let you get
back to your Friday. You you

1426
01:31:59,790 --> 01:32:02,760
work in today. Are you the
office? Yeah, I'm on lunch break

1427
01:32:02,760 --> 01:32:06,270
right now. Well, okay. You have
10 minutes. Perfect. Don't wait

1428
01:32:06,270 --> 01:32:12,090
10 minutes. You're an hour late.
Jones pushing the timecard Hey,

1429
01:32:12,090 --> 01:32:14,670
Dave, have a great weekend, man.
It's always a pleasure to update

1430
01:32:14,670 --> 01:32:17,460
and get a board meeting out of
you. Yeah, you too, man. Have a

1431
01:32:17,460 --> 01:32:20,100
good weekend. Everybody. Thank
you so much. Make sure you

1432
01:32:20,100 --> 01:32:22,620
propagate. Let everybody know
about the podcast. We'll be back

1433
01:32:22,620 --> 01:32:26,430
next week for another edition of
podcasting 2.0