1
00:00:00,000 --> 00:00:05,040
podcasting 2.0 for October
30 2020 This is episode nine and

2
00:00:05,040 --> 00:00:15,120
here come the pioneers kind of
like the Pilgrims a couple of

3
00:00:15,120 --> 00:00:20,430
ships sailing across the big
podcast ocean everybody is is

4
00:00:20,460 --> 00:00:26,700
he's wrong holiday monetarily
podcasting? 2.0 You know, I

5
00:00:26,730 --> 00:00:30,510
didn't even have a cool intro
name for you today. Gosh darn

6
00:00:30,510 --> 00:00:33,030
it, ladies and gentlemen, Dave
Jones, everybody.

7
00:00:33,480 --> 00:00:37,590
Nice. Okay, because like if this
was like Good Morning Vietnam.

8
00:00:37,590 --> 00:00:41,190
Yeah. I'm like that little. I'm
like that little, you know, like

9
00:00:41,190 --> 00:00:46,170
mealy mouthed guy, the corporate
guy that nobody likes. No, no,

10
00:00:46,170 --> 00:00:49,290
no, no, no, no. You told her it
doesn't matter. Because we're

11
00:00:49,290 --> 00:00:51,420
all going to end up by the way
this week is going we're all

12
00:00:51,420 --> 00:00:57,210
going to end up on substack.
Anyway, charging $5. You know,

13
00:00:58,350 --> 00:01:02,310
I'm very excited about Glenn
Greenwald leaving the intercept.

14
00:01:02,340 --> 00:01:07,170
And I am too. And I think I've
gotten a lot of emails already

15
00:01:07,170 --> 00:01:10,620
from people saying, Hey, man,
you really got to help Glenn out

16
00:01:10,620 --> 00:01:13,260
because, you know, his audio
sucks. He's gonna be doing a lot

17
00:01:13,260 --> 00:01:16,680
more podcasting. Like, I don't
know if I can help him with

18
00:01:16,680 --> 00:01:20,670
everything, but we can certainly
help him with some things. And

19
00:01:20,670 --> 00:01:25,290
that's substack thing though. If
you think about it. I love I

20
00:01:25,290 --> 00:01:31,620
love numbers. It's I think the
default option is $50 a year.

21
00:01:32,520 --> 00:01:37,680
That's the that's the default
subscription level they have on

22
00:01:37,680 --> 00:01:45,210
sub stack. So he has to move.
He's probably making half a

23
00:01:45,210 --> 00:01:48,240
million dollars. Where was
making half a million dollars.

24
00:01:48,240 --> 00:01:51,270
We have to move 10,000 people to
pay. I think he's got that

25
00:01:51,270 --> 00:01:51,900
audience.

26
00:01:52,380 --> 00:01:55,320
I think he's got that easy. i He
got me yesterday, within five

27
00:01:55,320 --> 00:01:55,800
minutes. I

28
00:01:55,800 --> 00:01:59,640
mean, I subscribe. I pay for it.
I did the $50 option I did same

29
00:01:59,640 --> 00:02:02,280
for Matt Taibbi, these are two
of the best journalists. I know.

30
00:02:02,280 --> 00:02:03,450
I love those guys.

31
00:02:04,590 --> 00:02:07,170
That's what that's what I posted
this morning. I'm like, if if I

32
00:02:07,170 --> 00:02:09,450
hope no more journalists keep
going to substack because I'm

33
00:02:09,450 --> 00:02:12,420
gonna go broke. I mean, I got
it. You feel like you got to

34
00:02:12,420 --> 00:02:14,670
support these guys. I mean, as
soon as they say, Hey, I'm

35
00:02:14,670 --> 00:02:17,940
getting screwed. And I gotta go
independent to keep my you know,

36
00:02:18,540 --> 00:02:22,170
to keep my integrity. Oh, yeah,
you're getting my five bucks. I

37
00:02:22,170 --> 00:02:25,230
mean, that's automatic. Yeah.
And then I'll cut off whatever

38
00:02:25,230 --> 00:02:27,690
other stupid discussion I don't
even know about anymore. But you

39
00:02:27,690 --> 00:02:29,100
know, and slot it over there.

40
00:02:29,160 --> 00:02:31,860
If only we had a way to manage
that better. Don't have to

41
00:02:31,860 --> 00:02:37,200
think. Think about that. Dave,
how's your week been man?

42
00:02:38,010 --> 00:02:40,620
Busy. It's been it's been busy.

43
00:02:41,940 --> 00:02:45,870
And I should point out that both
Dave and I have actual jobs like

44
00:02:45,900 --> 00:02:50,250
I think everybody else who hangs
out in podcast index and is

45
00:02:50,280 --> 00:02:55,530
developing or on the podcast
index dot social, demanding

46
00:02:55,530 --> 00:03:00,780
jobs. So I'm, honestly I'm
amazed that we're all still kind

47
00:03:00,780 --> 00:03:03,600
of standing here. Especially you
I know. I know that your week

48
00:03:03,600 --> 00:03:07,470
started off with a non it it
gig.

49
00:03:09,420 --> 00:03:15,210
Yeah, that that's it's it's it's
funny with it with it. You don't

50
00:03:15,900 --> 00:03:19,920
you don't ever know what's like,
that's part of you don't know

51
00:03:19,920 --> 00:03:23,010
what's coming. It just throw
everything throws you

52
00:03:23,010 --> 00:03:27,240
curveballs. And so you always
have to be, you know, you've got

53
00:03:27,240 --> 00:03:30,780
your regular it, which is just
day to day operations and all

54
00:03:30,780 --> 00:03:34,950
these kinds of things. Yeah. And
then at any moment, you know, it

55
00:03:34,950 --> 00:03:38,070
doesn't have to be just a crash.
It could just be like, Oh, crap,

56
00:03:38,100 --> 00:03:42,480
I gotta deal with this. You get
we get one of those every two,

57
00:03:42,480 --> 00:03:44,040
three days, you know? So

58
00:03:44,490 --> 00:03:48,630
usually, for me, it's like,
computer crash. That's, that's a

59
00:03:48,630 --> 00:03:52,650
disaster when I have a computer
issue. Oh, yeah. Here's a

60
00:03:52,650 --> 00:03:56,580
question for you. Whenever I
reboot my Surface Pro six, which

61
00:03:56,580 --> 00:04:00,450
I use for the studio
exclusively, even if it's an

62
00:04:00,480 --> 00:04:04,530
update, I think it'll come back
up it'll blue screen and it'll

63
00:04:04,530 --> 00:04:11,310
tell me the error is I RQL is
not less or equal than and then

64
00:04:11,310 --> 00:04:15,780
it tells me it's it's gathering
some important information with

65
00:04:15,780 --> 00:04:18,210
a little percentage counter and
then it reboots and then it's

66
00:04:18,210 --> 00:04:18,630
fine.

67
00:04:19,650 --> 00:04:22,230
That's that sounds like standard
Windows behavior to

68
00:04:22,229 --> 00:04:25,709
me. Oh, that's that's what it's
supposed to be. Okay. Yeah, it's

69
00:04:25,709 --> 00:04:29,249
a Microsoft product. It wasn't
nice little smiley face at least

70
00:04:29,249 --> 00:04:32,099
didn't go to blue screen with
the smiley and a QR code is very

71
00:04:32,099 --> 00:04:32,399
hip.

72
00:04:33,390 --> 00:04:35,910
That's insulting. That's
insulting to me. Don't give me a

73
00:04:35,910 --> 00:04:40,710
smiley face when you Is it okay.
It's a surface, pro or surface

74
00:04:40,710 --> 00:04:41,100
go

75
00:04:41,130 --> 00:04:44,670
down. This is Surface Pro six.

76
00:04:45,089 --> 00:04:50,429
Okay, so it's a Surface Pro.
It's a self. It is a it is a

77
00:04:50,429 --> 00:04:56,369
self contained device. You can't
add anything to it. You can't

78
00:04:56,369 --> 00:05:01,889
put cards in it. You can't put
RAM In it, you can't swap hard

79
00:05:01,889 --> 00:05:05,699
drives, there's nothing you can
do on the inside of this device.

80
00:05:06,179 --> 00:05:12,989
It's built by Microsoft. And the
hardware, and the software is

81
00:05:12,989 --> 00:05:17,729
built by Microsoft. And they're
sold together all as a as a

82
00:05:17,729 --> 00:05:23,699
package. So, and somehow, it
blue screens every time you boot

83
00:05:23,699 --> 00:05:27,269
it. Yeah, and our q not less
than or equal, that is a drug

84
00:05:27,299 --> 00:05:32,069
that is a driver that is 99% of
the time and driver issue. So

85
00:05:32,069 --> 00:05:35,249
Microsoft has a self contained
unit that they sold to you that

86
00:05:35,249 --> 00:05:38,399
they cannot write same drivers
for.

87
00:05:39,330 --> 00:05:43,290
Well, to be fair, I have a lot
of crap hanging off of this

88
00:05:43,290 --> 00:05:47,670
machine. You know, I got two
monitors hanging off of it.

89
00:05:47,970 --> 00:05:51,630
external hard drive and audio
interface. Yeah,

90
00:05:51,660 --> 00:05:55,800
you're you're you're triggering
my my rant session here. Because

91
00:05:56,880 --> 00:06:01,890
all right, if you go back, and
you know, I do, I don't a much

92
00:06:01,890 --> 00:06:06,630
call it full spectrum it work
from as a day as my day job.

93
00:06:06,630 --> 00:06:10,530
It's it's everything from you
know, server, server stuff,

94
00:06:10,800 --> 00:06:14,970
software development, help the
end user Help Desk. I mean,

95
00:06:14,970 --> 00:06:18,420
there's nothing that is off
limits in my job, if it's

96
00:06:18,420 --> 00:06:24,840
plugged into a wall. I touch it,
right. And so as part of the end

97
00:06:24,840 --> 00:06:33,000
user, stuff, like if you go back
1010 years ago, and we end you

98
00:06:33,000 --> 00:06:36,750
plug in dual monitors, triple
monitors, or whatever that stuff

99
00:06:36,750 --> 00:06:42,180
was rocks. It worked. It worked
every single time it did one

100
00:06:42,180 --> 00:06:42,480
play,

101
00:06:42,540 --> 00:06:48,240
or once we brought in HDMI got
tricky. or USB C or USB. That's

102
00:06:48,240 --> 00:06:49,620
the real problem. Yeah. Oh, it's

103
00:06:49,650 --> 00:06:53,760
all USBC and and Thunderbolt and
DisplayPort. Right windows,

104
00:06:54,120 --> 00:06:56,910
which are all kind of flavors of
the same thing. Yeah. When they

105
00:06:56,910 --> 00:07:00,990
brought that stuff in, multi
monitor went berserk. Yeah. And

106
00:07:00,990 --> 00:07:04,860
you can't at like, I mean, you
can't plug into monitors

107
00:07:04,860 --> 00:07:08,820
anymore, and be assured that
they're gonna work. Yeah. And

108
00:07:08,820 --> 00:07:11,700
like, we took a step backwards
here. That's why, you know, I

109
00:07:11,700 --> 00:07:14,160
always ran on this, like with
self driving cars, and those

110
00:07:14,160 --> 00:07:19,110
customers like, Yeah, show me.
Yeah, sure. We can even plug

111
00:07:19,110 --> 00:07:20,220
into monitors.

112
00:07:21,330 --> 00:07:23,820
I'm still waiting for my
refrigerator to order the milk

113
00:07:23,820 --> 00:07:25,500
automatically. Yeah, yeah.

114
00:07:25,560 --> 00:07:29,070
Yeah, we can't plug into
monitors and make it work. And

115
00:07:29,070 --> 00:07:31,740
you can't get your card
Bluetooth to connect every time

116
00:07:31,740 --> 00:07:35,040
that you're going to have the
car drive. For me. That is some

117
00:07:35,070 --> 00:07:36,240
big time BS.

118
00:07:36,300 --> 00:07:41,400
So this kind of leads me into a
topic for today. Because a lot

119
00:07:41,400 --> 00:07:47,760
of these things, I think are
developed in vacuums. Yeah, we

120
00:07:47,760 --> 00:07:50,520
have testers and there's all
kinds of stuff. But it's so I

121
00:07:50,520 --> 00:07:53,700
mean, so hard to create
something, certainly if it's

122
00:07:53,700 --> 00:07:57,930
software based, and understand
all the use cases and how people

123
00:07:57,930 --> 00:08:02,670
are going to do stuff with your
software. And this became so

124
00:08:02,670 --> 00:08:09,780
apparent to me this week, it was
a big aha moment. Tools. Yeah.

125
00:08:09,780 --> 00:08:15,180
So the he, I'll give you the
high level assessment. And then

126
00:08:15,990 --> 00:08:21,540
let me start with that. What I'm
feeling is, we've had a decade

127
00:08:21,990 --> 00:08:26,010
of lack of innovation in
podcasting, for a number of

128
00:08:26,010 --> 00:08:33,930
reasons. The main one being that
this was usually driven by the

129
00:08:34,110 --> 00:08:38,550
companies that create RSS feeds,
seeing as they have the most

130
00:08:38,550 --> 00:08:44,160
invested in creating additional
functionality that they can

131
00:08:44,160 --> 00:08:49,170
offer to their customers, their
podcasters. The chicken in the

132
00:08:49,170 --> 00:08:56,040
egg was that the app developers,
and let's just say, Apple,

133
00:08:56,070 --> 00:08:59,010
because that's really, that's
really what this has been about,

134
00:08:59,010 --> 00:09:03,150
because they were also not just
a popular app to use for

135
00:09:03,150 --> 00:09:06,690
podcast, but they were also
maintaining the index, the

136
00:09:06,690 --> 00:09:11,580
default index for most. And now
later, Spotify has been added to

137
00:09:11,580 --> 00:09:17,280
that. It's been a question of,
well, we want to add this, and

138
00:09:17,280 --> 00:09:20,070
will you guys get on board with
it? And then of course, you

139
00:09:20,070 --> 00:09:23,640
know, you have all kinds of what
we've seen go into very fast,

140
00:09:23,670 --> 00:09:27,990
very fast tempo with with a
namespace of podcast index, or

141
00:09:27,990 --> 00:09:31,950
at least on the GitHub, never
got anywhere because it would

142
00:09:31,950 --> 00:09:35,070
just be a back and forth and a
meeting and the end, the most

143
00:09:35,070 --> 00:09:39,930
egregious part, although not
anyone's fault, per se, is the

144
00:09:39,930 --> 00:09:44,460
users were completely left out
of the conversation. Yeah, sure.

145
00:09:44,490 --> 00:09:48,360
The people in the conversation
also have podcasts. But here I

146
00:09:48,360 --> 00:09:54,570
am, and this was it was very
frustrating. I'm a co founder of

147
00:09:54,570 --> 00:09:59,580
the project. We we've put this
together to combat a whole bunch

148
00:09:59,580 --> 00:10:05,760
of issues. To move podcasting
forward, we come to an

149
00:10:05,760 --> 00:10:10,230
agreement, not even agreement,
but we're working on chapters

150
00:10:10,440 --> 00:10:14,550
and chapters is already
supported. The whole reason that

151
00:10:14,970 --> 00:10:17,730
was it, who was already
supporting chapters out of the

152
00:10:17,730 --> 00:10:18,570
gate was that?

153
00:10:20,520 --> 00:10:22,410
Well, the apps on the App side,
yeah,

154
00:10:23,010 --> 00:10:26,190
hyper capture. So hyper, and I
think podcasts

155
00:10:26,460 --> 00:10:29,910
are maybe podcast attic, head to
head has got it in beta. And

156
00:10:29,910 --> 00:10:32,040
then Martin was working on it in
pot,

157
00:10:32,070 --> 00:10:35,820
right. So this is working, I
mean, the work is being done.

158
00:10:36,120 --> 00:10:40,260
And now it's the kind of the
reverse. So everyone's sitting

159
00:10:40,260 --> 00:10:46,080
around testing with one feed,
that has some that has a chapter

160
00:10:46,110 --> 00:10:51,750
tag in there with a JSON file,
linked by a URL. And that JSON

161
00:10:51,750 --> 00:10:56,940
file has the has the chapter
markers in it. And I'm like,

162
00:10:56,970 --> 00:11:02,400
holy crap, this is so cool. I
want to use this. Because when I

163
00:11:02,400 --> 00:11:07,170
use this, this is my thinking,
when I use this, I can say, on

164
00:11:07,170 --> 00:11:10,110
my show, or I have several of
them where a lot of people

165
00:11:10,110 --> 00:11:14,010
listen a lot, I think, in
aggregate, maybe a million

166
00:11:14,010 --> 00:11:19,260
people on a weekly basis, I say,
oh, man, I've got this cool new

167
00:11:19,260 --> 00:11:23,160
feature, check it out. If your
app doesn't have it, then check

168
00:11:23,160 --> 00:11:28,350
it out on hyper cat, your pod
friend or podcast addict, which

169
00:11:28,350 --> 00:11:34,410
I think in my mind, would make
everybody happy. Because they're

170
00:11:34,440 --> 00:11:37,440
developing apps, they want the
apps to be used, they want

171
00:11:37,440 --> 00:11:41,130
people to use the apps because
of the art that is created with

172
00:11:41,130 --> 00:11:44,610
that, you know, the the way it's
laid out, that's per individual

173
00:11:44,610 --> 00:11:46,860
developer, that's very
different. And there's a new

174
00:11:46,860 --> 00:11:52,710
feature. I am a what people
think it's very rare case, I

175
00:11:52,710 --> 00:11:57,660
don't really think so. But I do
not have a hosting company. I

176
00:11:57,720 --> 00:12:02,400
know because of the size of the
amount of traffic that we push,

177
00:12:02,640 --> 00:12:06,510
we have our own little CDN,
which void zero maintains up

178
00:12:06,510 --> 00:12:09,690
there and north of the
Netherlands and it's through

179
00:12:09,690 --> 00:12:13,680
ova. Ah, so we've built our own
little CDN. And I create my

180
00:12:13,680 --> 00:12:17,010
feeds with the freedom
controller, which you built. And

181
00:12:17,430 --> 00:12:19,830
we were at this point where I'm
like, Oh, my God, this, we can

182
00:12:19,830 --> 00:12:22,440
really push this forward.
Because the way I look at the

183
00:12:22,440 --> 00:12:28,020
situation, as a user, and I'm a
podcaster, with an audience is

184
00:12:28,740 --> 00:12:33,480
if I'm using this, and people
like it, and there's apps for

185
00:12:33,480 --> 00:12:38,760
it, it would be a much easier
call for a hosting company to

186
00:12:38,760 --> 00:12:43,050
retool, I understand what goes
into it. I have my non developer

187
00:12:43,050 --> 00:12:46,500
voice lots of times, but I I
really do understand what goes

188
00:12:46,500 --> 00:12:50,400
into creating this stuff,
certainly at scale. And if you

189
00:12:50,400 --> 00:12:55,650
have if you're, you know, a
company that's like most are

190
00:12:55,650 --> 00:12:58,710
just struggling to get by just
trying to make it all work for

191
00:12:58,710 --> 00:13:03,060
everybody. Yeah, that would
drive that adoption with some

192
00:13:03,090 --> 00:13:09,930
assuredness that, you know that
that it would, it would be used,

193
00:13:09,930 --> 00:13:13,470
because if I'm using it, other
podcasters, look at what I'm

194
00:13:13,470 --> 00:13:17,370
doing. And they'll say, oh, wow,
this is great. So I thought that

195
00:13:17,370 --> 00:13:21,030
I was in the perfect position
until I realized, well,

196
00:13:21,030 --> 00:13:24,870
actually, here's how it went. We
did our show on last Friday. And

197
00:13:24,870 --> 00:13:27,720
I said, Dave, I know what you're
working on. You got a whole

198
00:13:27,720 --> 00:13:31,320
bunch of crap. Don't worry about
the feed. Because the previous

199
00:13:31,320 --> 00:13:34,860
two episodes, you were hand
coding the feed and changing

200
00:13:34,860 --> 00:13:39,210
things. Which takes a long time.
And I foolishly said to myself,

201
00:13:39,240 --> 00:13:42,150
I used to do this shit. Don't
worry about it. Give me this

202
00:13:42,150 --> 00:13:46,140
give me a text editor. I'll take
care of this. Yeah, yeah. Until

203
00:13:46,140 --> 00:13:51,390
I then realize how much the data
in a feed has changed. I mean,

204
00:13:51,390 --> 00:13:54,090
back in the day, we we didn't
have to escape characters. And

205
00:13:54,090 --> 00:13:57,120
we weren't even thinking about
that. And then Oh, my God,

206
00:13:57,660 --> 00:14:04,320
there's like, the the margin for
error was so. So narrow, I mean,

207
00:14:04,410 --> 00:14:07,470
you know, you screw up one thing
in the feed. Now I have

208
00:14:07,470 --> 00:14:10,860
experienced with screwing up my
feed a lot of it. And it's very,

209
00:14:10,860 --> 00:14:15,330
very painful. When I screw up a
feed, I will be answering emails

210
00:14:15,330 --> 00:14:18,570
and having people tweet at me
for days, if not weeks,

211
00:14:18,570 --> 00:14:23,370
sometimes. And to this day. Oh,
where are the images in the

212
00:14:23,370 --> 00:14:26,610
podcast? 2.0 Feed where the
images the older no agenda

213
00:14:26,610 --> 00:14:31,290
images. How come there's two
episode 1286? Well, I can tell

214
00:14:31,290 --> 00:14:36,570
you feed shit ain't easy. But
here I am, arguably a pioneer,

215
00:14:36,870 --> 00:14:40,620
ready to do stuff. And
everyone's going like, Well,

216
00:14:41,220 --> 00:14:45,060
yeah. And I mean, literally,
that's the noise. I got back and

217
00:14:45,060 --> 00:14:46,080
I was there. As you could tell

218
00:14:46,080 --> 00:14:48,480
this story guy on the screen and
I didn't even know how to read.

219
00:14:49,350 --> 00:14:49,830
I was

220
00:14:49,830 --> 00:14:53,820
flipping out. I'm like, I
desperately want to party I want

221
00:14:53,820 --> 00:14:56,970
to play in this playground. And
so

222
00:14:57,000 --> 00:14:59,430
you were flipping out. You call
he called me and you're like,

223
00:14:59,550 --> 00:15:02,040
you're like What the hell am I
supposed to do? I don't know.

224
00:15:02,130 --> 00:15:05,070
It's like I want to use chapters
is sitting right there. And I

225
00:15:05,070 --> 00:15:08,640
got asked the can do it. And I,
like there's no tool. How do I

226
00:15:08,640 --> 00:15:09,810
create a chapter? Yeah,

227
00:15:09,810 --> 00:15:11,220
how do I create a chapter file?

228
00:15:11,490 --> 00:15:13,410
How do I get it into the feed
once I've created?

229
00:15:13,440 --> 00:15:17,790
Exactly. So this chicken in the
egg is stopping right now. And I

230
00:15:17,910 --> 00:15:25,110
will say, Martin, pod pod
friend, Martin. Thank you. Thank

231
00:15:25,110 --> 00:15:28,590
you. Thank you from the bottom
of my heart. I'm gonna be

232
00:15:28,590 --> 00:15:32,820
transparent as we always are. We
offered to pay Martin to do

233
00:15:32,820 --> 00:15:37,080
this. Because I realized it's
not a not a, it's not

234
00:15:37,230 --> 00:15:40,890
necessarily benefiting his own
development, to create something

235
00:15:40,890 --> 00:15:44,580
so that I can just manage the
feed and put in the cool

236
00:15:44,580 --> 00:15:48,240
elements that y'all are working
on. And he refused. He said, No,

237
00:15:48,240 --> 00:15:50,820
no, no, no, no, there'll be none
of that. But that's that's how

238
00:15:50,820 --> 00:15:55,440
desperate I was to get a tool
just just to be able to do it.

239
00:15:55,440 --> 00:16:00,150
And he went on a marathon 48
hour hackathon and came to us

240
00:16:00,150 --> 00:16:04,080
did his and he did and came up
with the RSS builder. And I am,

241
00:16:04,650 --> 00:16:09,750
I am deeply, deeply grateful,
really, so grateful for that.

242
00:16:09,990 --> 00:16:14,160
Because now and I'm expecting,
you know, with every new element

243
00:16:14,160 --> 00:16:19,230
that we all agree works, that
everyone works together, I think

244
00:16:19,230 --> 00:16:22,170
the code is up or will be up, I
think you already put it up. So

245
00:16:22,170 --> 00:16:26,010
we can add these little
elements. And I can help test

246
00:16:26,010 --> 00:16:30,300
because I can I can push and
make these features surface for

247
00:16:30,300 --> 00:16:33,810
a large enough audience, I think
that it matters, then the and

248
00:16:33,810 --> 00:16:37,320
the audience that I have is
very, very willing to experiment

249
00:16:37,320 --> 00:16:39,990
etcetera. So now

250
00:16:40,020 --> 00:16:43,080
that that's important, too,
because it's, it's, it's much

251
00:16:43,320 --> 00:16:47,460
easier to have the only way you
could test one of the ways you

252
00:16:47,460 --> 00:16:51,510
could have one feed with a ton
of users. And you could test

253
00:16:51,510 --> 00:16:54,990
that. Or you could have a whole
bunch of feeds with a few users.

254
00:16:55,170 --> 00:16:59,430
And that's chaos. It's one feed
that you can use as a tests and

255
00:16:59,430 --> 00:17:03,930
as a sandbox feed to test with
that has potentially, you know,

256
00:17:04,230 --> 00:17:08,640
maybe on the sandbox feed 20,000
users or more, that's gold.

257
00:17:08,730 --> 00:17:13,650
Yes. And I think by and this is
recommendation we got from a

258
00:17:13,650 --> 00:17:18,420
mutual acquaintance, to actually
Mark No, so my, my, the feed

259
00:17:18,420 --> 00:17:22,440
right now is just sandbox. And
it's a separate feed. And we're

260
00:17:22,440 --> 00:17:25,050
doing that for a very specific
reason. And actually gonna go

261
00:17:25,050 --> 00:17:28,500
back Say what you will about
Dave Weiner. But when we were

262
00:17:28,500 --> 00:17:33,210
booting up podcasting 16 years
ago, these features would be

263
00:17:33,210 --> 00:17:37,200
implemented into my feed
creation software on the spot

264
00:17:37,200 --> 00:17:41,640
almost, or the next day. And of
course, that was because he had

265
00:17:41,640 --> 00:17:44,100
a very different model, he was
creating a single piece of

266
00:17:44,100 --> 00:17:48,420
software, a tool that spit out
an RSS feed admit did many other

267
00:17:48,420 --> 00:17:52,200
things. But it was spit out the
RSS feed. So every everything we

268
00:17:52,230 --> 00:17:56,490
we were talking about or want to
try, we pretty much implemented

269
00:17:56,490 --> 00:18:00,990
real world right away. And I
really hope all developers,

270
00:18:02,070 --> 00:18:06,120
especially our app, guys
understand how valuable it is to

271
00:18:06,120 --> 00:18:11,790
get the real users using your
stuff in a controlled

272
00:18:11,790 --> 00:18:15,360
environment to start with, but
go live as soon as possible.

273
00:18:15,360 --> 00:18:19,530
Now, I'm going to toot my own
horn, I am the perfect guy for

274
00:18:19,530 --> 00:18:23,940
you. Because I am fearless. I
will go and I will break Yes, I

275
00:18:23,940 --> 00:18:27,060
will break my feet not on
purpose. But if it comes to

276
00:18:27,060 --> 00:18:31,500
that, I'll break my feet. And
for sure, guaranteed, as Dave

277
00:18:31,500 --> 00:18:35,370
Jones is my witness, I will
break your software. And I and I

278
00:18:35,370 --> 00:18:38,700
succeeded right away, I
immediately broke hyper capture.

279
00:18:39,960 --> 00:18:43,860
And, and I'm happy and I'm like,
Oh, this is so good. And I hope

280
00:18:44,700 --> 00:18:48,300
that everyone sees how valuable
this is because you're thinking,

281
00:18:48,690 --> 00:18:51,630
Well, you know, going to who
knew that I was going to create

282
00:18:51,630 --> 00:18:58,110
20 Chapter marks in my chapter
file and bring up webpages that

283
00:18:58,140 --> 00:19:01,830
apparently are loading
simultaneously. Now, I have an

284
00:19:01,830 --> 00:19:06,420
iPhone seven, for a number of
reasons security, mainly, I

285
00:19:06,420 --> 00:19:08,820
don't want a lot of the new
features and the new sensors.

286
00:19:09,780 --> 00:19:14,010
But it also may be a good
benchmark just to have shit

287
00:19:14,010 --> 00:19:17,430
work. It can work on an iPhone
seven, you're not going to have

288
00:19:17,430 --> 00:19:21,390
a problem with a 12. And the
same goes for Android. There's

289
00:19:21,390 --> 00:19:25,920
there's all kinds of limitations
to me, I think. And then even

290
00:19:25,920 --> 00:19:29,520
though the stuff was out, and
actually kind of released the

291
00:19:29,520 --> 00:19:33,270
hyper catcher stuff. We all sat
down and went hey, you know

292
00:19:33,270 --> 00:19:36,600
that's actually kind of a
security issue if Adam can just

293
00:19:36,600 --> 00:19:39,390
have shit loading up on
everybody's on everybody's

294
00:19:39,390 --> 00:19:42,570
phone. Just have some random
page. That could be a real

295
00:19:42,570 --> 00:19:47,580
problem. tracking, tracking. I
mean, there are definitely web

296
00:19:47,580 --> 00:19:50,940
pages that will crash your
iPhone. You know, we've all seen

297
00:19:50,940 --> 00:19:54,690
it. Yeah, call Apple right away.
Yeah, here's the number you

298
00:19:54,690 --> 00:19:57,420
know, it takes over your whole
your whole browser. You can't do

299
00:19:57,420 --> 00:20:02,070
anything can get out of it. So
I'm super excited that we can

300
00:20:02,070 --> 00:20:06,750
move forward now in this manner.
And so this show today, I'm

301
00:20:06,750 --> 00:20:10,200
going to run it through the RSS
builder, I'm going to add

302
00:20:10,200 --> 00:20:16,170
chapters to it. And I already
have feedback because now we get

303
00:20:16,170 --> 00:20:20,880
into the next part, which is
very interesting is, so now I

304
00:20:20,880 --> 00:20:27,390
have a tool for the RSS feed.
And I'm, I haven't I don't care

305
00:20:27,390 --> 00:20:30,390
what I build my RSS feed with.
But now at least I have a tool

306
00:20:30,390 --> 00:20:35,640
that is flexible enough. So when
a new a new feature comes out,

307
00:20:35,640 --> 00:20:37,890
something we all want to
support, and we're putting into

308
00:20:37,890 --> 00:20:41,430
the apps that the hosting
companies will look at and

309
00:20:41,430 --> 00:20:45,840
decide if they want to use we
can do it right away. But yeah,

310
00:20:46,560 --> 00:20:50,430
here's the first problem. So I
now have one authoring tool, and

311
00:20:50,430 --> 00:20:55,980
I'm very pleased with it hyper
capture, super pleased to have

312
00:20:55,980 --> 00:20:59,760
has to be more chapters you're
talking about, yeah, four

313
00:20:59,760 --> 00:21:03,960
chapters. Exactly, yeah. And
this brings me to my next point,

314
00:21:03,960 --> 00:21:07,740
and then I'll shut up. And I was
trying to make this point, and I

315
00:21:07,740 --> 00:21:12,870
don't think it came across very
well. But in today's world, and

316
00:21:12,870 --> 00:21:17,070
the best example of this is
Microsoft Word. When someone

317
00:21:17,070 --> 00:21:19,950
sends you a Word document, you
open it up in Word, and you read

318
00:21:19,950 --> 00:21:24,180
it. And when you create a Word
document, you open up Word, and

319
00:21:24,180 --> 00:21:26,820
you create it in Word, and then
you check it and you view it in

320
00:21:26,820 --> 00:21:29,520
Word, and it has a couple
different modes. So you can you

321
00:21:29,520 --> 00:21:34,860
know, look at it different ways
and and run some bug checking on

322
00:21:34,860 --> 00:21:39,060
it, which is called a spell
checker in in my world, and then

323
00:21:39,060 --> 00:21:45,270
you can send it off. Never has
anyone complete, I'm sure people

324
00:21:45,270 --> 00:21:48,450
have thought of it. But never
has anyone completed the full

325
00:21:48,450 --> 00:21:55,680
circle of well, editing my
podcast, how it's going to look

326
00:21:55,680 --> 00:22:00,960
what information is displayed in
a podcast app. It would be an

327
00:22:00,960 --> 00:22:04,530
I'm not asking for this. But
just think of the power. If we

328
00:22:04,530 --> 00:22:08,400
could do that in the app itself.
Because that was the experience

329
00:22:08,400 --> 00:22:11,760
I had with hyper capture. Hyper
capture allowed me to do one

330
00:22:11,760 --> 00:22:15,420
thing, which blew me away, is I
could create the chapters while

331
00:22:15,420 --> 00:22:21,840
listening to the show in the
app. That is incredible. I mean,

332
00:22:21,840 --> 00:22:24,810
it's just It's massive. Now I
know that David created it

333
00:22:24,810 --> 00:22:27,840
because he wants community
chapters, which believe me, I

334
00:22:27,840 --> 00:22:30,960
want, because I'm already
thinking, wow, this adds 30

335
00:22:30,960 --> 00:22:33,210
minutes to my production time,
you know, finding these

336
00:22:33,210 --> 00:22:37,050
chapters, I want a community
chapter system where the

337
00:22:37,050 --> 00:22:39,840
producers of my shows can go
ahead and do that. And it will

338
00:22:39,840 --> 00:22:43,800
grow over time. And of course,
you need to an admin interface

339
00:22:43,830 --> 00:22:47,340
to approve that. But that just
keep that in mind. It is

340
00:22:47,340 --> 00:22:52,230
incredibly powerful to be able
to do things to your podcast, in

341
00:22:52,230 --> 00:22:55,620
the app itself as a as a as a
creator, as a producer.

342
00:22:56,340 --> 00:22:59,520
You're talking about wiziwig for
podcast apps,

343
00:22:59,730 --> 00:23:05,730
in a way, in a way I mean so
well, where it's really

344
00:23:05,730 --> 00:23:10,560
prevalent, where really where it
really works well is in the A's

345
00:23:10,560 --> 00:23:15,240
with the chapters, but I can see
another use case. And the more I

346
00:23:15,390 --> 00:23:17,760
because someone showed up on the
index, I forgot who it was on

347
00:23:17,760 --> 00:23:20,580
the mastodon and said, Hey, I
was thinking of putting together

348
00:23:20,580 --> 00:23:26,340
a little podcast app that looks
at where you are by geolocation

349
00:23:26,340 --> 00:23:32,700
and then pulls up podcasts that
are geo tagged in your area. And

350
00:23:32,880 --> 00:23:36,150
now, of course no one has that
at this point. It's not an

351
00:23:36,150 --> 00:23:40,530
official tag. But I can
certainly see the benefit of it.

352
00:23:41,010 --> 00:23:47,010
And if there was a world where I
could add a location tag from

353
00:23:47,010 --> 00:23:49,350
the app itself, you know, my
phone actually has all that

354
00:23:49,350 --> 00:23:53,670
stuff built in GPS and
everything. I mean, these are

355
00:23:53,670 --> 00:23:58,650
just super easy things to think
of. Now, that doesn't make it

356
00:23:58,650 --> 00:24:01,350
any easier for a hosting
company. You know, how does that

357
00:24:01,350 --> 00:24:04,470
get in all problems that need to
be solved? I'm just putting it

358
00:24:04,470 --> 00:24:09,300
out there as a revolutionary
idea. Certainly when it comes to

359
00:24:10,020 --> 00:24:14,070
community based features, it
comments the same thing. You

360
00:24:14,070 --> 00:24:19,710
know, podcasting is getting its
ass kicked its ass kicked by

361
00:24:19,830 --> 00:24:25,290
real time chats on YouTube. Now,
once you go back, you watch the

362
00:24:25,290 --> 00:24:29,280
video again, you see the chat
scroll by that's that's cool

363
00:24:29,280 --> 00:24:35,820
stuff. And we have very, we
actually have zero audience

364
00:24:35,880 --> 00:24:41,070
interaction pieces, mainly. And
this is to finalize, because we

365
00:24:41,070 --> 00:24:45,840
haven't been able to create this
entire loop. And I feel really

366
00:24:45,840 --> 00:24:48,870
good at the end of this week,
because now I know that we are

367
00:24:48,900 --> 00:24:54,780
in. We are formidable. We've got
we've got great app developers

368
00:24:54,960 --> 00:24:58,290
working within the framework of
a namespace coming up with these

369
00:24:58,290 --> 00:25:02,040
features. They'll be able to
test it Good testbed with me and

370
00:25:02,040 --> 00:25:05,160
then real world with me, which
will bring other people who want

371
00:25:05,160 --> 00:25:07,920
to do this. And we'll all make
decisions if we want other

372
00:25:07,920 --> 00:25:11,460
people to use this tool. But you
know, all it takes is one

373
00:25:11,580 --> 00:25:14,940
hosting company to say, Okay,
we're going to change it and,

374
00:25:15,180 --> 00:25:18,150
you know, at boys be ready.
Because yeah, because you know,

375
00:25:18,150 --> 00:25:22,770
stuff is gonna start coming in.
So long story short, let's

376
00:25:22,770 --> 00:25:26,460
remember that users in this
process, and I am here, I am

377
00:25:26,460 --> 00:25:31,320
dedicated I am a part of the
development team, call me QA,

378
00:25:31,350 --> 00:25:36,300
call me Q, call me whatever you
want. But I am going to break

379
00:25:36,300 --> 00:25:39,840
your software, I'm going to do
crazy shit that will drive you

380
00:25:39,840 --> 00:25:42,960
nuts. And we're going to have
great, great features and

381
00:25:42,960 --> 00:25:44,460
functionality because of it.

382
00:25:44,879 --> 00:25:47,939
Yeah, well, what you're talking
about? I mean, what you're

383
00:25:47,939 --> 00:25:52,439
describing is the is actually
what you need to have a

384
00:25:52,439 --> 00:25:58,019
comprehensive test setup for any
kind of software. Yeah, because

385
00:25:58,079 --> 00:26:02,969
as developers go, I'm sure that
everybody you know, I'm sure

386
00:26:02,969 --> 00:26:06,689
every other developer is like
me, as I hear you describe,

387
00:26:07,049 --> 00:26:10,859
okay, what I need is, is, is a
piece of software that does

388
00:26:10,889 --> 00:26:16,019
this, and this and this. And as
I'm hearing it, I'm envisioning

389
00:26:16,289 --> 00:26:19,379
the pieces as they go together
in order just to make it

390
00:26:19,379 --> 00:26:25,409
function. But just simply
functioning is not what makes

391
00:26:25,409 --> 00:26:29,759
great software. No, it is what
makes great software is is

392
00:26:29,759 --> 00:26:33,449
functioning it has to function
at what it's supposed to do. And

393
00:26:33,449 --> 00:26:39,449
it's also got to do it in a way
that is enjoyable, and easy. And

394
00:26:39,449 --> 00:26:41,909
all of these intangibles that
you can't,

395
00:26:42,420 --> 00:26:45,720
you can't you can't dream up.
Yeah, you can't dream

396
00:26:45,720 --> 00:26:51,600
up code this, this that's
enjoyable, or delightful, or

397
00:26:51,600 --> 00:26:52,350
whatever. Well, yes.

398
00:26:52,350 --> 00:26:58,140
Now there's, you can 10 print
Hello, 20. Go to 10. Okay,

399
00:26:58,140 --> 00:27:00,660
that's just always gets me

400
00:27:03,210 --> 00:27:04,530
to hell go to hell,

401
00:27:05,100 --> 00:27:05,820
exactly.

402
00:27:06,870 --> 00:27:11,010
Like you, you can't. So what you
need is you need a you needed,

403
00:27:11,040 --> 00:27:15,030
you need the developer sitting
there thinking those things. But

404
00:27:15,030 --> 00:27:19,470
then you also need a non
developer who's trying to just

405
00:27:19,470 --> 00:27:24,480
simply use it. And who is
breaking it? And who's telling

406
00:27:24,480 --> 00:27:29,280
you, hey, this thing is really
awkward, or yes, technically it

407
00:27:29,280 --> 00:27:33,720
worked. I created this chapters
file. But I tried to actually

408
00:27:33,720 --> 00:27:38,130
load it in the app, and it took
10 minutes to load, right isn't

409
00:27:38,550 --> 00:27:42,990
like, you have to have both
sides of that coin, because it's

410
00:27:42,990 --> 00:27:45,450
the back and forth between the
two that actually make great

411
00:27:45,450 --> 00:27:49,560
software. So I think like,
that's, that's what I hear. And

412
00:27:49,560 --> 00:27:53,490
I know that that's a deficiency
of me, because you can't, not

413
00:27:53,490 --> 00:27:56,760
only can you not properly debug
and debug your own software, I

414
00:27:56,760 --> 00:28:01,560
mean, thoroughly debug it, you
can't, you also can't look at it

415
00:28:01,590 --> 00:28:07,650
with non developer eyes. Sure.
It's just you can't you can't do

416
00:28:07,650 --> 00:28:12,000
that. Because your, your mind
won't let you because you're

417
00:28:12,000 --> 00:28:16,050
thinking, make it work, make it
work, find the find the thing

418
00:28:16,050 --> 00:28:20,070
that's causing it not to work.
And so, like there's times when,

419
00:28:20,880 --> 00:28:26,970
like if people notice that go
dark for a little while, and

420
00:28:26,970 --> 00:28:31,530
don't respond to things. It's
usually because I'm having to,

421
00:28:32,640 --> 00:28:35,130
you know, take care of take care
of something and and I'm trying

422
00:28:35,130 --> 00:28:39,090
to just get my mind away from
podcast index and away from all

423
00:28:39,090 --> 00:28:44,550
that stuff. Sure. And, and go,
you know, clear my mind so that

424
00:28:44,550 --> 00:28:48,390
I can come back to it, and then
look at it with fresh eyes. And

425
00:28:48,420 --> 00:28:53,070
that it doesn't always work. But
you have to try. Because that's

426
00:28:53,070 --> 00:28:54,510
the only way you get good
software.

427
00:28:54,660 --> 00:29:00,270
Now what I was super pleased by
and which told me a lot is the I

428
00:29:00,270 --> 00:29:04,950
feel incredible speed at which
hosting companies have

429
00:29:04,950 --> 00:29:10,110
implemented the lock tag. That
went very fast. Now I know

430
00:29:10,110 --> 00:29:13,680
there's not a lot of logic
behind it. Although just having

431
00:29:13,890 --> 00:29:17,640
a toggle that says yes, lock my
feed. There's logic there. I get

432
00:29:17,640 --> 00:29:21,750
it. That went now how fast like
three to two, three weeks, and

433
00:29:21,750 --> 00:29:25,020
we have six or seven different
companies supporting it.

434
00:29:25,710 --> 00:29:28,530
Yeah, it's it was it was a low
hanging fruit.

435
00:29:29,340 --> 00:29:32,070
I think it's I think it's all
low hanging fruit personally, I

436
00:29:32,070 --> 00:29:35,340
think it's all just sitting
there waiting to be captured and

437
00:29:36,480 --> 00:29:41,070
well, well, Kevin from posted on
the message on the other day in

438
00:29:41,070 --> 00:29:43,920
response to something. I forgot
what he was responding to, but

439
00:29:43,920 --> 00:29:48,300
he actually printed out what he
said because he said at the end

440
00:29:48,300 --> 00:29:52,560
of the day podcast creators want
to see their photo and A's DS

441
00:29:52,560 --> 00:29:56,040
talking about the host the host
tags. Yeah, the contributor

442
00:29:56,040 --> 00:29:58,770
contributing or whatever we're
calling it. At the end of the

443
00:29:58,770 --> 00:30:02,250
day podcast creators want See
their photo and guests photos

444
00:30:02,250 --> 00:30:05,520
within the apps while episodes
are being played? That's really

445
00:30:05,520 --> 00:30:09,390
interesting. I said, I think
that's the use case, we need to

446
00:30:09,390 --> 00:30:13,500
design for closed platforms like
Apple already have this, we need

447
00:30:13,500 --> 00:30:17,250
an open spec that offers
something similar, nothing more

448
00:30:17,250 --> 00:30:23,400
and nothing less. felt that was
perfect. That that is exactly

449
00:30:23,400 --> 00:30:28,320
what is going on right now.
Because I don't know that. Maybe

450
00:30:28,320 --> 00:30:32,640
we see it a little clearly, I'm
being presumptuous here. Maybe

451
00:30:32,640 --> 00:30:38,430
we don't. But perhaps we see
things because we're not in the

452
00:30:38,430 --> 00:30:43,380
hosting business or the app
business. Sure. Sure, sure. And

453
00:30:43,380 --> 00:30:46,860
it's possible that what we're
seeing is maybe something that

454
00:30:46,860 --> 00:30:50,850
has not really sunk in yet. But
if you get back to the what were

455
00:30:50,850 --> 00:30:54,990
the clips we listened to last
week, the the silo companies

456
00:30:54,990 --> 00:30:58,680
like Spotify, and Amazon and
these people that are trying to

457
00:30:58,680 --> 00:31:04,230
bring things exclusive. This,
especially Spotify, they are

458
00:31:04,230 --> 00:31:09,000
trying to build a full complete
stack end to end user experience

459
00:31:09,000 --> 00:31:11,280
that is completely within their
system. Yes.

460
00:31:11,280 --> 00:31:15,660
And this This is, this is
exactly what I wanted to wear. I

461
00:31:15,660 --> 00:31:20,460
wanted to steer it because we
are in a race in a way. However,

462
00:31:20,700 --> 00:31:27,120
I do want to make note. And I
completely believe Kevin. When

463
00:31:27,120 --> 00:31:30,960
Apple was about to launch this
feature, they were making a big

464
00:31:30,960 --> 00:31:35,010
deal about it internally. I have
no, honestly no one from Apple

465
00:31:35,040 --> 00:31:38,700
podcasts has spoken to me since
we started this project. But

466
00:31:38,700 --> 00:31:43,560
they used to email me and said,
Yeah, we're launching this

467
00:31:43,830 --> 00:31:48,870
hosting. So can you please give
us pictures? And I don't see it

468
00:31:48,870 --> 00:31:51,510
in the app. I have the Apple
app. Where is it? Where's my

469
00:31:51,510 --> 00:31:55,680
picture? Where's this?
Fantastic. I don't understand

470
00:31:55,680 --> 00:31:58,860
the functionality. I gave it to
them. It may show up if you

471
00:31:58,860 --> 00:32:03,360
search somewhere. I mean, I can
I can look but where is it? How

472
00:32:03,360 --> 00:32:05,130
is it being used as my question?

473
00:32:05,669 --> 00:32:11,939
I see that. That's a great
point. Because, as you you

474
00:32:11,939 --> 00:32:15,689
mentioned, I think you mentioned
on the agenda not too long ago

475
00:32:15,689 --> 00:32:18,179
about your mentioned the the
Mises Institute, which I think

476
00:32:18,179 --> 00:32:19,859
you pronounced at Mises.

477
00:32:19,860 --> 00:32:24,030
Yes. Thank you. Mises Institute.
Yes, yes, yes, we gotcha. But

478
00:32:24,090 --> 00:32:24,750
they're here,

479
00:32:24,750 --> 00:32:28,590
but they're here in Auburn,
Auburn, Alabama, which is about

480
00:32:28,590 --> 00:32:32,820
two hours away from me. And I
remember, I used to listen to a

481
00:32:32,820 --> 00:32:35,790
ton of their material. And one
of the I remember this one

482
00:32:35,790 --> 00:32:40,140
lecture, where it may have been
Tom woods, actually. Now, I

483
00:32:40,140 --> 00:32:42,180
don't think it was him. But
anyway, he said, the lecture

484
00:32:42,180 --> 00:32:46,650
said, you know, a, he's talking
about antitrust, and he said, a

485
00:32:46,650 --> 00:32:55,710
small player, a small business
person can can out maneuver a

486
00:32:55,710 --> 00:33:00,210
large business any day of the
week. And they were growing,

487
00:33:00,210 --> 00:33:04,110
because you can always the small
business guy can always, you

488
00:33:04,110 --> 00:33:10,830
know, he can, he can trim his
expenses, he can, he can eat one

489
00:33:10,830 --> 00:33:15,420
fewer meals a day. I mean, like,
there's a lot that he or she can

490
00:33:15,420 --> 00:33:19,710
do in order to free up the
resources in order to make some

491
00:33:19,710 --> 00:33:23,760
sort of move and make it very
quickly. Whereas a large company

492
00:33:23,910 --> 00:33:27,420
that you know, you, you have to
have a certain amount of

493
00:33:27,420 --> 00:33:31,200
revenues or manage cash flow, it
takes a long time to steer that

494
00:33:31,200 --> 00:33:37,290
boat in another direction. So I
think that base that a small

495
00:33:37,290 --> 00:33:41,340
focus group of developers doing
this, this namespace were

496
00:33:41,340 --> 00:33:43,410
much more and much more nimble.
Yeah,

497
00:33:43,440 --> 00:33:47,340
we can move like we can move on
this host guests stuff much

498
00:33:47,340 --> 00:33:48,870
faster. Okay, in a big cup.

499
00:33:48,870 --> 00:33:52,470
So let me let's, now we're,
we're doing chapters at the same

500
00:33:52,470 --> 00:33:55,140
time, I'm not stopping on
chapters, because there's still

501
00:33:55,140 --> 00:33:59,520
work to be done, particularly
how we create chapters. Let's

502
00:33:59,520 --> 00:34:03,600
talk about the host and guest.
So this is the Apple app. It's

503
00:34:03,600 --> 00:34:07,470
updated. Its its newest one. I
know that my photos in there

504
00:34:07,470 --> 00:34:12,000
Jhansi Dvorak photos in there.
It's in their system internally.

505
00:34:12,000 --> 00:34:15,360
So I know that I know that
that's all right. And I searched

506
00:34:15,360 --> 00:34:19,890
for Adam curry in the Apple
podcast app. Now it does that no

507
00:34:19,890 --> 00:34:22,770
point anywhere in the interface
does it bring up my picture his

508
00:34:22,770 --> 00:34:27,450
picture? It shows me a number of
podcasts. And when I look at

509
00:34:27,450 --> 00:34:29,940
this, I think, Oh, this is
really good. Because it first

510
00:34:29,940 --> 00:34:33,870
has no agenda. I'm in that mo
facts. I mean, that Joe Rogan

511
00:34:33,870 --> 00:34:37,830
experience I mean that twice. So
I click on Joe Rogan experience,

512
00:34:38,100 --> 00:34:42,600
and I just get a list of Joe
Rogan experience podcasts with

513
00:34:42,600 --> 00:34:46,170
his most recent episode, why now
this is what I'd want. Why

514
00:34:46,170 --> 00:34:50,160
doesn't it show me the episodes
that I'm on? Because it seems

515
00:34:50,160 --> 00:34:54,780
like a no brainer. You know,
they got no fucking users. No

516
00:34:54,780 --> 00:34:57,720
one is really using this.
They're not listening to people.

517
00:34:57,990 --> 00:35:01,770
Adam Carolla. I've been on that
show one It's Hotep. Jesus, I've

518
00:35:01,770 --> 00:35:06,690
been on that show, Tom woods,
I'm seeing all of it. Even the

519
00:35:06,690 --> 00:35:10,920
buzz cast, there we go. Let me
click on that. It should say,

520
00:35:11,160 --> 00:35:14,880
here's the episode with Adam
curry, but it doesn't. It just

521
00:35:14,880 --> 00:35:17,640
takes you to broadcast, it just
takes you to bus casts. So they

522
00:35:17,670 --> 00:35:21,030
they either I didn't even you
don't even have to use the tag,

523
00:35:21,060 --> 00:35:24,900
you could just search. I mean,
you could, you could, in theory,

524
00:35:24,900 --> 00:35:28,230
just search for a name and show
notes and bring it up to because

525
00:35:28,230 --> 00:35:32,220
I know Netflix and l podcast,
which was on once two and a

526
00:35:32,220 --> 00:35:35,910
half, three years ago. I know
that they're not producing a

527
00:35:35,910 --> 00:35:42,510
tag. I know that Daniel have
hosts and guests in there. So we

528
00:35:42,510 --> 00:35:49,530
have a we have a communication
breakdown. So why don't we as

529
00:35:49,530 --> 00:35:53,040
the Nimble developers, and
sorry, Martin, I know you're not

530
00:35:53,040 --> 00:35:55,920
in the US, but sorry, for all
intents and purposes, you now

531
00:35:55,920 --> 00:35:59,430
are an American entrepreneur,
because America is actually

532
00:35:59,430 --> 00:36:02,040
small business. It's not big
businesses. Yeah, we got some

533
00:36:02,040 --> 00:36:06,150
notable ones. And it's the small
businesses that make up the core

534
00:36:06,150 --> 00:36:12,270
of this country. See, it is the
backbone. So let's work on hosts

535
00:36:12,270 --> 00:36:15,210
and guests tags. And let's make
it kick ass. And let's make our

536
00:36:15,240 --> 00:36:18,540
apps kick ass. Because when I
when I'm searching for Adam

537
00:36:18,540 --> 00:36:22,530
curry, I want to see my face
appear. And then I want to see

538
00:36:22,530 --> 00:36:25,590
what shows I'm on and I want it
to list the actual shows that

539
00:36:25,590 --> 00:36:29,130
I'm on. You can split it up any
way you want it. But just I

540
00:36:29,130 --> 00:36:30,780
mean, what a waste. What a
waste.

541
00:36:30,839 --> 00:36:34,889
I want to and you want to link
to Wikipedia. Yeah.

542
00:36:35,640 --> 00:36:38,580
And I already see some of that
insights, you know, podcast

543
00:36:38,580 --> 00:36:42,930
insights, or some, you know, low
level AI stuff, basically skip

544
00:36:42,930 --> 00:36:45,540
logic people are doing like, Oh,
it's fine to Twitter feed, let's

545
00:36:45,540 --> 00:36:49,350
find a Wikipedia entry. That's
fine. And how about this as a

546
00:36:49,350 --> 00:36:56,310
crazy thought? Why wouldn't it
be possible to add to that? So

547
00:36:56,310 --> 00:37:01,260
if there's a if there's a host
and a guest entry? Are we going

548
00:37:01,260 --> 00:37:04,500
to recreate all that work? I
mean, should guests and hosts

549
00:37:04,500 --> 00:37:07,050
maybe have I'm just throwing
shit out there? Should guests

550
00:37:07,050 --> 00:37:12,600
and hosts maybe not have a way
to have a format that can be

551
00:37:12,600 --> 00:37:15,990
used by all podcasts they appear
on no matter who creates it?

552
00:37:17,580 --> 00:37:20,220
What do you mean? You mean, like
in the mean, like in the tag

553
00:37:20,220 --> 00:37:21,600
itself by the

554
00:37:21,630 --> 00:37:25,470
index? Why Why? Why wouldn't I'm
just throwing stuff out, David.

555
00:37:25,470 --> 00:37:29,970
And just, to me, it's like,
okay, I'm the guest. And all I

556
00:37:29,970 --> 00:37:36,750
provide all I've ever been asked
for is my picture. And I don't I

557
00:37:36,750 --> 00:37:40,950
actually don't want my Wikipedia
link. Can I please give a bio

558
00:37:40,950 --> 00:37:44,850
that I like that I can link to?
Can I please put in the most

559
00:37:44,850 --> 00:37:48,480
recent project. So this is going
to be still how do I change my

560
00:37:48,480 --> 00:37:55,110
picture? Yeah. Now you're now
you're hearing a user talking?

561
00:37:55,770 --> 00:37:58,020
Yeah, well, that's exactly what
you're supposed to hear. I mean,

562
00:37:58,020 --> 00:38:03,690
like, that's the hold on my dogs
freaking out.

563
00:38:03,690 --> 00:38:07,110
Your dog agrees with me, man
that the dog is going Yes. Yes.

564
00:38:07,110 --> 00:38:12,990
drover. Anyway, do you want it
you want to go talk to him? We

565
00:38:12,990 --> 00:38:18,060
can wait. We can wait for anyone
to talk to him. And while Dave

566
00:38:18,060 --> 00:38:22,980
is doing that, let me see if I
can find developers, developers

567
00:38:22,980 --> 00:38:30,810
developers, because that is got
to be I guess I don't have that

568
00:38:30,810 --> 00:38:36,960
in the archive anywhere. But we
always have the Google

569
00:38:38,520 --> 00:38:42,120
developers, developers,
developers,

570
00:38:42,960 --> 00:38:44,430
developers, developers,
developers. Yeah, I

571
00:38:44,430 --> 00:38:47,130
mean, it's not. It's not like
I'm gonna stop the recording or

572
00:38:47,130 --> 00:38:50,550
anything. Dave, hold on. This is
a classic for those of you who

573
00:38:50,550 --> 00:38:52,140
are too young to have ever heard
it.

574
00:38:52,470 --> 00:38:56,250
developers, developers,
developers, developers,

575
00:38:56,250 --> 00:38:59,400
developers, developers,
developers, developers.

576
00:39:00,480 --> 00:39:07,980
Bomber bomber, yeah. It's a
classic. I'm putting that in the

577
00:39:07,980 --> 00:39:12,420
show notes first. It does not
stop either. It just keeps on

578
00:39:12,420 --> 00:39:15,480
going beautiful. I don't think
I've ever seen that full thing.

579
00:39:15,900 --> 00:39:18,870
Five minutes. Oh, the rant is
five minutes. And he's sweating

580
00:39:18,870 --> 00:39:21,120
like a hog. And it's fantastic.
I remember

581
00:39:21,120 --> 00:39:22,740
that. I remember that. Or
whatever.

582
00:39:25,140 --> 00:39:26,850
It's in there. It's in there
somewhere.

583
00:39:28,200 --> 00:39:32,880
Like that. I think chat to me
chapters is almost fully baked

584
00:39:32,880 --> 00:39:36,000
already. I mean, like, there's
just maybe a couple of well,

585
00:39:36,000 --> 00:39:36,510
interesting.

586
00:39:36,540 --> 00:39:42,060
Okay, here's a feedback on my
end. So. So I have a tool to

587
00:39:43,050 --> 00:39:46,020
have the hyper capture the
regular app, which I can create.

588
00:39:47,190 --> 00:39:52,470
The chapters with. My options
are comment and URL. So we know

589
00:39:52,470 --> 00:39:58,260
that it wasn't a good idea to
just pop up whatever URL was put

590
00:39:58,260 --> 00:40:08,790
in there. So now I either I
either need some logic that

591
00:40:09,060 --> 00:40:14,790
picks up an icon or the first
picture or something to display,

592
00:40:15,090 --> 00:40:18,420
or I need a way to also get a
picture in there.

593
00:40:19,290 --> 00:40:22,230
Yeah, we'll see that's in the
spec. So it may just be that

594
00:40:22,230 --> 00:40:24,510
David has hasn't put it in
there. And maybe there's a way

595
00:40:24,510 --> 00:40:29,370
to, or maybe he's looking,
treating the URL, I'm not sure

596
00:40:29,370 --> 00:40:32,220
what he's doing, he'll have to
clarify that because, like, it's

597
00:40:32,220 --> 00:40:37,080
no chapter. So in a Chapter, you
can specify the chapter spec has

598
00:40:37,380 --> 00:40:41,430
Start Time, which will be the
seconds into the data onto the

599
00:40:41,430 --> 00:40:47,460
audio. And then it has either a
URL of a web of the Assam web

600
00:40:47,460 --> 00:40:51,750
URL or an image URL. So it can
have, you can have either or

601
00:40:51,750 --> 00:40:57,420
both. So you can put in, you
know, an image URL instead of on

602
00:40:57,420 --> 00:41:01,770
a webpage, it'll just load the
image. But I'm not sure if he's,

603
00:41:01,800 --> 00:41:04,890
I'm not sure what his interface
was exposing that.

604
00:41:04,920 --> 00:41:10,410
No, I only have one, one URL
space to put in there. Okay,

605
00:41:10,410 --> 00:41:12,990
well ask him about that, then.
But let me just give you the

606
00:41:12,990 --> 00:41:19,500
next set of problems. Okay. So I
saw I want it to look good. So I

607
00:41:19,500 --> 00:41:22,770
want to have it now. There are
many times I can get an image

608
00:41:23,190 --> 00:41:26,460
and just copy and paste that
image. But some What if I have

609
00:41:26,460 --> 00:41:29,190
an image from my phone that I
want to put in? I'm just

610
00:41:29,190 --> 00:41:33,840
thinking as a user? Now, I gotta
find a place to host that image?

611
00:41:35,640 --> 00:41:37,800
Yeah, like if you're if you're
wanting to upload something

612
00:41:37,800 --> 00:41:38,610
yourself, yeah.

613
00:41:38,730 --> 00:41:42,660
Okay. So these are, these are
tools. And I think this is where

614
00:41:42,660 --> 00:41:47,310
the hosting guys come in. How
are you? How are your users

615
00:41:47,310 --> 00:41:50,190
going to create the content for
these tags?

616
00:41:52,800 --> 00:41:57,210
See that, to me. To me, that's,
that's the perfect role for

617
00:41:57,210 --> 00:41:57,570
them.

618
00:41:57,690 --> 00:42:00,600
It is the perfect, it is the
perfect role. Because

619
00:42:00,600 --> 00:42:02,760
they're already hosts. They're
already hosting things like

620
00:42:02,820 --> 00:42:07,320
transcripts, and feeds and
everything.

621
00:42:07,350 --> 00:42:10,080
I mean, like I mean, another
thing is, I'm just going to keep

622
00:42:10,080 --> 00:42:15,630
hammering on this transcripts.
Okay. How do I do it? I mean,

623
00:42:15,960 --> 00:42:19,770
I've gotten some answers. And
the answers are, well, you do it

624
00:42:19,770 --> 00:42:21,870
through this, and you run it
through that, and then you put

625
00:42:21,870 --> 00:42:24,540
it on a server and you put the
URL here.

626
00:42:27,300 --> 00:42:29,040
That's not something grandma can
do.

627
00:42:29,310 --> 00:42:36,180
It's not something I can do. I
mean, I can. But I'm so so. So

628
00:42:36,210 --> 00:42:40,800
someone's supporting transcripts
right now. Is that Is there

629
00:42:40,800 --> 00:42:41,490
support for that?

630
00:42:41,490 --> 00:42:45,480
Yeah. Buzzsprout. Yeah, Buzz
press supporting it?

631
00:42:45,660 --> 00:42:48,360
And do they have a tool for
creating the order? They just

632
00:42:48,360 --> 00:42:52,710
create the transcripts on the
fly? Or they

633
00:42:52,770 --> 00:42:57,780
don't know how they do it in
their UI. Okay, that's, I've

634
00:42:57,780 --> 00:43:00,030
created an account the other day
to see if I could do it, and

635
00:43:00,030 --> 00:43:02,700
then never followed through on
it. But I don't know. I don't

636
00:43:02,700 --> 00:43:06,120
know how they're exposing it. I
know. I think they read. I think

637
00:43:06,120 --> 00:43:09,930
they redirect you. Man, I don't
want to say because I don't know

638
00:43:10,170 --> 00:43:15,570
it. Like, it seems like here's
the problem with transcripts.

639
00:43:17,250 --> 00:43:22,320
With with the chain of getting
them into your feed, is that you

640
00:43:22,320 --> 00:43:25,890
have you have potentially, they
cost money. First of all, it

641
00:43:25,890 --> 00:43:29,880
costs money on almost every
service to do if you're going to

642
00:43:29,880 --> 00:43:33,600
do more than just a little bit
like if you have a three hour

643
00:43:33,600 --> 00:43:37,470
show, it's going to cost you I
don't know at least three bucks

644
00:43:38,070 --> 00:43:41,430
to three bucks to create a
transcript for that show. By the

645
00:43:41,430 --> 00:43:44,610
time you run it through their
their engine, and it spits out

646
00:43:45,360 --> 00:43:49,590
usually some sort of JSON file.
It's time encoded, and it's like

647
00:43:49,590 --> 00:43:53,670
every single word in the
transcript has a timecode. So

648
00:43:53,670 --> 00:43:55,980
it's a fairly sizable file, I
don't know, four or five

649
00:43:55,980 --> 00:44:01,320
megabytes, then you have to take
that and convert it into

650
00:44:01,320 --> 00:44:07,470
something that is more usable by
an app, something that's not

651
00:44:07,470 --> 00:44:14,820
just like your huge monster of
time coded single words. So

652
00:44:15,570 --> 00:44:21,150
there are hurdles as to
transcript to like, it makes

653
00:44:21,150 --> 00:44:24,750
sense that the chain is
complicated. Now, I don't know

654
00:44:24,750 --> 00:44:28,440
how Buzzsprout does that. Now if
if we're doing it, let's just

655
00:44:28,440 --> 00:44:33,570
say I'm gonna run mine through
AWS transcribe service. And it's

656
00:44:33,570 --> 00:44:36,690
going to spit me out a crazy
JSON file. And then I gotta

657
00:44:36,690 --> 00:44:39,870
figure out some way to get that
into a standard podcast

658
00:44:39,870 --> 00:44:41,880
namespace transcript format.

659
00:44:42,390 --> 00:44:47,520
So this is also why things never
get done. Because everyone says,

660
00:44:47,520 --> 00:44:50,340
Well, I'm ready to receive it.
And then the hoster say, I'm

661
00:44:50,340 --> 00:44:55,380
ready to put it in. And in the
middle. You've got users stuck

662
00:44:55,410 --> 00:44:58,410
saying, Okay, how do I do this?

663
00:45:00,000 --> 00:45:04,500
Yeah, well, the perfect, I
think, I think the transcripts

664
00:45:04,710 --> 00:45:08,160
is probably the worst case
scenario of that. And I don't

665
00:45:08,160 --> 00:45:12,540
want, like I said, But
Buzzsprout may have a much

666
00:45:12,540 --> 00:45:14,970
better solution to this than
that. I don't know. I just don't

667
00:45:14,970 --> 00:45:15,150
know.

668
00:45:15,630 --> 00:45:21,510
I see they they support
chapters? Because I put one of

669
00:45:21,510 --> 00:45:27,030
my feeds in there. Maybe it's a
pass through, okay. Yeah, well,

670
00:45:27,030 --> 00:45:29,340
I didn't have a lock tag on it.
So that's the good news.

671
00:45:31,200 --> 00:45:35,850
Maybe it's having an upgrade, I
will upgrade my feed, to see

672
00:45:35,850 --> 00:45:40,230
maybe I get transcripts in
there. But maybe it's premium

673
00:45:40,230 --> 00:45:44,130
feature, could be a premium
feature. But just looking at the

674
00:45:44,130 --> 00:45:47,700
so here, we have transcripts, or
Nina chapters, and they have a,

675
00:45:48,240 --> 00:45:52,050
this is actually quite usable.
They have ADD chapter markers.

676
00:45:52,440 --> 00:45:59,100
So So I hit that. And I can add,
well, the start times have a

677
00:45:59,100 --> 00:46:01,650
little player, so that all works
automatically. That's great. I'd

678
00:46:01,650 --> 00:46:05,610
love to use this, then it has a
chapter title and a URL. So it

679
00:46:05,610 --> 00:46:09,510
does not have an option for a
URL and a picture. That's

680
00:46:09,510 --> 00:46:09,870
interesting.

681
00:46:09,870 --> 00:46:12,780
So that's, so that's hyper
catcher and both both have that

682
00:46:12,780 --> 00:46:17,040
same sort of interface. And I
wonder if they're just because

683
00:46:17,280 --> 00:46:21,510
because in the spec, there is an
image property and an A in an in

684
00:46:21,510 --> 00:46:27,300
a URL property. So they, Tom and
Kevin and David, they, they need

685
00:46:27,300 --> 00:46:29,460
to tell us how to use that.

686
00:46:30,570 --> 00:46:34,530
Well, we're Yeah, I mean, to me
as as a as, let's call it my

687
00:46:34,530 --> 00:46:39,720
hosting provider in this case,
it would make sense to me that I

688
00:46:39,720 --> 00:46:44,190
can either grab an image from
somewhere and just drop it in

689
00:46:44,190 --> 00:46:48,000
there, and it uploads to my area
of my server space on

690
00:46:48,000 --> 00:46:54,420
Buzzsprout. And adjust does
everything else for me? Yeah. So

691
00:46:54,420 --> 00:46:57,510
and I understand the that. I
mean, so there's two use cases.

692
00:46:57,510 --> 00:47:00,510
One is the one that I don't
like, which is and that's just

693
00:47:00,510 --> 00:47:03,090
me, personally, I want people to
listen to my show, and I don't

694
00:47:03,090 --> 00:47:05,520
want you jumping around and I
don't want to see something

695
00:47:05,520 --> 00:47:07,980
that's Oh, well, I'm not going
to listen to this bit. I'm going

696
00:47:07,980 --> 00:47:11,310
to that bit. Which means I feel
you that's just my art, you

697
00:47:11,310 --> 00:47:15,000
know, it's like I would rather
people listen to it in linear

698
00:47:15,000 --> 00:47:18,000
fashion. I also don't like
people listening at one and a

699
00:47:18,000 --> 00:47:23,310
half times speed, you know,
that's just me. However, I would

700
00:47:23,310 --> 00:47:27,390
like to use this as eye candy,
the way it's being implemented

701
00:47:27,420 --> 00:47:31,080
in hyper capture. And I think
pod friend, is your you're

702
00:47:31,080 --> 00:47:36,180
listening, you get to a certain
point and up pops, whoa, here's

703
00:47:36,180 --> 00:47:40,170
a cool thing. Here's an image
and there's a URL, I can tap and

704
00:47:40,170 --> 00:47:44,790
go through. So we talked about
artwork on our show. And we're

705
00:47:44,790 --> 00:47:47,340
talking about artwork that we
did not choose for the album

706
00:47:47,340 --> 00:47:50,760
art, I want to rotate that. And
here's this, this is the perfect

707
00:47:50,760 --> 00:47:53,280
use case for me. Here's this
one. Here's that one. And that's

708
00:47:53,280 --> 00:47:56,310
not meant for you to tap through
to anything. It's also not meant

709
00:47:56,310 --> 00:47:59,970
to jump to it per se, I don't
mind how if people want to jump

710
00:47:59,970 --> 00:48:01,740
around. I mean, that's it is
what it is.

711
00:48:02,880 --> 00:48:05,580
Well, that's something that
evolved into the chapter spec

712
00:48:05,580 --> 00:48:11,490
this past week is we've been? Oh
gosh, it's hard to even remember

713
00:48:11,490 --> 00:48:14,910
what has happened in this in the
week. Because I think early on,

714
00:48:14,910 --> 00:48:17,940
I made contact with the
developer of a program called

715
00:48:17,940 --> 00:48:23,790
chapters app. And it's a Mac
program that will create mp3

716
00:48:23,790 --> 00:48:31,440
chapters in your mp3 file. And,
but his his software will also

717
00:48:31,440 --> 00:48:37,980
at the same time, spit out a
JSON Chapter format. And so I

718
00:48:37,980 --> 00:48:42,510
started looking at his JSON
chatra format. And it was so

719
00:48:42,510 --> 00:48:45,150
close to what we had. I mean,
like the properties were named

720
00:48:45,150 --> 00:48:48,450
the same. In a lot of instances.
I mean, it the format was just

721
00:48:48,450 --> 00:48:51,600
almost identical. So I made
contact with him. Frederick

722
00:48:52,200 --> 00:48:56,640
Buurman, I think is how you
pronounce his last name. And I

723
00:48:56,640 --> 00:48:59,310
made contact with him said, Hey,
your your format is so close to

724
00:48:59,310 --> 00:49:04,500
ours, this would be huge when if
we just combined, what if we

725
00:49:04,500 --> 00:49:07,380
merge these two formats
together? If it's not two in a

726
00:49:07,380 --> 00:49:10,800
way, that's not too painful for
you, not too painful for us. And

727
00:49:10,800 --> 00:49:13,080
we each have to just make a
couple of tweaks. And we have

728
00:49:13,080 --> 00:49:16,950
one single format that your your
users can go ahead and spit out

729
00:49:16,950 --> 00:49:20,220
a chapters file that will work
in the podcast namespace. He

730
00:49:20,220 --> 00:49:23,190
said, Yeah, that sounds great.
Exactly. Perfect. Perfect. Yeah.

731
00:49:23,220 --> 00:49:25,830
So it was perfect synergy. So we
pulled that we pulled that

732
00:49:25,830 --> 00:49:29,520
together this past week. And
he's cool with it. We're good

733
00:49:29,520 --> 00:49:34,740
with it. Very little change for
anybody to absorb. But the one

734
00:49:34,740 --> 00:49:38,010
thing that came in there was was
an extra property optional

735
00:49:38,010 --> 00:49:41,640
property called Table of
Contents or TOC, which is

736
00:49:41,640 --> 00:49:43,620
something he was using, but we
didn't have it and it was a

737
00:49:43,620 --> 00:49:48,030
great idea. So that you can
choose to have a silent chapter.

738
00:49:48,750 --> 00:49:52,860
So you have a chapter marker.
That doesn't show as Yes. Is

739
00:49:52,860 --> 00:49:55,350
that in the spec now? It is in
the spec? Yes.

740
00:49:55,410 --> 00:49:56,760
I love that.

741
00:49:57,180 --> 00:50:00,000
Yeah. So you can put your images
in there. They'll just work

742
00:50:00,000 --> 00:50:04,110
rotate, but it's not a jump
point. You know, it's just like

743
00:50:04,110 --> 00:50:07,650
a slideshow at that point and
you just see it. Uh huh. Yeah.

744
00:50:07,650 --> 00:50:10,800
And that I mean, you can have a
pot, you could have a podcast of

745
00:50:10,830 --> 00:50:15,360
all silent chapters where things
just are shown to you. But there

746
00:50:15,360 --> 00:50:20,130
are, there's no jump points at
all. That's all Dino. So now

747
00:50:20,130 --> 00:50:22,890
that we have that option, that's
a perfect scenario.

748
00:50:23,669 --> 00:50:27,059
So what what is the best way? So
this? So this is very

749
00:50:27,059 --> 00:50:30,839
interesting. This is now
implemented in in two, possibly

750
00:50:30,839 --> 00:50:34,229
three or four different places?
What is the best way to move

751
00:50:34,229 --> 00:50:37,409
this forward? Because now we
have a scenario where it's

752
00:50:37,439 --> 00:50:41,549
almost there. But it's not quite
to spec. Now, this is granted,

753
00:50:41,549 --> 00:50:45,209
this is something that has just
started happening. Yeah. How do

754
00:50:45,209 --> 00:50:48,929
we how do we move this forward?
Because I have a use case, I

755
00:50:48,929 --> 00:50:52,469
think it's a good use case. For
that use case to work, I need

756
00:50:52,469 --> 00:51:01,229
three extra things. In, in, in
whatever I'm using to create the

757
00:51:01,229 --> 00:51:07,199
chapters with, I need to be able
to put an image in addition to a

758
00:51:07,199 --> 00:51:13,079
URL, that image has to be hosted
somewhere. And I would like to

759
00:51:13,109 --> 00:51:18,089
have to add the silent, no
chapter mark. So how do we get

760
00:51:18,089 --> 00:51:22,019
it from where it is here? to I
mean, I know how it goes at

761
00:51:22,019 --> 00:51:26,159
Spotify. Some guy says, Hey,
we've decided we're going to do

762
00:51:26,159 --> 00:51:29,129
this. Everybody get on it, drop
whatever else you're doing.

763
00:51:29,609 --> 00:51:37,799
Yeah, that's clearly not the way
to work. Martin did. Well, I owe

764
00:51:37,799 --> 00:51:42,269
him. I owe him. I'll DJ your
daughter's Bar Mitzvah,

765
00:51:42,299 --> 00:51:48,269
whatever. Do anything. i Oh, my
Oh, Martin, for sure. Because it

766
00:51:48,269 --> 00:51:51,269
really took us a wave. Look at
the look at what happened, man.

767
00:51:51,839 --> 00:51:54,449
This is great. You did that.
It's great. You did that?

768
00:51:54,449 --> 00:51:59,789
Because that? I mean, it's, it's
great. Because you're, if you

769
00:51:59,789 --> 00:52:02,819
look at podcasts index, the
index to social everybody.

770
00:52:02,819 --> 00:52:06,149
There's a programmer? Yeah.
Everybody, there's a developer,

771
00:52:06,179 --> 00:52:12,179
except you. Really? Yes, maybe
one or two other people. And so

772
00:52:12,209 --> 00:52:17,339
like, if you don't break stuff
and speak up, then the

773
00:52:17,339 --> 00:52:19,769
developers are just gonna keep
on lalalala. You know, just

774
00:52:19,769 --> 00:52:21,929
gonna keep on going about their
business and like pumping out

775
00:52:21,929 --> 00:52:26,189
software that doesn't interop.
And that's no good. It's like, I

776
00:52:26,189 --> 00:52:29,069
think the way forward on this is
simple. You we finalize the

777
00:52:29,069 --> 00:52:35,849
tech, finalize that format, and
we put it now now, I think it

778
00:52:35,849 --> 00:52:39,809
was Kevin, ever Buzzsprout was
saying, because I keep

779
00:52:39,809 --> 00:52:42,449
mentioning bus route, because
they've they've really jumped on

780
00:52:42,449 --> 00:52:47,279
board and are trying to help us
finalize the spec. And so that's

781
00:52:47,279 --> 00:52:49,979
why they're Nikki's coming up a
lot. They've just been hands on,

782
00:52:50,579 --> 00:52:54,029
you know, helping, not just
sitting back and saying, oh,

783
00:52:54,029 --> 00:52:56,099
yeah, we'll do it when you know
when the time comes. But they've

784
00:52:56,099 --> 00:53:00,539
actually taken a hands on
pushing code. So and what he

785
00:53:00,539 --> 00:53:04,409
said was, you know, chapters is
not something that our, that our

786
00:53:04,409 --> 00:53:07,949
users are really calling for,
but we realize it's important,

787
00:53:07,949 --> 00:53:11,639
and we'll we'll support it. And
I knew and I think I said this

788
00:53:11,639 --> 00:53:14,129
early on that I knew that
chapters was going to have to be

789
00:53:14,129 --> 00:53:17,999
something that that I was going
to have to politic for. Because

790
00:53:19,079 --> 00:53:22,979
there are some things that are
not necessarily being asked for

791
00:53:22,979 --> 00:53:27,719
or clamoring for by users. But
you sort of have a vision for

792
00:53:27,719 --> 00:53:35,339
it. And mp3 chapters are good,
because there's really zero

793
00:53:35,339 --> 00:53:38,219
privacy implication. You can
embed everything in there and

794
00:53:38,219 --> 00:53:41,699
it's not it's not a big deal,
but it is a pain in the butt.

795
00:53:41,760 --> 00:53:46,080
Oh yeah. No, it's horrible. No,
I think everything is great. I

796
00:53:46,080 --> 00:53:49,050
mean, I really do. Everything is
great, but we just need to go

797
00:53:49,050 --> 00:53:54,480
through a couple of loops and
Buzzsprout I am now your

798
00:53:54,480 --> 00:54:00,900
customer I am signed up for the
$24 a month plan and now I have

799
00:54:00,900 --> 00:54:06,210
demands Yeah. Now have demands
as a customer I have demands

800
00:54:06,509 --> 00:54:09,239
it's going straight to this
suggestion but we got a we got a

801
00:54:09,239 --> 00:54:10,409
customer one chapters.

802
00:54:10,770 --> 00:54:14,700
Here's something interesting. So
there is no there's nothing

803
00:54:14,730 --> 00:54:17,370
extra that I could find in this
plan doesn't matter because I'm

804
00:54:17,400 --> 00:54:21,090
happy to support them. Under
artists slash there is more

805
00:54:21,090 --> 00:54:24,720
episodes settings. items below
are optional don't have to be

806
00:54:24,720 --> 00:54:27,390
completed. Also some kind of
impacts in higher episode

807
00:54:27,390 --> 00:54:30,120
displays to be sure to
understand what they do before

808
00:54:30,120 --> 00:54:36,180
setting them. And then it has
artists slash guest and already

809
00:54:36,180 --> 00:54:40,920
populated in there's Adam curry
ampersand John C. Dvorak, too. I

810
00:54:40,920 --> 00:54:45,510
doubt an ampersand is a good way
to separate two artists and

811
00:54:45,510 --> 00:54:48,150
guests. I don't know if that's
possible. So

812
00:54:48,569 --> 00:54:53,549
I'm really just pull another
iTunes author tags. Gah, okay,

813
00:54:53,609 --> 00:54:59,969
it's in there as a single
gotcha. I got it. But when the

814
00:54:59,999 --> 00:55:05,039
He, when the contributor tag
gets finalized, we'll, they'll

815
00:55:05,039 --> 00:55:07,319
be able to separate that
logically. Because it'll be

816
00:55:07,529 --> 00:55:09,059
it'll be structured data in the
fee.

817
00:55:09,150 --> 00:55:12,330
Right, which adds a lot of
complexity to what they're

818
00:55:12,330 --> 00:55:13,590
doing. I understand that.

819
00:55:16,379 --> 00:55:24,659
That's, I mean, the whole idea
of having of having the and

820
00:55:24,659 --> 00:55:26,759
that's, I think it caused some
confusion earlier in the week,

821
00:55:26,759 --> 00:55:31,259
because you had, you are calling
for tools. And yeah, and the

822
00:55:31,259 --> 00:55:33,869
hosters, were saying, Well, I
mean, that's what we do. I mean,

823
00:55:33,869 --> 00:55:38,969
we build we build tools. But
there's also a class of a class

824
00:55:38,969 --> 00:55:42,689
of podcaster out there who is
self hosted. And then there's

825
00:55:42,689 --> 00:55:48,929
also podcasters, who are on
hosts that are smaller and

826
00:55:48,929 --> 00:55:51,749
don't, maybe they're, they're
using them because they're

827
00:55:51,749 --> 00:55:54,959
cheaper, or for some reason
other for some unknown reason

828
00:55:54,959 --> 00:55:58,259
that we don't know about. And
they don't have, and they're

829
00:55:58,259 --> 00:56:01,169
just slow, and they're not quick
to adopt, and that kind of

830
00:56:01,169 --> 00:56:03,149
thing. And those, you don't want
to lay those guys out in the

831
00:56:03,149 --> 00:56:07,199
cold either. So the fact the
fact that there's just more

832
00:56:07,199 --> 00:56:11,039
tools is going to make this
thing easier. And I think I

833
00:56:11,039 --> 00:56:15,539
think we can submit it by
finalizing that the chapters tag

834
00:56:15,569 --> 00:56:21,599
this this week. I mean, I think
that's totally doable. And one

835
00:56:21,599 --> 00:56:25,619
of the things that I plan on
doing this weekend is I'm just

836
00:56:25,619 --> 00:56:30,749
going to take a look at the
landscape and do a reorder on

837
00:56:31,199 --> 00:56:34,559
have already had some
discussions with people who have

838
00:56:34,589 --> 00:56:41,129
expressed their ideas about
what, you know, what should be

839
00:56:41,129 --> 00:56:44,219
in phase one, phase two. And I
agree, and I think everybody

840
00:56:44,219 --> 00:56:46,739
pretty much sees the way this is
going. So I'm just gonna go

841
00:56:46,739 --> 00:56:50,399
ahead and reorder everything
into phase one, phase two. And

842
00:56:50,519 --> 00:56:53,759
then we'll just we'll kind of
finalize this homestretch of

843
00:56:53,759 --> 00:56:58,769
phase one is, hey, here's the
three tags that we want to focus

844
00:56:58,769 --> 00:57:01,259
on the most and see if we can
get these things to the finish

845
00:57:01,259 --> 00:57:02,519
line. I think that's

846
00:57:02,550 --> 00:57:05,610
I think that's an excellent,
excellent idea. And I will take

847
00:57:05,610 --> 00:57:12,960
it upon myself, I'm going to
create an account with blueberry

848
00:57:13,020 --> 00:57:17,640
and one with fireside and who
else we have Captivate. Yeah,

849
00:57:17,640 --> 00:57:20,520
transistor transistor, I'll just
create an account with

850
00:57:20,520 --> 00:57:25,050
everybody. And I will, I will
wreak, I will run my feeds

851
00:57:25,050 --> 00:57:30,270
through every system and provide
my feedback. And agree, but the

852
00:57:30,270 --> 00:57:35,550
main thing is, if we have a
namespace that has those

853
00:57:35,550 --> 00:57:39,090
elements in it that we
discussed, I'm going to push for

854
00:57:39,090 --> 00:57:45,960
it to be implemented as such.
Because we know that we have app

855
00:57:45,960 --> 00:57:52,560
developers who are developing to
that spec, but if no one's going

856
00:57:52,560 --> 00:57:56,970
to create them to that spec, we
lose again. Yeah, and every

857
00:57:56,970 --> 00:58:00,690
single time we go through this
loop, Spotify gets one step

858
00:58:00,690 --> 00:58:05,940
closer to just making it, look,
they have years to go. They

859
00:58:05,940 --> 00:58:10,140
really do. I don't believe any
of the hype. I'm not so sure

860
00:58:10,140 --> 00:58:15,390
that they're the cat's meow. in
all regards, they have anchor,

861
00:58:15,390 --> 00:58:20,070
which is a big deal. But we are
very nimble. And I know what it

862
00:58:20,070 --> 00:58:22,590
takes in any corporation no
matter how they come across to

863
00:58:22,590 --> 00:58:29,820
do certain things. And we need
to keep plowing ahead. And and I

864
00:58:29,820 --> 00:58:33,810
can evangelize everything and
anything and get people to use

865
00:58:33,810 --> 00:58:37,950
your apps and go to your
services. But I have to be able

866
00:58:37,950 --> 00:58:38,850
to show it working.

867
00:58:40,140 --> 00:58:42,810
So for another critical play
this piece of the puzzle.

868
00:58:42,839 --> 00:58:47,519
Right. So So I would say with
with deep respect to the

869
00:58:47,519 --> 00:58:50,819
Buzzsprout. Team, you're not
done yet. I know it's just been

870
00:58:50,819 --> 00:58:55,319
finalized. But please consider
revisiting your chapters for

871
00:58:55,440 --> 00:58:58,680
two receptors is not final yet.
It's not finalized yet.

872
00:58:59,670 --> 00:59:02,970
Know what, what is the only
thing is finalized the lock tag,

873
00:59:02,970 --> 00:59:03,960
then as far as I know,

874
00:59:04,200 --> 00:59:07,770
lock, transcripts transcripts is

875
00:59:07,770 --> 00:59:10,950
no there's no apparent way for
me to make that there's no

876
00:59:10,950 --> 00:59:13,620
apparent way in Buzzsprout for
me to add that.

877
00:59:14,610 --> 00:59:18,240
They'll they'll have to let us
then they'll have to pipe in and

878
00:59:18,240 --> 00:59:21,900
tell us what to do. Yeah, I know
that guy. Because I see him. I

879
00:59:21,900 --> 00:59:24,690
see him in the index. We're,
we're aggregating that data now.

880
00:59:24,690 --> 00:59:27,180
And I see Buzzsprout feeds with
transcripts. I just don't know

881
00:59:27,180 --> 00:59:34,530
how to get them in there. So
yeah. And what was the last one?

882
00:59:35,070 --> 00:59:40,020
There's three. I'm drawing a
blank. But anyway, well, there's

883
00:59:40,020 --> 00:59:43,020
three tags are finalists, we
need to we need to finalize, I

884
00:59:43,020 --> 00:59:47,550
think we can get chapters done
this week. That and, you know,

885
00:59:47,550 --> 00:59:52,170
the and a contributor tag. That
also seems very doable. I think

886
00:59:52,170 --> 00:59:55,530
we can get that thing done
definitely by the 15th. We'll

887
00:59:55,530 --> 00:59:55,950
also

888
00:59:56,010 --> 01:00:02,100
and so then, the contributor tag
implementing The tag into two,

889
01:00:02,760 --> 01:00:06,360
just using Buzzsprout and the
RSS builder. I'm pretty sure

890
01:00:06,360 --> 01:00:12,030
I'll be able to do it in the RSS
builder. But then really, how is

891
01:00:12,030 --> 01:00:13,560
it being used?

892
01:00:14,490 --> 01:00:17,940
But I think that's an easy one
to implement on the app side.

893
01:00:18,450 --> 01:00:22,260
And it because it's, I mean,
it'll, it'll just be essentially

894
01:00:23,700 --> 01:00:25,410
just a URL and a name.

895
01:00:25,890 --> 01:00:29,160
Right, right. But in an image,
I'm saying all the all the

896
01:00:29,160 --> 01:00:33,120
things that we were talking
about, how was the app going to

897
01:00:33,120 --> 01:00:38,100
use this? So and I think we've
given a couple of good examples,

898
01:00:38,850 --> 01:00:43,080
just in a basic search. Now, I
don't know if that's the index

899
01:00:43,080 --> 01:00:46,890
or how that works. In a basic
search. If I'm searching for a

900
01:00:46,890 --> 01:00:51,420
guest, then I want to see the
shows that that guest is on, and

901
01:00:51,420 --> 01:00:56,190
specifically the, you know, the
actual episodes. Otherwise, what

902
01:00:56,190 --> 01:01:00,720
did you do for me? That's apple.
And that's, Apple's doing that

903
01:01:00,720 --> 01:01:05,640
stupidly. So we can blow past
Apple just by making that that's

904
01:01:05,640 --> 01:01:06,780
a big feature.

905
01:01:07,350 --> 01:01:10,290
Yeah, I'll start doing that
immediately. I mean, that's that

906
01:01:10,290 --> 01:01:15,090
search, like, as soon as we
aggregate that data in that way,

907
01:01:15,390 --> 01:01:17,910
like, I mean, that's instant
search ability.

908
01:01:17,939 --> 01:01:22,049
So the next to the next part is,
what do I get? How can I

909
01:01:22,049 --> 01:01:27,329
contribute? To help to making
that better? This is a good one.

910
01:01:27,329 --> 01:01:32,669
So what can I do besides just
adding a URL to a picture or, or

911
01:01:32,669 --> 01:01:37,529
a single page? What can I do to
make it better for the apps to

912
01:01:37,529 --> 01:01:40,889
do something with that
information? And and can I

913
01:01:40,889 --> 01:01:45,899
control it to change the
information? I mean, this to me,

914
01:01:45,899 --> 01:01:49,919
is another authoring tool that I
would expect from me or my tool

915
01:01:49,919 --> 01:01:56,489
provider? Is it just a simple
URL to a wiki page? Sure. Seems

916
01:01:56,489 --> 01:01:58,529
kind of sad. That's the best we
can do.

917
01:02:00,300 --> 01:02:05,160
Yeah, well, there's other work
going on, too. I know, I'm just

918
01:02:05,160 --> 01:02:08,160
saying that not chaser, you
know, pot chaser is built,

919
01:02:08,160 --> 01:02:10,500
essentially, if I understand
them, right, they're building a

920
01:02:10,500 --> 01:02:16,530
database of various sort of
verified, as use that term

921
01:02:16,530 --> 01:02:21,630
loosely, because they're just
verified hosts and guests. With

922
01:02:21,810 --> 01:02:24,360
a lot of this information,
they're trying to build almost

923
01:02:24,360 --> 01:02:28,200
like a podcast. I mean, a wiki
itself is what the way I take.

924
01:02:28,230 --> 01:02:33,840
That's interesting. Yeah, and I
mean, like they, they were on

925
01:02:33,840 --> 01:02:39,990
the GitHub comments, saying, you
know, hey, we got this work in

926
01:02:39,990 --> 01:02:44,310
progress. And they may have
released it this week, are not.

927
01:02:45,270 --> 01:02:48,780
But they're going to also have
an API. So there may be a third

928
01:02:48,810 --> 01:02:53,070
party API that can now that can
pull in some information we may

929
01:02:53,070 --> 01:02:57,870
be get, this may be the
beginning of like, the the

930
01:02:57,870 --> 01:03:02,670
industry solving a problem. And
this seems to be happening a lot

931
01:03:02,670 --> 01:03:07,050
with this whole project is the
industry is seeing a problem and

932
01:03:07,050 --> 01:03:10,620
beginning then the motion of
implement of fixing it or

933
01:03:10,620 --> 01:03:14,250
building things around it. And
then now the podcast namespace

934
01:03:14,250 --> 01:03:17,100
can just give it an outlet. So

935
01:03:17,430 --> 01:03:21,870
okay, so here's what I would
recommend, since I I didn't

936
01:03:21,870 --> 01:03:25,950
participate in the conversation
on the GitHub and I, or at all

937
01:03:25,950 --> 01:03:28,230
because I wasn't thinking about
it. I've never cared about it,

938
01:03:28,260 --> 01:03:33,390
because I saw nothing come of
it. If we can at least get to

939
01:03:33,390 --> 01:03:35,940
the point because I'm looking at
pod chaser. They do the same

940
01:03:35,940 --> 01:03:39,300
thing. That was great because
pod chaser does. They do seem to

941
01:03:39,300 --> 01:03:42,270
have a lot of good stuff in
here, which everybody could hook

942
01:03:42,270 --> 01:03:47,100
into. I don't know how people
feel about it about using third

943
01:03:47,100 --> 01:03:53,640
parties. But let's see, they
already integrate with POD rover

944
01:03:53,640 --> 01:03:58,350
pod status. My podcast reviews,
Captivate vote Buzzsprout is

945
01:03:58,350 --> 01:03:58,740
here.

946
01:03:59,610 --> 01:04:01,500
My podcast reviews, that's
Daniel J. Lewis.

947
01:04:02,670 --> 01:04:06,810
So they says they have partial
integration. Okay, that's the

948
01:04:06,810 --> 01:04:09,270
whole lesson. I'm just reading
this some features integrated

949
01:04:09,270 --> 01:04:12,240
with POD chaser. New shows are
able to be submitted to pod

950
01:04:12,240 --> 01:04:16,350
chaser. Okay, pod chaser links
on hosted podcast pages, no pod

951
01:04:16,350 --> 01:04:19,950
chaser ratings displayed no.
Displayed on episode no creator

952
01:04:19,950 --> 01:04:25,200
profiles displayed on? No, this
means so that's kind of worth

953
01:04:25,200 --> 01:04:28,110
looking at. As long as it can as
long as you can have

954
01:04:28,110 --> 01:04:31,920
competition. Yeah, so that
that's not a single point of

955
01:04:31,920 --> 01:04:36,270
failure. But at its very core,
it will be great to be in a

956
01:04:36,270 --> 01:04:45,000
podcast app and say, Adam curry
and it will show me the episodes

957
01:04:45,000 --> 01:04:48,300
of shows where I was listed as a
guest or a host.

958
01:04:48,750 --> 01:04:50,940
Not just the podcast, the
episode itself

959
01:04:50,970 --> 01:04:53,760
the the actual episode itself.
Yeah, yeah.

960
01:04:53,820 --> 01:04:54,990
I mean, I think which

961
01:04:55,110 --> 01:04:59,340
kind of makes sense. Yeah, I
think that's the point of it

962
01:04:59,340 --> 01:04:59,730
all.

963
01:05:00,000 --> 01:05:02,850
That's what everybody wants.
Yeah, that's the one thing

964
01:05:02,850 --> 01:05:06,030
everybody wants. And it sounds
like if we're understanding this

965
01:05:06,030 --> 01:05:10,950
right, Apple has gotten 1% of
the way a stop to the finish

966
01:05:10,950 --> 01:05:12,720
line 80% 80%.

967
01:05:12,720 --> 01:05:15,120
Because they don't even they
don't even surface the picture I

968
01:05:15,120 --> 01:05:15,660
sent him.

969
01:05:15,780 --> 01:05:19,110
Yeah, the picture forgot about
that. We can do this, this can

970
01:05:19,110 --> 01:05:21,810
be better. This can all be
better. I mean, the

971
01:05:21,810 --> 01:05:25,500
decentralized, the building a
decentralized Can, can just work

972
01:05:25,500 --> 01:05:30,330
better? Well, it's not the world
feature. It's not that we're

973
01:05:30,330 --> 01:05:34,770
targeting feature parity is it's
that we're, we're taught, you

974
01:05:34,770 --> 01:05:39,000
know, mutual friend of ours said
that. Yesterday's like, you

975
01:05:39,000 --> 01:05:43,290
know, there's no, it's not
enough to just do what they do.

976
01:05:43,290 --> 01:05:44,010
You got to do

977
01:05:44,100 --> 01:05:47,610
better, better. Yeah, we're
building back better.

978
01:05:48,450 --> 01:05:51,900
Because, because if somebody's
locked into a silo app, yeah.

979
01:05:52,740 --> 01:05:55,320
You want to get them out of the
silo app and back into the open

980
01:05:55,320 --> 01:05:58,890
market. And so like, there's no
reason to do that. If you're, if

981
01:05:58,890 --> 01:06:01,350
it's just like, well, the open
system just has the same stuff

982
01:06:01,350 --> 01:06:01,980
I've got already.

983
01:06:02,280 --> 01:06:04,830
Well, this is perhaps even this
is a better example than

984
01:06:04,830 --> 01:06:08,670
chapters really, because here's
Apple, they've had this for

985
01:06:08,670 --> 01:06:11,970
months and months and months.
They've had this integrated,

986
01:06:11,970 --> 01:06:16,080
they've received my pictures,
they decided, I think, if you

987
01:06:16,080 --> 01:06:20,970
search somewhere on Apple, it'll
show my profile. And it may have

988
01:06:20,970 --> 01:06:23,910
a wiki page link, I recall
something like that. But it's

989
01:06:23,910 --> 01:06:26,550
definitely not surfacing their
app, or at least not any

990
01:06:26,550 --> 01:06:29,430
apparent manner. We can kick
everybody's ass because the

991
01:06:29,430 --> 01:06:32,220
number one thing, the number one
reason for this feature was

992
01:06:32,220 --> 01:06:36,030
exactly that. Oh, my God, I
loved hearing that guy on that

993
01:06:36,030 --> 01:06:40,230
show. Well, you know, where else
is he appearing? I believe that

994
01:06:40,230 --> 01:06:45,690
was the main driver behind the
feature. And what was discussed,

995
01:06:45,690 --> 01:06:49,050
if I recall correctly as well,
you know, a lot of people will

996
01:06:49,260 --> 01:06:54,060
do spammy titles. Like if you
liked Adam curry, you'll love

997
01:06:54,060 --> 01:06:58,320
this episode, you know, that
kind of stuff. But I think if we

998
01:06:58,320 --> 01:07:02,550
have enough fields for, and by
the way, is a room for four

999
01:07:02,550 --> 01:07:04,320
guests, or is it just one guest?

1000
01:07:04,920 --> 01:07:06,120
Now, there's no limit?

1001
01:07:06,180 --> 01:07:08,460
There's no limit to how many
guests tags you put in there.

1002
01:07:08,759 --> 01:07:11,159
There's not a limit to how many
you put in there unless it's

1003
01:07:11,159 --> 01:07:15,269
imposed by the host, which would
they'll they will have to impose

1004
01:07:15,269 --> 01:07:20,339
limits and A's, but there's I
mean, per spec, there's no,

1005
01:07:20,369 --> 01:07:23,309
there's no limit. But I mean,
like an aggregator I'll stop.

1006
01:07:23,849 --> 01:07:27,329
You know, I'll pick up, you
know, five people. And then I'll

1007
01:07:27,329 --> 01:07:29,789
just stop after that. I mean,
I'm not going to pick up 100

1008
01:07:30,179 --> 01:07:31,139
guests. But is this?

1009
01:07:31,290 --> 01:07:33,690
Is this an endpoint you want to
provide?

1010
01:07:35,490 --> 01:07:38,400
Well, it will just get returned
with the with the episode

1011
01:07:38,400 --> 01:07:42,810
results, and then there'll be a
separate search. Which, and I'm

1012
01:07:42,810 --> 01:07:46,770
kind of like we have we have 50
million episodes in the index

1013
01:07:46,770 --> 01:07:51,420
right now. So that's a lot of
data. And I've really held off

1014
01:07:51,420 --> 01:07:56,850
on any sort of episode search,
until we sort of fry this fish.

1015
01:07:56,970 --> 01:08:00,270
Right? Because for that mean for
you, because you want to get

1016
01:08:00,270 --> 01:08:02,370
that right. To start with. Yeah,

1017
01:08:02,490 --> 01:08:11,040
yeah. Cuz because really, I
can't imagine searching 50

1018
01:08:11,040 --> 01:08:14,880
million episodes without having
some indication of what you're

1019
01:08:14,880 --> 01:08:18,840
looking or have something
specific. Right. So he's

1020
01:08:19,110 --> 01:08:21,900
saying guest and then name is
that still?

1021
01:08:23,279 --> 01:08:25,199
No, no, I think that's fine.
Yeah. Surely on the

1022
01:08:25,530 --> 01:08:29,880
purely on the the guest field in
your database, he said simply.

1023
01:08:30,600 --> 01:08:33,330
So that's, that's an easier
search.

1024
01:08:33,780 --> 01:08:36,660
Oh, yeah. I mean, like, that's,
that's very doable. If we have

1025
01:08:36,660 --> 01:08:39,570
that structured data in there,
we can do that. Right very

1026
01:08:39,570 --> 01:08:40,380
quickly. So

1027
01:08:40,410 --> 01:08:43,620
just looking at the way
Buzzsprout has implemented it

1028
01:08:43,620 --> 01:08:46,920
right now, which is why they
have partial integration,

1029
01:08:46,920 --> 01:08:56,910
whatever. Where it's guest slash
host. Host slash guest. Actually

1030
01:08:56,910 --> 01:09:02,760
is so interesting. From just
looking at the regular podcast

1031
01:09:02,760 --> 01:09:06,420
info, it still uses the artists
tag. I know that's an industry

1032
01:09:06,420 --> 01:09:13,050
wide thing. I find that
hilarious. It's what it is.

1033
01:09:14,040 --> 01:09:18,180
We need to have hosters we need
to have them guest on the show.

1034
01:09:18,180 --> 01:09:22,950
Yeah. We next episode, we need
to get hosters in because they

1035
01:09:22,950 --> 01:09:26,400
can show us how to use their
software. Yeah, and yes, because

1036
01:09:26,400 --> 01:09:29,670
I'm probably doing around here
this artist slash guests so

1037
01:09:29,670 --> 01:09:35,700
already. That it's an I'm not
picking on Buzzsprout I love

1038
01:09:35,700 --> 01:09:41,520
these guys. They're going to be
fantastic. It's just this is the

1039
01:09:41,520 --> 01:09:45,690
same everywhere. Everyone's
making these legacy things.

1040
01:09:47,340 --> 01:09:49,890
Like they're they're jumping on
the tag. They're gonna do that.

1041
01:09:49,890 --> 01:09:50,190
No, no,

1042
01:09:50,189 --> 01:09:54,749
I know. But I'm, I'm just
providing the feedback. I'm not

1043
01:09:54,749 --> 01:09:59,969
an artist. It's a small thing.
Oh, yes. Which is a small thing.

1044
01:10:00,359 --> 01:10:06,119
And do I do Adam Currys?
Ampersand Jhansi. Dvorak and

1045
01:10:06,119 --> 01:10:12,179
then slash nothing? Or shouldn't
it be two separate entries? One

1046
01:10:12,179 --> 01:10:17,189
for Adam Curry One for Jhansi,
Dvorak. So these are all things

1047
01:10:17,189 --> 01:10:22,949
that you cannot create, as just
a software developer on the

1048
01:10:22,949 --> 01:10:26,249
index as just a software
developer on the hosting side,

1049
01:10:26,249 --> 01:10:29,279
or is just a software developer
on the app side, this

1050
01:10:29,279 --> 01:10:32,669
conversation that we're having
has to happen. We can't do it in

1051
01:10:32,669 --> 01:10:34,859
our vacuum either. You know,

1052
01:10:34,890 --> 01:10:40,230
this, this was this went from
the the show where we read

1053
01:10:40,230 --> 01:10:44,550
namespaces, to the show where we
describe trying to use software

1054
01:10:44,550 --> 01:10:51,450
on the internet. How beautiful
is this? Let me scroll. Now, I'm

1055
01:10:51,450 --> 01:10:55,200
looking at this text box. I'm
not sure what it means. Yeah,

1056
01:10:55,230 --> 01:11:00,000
it's our quest to get rid of all
of our audiences is Wow, no, I

1057
01:11:00,270 --> 01:11:00,660
see.

1058
01:11:00,719 --> 01:11:04,529
I think there's eight people who
who care. I really do. But

1059
01:11:04,560 --> 01:11:07,650
you want to do you want to thank
them? Do you think that's? Well,

1060
01:11:07,650 --> 01:11:13,050
hold on? Yeah, I just wanted to
say that we are at a beautiful

1061
01:11:13,050 --> 01:11:17,190
point, a beautiful point where
we all understand what's

1062
01:11:17,190 --> 01:11:23,040
happening. And we have this
glue. And, and I want to make it

1063
01:11:23,040 --> 01:11:27,180
even more sticky. So we really
talk to all the players because

1064
01:11:27,180 --> 01:11:31,320
that's what's never happened,
you know? And in the users, I

1065
01:11:31,320 --> 01:11:35,250
don't think they've been in the
conversation, and just makes

1066
01:11:35,250 --> 01:11:37,560
better software. It really does.

1067
01:11:38,010 --> 01:11:40,200
And people are on podcasts
index, not social.

1068
01:11:41,970 --> 01:11:47,820
Well, let me tell you what I can
find. You get stats. Yeah,

1069
01:11:47,970 --> 01:11:56,670
stats. Let me see. Where's my
preferences here? I think gets

1070
01:11:57,390 --> 01:11:59,580
on that one a second. For sure.
Because I

1071
01:11:59,580 --> 01:12:03,990
see new people popping up 170
Nasty new people popping

1072
01:12:03,990 --> 01:12:08,280
up on a fairly regular basis. 80
to active this week. Yeah,

1073
01:12:08,280 --> 01:12:09,120
I mean, that's, that's a

1074
01:12:09,120 --> 01:12:14,040
good. That's not bad. We had 971
interactions this week, whatever

1075
01:12:14,040 --> 01:12:18,210
that means. But luckily,
luckily, I have no backlog jobs.

1076
01:12:18,570 --> 01:12:21,840
What does that mean? That shit
software's what the? What's the

1077
01:12:21,840 --> 01:12:26,310
backlog, Joe? Well, if I click
on it, I get a dashboard. And

1078
01:12:26,370 --> 01:12:30,420
oh, okay. Yeah, this is this is
not for the faint of heart. This

1079
01:12:30,420 --> 01:12:33,990
is, this is probably the
disseration This is a sidekick,

1080
01:12:34,020 --> 01:12:37,860
sidekick. It's the Federation
stuff. Yeah, it's how many

1081
01:12:37,890 --> 01:12:43,500
processes failed and queued. I
love that term. N q not cute,

1082
01:12:43,560 --> 01:12:45,750
and cute, and cute and cute.

1083
01:12:47,280 --> 01:12:49,470
You need to you need to close
that page right now.

1084
01:12:49,500 --> 01:12:53,280
I do want to let us thank some
of the people who have

1085
01:12:53,280 --> 01:12:59,010
enthusiastically supported
podcasts index.org. The this

1086
01:12:59,040 --> 01:13:03,480
podcast that goes with it. The
Mastadon which now has search,

1087
01:13:03,720 --> 01:13:10,560
that was an extra 29 bucks a
month? 2995 Yeah, well, I got to

1088
01:13:10,680 --> 01:13:17,430
if I ordered within 30 minutes.
On TV, as seen on TV. It's this

1089
01:13:17,430 --> 01:13:21,780
is the value for value system.
All we ask for is what value are

1090
01:13:21,780 --> 01:13:26,160
you getting out of the entire
project and put that into time

1091
01:13:26,160 --> 01:13:28,740
talent or treasure or a
combination of all three? Of

1092
01:13:28,740 --> 01:13:31,770
course, we have lots of people
spending time, lots of people

1093
01:13:31,770 --> 01:13:35,100
spending their talent, and so
beautiful to see people

1094
01:13:35,400 --> 01:13:38,040
supporting us with finances
which we need otherwise, you

1095
01:13:38,040 --> 01:13:43,080
know, otherwise it stops
eventually. And I love the

1096
01:13:43,170 --> 01:13:46,920
recurring subscriptions people
getting certain basically buying

1097
01:13:46,920 --> 01:13:51,000
a server space which Yeah, it's
yeah, it's like it's almost it's

1098
01:13:51,000 --> 01:13:55,860
like the other side to the
Amazon Spot Instances. Does that

1099
01:13:55,860 --> 01:13:58,500
make any sense? It's like we
have almost like a balance.

1100
01:13:58,530 --> 01:14:02,730
Yeah, like we we we spin up a
spot instance and there's a $20

1101
01:14:02,730 --> 01:14:05,880
a month offset. It's really
interesting how that works. And

1102
01:14:05,880 --> 01:14:08,790
I love it personally is great.
Like a carbon offset is a

1103
01:14:08,790 --> 01:14:12,600
server. It's a server credit
offset. Yes. Exists server

1104
01:14:12,600 --> 01:14:12,960
credit.

1105
01:14:12,960 --> 01:14:18,630
Yeah. The Yeah. I love that
because we like it only really

1106
01:14:18,630 --> 01:14:23,970
takes. I mean like if if you
have 20 people that do here 25

1107
01:14:23,970 --> 01:14:28,980
People that do $10 a month. It's
done. Like it's really not it's

1108
01:14:29,010 --> 01:14:33,300
it's a low bar. It's so easy.
No, it doesn't mean our hosting

1109
01:14:33,300 --> 01:14:35,640
fees. We intentionally keep them
as low as possible.

1110
01:14:35,670 --> 01:14:38,460
Oh, you're the master. You're
the master of the hosting fees.

1111
01:14:39,780 --> 01:14:45,600
Stay. Steve Webb is the master
of giving us $50 $50 donation.

1112
01:14:46,080 --> 01:14:51,840
Steve God bless you. He is one
of the original God casters have

1113
01:14:51,840 --> 01:14:55,890
known him for a long, long time.
Very heated his beautiful wife

1114
01:14:55,890 --> 01:14:59,820
very, very sweet of you, Steve.
Thank you. He's long long term

1115
01:14:59,820 --> 01:15:02,820
believe You've heard in what
we're doing. Oh, that's great.

1116
01:15:03,450 --> 01:15:08,100
By the way, tell it if, if we
missed anybody at the beginning,

1117
01:15:08,100 --> 01:15:10,920
like the first couple of ships,
you got to email us. Yeah. Tell

1118
01:15:10,920 --> 01:15:14,220
us because we may have forgotten
to credit you. It was where we

1119
01:15:14,220 --> 01:15:15,540
were in, in chaos.

1120
01:15:16,710 --> 01:15:18,720
Just startup chaos.

1121
01:15:19,590 --> 01:15:25,080
Todd Todd May May thin or
mathan. He said that he he

1122
01:15:25,410 --> 01:15:29,820
taught math and yeah, he said he
was original here for the for

1123
01:15:29,820 --> 01:15:30,540
the iPod

1124
01:15:30,540 --> 01:15:37,050
or he ran it he hand coded his
OPML node for what country is he

1125
01:15:37,050 --> 01:15:38,490
in? Does it say What country is
in

1126
01:15:38,700 --> 01:15:41,700
a said on the mastodon but it's
not in the email? So I don't

1127
01:15:41,700 --> 01:15:41,940
remember

1128
01:15:41,940 --> 01:15:44,250
because I think he was I don't
know if he was in the US. But

1129
01:15:44,250 --> 01:15:46,980
yes. Oh, it's so nice. Nice to
end. Yes. And I do remember on

1130
01:15:46,980 --> 01:15:51,570
the on podcast, index dot
social. Yeah, we had that all

1131
01:15:51,570 --> 01:15:55,440
set up with the directory was it
was the the early podcasts

1132
01:15:55,440 --> 01:15:59,700
index.org, which was very
manual. its execution.

1133
01:16:00,180 --> 01:16:02,520
But you kind of miss it too,
though, right. I mean, it's

1134
01:16:02,520 --> 01:16:04,080
like, why simple.

1135
01:16:04,200 --> 01:16:06,900
When you and I were first
talking about this project, you

1136
01:16:06,900 --> 01:16:09,570
know, we discussed the deep and
we talked about it, how

1137
01:16:09,570 --> 01:16:12,990
beautiful that was? That? Yeah,
you could just do these include

1138
01:16:12,990 --> 01:16:16,740
nodes. And you could just have
this this outline that goes on

1139
01:16:16,740 --> 01:16:19,710
forever. And you can you know,
it was like, it was like Gopher,

1140
01:16:20,610 --> 01:16:21,510
it was just like,

1141
01:16:22,410 --> 01:16:26,310
I've got all the podcasts and in
South America, and there's,

1142
01:16:26,460 --> 01:16:27,480
there's 18 of them.

1143
01:16:29,220 --> 01:16:32,580
But you know that we had him?
Yeah, that's for sure. That's

1144
01:16:32,580 --> 01:16:33,180
for sure.

1145
01:16:33,270 --> 01:16:37,260
Todd, thanks for the $20 month
automatic payment. We get one

1146
01:16:37,260 --> 01:16:47,070
aggregator left. And it's all
yours, baby. The see 10 $10 a

1147
01:16:47,070 --> 01:16:49,590
month now. Sorry, it's not $10
By

1148
01:16:49,589 --> 01:16:53,099
the way, I'm sorry. I'm sorry to
interrupt you. Yeah, he actually

1149
01:16:53,099 --> 01:16:57,479
taught I'm just looking at him.
Todd mathan. He posted a

1150
01:16:57,479 --> 01:17:05,609
screenshot of an email from 11th
of October 2004. I know. I know

1151
01:17:05,639 --> 01:17:08,489
where he says believe he still
has the email. What is wrong

1152
01:17:08,489 --> 01:17:12,269
with you, Todd? He says, Hey,
Adam, I'd be happy to help out

1153
01:17:12,269 --> 01:17:15,329
with a quote radio category in
the podcast directory. I've got

1154
01:17:15,329 --> 01:17:18,749
an OPML editor, my own server
and I said go for it. Just send

1155
01:17:18,749 --> 01:17:22,499
me the URL to the OPML. Thanks.
That's how we roll baby. That

1156
01:17:22,499 --> 01:17:26,789
was it. That was it. Oh, man.

1157
01:17:27,000 --> 01:17:28,110
What a time capsule?

1158
01:17:28,200 --> 01:17:30,090
Yes. Beautiful. Nice. Very cool.

1159
01:17:31,980 --> 01:17:36,330
See adventures and audio. Send
us $10 donation.

1160
01:17:36,389 --> 01:17:37,829
Thank you very much. Any note?
Thank

1161
01:17:37,830 --> 01:17:45,390
you. No, no. I don't see a note.
I didn't see. Michael Kimmerer

1162
01:17:46,620 --> 01:17:49,920
automatic payment $5.33 a month.

1163
01:17:49,980 --> 01:17:51,090
Thank you very much.

1164
01:17:51,780 --> 01:18:00,930
Thank you, Michael. Let's see.
Pedro on calvess. I hope I

1165
01:18:00,930 --> 01:18:06,510
pronounced that right. He sent
an autumn air he's got he did an

1166
01:18:06,510 --> 01:18:14,280
automatic subscription for $5
Thank you very much. I think the

1167
01:18:14,280 --> 01:18:15,120
cops come and get me.

1168
01:18:16,590 --> 01:18:19,020
It's because of all that big Pay
Pal money. You're rocking.

1169
01:18:19,020 --> 01:18:19,800
Rocking in there. It's

1170
01:18:19,800 --> 01:18:23,310
like it's making a dent. It's
making waves.

1171
01:18:23,519 --> 01:18:25,739
It's gotta be drug dealers over
there.

1172
01:18:27,630 --> 01:18:32,550
See, we got a one time donation
for $15 from Allison Hamel.

1173
01:18:33,300 --> 01:18:35,880
Thank you. Thank you very much.
I couldn't find a note.

1174
01:18:36,540 --> 01:18:39,450
Sent send us a note. If you want
us to mention anything. Send it

1175
01:18:39,450 --> 01:18:41,310
we'll do it on the next episode
for sure.

1176
01:18:41,760 --> 01:18:46,950
Yeah, and then an anonymous
donation for $11.11.

1177
01:18:47,010 --> 01:18:51,210
Ah, nothing like an 1111. I
could use them all day. That's a

1178
01:18:51,210 --> 01:18:54,390
good luck. Donation. Do you ever
see that? Do you ever block

1179
01:18:54,390 --> 01:18:56,640
1111? Are you one of those
people who sees that?

1180
01:18:57,060 --> 01:18:59,310
No, I thought it was snake as I
thought it was a bad luck

1181
01:18:59,310 --> 01:18:59,850
donation.

1182
01:19:00,150 --> 01:19:04,290
Oh, no. It's supposed to be
synchronicity. Oh, yeah. When

1183
01:19:04,290 --> 01:19:07,200
you see 1111 That's supposed to
be new that you're you're

1184
01:19:07,200 --> 01:19:09,600
clicking in in harmony with the
universe?

1185
01:19:10,020 --> 01:19:13,950
No, I didn't get that at all. My
pessimism completely took over.

1186
01:19:14,130 --> 01:19:17,970
Okay. Well, that's it. That's
what we asked. Well,

1187
01:19:18,000 --> 01:19:22,140
that's a good list that we
really appreciate it. Thank you.

1188
01:19:22,140 --> 01:19:24,120
Thank you so much value for
value. You're going to be

1189
01:19:24,120 --> 01:19:27,810
hearing this a lot from us as we
move forward, because

1190
01:19:27,840 --> 01:19:31,980
ultimately, the idea is to turn
that into something a little

1191
01:19:31,980 --> 01:19:37,740
more tangible for everybody the
value for value. Right. Well,

1192
01:19:37,800 --> 01:19:45,090
here's. I will. I will. What
else do you have on your list? I

1193
01:19:45,090 --> 01:19:47,970
got some clips. You wanna do
some clips for sure. For sure

1194
01:19:47,970 --> 01:19:48,600
which I got.

1195
01:19:48,870 --> 01:19:58,020
So did you find my sheet here?
Did you hear about the four I

1196
01:19:58,020 --> 01:20:01,470
think you heard about the four
q&a on podcasts that Spotify

1197
01:20:01,470 --> 01:20:02,070
removed, right?

1198
01:20:02,280 --> 01:20:05,250
Yes, I immediately took that as
an opportunity to horror out

1199
01:20:05,250 --> 01:20:10,590
podcast index.org and associated
apps and developers. And yes, of

1200
01:20:10,590 --> 01:20:14,670
course, I took that immediately.
You bet as you should, as you

1201
01:20:14,670 --> 01:20:19,260
said, that's even when Joe
Rogan's Alex Jones episode

1202
01:20:19,260 --> 01:20:23,730
didn't pop up or got removed or
whatever the story was. There

1203
01:20:23,730 --> 01:20:26,610
was a lot of all of a sudden oh
my god, it's gone. I immediately

1204
01:20:26,610 --> 01:20:31,200
posted if you're looking for
episode 1555 of JRE is right

1205
01:20:31,200 --> 01:20:32,010
over here.

1206
01:20:33,390 --> 01:20:40,890
So that the okay so they removed
for Q anon podcasts is how is

1207
01:20:40,890 --> 01:20:41,400
that was? Well,

1208
01:20:41,400 --> 01:20:43,950
that's how they categorize it.
Right. They say it was Q anon

1209
01:20:43,950 --> 01:20:45,600
podcast. Yeah. Well, I

1210
01:20:45,600 --> 01:20:51,600
went and listened to each one of
them. And by the way, I deserve

1211
01:20:51,600 --> 01:20:57,510
$10 a month, just for having to
listen to some of these podcasts

1212
01:20:57,540 --> 01:21:02,610
every week to get clips.
somebody owes me money for this.

1213
01:21:02,940 --> 01:21:05,850
Because sometimes it is painful
to listen to.

1214
01:21:06,000 --> 01:21:10,380
I like to x 22. I've listened to
x 22. And I've, and I've

1215
01:21:10,380 --> 01:21:16,860
followed Praying Medic, on on
Twitter. I think he's gone from

1216
01:21:16,860 --> 01:21:20,430
Twitter. And so I kind of lost
the and the reason why I do it

1217
01:21:20,430 --> 01:21:23,910
is just to check in. See what's
going on with the Q anon people.

1218
01:21:24,000 --> 01:21:24,330
Now.

1219
01:21:26,220 --> 01:21:29,730
When I say terrible podcasts I'm
really talking about you've got

1220
01:21:29,730 --> 01:21:35,220
one ISO in there. No, yes. Yeah,
drop it. That must have been

1221
01:21:35,220 --> 01:21:36,390
tough for you.

1222
01:21:37,290 --> 01:21:39,030
Podcast. Is that a q&a on

1223
01:21:39,030 --> 01:21:45,420
podcast? No. That's from a
podcast called mom knows best

1224
01:21:45,420 --> 01:21:47,550
from the Dance Moms moms.

1225
01:21:47,790 --> 01:21:49,410
So Oh, my goodness.

1226
01:21:49,620 --> 01:21:52,350
I don't even know how I ended up
there. I think he was on cast

1227
01:21:52,350 --> 01:21:54,120
coverage or something like that.
And you say

1228
01:21:54,120 --> 01:21:59,250
something about the Todd keeping
his email since 2004. I don't

1229
01:21:59,250 --> 01:22:02,730
know what you're doing in your
free time. Check yourself.

1230
01:22:03,510 --> 01:22:11,430
Okay. So my theory is that I
mean, I think I listened to one

1231
01:22:11,430 --> 01:22:15,090
episode of each one of these
four that got removed. And

1232
01:22:15,450 --> 01:22:21,660
there's nothing there. I mean,
like it, it's not. These are so

1233
01:22:22,590 --> 01:22:27,390
play I think clip. I think clip
one Q anon one is x 22.

1234
01:22:27,690 --> 01:22:30,810
Let's talk about prepared with
the elections only weeks away.

1235
01:22:30,840 --> 01:22:33,630
We all know we need to be
prepared for the worst civil

1236
01:22:33,630 --> 01:22:36,390
unrest is getting so ugly and
sponsor to bring the entire

1237
01:22:36,390 --> 01:22:38,760
system to its knees, we know
what the deep state's going to

1238
01:22:38,760 --> 01:22:41,220
do. We know that they're going
to be pushing the second wave of

1239
01:22:41,220 --> 01:22:44,550
COVID 19 grocery stores and food
manufacturers are already

1240
01:22:44,550 --> 01:22:47,160
preparing themselves for
nationwide panic, will you be

1241
01:22:47,160 --> 01:22:49,860
ready, don't wait until it's too
late. Remember the toilet paper

1242
01:22:49,860 --> 01:22:53,760
shortage, I urge you to visit
prepare with x 20 two.com. and

1243
01:22:53,760 --> 01:22:56,070
build your emergency fund. And
you need

1244
01:22:56,070 --> 01:23:01,740
to seeds is basically just a
emergency food supplies. That's

1245
01:23:01,740 --> 01:23:07,110
what that's that's what this
was. I mean, like, I know, x 22.

1246
01:23:07,140 --> 01:23:10,830
It may be a good podcast, but
like, that's basically what

1247
01:23:10,830 --> 01:23:14,820
you're gonna get. So there's not
going to be anybody fooled into

1248
01:23:14,820 --> 01:23:18,780
go into shooting up a place, or
doing committing some crime by

1249
01:23:18,780 --> 01:23:23,700
listening to this podcast there.
The what I think is going on is

1250
01:23:23,700 --> 01:23:28,980
basically they just they needed.
Spotify needed some they needed

1251
01:23:28,980 --> 01:23:32,490
to get rid of somebody, they
needed to drop the banhammer on

1252
01:23:32,490 --> 01:23:36,990
somebody. And so they just
picked a few unfortunate

1253
01:23:36,990 --> 01:23:42,750
podcasts. Because q anon was an
easy target. And they're like,

1254
01:23:42,750 --> 01:23:46,290
Okay, we're just gonna get rid
of these as an as examples

1255
01:23:46,320 --> 01:23:50,700
because our main show, the one
we spent 100 million on Joe

1256
01:23:50,700 --> 01:23:59,700
Rogan. We can't we we can't
survive the PR of taking him

1257
01:23:59,700 --> 01:24:03,180
down. And all of our internal
employees are freaking out.

1258
01:24:03,210 --> 01:24:05,190
They're trying to unionize.
They're doing all this kind of

1259
01:24:05,190 --> 01:24:09,450
stuff because they hate Joe
Rogan. But in order to appeal

1260
01:24:09,480 --> 01:24:13,230
and we can't but we can't take
him down. So in order to you

1261
01:24:13,230 --> 01:24:15,780
don't want to have that would be
like another Conan O'Brien

1262
01:24:15,780 --> 01:24:21,360
moment. So you so what they're
doing like, look, we we can't

1263
01:24:21,360 --> 01:24:25,590
take down Joe Rogan. But here's
four Q anon podcasts. See, these

1264
01:24:25,590 --> 01:24:28,710
guys are terrible. Let's take
them off the air. Okay. That's

1265
01:24:28,710 --> 01:24:29,430
the way I read it.

1266
01:24:29,550 --> 01:24:34,170
All right. So I make a study of
this. And there's a couple of

1267
01:24:34,170 --> 01:24:39,870
things going on. One let's talk
about Joe Rogan for a second

1268
01:24:39,900 --> 01:24:43,260
because there's something going
on with him. And I consider him

1269
01:24:43,260 --> 01:24:45,780
to be a friend, not a best
friend or anything but we talk

1270
01:24:45,780 --> 01:24:55,470
we text we whatever. If you look
at his most recent podcasts, the

1271
01:24:55,470 --> 01:24:59,910
one with Kanye West now I speak
Kanye so I enjoyed that very

1272
01:24:59,910 --> 01:25:02,790
much Watch you got to you got to
speak Kanye. I've had a year and

1273
01:25:02,790 --> 01:25:06,210
a half education for mo to
understand just the the topics

1274
01:25:06,210 --> 01:25:11,070
that he brooches. But certainly
in the Alex Jones, Tim Dylan

1275
01:25:11,970 --> 01:25:17,670
example. He was fact checking
everything that was said, Every

1276
01:25:17,670 --> 01:25:22,860
four minutes five minutes that
Jamie, is this true? Now this is

1277
01:25:22,890 --> 01:25:28,500
a problem that Joe has created
for himself. Because the eyes on

1278
01:25:28,500 --> 01:25:33,690
him, he you know, the there's a
lot of people within the Spotify

1279
01:25:33,690 --> 01:25:36,450
organization as you then that's
absolutely true. There's a lot

1280
01:25:36,450 --> 01:25:40,650
of internal issues with that
doesn't even matter why or if

1281
01:25:40,650 --> 01:25:43,140
it's right, or if it's wrong,
it's just a fact is what it is.

1282
01:25:43,800 --> 01:25:52,440
And his way to combat that is by
trying to fact check, you know,

1283
01:25:52,470 --> 01:25:55,980
weird, crazy, outrageous stuff
so that he later can at least

1284
01:25:55,980 --> 01:26:00,600
say, well, we fact check that
this is very destructive to his

1285
01:26:00,600 --> 01:26:05,430
entire format. And he will have
to stop or people will stop

1286
01:26:05,550 --> 01:26:11,250
watching slash listening. It is
disruptive to his format. very

1287
01:26:11,250 --> 01:26:14,520
disruptive. There's always been
some level of the young Jamie,

1288
01:26:15,030 --> 01:26:19,290
looking stuff up. But now fact
checking. I mean, it's the

1289
01:26:19,290 --> 01:26:23,160
possibly the worst thing you can
do. Because for every fact

1290
01:26:23,160 --> 01:26:26,400
check, we've got a fact check
false. You can fact check

1291
01:26:26,400 --> 01:26:30,300
anything from any page anywhere.
And it's a never ending story.

1292
01:26:30,570 --> 01:26:33,570
And what he's doing is he's
disrupting his flow and his

1293
01:26:33,570 --> 01:26:37,440
interview. And that is because
he's on Spotify. That yeah,

1294
01:26:37,470 --> 01:26:42,180
that's because Joe is a really,
really nice guy. He's really a

1295
01:26:42,180 --> 01:26:46,950
sweet guy. I know him. He
doesn't want to offend people,

1296
01:26:46,950 --> 01:26:52,980
he wants to try and keep all
sides kind of imbalance. It just

1297
01:26:52,980 --> 01:26:57,420
doesn't work that way. It's you
know, you if you try to straddle

1298
01:26:57,420 --> 01:26:59,970
you just it's just gonna wind up
mediocre. So we have to figure

1299
01:26:59,970 --> 01:27:03,900
that out. But that is because of
the Spotify move. I would hate

1300
01:27:03,900 --> 01:27:07,620
to wake up every single morning.
Like, what are they bitching

1301
01:27:07,620 --> 01:27:12,000
about now? There's just a lot of
negativity. The Q anon thing

1302
01:27:12,150 --> 01:27:15,810
stems from a different issue.
From a lie, a lie that was

1303
01:27:15,810 --> 01:27:21,090
created and propagated My day
job is deconstructing media. And

1304
01:27:21,150 --> 01:27:26,280
where it really started was with
the town hall in Florida with

1305
01:27:26,280 --> 01:27:31,080
President Trump and Savannah
Guthrie, and this is where it

1306
01:27:31,080 --> 01:27:31,590
started.

1307
01:27:32,460 --> 01:27:37,290
Denouncing let me ask you about
Q anon. It is this theory that

1308
01:27:38,400 --> 01:27:42,840
Democrats are a satanic
pedophile ring and that you are

1309
01:27:42,840 --> 01:27:45,660
the Savior that this

1310
01:27:45,690 --> 01:27:49,230
I followed Q anon from the
beginning. It has never been

1311
01:27:49,230 --> 01:27:54,660
about Democrats. Yeah. But
they've created this lie. And I

1312
01:27:54,660 --> 01:27:58,350
think the first time I really
saw it big was here. And

1313
01:27:58,650 --> 01:28:03,930
Democrats, and it was
interesting. I didn't clip it. I

1314
01:28:03,930 --> 01:28:08,820
don't think but on Saturday
Night Live, when they did the,

1315
01:28:09,270 --> 01:28:14,940
the take off of that town hall.
They actually had Alec Baldwin

1316
01:28:14,940 --> 01:28:18,300
as the Trump character saying
it's Democrats, Democrats,

1317
01:28:18,300 --> 01:28:22,920
satanic children, which Trump
never said. So they have turned

1318
01:28:22,920 --> 01:28:27,570
this into a well, this is
political, because they're

1319
01:28:27,570 --> 01:28:32,940
saying Democrats, I would
challenge anybody to find

1320
01:28:32,940 --> 01:28:35,760
something that says
specifically, it's just

1321
01:28:35,760 --> 01:28:41,880
Democrats, if anything is
Hollywood celebrities. People

1322
01:28:41,880 --> 01:28:49,320
like Zuckerberg, Tom Hanks,
Madonna, you know, these people

1323
01:28:49,320 --> 01:28:54,240
may be Democrats. But that was
I've never heard this specified

1324
01:28:54,240 --> 01:28:59,610
as it's only Democrats, and who
was a big relationship over at

1325
01:28:59,610 --> 01:29:07,500
Spotify. Higher Higher Ground
productions, Michelle and Barack

1326
01:29:07,500 --> 01:29:12,540
Obama. So there was a power play
and the power play went all the

1327
01:29:12,540 --> 01:29:16,470
way through even though it was
it's disingenuous, and really

1328
01:29:16,470 --> 01:29:23,520
created in my mainstream media
because cue I never saw this

1329
01:29:23,520 --> 01:29:28,110
distinction. And now maybe it's
just out there. And that's what

1330
01:29:28,110 --> 01:29:33,240
it will be forever, because now
I hear people's I even heard, I

1331
01:29:33,240 --> 01:29:40,020
heard Todd and Rob on, I guess
was the new media show talking

1332
01:29:40,020 --> 01:29:44,520
about this very issue. And they
stated as fact. Well, it's

1333
01:29:44,520 --> 01:29:48,240
political because it's about
Democrats doing such so it's out

1334
01:29:48,240 --> 01:29:51,630
there. It's already been
cemented in people's minds. This

1335
01:29:51,630 --> 01:29:55,200
was a political move. I believe
that there's already enough

1336
01:29:55,200 --> 01:29:58,380
trouble with the Michelle Obama
podcast not getting the reach it

1337
01:29:58,380 --> 01:30:02,100
does. They can tell me all that
they want about it. That's the

1338
01:30:02,100 --> 01:30:06,630
number to podcast. I think it's
baloney. This was a power play,

1339
01:30:06,630 --> 01:30:11,280
someone got pissed off, and then
something had to fall. So in

1340
01:30:11,280 --> 01:30:15,330
that part, you're correct. And,
and somehow pressure was

1341
01:30:15,330 --> 01:30:20,070
applied. Because Oh, my God,
there. And I think that people

1342
01:30:20,070 --> 01:30:26,100
who were asked for this and were
responsible for the delisting

1343
01:30:26,400 --> 01:30:29,370
probably believe it's only about
Democrats, and they've never

1344
01:30:29,370 --> 01:30:31,140
looked into it and never
listened to it.

1345
01:30:31,469 --> 01:30:36,599
So it's like an accident. It's
like, an accident of of news

1346
01:30:36,629 --> 01:30:40,979
cemented this connection. And
now they have to go, they have

1347
01:30:40,979 --> 01:30:41,579
to defend it.

1348
01:30:42,240 --> 01:30:45,210
Yes, and it will be that way
forever. And these things happen

1349
01:30:45,210 --> 01:30:48,270
all the time. It's often by
accident. But this was

1350
01:30:48,360 --> 01:30:52,470
purposeful, purposeful,
purposefully turned into that to

1351
01:30:52,470 --> 01:30:54,420
get rid of it. And

1352
01:30:54,660 --> 01:30:57,690
they must have, they must have
just a console, then that just

1353
01:30:57,690 --> 01:31:01,740
says, like, where you can just
search for stuff, and hit the

1354
01:31:01,740 --> 01:31:06,180
Delete button, because somebody
just said Q anon. And then they

1355
01:31:06,180 --> 01:31:08,610
found like four podcasts and
they just like, Okay, we'll take

1356
01:31:08,610 --> 01:31:12,600
the top four, because one of
these was podcast called

1357
01:31:12,600 --> 01:31:15,690
indigenous mic. And I think
it's, I think that may be

1358
01:31:15,690 --> 01:31:16,500
clipped for.

1359
01:31:22,560 --> 01:31:25,950
Hey, what's going on beautiful
people. Thank you so much for

1360
01:31:25,950 --> 01:31:31,620
tuning in today. I'm your host,
indigenous Mike. And today, I

1361
01:31:31,620 --> 01:31:37,290
want to focus on Democrats
having faith, having strength

1362
01:31:38,160 --> 01:31:45,870
and finding yourself evil. So
over the past few years,

1363
01:31:46,620 --> 01:31:49,170
I want to hear it now. I want to
hear the rest of it. I have

1364
01:31:49,200 --> 01:31:56,640
been finding myself, I have been
realizing the true potential of

1365
01:31:56,640 --> 01:31:59,280
myself and every other person on
this planet.

1366
01:31:59,429 --> 01:32:04,919
Clearly dangerous speech going
on. Yeah, clearly dangerous,

1367
01:32:05,130 --> 01:32:09,060
is the worst sort of hate speech
that I've ever heard. I don't

1368
01:32:09,060 --> 01:32:11,340
even know. I mean, like, this
guy's just, and this was an M

1369
01:32:11,340 --> 01:32:14,580
for a, by the way, audio was
greatly three. So I mean,

1370
01:32:14,580 --> 01:32:18,420
clearly this person is just
indigenous mind. He's just, this

1371
01:32:18,420 --> 01:32:19,440
is one token into his.

1372
01:32:21,120 --> 01:32:26,910
So we need to talk about this
briefly. Section 230 of the

1373
01:32:26,910 --> 01:32:31,110
Communications Decency Act from
1996. I'm a student of this. And

1374
01:32:31,110 --> 01:32:36,120
it's incredibly important to
podcast index.org, that we

1375
01:32:36,120 --> 01:32:42,000
maintain this protection under
Section 230. Which means we

1376
01:32:42,000 --> 01:32:45,630
cannot be held liable for
anything that is uploaded to our

1377
01:32:45,630 --> 01:32:50,790
platform. Now, we may get a
government request for something

1378
01:32:50,880 --> 01:32:57,510
which I don't know, I don't
know. How, how if or when that

1379
01:32:57,510 --> 01:33:01,020
will come about. I guarantee you
we're going to have all kinds of

1380
01:33:01,050 --> 01:33:06,780
shit coming our way. It will
happen. And it was an

1381
01:33:06,780 --> 01:33:09,930
interesting. That sounds great
in the noise gate.

1382
01:33:12,270 --> 01:33:13,620
Flanger I

1383
01:33:13,620 --> 01:33:17,070
guarantee you that will happen.
But I just want to state one

1384
01:33:17,070 --> 01:33:20,610
thing. There is no legal
definition of hate speech.

1385
01:33:20,730 --> 01:33:24,570
There's no legal definition of
it. And I was extremely

1386
01:33:24,570 --> 01:33:31,230
disappointed to see our senators
and everybody else circle

1387
01:33:31,230 --> 01:33:39,330
jerking around with Pichai and
Zuckerberg and and Dorsey and

1388
01:33:39,330 --> 01:33:43,380
actually discussing the concept
of hate speech as if it's a

1389
01:33:43,380 --> 01:33:50,490
thing and I will put my neck on
the line for any kind of speech.

1390
01:33:50,820 --> 01:33:55,020
I don't care what it is we have
constitutional things that are a

1391
01:33:55,020 --> 01:33:59,250
problem. Literally inciting
violence. I mean, that's that

1392
01:33:59,250 --> 01:34:02,670
that's clearly spelled out what
those exceptions are. But

1393
01:34:02,670 --> 01:34:06,990
everything else I will I will
stick I will stake a lot on that

1394
01:34:06,990 --> 01:34:10,320
so there's nothing is going to
get taken down or removed. This

1395
01:34:10,320 --> 01:34:15,870
is this is very destructive what
Spotify and Apple and others are

1396
01:34:15,870 --> 01:34:19,020
doing. It's very, very, very,
very bad.

1397
01:34:19,890 --> 01:34:24,390
If you've been reading I'm sure
you have Tybee and greenwell's

1398
01:34:24,780 --> 01:34:26,520
articles lately have

1399
01:34:26,520 --> 01:34:29,220
course on the subject. Yeah,
yeah, he's,

1400
01:34:30,030 --> 01:34:33,810
let's see was this Yeah, this is
from Greenwald's thing

1401
01:34:33,810 --> 01:34:40,650
yesterday, he says. This was not
an easy choice, and voluntarily

1402
01:34:40,650 --> 01:34:43,350
sacrificing the support of large
institution and guaranteed

1403
01:34:43,350 --> 01:34:45,750
salary in exchange for nothing
other than unbelief that there

1404
01:34:45,750 --> 01:34:48,750
are enough people who believe in
the virtues of independent

1405
01:34:48,750 --> 01:34:51,600
journalism and the need for free
discourse who will be willing to

1406
01:34:51,600 --> 01:34:56,250
support my work by subscribing
to like a think that was

1407
01:34:56,250 --> 01:35:00,450
happening. There's this talk
about well, the to private

1408
01:35:00,450 --> 01:35:05,430
companies, and it's not a matter
of free speech because this is

1409
01:35:05,430 --> 01:35:11,790
not the government. But what you
seen with Greenwald, anti Eb,

1410
01:35:12,510 --> 01:35:17,520
especially Mata ABC has been,
he's been showing how the news

1411
01:35:17,520 --> 01:35:22,380
media has become more and more
concentrated in in tech just lit

1412
01:35:22,380 --> 01:35:25,830
the flame like it just it was a
gasoline and tank just lit it up

1413
01:35:26,190 --> 01:35:32,310
to where almost all local media
has been decimated. So there

1414
01:35:32,550 --> 01:35:37,320
there is, yes, these are private
companies. But they've become

1415
01:35:37,320 --> 01:35:41,220
really over the last seven to
eight years, maybe 10 years,

1416
01:35:41,220 --> 01:35:46,260
they've become the default
funnel for all speech gets

1417
01:35:46,260 --> 01:35:50,400
pushed through, really these
three companies mainly Twitter,

1418
01:35:50,400 --> 01:35:54,930
Facebook, Google. I mean,
there's, yes, they're private

1419
01:35:54,930 --> 01:35:58,860
companies. But when they put all
other local media out of

1420
01:35:58,860 --> 01:36:03,570
business, then they have
basically vacuumed it all up.

1421
01:36:03,570 --> 01:36:07,770
And they they took the space
that local media had like here

1422
01:36:07,770 --> 01:36:12,180
in Birmingham, Alabama, we had
going his you know,

1423
01:36:12,180 --> 01:36:15,150
historically, we had two major
newspapers at the post Herald

1424
01:36:15,150 --> 01:36:18,960
and Birmingham News. And they're
both gone. Yeah. I mean, the

1425
01:36:18,960 --> 01:36:22,350
Birmingham News building, it was
a huge building that they built

1426
01:36:22,350 --> 01:36:25,500
about, I guess, about 20 years
ago. And it's now an insurance

1427
01:36:25,500 --> 01:36:29,490
company. There's for all
practical purposes, there is no

1428
01:36:29,490 --> 01:36:31,410
newspaper in Birmingham anymore.

1429
01:36:32,219 --> 01:36:34,889
Right, but a bit sure there's a
couple of good blogs.

1430
01:36:35,489 --> 01:36:38,819
Oh, yeah. Well, aol.com is the
is the website for all news

1431
01:36:38,819 --> 01:36:41,969
here. And it's just, you know,
they just kind of scooped up all

1432
01:36:41,969 --> 01:36:44,789
the leftover reporters from the
various newspapers like

1433
01:36:44,790 --> 01:36:49,890
we this is who I could talk for
hours about this, however, yeah.

1434
01:36:52,440 --> 01:36:57,090
I'm just looking at federated
Mastodon servers or pour out

1435
01:36:57,600 --> 01:37:00,030
fluorine, plural, whatever it's
called.

1436
01:37:00,450 --> 01:37:01,860
Aroma pluralism.

1437
01:37:02,670 --> 01:37:06,660
That's another kind of new
social, whatever it is. Yeah.

1438
01:37:06,930 --> 01:37:13,110
That's much bigger than it was I
mean, that's grown. So I'm, I'm

1439
01:37:13,110 --> 01:37:16,290
much less of a oh my god,
they're censoring us. I'm like,

1440
01:37:16,320 --> 01:37:23,250
I'm gonna have my conversation
somewhere else. It is. It is an

1441
01:37:23,250 --> 01:37:30,270
educational issue that people
are headline readers. And it's

1442
01:37:30,270 --> 01:37:35,550
slowly these are slow processes,
but to have Greenwald, and tyy

1443
01:37:35,550 --> 01:37:41,640
be, and there'll be more. Okay,
how about Megyn Kelly, now she

1444
01:37:41,640 --> 01:37:45,390
got a huge pay day. But Megyn
Kelly on the podcast,

1445
01:37:45,630 --> 01:37:51,360
unrestricted is dynamite. She I
mean, she's really good. I was

1446
01:37:51,360 --> 01:37:54,510
always like, yeah, and I don't
get I don't really care too much

1447
01:37:54,510 --> 01:37:58,470
for, right. But when she's her
unrestricted self, she's a great

1448
01:37:58,470 --> 01:38:03,000
journalist. She doesn't actually
really create an outstanding

1449
01:38:03,000 --> 01:38:05,400
product. Now she's gonna get
into her trouble because she's

1450
01:38:05,400 --> 01:38:09,090
got legacy box and other
sponsors. She doesn't need a

1451
01:38:09,090 --> 01:38:13,350
sponsor. I think she got $60
million pay off to leave NBC or

1452
01:38:13,350 --> 01:38:17,640
CBS versus do it for fun. Yeah,
but she's doing it. She's she's

1453
01:38:17,640 --> 01:38:25,350
taking it very seriously. We
have enough uptake. True. I

1454
01:38:25,350 --> 01:38:28,170
mean, as you've pointed out,
there's at least 40% of the

1455
01:38:28,170 --> 01:38:33,570
market of the podcast market
that we can, can work with. Now

1456
01:38:33,570 --> 01:38:37,320
we need a couple of things.
First of all, we need to free

1457
01:38:37,320 --> 01:38:40,260
podcasting from corporate
control. This is what's taking

1458
01:38:40,260 --> 01:38:42,870
place, we can all say it's, you
know, we can pretend it's not

1459
01:38:42,870 --> 01:38:48,150
happening. Spotify is the
furthest along. Amazon is trying

1460
01:38:48,150 --> 01:38:51,750
to figure it out, they may never
figure it out. Google believes

1461
01:38:51,750 --> 01:38:55,590
they own it anyway. Because it's
on the internet. So it's there's

1462
01:38:56,130 --> 01:39:00,750
I Heart Radio, pathetic attempt
at trying to save a company

1463
01:39:00,750 --> 01:39:03,120
that's leveraged with billions
of dollars they can't afford,

1464
01:39:03,120 --> 01:39:05,910
I'm sorry, it's not going to be
not going to be a happy ending

1465
01:39:05,910 --> 01:39:14,250
for them. And the leftover is
Apple, who will probably

1466
01:39:14,250 --> 01:39:17,370
innovate for as you've pointed
out, podcasts, plus, we've got

1467
01:39:17,400 --> 01:39:20,670
Apple TV plus, we got all kinds
of plus stuff. So they'll

1468
01:39:20,670 --> 01:39:23,910
probably do their own version
because people believe that they

1469
01:39:23,910 --> 01:39:29,010
can make money off of a network
of shows, which I know doesn't

1470
01:39:29,040 --> 01:39:35,220
work in this new paradigm. So we
in order to succeed, we have to

1471
01:39:35,220 --> 01:39:39,060
free podcasting from corporate
control. And here's the big one.

1472
01:39:39,090 --> 01:39:41,970
Not for today's show. But we're
going to talk about it integrate

1473
01:39:41,970 --> 01:39:47,640
decentralized content with
decentralized money. Yeah. And

1474
01:39:47,730 --> 01:39:50,790
through that, we're going to be
building a self sustaining

1475
01:39:50,820 --> 01:39:54,540
ecosystem for podcasting. You
know, the index is kind of

1476
01:39:54,540 --> 01:39:57,390
running by its own right now
because the servers are paid

1477
01:39:57,390 --> 01:40:02,490
for. You're not paid for. Yeah.
I have Eric back office, he's

1478
01:40:02,490 --> 01:40:05,430
gonna be doing lots of legal
stuff he's not paid for. So we

1479
01:40:05,430 --> 01:40:08,400
need to have a system, everybody
needs to get a pay day, we might

1480
01:40:08,400 --> 01:40:13,530
as well just all quit. But I
believe in my core in my core,

1481
01:40:14,160 --> 01:40:18,450
we can make this happen. And I
love doing these numbers for

1482
01:40:18,450 --> 01:40:21,570
everybody. And I'll leave it at
that. Because I think we've done

1483
01:40:21,570 --> 01:40:26,310
it before. There are 100 million
podcast listeners in the US.

1484
01:40:26,310 --> 01:40:30,180
That's the IAB statistics. On
average, those 100 million

1485
01:40:30,180 --> 01:40:34,170
people listen to one hour a day,
seven days a week or one hour a

1486
01:40:34,170 --> 01:40:40,110
day, people listen, if we can
convert 1% of those 100 million

1487
01:40:40,110 --> 01:40:46,770
people. And the conversion for
no agenda is like 3%. So of all

1488
01:40:46,770 --> 01:40:50,580
the people we have, we've
converted 3% to send us money

1489
01:40:50,580 --> 01:40:55,530
directly send actual monetary
value, forgetting all that, oh,

1490
01:40:55,530 --> 01:40:58,290
setting aside all the things
that people do, that would cost

1491
01:40:58,290 --> 01:41:03,630
us money, the pure money, I
think we can convert 1% of the

1492
01:41:03,630 --> 01:41:08,610
100 million podcast listeners to
support the shows they listened

1493
01:41:08,610 --> 01:41:14,310
to in a frictionless manner. So
if we can convert 1% to

1494
01:41:14,310 --> 01:41:20,310
podcasting 2.0. And we say we
value, one hour of listening at

1495
01:41:20,310 --> 01:41:26,730
$1 per hour, we're talking about
a million dollars a day that can

1496
01:41:26,730 --> 01:41:32,010
flow through to podcasters app
developers and hosting

1497
01:41:32,010 --> 01:41:35,880
companies. And a little piece of
everybody that is a part of it

1498
01:41:35,880 --> 01:41:40,920
can participate in this flow. I
think we have a way to capture

1499
01:41:40,920 --> 01:41:45,180
it. This is not going to be
easy. But we need a next

1500
01:41:45,180 --> 01:41:49,050
generation solution for the next
problem, or the really the next

1501
01:41:49,290 --> 01:41:54,000
phase of media. Nothing, all of
this is going to go away these

1502
01:41:54,000 --> 01:41:58,080
advertising advertisements. It's
all going to change. It's not

1503
01:41:58,080 --> 01:42:02,610
going to be a successful look.
They've had 15 years. It's not a

1504
01:42:02,610 --> 01:42:06,840
billion dollar business yet. No,
it's not going to be a billion

1505
01:42:06,840 --> 01:42:11,100
dollar business. YouTube is
having an incredible problem

1506
01:42:11,100 --> 01:42:14,790
right now you know what their
problem is? They need to go up

1507
01:42:14,790 --> 01:42:19,890
5% for their quarterly revenue.
They are they have no more

1508
01:42:19,890 --> 01:42:21,930
content to stick their ads on.

1509
01:42:23,250 --> 01:42:24,180
It's so saturated.

1510
01:42:24,480 --> 01:42:28,590
They're doing they're doing
three ad breaks before before

1511
01:42:28,590 --> 01:42:31,260
you see the video. They're
showing political ads on

1512
01:42:31,260 --> 01:42:32,640
children's programming.

1513
01:42:33,090 --> 01:42:36,360
It's a reverse inventory
problem. Yes, exactly.

1514
01:42:36,450 --> 01:42:39,660
They literally don't have the
inventory. They've oversold

1515
01:42:39,660 --> 01:42:42,570
everything. So now they have to
start jamming it up. Everybody's

1516
01:42:42,570 --> 01:42:46,470
bought it. And you know what
happens? People go to bid shoot.

1517
01:42:46,860 --> 01:42:50,520
You know what, yeah, you know,
what happens with when people

1518
01:42:50,520 --> 01:42:54,450
get sick and tired of Twitter?
Some it's gonna be on the

1519
01:42:54,450 --> 01:42:58,710
blockchain or god knows what,
you cannot stop this.

1520
01:42:59,040 --> 01:43:02,310
You know, we're guessing we'll
be on the blockchain to pot I

1521
01:43:02,580 --> 01:43:06,120
have no doubt in mine. In my
mind podcast subscriptions will

1522
01:43:06,120 --> 01:43:11,070
be on some form of blockchain
or, or DHT space or whatever,

1523
01:43:11,130 --> 01:43:16,800
whatever it is, we will overcome
these issues. But we have to be

1524
01:43:16,800 --> 01:43:20,850
fearless and we have to move
ahead with big, big brass balls.

1525
01:43:21,990 --> 01:43:31,380
Which I love doing. Big brass
balls. I could put instead of

1526
01:43:31,380 --> 01:43:34,410
here come the pioneers, big
brass balls. Yeah, much chapter

1527
01:43:34,410 --> 01:43:38,850
marker. I'm just chapter. Okay,
I'll make it as a chapter

1528
01:43:38,850 --> 01:43:43,860
marker. There you go. That's an
even funnier idea. So and I'm

1529
01:43:43,860 --> 01:43:48,150
super excited. And we have work
to do, you know, we have to

1530
01:43:48,150 --> 01:43:54,270
figure out Dave and I have been
working on the decentralized

1531
01:43:54,270 --> 01:44:00,090
money part. And we cannot wait
to show everybody how it works.

1532
01:44:00,090 --> 01:44:04,290
And we're still finalizing bits
and pieces. If we're a proof of

1533
01:44:04,290 --> 01:44:09,150
concept, which works. But we
can't do any of it until we have

1534
01:44:09,150 --> 01:44:14,940
figured out how to work between
toolmakers hosters app

1535
01:44:14,940 --> 01:44:18,810
developers and producers and
listeners, we haven't quite

1536
01:44:18,810 --> 01:44:23,580
close that loop yet. We we
really accelerated this week.

1537
01:44:24,510 --> 01:44:28,860
With with with, with just
understanding the problem and

1538
01:44:28,860 --> 01:44:30,690
starting to create some fixes
for it.

1539
01:44:31,620 --> 01:44:35,490
We just gotta be it's gotta be
something that it's got to be

1540
01:44:35,490 --> 01:44:39,420
able to touch every person in
the chain from their listener

1541
01:44:39,420 --> 01:44:42,840
all the way through to the
Creator. And it's got to also be

1542
01:44:42,840 --> 01:44:48,150
something that is not that is
not controlled by any one

1543
01:44:48,150 --> 01:44:51,720
person. It's got to be something
that we can all fit anybody can

1544
01:44:51,720 --> 01:44:55,380
lift dropped down on their own
system. It's not it's got to be

1545
01:44:55,380 --> 01:44:58,740
something that's not we're going
to run our piece of it, but it's

1546
01:44:58,740 --> 01:45:02,400
not going to be something that
that, oh, that's just you know,

1547
01:45:02,400 --> 01:45:05,670
the podcast index thing. It's an
old, it's got to be an open

1548
01:45:05,670 --> 01:45:07,980
spec, it's got to be because
that's the only way I'll

1549
01:45:07,980 --> 01:45:08,550
survive.

1550
01:45:09,240 --> 01:45:15,210
And, and, and with that comes,
like, we can't even start to

1551
01:45:15,210 --> 01:45:19,170
talk about it until we figured
out how to agree on a namespace

1552
01:45:19,170 --> 01:45:22,350
element, and how to get it
implemented and working and

1553
01:45:22,350 --> 01:45:27,450
tested and iterated and iterated
and iterated. Again, if we can't

1554
01:45:27,450 --> 01:45:35,910
do that properly, with host and
guest tags, we're never, we're

1555
01:45:35,910 --> 01:45:40,620
never gonna, we're never gonna
get anything else done. So, I'm

1556
01:45:40,620 --> 01:45:46,500
very excited about moving all of
these and I'm focusing purely on

1557
01:45:46,500 --> 01:45:50,490
the tags where I can purely on
the tags and the namespace. I

1558
01:45:50,490 --> 01:45:57,690
will do my best to create, to
create use cases of, of these

1559
01:45:57,690 --> 01:46:00,240
different pieces of
functionality, and I will

1560
01:46:00,240 --> 01:46:05,610
continue to be vocal about the
problems I'm having. And I'll

1561
01:46:05,610 --> 01:46:08,490
add some wishlist things in
there as well because, you know,

1562
01:46:08,790 --> 01:46:09,990
no one asked me,

1563
01:46:11,520 --> 01:46:18,660
you know, I will continue to put
put emojis in podcasters

1564
01:46:18,660 --> 01:46:19,320
excellent social.

1565
01:46:21,690 --> 01:46:22,980
Have you been doing emojis?

1566
01:46:23,820 --> 01:46:26,550
That's, it's gotta stop.

1567
01:46:26,580 --> 01:46:29,910
I can't I can't bring myself to
do emojis. It's very difficult

1568
01:46:30,360 --> 01:46:33,870
to control. And whenever you do
a smiley face old school that

1569
01:46:33,870 --> 01:46:35,700
always says, Did you mean this?

1570
01:46:36,210 --> 01:46:37,560
Yeah, like no, Arrow,

1571
01:46:38,640 --> 01:46:40,500
Arrow, Arrow, key arrow key to
the right.

1572
01:46:42,750 --> 01:46:45,660
All right, I gotta do some work.
Yeah, you bet. Ready to wrap it?

1573
01:46:45,690 --> 01:46:46,050
Yeah.

1574
01:46:46,080 --> 01:46:48,990
Anything else? Is there anything
else that we can do for you if

1575
01:46:48,990 --> 01:46:50,130
there's something that you need?

1576
01:46:52,620 --> 01:46:56,040
I do need sleep. We had storms
here. A couple of nights. Yeah,

1577
01:46:56,040 --> 01:46:56,280
that's

1578
01:46:56,280 --> 01:46:59,070
right. It was getting pretty
close to you guys. Another

1579
01:46:59,070 --> 01:47:00,990
hurricane bullcrap. Now,

1580
01:47:01,050 --> 01:47:05,100
it hit about 45 minutes south of
us. And it was the wind was

1581
01:47:05,100 --> 01:47:06,750
screaming up here and

1582
01:47:06,780 --> 01:47:07,770
Mia, you know, none

1583
01:47:07,770 --> 01:47:08,340
of my family

1584
01:47:08,580 --> 01:47:12,990
can't see it. All right, my
brother. Happy Halloween. You

1585
01:47:12,990 --> 01:47:16,980
going out? Oh, yeah, we'll be
taking their little girl. I'm

1586
01:47:16,980 --> 01:47:17,880
gonna go dressed as

1587
01:47:17,910 --> 01:47:25,470
namespace and be the contributor
today. All right, Dave. Have a

1588
01:47:25,470 --> 01:47:28,920
great weekend, buddy. I'll talk
to you next week. See everybody

1589
01:47:28,980 --> 01:47:30,960
on the next podcasting 2.0

