1
00:00:00,000 --> 00:00:05,730
Oh, podcasting 2.0 for October
9 2020, episode number six name

2
00:00:05,730 --> 00:00:12,780
your space I'd like yelling on a
Friday. Makes me feel good.

3
00:00:13,710 --> 00:00:18,300
Ladies and gentlemen, to Dragon
Slayer Dave Jones on the

4
00:00:18,300 --> 00:00:19,080
microphone.

5
00:00:19,830 --> 00:00:27,390
Yeah. I just made a mistake of
scarfed down some lunch I ate a

6
00:00:27,390 --> 00:00:33,390
sandwich. But then I made the
mistake of I ate a butter finger

7
00:00:33,390 --> 00:00:37,290
right after that. Oh. And then
and then I realized that had

8
00:00:37,290 --> 00:00:39,930
some more sandwich. And so I ate
that. And I was like, you know,

9
00:00:39,930 --> 00:00:43,230
I really, I don't want the taste
of roast beef sandwich in my

10
00:00:43,230 --> 00:00:45,840
mouth for the whole show. So I
had to eat another butter finger

11
00:00:45,840 --> 00:00:49,020
to compensate for having food

12
00:00:49,380 --> 00:00:53,220
waffling issue real issues, man.
We should talk to somebody about

13
00:00:53,220 --> 00:00:58,020
that. Yeah. All right. My
favorite is vanilla yogurt and

14
00:00:58,020 --> 00:01:03,060
cheese. No. Cheese. Yeah. So
I'll take a bite of cheese. And

15
00:01:03,060 --> 00:01:04,470
then I'll have some vanilla
yogurt with.

16
00:01:06,420 --> 00:01:09,660
That's a strange one. Yeah.
Preferably. green jello and

17
00:01:09,660 --> 00:01:10,170
carrots.

18
00:01:10,320 --> 00:01:13,410
Oh, yes. There you go. There you
go. There's a nice callback

19
00:01:15,000 --> 00:01:17,790
episode number six, which means
we've really only been at this

20
00:01:17,790 --> 00:01:20,280
for less than two months. Right.
And we've probably had a week of

21
00:01:20,280 --> 00:01:25,860
calls and started and I think we
recorded the first episode a

22
00:01:25,860 --> 00:01:28,200
week before we released it, if I
recall correctly.

23
00:01:29,130 --> 00:01:31,710
Yeah, it feels longer than that.
does.

24
00:01:31,740 --> 00:01:35,130
It does well. So we got some
exciting news for today. Because

25
00:01:35,130 --> 00:01:40,290
just before we started, you
dropped a namespace and did a

26
00:01:40,290 --> 00:01:44,610
drop down menu namespace dropped
on the hub.

27
00:01:45,390 --> 00:01:49,230
Yeah. Yeah. So I mean, do we
what do we want to do want to

28
00:01:49,230 --> 00:01:50,760
talk about some donations? Or do
we?

29
00:01:50,789 --> 00:01:54,959
No, no, no, no, no, I want to
know, don't bury the lead. Let's

30
00:01:54,959 --> 00:01:57,779
get to the namespace first, and
then donations definitely

31
00:01:58,289 --> 00:02:01,649
touched posted to ease and other
stuff. No, no, no, not.

32
00:02:01,980 --> 00:02:04,500
This is this is the lead you
got? We got lots of stuff to

33
00:02:04,500 --> 00:02:05,160
talk about.

34
00:02:05,700 --> 00:02:11,550
All right. Yeah. So I spent a
couple of days writing up.

35
00:02:12,060 --> 00:02:18,600
Something is, first of all, the
namespace is not meant to be I

36
00:02:18,600 --> 00:02:22,470
mean, this is not a complete
thing. This is just something to

37
00:02:22,470 --> 00:02:24,570
get everybody started, maybe

38
00:02:24,570 --> 00:02:26,670
you should back up for a second,
I'll just give you my

39
00:02:26,670 --> 00:02:29,010
understanding of what a
namespace is for people who are

40
00:02:29,010 --> 00:02:33,090
listening going, Oh, no, no, no,
don't just do technical. Debt

41
00:02:33,090 --> 00:02:38,430
for a namespace is a way to take
the existing podcast

42
00:02:38,430 --> 00:02:43,140
infrastructure, which is based
on RSS mainly, and add

43
00:02:43,140 --> 00:02:46,500
functionality to it. Is that
fair?

44
00:02:47,520 --> 00:02:53,550
Yes, it's a way to extend a an
XML document, without having to

45
00:02:53,550 --> 00:03:00,510
write a new document. Document
definition, right. So which

46
00:03:00,990 --> 00:03:05,640
Google did for their for their
podcast, you know, directory

47
00:03:05,640 --> 00:03:10,170
thing, but or whatever they call
it, Google did that they wrote a

48
00:03:10,170 --> 00:03:15,540
DTD. And all this jazz, but you
can sort of get around that by

49
00:03:15,540 --> 00:03:20,370
just creating a namespace. And
it allows you to extend the XML

50
00:03:20,370 --> 00:03:24,450
with new element types. Easily

51
00:03:24,600 --> 00:03:28,950
now when when Google does their
own DTD? Is that their version

52
00:03:28,950 --> 00:03:33,960
of capturing the space? Hoping
for adoption, hoping for

53
00:03:33,960 --> 00:03:35,370
adoption for to their?

54
00:03:36,359 --> 00:03:39,539
Maybe? I think they I think they
do it more from the standpoint

55
00:03:39,539 --> 00:03:42,869
of just that they're, they're
just kind of super geeky. Oh,

56
00:03:42,899 --> 00:03:45,329
okay. You know, and they just
kind of go off, they go to the

57
00:03:45,359 --> 00:03:48,089
very bottom of everything.
Right? Well, this is the right

58
00:03:48,089 --> 00:03:49,289
this is this is how you do

59
00:03:50,430 --> 00:03:53,640
watch us, we got a lot of people
to throw at it. Okay. I

60
00:03:53,640 --> 00:03:55,170
understand. That's my

61
00:03:55,170 --> 00:04:01,080
impression. But um, yeah, so
this, there's many namespaces,

62
00:04:01,380 --> 00:04:04,560
for RSS that have cropped up
over the years. Some of them

63
00:04:04,560 --> 00:04:09,060
specific to podcasting. Some of
them not. There's a list of

64
00:04:09,060 --> 00:04:14,280
them. So what I posted in the
podcast, index dot social, was a

65
00:04:14,280 --> 00:04:20,010
link to the GitHub repository
that contains the write up for

66
00:04:20,010 --> 00:04:22,740
this. And let me just jump over
there real quick.

67
00:04:23,820 --> 00:04:26,790
Because this is where you get to
put your writing skills to good

68
00:04:26,790 --> 00:04:29,970
use, and get to write some of
that Dave Jones poetry.

69
00:04:31,980 --> 00:04:33,000
Yeah, you're setting me up.

70
00:04:36,210 --> 00:04:39,630
I'm digging it. I haven't even I
only read the first line. I

71
00:04:39,630 --> 00:04:41,130
didn't know we started the show.
So

72
00:04:41,549 --> 00:04:44,459
yeah, we had a debate about
whether you could spell holistic

73
00:04:44,459 --> 00:04:47,669
with the nature of who we
neither one of us knew actually,

74
00:04:47,669 --> 00:04:48,239
we had to Google.

75
00:04:49,920 --> 00:04:52,230
Can I read this? Can I read
this? While you're looking that

76
00:04:52,230 --> 00:04:55,230
up? Can I just read this
paragraph? Go for it. Okay.

77
00:04:56,250 --> 00:05:00,690
Podcast index namespace, a
holistic RSS net namespace for

78
00:05:00,690 --> 00:05:04,320
podcasting. That is meant to
synthesize the fragmented world

79
00:05:04,320 --> 00:05:08,880
of podcast namespaces. The broad
goal is to create one namespace

80
00:05:08,880 --> 00:05:12,660
to rule them all. That is easily
extensible community controlled

81
00:05:12,660 --> 00:05:16,170
slash authored and addresses the
needs of the indie podcast

82
00:05:16,170 --> 00:05:21,210
industry now. And in the future.
The largest, the largest podcast

83
00:05:21,210 --> 00:05:24,270
platforms have shown virtually
no interest in extending their

84
00:05:24,270 --> 00:05:28,380
namespaces for new functionality
in many years. Our hope now,

85
00:05:28,380 --> 00:05:32,400
this will be our mission. Our
hope is that Yeah, can you is

86
00:05:32,430 --> 00:05:36,300
not allowed to change that or
Dahlia was I'll read it, I'll

87
00:05:36,300 --> 00:05:41,130
read it properly, then. Our
mission is that this is our

88
00:05:41,130 --> 00:05:43,890
mission is that this namespace
will become the framework for

89
00:05:43,890 --> 00:05:48,750
that in the podcast framework,
that a framework that the indie

90
00:05:48,750 --> 00:05:51,930
podcast community needs to
deliver new functionality to

91
00:05:51,930 --> 00:05:56,550
apps and aggregators. Do we like
the indie podcast moniker?

92
00:05:58,350 --> 00:06:00,930
I don't know. I mean, I tried to
set it apart from

93
00:06:03,270 --> 00:06:08,370
unaffiliated and affiliated or
is that too political? I don't

94
00:06:08,370 --> 00:06:12,780
know. Yeah. Maybe independent
just indie just you know, all of

95
00:06:12,780 --> 00:06:15,510
a sudden, you know, I gotta wear
black jeans have long black

96
00:06:15,510 --> 00:06:18,300
hair. I just don't I feel so emo
emo. That's what I

97
00:06:19,590 --> 00:06:21,480
put that in there. Okay, Emo
cross it up at

98
00:06:22,860 --> 00:06:24,540
the end. I think independent,

99
00:06:25,080 --> 00:06:26,700
independent or unaffiliated?

100
00:06:27,000 --> 00:06:30,450
I think independent independence
better. Independent,

101
00:06:30,780 --> 00:06:33,780
independent, because, yeah,
because they're in they're

102
00:06:33,780 --> 00:06:41,010
independent of any overlords,
they're part of the community.

103
00:06:42,630 --> 00:06:47,220
So the idea here is that this
whatever this is indie,

104
00:06:47,790 --> 00:06:52,620
independent, unaffiliated is
that this namespace is

105
00:06:52,620 --> 00:06:57,060
targeting, basically the whole
world of podcasting outside of

106
00:06:57,090 --> 00:07:00,990
really about three, right?
Google apple, and let's just say

107
00:07:00,990 --> 00:07:01,500
Spotify.

108
00:07:01,560 --> 00:07:04,140
Well, then why don't we just say
what it is the non corporate

109
00:07:04,140 --> 00:07:06,060
controlled asshole industry,

110
00:07:06,750 --> 00:07:12,450
as maths, a lot of work on many
words. Is your book your book

111
00:07:12,450 --> 00:07:12,870
fixing?

112
00:07:14,880 --> 00:07:17,550
Anyway, I love it, I totally
understand what it says.

113
00:07:18,960 --> 00:07:24,720
Yes, the idea is that those guys
don't even need. I mean, they

114
00:07:24,720 --> 00:07:27,930
don't really need a namespace
anyway. They can kind of do

115
00:07:28,290 --> 00:07:30,450
whatever they want in the
background. And however they

116
00:07:30,450 --> 00:07:31,380
want to do it. Yeah.

117
00:07:31,740 --> 00:07:34,830
Yeah, they Google has a copy of
the entire Internet. So I mean,

118
00:07:34,830 --> 00:07:39,120
like, what, what do they really
need? So, I mean, this is really

119
00:07:39,120 --> 00:07:46,290
meant to give people like Todd
Cochran at blueberry, like us,

120
00:07:47,430 --> 00:07:52,110
you know, like, fireside and
these guys that are trying to

121
00:07:53,100 --> 00:07:58,140
pull in, as well as other
podcast app developers who run a

122
00:07:58,140 --> 00:08:03,510
large back end. We're trying,
you know, we're trying to solve

123
00:08:03,510 --> 00:08:08,460
some problems and give new
functionality to apps. And they

124
00:08:08,460 --> 00:08:13,260
just the big guys just don't
seem interested in furthering

125
00:08:13,260 --> 00:08:14,220
this at all

126
00:08:14,340 --> 00:08:19,260
right, because they have zero
benefit to them. So, right,

127
00:08:19,679 --> 00:08:21,749
they'll just do some, they'll
just do something off on their

128
00:08:21,749 --> 00:08:28,109
own, and they don't really care
anymore. So this is meant to get

129
00:08:28,109 --> 00:08:32,459
the ball rolling, and to be a
central place where people can

130
00:08:32,459 --> 00:08:36,719
do pull requests can discuss.
I'm sure a lot of that will

131
00:08:36,719 --> 00:08:40,499
happen on podcast indexed by
social Putin. Basically, this is

132
00:08:40,499 --> 00:08:45,299
just the repository, go ahead
and fork it. And, you know,

133
00:08:45,719 --> 00:08:50,519
start playing around with with
your ideas. The thing, there's a

134
00:08:50,519 --> 00:08:55,049
couple of things I feel pretty
strongly about. And I can go Oh,

135
00:08:55,050 --> 00:09:00,180
yeah, yes, please. And so just
so I understand the process. So

136
00:09:00,180 --> 00:09:02,610
you can fork it in your own
GitHub, you can make changes,

137
00:09:02,610 --> 00:09:05,490
then you do a pull request,
which then means hey, I want

138
00:09:05,490 --> 00:09:08,700
this Incorporated. And then how
does that get decided what's

139
00:09:08,700 --> 00:09:09,270
pulled in?

140
00:09:10,260 --> 00:09:13,650
It? There's a couple of things
that can happen. It can, it can

141
00:09:13,650 --> 00:09:17,580
have conflicts with the existing
now, this is less likely on just

142
00:09:17,580 --> 00:09:20,400
documentation. But a typical
pull request can create a

143
00:09:20,400 --> 00:09:23,430
conflict with existing code and
other pull requests, and you

144
00:09:23,430 --> 00:09:27,630
have to basically decide who
wins or decide how to go about

145
00:09:27,630 --> 00:09:30,150
merging that in if it clobbers,
something else, that's

146
00:09:30,150 --> 00:09:33,720
important. But the other option
is that everything that the

147
00:09:33,720 --> 00:09:38,460
checks workout in there says
okay, this is fine. And then you

148
00:09:38,460 --> 00:09:40,890
just have to decide whether you
want to incorporate it or not.

149
00:09:40,890 --> 00:09:44,940
So there's a right you know, a
repository moderator or owner

150
00:09:45,390 --> 00:09:47,730
who makes a decision and you

151
00:09:49,050 --> 00:09:56,220
potentially have 1000s of what
are the individual items called?

152
00:09:56,760 --> 00:10:00,300
Elements, elements, so this
could have thought Dozens of

153
00:10:00,300 --> 00:10:03,090
elements ultimately. Is that not

154
00:10:03,960 --> 00:10:12,510
a bad idea? Yeah. Okay, that'd
be a bad idea. Okay. So just to

155
00:10:12,510 --> 00:10:15,720
go over the goals. You want me
to do that? Yeah. You want to

156
00:10:15,720 --> 00:10:16,140
read them off?

157
00:10:16,170 --> 00:10:17,700
I'll read them off. I'll read
them out. There's a good

158
00:10:17,700 --> 00:10:19,650
proofread at the same time. Have
you taken notes on those

159
00:10:19,650 --> 00:10:24,570
important changes? No, I got a
pencil. Go one. Eliminate

160
00:10:24,570 --> 00:10:27,600
redundancy. Do you mind if I
read it in the broadcast voice?

161
00:10:27,600 --> 00:10:28,530
Because I really

162
00:10:28,680 --> 00:10:30,960
think that would be that would
make my day. It would be

163
00:10:30,960 --> 00:10:31,440
wonderful.

164
00:10:32,130 --> 00:10:34,350
I'll do I'll kind of do
Attenborough if I can.

165
00:10:35,430 --> 00:10:38,580
Oh, is are there any other
creatures? Yes,

166
00:10:38,609 --> 00:10:41,369
there is significant overlap
amongst the many existing

167
00:10:41,399 --> 00:10:42,929
podcast namespaces.

168
00:10:44,520 --> 00:10:45,540
That is so pretty good.

169
00:10:46,590 --> 00:10:49,260
Each platform and public
publishers created their own

170
00:10:49,260 --> 00:10:51,900
namespace to give their
respective system and audience

171
00:10:51,990 --> 00:10:55,050
and audience the metadata they
need in the way they want it

172
00:10:55,050 --> 00:10:55,530
delivered.

173
00:10:56,490 --> 00:10:59,550
Yeah, so a good example of this
would be fireside what

174
00:10:59,550 --> 00:11:05,520
his fireside, fireside is the
podcast host. Yeah. Okay. So

175
00:11:05,520 --> 00:11:08,760
what have they put in? Their
stand? Benjamin? Right. Thanks.

176
00:11:08,760 --> 00:11:11,490
Yes. So what what has been put
in there that is?

177
00:11:12,180 --> 00:11:15,540
Well, they have a namespace,
okay. It's small. All right. And

178
00:11:15,600 --> 00:11:19,200
within this repository, you can
look at the existing namespaces

179
00:11:19,230 --> 00:11:23,310
dot txt file, and it shows a
list of them. That's, that was

180
00:11:23,310 --> 00:11:28,020
compiled by Christopher I seen
in the podcast.

181
00:11:28,050 --> 00:11:30,960
Oh, right. Right, right. Yeah,
he did for like the top 10 or

182
00:11:30,960 --> 00:11:31,770
top 20.

183
00:11:32,250 --> 00:11:35,730
I hate I think he had this list
is extensive. He sent me a

184
00:11:35,730 --> 00:11:39,810
bigger list. This got a lot of
them in there. So for instance,

185
00:11:39,810 --> 00:11:46,230
firesides namespace just has a
few extensions to it. We pull

186
00:11:46,230 --> 00:11:46,770
that out.

187
00:11:47,100 --> 00:11:50,550
And that's so that they can run
stats for their users and other

188
00:11:50,550 --> 00:11:51,540
things. Like,

189
00:11:52,620 --> 00:11:56,160
let me pull it up at transfer
case here. Yeah, well, these are

190
00:11:56,160 --> 00:12:02,760
hosts their extensions, our host
name, Gen date, player URL,

191
00:12:02,940 --> 00:12:08,490
player embed code. So I'm
thinking that that is most

192
00:12:08,490 --> 00:12:11,460
likely just a way for them to
track some of theirs. The

193
00:12:11,460 --> 00:12:15,330
hostname is a way for them to
figure out maybe if they have a

194
00:12:15,450 --> 00:12:20,340
server farm, which, which host
generated the RSS feed for Boca

195
00:12:20,340 --> 00:12:24,660
blog traffic tracking, and maybe
I'm just guessing and then the

196
00:12:24,660 --> 00:12:29,280
player URL that's probably a web
based, like player html5 player

197
00:12:29,280 --> 00:12:32,910
app. And then player embed code
is probably just a way for you

198
00:12:32,910 --> 00:12:33,660
as an iframe

199
00:12:33,660 --> 00:12:36,750
so so we would likely just take
these and put them right into

200
00:12:37,380 --> 00:12:38,370
the namespace.

201
00:12:39,570 --> 00:12:45,810
Yeah, that's. So that's one of
the next, let me get back over

202
00:12:45,810 --> 00:12:50,970
there. That's one of the next
goals listed. As goal, that's

203
00:12:50,970 --> 00:12:52,530
goal number five, so we'll get
there.

204
00:12:52,590 --> 00:12:56,970
All right, goal number two,
avoid attributes, attributes,

205
00:12:56,970 --> 00:13:00,570
and XML elements should be used
only when absolutely needed the

206
00:13:00,570 --> 00:13:03,300
preferences to create a new
element type, rather than reuse

207
00:13:03,300 --> 00:13:06,540
the same element with different
attributes. For example, instead

208
00:13:06,540 --> 00:13:10,830
of using podcast index colon,
image type equals large, we

209
00:13:10,830 --> 00:13:14,730
would use podcast index colon
image large, this makes the

210
00:13:14,730 --> 00:13:17,550
corresponding aggregator code
easier and more linear. I

211
00:13:17,550 --> 00:13:19,830
understand why that is. I got
that.

212
00:13:20,190 --> 00:13:23,640
And other people may not agree
with this. But my personal

213
00:13:23,640 --> 00:13:27,270
preference is always to just
have the the element with a

214
00:13:27,270 --> 00:13:32,190
value in it and avoid attributes
if at all possible. And the

215
00:13:32,190 --> 00:13:36,030
reason is just because it gets
messy, your code just has to dig

216
00:13:36,030 --> 00:13:40,560
in farther, lots of question
marks. Yeah, and the attributes

217
00:13:40,560 --> 00:13:44,460
can be, they can be hard to
handle like in the node, XML

218
00:13:44,460 --> 00:13:49,590
parser that we're using now.
It's, it can be a mess, to try

219
00:13:49,590 --> 00:13:52,680
to dig those attributes out. So
I would prefer to avoid them. I

220
00:13:52,680 --> 00:13:55,020
think it makes for easier,
easier code.

221
00:13:55,320 --> 00:14:00,180
Okay. All right. Goal number
three use RSS native elements.

222
00:14:00,600 --> 00:14:03,930
The RSS version 2.0
specification already has a

223
00:14:03,930 --> 00:14:07,140
robust set of defined elements,
we should aim to use those

224
00:14:07,140 --> 00:14:10,920
instead of creating new ones.
Instead of creating a podcast

225
00:14:11,040 --> 00:14:15,120
index colon owner element, we
can use the already existing

226
00:14:15,150 --> 00:14:18,630
Managing Editor element that can
contains both name and email

227
00:14:18,630 --> 00:14:21,690
address in situation like so
don't want to reinvent the wheel

228
00:14:21,720 --> 00:14:24,990
in situations like item level
images where the RSS spec never

229
00:14:24,990 --> 00:14:28,200
defined that element, it is
appropriate to define new ones.

230
00:14:29,010 --> 00:14:34,440
Yeah, and there's a lot of have
the RSS namespace or excuse me,

231
00:14:34,470 --> 00:14:40,530
the RSS spec. There's a lot of
that that is not used at all or

232
00:14:40,530 --> 00:14:45,210
properly. And one of them is the
managing editor is a good

233
00:14:45,210 --> 00:14:49,020
example of a tag that's just not
used. Often. Probably

234
00:14:49,020 --> 00:14:50,100
underutilized.

235
00:14:50,310 --> 00:14:52,530
underutilized. That's a better
term. Yeah, a better way to say

236
00:14:52,530 --> 00:14:54,900
it there and there's quite a few
of those that are that are

237
00:14:54,900 --> 00:14:58,320
underutilized like you know
there's one that we use in free

238
00:14:58,320 --> 00:15:01,380
control if Britain controller
that shows is the source of

239
00:15:01,380 --> 00:15:06,210
where you where that item came
from? Oh, okay. No. And yeah, we

240
00:15:06,210 --> 00:15:11,040
used it for some creative
purposes so that rather than

241
00:15:11,040 --> 00:15:16,380
reinventing the wheel here, it
makes sense to just use try to

242
00:15:16,380 --> 00:15:18,780
use what's already there as much
as possible.

243
00:15:18,900 --> 00:15:24,210
I agree. I mean, I, I kind of
vicariously went through RSS 1.0

244
00:15:24,210 --> 00:15:29,640
to 2.0 at a distance with Dave
Winer. That's that was quite an

245
00:15:29,640 --> 00:15:35,340
ordeal. That that was not not
to. Not pretty to watch,

246
00:15:35,340 --> 00:15:35,880
actually.

247
00:15:36,780 --> 00:15:38,460
Yeah, so a lot of fighting.

248
00:15:39,300 --> 00:15:43,230
Okay, goal number four keep
existing conventions. Oh, here

249
00:15:43,230 --> 00:15:46,080
we go. reinventing the wheel
helps nobody, when at all

250
00:15:46,080 --> 00:15:48,930
possible existing convention
should be maintained. For

251
00:15:48,930 --> 00:15:52,470
example, it would make sense to
turn podcast index colon

252
00:15:52,470 --> 00:15:59,880
explicit into it. unary element.
What's a unary? Like a single?

253
00:16:00,180 --> 00:16:03,090
Single operator? Oh, not binary.
But unary?

254
00:16:03,540 --> 00:16:06,840
Yeah. That may not be the
appropriate use of that word.

255
00:16:07,710 --> 00:16:09,720
I mean, I read it almost as
urinary so

256
00:16:14,640 --> 00:16:15,450
gotta get the bathroom.

257
00:16:16,500 --> 00:16:20,520
Okay, adjectives are involving a
single component or element, a

258
00:16:20,520 --> 00:16:23,010
beautiful, beautiful word. I'm
going to use this in regular

259
00:16:23,010 --> 00:16:23,700
language.

260
00:16:24,390 --> 00:16:27,990
Okay, I just sound appropriate.
You think that's right. I mean,

261
00:16:27,990 --> 00:16:32,490
basically, what it would mean is
like, the element is there for a

262
00:16:33,030 --> 00:16:35,130
while it it goes on to say if
you want to keep reading,

263
00:16:35,220 --> 00:16:38,280
okay, so it turns it into a
unary element, where its

264
00:16:38,280 --> 00:16:42,090
existence is taken as a yes. And
its absence as a no. Yeah,

265
00:16:42,120 --> 00:16:44,790
totally makes sense. You don't
have it in there. It's just off.

266
00:16:45,150 --> 00:16:48,840
You put it in there. You can
switch it on. Yeah. But that has

267
00:16:48,840 --> 00:16:53,400
never been the standard. Oh, and
we need sound effects for this.

268
00:16:57,210 --> 00:17:00,120
Since we're messing around
anyway. Okay. Let me reread

269
00:17:00,120 --> 00:17:07,140
that. So for example, it would
make sense to turn podcasts

270
00:17:07,140 --> 00:17:11,100
index colon explicit into a
unary element where it's existed

271
00:17:11,100 --> 00:17:15,150
is taken its existence is taken
as a yes. And its absence as a

272
00:17:15,150 --> 00:17:17,580
no. But that has never been the
standard.

273
00:17:21,030 --> 00:17:21,870
Long way to get

274
00:17:23,700 --> 00:17:27,810
to early, given us how this
namespace will probably sit

275
00:17:27,840 --> 00:17:31,260
alongside at least one other
namespace. It makes sense to

276
00:17:31,260 --> 00:17:34,680
keep existing conventions in
place. And I agree.

277
00:17:34,919 --> 00:17:37,979
Yes, we just don't want to. We
don't want to have to reach out

278
00:17:37,979 --> 00:17:41,669
to people and expect stuff to
work already. Yeah. Basically,

279
00:17:41,669 --> 00:17:41,939
that

280
00:17:42,030 --> 00:17:45,900
we want people to just upgrade
for more fun and valuable cash

281
00:17:45,900 --> 00:17:46,800
and prizes.

282
00:17:47,070 --> 00:17:50,130
Yeah, that's, that's there you
go. And there's there's a cash

283
00:17:50,130 --> 00:17:51,630
and presence element. Oh, nice.

284
00:17:52,080 --> 00:17:56,910
Oh, number five, the general,
there's no way to address every

285
00:17:56,910 --> 00:18:01,050
possible metadata point at each
platform would want. That is not

286
00:18:01,050 --> 00:18:04,110
the aim. Instead, we focus on
defining the elements that would

287
00:18:04,110 --> 00:18:07,440
be useful to the broadcast set
of apps, publishers, platforms

288
00:18:07,440 --> 00:18:10,200
and aggregators. Individual
parties can keep their

289
00:18:10,200 --> 00:18:13,380
respective supplemental
namespaces small and targeted as

290
00:18:13,380 --> 00:18:15,480
an adjunct to this larger
namespace.

291
00:18:16,110 --> 00:18:19,500
Okay, yes. So the example of the
fireside

292
00:18:19,530 --> 00:18:22,290
that's kindly do say that small,
they don't necessarily have to

293
00:18:22,290 --> 00:18:23,850
put it in. Yeah, we

294
00:18:23,850 --> 00:18:26,790
don't have to try to reinvent
what or we don't have to try to

295
00:18:26,790 --> 00:18:31,170
incorporate what fireside is
doing in our in this broader

296
00:18:31,170 --> 00:18:35,220
namespace because there's always
going to be like this one

297
00:18:35,250 --> 00:18:38,340
fireside colon host name. And
element is something that

298
00:18:38,340 --> 00:18:42,900
probably nobody else wants or
needs, but then, right, so it

299
00:18:42,900 --> 00:18:46,170
doesn't make any sense to try to
stick that in here. And when

300
00:18:46,170 --> 00:18:50,010
they can just their namespaces
small, and they can just include

301
00:18:50,010 --> 00:18:52,590
their own route beside it. I
mean, you can have 25 namespaces

302
00:18:52,590 --> 00:18:56,850
in an in an XML document if you
want. So that's fine. We don't

303
00:18:56,850 --> 00:18:59,430
we don't want I'm trying to say
is that we don't have to take

304
00:18:59,520 --> 00:19:02,940
every existing namespace that's
out there and take all the tags

305
00:19:02,940 --> 00:19:04,260
and shove them all into this
one.

306
00:19:04,679 --> 00:19:08,099
I wouldn't mind doing a podcast
called namespace of the week,

307
00:19:08,099 --> 00:19:09,899
and we just read through a
namespace,

308
00:19:10,320 --> 00:19:11,790
oh, my God, that would be
horrible.

309
00:19:14,310 --> 00:19:16,650
Bear that in mind as we continue
reading this one,

310
00:19:17,010 --> 00:19:18,540
never another donation.

311
00:19:19,890 --> 00:19:22,620
So then you have the element
list. And I can

312
00:19:22,620 --> 00:19:26,040
go through this if you want me
to. Yeah, it might be quicker

313
00:19:26,040 --> 00:19:34,770
that way. So one thing that J.
James Crillon has mentioned a

314
00:19:34,770 --> 00:19:40,170
couple of times, is the ability
to specify different size images

315
00:19:40,380 --> 00:19:45,360
in the in the RSS. So that's
what these these first three are

316
00:19:45,360 --> 00:19:48,570
image, large image, medium image
small, and there's some pixel

317
00:19:48,570 --> 00:19:52,890
width definitions in there about
what suggested and it's

318
00:19:52,890 --> 00:19:57,210
basically just to give hints to
the player or app or whatever of

319
00:19:57,210 --> 00:20:01,620
how to what you want to grab
first Should be pretty self

320
00:20:01,620 --> 00:20:07,290
explanatory. Now the categories,
but I don't I'll say this

321
00:20:07,320 --> 00:20:13,380
upfront, I don't expect that
everybody is going, I would be

322
00:20:13,380 --> 00:20:15,570
naive to think that everybody
would ditch the existing

323
00:20:15,570 --> 00:20:17,820
categories that are out there in
podcasts and start using

324
00:20:17,820 --> 00:20:20,460
podcasts index categories.
That's really not what not what

325
00:20:20,460 --> 00:20:24,390
this is for. It's basically,
we're going to be consuming

326
00:20:24,390 --> 00:20:28,800
these, these namespaces. Also,
we're already set up to handle

327
00:20:28,800 --> 00:20:31,680
what's out there already. But as
far as,

328
00:20:32,820 --> 00:20:36,750
right, we can display everything
that's already in a namespace

329
00:20:36,750 --> 00:20:38,070
pretty much, right? We

330
00:20:38,070 --> 00:20:42,720
can, yeah, so this is basically
just our category name names, I

331
00:20:42,720 --> 00:20:46,860
like them. I think our category
list works well. So this is just

332
00:20:47,130 --> 00:20:51,960
a way for, to I'm just putting
in there to be used whatever.

333
00:20:53,610 --> 00:20:57,990
The now Now we'll start to get
into some, which I think I feel

334
00:20:57,990 --> 00:21:05,460
pretty strongly about location.
Spotify has a country of origin

335
00:21:05,490 --> 00:21:11,040
tag in their namespace. And that
when I read through their

336
00:21:11,040 --> 00:21:15,810
namespace, that seems to be the
only serious contribution that

337
00:21:15,810 --> 00:21:19,770
they've made, as far as that,
that their namespace goes

338
00:21:19,770 --> 00:21:23,070
everything else. I think there's
not really much there. But the

339
00:21:23,070 --> 00:21:29,280
look, location tag could be a
country code and a locality. So

340
00:21:29,280 --> 00:21:37,110
something like us, Alabama, or
Brazil, Rio, like you could have

341
00:21:37,980 --> 00:21:40,410
in a separate about pipe
character, since that'll never

342
00:21:40,410 --> 00:21:44,550
really be an existing character
in the language. So that's,

343
00:21:44,580 --> 00:21:48,540
that's my idea for that. Again,
I think the tag is important.

344
00:21:48,840 --> 00:21:53,010
But how its font had the final
implementation of it is very

345
00:21:53,010 --> 00:21:54,690
much open to the community to
decide.

346
00:21:55,260 --> 00:22:00,030
Right? You know, what have those
really funny? What is it called

347
00:22:00,030 --> 00:22:06,960
the I should know this. I'm a
general license. That Maidenhead

348
00:22:06,960 --> 00:22:11,760
grid square locator. What is
that? A Maidenhead grid square

349
00:22:11,760 --> 00:22:19,320
locator? So, I'm going to enter
my zip code. And I'll enter my

350
00:22:19,320 --> 00:22:21,510
and why they didn't want my
callsign I don't think I need

351
00:22:21,510 --> 00:22:28,410
it. But I see. Okay, zip code.
We'll just work on that. So my

352
00:22:28,740 --> 00:22:36,180
my Maidenhead grid locator is e
m 10 D, F. And it's an area of

353
00:22:36,210 --> 00:22:39,750
not quite sure what how big the
area is. But it's big enough to

354
00:22:39,750 --> 00:22:46,740
obfuscate where I live, except
the.is. Right in the middle. It

355
00:22:46,740 --> 00:22:49,500
did not. It doesn't. That's not
good. That's not disclosing my

356
00:22:49,500 --> 00:22:51,870
address. But you look at the
middle of the square like yeah,

357
00:22:51,870 --> 00:22:56,760
that's where I am. So you could
also offset it. But what I like

358
00:22:56,760 --> 00:22:59,760
about it is that it's this is
well known. There's tons of

359
00:22:59,760 --> 00:23:03,900
API's on the internet is ham
radio that invented this. And

360
00:23:03,900 --> 00:23:06,150
I'm sure that Well, I'm sure
it's from something what is it?

361
00:23:06,150 --> 00:23:09,060
Maidenhead grid square locator?
I'm sure you've never heard of

362
00:23:09,060 --> 00:23:10,590
this. No, no, I

363
00:23:10,590 --> 00:23:11,700
have no idea what this is.

364
00:23:11,730 --> 00:23:16,890
Yeah, it's, it's been used ever
since. Then, if there's a wiki

365
00:23:16,890 --> 00:23:21,420
page about it, here we go.
Maidenhead locator system is a

366
00:23:21,420 --> 00:23:25,170
geographic coordinate system
used by amateur radio operators.

367
00:23:25,710 --> 00:23:32,400
What's its history? I guess it
was an amateur radio. came from

368
00:23:32,400 --> 00:23:36,480
the German cure a locator
system. And then they had they

369
00:23:36,480 --> 00:23:40,350
had the working group meeting in
Maidenhead England. Okay. Okay,

370
00:23:40,380 --> 00:23:43,890
so there you go. But, okay,
Maidenhead locator compresses

371
00:23:43,890 --> 00:23:46,710
latitude and longitude into a
short string of characters,

372
00:23:46,710 --> 00:23:50,070
which is similar in concept to
the world geographic reference

373
00:23:50,070 --> 00:23:55,230
system. Except it's really easy
to do, but it uses uppercase

374
00:23:55,230 --> 00:23:56,970
lowercase. I don't know if
that's a problem.

375
00:23:57,840 --> 00:24:02,520
Shouldn't be Yeah, anyway, and I
know that it's a good idea.

376
00:24:03,030 --> 00:24:06,090
The bottom line is when the
apocalypse comes.

377
00:24:07,830 --> 00:24:11,040
Where you're gonna say the world
namespace is gonna save the

378
00:24:11,040 --> 00:24:11,310
world.

379
00:24:12,120 --> 00:24:17,310
Where was that? Where was that
drop? I had this somewhere. Save

380
00:24:17,310 --> 00:24:21,210
was it save the world? Save the
world.

381
00:24:23,610 --> 00:24:25,710
I just sent you clips, by the
way. Oh, thank you. Now

382
00:24:25,710 --> 00:24:30,870
here we have ham radio, guys.
Ham radio is the public service

383
00:24:30,900 --> 00:24:36,120
network of last resort, when the
apocalypse comes where the guys

384
00:24:36,120 --> 00:24:37,800
who are going to save the world.

385
00:24:37,800 --> 00:24:41,220
Right, right. So at least we'll
know where the nodes are and

386
00:24:41,220 --> 00:24:44,100
where people are and where the
podcasts are.

387
00:24:44,490 --> 00:24:47,130
When you go into a car when you
go into a conference in the

388
00:24:47,130 --> 00:24:49,170
keynote starts and that's what
the guest sounds like do you

389
00:24:49,170 --> 00:24:51,930
just do you just kind of like
hope put your head down and your

390
00:24:51,930 --> 00:24:52,380
hands

391
00:24:53,370 --> 00:24:57,720
I'm all jacked. I'm like, yeah,
yeah, we're gonna save the

392
00:24:57,720 --> 00:25:04,290
world, man. Hell yeah, we're all
Remember, the ham radio guys are

393
00:25:04,290 --> 00:25:07,080
really frustrated firemen and
EMTs basic.

394
00:25:09,000 --> 00:25:12,450
I've got that I had a ham radio
license. Got it in high school,

395
00:25:12,450 --> 00:25:17,490
there's a well known High
School, it was eighth grade, we

396
00:25:17,490 --> 00:25:25,920
had a class at my junior high
called consumer electronics. And

397
00:25:25,950 --> 00:25:32,460
they present it consumer. No,
no, I'm sorry. Consumer Science,

398
00:25:32,640 --> 00:25:35,550
I think is what it was called
some crazy name that didn't have

399
00:25:35,550 --> 00:25:37,770
anything to do with what we
actually did this, the first

400
00:25:37,770 --> 00:25:42,240
like, the first half of the year
was aerospace, which was fine.

401
00:25:42,450 --> 00:25:46,230
And the second half of the year
was get your podcast and get

402
00:25:46,230 --> 00:25:50,220
your ham radio license. And so
we like the whole second half of

403
00:25:50,220 --> 00:25:52,500
the year for like, I think it
was like fifth period during the

404
00:25:52,500 --> 00:25:55,710
day, we would just get in there
and just be CQ, and and learn

405
00:25:55,710 --> 00:25:58,770
and, you know, learn Morse code
and the whole nine yards. And

406
00:25:58,770 --> 00:26:03,450
then at the end of the year, we
all our teacher was the proxy,

407
00:26:03,450 --> 00:26:07,320
and he gave us the test. That
was fun. All right, very clever

408
00:26:07,320 --> 00:26:10,080
ham radio license it like, I
don't know what I was, like 15

409
00:26:10,080 --> 00:26:11,190
or 14, like that

410
00:26:11,250 --> 00:26:13,560
back in the day you had to code
back then probably had to be

411
00:26:13,560 --> 00:26:15,120
able to do code. Yeah, it

412
00:26:15,120 --> 00:26:17,370
wasn't real fast that I just
did. I was

413
00:26:17,490 --> 00:26:22,980
12 words a minute guy. Yeah, I
haven't seen your clips yet. But

414
00:26:22,980 --> 00:26:24,630
maybe it's going through the
pipes.

415
00:26:25,350 --> 00:26:34,110
Okay, it's just as the Okay, so
the next tag is the one that I

416
00:26:34,110 --> 00:26:38,850
think are the next group is one
I think is really important. So

417
00:26:38,850 --> 00:26:44,340
it's, it's the locked tag, yes
or no. And I'll just read the

418
00:26:44,340 --> 00:26:46,680
description. This is a channel
level element. This tells other

419
00:26:46,680 --> 00:26:50,250
podcast platforms, whether they
are allowed to import this feed.

420
00:26:50,730 --> 00:26:54,960
A value of yes means that any
attempt to import this feed into

421
00:26:54,960 --> 00:26:58,350
a new platform should be
rejected. It is expected that

422
00:26:58,350 --> 00:27:02,280
podcast hosting providers will
enable a toggle in their duty to

423
00:27:02,280 --> 00:27:07,680
allow their users to turn feed
transfer log on or off. And so I

424
00:27:07,680 --> 00:27:13,710
think this is a way to directly
combat feed import fraud. The

425
00:27:13,710 --> 00:27:16,800
same way that pod news exposed
this past week with anchor.

426
00:27:17,550 --> 00:27:20,550
Right, right, right. Everybody
knew it was going on. But he

427
00:27:20,730 --> 00:27:23,520
just laid it out. Here's it,
here's exactly how you do it and

428
00:27:23,520 --> 00:27:29,100
exactly how easy it is. So if we
have a lock, element locked

429
00:27:29,130 --> 00:27:30,630
element in the feed,

430
00:27:31,920 --> 00:27:34,440
then it should not be allowed to
import and what do you think we

431
00:27:34,440 --> 00:27:36,390
have to make sure Ankur adopts
that?

432
00:27:36,960 --> 00:27:41,670
Well, that's that's why I think
this is so important is because

433
00:27:42,450 --> 00:27:45,840
if as long as there's nothing
out there to actually no formal

434
00:27:45,840 --> 00:27:50,250
spec to stop it, there's no way
to really shame them other than

435
00:27:50,250 --> 00:27:53,790
just doing what what the what
Panis did, and just publishing,

436
00:27:54,000 --> 00:27:57,990
you know, articles about it. But
if if there's a formal spec that

437
00:27:57,990 --> 00:28:03,480
says, This is your, I've chosen
not to allow you to import this,

438
00:28:03,870 --> 00:28:08,250
and you do it anyway. You're,
you're sending a clear message

439
00:28:08,250 --> 00:28:10,980
to everybody. You're just
basically flipping the middle

440
00:28:10,980 --> 00:28:17,520
finger to the whole to the whole
industry, and the shame gets you

441
00:28:17,760 --> 00:28:22,710
10x That's my fate. I mean,
there's a if everybody says,

442
00:28:22,710 --> 00:28:26,340
Yeah, we agreed to adopt this
standard, and you don't, you're

443
00:28:26,340 --> 00:28:32,730
a douche. Yeah, I mean, really,
because it's not it's not like

444
00:28:32,730 --> 00:28:40,260
it's a like, debatable thing. If
I if I say if I put in my feed,

445
00:28:41,010 --> 00:28:46,350
transfer a lot. Yes. And I that
I'm clearly telling you not to

446
00:28:46,410 --> 00:28:51,810
not to clone my feed. Right, if
you do it anyway. He be your,

447
00:28:52,320 --> 00:28:54,990
you know, you're just given me
the middle finger.

448
00:28:55,290 --> 00:28:58,800
Should we consider naming this?
I mean, it's this document

449
00:28:58,800 --> 00:29:03,930
called podcast index namespace.
Yeah. Now, should we consider

450
00:29:03,930 --> 00:29:06,030
just calling it podcast
namespace?

451
00:29:07,320 --> 00:29:10,020
That's fine. Yeah, that'd be
fine with me. Let's do that.

452
00:29:10,620 --> 00:29:12,210
Just change it to podcast. Yes.

453
00:29:12,240 --> 00:29:16,710
We seem more independent that
way. We are. We actually, and

454
00:29:16,710 --> 00:29:20,340
the whole thing is independent.
That's the point. That I think

455
00:29:20,340 --> 00:29:23,520
that's a lot better. Because if
it says Spotify namespace, I'd

456
00:29:23,520 --> 00:29:24,180
be like, nope.

457
00:29:24,870 --> 00:29:27,720
Yeah, me too. I think that's
great. Because this this really

458
00:29:27,720 --> 00:29:29,910
is the community's namespaces

459
00:29:29,940 --> 00:29:34,590
Yeah, exactly. Exactly. Okay.
And I totally agree on that. So

460
00:29:34,590 --> 00:29:39,090
And moreover, for that very
reason, is it's one thing to say

461
00:29:39,090 --> 00:29:41,670
well, the podcast index
namespace says nothing to say,

462
00:29:41,670 --> 00:29:46,470
Dude, bro. The podcast namespace
says this. So you got to start

463
00:29:46,950 --> 00:29:49,020
rejecting those feeds anchor.

464
00:29:50,070 --> 00:29:52,350
Yeah, that's that's a good
that's a good point. Because

465
00:29:52,350 --> 00:29:54,000
it's just from the naming
standpoint. That's

466
00:29:54,000 --> 00:29:56,490
also I'm really good at shaming
once I have the ammunition.

467
00:29:57,690 --> 00:30:00,600
Yeah, I know where I'm looking.
forward to it.

468
00:30:01,260 --> 00:30:05,490
Okay, we got locked. And so
there's a couple of tags that

469
00:30:05,490 --> 00:30:13,320
kind of go with that. And this
may seem redundant. But I feel

470
00:30:13,320 --> 00:30:17,160
like it's necessary. The next
one is, is, let's just call it

471
00:30:17,160 --> 00:30:22,890
podcast colon email. And that is
a channel level element, an

472
00:30:22,890 --> 00:30:25,800
email address that can be used
to verify ownership of the feed

473
00:30:26,100 --> 00:30:29,640
during a move and import or
import operations. This could be

474
00:30:29,670 --> 00:30:32,070
a public email or a virtual
email address that the hosting

475
00:30:32,070 --> 00:30:35,340
provider that redirects to the
owners true email address. So

476
00:30:36,480 --> 00:30:39,810
this goes along with the
transfer lock or the import

477
00:30:39,810 --> 00:30:43,860
lock. Right? Yeah. And you're
gonna, you're giving an email

478
00:30:43,860 --> 00:30:47,850
address, this says, If you want
to communicate with me, for

479
00:30:47,850 --> 00:30:51,540
tech, about doing something with
my feed,

480
00:30:51,720 --> 00:30:54,900
just how you just like domain
registration.

481
00:30:55,680 --> 00:31:00,540
Yeah, exactly. Like I can go in,
you could say that you can say

482
00:31:00,540 --> 00:31:02,520
that's redundant, because
there's there's iTunes owner

483
00:31:02,520 --> 00:31:04,440
email. There's many Yeah, but

484
00:31:04,590 --> 00:31:07,890
but that could be important for
a number of reasons. One for

485
00:31:09,750 --> 00:31:12,330
it's just two different roles, I
guess. I mean, it's just like

486
00:31:12,360 --> 00:31:15,240
DNS registration, you have
administrative financial

487
00:31:15,240 --> 00:31:18,450
general. So yeah, that made
those roles are understood, I

488
00:31:18,450 --> 00:31:18,780
think,

489
00:31:19,170 --> 00:31:23,730
I think if there's a new
element, specifically targeted

490
00:31:23,730 --> 00:31:30,120
at this, then what's out there
already is a mishmash of, of

491
00:31:30,750 --> 00:31:33,900
people's actual, some of them
are actual email addresses, like

492
00:31:33,900 --> 00:31:37,350
in the owner email. And some of
them are just kind of throw, you

493
00:31:37,350 --> 00:31:39,660
can tell they're just kind of
junk. If this if there's

494
00:31:39,660 --> 00:31:43,530
something new going in, like
this namespace, you could say,

495
00:31:43,530 --> 00:31:49,710
Okay, this is for this reason.
And this is your chance to plant

496
00:31:49,710 --> 00:31:53,880
your flag and put a put an
actual contact address in this

497
00:31:53,880 --> 00:31:57,990
this little achieve this goal,
right. So I think I think it's

498
00:31:57,990 --> 00:32:01,590
worth having that redundancy in
there. And it could even be

499
00:32:01,590 --> 00:32:03,780
change, it doesn't even have to
be email can be changed to be

500
00:32:03,780 --> 00:32:09,450
something like podcast colon
contact, and that could be

501
00:32:09,450 --> 00:32:13,020
either an email address or a URL
to the at the hosting provider

502
00:32:13,020 --> 00:32:17,100
who, you know, who knows that's,
we can debate this, which is

503
00:32:17,100 --> 00:32:24,990
fine by me. The next one is
previous URL. And I feel like

504
00:32:24,990 --> 00:32:31,710
this is a really good idea to
the previous URL tag contains,

505
00:32:32,520 --> 00:32:36,480
there can be as many of these as
needed. And every time that a

506
00:32:36,480 --> 00:32:41,190
podcast moves from one URL to
the next, it should add a

507
00:32:41,190 --> 00:32:46,260
previous URL tag, an additional
previous URL tag to the channel.

508
00:32:47,370 --> 00:32:51,750
That will it operates like an
email header, wait email,

509
00:32:52,139 --> 00:32:59,039
does that allow for archives? Or
am I just Well, no, it'll

510
00:32:59,040 --> 00:33:04,260
it allows you to associate a pre
what, what a previous Feed URL

511
00:33:04,260 --> 00:33:06,990
with its new one, so that you
can deduplicate got

512
00:33:06,990 --> 00:33:09,030
it? Ah, okay. Understood.

513
00:33:09,480 --> 00:33:15,300
Yeah. So somebody moves from
blueberry to to Lipson, and they

514
00:33:15,300 --> 00:33:18,060
don't, and they don't actually
do it, they don't do a 301. And

515
00:33:18,060 --> 00:33:21,870
they don't tell anybody, right,
they can just, yeah, you end up

516
00:33:21,870 --> 00:33:24,990
with two feeds. And it takes you
a long, it may take you a long

517
00:33:24,990 --> 00:33:27,690
time to figure out that those
that the old one is dead now,

518
00:33:27,690 --> 00:33:32,040
right? This, this lets you say,
Look, if this podcast were to

519
00:33:32,040 --> 00:33:36,360
happen, were to pop from host to
host, maybe five times, adding

520
00:33:36,360 --> 00:33:40,320
all these previous URLs would
would let you always deduplicate

521
00:33:40,320 --> 00:33:42,390
and remove those old URLs from
your feed.

522
00:33:42,420 --> 00:33:43,800
Great. That's great.

523
00:33:45,690 --> 00:33:51,270
The new feed URL, again, it may
seem redundant, because Google's

524
00:33:51,300 --> 00:33:56,610
namespace has a new feed URL
tag, and also iTunes has a new

525
00:33:56,610 --> 00:34:00,750
feed URL tag, but they don't
match. Don't use the same

526
00:34:00,750 --> 00:34:04,800
format. And so since we're
already sort of in this mindset,

527
00:34:04,890 --> 00:34:10,140
it makes sense to me to put a
new feed URL into formally into

528
00:34:10,140 --> 00:34:14,820
something called the podcast
namespace, right. Okay. Yeah.

529
00:34:14,820 --> 00:34:20,310
And then here's another one that
I think some people have wanted.

530
00:34:20,400 --> 00:34:27,420
And I think it's a good idea is
the podcast, colon ID. Now, if

531
00:34:27,420 --> 00:34:32,940
you just leave, if you don't put
a platform in a platform

532
00:34:32,940 --> 00:34:36,930
attribute, if you just put in
podcast that the podcast colon

533
00:34:36,930 --> 00:34:42,240
ID, and then the value is a is a
number, it's assumed to be the

534
00:34:42,240 --> 00:34:47,700
podcast index ID, right? If you
put in platform equals, then you

535
00:34:47,700 --> 00:34:51,000
can, there's some listed down in
the further in the document, you

536
00:34:51,000 --> 00:34:55,980
could put in the slug of
whatever your provider is. And

537
00:34:56,190 --> 00:35:00,960
then you can put not just your
provider so let's say Now that

538
00:35:01,650 --> 00:35:08,880
you're listed on blueberries
directory, us, Google Play, and

539
00:35:10,260 --> 00:35:13,860
iTunes, you could put all your
IDs on those respective.

540
00:35:14,250 --> 00:35:15,450
Oh, good, good.

541
00:35:15,450 --> 00:35:19,110
I like that one for each. And
that's another way that we can

542
00:35:19,140 --> 00:35:22,500
that aggregators can be signaled
to can be given good information

543
00:35:22,500 --> 00:35:23,520
to deduplicate. Now,

544
00:35:23,520 --> 00:35:26,970
will you rename all these
elements as well, to podcast

545
00:35:26,970 --> 00:35:30,060
colon location? Does that
conflict with other namespaces?

546
00:35:30,210 --> 00:35:33,450
No, it doesn't. Okay, cool. It
does. I don't I don't think as

547
00:35:33,450 --> 00:35:36,330
far as I know, I don't think
there is a podcast namespace.

548
00:35:36,330 --> 00:35:41,460
Okay. Well, one, just called cod
puck. Okay, cool. So those are

549
00:35:41,460 --> 00:35:45,090
the those are the elements that
that I felt were good to start

550
00:35:45,090 --> 00:35:50,370
with. And I really feel like the
transfer locking in that. And

551
00:35:50,370 --> 00:35:57,930
the tracking ones are, are good
will would give good new ammo to

552
00:35:57,930 --> 00:36:02,460
the podcasting world. As well as
to aggregators and app

553
00:36:02,460 --> 00:36:07,080
developers. The now there's some
that I know that people have

554
00:36:07,080 --> 00:36:10,770
wanted, and I didn't know enough
detail about it. So I just kind

555
00:36:10,770 --> 00:36:13,500
of sketched them out real quick.
And that's in the element. List

556
00:36:13,500 --> 00:36:14,550
proposal section.

557
00:36:14,580 --> 00:36:18,120
Right? We have captions,
transcripts and alternate

558
00:36:18,120 --> 00:36:22,140
enclosure. Yeah. It's also nice.
That's so that's where you can

559
00:36:22,140 --> 00:36:27,510
do alternative like IPFS, or
some other beat torrent, or

560
00:36:27,510 --> 00:36:31,320
different bit rates? Oh, yeah.
Nice. Yeah. Nice. Nice. Nice.

561
00:36:31,710 --> 00:36:33,690
And I think that's one that
James one of the captions and

562
00:36:33,690 --> 00:36:37,470
transcripts are one that Todd
Everbloom wanted. And there's

563
00:36:37,470 --> 00:36:40,920
been a few other people piping
up to do like things like

564
00:36:40,920 --> 00:36:46,710
chapters. There's plenty of
ideas out there. And so what I

565
00:36:46,710 --> 00:36:49,860
would say is, let's just, let's
start this discussion. Let's

566
00:36:49,860 --> 00:36:53,190
start hammering on this thing
and try to get something. Let's

567
00:36:53,190 --> 00:36:54,690
try to get something good put
together.

568
00:36:54,900 --> 00:36:55,860
That's a lot of work.

569
00:36:57,000 --> 00:37:00,300
Yeah. Yeah, it's, you know,

570
00:37:01,050 --> 00:37:04,530
I think that how do I help you
drive this? How do I help just

571
00:37:04,530 --> 00:37:08,790
by? Yeah, how do I help you
drive it get people to

572
00:37:08,820 --> 00:37:18,540
participate? Firearms or can?
Poison poisoning? Threat of

573
00:37:18,540 --> 00:37:19,170
poisoning?

574
00:37:19,440 --> 00:37:22,200
Yeah. Yeah. You never know when
it's gonna happen. So I mean,

575
00:37:22,200 --> 00:37:26,910
you better get on board. I think
just just talking about it. And

576
00:37:27,180 --> 00:37:35,040
if, really, if we can get the
podcast, news guys and the in

577
00:37:35,040 --> 00:37:38,460
the podcast platforms, on board,
luckily, we already have

578
00:37:38,460 --> 00:37:41,580
connections with quite a few of
those guys. Yeah, guys. Good.

579
00:37:42,150 --> 00:37:45,150
Yeah, we could we can just get
this out there. Because I think,

580
00:37:45,510 --> 00:37:50,820
what would the feeling that I
get is that everybody has wanted

581
00:37:50,820 --> 00:37:54,480
this to happen for a long time.
But there's never been a single

582
00:37:54,480 --> 00:37:57,600
entity that's tried to pull it
all together. Yeah, everybody

583
00:37:57,600 --> 00:37:58,410
did the same table.

584
00:37:58,440 --> 00:38:01,440
Yeah, that seems to be a lot of
consensus about that, which I

585
00:38:01,440 --> 00:38:05,130
love that because that's exactly
what we have. We've got to an

586
00:38:05,130 --> 00:38:08,640
actual community, people who
care and when people care and

587
00:38:08,640 --> 00:38:10,680
other people show up who care
stuff gets done, and I

588
00:38:10,680 --> 00:38:12,240
definitely see stuff getting
done.

589
00:38:13,290 --> 00:38:17,790
Podcast index dot social has
become as much about general

590
00:38:17,790 --> 00:38:22,050
podcast technology techno
technology needs as it has about

591
00:38:22,080 --> 00:38:23,160
the API's. So

592
00:38:23,670 --> 00:38:28,800
absolutely. And there's such a
good mix of people. A really

593
00:38:28,800 --> 00:38:33,030
good mix of people have all
kinds of ideas. I'm I'm just

594
00:38:33,030 --> 00:38:38,190
blown away by it every single
time. And just all these me and

595
00:38:38,190 --> 00:38:43,410
everyone has. I can also see a
lot of frustrations from for a

596
00:38:43,410 --> 00:38:47,130
long living frustrations that
people are like, Oh, fuck,

597
00:38:47,130 --> 00:38:52,290
someone wants to listen. Just
listen to me. I like it. I

598
00:38:52,290 --> 00:38:57,000
really do. It was actually it
was quite nice listening to Todd

599
00:38:57,030 --> 00:39:03,240
and Rob on the media show where
they I don't think I've ever had

600
00:39:03,240 --> 00:39:06,210
that done where I did an
interview and then the same host

601
00:39:06,210 --> 00:39:08,190
went back and analyze the
interview.

602
00:39:09,330 --> 00:39:11,670
It was kind of necessary I'm
glad they did it.

603
00:39:12,390 --> 00:39:15,360
Yeah, I'm super happy they did
it because it also taught me

604
00:39:15,360 --> 00:39:22,110
something that I guess I maybe I
come across as a raving lunatic

605
00:39:22,110 --> 00:39:25,560
sometimes to some people when I
could Yeah, I'm always in my

606
00:39:25,560 --> 00:39:29,070
head. I'm visualizing everything
and and it just comes out of

607
00:39:29,070 --> 00:39:31,740
that little a lot of like
diarrhea of the mouth just flows

608
00:39:31,740 --> 00:39:35,130
out for like, why is he talking
about?

609
00:39:35,370 --> 00:39:39,240
Did you get the clips? Did you
get this close? Second? Because

610
00:39:39,270 --> 00:39:41,370
I've got some good diarrhea of
the mouth in there.

611
00:39:41,460 --> 00:39:47,310
Oh, nice. No, I don't have them.
Well, they bounced backwards.

612
00:39:47,370 --> 00:39:50,850
You know, I have a limit on my
mail server. wouldn't think so.

613
00:39:52,200 --> 00:39:56,910
Yes, pretty small. Anyway, weird
wonder why they addressed it to

614
00:39:56,910 --> 00:40:00,600
you again. We just got a big
donation by the way. $100

615
00:40:00,630 --> 00:40:01,620
Oh my goodness.

616
00:40:02,070 --> 00:40:05,790
I don't know if this person
wants it read

617
00:40:05,820 --> 00:40:09,090
though. So maybe we can use your
first name only?

618
00:40:09,990 --> 00:40:14,130
Yeah. And then I'll email them
and see if it's okay to mention

619
00:40:14,130 --> 00:40:15,030
on the next show.

620
00:40:16,379 --> 00:40:18,659
Now, are you emailing from your
regular account? You know, I

621
00:40:18,659 --> 00:40:21,299
have pretty strict rules demark
and all that stuff.

622
00:40:21,749 --> 00:40:25,709
And mail from my podcast index
account. I should probably do

623
00:40:25,709 --> 00:40:26,639
that from just do

624
00:40:26,640 --> 00:40:29,460
it from the Gmail, we know that
for us. Yeah. Okay, because

625
00:40:29,970 --> 00:40:33,960
there's something with the with
the demark records on on the

626
00:40:33,960 --> 00:40:37,320
emails because I'm, I'm getting
all kinds of I haven't really

627
00:40:37,320 --> 00:40:39,210
looked at it. I'm getting like
errors.

628
00:40:39,959 --> 00:40:43,829
Or you get, like killed on that
flood.

629
00:40:44,430 --> 00:40:49,590
Yeah, yeah, I got a serious mail
email attack, not a bomb and

630
00:40:49,590 --> 00:40:52,680
attack. And it was just that
long was like, couple months

631
00:40:52,680 --> 00:40:59,280
ago. Yes, five months ago. And
I've just got 10s of 1000s of

632
00:40:59,310 --> 00:41:04,500
emails a minute, but all
subscribing me to stuff and oh

633
00:41:04,500 --> 00:41:08,550
my god, it was a nightmare.
Thank God for Mark void zero.

634
00:41:08,970 --> 00:41:13,170
who rescued me. They put the
clamps down on that thing, too.

635
00:41:13,170 --> 00:41:16,470
Yeah. Well, he's an email expert
that that's actually what he

636
00:41:16,470 --> 00:41:19,110
loves. And he's so proud of his
email. He's always been trying

637
00:41:19,110 --> 00:41:22,200
to get me on his on his servers
and like, gotta migrate all that

638
00:41:22,200 --> 00:41:26,010
shit. And now it was Do or die.
And he said, All right, man. I'm

639
00:41:26,010 --> 00:41:29,430
cool. And he's got it locked. I
mean, people were trying to send

640
00:41:29,430 --> 00:41:35,910
me email from their from the
Apple Mac dot Mac account or

641
00:41:35,910 --> 00:41:40,050
what I iCloud account, and
somewhere so some SMTP server

642
00:41:40,050 --> 00:41:44,940
had showed up on a UBL. And
yeah, like, well, Apple should

643
00:41:44,940 --> 00:41:47,760
know this. But all right, I'll
put an exception for them.

644
00:41:48,540 --> 00:41:51,270
So do I have the hot pipe? Does
it come straight 3d If I get

645
00:41:51,270 --> 00:41:55,500
from my Gmail? Oh, yeah. Yeah,
yeah. So you do alright. Yeah.

646
00:41:55,500 --> 00:41:56,970
Okay. I just I just recently got
him.

647
00:41:56,970 --> 00:42:00,330
Okay. Yeah, that went through.
We got we got to figure that

648
00:42:00,330 --> 00:42:03,960
out. There's some some
misconfiguration with where

649
00:42:03,960 --> 00:42:04,800
we're using Mailgun.

650
00:42:06,510 --> 00:42:10,080
on ours, now we're using
FastMail. Okay, for podcast

651
00:42:10,080 --> 00:42:19,830
index.org. So that's pretty much
the namespace. And I want to I

652
00:42:19,830 --> 00:42:24,060
wanted to just give everybody
enough to get them started. And

653
00:42:25,080 --> 00:42:28,230
the, there's a couple of other
things in there. There's the

654
00:42:28,230 --> 00:42:31,590
categories, dot json file,
likes, that's just a list of our

655
00:42:31,590 --> 00:42:34,230
categories. I'm not concerned
about category stuff, just don't

656
00:42:34,230 --> 00:42:41,340
even worry about that. Example.
dot XML is just an example feed

657
00:42:41,340 --> 00:42:45,150
that shows our namespace or
excuse me, the podcast

658
00:42:45,150 --> 00:42:48,510
namespaces. We're going to
rename it shows the podcast

659
00:42:48,510 --> 00:42:52,290
namespace living side by side
with the iTunes namespace. It

660
00:42:52,290 --> 00:42:57,300
just gives a good visual example
of how this stuff would look in

661
00:42:57,300 --> 00:43:02,070
practice. Excellent. Thank feed
an owl, we'll say this. So it's

662
00:43:02,070 --> 00:43:08,370
assumed I needed some some kind
of like, fake ish, real world.

663
00:43:10,080 --> 00:43:14,760
Stuff to stick in there. So I'll
put in the podcast, podcast

664
00:43:14,760 --> 00:43:18,360
colon email address, I put like
a what would be kind of like a

665
00:43:18,360 --> 00:43:22,050
virtual blueberry address. So
it's assumed that this podcast

666
00:43:22,050 --> 00:43:26,100
is being hosted on bluebridge
Picton Got it. Got it. Anyways,

667
00:43:26,280 --> 00:43:27,990
that's namespace Yeah,

668
00:43:27,990 --> 00:43:32,520
like it was and just dropped out
of the blue. But I think it was

669
00:43:32,520 --> 00:43:34,830
time you were talking last
night. Like now I'm gonna do

670
00:43:34,830 --> 00:43:38,820
this namespace. See, I think
with by changing the podcast,

671
00:43:39,390 --> 00:43:42,540
namespace and changing all the
element names, I think that'll

672
00:43:42,540 --> 00:43:45,690
just make it even more clear.
What we're trying to do here.

673
00:43:46,350 --> 00:43:49,080
That's, that's a great idea. I
think that's that's exactly what

674
00:43:49,080 --> 00:43:49,620
we need to say, well,

675
00:43:49,620 --> 00:43:53,820
these are the things that I went
through with the RSS 1.0 to 2.0.

676
00:43:54,750 --> 00:43:58,800
That they you gotta yeah,
there's people get. There's no

677
00:43:58,800 --> 00:44:02,010
context in text often,
especially not computer code.

678
00:44:02,610 --> 00:44:07,650
Yeah, you know, so every colon
every word is, is important.

679
00:44:07,710 --> 00:44:13,770
I've learned a lot of coders
take language very literal.

680
00:44:14,880 --> 00:44:15,810
Yeah, you have to.

681
00:44:16,170 --> 00:44:20,250
Yeah, here's a strong, there's a
strong Asperger's element to a

682
00:44:20,250 --> 00:44:21,570
lot of programmers. Yeah.

683
00:44:22,200 --> 00:44:26,940
Yes. It's. And I was just
thinking about this last night.

684
00:44:27,870 --> 00:44:31,140
I had a company that 700
employees, we had a lot of

685
00:44:31,380 --> 00:44:37,080
coders and the overlap between
musicians and people who write

686
00:44:37,080 --> 00:44:42,420
code is very strong. And you and
I were talking about our talking

687
00:44:42,420 --> 00:44:45,210
about something last night and
we're, you've been doing this

688
00:44:45,210 --> 00:44:49,650
for 22 years. And we're talking
about some some kid whose first

689
00:44:49,650 --> 00:44:54,060
project took off as like, now he
helped coders truly are like

690
00:44:54,060 --> 00:45:02,400
musicians. You can be working
now the gigs haircut for a long

691
00:45:02,400 --> 00:45:05,460
time, you can get a good
corporate gig, you know, play

692
00:45:05,460 --> 00:45:09,150
in, in the theater, whatever it
is, it's all kind of the same

693
00:45:09,150 --> 00:45:09,570
thing.

694
00:45:10,170 --> 00:45:14,160
Programming is such, you said
this before, a dozen times that

695
00:45:14,160 --> 00:45:17,220
programming is as much as much
art as it is.

696
00:45:17,549 --> 00:45:21,629
copes. Yeah. Which is why, you
know, when I do it, it looks

697
00:45:21,629 --> 00:45:22,739
like I'm finger painting

698
00:45:24,330 --> 00:45:28,110
me to have you got you know, and
that's the thing, it's like you,

699
00:45:28,230 --> 00:45:31,320
nobody's going to use your
nobody's going to use your

700
00:45:31,320 --> 00:45:35,310
software because the code is so
beautiful. Yeah, but that's just

701
00:45:35,310 --> 00:45:38,250
not there. Like, oh my God, look
how pretty that code is. I'm

702
00:45:38,250 --> 00:45:42,690
going to use this product. No,
you use the product because it

703
00:45:42,690 --> 00:45:45,750
meets your needs. Right. And,
and it and it does it in a way

704
00:45:45,750 --> 00:45:51,570
that this satisfying to you. But
But the the code itself is a is

705
00:45:51,570 --> 00:45:56,610
an aspect of the it reflects the
programmer, it reflects who he

706
00:45:56,610 --> 00:46:01,050
or she is. And you can, you
know, you can just you can see a

707
00:46:01,050 --> 00:46:03,960
certain style in a certain
person and it just is fairly

708
00:46:03,960 --> 00:46:07,050
consistent. Like a signature,
you know, that.

709
00:46:07,440 --> 00:46:08,430
Right, right.

710
00:46:08,459 --> 00:46:09,449
Did you get those clips?

711
00:46:10,020 --> 00:46:11,070
I did? I certainly do.

712
00:46:11,669 --> 00:46:19,709
Which one was it? Okay, so this
is funny. I think Ralphie

713
00:46:19,709 --> 00:46:21,929
dropped his new version of cast
cover. Yes,

714
00:46:21,960 --> 00:46:24,900
it looks beautiful cast
coverage.com That thing is

715
00:46:24,900 --> 00:46:29,940
fantastic. I switched it to
Dutch language. Yeah, just going

716
00:46:29,940 --> 00:46:32,610
through hidden through Dutch
podcasts, like, you know, I

717
00:46:32,610 --> 00:46:37,110
speak Dutch fluently. And I have
no idea what's out there. And

718
00:46:37,110 --> 00:46:40,200
all of a sudden, I'm getting it
random is very nice experience.

719
00:46:40,800 --> 00:46:46,050
Is, is there a okay, I'm not
bilingual. So when you're

720
00:46:46,080 --> 00:46:48,090
listening to some, let's just
say you're listening to

721
00:46:48,090 --> 00:46:52,320
somebody, something in English,
and then it flips, like

722
00:46:52,320 --> 00:46:58,410
immediately to, to Dutch. Does
your does your brain? Does it

723
00:46:58,410 --> 00:47:01,050
take a second to adjust? Or is
it just an automatic?

724
00:47:01,500 --> 00:47:08,010
almost automatic? Now, of
course, it depends how recently

725
00:47:08,010 --> 00:47:12,690
I've been using it. But I read
that I read a lot of Dutch just

726
00:47:12,690 --> 00:47:16,260
for news flow and people who
send me stuff. And I and I

727
00:47:16,260 --> 00:47:18,690
remember when I was a kid, we
moved there and it took me a

728
00:47:18,690 --> 00:47:20,820
while I was translating, you
know, translate from Dutch to

729
00:47:20,820 --> 00:47:24,360
English in my head. And now it's
just that those, you know, it's

730
00:47:24,360 --> 00:47:29,100
just talking straight to the
API. It's going right right in

731
00:47:29,100 --> 00:47:31,860
there right to the brainstem?
Yeah, it's very, it's very cool

732
00:47:31,860 --> 00:47:39,780
that way, and I will also you
know, I will take on that it's

733
00:47:39,780 --> 00:47:42,510
hard to say but like the whole
feeling of because, you know,

734
00:47:42,540 --> 00:47:45,030
Dutch is different. The Dutch
have different culture. You

735
00:47:45,030 --> 00:47:47,430
know, like, I immediately want
to wear my wooden shoes, you

736
00:47:47,430 --> 00:47:50,280
know, it's like that kind of
idea. I feel that I really do.

737
00:47:50,280 --> 00:47:51,270
It's very interesting.

738
00:47:51,900 --> 00:47:55,590
Oh, that is interesting. So you
so it's, it's as much if it hits

739
00:47:55,590 --> 00:47:59,160
you with a feel as much as it
does with the the understanding

740
00:47:59,160 --> 00:48:02,760
Absolutely. And if I if I hear
someone speak it on television,

741
00:48:02,850 --> 00:48:06,000
or in a movie, and it's actual
Dutch because a lot of it is

742
00:48:06,000 --> 00:48:10,800
really just an actor who kind of
learned it phonetically it Yeah,

743
00:48:10,800 --> 00:48:15,660
it's vibe. It's I immediately am
transported as I said API

744
00:48:15,660 --> 00:48:17,130
straight to the to the
brainstem.

745
00:48:18,120 --> 00:48:22,800
Hit play a cast coverage, I'm
not ashamed. And I'm gonna tell

746
00:48:22,800 --> 00:48:26,580
the whole world I'm not ashamed
of the gospel.

747
00:48:26,610 --> 00:48:33,300
Nice. I'm not ashamed of the
gospel. Wait a minute, is that

748
00:48:33,300 --> 00:48:38,850
Reverend Manning? I don't know
who that is. That's all hell

749
00:48:39,330 --> 00:48:40,950
break loose and you're gonna
need a Bitcoin.

750
00:48:42,120 --> 00:48:45,000
It sounds a lot like it does. It
does. That's

751
00:48:45,000 --> 00:48:46,470
great. I love that one.

752
00:48:46,560 --> 00:48:49,440
Ralphie dropped the link to the
new cast coverage in the in the

753
00:48:49,440 --> 00:48:53,070
mastodon and I clicked on it and
hit go. And that is the it

754
00:48:53,070 --> 00:48:55,770
started right there at that
exact moment.

755
00:48:56,190 --> 00:48:58,170
One more time for the
experience. And I'm gonna tell

756
00:48:58,170 --> 00:49:00,750
the whole world I'm not ashamed

757
00:49:00,750 --> 00:49:07,620
of the gospel. Glory, ashamed of
the gospel.

758
00:49:09,330 --> 00:49:12,360
Nice. Yeah. That's an
experience.

759
00:49:12,480 --> 00:49:15,240
That's I mean, talk about a
product launch.

760
00:49:17,910 --> 00:49:21,810
And I tweeted out a link that
had been updated. And someone

761
00:49:21,810 --> 00:49:24,630
said, Hey, drop me right in the
middle of the podcast. I think I

762
00:49:24,630 --> 00:49:28,170
like it. So yeah, that's, that's
by design, man. And it's true.

763
00:49:28,170 --> 00:49:31,290
Because if you're just sampling
podcast, you're starting with

764
00:49:31,290 --> 00:49:36,390
ads or you're starting with due
to someone's opening music,

765
00:49:36,390 --> 00:49:40,320
you're waiting half an hour. I
think that that's, that's a user

766
00:49:40,320 --> 00:49:43,320
who put something together that
the user wanted, and it makes

767
00:49:43,320 --> 00:49:45,900
sense for everybody. I think
it's great.

768
00:49:46,230 --> 00:49:50,490
I was I got an email this
morning about this new podcast

769
00:49:50,490 --> 00:49:53,700
from a quote unquote, podcast,
which is really not one from

770
00:49:53,700 --> 00:50:01,710
Audible, some kind of self help
podcast, and so the First, like

771
00:50:01,710 --> 00:50:04,920
literally like the first 45
seconds to a minute of it is

772
00:50:04,920 --> 00:50:09,450
just the work is some do some
bit a bit of background of like,

773
00:50:09,480 --> 00:50:12,090
you know, non offensive
background music. And then it's

774
00:50:12,090 --> 00:50:16,410
like, you know, hey, this is our
new podcast, where, during this

775
00:50:16,410 --> 00:50:19,050
podcast, we're going to explore
these ideas and this and this

776
00:50:19,050 --> 00:50:21,240
and this. And here's the bubble
blah, blah, blah. I mean, he was

777
00:50:21,240 --> 00:50:25,890
like, 30 to 45 seconds. So just,
yeah, I already know all this.

778
00:50:25,890 --> 00:50:30,390
That's why I clicked on it like
that. That is the quickest way

779
00:50:30,390 --> 00:50:33,180
to get somebody uninterested in
your show is to tell them all

780
00:50:33,180 --> 00:50:36,990
about your show. Yeah, before,
man before I actually do it

781
00:50:39,030 --> 00:50:41,670
skips all that cast cover just
like Yeah, screw that. We're

782
00:50:41,670 --> 00:50:45,840
just gonna straight to the
middle. Yeah, anyway, so that

783
00:50:46,110 --> 00:50:51,690
that's kind of where we're at on
the namespace. I think it's, I

784
00:50:51,750 --> 00:50:53,220
think we'll see what happens. I
like

785
00:50:53,220 --> 00:50:56,910
it. I like it a lot. Now, let's
see, we had put my own notes

786
00:50:56,910 --> 00:51:03,510
here. Well, gosh, why don't we
Why don't we thank people who

787
00:51:03,510 --> 00:51:06,060
donated and then we'll move on
to the next. There's a couple

788
00:51:06,060 --> 00:51:08,640
more things that we should touch
on today. Yeah, sure.

789
00:51:10,800 --> 00:51:11,790
Let's see here.

790
00:51:12,840 --> 00:51:15,870
While you're looking at Apple,
just say that the entire project

791
00:51:15,870 --> 00:51:20,580
podcast index.org Is, is built
around the value for value

792
00:51:20,580 --> 00:51:24,420
concept you get out of it, what
you put into it. And we are

793
00:51:24,420 --> 00:51:28,860
always looking for time, talent,
treasure. So obviously, we're

794
00:51:28,860 --> 00:51:32,310
putting a lot of that in
ourself. But so many people have

795
00:51:32,310 --> 00:51:34,920
understood this and are
supporting it. It's really

796
00:51:34,920 --> 00:51:40,380
fantastic. And it's it sets us
up as a as a culture in the

797
00:51:40,380 --> 00:51:45,090
community for what's coming, you
know, true true value transfer

798
00:51:45,090 --> 00:51:47,940
to everybody involved. And so
just to be able to do this to

799
00:51:47,940 --> 00:51:51,120
get it started not to have come
out of our own pockets. Although

800
00:51:51,120 --> 00:51:55,050
of course, we were always
perfectly willing to. To do that

801
00:51:55,050 --> 00:51:59,940
if necessary, is very, very
heartwarming, and every single

802
00:51:59,940 --> 00:52:02,940
person who supports it, not just
with finances, but with your

803
00:52:02,940 --> 00:52:05,340
time and your talent and what
we're all building here is so

804
00:52:05,340 --> 00:52:10,650
incredibly appreciated. It's I
had I have not been this

805
00:52:10,650 --> 00:52:18,900
excited. Since I first used
gopher in that, I'm telling you,

806
00:52:18,900 --> 00:52:19,260
that'd be

807
00:52:19,260 --> 00:52:24,000
nice. Yeah, then this side is on
first use Gopher,

808
00:52:24,240 --> 00:52:27,060
it is truly that exciting. I
mean, there are a number of very

809
00:52:27,060 --> 00:52:30,690
exciting moments but it's the
feeling really is coming back

810
00:52:30,690 --> 00:52:33,900
and this kind of unknown and,
and you're working with people

811
00:52:33,900 --> 00:52:38,730
who you know from a handle or an
icon or, and it's all kind of

812
00:52:38,730 --> 00:52:42,270
the same goal. It's a very good
energy very, very appreciative

813
00:52:42,300 --> 00:52:46,230
of what will go I love I love
this. I really do. And we love

814
00:52:46,230 --> 00:52:50,610
the people who help us and all
you have to do is to support us

815
00:52:50,610 --> 00:52:54,900
is click on the donate button on
podcast index.org It's also on

816
00:52:54,900 --> 00:52:58,380
the developer site, and whatever
you get out of it, you know just

817
00:52:58,380 --> 00:53:00,510
whatever it's worth to you
however you want to support it.

818
00:53:00,690 --> 00:53:03,720
We do of course have our special
feature where you can be named

819
00:53:03,720 --> 00:53:06,450
with a recurring donation a
server will be named after you

820
00:53:08,640 --> 00:53:12,480
tweeted out the hilarious.

821
00:53:13,650 --> 00:53:18,990
So, you know Benjamin nastic
donated $500 Just like 30

822
00:53:18,990 --> 00:53:23,490
minutes ago. Oh, Mike, I'm just
gonna say Benjamin. The message

823
00:53:23,490 --> 00:53:26,400
just says, David Adam, you're
doing great work. keep on keepin

824
00:53:26,400 --> 00:53:27,930
on. That's the whole message.

825
00:53:27,959 --> 00:53:29,219
Thank you so much Benjamin.

826
00:53:30,000 --> 00:53:35,010
I mean, like, they Benjamin gets
like the whole the whole rack

827
00:53:39,090 --> 00:53:42,390
you make whatever decisions you
have to when you said that, like

828
00:53:42,390 --> 00:53:44,760
this is such a great idea. And
I'm glad you're going to manage

829
00:53:44,760 --> 00:53:48,570
it. Yeah. You're gonna need a
spreadsheet brother.

830
00:53:48,990 --> 00:53:52,440
Yeah, I'm gonna manage this by
not managing it. All right. Very

831
00:53:52,440 --> 00:53:58,020
good. Just ignore it for now.
Benjamin bake. Yes, yes. Okay.

832
00:53:58,590 --> 00:54:05,760
And see get a subscription at
$50 a month. Wow. Nice from pod

833
00:54:05,760 --> 00:54:06,270
verse.

834
00:54:07,200 --> 00:54:08,430
Cool. Very cool.

835
00:54:09,000 --> 00:54:09,870
Yeah, that's

836
00:54:10,830 --> 00:54:12,810
that's to servers. Servers.

837
00:54:13,650 --> 00:54:17,580
is Mitch and the guys over there
at pod verse nice and says

838
00:54:17,880 --> 00:54:20,370
they don't do they have a
website up yet for pod verse?

839
00:54:20,580 --> 00:54:22,590
Yeah. What is their URL?

840
00:54:22,980 --> 00:54:28,830
It's a pod verse.fm I think Oh,
that's right. FM. Lisa, here on

841
00:54:28,890 --> 00:54:29,610
verse.

842
00:54:29,640 --> 00:54:34,680
I also saw that we got baked
into podcast addict as a choice.

843
00:54:35,490 --> 00:54:38,670
Oh, yeah. I saw that pop up. It
kind of came out of the blue.

844
00:54:40,560 --> 00:54:46,170
I think someone Someone did a
pull request. I don't know who I

845
00:54:46,170 --> 00:54:47,850
presume someone from the index

846
00:54:48,540 --> 00:54:51,090
is podcast addict. Is that an
open source project?

847
00:54:52,020 --> 00:54:57,840
I think so. They have their own.
They have their own index. I

848
00:54:57,840 --> 00:55:02,910
know I know that and then Uh, in
the past couple of weeks, I've

849
00:55:02,910 --> 00:55:06,150
seen them say, oh, you know, we,
we have our own index, but that

850
00:55:06,150 --> 00:55:10,770
someone created the code or did
whatever and nice. I haven't

851
00:55:10,770 --> 00:55:14,520
it's now it's pod verse running
on entirely on the index or is

852
00:55:14,520 --> 00:55:16,110
it running off of a multiple?

853
00:55:16,560 --> 00:55:18,120
Now it's working on the index?
Really?

854
00:55:18,150 --> 00:55:21,090
I haven't. I haven't promoted
this.

855
00:55:21,450 --> 00:55:25,380
Well, I'll, I'll read the note.
Okay. All right. Let's see. So

856
00:55:25,380 --> 00:55:29,940
pod verse, you're gonna get the,
you're gonna get the master API.

857
00:55:30,630 --> 00:55:33,090
Server. Thanks. Nice, nice.

858
00:55:33,510 --> 00:55:35,850
The for the front end, you're
gonna get one of the front end

859
00:55:35,850 --> 00:55:39,630
servers. I wanted to assist.
Hey, guys want to let you know

860
00:55:39,630 --> 00:55:44,070
that the monthly donation is
from pot verse in my team,

861
00:55:46,080 --> 00:55:50,130
Korea, Korea, and I think that
you named Kreon, Gary and Kyle.

862
00:55:50,760 --> 00:55:53,580
Dave, thanks for the absurdly
fast turnaround on the Recently

863
00:55:53,580 --> 00:55:56,700
Updated podcast and point
overnight by integrating this

864
00:55:56,700 --> 00:55:59,760
endpoint with our own feed
parsing system, we can now

865
00:55:59,760 --> 00:56:03,810
expand our database from 100,000
to a million podcast at no extra

866
00:56:03,810 --> 00:56:07,710
cost to us. Wow. Yeah, while
simultaneously reducing our

867
00:56:07,710 --> 00:56:13,140
servers CPU usage from 80% to
20%. And allowing our system to

868
00:56:13,140 --> 00:56:17,250
detect podcast updates faster as
a floor wax

869
00:56:17,250 --> 00:56:19,440
and a dessert topping, ladies
and gentlemen.

870
00:56:21,630 --> 00:56:24,930
As a small open source project,
savings like these are a game

871
00:56:24,930 --> 00:56:27,300
changer for our ability to
scale. And we couldn't do it

872
00:56:27,300 --> 00:56:30,210
without y'all. It's amazing.
It's amazing how much value you

873
00:56:30,210 --> 00:56:32,550
in the podcast in this community
have created in just over a

874
00:56:32,550 --> 00:56:34,710
month. Thanks again for the
incredible work you're doing

875
00:56:34,710 --> 00:56:35,220
Mitch.

876
00:56:35,460 --> 00:56:36,120
Oh, man, he's

877
00:56:36,120 --> 00:56:40,350
so nice. Yeah, he gave me like a
graph of their server stats. He

878
00:56:40,350 --> 00:56:42,600
says we switched to the new
endpoint two days ago and their

879
00:56:42,600 --> 00:56:46,620
server their server usage went
from 80% to like, a cliff.

880
00:56:46,680 --> 00:56:50,070
Oh my god. That's so cool. This
is a nice little project that

881
00:56:50,070 --> 00:56:51,930
got here to nice little

882
00:56:51,930 --> 00:56:54,960
player. It's got the clips you
can make clips with.

883
00:56:55,050 --> 00:57:00,810
Oh, that's right. Okay. Oh,
nice. Oh, contextual menu. like

884
00:57:00,810 --> 00:57:02,670
crap, man. This is nice.

885
00:57:02,850 --> 00:57:05,880
If you go to the clips thing,
like there's some pretty good

886
00:57:05,880 --> 00:57:11,160
clips on there. It's pretty
neat. I spent some time on there

887
00:57:11,160 --> 00:57:11,820
yesterday.

888
00:57:12,210 --> 00:57:15,360
Ha. And you can just make your
own clips.

889
00:57:16,200 --> 00:57:19,560
It looks like it. There's like a
there's some controls down there

890
00:57:19,560 --> 00:57:22,470
at the bottom like a scissor.
got scissors.

891
00:57:22,920 --> 00:57:26,190
Yeah. Look at this. Holy crap.

892
00:57:26,370 --> 00:57:27,360
Cut it up, man.

893
00:57:28,440 --> 00:57:33,180
This is good. I gotta I gotta
share this right away to the

894
00:57:33,180 --> 00:57:33,720
world.

895
00:57:34,350 --> 00:57:39,390
One thing I don't know, Mitch in
the guys is, can you when you

896
00:57:39,390 --> 00:57:42,390
make a clip? Can you share that
back out as its own as a

897
00:57:42,390 --> 00:57:47,100
defense? Oh, I think so. I'm
what I'm tweeting is pod verse

898
00:57:47,100 --> 00:57:49,410
let you make clips and share
them. So they better have it in

899
00:57:49,410 --> 00:57:54,900
there. Because I'm just I'm just
promoted. Now. All right.

900
00:57:55,740 --> 00:58:05,400
All right. Thanks. Thanks, guys.
Cameron rose. See, he did a $25

901
00:58:05,400 --> 00:58:10,260
a month subscription. Cameron.
Nice. You are going to get the

902
00:58:11,970 --> 00:58:14,760
you're gonna get the images, the
new images server that is not

903
00:58:14,760 --> 00:58:22,440
even 100%. Oh, yeah. Okay. So
Cameron sent $25 A month says,

904
00:58:22,440 --> 00:58:24,720
Hi, David. Adam, thanks for
taking this project on free

905
00:58:24,720 --> 00:58:28,560
speech is always needed is
always in native defenders. And

906
00:58:28,560 --> 00:58:31,560
I think that podcasts are a
critical vector for that. I

907
00:58:31,560 --> 00:58:34,140
agree that providing a structure
for others to build from is the

908
00:58:34,140 --> 00:58:36,630
right direction rather than
trying to dictate and in

909
00:58:36,630 --> 00:58:41,460
product. Totally agree. Adam, as
much as you seem to disdain

910
00:58:41,460 --> 00:58:46,800
Scott Adams, some sort of
cartoonist. I think he's very

911
00:58:46,800 --> 00:58:49,800
right. And that one should
always aim for that one should

912
00:58:49,800 --> 00:58:53,040
always aim for systems, not
goals. And this would be a good

913
00:58:53,040 --> 00:58:55,260
display of just that. I'm
excited to see what comes out of

914
00:58:55,260 --> 00:58:55,680
it all.

915
00:58:55,800 --> 00:58:59,610
Hey, I love Scott Adams. I have
no, we were just joking around

916
00:58:59,700 --> 00:59:02,850
on the show about him. Yeah, I'm
sure I'm sure this is tongue in

917
00:59:02,850 --> 00:59:03,480
cheek too.

918
00:59:03,930 --> 00:59:07,800
Yeah. If the subscription is
enough for a server naming it is

919
00:59:07,950 --> 00:59:13,170
Please assign it to my company
to be Omp tech. Alright. Say

920
00:59:13,170 --> 00:59:16,920
Yeah, sure. Absolutely. We'll do
that. I'd also like to support

921
00:59:16,920 --> 00:59:20,340
and rewrites Adams suggestion in
the last cast about the critical

922
00:59:20,340 --> 00:59:23,520
importance of owning and using
public domain names. I know a

923
00:59:23,520 --> 00:59:26,250
lot of people look down on the
expanded list of TLDs available,

924
00:59:26,250 --> 00:59:28,350
but I've come around to them and
it greatly expands the

925
00:59:28,350 --> 00:59:31,050
opportunities for the Average
Joe Joe to find something they

926
00:59:31,050 --> 00:59:32,160
like. I agree with that

927
00:59:32,160 --> 00:59:35,460
too. What exactly are you saying
here?

928
00:59:36,210 --> 00:59:39,510
The TLD like the new TLDs like I
like.io.

929
00:59:39,660 --> 00:59:43,980
Oh, the top level domains? Yeah.
Oh, yeah. Like, yeah, sure. Did

930
00:59:43,980 --> 00:59:45,750
I say I didn't like those two
that make him

931
00:59:45,930 --> 00:59:48,300
think he's just making a comment
for I think he's just making

932
00:59:48,300 --> 00:59:49,230
that comment himself.

933
00:59:49,530 --> 00:59:52,800
I totally like it. They're
expensive though. Some of them

934
00:59:52,800 --> 00:59:55,260
really thinking you know,
because of just how it works.

935
00:59:55,800 --> 00:59:58,260
Doesn't it take like 100 grand
out of the gate to start one of

936
00:59:58,260 --> 00:59:59,430
those? A

937
00:59:59,430 --> 01:00:02,760
TLD I looked into it when I
didn't pursue it when I should

938
01:00:02,760 --> 01:00:06,000
have, you know, that was around
the time that GoDaddy guy

939
01:00:06,000 --> 01:00:08,880
figured it out. And it just
wasn't. It wasn't a business I

940
01:00:08,880 --> 01:00:11,610
was interested in. But at the
time, you could do it. You had

941
01:00:11,610 --> 01:00:15,720
to have some guarantee. I don't
know if 100 grand or not, but it

942
01:00:15,720 --> 01:00:16,890
was not a big hurdle.

943
01:00:17,910 --> 01:00:20,970
Like WordPress to get from
WordPress, they started the dot

944
01:00:20,970 --> 01:00:21,930
blog domain.

945
01:00:22,350 --> 01:00:25,230
Yeah, that's right, Matt. Yeah.
Yeah.

946
01:00:25,890 --> 01:00:28,890
And I think, I think I want to
say it was like, 100 grand. I

947
01:00:28,890 --> 01:00:29,610
don't know. That's,

948
01:00:30,120 --> 01:00:33,270
that's possible. But that's
right for him. You know, man, I

949
01:00:33,270 --> 01:00:36,750
would hate to have to run that
business. Yeah. Oh, my God.

950
01:00:36,750 --> 01:00:40,470
You're what you're dealing with
all day? Yeah. Takedown request,

951
01:00:40,470 --> 01:00:47,700
DMCA? FBI. That's MSLs. National
Security Letters.

952
01:00:47,730 --> 01:00:50,940
You bet. Oh, yeah. And you can't
even talk about it. No. Kidding

953
01:00:50,940 --> 01:00:56,490
bitch about it. No. Se is no
agenda stream. Is no agenda

954
01:00:56,490 --> 01:00:59,370
stream really so much better
than no agenda dot stream? I

955
01:00:59,370 --> 01:01:03,090
guess he's talking about TLDs is
if there's any way you can

956
01:01:03,090 --> 01:01:05,790
utilize domain names to confirm
feed off authenticity, I would

957
01:01:05,790 --> 01:01:08,010
recommend it. No need to
reinvent the wheel red

958
01:01:08,010 --> 01:01:14,340
checkmarks here because that's
funny. Yes, that'd be that.

959
01:01:14,400 --> 01:01:15,630
Thanks, Kathy. Thank

960
01:01:15,630 --> 01:01:21,600
you so much. Let's see like this
paper crumbling sound effect

961
01:01:21,600 --> 01:01:24,990
you're doing? That's that's
working for me. And it's a nice

962
01:01:25,080 --> 01:01:26,790
transition between donations.

963
01:01:27,060 --> 01:01:32,700
I'm a I'm a complete Luddite. I
print everything. That's cool.

964
01:01:33,150 --> 01:01:36,000
Yeah, I mean, like, I will print
it. I will literally print out

965
01:01:36,000 --> 01:01:38,400
an email and then walk over to
the printer and grab it and read

966
01:01:38,400 --> 01:01:41,820
it off off the paper. Oh, one
paragraph? Oh, that's an

967
01:01:41,820 --> 01:01:46,770
extreme. Sometimes. I mean, not
all the time. Looking at the

968
01:01:46,770 --> 01:01:50,400
screen all day just drives my
eyes crazy. Yeah. It's just it

969
01:01:50,400 --> 01:01:57,180
just gives me a break. Cold acid
from the rare encounter podcasts

970
01:01:57,300 --> 01:02:01,290
is the new subscription for $10
a month. Thank you. Thanks.

971
01:02:01,290 --> 01:02:05,910
Cool. And now you're gonna get
aggregator five. All right.

972
01:02:06,720 --> 01:02:11,400
Thank you cold acid. Appreciate
it. And Mitch. coming in again,

973
01:02:11,400 --> 01:02:15,240
Mitch. Mitch is out of control.
He's just throwing piles of cash

974
01:02:15,240 --> 01:02:19,710
at Mitch from pod verse. I think
so. Mitch. Mitch. Mitch down.

975
01:02:19,920 --> 01:02:21,030
Give us 10 bucks.

976
01:02:21,060 --> 01:02:22,110
Right. Nice.

977
01:02:22,140 --> 01:02:26,730
They just, yeah. Yeah, Mitch is
out of control.

978
01:02:27,000 --> 01:02:29,550
He's making it rain. Podcast,
rain, baby.

979
01:02:31,740 --> 01:02:38,160
See? Okay, and I hope I'm saying
this name, right. Clint. Pro PR

980
01:02:38,190 --> 01:02:38,970
o IE,

981
01:02:39,870 --> 01:02:43,290
what do you think? Pro Pro? Pro
Pro?

982
01:02:44,310 --> 01:02:50,610
Yeah. Five bucks. Nice. Thank
you. Thank you. And a $5 a month

983
01:02:50,610 --> 01:02:54,990
subscription. Also from Jeremy
new. Thank you, Jeremy. Yeah,

984
01:02:54,990 --> 01:02:58,320
these are great. I mean, long
term subscriptions are extremely

985
01:02:58,320 --> 01:03:02,160
appreciated. That really builds
up a base over time. Thank you.

986
01:03:02,640 --> 01:03:05,460
Yeah, it takes the pressure off,
you know, you start starting to

987
01:03:05,460 --> 01:03:09,840
spin up servers, and you start
looking at the bill and you

988
01:03:09,840 --> 01:03:13,650
start thinking, Well, I really
need to do this, but oh my god,

989
01:03:13,650 --> 01:03:17,010
that's gonna be an extra 40
bucks a month. And I love it. I

990
01:03:17,009 --> 01:03:23,819
love how you think Dave Jones?
You know, me? Like, I don't

991
01:03:23,819 --> 01:03:26,819
know, I guess like, this is for
them. Dave is this right? Like,

992
01:03:26,819 --> 01:03:32,849
no, no, we need to bring that
down. Do a different also,

993
01:03:32,909 --> 01:03:36,059
before you continue, I just
wanted to say that I'm so happy

994
01:03:36,539 --> 01:03:42,119
that so many people get to see
and work with you. Cuz, you

995
01:03:42,119 --> 01:03:47,399
know, we've been doing stuff for
10 years. And I've seen people

996
01:03:47,399 --> 01:03:50,579
go holy crap, you know, I
breathed something. And Dave's

997
01:03:50,579 --> 01:03:55,199
got it implemented or has an
idea. This is Dave Jones. So I

998
01:03:55,199 --> 01:03:57,419
just want to make that very
clear that you know, the dragon

999
01:03:57,419 --> 01:04:02,069
slayer for sure. Because I've
thrown I mean, I will talk to

1000
01:04:02,069 --> 01:04:05,339
you the way I spoke on the
international podcast day with

1001
01:04:05,339 --> 01:04:10,199
an idea. And you'll go okay, and
you'll usually turn it around

1002
01:04:10,199 --> 01:04:12,929
and you'll ask me two questions.
And then it's like, oh, test

1003
01:04:12,959 --> 01:04:20,009
this. Yeah. So it's a joy to see
you're working with all these

1004
01:04:20,009 --> 01:04:24,329
other people as well. And I hope
they, they appreciate the how

1005
01:04:24,329 --> 01:04:25,709
this is all flowing through you.

1006
01:04:26,190 --> 01:04:28,740
Yeah, it's been great. It's been
it's been a lot of fun. Tina

1007
01:04:28,740 --> 01:04:29,850
wants to make sure you're having

1008
01:04:29,850 --> 01:04:33,360
fun because Dave must be having
fun. Besides, he better be if

1009
01:04:33,360 --> 01:04:35,070
he's not then we're in trouble.

1010
01:04:35,610 --> 01:04:39,480
Yeah, true. No, no, it's it's
great. Yeah, it's been it's been

1011
01:04:39,480 --> 01:04:40,650
a it's been a blast because it's

1012
01:04:40,650 --> 01:04:43,830
all consuming. I mean, I'm also
sitting on the couch, you know,

1013
01:04:43,830 --> 01:04:48,420
like, chatting with you or
checking the, the mastodon

1014
01:04:48,420 --> 01:04:50,250
server or anything, you know,
it's like

1015
01:04:51,660 --> 01:04:52,530
it gets in your brain

1016
01:04:52,560 --> 01:04:54,330
does it does and does.

1017
01:04:55,920 --> 01:04:57,510
Well, that's it for donations, I
think. Okay,

1018
01:04:57,600 --> 01:05:00,240
well, it's very good. This'll
definitely keep us power. for a

1019
01:05:00,240 --> 01:05:04,440
bit longer, incredibly
appreciated, again, value for

1020
01:05:04,440 --> 01:05:06,390
value can't say it enough your
time, your talent, your

1021
01:05:06,390 --> 01:05:10,050
treasure, some people seem to be
contributing all three, whatever

1022
01:05:10,050 --> 01:05:13,050
you put into, it usually flows
out. And that is what we've

1023
01:05:13,050 --> 01:05:16,650
learned over the course of many
years of the applying the value

1024
01:05:16,650 --> 01:05:20,520
for value model. So let's talk
about the image server for a

1025
01:05:20,520 --> 01:05:23,760
moment, because that we've kind
of went through a lot of what it

1026
01:05:23,760 --> 01:05:30,660
already does in the namespace.
But longer term, it appears to

1027
01:05:30,660 --> 01:05:36,120
me that this can be a good
resource for a lot of things. A

1028
01:05:36,120 --> 01:05:39,180
lot of people seem to need these
images. And I'm really happy to

1029
01:05:39,180 --> 01:05:41,250
set that up. You set that one up
pretty quick, too.

1030
01:05:42,690 --> 01:05:48,780
Yeah, this this week was
dedicated to me throwing Andy

1031
01:05:48,780 --> 01:05:53,790
from the mastodon under the bus,
because he's been waiting for me

1032
01:05:53,790 --> 01:06:00,720
to refactor the recent episodes
in point for like, two weeks,

1033
01:06:01,080 --> 01:06:06,240
and I keep saying, Yeah, I'll
get that for you. And it's and

1034
01:06:06,240 --> 01:06:09,300
then go off and create an image
server, right, where I go off

1035
01:06:09,300 --> 01:06:15,930
and do a namespace, right? Okay.
Um, I've, I've got to get I've

1036
01:06:15,930 --> 01:06:20,400
kind of felt some pressure to
get back to getting some stuff,

1037
01:06:20,610 --> 01:06:23,940
some of these endpoints
reengineered. So I'm really

1038
01:06:23,940 --> 01:06:26,460
going to try to buckle down and
start start focusing on that for

1039
01:06:26,460 --> 01:06:30,570
a while. Okay. And because I
mean, we don't want to neglect

1040
01:06:30,570 --> 01:06:32,670
the core of, of what we're doing
here.

1041
01:06:33,480 --> 01:06:36,690
Now is the endpoints obviously,
do I need to cock block anybody?

1042
01:06:36,690 --> 01:06:37,680
So they don't disturb you

1043
01:06:38,100 --> 01:06:41,520
know? Yeah. Now I can close my
browser.

1044
01:06:41,550 --> 01:06:42,570
Oh, okay. Good.

1045
01:06:45,000 --> 01:06:49,560
Play. See what you know. We lost
Conan O'Brien.

1046
01:06:50,910 --> 01:06:53,130
He went off word who did he sign
with?

1047
01:06:54,270 --> 01:06:57,240
I think it's Amazon.

1048
01:06:58,200 --> 01:07:01,470
No fraud. Audible probably. I
think I did see a blurb about

1049
01:07:01,470 --> 01:07:01,860
that.

1050
01:07:02,040 --> 01:07:05,580
Yeah, play. I think that's a
good PLAY CLIP three Conan Eisah

1051
01:07:05,820 --> 01:07:12,030
Oh, clip three. There's too much
comedy. And I think that's why I

1052
01:07:12,030 --> 01:07:20,430
started this podcast is to try
and stop it here we got to pay

1053
01:07:20,430 --> 01:07:24,120
homage to the guys that
disappear. But the so the image

1054
01:07:24,120 --> 01:07:29,730
server is probably going to be

1055
01:07:29,940 --> 01:07:32,880
going on we're not doing it
right. Changed. We're not doing

1056
01:07:32,880 --> 01:07:35,970
it right. I'll show you how we
do it.

1057
01:07:38,910 --> 01:07:49,920
Everybody and I think that's why
I started this podcast is to try

1058
01:07:49,920 --> 01:07:56,700
and stop. tabs as they go on
their way out. I forgot what all

1059
01:07:56,700 --> 01:07:58,200
right party is was clipped to
you.

1060
01:07:58,650 --> 01:08:00,090
All right party.

1061
01:08:02,010 --> 01:08:08,730
It was a very alright party.
Let's throw it.

1062
01:08:09,750 --> 01:08:12,360
Oh, he's probably he's probably
joking around about the SCOTUS

1063
01:08:12,360 --> 01:08:13,650
party in the Rose Garden.

1064
01:08:14,610 --> 01:08:17,160
I think that was from his
interview with Sarah Silverman.

1065
01:08:18,090 --> 01:08:23,040
Okay, yeah, explains that. Yes,
the image server will probably

1066
01:08:23,040 --> 01:08:26,610
just going to I'm probably going
to end up reengineering that

1067
01:08:26,610 --> 01:08:34,830
because I don't the ideas sound.
But I think the way that it

1068
01:08:34,830 --> 01:08:39,150
needs to be filled in right now.
It's basically just running.

1069
01:08:39,600 --> 01:08:43,530
There's running three image
converters in parallel,

1070
01:08:44,070 --> 01:08:46,080
each for each one for a
different size.

1071
01:08:46,950 --> 01:08:50,190
No, it's they're just, they're
just taking different sections

1072
01:08:50,190 --> 01:08:53,520
of the index. And grabbing them
and sticking them in five

1073
01:08:53,520 --> 01:08:59,490
different sizes. And his work in
the problem is going to be and I

1074
01:08:59,490 --> 01:09:02,610
can see it already, which is
just a big way. Well, yeah.

1075
01:09:02,610 --> 01:09:05,610
Mike, Mike was talking about
dupes. There's that and there's

1076
01:09:05,610 --> 01:09:10,440
also just you're in you're going
to end up doing a lot wasting a

1077
01:09:10,440 --> 01:09:15,330
lot of space for podcasts that
never get touched. And so I

1078
01:09:15,330 --> 01:09:22,920
think a better way to do this is
going to be to to respond to

1079
01:09:22,920 --> 01:09:26,730
have it monitoring and respond
when calls are made that return

1080
01:09:26,730 --> 01:09:31,650
podcasts. And then do it on the
fly. So basically, just

1081
01:09:32,790 --> 01:09:35,190
the first request is is the
toughest.

1082
01:09:36,239 --> 01:09:39,749
Yeah, no, the first real quick
here's, here's my idea. So

1083
01:09:42,029 --> 01:09:47,129
Martin had came up with this
idea to use an initially very

1084
01:09:47,129 --> 01:09:50,909
small size image and blur it.
And that seems to

1085
01:09:50,969 --> 01:09:53,159
that was the intro very
interesting the way that worked.

1086
01:09:53,789 --> 01:09:58,229
Yeah, like as a as an effect. I
mean, you're masquerading a

1087
01:09:58,229 --> 01:10:01,889
problem with conductivity and
software, but it worked. I mean,

1088
01:10:01,889 --> 01:10:05,069
the the illusion is beautiful.
Oh, that is actually kind of

1089
01:10:05,639 --> 01:10:07,379
almost like it was a feature.

1090
01:10:08,460 --> 01:10:13,770
And in this file size of that
thing is tiny. It's, it's 987

1091
01:10:13,770 --> 01:10:20,250
bytes, right? So my thought is,
what we could do is we could, we

1092
01:10:20,250 --> 01:10:26,940
could resize on the fly to the
20 by 20, when somebody

1093
01:10:26,940 --> 01:10:32,910
initially when somebody
initially asks for it. And

1094
01:10:32,970 --> 01:10:37,290
excuse me, let me back that up,
we can go ahead and pull down to

1095
01:10:37,290 --> 01:10:43,080
20 by 20s. And serve that
immediately. And then when

1096
01:10:43,080 --> 01:10:48,780
somebody asks for the full, and
then when they asked for it, we

1097
01:10:48,780 --> 01:10:50,880
go ahead and pull the other
images and convert them in the

1098
01:10:50,880 --> 01:10:56,160
background. So that there's like
a one second delay, right?

1099
01:10:57,000 --> 01:11:00,420
Before we deliver the full the
other resolution.

1100
01:11:01,740 --> 01:11:03,210
So okay, I get it.

1101
01:11:04,290 --> 01:11:06,930
What we may find out is we may
find out that there's out of a

1102
01:11:06,930 --> 01:11:11,940
million and a half feets there's
only you know, 400,000 that ever

1103
01:11:11,940 --> 01:11:13,770
get requested for images. And

1104
01:11:14,970 --> 01:11:18,030
although I, I do hope in the
future that people consider

1105
01:11:18,240 --> 01:11:21,390
changing their art per episode.
I think it's really worth it.

1106
01:11:22,470 --> 01:11:25,950
Yeah, it makes everything so
much colorful. It makes the

1107
01:11:25,950 --> 01:11:29,820
world prettier. The apps better.
I don't know. It's attractive.

1108
01:11:30,210 --> 01:11:31,050
It's exciting.

1109
01:11:31,500 --> 01:11:35,520
I'm always excited when I look
do a search. And then one comes

1110
01:11:35,520 --> 01:11:38,880
back and all the episodes are
different. Yeah, so yes, you

1111
01:11:38,880 --> 01:11:39,270
happy?

1112
01:11:40,740 --> 01:11:44,280
And you look. Oh, wow, that
might be a good episode. Yeah,

1113
01:11:44,430 --> 01:11:47,700
that's probably the Ardo. I
know, it's, it's hard. It's

1114
01:11:47,700 --> 01:11:51,780
hard. But you know, we're lucky.
No agenda. We have people who

1115
01:11:51,990 --> 01:11:54,990
want we get like 20 submissions
a show before the show's even

1116
01:11:54,990 --> 01:11:55,440
over.

1117
01:11:56,070 --> 01:11:58,590
Yeah, for most people, that
would be really difficult.

1118
01:11:58,620 --> 01:11:59,400
Right? Yeah, no

1119
01:11:59,400 --> 01:12:02,640
kidding. But we also deliver the
show 30 minutes after the

1120
01:12:02,640 --> 01:12:03,120
stream?

1121
01:12:03,990 --> 01:12:10,560
Yeah. That's still incredible.
Fast. Yeah. So that's the image

1122
01:12:10,560 --> 01:12:15,150
thing. So basically, what I'm
saying is, all this, all the

1123
01:12:15,150 --> 01:12:17,940
stuff that has happened to this
point, I may just throw that

1124
01:12:17,940 --> 01:12:20,010
stuff away, like, you know,

1125
01:12:21,120 --> 01:12:23,820
shortly and but the way you
access, it won't change, right?

1126
01:12:23,820 --> 01:12:26,970
No one has to change code
necessarily. Right? Yeah.

1127
01:12:27,720 --> 01:12:30,780
Well, if we do it this other
way, what I think is we will put

1128
01:12:30,780 --> 01:12:34,770
in an extra property in the
endpoint that returns the URL of

1129
01:12:34,770 --> 01:12:39,690
that 20 of that small 20 by 20.
Image. And when the endpoint and

1130
01:12:39,690 --> 01:12:46,140
when that happens, it will
trigger the full resolution

1131
01:12:46,140 --> 01:12:50,940
download and conversion on the
image on the object. So nice. So

1132
01:12:51,000 --> 01:12:53,760
that would be a good way to
like, be more efficient with

1133
01:12:53,760 --> 01:12:58,710
this whole thing. Yeah, I think
that's the new because because

1134
01:12:58,770 --> 01:13:00,540
this thing's gonna take like 300
gigs

1135
01:13:00,780 --> 01:13:02,760
of disk, it's gonna be it's
gonna be pretty hefty.

1136
01:13:03,390 --> 01:13:07,530
Yeah. And we may only need half
that if we do it this other way.

1137
01:13:09,300 --> 01:13:12,570
And then we could check for
duplicates, and only serve, only

1138
01:13:12,570 --> 01:13:15,810
serve the one the one version of
that if we needed to out on the

1139
01:13:15,810 --> 01:13:19,980
back end. We can do. Like we, we
can just do like a soft link or

1140
01:13:19,980 --> 01:13:26,190
something in on the Linux file
system. Okay. Cool. We're good.

1141
01:13:26,640 --> 01:13:28,800
We got other stuff to talk
about. We're going kind of long.

1142
01:13:28,800 --> 01:13:31,440
You want to? You want to wrap it
up? Are you guys anything else

1143
01:13:31,440 --> 01:13:31,740
you want to?

1144
01:13:32,520 --> 01:13:37,230
Well, besides the you're
intending to work on endpoints,

1145
01:13:37,650 --> 01:13:41,730
we'll get the namespace name
change. We'll get that up. I

1146
01:13:41,730 --> 01:13:45,390
guess I'll do work on promoting
that and see if we get some

1147
01:13:45,390 --> 01:13:51,210
people to come in and work on
it. And what else do you need to

1148
01:13:51,210 --> 01:13:57,480
say anything I can get for you?
A beer. What happened to hookers

1149
01:13:57,480 --> 01:14:00,900
and blow man rent boys Sheraton?
A none of that

1150
01:14:00,900 --> 01:14:03,690
he's way, way too much. Way too
much baggage.

1151
01:14:04,830 --> 01:14:09,870
Here. So I will just say and
here's your T's. The Dave and I

1152
01:14:09,870 --> 01:14:14,490
have been also been we've been
working pretty hard on the

1153
01:14:14,490 --> 01:14:19,770
second mission, which is
retooling podcasting to a

1154
01:14:19,770 --> 01:14:25,560
platform of value. It's just way
too early to talk about it. But

1155
01:14:25,560 --> 01:14:29,790
we found interesting people that
have some ideas and we're we're

1156
01:14:29,790 --> 01:14:36,270
looking at some some initial
tests. But I am quite excited.

1157
01:14:36,960 --> 01:14:39,930
Yeah, me too. It's gonna be that
that's when things are gonna get

1158
01:14:39,930 --> 01:14:40,470
real fun.

1159
01:14:40,530 --> 01:14:44,970
Yeah. Yeah, I think you're
right. So all all will be

1160
01:14:44,970 --> 01:14:45,600
revealed.

1161
01:14:47,580 --> 01:14:51,690
Good do a cast coverage. Paul,
shoot you

1162
01:14:53,190 --> 01:14:56,610
can't wait for this one. Another
random shot from cast

1163
01:14:56,610 --> 01:14:57,780
coverage.com

1164
01:14:57,930 --> 01:15:02,010
and coming in here and putting
us all in jail. You have a mask

1165
01:15:02,010 --> 01:15:07,260
or no mask we're going. Okay? Or
he might not put you in he just

1166
01:15:07,260 --> 01:15:13,500
shoot you. Um, well, he probably
would shoot you back. There we

1167
01:15:13,500 --> 01:15:13,740
go.

1168
01:15:14,340 --> 01:15:17,910
I like that mask or no mask we
go on beautiful, beautiful.

1169
01:15:18,630 --> 01:15:23,700
Yeah, but we didn't even talk
about the web. So all that

1170
01:15:23,700 --> 01:15:28,110
stuff's working now. Well, let's
talk about that next week. That

1171
01:15:28,110 --> 01:15:31,080
was like, multiple days of stuff
to get that

1172
01:15:31,080 --> 01:15:33,180
work. But do you want to just
just briefly talk about it? I

1173
01:15:33,180 --> 01:15:36,240
mean, it's, it's an important
piece.

1174
01:15:38,550 --> 01:15:42,540
Yeah, well, I'll just let's talk
about next week. Okay. So my

1175
01:15:42,540 --> 01:15:45,960
next week will the basically
it's working. And I've got some

1176
01:15:45,960 --> 01:15:49,350
good stats, too, that we can
talk about next week. I'll dig

1177
01:15:49,350 --> 01:15:51,000
in a little bit. Excellent.
Excellent.

1178
01:15:51,690 --> 01:15:57,180
Well, Dave, it's as always, man,
it's a it's a real joy working

1179
01:15:57,180 --> 01:16:00,870
with you on this project. It's
really, really fun. It is fun.

1180
01:16:01,320 --> 01:16:06,600
And I'm all I'm all God with it.
That's what's going on here.

1181
01:16:06,930 --> 01:16:10,140
Alright, everybody, that'll do
it for podcasting. 2.0 for

1182
01:16:10,140 --> 01:16:13,830
today. We'll be back next week
with another episode. Well, I'm

1183
01:16:13,830 --> 01:16:16,020
sure we'll have lots of stuff to
talk about. Dave. See you then

1184
01:16:16,020 --> 01:16:16,320
man.