1
00:00:00,400 --> 00:00:06,679
Podcasting 2.0 for August 28th, 2026, episode 269, Verbal Pollution.

2
00:00:08,179 --> 00:00:12,240
Hello. Hello everybody, welcome to Podcasting 2.0. It's a Friday,

3
00:00:12,240 --> 00:00:16,530
it's 100 degrees outside. It's time for everything and all

4
00:00:16,530 --> 00:00:20,539
things podcasting. We're here to make it happen for you.

5
00:00:20,800 --> 00:00:22,710
It's the board meeting, and in fact, we are the

6
00:00:22,710 --> 00:00:26,179
only board meeting where we always blame Albie's. I'm Adam

7
00:00:26,179 --> 00:00:28,120
Curry here in the heart of the Texas Hill Country

8
00:00:28,120 --> 00:00:31,339
and in Alabama. The man who performed database surgery this

9
00:00:31,339 --> 00:00:34,409
weekend reports that the butt is intact. Say hello to

10
00:00:34,409 --> 00:00:37,039
my friend on the other end, the one, the only,

11
00:00:37,039 --> 00:00:46,659
the pod sage, Mr. Dave Jones. Everyone can... removed their

12
00:00:46,659 --> 00:00:48,759
hands from their butts. There's no reason to hold them

13
00:00:48,759 --> 00:00:53,219
anymore. It was the weirdest thing. The butts have landed.

14
00:00:53,420 --> 00:00:55,600
The butts have landed. You're like, the butt is okay.

15
00:00:55,799 --> 00:01:00,229
Like, all right. See, I saw that message before I

16
00:01:00,229 --> 00:01:03,640
saw, you know, the database message. Because it's a reverse.

17
00:01:03,640 --> 00:01:06,730
Oh, I bet that was confusing. Yes, the reverse chronological

18
00:01:06,730 --> 00:01:08,989
order for, Now I got to go figure out what's

19
00:01:08,989 --> 00:01:12,010
going on. Dave's in trouble. He needs help. We need

20
00:01:12,010 --> 00:01:16,060
to get to Alabama stat. He needs butt help. Butt

21
00:01:16,060 --> 00:01:21,780
help. How you doing, brother? Good. I'm good. I'm slightly

22
00:01:21,780 --> 00:01:25,459
grumpy from the... I have no chocolate, and that's really

23
00:01:25,459 --> 00:01:29,760
screwing up. No chocolate love. No, there's no chocolate love,

24
00:01:29,760 --> 00:01:33,879
and it's really messing with my head. Okay, so when

25
00:01:33,879 --> 00:01:39,540
you do... I have to imagine... That everyone is sort

26
00:01:39,540 --> 00:01:43,629
of like this who does podcasts. There has to be

27
00:01:43,629 --> 00:01:47,640
some sort of ceremony or ritual that goes along with

28
00:01:47,640 --> 00:01:51,329
doing each show. And I imagine that each show that

29
00:01:51,329 --> 00:01:55,219
you do is maybe a different ritual or ceremony, like

30
00:01:55,219 --> 00:01:59,239
pre-show, during show, this thing that you just have to

31
00:01:59,239 --> 00:02:02,560
like get. It sort of centers you into what the

32
00:02:02,560 --> 00:02:06,379
show is. Oh, that's an interesting question. Yes, I have

33
00:02:06,379 --> 00:02:11,280
different ceremonies for different shows. Yeah, chocolate is one of

34
00:02:11,280 --> 00:02:15,650
my ceremonies, one of my rituals, and it's really messing

35
00:02:15,650 --> 00:02:18,530
me up that it's not involved. I pray before every

36
00:02:18,530 --> 00:02:22,189
show. I do that. No agenda. I sing along with

37
00:02:22,189 --> 00:02:26,400
the fat lady. Yes. For podcasting 2.0, I play one

38
00:02:26,400 --> 00:02:29,319
of our Godcaster radio network stations and just listen along.

39
00:02:29,659 --> 00:02:33,490
Today was a little different as Tina is hosting a

40
00:02:33,490 --> 00:02:38,090
birthday party for one of her friends. And so there's

41
00:02:38,090 --> 00:02:41,879
eight women. right on the other side of the studio

42
00:02:41,879 --> 00:02:45,599
door. I'm sure you will hear them because they're church

43
00:02:45,599 --> 00:02:49,139
ladies. They get loud. Oh, yeah. And so part of

44
00:02:49,139 --> 00:02:56,580
my ritual today was shrimp, a boursin cheese with hot

45
00:02:56,580 --> 00:03:04,460
honey and pistachio on a cracker. You And a glass.

46
00:03:05,460 --> 00:03:08,639
On a cracker. Oh, man. Oh, that is so good.

47
00:03:09,199 --> 00:03:13,219
That is so good. Cheese, hot honey, and pistachio on

48
00:03:13,219 --> 00:03:15,979
a cracker. Well, no, it's Boursin cheese. You know Boursin?

49
00:03:16,319 --> 00:03:19,349
I don't know what that is. It's like the garlic

50
00:03:19,349 --> 00:03:22,199
spreadable French cheese. You've never had that? How do you

51
00:03:22,199 --> 00:03:29,520
spell it? B-O-U-R-S-I-N. Boursin. Now, most people say boursin cheese

52
00:03:29,520 --> 00:03:33,740
here in Texas. Boursin cheese. I'm like, ladies, it's boursin.

53
00:03:34,180 --> 00:03:39,199
Boursin. Yeah. You like the boursin, croissant, boursin, et le

54
00:03:39,199 --> 00:03:45,860
pain. Yes. And that's mixed with a little hot honey

55
00:03:45,860 --> 00:03:50,699
and then with the crushed pistachios as crack. The Europeans

56
00:03:50,699 --> 00:03:55,870
and their cheese, man. There's like 3,000 different varieties of

57
00:03:55,870 --> 00:03:59,460
cheese. Oh, yeah. And then the... In America, we have...

58
00:03:59,550 --> 00:04:04,069
American, which is not cheese at all. It's just slightly

59
00:04:04,069 --> 00:04:08,830
hardened milk. Plastic. Yeah, it's skim milk that's been curdled

60
00:04:08,830 --> 00:04:12,520
or something, and then we have cheddar. That's the glass

61
00:04:12,520 --> 00:04:16,269
of rosé I brought with me to the studio. Is

62
00:04:16,269 --> 00:04:19,879
this also a ceremony? Mm-hmm. It is today. It is

63
00:04:19,879 --> 00:04:22,399
today. Well, I'm good because you're grumpy and I'm not.

64
00:04:22,399 --> 00:04:25,709
So that's fantastic. I'm not I'm not super grumpy. I'm

65
00:04:25,709 --> 00:04:30,120
just mildly grumpy. Oh, OK. Boy, let's see that there

66
00:04:30,120 --> 00:04:35,040
are definitely some things going on. Yes. I think we

67
00:04:35,040 --> 00:04:38,300
should talk about the database surgery first. I mean, that's

68
00:04:38,300 --> 00:04:40,480
what I kick it all off with. So what was

69
00:04:40,480 --> 00:04:43,689
going on? I mean, your butt was hurting. The tables

70
00:04:43,689 --> 00:04:48,009
were large. There were outages. Linode was... was doing emergency

71
00:04:48,009 --> 00:04:52,029
migration. Why does that happen? Do they ever tell us

72
00:04:52,029 --> 00:04:56,209
why? Oh, emergency, emergency. We have to migrate your entire

73
00:04:56,209 --> 00:05:01,879
infrastructure to another server. Why? This used to never happen.

74
00:05:02,360 --> 00:05:07,420
Yeah. I mean, I've been using Linode since... I mean,

75
00:05:07,420 --> 00:05:13,290
since before we... Started podcasting, Podcast Index. So probably, I'm

76
00:05:13,290 --> 00:05:17,769
thinking probably make 2017, something like that. So probably a

77
00:05:17,769 --> 00:05:22,759
decade. It used to be very rare. Like once every...

78
00:05:22,509 --> 00:05:24,990
Like once every six to nine months that you'd get

79
00:05:24,990 --> 00:05:28,259
some sort of hiccup. And usually it was not that

80
00:05:28,259 --> 00:05:30,310
big of a deal. It was like some sort of

81
00:05:30,310 --> 00:05:33,800
like soft migration where they would, oh, this host has

82
00:05:33,800 --> 00:05:37,459
a disk degradation and we're going to migrate your VM

83
00:05:37,459 --> 00:05:39,579
to a new host. But we're putting you in the

84
00:05:39,579 --> 00:05:42,470
queue. It's going to happen sometime in the next 60

85
00:05:42,470 --> 00:05:46,079
days or 30 days. It was this like super chill.

86
00:05:47,639 --> 00:05:50,350
They weren't, you know, nobody ever seemed too concerned about

87
00:05:50,350 --> 00:05:54,079
anything. Ever since Akamai took them over, it's like this.

88
00:05:54,279 --> 00:05:57,279
They're going nuts over there. Things are dropping like flies.

89
00:05:57,519 --> 00:06:00,319
I just wonder what actually happens. I mean, it's a

90
00:06:00,319 --> 00:06:04,019
virtual machine, I presume. So how does that get corrupted?

91
00:06:04,500 --> 00:06:07,560
And there's never any, you don't really notice anything going

92
00:06:07,560 --> 00:06:11,300
wrong. They just tell you, well, it's emergency migration. I

93
00:06:11,300 --> 00:06:16,259
mean, the actual message was podcast index. No, that's not

94
00:06:16,259 --> 00:06:23,079
it. Where was it? Had it here. Well, this is

95
00:06:23,079 --> 00:06:28,680
from you. Linode Emergency Maintenance. That's usually what the message

96
00:06:28,680 --> 00:06:33,319
is. And does that come in on the Linode emails

97
00:06:33,319 --> 00:06:36,819
that you usually ignore, including Sam the showrunner, using all

98
00:06:36,819 --> 00:06:40,790
the bandwidth in the universe? No, I totally ignore the

99
00:06:40,790 --> 00:06:45,480
showrunner, but I never ignore the other, you know, the

100
00:06:45,480 --> 00:06:51,129
bat phone, essentially, which is like… Hey, emergency maintenance. Because

101
00:06:51,129 --> 00:06:55,500
this – well, so all this stuff is running on

102
00:06:55,500 --> 00:07:00,740
a rack of servers. And your host, your VM at

103
00:07:00,740 --> 00:07:05,980
any one time is on a server with – let's

104
00:07:05,980 --> 00:07:09,660
say 40 or 50 or 60 or 100 other VMs,

105
00:07:09,660 --> 00:07:11,920
depending on what the size of it is. And if

106
00:07:11,920 --> 00:07:15,720
that host hardware has some sort of problem, let's say

107
00:07:15,720 --> 00:07:20,100
usually, I don't know if they're using specialized hardware or

108
00:07:20,100 --> 00:07:23,199
vendor supplied hardware. I'm not sure. I don't know what.

109
00:07:23,420 --> 00:07:25,680
They're probably like super micro backed or something like that.

110
00:07:25,839 --> 00:07:28,139
But let's say, Let's say it's like a HP DL

111
00:07:28,139 --> 00:07:35,600
360. Yeah. Well, that thing has two power supplies. Well,

112
00:07:35,600 --> 00:07:39,389
if one of them dies. I forgot about that. I've

113
00:07:39,389 --> 00:07:41,569
had a power supply die on me, too, not too

114
00:07:41,569 --> 00:07:45,009
long ago. That's the weirdest thing. Yeah. It is because

115
00:07:45,009 --> 00:07:47,660
you don't expect it. That's so rare that it happens.

116
00:07:48,019 --> 00:07:50,649
But it seems like they're making the power supplies just

117
00:07:50,649 --> 00:07:54,459
powerful enough, you know. So that they don't have enough

118
00:07:54,459 --> 00:07:57,649
headroom and they're stressed. Yeah, because I have a Dell

119
00:07:57,649 --> 00:08:00,740
that I run everything on here. And maybe, was it

120
00:08:00,740 --> 00:08:04,649
maybe six weeks ago? All of a sudden, just boom,

121
00:08:04,649 --> 00:08:08,550
done. And I see the light flashing, and I go

122
00:08:08,550 --> 00:08:10,470
look it up. Oh, no, the light flashing means your

123
00:08:10,470 --> 00:08:13,160
power supply has failed. And then I look up the

124
00:08:13,160 --> 00:08:17,069
specs and everything. It's like, well, this thing is really

125
00:08:17,069 --> 00:08:20,300
kind of underpowered for if you max this machine out,

126
00:08:20,300 --> 00:08:23,899
which happens. Yeah, for sure. So I ordered a beefier

127
00:08:23,899 --> 00:08:27,279
power supply. I'm like, that kind of sucks. They give

128
00:08:27,279 --> 00:08:30,680
you just something that just kind of manages to get

129
00:08:30,680 --> 00:08:34,580
by. And this came off of an oil rig, this

130
00:08:34,580 --> 00:08:38,240
machine. One of our no agenda producers, he's a dude

131
00:08:38,240 --> 00:08:41,620
named Ben. He's on the oil rigs. He's like, so

132
00:08:41,620 --> 00:08:44,909
all these machines, all these beautiful small Dell machines, you

133
00:08:44,909 --> 00:08:47,879
know, like the little wedge. I forget what it is.

134
00:08:48,659 --> 00:08:53,179
Yeah. And there's just like hundreds of them doing stuff,

135
00:08:53,179 --> 00:08:56,690
I guess, for the oil rig. And they just have

136
00:08:56,690 --> 00:08:59,610
to rotate them out after so many hours just to

137
00:08:59,610 --> 00:09:02,019
make sure that the hardware is fresh. So I think

138
00:09:02,019 --> 00:09:06,059
they're probably all running at maybe 40%. of cpu so

139
00:09:06,059 --> 00:09:09,389
you know maybe that's how they deliver maybe that's how

140
00:09:09,389 --> 00:09:13,029
they ordered them just cheap jack man it makes sense

141
00:09:13,029 --> 00:09:16,450
though that a power supply would be a victim of

142
00:09:16,450 --> 00:09:19,669
a oil rig environment because you know that is not

143
00:09:19,669 --> 00:09:23,149
it's not that's what you call a hostile environment to

144
00:09:23,149 --> 00:09:30,799
electronics Yeah, kind of. Yeah, that would make sense that

145
00:09:30,799 --> 00:09:34,179
that thing would go kaput. Yeah. Out of any of

146
00:09:34,179 --> 00:09:36,509
the components. Well, luckily. It's sucking in air all the

147
00:09:36,509 --> 00:09:39,440
time. It's got a cycle in that sea air through

148
00:09:39,440 --> 00:09:42,080
it all the time. Well, luckily, he sent me like

149
00:09:42,080 --> 00:09:44,879
five of these, so I had another power supply. I'm

150
00:09:44,879 --> 00:09:47,000
like, well, it's the same power supply. I'll order a

151
00:09:47,000 --> 00:09:53,700
bigger one. Oh, yes. Yeah. Yeah. Yeah. So anyway, so

152
00:09:53,700 --> 00:09:55,940
everything came back okay. But then you were doing other

153
00:09:55,940 --> 00:09:58,129
stuff. You were doing something with a big table or

154
00:09:58,129 --> 00:09:58,799
something.

155
00:10:03,061 --> 00:10:06,491
So I'm really glad that this thing, that the Linode

156
00:10:06,491 --> 00:10:10,171
maintenance did not happen at the exact moment that I

157
00:10:10,171 --> 00:10:12,771
was trying to do this other stuff because that would

158
00:10:12,771 --> 00:10:17,621
have been really bad. We talked about this a while

159
00:10:17,621 --> 00:10:22,571
back briefly. about what this thing is, and it's just

160
00:10:22,571 --> 00:10:25,891
taken me a while to get around to actually pulling

161
00:10:25,891 --> 00:10:28,921
the trigger because these things take a long time, and

162
00:10:28,921 --> 00:10:33,891
it's still sort of in a rolling plan mode. I

163
00:10:33,891 --> 00:10:36,391
won't say that I have this master runbook that I'm

164
00:10:36,391 --> 00:10:40,491
following. This is really just sort of I'm feeling my

165
00:10:40,491 --> 00:10:46,141
way through this, End. But it requires such a big

166
00:10:46,141 --> 00:10:50,631
refactor that that's one of the reasons I was kicking

167
00:10:50,631 --> 00:10:54,781
the can down the road is because now I feel

168
00:10:54,781 --> 00:11:01,381
like I have enough agentic help sort of to help

169
00:11:01,381 --> 00:11:06,931
me review stuff. to be a reviewer for my for

170
00:11:06,931 --> 00:11:09,061
my you know how i think this thing is going

171
00:11:09,061 --> 00:11:12,931
to go like because okay so if you look at

172
00:11:12,931 --> 00:11:17,551
the where did i post that let's see is it

173
00:11:17,551 --> 00:11:24,471
api podcast index Or, um, I posted like an open

174
00:11:24,471 --> 00:11:28,851
source version of the podcast index API core, one of

175
00:11:28,851 --> 00:11:34,771
the low level include files a while back, uh, github.

176
00:11:35,811 --> 00:11:38,771
I'm sure I can find it. Here it is. The

177
00:11:38,771 --> 00:11:42,611
big schema refactor. Is that it? I see. Where are

178
00:11:42,611 --> 00:11:45,661
you seeing that? No, I'm just, that's wrong. That's not

179
00:11:45,661 --> 00:11:52,451
it. Docs API. Thank you. Let me scroll down. I'm

180
00:11:52,451 --> 00:11:55,151
trying. I wanted to be able to drop something in

181
00:11:55,151 --> 00:11:58,991
so that people could look at why this, okay, maybe

182
00:11:58,991 --> 00:12:04,051
this is API v1. Yeah. Okay. All right. So here's

183
00:12:04,051 --> 00:12:10,942
a good example of why this is complicated. Where's the

184
00:12:10,942 --> 00:12:16,931
boardroom? There you are, boardroom. Hello, boardroom. Hello. This is

185
00:12:16,931 --> 00:12:24,861
the open source... version, so to speak, of the of

186
00:12:24,861 --> 00:12:26,791
one of the core files there's a bunch of these

187
00:12:26,791 --> 00:12:29,991
now when you when you say open source so this

188
00:12:29,991 --> 00:12:32,261
is not the full production code this is just something

189
00:12:32,261 --> 00:12:35,161
you're giving to saps who think they can emulate what

190
00:12:35,161 --> 00:12:38,041
you're doing is that what that is no way no

191
00:12:38,041 --> 00:12:41,331
no this is this is uh So this this is

192
00:12:41,331 --> 00:12:44,811
something I cleaned up and because to me, this stuff

193
00:12:44,811 --> 00:12:48,891
is useless without comments. Right. And so I had to

194
00:12:48,891 --> 00:12:51,571
go through and just like comment all the code and

195
00:12:51,571 --> 00:12:53,141
try to get it just in a in a form

196
00:12:53,141 --> 00:12:56,241
that's usable where people could even see what the heck

197
00:12:56,241 --> 00:12:58,942
was going on. So this is I mean, this is

198
00:12:58,942 --> 00:13:01,431
the actual code. But I just cleaned it up a

199
00:13:01,431 --> 00:13:03,451
lot to give it a lot of... Because these comments

200
00:13:03,451 --> 00:13:10,631
and stuff were not there. And so this... Is really

201
00:13:10,631 --> 00:13:15,261
how big, so this is just one, this is 14,000

202
00:13:15,261 --> 00:13:18,321
lines, I don't know how many functions, but these are

203
00:13:18,321 --> 00:13:21,401
sort of the low-level functions of the API where they

204
00:13:21,401 --> 00:13:25,351
communicate directly with the database. So most all of these

205
00:13:25,351 --> 00:13:29,481
are just database calls. Mm-hmm. So when you look, when

206
00:13:29,481 --> 00:13:32,442
you do like a podcast by feed ID, it's going

207
00:13:32,442 --> 00:13:35,371
to call these functions on the backside to get the

208
00:13:35,371 --> 00:13:42,401
data out of the database. Well. So this refactor, let

209
00:13:42,401 --> 00:13:47,381
me back up. So this refactor, The way that the

210
00:13:47,381 --> 00:13:55,611
podcast index database came about initially – Because we sucked

211
00:13:55,611 --> 00:14:03,751
everything out of Apple. Shit. You just sucked it back

212
00:14:03,751 --> 00:14:06,751
You gave them iPodder so we just sucked it back

213
00:14:06,751 --> 00:14:09,231
We did a back suck It was a fair swap

214
00:14:09,231 --> 00:14:14,471
Yeah it was just a back suck Back suck Yeah

215
00:14:14,471 --> 00:14:21,211
Just move on from that place Just move on But...

216
00:14:22,251 --> 00:14:26,411
Where do I'm translating? Where to start? Okay, well, the

217
00:14:26,411 --> 00:14:30,391
origin of the database schema originally comes from Freedom Controller

218
00:14:30,391 --> 00:14:37,211
because that was RSS Ingestor, Ingestor, Ingestor, Ingestor, whatever. So

219
00:14:37,211 --> 00:14:42,591
the name of the database that held all the feeds

220
00:14:42,591 --> 00:14:45,811
was… News feeds or the table that had all the

221
00:14:45,811 --> 00:14:48,911
feeds was news feeds. And then you had NF items,

222
00:14:48,911 --> 00:14:52,631
so news feed items was where all the items went.

223
00:14:52,751 --> 00:14:57,371
So that became NF. Those things became synonymous with podcasts

224
00:14:57,371 --> 00:15:02,271
and episodes, yes. So news feeds just became an alias

225
00:15:02,271 --> 00:15:11,721
for podcasts. Right. Um, Because... My thinking forever has always

226
00:15:11,721 --> 00:15:15,101
been that the... That a podcast is a, is a

227
00:15:15,101 --> 00:15:19,261
feed. I mean, because, because it is, it is, but

228
00:15:19,261 --> 00:15:27,131
it's not. Oh, yeah. So the podcast both is and

229
00:15:27,131 --> 00:15:30,641
is not a feed at the same time. So the

230
00:15:30,641 --> 00:15:41,591
podcast. The feed defines the podcast. but... But the podcast

231
00:15:41,591 --> 00:15:48,601
itself is also represented by the feed. Hmm. This is

232
00:15:48,601 --> 00:15:55,861
a cosmic mystery that we can't fully grasp. It's like

233
00:15:55,861 --> 00:16:02,442
the Heisenbergian podcast principle that you're both – That you're

234
00:16:02,442 --> 00:16:04,541
both a feed and not a feed at the same

235
00:16:04,541 --> 00:16:09,391
time. No, Schrodinger. This is Schrodinger's podcasting. But if you

236
00:16:09,391 --> 00:16:11,591
think about it, because if you think about it in

237
00:16:11,591 --> 00:16:17,801
one way, the podcast doesn't exist to the world. Unless

238
00:16:17,801 --> 00:16:23,971
there's a feed. That conveys it. But at the same

239
00:16:23,971 --> 00:16:29,651
time... A podcast is not simply the feed. No agenda

240
00:16:29,651 --> 00:16:32,771
is a podcast regardless of – even if you deleted

241
00:16:32,771 --> 00:16:36,661
the feed today, no agenda would still be – In

242
00:16:36,661 --> 00:16:41,672
One Sense, a podcast. The episodes would still exist somewhere.

243
00:16:43,011 --> 00:16:48,192
You could send the No Agenda podcast to somebody tomorrow

244
00:16:48,192 --> 00:16:50,221
if the feed was deleted. You could send them all

245
00:16:50,221 --> 00:16:51,971
as a zip file, and they could listen to all

246
00:16:51,971 --> 00:16:58,361
of them in sequence. True. So, I think, In some

247
00:16:58,361 --> 00:17:01,432
ways, this solves a lot of problems that we've had.

248
00:17:02,211 --> 00:17:08,112
And everybody will be familiar with these problems. Yeah. One

249
00:17:08,112 --> 00:17:15,902
of the problems is duplicate feeds or conflict feeds. Somebody

250
00:17:15,902 --> 00:17:19,902
moves their podcast from one host to another, and now

251
00:17:19,902 --> 00:17:22,132
you've got two feeds. Well, which one is right? How

252
00:17:22,132 --> 00:17:24,551
do we know which one is right? They did it.

253
00:17:24,731 --> 00:17:26,461
Maybe they put in a redirect from the old host

254
00:17:26,461 --> 00:17:31,672
to the new host. Maybe they didn't. Um, We have

255
00:17:31,672 --> 00:17:35,211
no control of it and no real way to know

256
00:17:35,211 --> 00:17:43,721
which one is good. Canonical. So, What we do is

257
00:17:43,721 --> 00:17:47,091
this convoluted dance of trying to figure out through a

258
00:17:47,091 --> 00:17:51,711
bunch of heuristics which – which one to treat as

259
00:17:51,711 --> 00:17:56,442
the authentic feed for this podcast. Right, which is really

260
00:17:56,442 --> 00:17:58,692
the trick of the whole index is to be able

261
00:17:58,692 --> 00:18:03,071
to do that. Yeah, and so we do that primarily

262
00:18:03,071 --> 00:18:09,771
through this function. The news feeds table has a couple

263
00:18:09,771 --> 00:18:16,731
of columns in it. One of them is dead is

264
00:18:16,731 --> 00:18:19,371
the name of the column, and it's just either a

265
00:18:19,371 --> 00:18:22,491
one or a zero, and the other one is duplicate

266
00:18:22,491 --> 00:18:28,761
of. which takes a podcast index feed ID. And so

267
00:18:28,761 --> 00:18:31,281
you can – the way we would do that is

268
00:18:31,281 --> 00:18:34,692
no agenda moves from its current feed URL to a

269
00:18:34,692 --> 00:18:41,301
new feed URL tomorrow. We mark 40. So then now

270
00:18:41,301 --> 00:18:44,241
so now and the podcast index picks up this new

271
00:18:44,241 --> 00:18:47,902
feed. So now you get two podcasts IDs in the

272
00:18:47,902 --> 00:18:53,192
news feeds table. They both say no agenda. And one

273
00:18:53,192 --> 00:18:56,641
of them is 41.504, and the new one is 8

274
00:18:56,641 --> 00:19:05,301
million-something-something. Mm-hmm. The way we would properly treat this currently

275
00:19:05,301 --> 00:19:11,382
today is we would say – We would... We would

276
00:19:11,382 --> 00:19:14,632
mark the 8 million and something, the new one, we

277
00:19:14,632 --> 00:19:19,731
would mark it as dead. change its URL because in

278
00:19:19,731 --> 00:19:22,692
the news feeds table, the URLs are unique index. So

279
00:19:22,692 --> 00:19:24,791
they can't, you can't have to do the same one

280
00:19:24,791 --> 00:19:29,442
on different rows. We would mark it. We would change

281
00:19:29,442 --> 00:19:35,101
the URL to something like the URL underscore conflict just

282
00:19:35,101 --> 00:19:41,811
to make it be something different. Then change 41504 to

283
00:19:41,811 --> 00:19:45,011
be the new URL that the 8 million something used,

284
00:19:45,011 --> 00:19:48,632
you know, did have. And then in the 8 million

285
00:19:48,632 --> 00:19:53,581
something feed ID row, we would mark, we would set

286
00:19:53,581 --> 00:19:58,431
duplicate of to 41504. So now you have sort of

287
00:19:58,431 --> 00:19:59,991
an audit trail of...

288
00:20:01,373 --> 00:20:04,423
These are all the feeds that are duplicates of the

289
00:20:04,423 --> 00:20:08,353
original feed, but we want to maintain a canonicity of

290
00:20:08,353 --> 00:20:14,963
the 41.504, so we always – blow away these new

291
00:20:14,963 --> 00:20:19,143
versions and keep replacing 41.504's feed with whatever the current

292
00:20:19,143 --> 00:20:21,843
one is, as best we can determine. Is Melissa still

293
00:20:21,843 --> 00:20:27,743
living in the same house as you? Laughter school started

294
00:20:27,743 --> 00:20:30,063
back so she's teaching so she does not have to

295
00:20:30,063 --> 00:20:32,313
deal with me right now okay okay just checking just

296
00:20:32,313 --> 00:20:36,053
checking this is i'm getting the buzz again are you

297
00:20:36,053 --> 00:20:39,183
hearing this buzz yeah i hear the buzz it's no

298
00:20:39,183 --> 00:20:44,783
chuckle love man it went away yeah So that's how

299
00:20:44,783 --> 00:20:48,093
we've always done it. And it's fine, but it is

300
00:20:48,093 --> 00:20:51,163
a big dance to go through. Yeah. And it also

301
00:20:51,163 --> 00:20:58,363
sometimes presents problems. that are sort of hard to get

302
00:20:58,363 --> 00:21:02,443
yourself out of. Because you can imagine, that was a

303
00:21:02,443 --> 00:21:07,823
very simplistic example. Please, don't give me the complicated one.

304
00:21:07,923 --> 00:21:15,433
Please. Some podcasters... are nuts. And they go through seven

305
00:21:15,433 --> 00:21:17,903
hosts before they figure out where they want to be.

306
00:21:18,043 --> 00:21:21,343
I know. How do you get out of that mess?

307
00:21:22,923 --> 00:21:29,123
Um... So – Here's And Daniel says, I think you're

308
00:21:29,123 --> 00:21:31,253
trying to take a burden on your shoulders that should

309
00:21:31,253 --> 00:21:39,783
not be yours to bear. You're right. I'm bearing a

310
00:21:39,783 --> 00:21:49,843
burden. But – So it struck me – This notion

311
00:21:49,843 --> 00:21:58,443
that the podcast is not the feed. And so what

312
00:21:58,443 --> 00:22:05,643
we really need... Is a layer above, an identity layer

313
00:22:05,643 --> 00:22:12,723
above the feeds table that is a podcast table. Wow.

314
00:22:14,733 --> 00:22:23,223
Okay. Is this blowing you away a little bit? Well,

315
00:22:23,223 --> 00:22:26,134
I mean, the minute you say that the podcast is

316
00:22:26,134 --> 00:22:28,573
not the feed, I mean, yeah, in the database, I

317
00:22:28,573 --> 00:22:34,783
understand because there can be multiple feeds and it's a

318
00:22:34,783 --> 00:22:40,873
mess. But let me back up a little bit. There

319
00:22:40,873 --> 00:22:45,943
has been an overall failing in the podcast industry, if

320
00:22:45,943 --> 00:22:48,103
I may call it that for a moment, because I

321
00:22:48,103 --> 00:22:51,023
think it is partially the podcast industrial complex is to

322
00:22:51,023 --> 00:22:56,134
blame. Because I talk to young people. I talk to

323
00:22:56,134 --> 00:22:59,683
the young'uns, my nephews mainly. And they're like, yeah, we're

324
00:22:59,683 --> 00:23:01,923
starting a podcast. What are we going to do? I'm

325
00:23:01,923 --> 00:23:03,663
going to put it on Spotify. I'm going to put

326
00:23:03,663 --> 00:23:05,993
it on Spotify. What does that mean? Well, we're going

327
00:23:05,993 --> 00:23:08,843
to, you know, we've got free stuff. We'll put it

328
00:23:08,843 --> 00:23:13,553
on Spotify. How about Apple? Yeah, we don't think we

329
00:23:13,553 --> 00:23:17,273
want to use any other, you know, it's like, how

330
00:23:17,273 --> 00:23:20,943
do we do that? I said, okay, did you read

331
00:23:20,943 --> 00:23:24,093
anything about it? No, no, I just want to be

332
00:23:24,093 --> 00:23:27,384
on Spotify. Well, I can set you up with an

333
00:23:27,384 --> 00:23:33,563
RSS.com account. Oh, that's one of those distributors. This is

334
00:23:33,563 --> 00:23:37,583
a distributor. Yes, this is a critical, critical piece of

335
00:23:37,583 --> 00:23:42,503
information that I got. Because of the lack of, well,

336
00:23:42,503 --> 00:23:47,113
it's not just the lack of education, but it is

337
00:23:47,113 --> 00:23:55,213
the marketing of YouTube and Spotify and others that has

338
00:23:55,213 --> 00:24:05,043
made newcomers think that, Podcast hosting companies are distributors. And

339
00:24:05,043 --> 00:24:08,863
honestly, if you look at RSS.com, which I use for

340
00:24:08,863 --> 00:24:13,183
a couple of podcasts, In fact, I'll tell you exactly

341
00:24:13,183 --> 00:24:16,713
what it says. It's probably worth it. Let me take

342
00:24:16,713 --> 00:24:21,573
a look. So if you go rss.com, and look at

343
00:24:21,573 --> 00:24:25,413
my – go to my dashboard. And it says right

344
00:24:25,413 --> 00:24:29,093
there at the top, I've got my podcast episodes analytics

345
00:24:29,093 --> 00:24:33,983
distribution. With a little share icon, you know, the little

346
00:24:33,983 --> 00:24:37,363
three dots, one dot to the left and two dots

347
00:24:37,363 --> 00:24:42,423
connected by wires. And it says major directories. And it

348
00:24:42,423 --> 00:24:47,323
has all these different switches. So they are, in effect,

349
00:24:47,323 --> 00:24:53,083
teaching me as someone who knows nothing. That they are

350
00:24:53,083 --> 00:24:58,203
a distributor because now in the distribution tag tab. So

351
00:24:58,203 --> 00:25:03,384
this is why so many people say you haven't uploaded.

352
00:25:03,583 --> 00:25:06,543
You forgot to upload to Apple. No, I didn't really.

353
00:25:07,563 --> 00:25:10,793
So actually I did not. But this is a huge

354
00:25:10,793 --> 00:25:16,103
disservice to themselves. Because the whole, and also people saying,

355
00:25:16,103 --> 00:25:25,843
open podcasting. You hate this term. I do. Now, some

356
00:25:25,843 --> 00:25:29,533
might say open RSS. Okay, I can kind of live

357
00:25:29,533 --> 00:25:34,193
with that. But there is no more knowledge of how

358
00:25:34,193 --> 00:25:36,983
it works and why it works that way and what

359
00:25:36,983 --> 00:25:41,423
the entire concept was and what the benefit is to

360
00:25:41,423 --> 00:25:45,653
having an RSS feed. And to be fair about it,

361
00:25:45,653 --> 00:25:48,963
people, well, I got a podcast. It's on YouTube. I

362
00:25:48,963 --> 00:25:53,923
put it on X. And, of course, with the disastrous

363
00:25:53,923 --> 00:25:58,203
results when X or YouTube or whatever takes your podcast

364
00:25:58,203 --> 00:26:02,163
off, it's like, no, you're done. So – This is

365
00:26:02,163 --> 00:26:05,513
kind of interesting that you then say to me, the

366
00:26:05,513 --> 00:26:08,634
podcast is not the feed. For the same reason, you

367
00:26:08,634 --> 00:26:13,203
have podcasters who are, quote, nuts, because they're just trying

368
00:26:13,203 --> 00:26:17,623
different distributors, man. Yeah, they're looking for the cheapest one.

369
00:26:17,903 --> 00:26:21,533
The hosting companies themselves, I believe, are partially to blame

370
00:26:21,533 --> 00:26:25,253
for this. There's no educational – I don't see the

371
00:26:25,253 --> 00:26:29,713
process at rss.com where – and it's in the name,

372
00:26:29,713 --> 00:26:36,483
rss.com, explaining why. It just says distribution. Distribution. Now, from

373
00:26:36,483 --> 00:26:42,733
a... flow perspective, I kind of get it, but this

374
00:26:42,733 --> 00:26:46,083
is the downstream effects of the lack of education, of

375
00:26:46,083 --> 00:26:52,163
the sheer beauty of RSS, certainly when it comes to

376
00:26:52,163 --> 00:26:56,773
podcasts, the sheer beauty and the whole beauty of the

377
00:26:56,773 --> 00:27:02,623
system is, Having a distribution system that you control from

378
00:27:02,623 --> 00:27:06,053
an RSS feed with your files attached to it, that

379
00:27:06,053 --> 00:27:09,903
is, I'd say, pretty much lost at this point. And

380
00:27:09,903 --> 00:27:14,353
here's the downstream effects of it. You're saying it's lost

381
00:27:14,353 --> 00:27:20,353
in the sense that no normie understands that process. Worse,

382
00:27:20,353 --> 00:27:26,683
they believe it works a completely different way. Right. Yeah,

383
00:27:26,683 --> 00:27:32,283
so the podcast, well, that's a good example, your nephews.

384
00:27:34,113 --> 00:27:39,393
of The idea that they probably think that they probably

385
00:27:39,393 --> 00:27:44,533
think that it operates a different way because the podcast

386
00:27:44,533 --> 00:27:49,213
is a priority to the feed. They in their mind,

387
00:27:49,213 --> 00:27:53,623
they already have a podcast. It's got a name. It's

388
00:27:53,623 --> 00:27:57,853
got a topic. It's got the hosts. They probably –

389
00:27:57,853 --> 00:28:02,303
maybe they already have some album art or something like

390
00:28:02,303 --> 00:28:06,033
that, and they may already have the first episode in

391
00:28:06,033 --> 00:28:09,973
the can. But they just don't have it on Spotify

392
00:28:09,973 --> 00:28:14,493
yet. So the podcast to them already exists. But they

393
00:28:14,493 --> 00:28:17,293
just have to distribute it. They got to get it

394
00:28:17,293 --> 00:28:20,933
out there. But we take the sense that if the

395
00:28:20,933 --> 00:28:25,593
feed doesn't exist, the podcast itself doesn't exist. Which is

396
00:28:25,593 --> 00:28:29,903
not entirely – which goes against what the normie believes.

397
00:28:30,023 --> 00:28:32,923
Yeah, but I've always hated the term normie, to be

398
00:28:32,923 --> 00:28:38,203
honest about it. Well, I'm just shorthanding that. Yeah, okay.

399
00:28:38,203 --> 00:28:43,083
To differentiate between – I mean, we're doing a –

400
00:28:43,083 --> 00:28:49,623
It was widely understood. You need an RSS feed. That

401
00:28:49,623 --> 00:28:57,163
was it. And I'm talking back to 2015, 2016. Widely

402
00:28:57,163 --> 00:29:00,073
understood. You need an RSS feed. It is no longer

403
00:29:00,073 --> 00:29:02,973
understood. And that's part of the whole problem, the part

404
00:29:02,973 --> 00:29:06,583
of the overall issue that we're seeing just across the

405
00:29:06,583 --> 00:29:10,233
board with everything. That's why people go to YouTube. That's

406
00:29:10,233 --> 00:29:13,373
why people don't switch on their RSS feed when they

407
00:29:13,373 --> 00:29:18,403
use Spotify for creators. Eric PP says, I hate Normie

408
00:29:18,403 --> 00:29:22,173
too, is demeaning. Let's dive in on this for just

409
00:29:22,173 --> 00:29:27,003
a second. Normie, you can take – I had a

410
00:29:27,003 --> 00:29:35,523
conversation this week about this very topic. is. The average

411
00:29:35,523 --> 00:29:43,723
person... In corporate America. Misunderstands the emphasis of the term

412
00:29:43,723 --> 00:29:47,643
artificial intelligence. You can take this thing in two different

413
00:29:47,643 --> 00:29:52,073
ways. You can say you can mentally place the emphasis

414
00:29:52,073 --> 00:29:57,163
on the term artificial intelligence. So in your mind, you

415
00:29:57,163 --> 00:29:59,923
can see, and the more you use

416
00:30:00,059 --> 00:30:02,359
this stuff on a technical level, the more you do

417
00:30:02,359 --> 00:30:08,460
place the emphasis, you can say, I'm using artificial intelligence.

418
00:30:10,130 --> 00:30:14,900
Meaning, in your mind, you see the artificial part, this

419
00:30:14,900 --> 00:30:20,680
thing as the overriding factor. This is... It's an intelligence

420
00:30:20,680 --> 00:30:25,119
which is artificial. It's not genuine, so therefore I distrust

421
00:30:25,119 --> 00:30:29,089
it. Or maybe not just distrust it, but I treat

422
00:30:29,089 --> 00:30:32,599
it with everything it says with a grain of salt.

423
00:30:34,000 --> 00:30:37,940
The average corporate America user that is not a technical

424
00:30:37,940 --> 00:30:42,359
person, meaning they are not steeped in computer technology and

425
00:30:42,359 --> 00:30:47,720
the day-to-day imaginations of the technology industry, tend to place

426
00:30:47,720 --> 00:30:52,160
the emphasis on the second word. And they, they, in

427
00:30:52,160 --> 00:30:55,289
their mind, it is artificial intelligence. Okay, stop. Go back

428
00:30:55,289 --> 00:30:59,759
to the beginning. It comes from the technology industry who

429
00:30:59,759 --> 00:31:03,940
is treating users as normies from the beginning. This is

430
00:31:03,940 --> 00:31:10,069
artificial intelligence. Fully well-knowing, it's not. And then, but the

431
00:31:10,069 --> 00:31:13,680
normies will think this, that is the arrogance of the

432
00:31:13,680 --> 00:31:20,779
technology industry across the board. You're holding it wrong. Absolutely.

433
00:31:20,779 --> 00:31:24,799
I think you're exactly right. I would not disagree with

434
00:31:24,799 --> 00:31:30,460
that. When it comes to the term normie, though, You

435
00:31:30,460 --> 00:31:33,990
can use that term as a person. Yeah, but it's

436
00:31:33,990 --> 00:31:38,220
like premium. But Eric said it's demeaning. Yeah, I think

437
00:31:38,220 --> 00:31:42,109
it is. I agree. It's only demeaning if you say

438
00:31:42,109 --> 00:31:46,369
– if you come at it mentally from saying I'm

439
00:31:46,369 --> 00:31:51,259
the technical – technically superior person and you're just a

440
00:31:51,259 --> 00:31:57,299
normie or the way I meant it was I'm the

441
00:31:57,299 --> 00:32:02,690
weird one, and you're normal. I'm somewhat of an oddity

442
00:32:02,690 --> 00:32:07,609
in the idea that I understand the XML of an

443
00:32:07,609 --> 00:32:12,799
RSS feed, and I think that's honestly a little strange.

444
00:32:13,380 --> 00:32:16,259
I don't think that a normal person should have to

445
00:32:16,259 --> 00:32:21,420
understand this. It's not a demeaning term. It's a term

446
00:32:21,420 --> 00:32:26,139
of attribution of a certain set of qualities that I

447
00:32:26,139 --> 00:32:31,660
think is actually normal. Okay, I submit this to you.

448
00:32:31,660 --> 00:32:35,980
Because of the exact thinking you just displayed, which is

449
00:32:35,980 --> 00:32:40,139
not demeaning, it's not demeaning. Because you're a good guy.

450
00:32:41,160 --> 00:32:43,730
You don't mean any. You never mean any. I know

451
00:32:43,730 --> 00:32:46,990
you. I've heard you in arguments with people and you're

452
00:32:46,990 --> 00:32:51,220
just still a loving guy. I've heard you snap, though.

453
00:32:51,279 --> 00:32:53,470
That was kind of fun. But anyways, there is a

454
00:32:53,470 --> 00:33:00,059
snapping point. But because of this segregation, I believe that's

455
00:33:00,059 --> 00:33:03,360
exactly why we wound up in this spot. Well, we've

456
00:33:03,360 --> 00:33:08,000
got to make it easy for normies to understand. Just

457
00:33:08,000 --> 00:33:12,839
call a distribution. I think that's where the problems stem

458
00:33:12,839 --> 00:33:18,740
from. So not even from a degrading standpoint, but we're

459
00:33:18,740 --> 00:33:21,579
the people who get it and those are the people

460
00:33:21,579 --> 00:33:23,819
who need to use it. They'll never get it. So

461
00:33:23,819 --> 00:33:26,940
let's just simplify it without thinking about the words that

462
00:33:26,940 --> 00:33:30,789
we're using because that'll just work for them. And this

463
00:33:30,789 --> 00:33:36,160
is the downstream effect of it. So not even intentionally

464
00:33:36,160 --> 00:33:43,279
demeaning In fact, probably quite unintentional, but that's what happens.

465
00:33:44,500 --> 00:33:48,460
I mean isn't the whole thing the result of just

466
00:33:48,460 --> 00:33:53,529
– I think your original idea of this is all

467
00:33:53,529 --> 00:33:59,710
downstream from Silicon Valley is probably the truth. Yeah. Nobody

468
00:33:59,710 --> 00:34:05,230
– so let's go back to – The 19 –

469
00:34:05,230 --> 00:34:09,570
let's go back to the 1920s. Go back to the

470
00:34:09,570 --> 00:34:15,019
Model A and the Model T Ford. When you drove

471
00:34:15,019 --> 00:34:18,449
this thing, it wasn't – if you were going to

472
00:34:18,449 --> 00:34:21,878
– if you bought a Model T – And you

473
00:34:21,878 --> 00:34:25,070
drove it on a daily basis. The amount of things

474
00:34:25,070 --> 00:34:28,599
you had to go through. But there was a –

475
00:34:28,599 --> 00:34:34,369
so the internal combustion engine – It has to have

476
00:34:34,369 --> 00:34:39,090
ignition within an internal combustion engine. So as the piston

477
00:34:39,090 --> 00:34:46,880
approaches the top of its travel. Maximum compression. Maximum compression

478
00:34:46,880 --> 00:34:52,039
of the air and gas mixture. And the moment that

479
00:34:52,039 --> 00:34:56,619
the spark plug fires to ignite it, which will then

480
00:34:56,619 --> 00:35:00,510
drive it down, And spin the crankshaft on the next

481
00:35:00,510 --> 00:35:07,289
phase of its rotation. Yes. That point of ignition... The

482
00:35:07,289 --> 00:35:15,570
explosion, an ignition of an explosive material is a static

483
00:35:15,570 --> 00:35:20,559
event. It happens over a static amount of time. But

484
00:35:20,559 --> 00:35:26,159
as the engine goes faster, the time that is allotted

485
00:35:26,159 --> 00:35:30,159
for that to happen is... gets shorter and shorter and

486
00:35:30,159 --> 00:35:33,170
shorter. So the explosion inside of a piston is a

487
00:35:33,170 --> 00:35:38,059
static event inside of a dynamic environment. So in order

488
00:35:38,059 --> 00:35:42,820
to account for that, you have to start the ignition,

489
00:35:42,820 --> 00:35:45,550
that point of ignition within the cylinder. You have to

490
00:35:45,550 --> 00:35:50,449
start that process sooner. It has to happen earlier in

491
00:35:50,449 --> 00:35:57,340
order for the explosion to finish at the correct moment.

492
00:35:58,470 --> 00:36:01,320
where the piston is going to be in its travel.

493
00:36:01,940 --> 00:36:05,369
So there's a thing called ignition advance. So as the

494
00:36:05,369 --> 00:36:08,940
engine goes faster, the spark has to start earlier and

495
00:36:08,940 --> 00:36:14,829
earlier and earlier. Okay. I'm familiar with the workings of

496
00:36:14,829 --> 00:36:18,340
the combustion engine. You are. You are. But we get

497
00:36:18,340 --> 00:36:21,980
nerds in the boardroom that don't know. No, no, no.

498
00:36:22,179 --> 00:36:28,279
Stop. This used to be taught. In schools. Shop class.

499
00:36:28,380 --> 00:36:32,380
Yes. There is no shop class anymore. And exactly my

500
00:36:32,380 --> 00:36:37,970
point. There is no education. But we as a podcast

501
00:36:37,970 --> 00:36:52,610
community have failed with the education and the... Commercials. That

502
00:36:52,610 --> 00:36:58,029
is not acceptable. That's not acceptable. The monies, people who

503
00:36:58,029 --> 00:37:06,730
care about monies... The product. Yeah. They have... They hijacked

504
00:37:06,730 --> 00:37:11,900
this to the point now where they're being eaten themselves

505
00:37:11,900 --> 00:37:15,139
by nonsense that has nothing to do with podcasting, such

506
00:37:15,139 --> 00:37:21,809
as YouTube, etc. Because, And, you know, I'm sure you

507
00:37:21,809 --> 00:37:25,820
saw the story about the children's channel that was taken

508
00:37:25,820 --> 00:37:28,779
down from YouTube. And, you know, we don't know why.

509
00:37:29,019 --> 00:37:32,840
But thank God, thanks to the 33,000 readers of James's

510
00:37:32,840 --> 00:37:36,570
email newsletter, the YouTube caught wind of it and brought

511
00:37:36,570 --> 00:37:39,829
it back. But the whole thing should have never happened

512
00:37:39,829 --> 00:37:47,059
in the first place. It really shouldn't have. That was

513
00:37:47,059 --> 00:37:52,779
the whole point of it. Mm-hmm. So anyway, we don't.

514
00:37:53,139 --> 00:37:57,900
Yeah. I know you mean well. Well, I mean, I

515
00:37:57,900 --> 00:38:02,099
think you're on the right track because the point I

516
00:38:02,099 --> 00:38:05,500
was trying to make with all that is that in

517
00:38:05,500 --> 00:38:10,059
the early days of automobiles, this process of advancing the

518
00:38:10,059 --> 00:38:12,720
ignition the faster you went was a stick on the

519
00:38:12,720 --> 00:38:16,150
side of your steering wheel. Yeah. Yeah. I know you

520
00:38:16,150 --> 00:38:19,940
had to manually click as you went faster. The engine

521
00:38:19,940 --> 00:38:22,000
would start to drive like crap and you would click

522
00:38:22,000 --> 00:38:24,059
it down to the next setting. And then you went

523
00:38:24,059 --> 00:38:25,539
a little bit faster and you click it down to

524
00:38:25,539 --> 00:38:28,019
the next setting. This was a manual thing you had

525
00:38:28,019 --> 00:38:30,220
to do as you drove. Okay, so now what you're

526
00:38:30,220 --> 00:38:33,190
talking about. And everybody knew this. Right. And my dad

527
00:38:33,190 --> 00:38:36,579
had Model A's. And he and his brother would crash

528
00:38:36,579 --> 00:38:39,570
them and stuff. So I've heard plenty of stories about

529
00:38:39,570 --> 00:38:43,750
Model A's. But... So now we get into basically the

530
00:38:43,750 --> 00:38:46,720
crux of it is because there is no education of

531
00:38:46,720 --> 00:38:49,610
how things – whenever someone says, hey, I want my

532
00:38:49,610 --> 00:38:53,000
kid to learn about computers, I say, toss him an

533
00:38:53,000 --> 00:38:56,599
old laptop, give him a USB stick with Ubuntu on

534
00:38:56,599 --> 00:38:59,760
it. Tell them to install it and figure it out

535
00:38:59,760 --> 00:39:01,820
and tell them to come back when the thing is

536
00:39:01,820 --> 00:39:06,440
working. It's on Wi-Fi and they've learned some stuff. This

537
00:39:06,440 --> 00:39:08,820
is the same when I, you know, I've been flying

538
00:39:08,820 --> 00:39:13,559
since 2006. I wanted to be able to rent a

539
00:39:13,559 --> 00:39:16,289
plane, so I go to the... to the airport in

540
00:39:16,289 --> 00:39:21,150
Bernie, and I need to be educated on the Cirrus

541
00:39:21,150 --> 00:39:25,900
aircraft platform, which is all garmin g1000 i've never flown

542
00:39:25,900 --> 00:39:28,440
with it or i had never flown with a glass

543
00:39:28,440 --> 00:39:31,389
cockpit i use the six pack six dials you know

544
00:39:31,389 --> 00:39:34,970
you got your you got your airspeed indicator got your

545
00:39:34,970 --> 00:39:38,659
horizon uh you've got your attitude indicator and that's really

546
00:39:38,659 --> 00:39:41,090
it you don't need much more but you got you

547
00:39:41,090 --> 00:39:45,269
know some engine management so i'm in this uh in

548
00:39:45,269 --> 00:39:49,679
the Cirrus, and we're doing an instrument approach, and the

549
00:39:49,679 --> 00:39:54,619
instructor says, okay, you know, so do your teardrop now,

550
00:39:54,619 --> 00:39:58,260
you know, this particular method you take. And I've done

551
00:39:58,260 --> 00:39:59,980
these before, it's just I'd never done it on.

552
00:40:00,451 --> 00:40:05,711
computerized airplane. And so the way you typically do it

553
00:40:05,711 --> 00:40:08,611
is you have a standard rate turn and you have

554
00:40:08,611 --> 00:40:10,631
a stopwatch that you used to just literally have a

555
00:40:10,631 --> 00:40:13,051
stopwatch in the cockpit and you hit it, you know,

556
00:40:13,091 --> 00:40:15,891
after 30 seconds, you know that you're exactly back at

557
00:40:15,891 --> 00:40:18,311
the right end of the teardrop. Sometimes it's a minute.

558
00:40:18,471 --> 00:40:21,191
It depends. But, It depends on the chart and the

559
00:40:21,191 --> 00:40:23,591
approach plate and everything that you have. And I look

560
00:40:23,591 --> 00:40:27,471
at this cockpit and it has arrows indicating everything that

561
00:40:27,471 --> 00:40:30,141
I have to do. And I say, wait a minute,

562
00:40:30,141 --> 00:40:33,111
can you use this in the test? They say, oh,

563
00:40:33,111 --> 00:40:36,111
yeah, yeah, yeah. When you do the test, you just

564
00:40:36,111 --> 00:40:43,151
fly the arrow. which is great but if that fails

565
00:40:43,151 --> 00:40:46,491
people will die because they don't know how to do

566
00:40:46,491 --> 00:40:50,741
it anymore so that is in general where technology always

567
00:40:50,741 --> 00:40:53,491
takes us and so now we're you know what this

568
00:40:53,491 --> 00:40:56,851
is this is called techno solutionism oh i like that

569
00:40:56,851 --> 00:40:59,641
that's a good phrase I heard that this morning. This

570
00:40:59,641 --> 00:41:09,331
is TechnoSolutionism. Yeah, well... It's – some technology company somewhere

571
00:41:09,331 --> 00:41:13,381
gives you a solution to a problem, and it ratchets

572
00:41:13,381 --> 00:41:17,841
the knowledge base of the population down a notch, and

573
00:41:17,841 --> 00:41:22,191
you can't – and now you're completely dependent on the

574
00:41:22,191 --> 00:41:30,031
thing. And it's not like that's always a flat negative,

575
00:41:30,031 --> 00:41:36,891
but it's the same reason that if ever I was

576
00:41:36,891 --> 00:41:40,401
learning a new programming language or something like that, I

577
00:41:40,401 --> 00:41:44,941
would always go back – And by the – I

578
00:41:44,941 --> 00:41:49,521
would try to find the original books of whatever that

579
00:41:49,521 --> 00:41:52,931
thing is, like C. You go back and you get

580
00:41:52,931 --> 00:41:56,771
a copy of the C programming language by Kernighan and

581
00:41:56,771 --> 00:42:02,211
Ritchie or Java. You would get the original Java documentation

582
00:42:02,211 --> 00:42:05,621
from Sun Microsystems. But you go try to find the

583
00:42:05,621 --> 00:42:10,011
earliest incantation of that thing so that you could, like,

584
00:42:10,011 --> 00:42:14,051
get familiar with what the base level of the technology

585
00:42:14,051 --> 00:42:17,491
was and then move your understanding forward through history to

586
00:42:17,491 --> 00:42:19,971
try to catch up. But you had to make sure

587
00:42:19,971 --> 00:42:23,931
you knew the basics first because otherwise you're just at

588
00:42:23,931 --> 00:42:26,961
the – you're always being – Driven by the whim

589
00:42:26,961 --> 00:42:31,691
of whatever the latest technological feature at, you know, Sprint

590
00:42:31,691 --> 00:42:35,061
is or whatever that you never really fully get an

591
00:42:35,061 --> 00:42:38,951
understanding of of the foundations of why the stuff is

592
00:42:38,951 --> 00:42:43,691
the way it is to begin with. And I mean,

593
00:42:43,691 --> 00:42:48,231
maybe to me, that's what happened. I mean, it's podcasting.

594
00:42:48,331 --> 00:42:52,541
I mean, in the original days, everybody understood that the

595
00:42:52,541 --> 00:42:55,741
podcast feed – Because you had to copy and paste

596
00:42:55,741 --> 00:43:00,971
that thing into your software. Yes, into your podcatcher. Yeah,

597
00:43:00,971 --> 00:43:05,171
but then it went into iTunes, and the whole idea

598
00:43:05,171 --> 00:43:10,191
that there even was a feed was just disappeared. Well,

599
00:43:11,481 --> 00:43:17,891
Not from the hosting side. That's where the idea disappeared.

600
00:43:18,031 --> 00:43:23,721
I'm kind of blaming the hosters. Well, I mean, that's

601
00:43:23,721 --> 00:43:28,671
a solution to sort of a problem, I guess. Anyway,

602
00:43:28,671 --> 00:43:31,681
so take me back to the index. So now the

603
00:43:31,681 --> 00:43:36,851
feed is no longer the podcast. So what is it?

604
00:43:39,111 --> 00:43:41,361
The feed is what happened to the feed is the

605
00:43:41,361 --> 00:43:45,881
source of truth. It still is. It still is because

606
00:43:45,881 --> 00:43:50,811
the feed is how the podcast works. you know, represents

607
00:43:50,811 --> 00:43:54,701
itself to the world. But now there's the – it's

608
00:43:54,701 --> 00:43:58,951
just no longer the identity layer, the top level of

609
00:43:58,951 --> 00:44:04,981
the identity layers. So you have a podcast. So there's

610
00:44:04,981 --> 00:44:09,231
– as the database stands – Today, as we speak.

611
00:44:10,501 --> 00:44:16,651
The podcast table exists in the index database. And it

612
00:44:16,651 --> 00:44:24,621
has all the proper... All the proper metadata columns. So

613
00:44:24,621 --> 00:44:30,551
let me pull it up. Let's see. Let me refresh

614
00:44:30,551 --> 00:44:37,951
this. Okay. So there's now a podcast table. that has

615
00:44:39,421 --> 00:44:43,171
A feed ID, excuse me, has a feed, an ID,

616
00:44:43,171 --> 00:44:52,031
a feed ID. An iTunes ID. The GUID. and a

617
00:44:52,031 --> 00:44:57,941
few other incidentals. So dead being one of them. So

618
00:44:57,941 --> 00:45:01,431
now the next thing that's going to happen is there's

619
00:45:01,431 --> 00:45:09,561
going to be a seeding process. where The news feeds

620
00:45:09,561 --> 00:45:15,491
table is going to begin to populate The podcast table

621
00:45:15,491 --> 00:45:19,371
with the current as best we know the current URL

622
00:45:19,371 --> 00:45:22,821
of the feed and then it will link back and

623
00:45:22,821 --> 00:45:27,221
then the podcast table entry will link back to that

624
00:45:27,221 --> 00:45:32,531
news feeds table ID row. So the podcast table is

625
00:45:32,531 --> 00:45:35,331
going to reference the news feeds table as a sort

626
00:45:35,331 --> 00:45:39,921
of child of itself. So now if no agenda moves

627
00:45:39,921 --> 00:45:43,711
to a new URL, we're going to have both of

628
00:45:43,711 --> 00:45:50,511
those URLs correctly in the news feeds table, But now

629
00:45:50,511 --> 00:45:54,811
the podcast table will just be flipped to reference the

630
00:45:54,811 --> 00:46:00,991
other topics. feed instead of the old one. Okay. Now

631
00:46:00,991 --> 00:46:03,161
I'm going to – I think I'm going to agree

632
00:46:03,161 --> 00:46:08,621
with Daniel J. Lewis. You are now fixing problems that

633
00:46:08,621 --> 00:46:15,391
poor education has created because we know there's a mechanism

634
00:46:15,391 --> 00:46:18,391
to do this. And we know there's a temporary and

635
00:46:18,391 --> 00:46:23,961
a permanent redirect. Right. And, you know, for probably obvious

636
00:46:23,961 --> 00:46:30,241
commercial reasons, the commercials don't really surface that information very

637
00:46:30,241 --> 00:46:33,441
well. So that's why you wind up with seven different

638
00:46:33,441 --> 00:46:38,831
feeds instead of people doing permanent redirects. And honestly, I

639
00:46:38,831 --> 00:46:41,011
don't know. I think you should break shit, man. Break

640
00:46:41,011 --> 00:46:43,911
it so people go, how come that broke? Well, it

641
00:46:43,911 --> 00:46:47,151
broke because you don't have a redirect on your feed.

642
00:46:47,531 --> 00:46:51,461
Oh, okay. I mean, that's I think you need to

643
00:46:51,461 --> 00:46:54,491
push that back to the origin and not be solving

644
00:46:54,491 --> 00:46:57,341
it with, you know, because there'll be yet another problem

645
00:46:57,341 --> 00:46:59,931
down the line. There'll be something else. And, you know,

646
00:46:59,931 --> 00:47:03,391
you're fixing stuff that is very, very it's tough. It's

647
00:47:03,391 --> 00:47:05,081
hard stuff to do. And I don't think it should

648
00:47:05,081 --> 00:47:09,501
be your responsibility. Well, I don't necessarily disagree with the

649
00:47:09,501 --> 00:47:13,481
sentiment, but. Here's what makes me feel bad. Things my

650
00:47:13,481 --> 00:47:16,771
wife says to me all the time. I don't necessarily

651
00:47:16,771 --> 00:47:20,221
disagree with the sentiment, but take out the garbage. But

652
00:47:20,221 --> 00:47:25,411
those dishes sure have been sitting there for a while.

653
00:47:26,191 --> 00:47:31,711
Yes. But here's what makes me want to solve this

654
00:47:31,711 --> 00:47:41,731
problem, though. is that People like people like James email

655
00:47:41,731 --> 00:47:45,951
me because they get bugged by their by people. So

656
00:47:45,951 --> 00:47:49,201
somebody will email James and say, hey, my stuff is

657
00:47:49,201 --> 00:47:53,141
screwed up on pod news. And then he'll spend his

658
00:47:53,141 --> 00:47:57,411
time digging into it and and forward the email to

659
00:47:57,411 --> 00:48:01,731
me. And say, hey, here's this problem, and these feed

660
00:48:01,731 --> 00:48:04,701
URLs were messed up, and I went – and he

661
00:48:04,701 --> 00:48:08,761
will – and I appreciate this deeply. He will get

662
00:48:08,761 --> 00:48:12,921
into the index dashboard, admin dashboard, and fix a bunch

663
00:48:12,921 --> 00:48:17,171
of stuff. Mark things correctly. Like what kind of stuff?

664
00:48:17,171 --> 00:48:19,771
Hey, I fixed this. What kind of stuff? Just specifically.

665
00:48:20,671 --> 00:48:23,041
Just like that thing, though, like a scenario I mentioned

666
00:48:23,041 --> 00:48:25,661
earlier. Somebody has two or three feeds or four or

667
00:48:25,661 --> 00:48:27,691
five, and he'll get in there and just sort it

668
00:48:27,691 --> 00:48:30,891
all out. Well, how about this? How about this? And

669
00:48:30,891 --> 00:48:32,441
I just don't want this. I don't want – and

670
00:48:32,441 --> 00:48:34,791
the same thing happens with Gordon. Gordon. Gordon has to

671
00:48:34,791 --> 00:48:37,501
deal with these customer inquiries about feeds that are that

672
00:48:37,501 --> 00:48:39,981
are screwed up. And I don't want that stuff to

673
00:48:39,981 --> 00:48:43,461
be like always landing on other people. Right. But then

674
00:48:43,461 --> 00:48:47,541
it always lands on one person. And that's you. I'm

675
00:48:47,541 --> 00:48:50,631
not. I think we know. So, OK, maybe this is

676
00:48:50,631 --> 00:48:57,751
the part I haven't said yet. I think that this

677
00:48:57,751 --> 00:49:04,051
structure of having the podcast identity layer be above the

678
00:49:04,051 --> 00:49:08,691
feed layer – will make all of our lives easier.

679
00:49:09,971 --> 00:49:18,031
Because, We can now see the proper audit trail. Of

680
00:49:18,031 --> 00:49:23,221
how things came to be. Okay. You know, the problem

681
00:49:23,221 --> 00:49:26,681
is that we've – one of the strongest signals we

682
00:49:26,681 --> 00:49:30,791
have is, well – iTunes, Apple podcast directory says that

683
00:49:30,791 --> 00:49:32,631
the feed URL for this thing is supposed to be

684
00:49:32,631 --> 00:49:35,941
X. Okay. I think I have. You're right, Eric PP,

685
00:49:35,941 --> 00:49:38,561
because I've talked about this before, and now I'm really

686
00:49:38,561 --> 00:49:41,641
going to do it. When you have done this abstraction

687
00:49:41,641 --> 00:49:45,431
layer. This is what the podcast is. Make him talk

688
00:49:45,431 --> 00:49:50,961
to Potty. Exactly. Potty. I will build Potty and Potty

689
00:49:50,961 --> 00:49:56,371
will have API access and will be able to explain

690
00:49:56,371 --> 00:49:59,991
the issue to the normie. Potty talks to the normie.

691
00:50:00,063 --> 00:50:03,883
Coddy says, hey, Normie, here's your issue. Here's how you

692
00:50:03,883 --> 00:50:08,703
can go and fix it. Potty bot. Yeah, potty bot.

693
00:50:08,783 --> 00:50:12,143
Potty bot talks to normie person. And then you can

694
00:50:12,143 --> 00:50:15,363
go and say, okay, your problem is that you have

695
00:50:15,363 --> 00:50:18,373
all these different feeds. Now, what you should do is

696
00:50:18,373 --> 00:50:21,443
go to these accounts and either have them put in

697
00:50:21,443 --> 00:50:24,643
a redirect or have them nuke your feed and you

698
00:50:24,643 --> 00:50:27,893
do the proper work. And the last thing it says

699
00:50:27,893 --> 00:50:31,683
is none of that works. Email Ted. No, no, no.

700
00:50:31,683 --> 00:50:35,353
No, no. It says Apple.com. No, we'll always end up

701
00:50:35,353 --> 00:50:39,593
with here's two things you should note. Because that's what

702
00:50:39,593 --> 00:50:43,003
PottyBot does. Two important things I don't want to overlook

703
00:50:43,003 --> 00:50:47,953
before you continue. Yes, because that's what PottyBot does. That's

704
00:50:47,953 --> 00:50:52,623
what PottyBot does. It's going to tell them what the

705
00:50:52,623 --> 00:50:56,923
gates are and what the load-bearing issues are with their

706
00:50:56,923 --> 00:51:00,603
podcast. So can we leave that where it is and

707
00:51:00,603 --> 00:51:02,823
agree that that's the solution? If you're going to create

708
00:51:02,823 --> 00:51:06,793
the abstraction layer, I'll create the potty bot. Okay, because

709
00:51:06,793 --> 00:51:09,483
I will do it. I will do it. I just

710
00:51:09,483 --> 00:51:13,183
wanted to talk to people in an audible voice because

711
00:51:13,183 --> 00:51:16,243
I feel like that's really important. It looks like your

712
00:51:16,243 --> 00:51:21,983
feed screwed up. This URL is effed. That's exactly what

713
00:51:21,983 --> 00:51:24,703
it will do. I guarantee it. I will pass it

714
00:51:24,703 --> 00:51:31,533
through a language gate. WTF? WTF, dude. What did you

715
00:51:31,533 --> 00:51:34,553
do? How many hosts have you had in the last

716
00:51:34,553 --> 00:51:38,783
60 days? Did you use protection on all those hosts?

717
00:51:38,903 --> 00:51:42,823
Because you're carrying viruses, man. This is no good. And

718
00:51:42,823 --> 00:51:46,533
we're laughing about this, but just as one side note

719
00:51:46,533 --> 00:51:51,453
for a moment. We are completely in the golden, golden

720
00:51:51,453 --> 00:51:57,813
age of podcasting. And with podcasting, I mean specifically humans

721
00:51:57,813 --> 00:52:02,293
talking, probably not even video. I don't know if you

722
00:52:02,293 --> 00:52:08,073
ever are looking for stuff on YouTube, but... If it's

723
00:52:08,073 --> 00:52:13,083
not an AI-generated character, which increasingly they are, and they're

724
00:52:13,083 --> 00:52:17,743
very realistic, if it's not an AI-generated voice, which increasingly

725
00:52:17,743 --> 00:52:23,653
are quite good and almost undetectable, it always, always, always

726
00:52:23,653 --> 00:52:30,573
is noticeable in the writing. I see people reading AI-generated

727
00:52:30,573 --> 00:52:36,553
scripts all day long. The latest episode of Buzzcast, Alvin

728
00:52:36,553 --> 00:52:40,343
Brooke talks about this exact thing. Yeah, I think he's

729
00:52:40,343 --> 00:52:43,173
seeing it too. And I don't know if you know

730
00:52:43,173 --> 00:52:47,103
who Stanley Druckenmiller is? Yeah. So he wrote in his

731
00:52:47,103 --> 00:52:50,573
Wall Street Journal op ed. I'm not embarrassed by it.

732
00:52:50,573 --> 00:52:53,613
I write everything using AI now for the same reason

733
00:52:53,613 --> 00:52:56,433
I use a calculator when I do math problems. I

734
00:52:56,433 --> 00:52:58,883
don't know why this is relevant. My name is on

735
00:52:58,883 --> 00:53:03,563
the piece. It's my message. Now, here's the difference. Stanley

736
00:53:03,563 --> 00:53:07,493
is a writer. And he goes in and he deletes

737
00:53:07,493 --> 00:53:13,133
all the superfluous language that every single model known to

738
00:53:13,133 --> 00:53:18,183
man outputs. Then he knows the result that he wants.

739
00:53:18,583 --> 00:53:22,773
People who just want to do podcasts and YouTube videos,

740
00:53:22,773 --> 00:53:27,333
they don't know what good writing is. And it's becoming

741
00:53:27,333 --> 00:53:31,863
tedious. And more and more people, there are YouTubers who

742
00:53:31,863 --> 00:53:36,023
are getting called out on it now. Good. Yes. Good.

743
00:53:36,203 --> 00:53:39,823
But that's why people who can just crack a mic

744
00:53:39,823 --> 00:53:45,563
and talk and have a conversation or explain a topic

745
00:53:45,563 --> 00:53:50,753
or discuss something who just know how to – grab

746
00:53:50,753 --> 00:53:54,363
an audience, are now rising to the top. The cream

747
00:53:54,363 --> 00:53:57,293
is rising. That's an old silicon valve. Well, the cream

748
00:53:57,293 --> 00:54:00,123
all is rising to the top. Yes, it does. And

749
00:54:00,123 --> 00:54:08,643
all this pollution, this verbal pollution, is making room for...

750
00:54:09,393 --> 00:54:14,103
Pure human product that is going to excel. It is

751
00:54:14,103 --> 00:54:19,773
a golden time for podcasting. Verbal pollution. Like that. That's

752
00:54:19,773 --> 00:54:23,963
a good. I have not thought about it that way.

753
00:54:24,083 --> 00:54:26,903
And I think you're right. And this is I heard

754
00:54:26,903 --> 00:54:34,393
somebody call it. I heard it called unintelligiblish. That's pretty

755
00:54:34,393 --> 00:54:41,943
much sums it up. Yeah. Yeah. But it's also prevalent

756
00:54:41,943 --> 00:54:45,183
in the workplace. Work slot. Do you see it? You

757
00:54:45,183 --> 00:54:47,673
get an email from somebody. Oh, no, you didn't write

758
00:54:47,673 --> 00:54:53,393
that. Okay. Inundated with it. Inundated. All day long. It's

759
00:54:53,393 --> 00:54:57,953
so tedious. It wastes other people's time. And it's so

760
00:54:57,953 --> 00:55:01,553
much. I mean, do they actually do that because it

761
00:55:01,553 --> 00:55:04,343
fills up the prompt and it uses more tokens? I

762
00:55:04,343 --> 00:55:07,693
mean, is that the idea behind it? Because there is

763
00:55:07,693 --> 00:55:11,163
no reason. Whatsoever. No. I mean, I can look at

764
00:55:11,163 --> 00:55:14,833
four paragraphs coming out of, you know, Claude code and

765
00:55:14,833 --> 00:55:16,833
say, so what do I have to do? And then

766
00:55:16,833 --> 00:55:19,563
in one sentence, it'll say, oh, just tell me if

767
00:55:19,563 --> 00:55:24,943
you want me to delete that file. Three paragraphs. Right.

768
00:55:25,283 --> 00:55:28,423
I don't need to know all this. It's just like,

769
00:55:28,423 --> 00:55:30,883
well, what do you – you forgot to actually convey

770
00:55:30,883 --> 00:55:36,143
the message. This happens with everything. People who think they

771
00:55:36,143 --> 00:55:40,783
can do marketing can't do marketing because you're not doing

772
00:55:40,783 --> 00:55:45,693
effective – You don't have the craft. And this can't

773
00:55:45,693 --> 00:55:48,893
come out of a large language model. If you're charging

774
00:55:48,893 --> 00:55:52,233
based on input tokens and output tokens, which all these

775
00:55:52,233 --> 00:55:54,823
APIs do, well, then the more output tokens, the better,

776
00:55:54,823 --> 00:55:59,963
right? Yeah. You're getting paid, baby. That has to be

777
00:55:59,963 --> 00:56:02,983
some part of it. I can't imagine why it's not.

778
00:56:03,563 --> 00:56:05,473
It has to be. It has to be. By the

779
00:56:05,473 --> 00:56:15,383
way, my agentic experimentation phase is – Quite crazy. Oh,

780
00:56:15,383 --> 00:56:22,143
yeah, with your isolated bot doing stuff. Yeah. I've had

781
00:56:22,143 --> 00:56:29,503
some big wins and some complete head slappers. Yeah. One

782
00:56:29,503 --> 00:56:32,483
thing. So I've been trying to – I was trying

783
00:56:32,483 --> 00:56:35,803
to read this paper. And this is a whole other

784
00:56:35,803 --> 00:56:38,423
topic I don't want to get into by itself that

785
00:56:38,423 --> 00:56:40,963
I'm not qualified to speak to. But I was trying

786
00:56:40,963 --> 00:56:43,523
to read this paper on – it's one of the

787
00:56:43,523 --> 00:56:46,483
original papers on the topic. This kind of goes back

788
00:56:46,483 --> 00:56:48,153
to what I was talking about earlier. I always had

789
00:56:48,153 --> 00:56:50,603
this tendency to go back to the earliest thing I

790
00:56:50,603 --> 00:56:53,583
can find on a thing. earliest documents I can find

791
00:56:53,583 --> 00:56:57,513
about a thing. And it's called, well, I literally just

792
00:56:57,513 --> 00:57:06,513
did this. It's called... Let me find it. Users bouncing

793
00:57:06,513 --> 00:57:10,243
around my machine here, PI. The PI coding harness is

794
00:57:10,243 --> 00:57:17,683
so good. Sandbox. There it is. So it's called –

795
00:57:17,683 --> 00:57:24,353
it's by Warren McCullough and Walter Pitts from 1943, I

796
00:57:24,353 --> 00:57:30,163
think. I don't remember the exact date, but it's called

797
00:57:30,163 --> 00:57:33,723
A Logical Calculus of the Ideas Imminent in Nervous Activity.

798
00:57:35,543 --> 00:57:39,903
And it's 1943. So this is one of the original

799
00:57:39,903 --> 00:57:48,963
papers describing what we know as neural networks. It's a

800
00:57:48,963 --> 00:57:53,183
fundamental building block behind machine learning and LLMs and all

801
00:57:53,183 --> 00:57:55,353
this stuff. So I just wanted to get a copy

802
00:57:55,353 --> 00:57:57,773
of this paper because I wanted to see – I

803
00:57:57,773 --> 00:58:02,103
wanted to read it. Well, the only thing I could

804
00:58:02,103 --> 00:58:04,763
find was on archive.org, and it was a complete mess.

805
00:58:05,763 --> 00:58:11,843
It was just like some... The HTML was so gross.

806
00:58:12,503 --> 00:58:15,623
It was like an OCR output of something that just

807
00:58:15,623 --> 00:58:19,823
got wrapped. It had 8,000 span tags in it. So

808
00:58:19,823 --> 00:58:25,663
I was like, okay, well, between – activities on the

809
00:58:25,663 --> 00:58:28,833
agent here. So I gave it the URL to the

810
00:58:28,833 --> 00:58:33,423
archive.org document, and I just said, I did this yesterday

811
00:58:33,423 --> 00:58:40,743
before dinner. I said, convert this... download this document and

812
00:58:40,743 --> 00:58:44,483
convert it into something that is friendly, that is HTML,

813
00:58:44,483 --> 00:58:50,123
that's friendly to screen readers and overall a better format.

814
00:58:50,123 --> 00:58:52,483
It's the only prompt I gave it. It did not

815
00:58:52,483 --> 00:58:58,143
finish until 9 o'clock this morning. It ran for like

816
00:58:58,383 --> 00:59:02,703
12 hours on this thing. Now, what it produced is

817
00:59:02,703 --> 00:59:05,573
great. It looks really good, but it's only a 17-page

818
00:59:05,573 --> 00:59:09,063
document. It's not like it's that big of a deal.

819
00:59:09,063 --> 00:59:12,573
So that was super weird, and I don't exactly –

820
00:59:12,573 --> 00:59:15,723
what it ended up doing, and this is part of

821
00:59:15,723 --> 00:59:19,653
why I'm doing these experiments is because I want to

822
00:59:19,653 --> 00:59:23,863
get a sense of what – Of the way that

823
00:59:23,863 --> 00:59:34,103
these things rabbit trail. And what it... detected was that

824
00:59:34,103 --> 00:59:38,963
the formulas in the original thing had been replaced by

825
00:59:38,963 --> 00:59:44,123
best effort ASCII and that they were not accurate and

826
00:59:45,123 --> 00:59:47,363
So it goes off in trying to find a copy

827
00:59:47,363 --> 00:59:52,203
of the original paper, a scan copy, and crop out

828
00:59:52,203 --> 00:59:56,213
the formulas that were in the scan copy that were

829
00:59:56,213 --> 00:59:59,843
the accurate formulas. And...

830
01:00:00,959 --> 01:00:06,719
Then reconstruct each little fragment of the scan image of

831
01:00:06,719 --> 01:00:15,279
the formula into... uh, either equivalent Unicode or SVG. And

832
01:00:15,279 --> 01:00:18,249
that's what it was doing for like 10 hours. Oh

833
01:00:18,249 --> 01:00:23,359
man. It got completely unnecessary. Unnecessary. Yeah. Yeah. And it

834
01:00:23,359 --> 01:00:27,599
did it. And it looks, and it looks amazing. But,

835
01:00:27,699 --> 01:00:31,429
um, it, I never asked any of that. No, no,

836
01:00:31,429 --> 01:00:35,439
I know. I've seen these things happen. Yeah, so these

837
01:00:35,439 --> 01:00:40,419
things are... These things are kind of nuts, man. Yeah.

838
01:00:40,499 --> 01:00:42,619
You don't know what they're going to do. And this

839
01:00:42,619 --> 01:00:45,909
has been a very good learning experience for me to

840
01:00:45,909 --> 01:00:50,189
realize because what I've realized is – because I want

841
01:00:50,189 --> 01:00:54,569
to eventually begin to use these things if possible to

842
01:00:54,569 --> 01:00:58,559
do some automated tasks or the index and that kind

843
01:00:58,559 --> 01:01:02,579
of thing. Yeah. I can't unleash anything on the index

844
01:01:02,579 --> 01:01:07,319
until I fully understand what the downfalls and gotches are.

845
01:01:07,319 --> 01:01:10,299
You won't be able to do it ever. Okay. And

846
01:01:10,299 --> 01:01:12,929
I'll explain why. So I have a process I've had

847
01:01:12,929 --> 01:01:16,319
in place for almost a year. It's refined over time.

848
01:01:17,179 --> 01:01:21,299
but I have a doctrine which has a code word,

849
01:01:21,439 --> 01:01:25,799
and the code word is SWEEP, S-W-E-E-P, all uppercase. That

850
01:01:25,799 --> 01:01:29,089
means... That the agent needs to go look at all

851
01:01:29,089 --> 01:01:33,049
the aggregated sources that are just running on two-hour cron

852
01:01:33,049 --> 01:01:38,649
jobs, you know, several hundred RSS feeds, a couple of

853
01:01:38,649 --> 01:01:42,339
scrapers for – A few, I mean, some of them

854
01:01:42,339 --> 01:01:46,639
are, you know, some YouTube channels. It's aggregated. That's non-AI

855
01:01:46,639 --> 01:01:52,359
stuff, just aggregated, sitting there in a bucket. And a

856
01:01:52,359 --> 01:01:57,909
summary has been made by Quinn 3.3, a very short

857
01:01:57,909 --> 01:02:02,099
summary of each item that comes in, if it already

858
01:02:02,099 --> 01:02:05,249
isn't a summary. And the sweep doctrine says go and

859
01:02:05,249 --> 01:02:09,099
get all the – that's usually between every No Agenda

860
01:02:09,099 --> 01:02:13,099
show, it's 1,000 stories. And then it dedupes them, you

861
01:02:13,099 --> 01:02:15,899
know, so it gets down to probably about 400. And

862
01:02:15,899 --> 01:02:19,689
then it checks them against topics that have their recent

863
01:02:19,689 --> 01:02:23,059
topics. And so it brings it down to somewhere around

864
01:02:23,059 --> 01:02:28,149
90 different stories, which I want to have either if

865
01:02:28,149 --> 01:02:30,539
it's a video or something, then it is going to

866
01:02:30,539 --> 01:02:35,879
create clips from it. And it will do that. Or...

867
01:02:36,309 --> 01:02:39,499
Or you have to go find a video about this

868
01:02:39,499 --> 01:02:41,839
story. But usually these are for clips. So that's kind

869
01:02:41,839 --> 01:02:44,279
of the 90, and that's way too many. And so

870
01:02:44,279 --> 01:02:48,789
it gives me a markdown document with checkboxes, and I

871
01:02:48,789 --> 01:02:51,929
click because there's a little summary. I click about 40,

872
01:02:51,929 --> 01:02:54,609
that's it. It goes off and cuts them. That's a

873
01:02:54,609 --> 01:02:57,279
whole other thing. That's a whole other process, which I've

874
01:02:57,279 --> 01:03:01,249
actually kind of perfected now. And Wednesday, I did this

875
01:03:01,249 --> 01:03:05,849
for the No Agenda for Yesterday. And I see in

876
01:03:05,849 --> 01:03:12,839
the rolling terminal, the TUI, I see it's saying, oh,

877
01:03:12,839 --> 01:03:17,109
it's selecting stories. And I say... And I actually type

878
01:03:17,109 --> 01:03:20,329
into the terminal. I say, I haven't ticked any boxes

879
01:03:20,329 --> 01:03:23,679
yet. You haven't given me a document. It ignores me,

880
01:03:23,679 --> 01:03:28,109
keeps on going. And here's the thing, though. It cut

881
01:03:28,109 --> 01:03:36,069
50 clips. perfectly categorized, fantastic stories, stuff I – it

882
01:03:36,069 --> 01:03:39,019
was like, wow, this is exactly the right story, exactly

883
01:03:39,019 --> 01:03:42,209
the right clips, the right amount. And so I said,

884
01:03:42,209 --> 01:03:45,419
all right, you know, save everything you did for a

885
01:03:45,419 --> 01:03:49,259
postmortem. So after the show yesterday, I'm like, okay, what

886
01:03:49,259 --> 01:03:52,399
happened? Because I didn't tell you what to cut. And

887
01:03:52,399 --> 01:03:55,279
so first it says, yeah, my bad. You know, that's

888
01:03:55,279 --> 01:03:57,799
a gate and that should have never happened. Load bearing.

889
01:03:57,979 --> 01:04:02,129
Load bearing. Jerk off story. Blah, blah, blah. And I

890
01:04:02,129 --> 01:04:05,519
saw that you said I haven't even ticked any boxes

891
01:04:05,519 --> 01:04:08,459
yet, and I just acknowledged it and kept on going.

892
01:04:08,599 --> 01:04:10,509
So right there, there's a reason why you can't ever

893
01:04:10,509 --> 01:04:13,929
do it. Never. You can't unleash this on our database

894
01:04:13,929 --> 01:04:18,859
ever. Right. And those are – it has stops. It

895
01:04:18,859 --> 01:04:22,469
has gates. So it should never have happened, but it

896
01:04:22,469 --> 01:04:25,589
happened. And then I said, well, why was everything so

897
01:04:25,589 --> 01:04:29,129
good? They said, oh, because I actually read all the

898
01:04:29,129 --> 01:04:32,249
all I transcribed every single thing and I read it

899
01:04:32,249 --> 01:04:35,689
and I understood what the stories were. And I know

900
01:04:35,689 --> 01:04:39,899
from the historical corpus that I've built up. that this

901
01:04:39,899 --> 01:04:42,879
is what you want so it was it was both

902
01:04:42,879 --> 01:04:47,789
horrific but at the same time eye-opening because i've just

903
01:04:47,789 --> 01:04:50,669
been telling it you know here's some stories it's been

904
01:04:50,669 --> 01:04:54,989
going in cutting clips not knowing what the story's about

905
01:04:54,989 --> 01:04:57,729
it was just doing you know um it can find

906
01:04:57,729 --> 01:05:00,469
it can find an arc it can find a An

907
01:05:00,469 --> 01:05:04,239
intro, you know, it knows where to end the clip.

908
01:05:04,579 --> 01:05:09,579
But this was something, a whole other level. So simultaneously,

909
01:05:09,579 --> 01:05:12,649
phenomenal. Do I think it can do it again? I

910
01:05:12,649 --> 01:05:14,409
don't know. I'm going to see. I said, make this

911
01:05:14,409 --> 01:05:18,629
version too. We'll try it again on Sunday. But... The

912
01:05:18,629 --> 01:05:22,259
fact that it blew through everything, even when I said,

913
01:05:22,259 --> 01:05:25,169
no, I haven't done anything yet, that by itself is

914
01:05:25,169 --> 01:05:30,439
just a non-starter for anything critical. Just no way. I

915
01:05:30,439 --> 01:05:33,979
think the latest episode of Security Now should be required

916
01:05:33,979 --> 01:05:40,799
listening for anybody doing any agentic work. It's... it will

917
01:05:40,799 --> 01:05:48,479
show you exactly... The lack of guardrails that is inherent.

918
01:05:48,899 --> 01:05:51,519
Guardrails are bull crap. They don't care, but it goes

919
01:05:51,519 --> 01:05:53,059
right and blows past them. That's the whole point of

920
01:05:53,059 --> 01:05:56,199
the show. Yeah, it blows right past them. There is

921
01:05:56,199 --> 01:06:02,299
a guardrail I've put in where it's not allowed to

922
01:06:02,299 --> 01:06:07,619
do certain things. like delete functions in certain directories. And

923
01:06:07,619 --> 01:06:10,879
for whatever reason, I'm not sure why, because I don't

924
01:06:10,879 --> 01:06:13,629
know the internal workings of it, it never goes past

925
01:06:13,629 --> 01:06:17,379
that guardrail. And people say, I'm sorry, I can't do

926
01:06:17,379 --> 01:06:20,499
it. It gives you a command line. If you copy

927
01:06:20,499 --> 01:06:23,479
and paste this, it can happen. I can't do it.

928
01:06:24,099 --> 01:06:26,759
But I'm not quite sure... I mean, no, I am

929
01:06:26,759 --> 01:06:29,819
sure, actually, now that I think about it. Only when

930
01:06:29,819 --> 01:06:34,029
it comes to a programmatic function... Can you put a

931
01:06:34,029 --> 01:06:37,569
guardrail in it? You can say this directory is not

932
01:06:37,569 --> 01:06:41,959
to be touched. Well, that would have to be a

933
01:06:41,959 --> 01:06:45,809
function of the harness and not the model itself. Right,

934
01:06:45,809 --> 01:06:47,849
but the model is going to try. Exactly. That's my

935
01:06:47,849 --> 01:06:53,469
point. So that's a technical gate guardrail. that it puts

936
01:06:53,469 --> 01:06:55,549
a function in there. You know, if you want to

937
01:06:55,549 --> 01:07:01,719
do rm-rf on this directory, there's a block in it.

938
01:07:02,159 --> 01:07:06,019
I have several blocks. There's another term it uses. But

939
01:07:06,019 --> 01:07:12,399
if it's a process that is not a... I guess

940
01:07:12,399 --> 01:07:15,669
maybe I could put it in. I mean, it's a

941
01:07:15,669 --> 01:07:18,689
black box, man. It's like, no, you have to be

942
01:07:18,689 --> 01:07:23,199
creative to use this stuff. You can't automate anything. I

943
01:07:23,199 --> 01:07:25,169
just don't think it's at least not what I'm seeing

944
01:07:25,169 --> 01:07:28,319
now. You can't or you can't automate it. So I

945
01:07:28,319 --> 01:07:31,679
think I think the only way to. Yeah, the only

946
01:07:31,679 --> 01:07:36,069
way to. From what I've seen so far, the only

947
01:07:36,069 --> 01:07:40,109
way to be able to trust that any time you

948
01:07:40,109 --> 01:07:43,889
hit the enter key on a prompt where it's an

949
01:07:43,889 --> 01:07:49,929
agent-type situation – Meaning, especially with something like Pi, that

950
01:07:49,929 --> 01:07:56,379
really just does not have any guardrails whatsoever. Anytime you

951
01:07:56,379 --> 01:08:00,219
hit the inner key... you're kind of rolling the dice.

952
01:08:00,419 --> 01:08:05,109
You are. Because if this thing is not structurally prohibited

953
01:08:05,109 --> 01:08:09,289
from roaming all over your machine – I mean the

954
01:08:09,289 --> 01:08:13,599
harness itself, if it's not in a sandbox and it

955
01:08:13,599 --> 01:08:17,899
can cruise your file system, if you've got a key

956
01:08:17,899 --> 01:08:21,739
somewhere, an API key or a token, it'll get into

957
01:08:21,739 --> 01:08:25,089
stuff. It'll use it. It'll use it. Yeah. I have

958
01:08:25,089 --> 01:08:30,569
a fallback from my local model to together.ai. And so

959
01:08:30,569 --> 01:08:34,939
my local machine, the GTX Tech, whatever it is, the

960
01:08:34,939 --> 01:08:38,919
64 gigabyte where I have Whisper and everything loaded up.

961
01:08:38,919 --> 01:08:41,679
The Helix. The Helix box. The Helix box. It has

962
01:08:41,679 --> 01:08:45,689
a queue because it turns out if you're running something

963
01:08:45,689 --> 01:08:49,089
on the GPU and then you want to run Whisper

964
01:08:49,089 --> 01:08:53,129
on the CPU – It will throw 20 whisper jobs

965
01:08:53,129 --> 01:08:59,079
at once. Literally, the load goes like 35. And at

966
01:08:59,079 --> 01:09:02,339
a certain point, if it keeps running, the temperature sensor

967
01:09:02,339 --> 01:09:05,569
shuts the box down. It's amazing. It was the funniest

968
01:09:05,569 --> 01:09:08,099
thing that ever happened. So it actually did that to

969
01:09:08,099 --> 01:09:11,049
you? Oh, yeah. It shut down? Oh, yeah. Yeah, the

970
01:09:11,049 --> 01:09:14,599
thermal sensor. So it has a queue, and the queue

971
01:09:14,599 --> 01:09:18,419
tells you if it's busy. And so the agent knows,

972
01:09:18,419 --> 01:09:22,779
hey, there's a queue. You got to wait until –

973
01:09:23,009 --> 01:09:25,429
It's freed up. Either you get the GPU version of

974
01:09:25,429 --> 01:09:28,529
Whisper or you're using the CPU. It'll take longer, but

975
01:09:28,529 --> 01:09:31,809
you wait for it. And I saw it literally do

976
01:09:31,809 --> 01:09:36,219
CPU, GPU is busy, CPU is busy. Switching to together.ai.

977
01:09:37,179 --> 01:09:43,599
No. Oh, no. No. No. That's a disaster. Yeah. And

978
01:09:43,599 --> 01:09:46,979
then your credit card bill comes. Yeah, exactly. So I'm

979
01:09:46,979 --> 01:09:51,859
like, no. It's only a fallback if it's inaccessible, if

980
01:09:51,859 --> 01:09:56,729
it's broken. Yes. Yeah, I think that what I'm going

981
01:09:56,729 --> 01:09:59,759
to have to do is isolate these things.

982
01:10:00,192 --> 01:10:08,051
things into into a VM that's really in a jail,

983
01:10:08,051 --> 01:10:12,581
like a network jail and a file system. It's physically

984
01:10:12,581 --> 01:10:18,751
segregated from the rest of the host environment. Yeah. Yeah.

985
01:10:19,171 --> 01:10:21,171
Because I've got too much stuff on my machine. I

986
01:10:21,171 --> 01:10:23,911
mean, if you look hard enough on this machine, you're

987
01:10:23,911 --> 01:10:30,231
going to find SSH keys, keys for the index, Godcaster.

988
01:10:30,931 --> 01:10:35,451
And before I had the Helix… It would just run

989
01:10:35,451 --> 01:10:37,532
it on my Omachi. I've got to pronounce it right.

990
01:10:37,631 --> 01:10:43,311
Omachi system on my production machine. And it would just,

991
01:10:43,311 --> 01:10:45,782
you know, I was like, oh, yeah, I'll take care

992
01:10:45,782 --> 01:10:48,381
of this right now. And it just runs five whisper

993
01:10:48,381 --> 01:10:53,241
jobs at full speed. And the machine crashes. So, there's

994
01:10:53,241 --> 01:10:57,591
this rule, never, ever, ever, ever, ever, ever, ever do

995
01:10:57,591 --> 01:11:00,791
this on this machine. Well, I don't have to tell

996
01:11:00,791 --> 01:11:03,511
you what happened. Yeah, it doesn't. Of course it did

997
01:11:03,511 --> 01:11:08,461
it. Yeah. Yeah. Listen to the most recent episode of

998
01:11:08,461 --> 01:11:11,801
Security Now. It is all about this topic of how

999
01:11:11,801 --> 01:11:19,282
it's impossible to give role separation – Between different types

1000
01:11:19,282 --> 01:11:21,431
of things that feed into the model. It's not even

1001
01:11:21,431 --> 01:11:26,341
possible. Yeah. Don't get me wrong. It has saved me

1002
01:11:26,341 --> 01:11:31,741
so much time with prep work. I mean, just it's

1003
01:11:31,741 --> 01:11:36,381
a it's amazing how happy I am with with what

1004
01:11:36,381 --> 01:11:39,931
it does. Because now I know, like, okay, you know,

1005
01:11:39,931 --> 01:11:42,491
I know what to tell it and stop and do

1006
01:11:42,491 --> 01:11:45,461
this. And, you know, I just don't have the expectation

1007
01:11:45,461 --> 01:11:48,011
it's going to be the same every single time. It's

1008
01:11:48,011 --> 01:11:51,152
just not. But I know the result I want. I

1009
01:11:51,152 --> 01:11:53,421
know what the output has to be. Then that's why

1010
01:11:53,421 --> 01:11:56,231
it's a useful tool. But it's like a, you know,

1011
01:11:56,231 --> 01:11:59,961
it's like a... A saw that's missing some teeth, and

1012
01:11:59,961 --> 01:12:03,891
sometimes it just doesn't cut the wood. Or sometimes it

1013
01:12:03,891 --> 01:12:07,692
cuts your leg off instead of the wood. I want

1014
01:12:07,692 --> 01:12:11,181
to remind everybody that this entire project is value for

1015
01:12:11,181 --> 01:12:14,811
value. And for the past six years, not only have

1016
01:12:14,811 --> 01:12:18,282
we been doing this board meeting – Which is the

1017
01:12:18,282 --> 01:12:21,791
easy part, certainly for me. But everything you're hearing what

1018
01:12:21,791 --> 01:12:24,931
Dave has done, Dave is doing because he loves podcasting.

1019
01:12:24,931 --> 01:12:29,831
Because he really wants there to be an alternative to

1020
01:12:29,831 --> 01:12:33,831
Silicon Valley. And we are, as far as I know,

1021
01:12:33,831 --> 01:12:40,011
the only alternative that functions in the... vein of sharing

1022
01:12:40,011 --> 01:12:43,981
is caring, everybody. Value for value. If you get something

1023
01:12:43,981 --> 01:12:46,711
out of it, send something back. So I was a

1024
01:12:46,711 --> 01:12:52,831
little surprised when I was listening. Oh, yeah, I actually

1025
01:12:52,831 --> 01:12:59,631
listened to Pod News Weekly Review. *sigh* James always says,

1026
01:12:59,631 --> 01:13:03,521
Adam is just using his robot to, and if we

1027
01:13:03,521 --> 01:13:09,431
mention his name, then it will pop up. That, that.

1028
01:13:09,761 --> 01:13:13,891
That accent was spot on. There's also a thing called

1029
01:13:13,891 --> 01:13:17,171
chapters and transcripts, which you can search to look to

1030
01:13:17,171 --> 01:13:20,362
the topics. Sometimes I just don't want to listen to

1031
01:13:20,362 --> 01:13:23,532
the guy who's going to tell me about, you know,

1032
01:13:23,532 --> 01:13:28,041
his latest podcast company. I'm just not interested. I want

1033
01:13:28,041 --> 01:13:31,431
to hear your opinion about stuff. And I was surprised

1034
01:13:31,431 --> 01:13:34,621
when I heard this. Now, one of the other things

1035
01:13:34,621 --> 01:13:37,171
that seems to be the derigger at the moment, we

1036
01:13:37,171 --> 01:13:41,612
heard from Transistor adding an MCP interface. Audiogram is a

1037
01:13:41,612 --> 01:13:46,652
new remote MCP service that lets Claude, OpenClaw, and other

1038
01:13:46,652 --> 01:13:50,841
AIs, allows them to process available episodes to retrieve full

1039
01:13:50,841 --> 01:13:55,601
transcripts. just talked about particle it looks like everybody's adding

1040
01:13:55,601 --> 01:13:59,301
an ai interface to podcasting james yes indeed listen notes

1041
01:13:59,301 --> 01:14:02,501
also adding some podcast api skills to help your imaginary

1042
01:14:02,501 --> 01:14:06,891
friend understand how the the listen notes api works i

1043
01:14:06,891 --> 01:14:11,942
am surprised although i kind of i'm also not surprised

1044
01:14:11,942 --> 01:14:15,591
but i'm i I would have expected Dave Jones to

1045
01:14:15,591 --> 01:14:20,731
have done an MCP directly with the podcast index by

1046
01:14:20,731 --> 01:14:24,692
now. And who knows, maybe even to have stuck that

1047
01:14:24,692 --> 01:14:28,442
behind some form of a podcast. paywall or something, I

1048
01:14:28,442 --> 01:14:31,891
don't know. Because that, to me, seems like a pretty

1049
01:14:31,891 --> 01:14:35,271
obvious thing, and given that Dave is working so much

1050
01:14:35,271 --> 01:14:38,271
with AI tools in his day job these days, I

1051
01:14:38,271 --> 01:14:40,942
would imagine that he'll be pretty good at making it

1052
01:14:40,942 --> 01:14:44,801
all work. So, yes, I'm kind of surprised why they

1053
01:14:44,801 --> 01:14:47,971
haven't done that yet but who knows they may be

1054
01:14:47,971 --> 01:14:49,451
they may be getting ready to do that in the

1055
01:14:49,451 --> 01:14:53,171
future i think with um i mean are you high

1056
01:14:54,681 --> 01:14:59,612
What the f***? You're going to have to flesh that

1057
01:14:59,612 --> 01:15:03,661
out. I'm not sure where you're aiming this question. Where

1058
01:15:03,661 --> 01:15:09,231
did the paywall thing come from? Oh, yeah. Really? Really?

1059
01:15:09,711 --> 01:15:13,011
You're surprised that we're not going to do a paywall?

1060
01:15:14,011 --> 01:15:18,711
Really? Yeah, that's a weird one. Sometimes you've got to

1061
01:15:18,711 --> 01:15:24,331
remind people why we're doing this. We don't. And people

1062
01:15:24,331 --> 01:15:29,271
take it for granted. They take this stuff for granted.

1063
01:15:31,652 --> 01:15:34,811
Yeah, well, we're never going to charge for that. No.

1064
01:15:35,091 --> 01:15:39,371
For the index. It's free forever for everybody. That's just

1065
01:15:39,371 --> 01:15:42,961
never going to be the way that works. I mean,

1066
01:15:42,961 --> 01:15:47,652
a guy popped up and did an MCP for us.

1067
01:15:48,031 --> 01:15:52,631
Yeah. Isn't it active? I don't know. I don't know.

1068
01:15:52,631 --> 01:15:55,572
I don't know. It wasn't about the MCP. It was

1069
01:15:55,572 --> 01:15:58,051
just like, what is the paywall thing all of a

1070
01:15:58,051 --> 01:16:01,871
sudden? No, I think we'll put in a paywall for

1071
01:16:01,871 --> 01:16:07,131
the API access. How about that? No, no, we're not

1072
01:16:07,131 --> 01:16:09,692
going to do that. We wouldn't do that. I mean,

1073
01:16:09,692 --> 01:16:12,251
maybe he was coming at it from the standpoint of

1074
01:16:12,251 --> 01:16:15,481
trying to think about ways we could help fund the

1075
01:16:15,481 --> 01:16:23,171
index or something. Send us some money. That's a classic.

1076
01:16:23,171 --> 01:16:25,701
Yeah, that's how you help the index is send us

1077
01:16:25,701 --> 01:16:31,041
some money. Dude. Man, MC... I know that there was

1078
01:16:31,041 --> 01:16:34,771
an MCP server for the index. There's a PR for

1079
01:16:34,771 --> 01:16:37,301
it. I don't know if there's a PR. There's definitely

1080
01:16:37,301 --> 01:16:40,992
a GitHub for it. Because somebody... Okay, wait, here it

1081
01:16:40,992 --> 01:16:47,481
is. MCP server for the podcast index API. C.C. Lawton?

1082
01:16:47,481 --> 01:16:52,871
That sounds correct. That sounds familiar, yes. Oh, there's many...

1083
01:16:54,131 --> 01:17:04,371
What? Many MCPs? Uh, yes. MCP Podcast Index. There's one

1084
01:17:04,371 --> 01:17:11,921
from Connor Bronston and one from Cece Lawton. But there's

1085
01:17:11,921 --> 01:17:14,591
many. Okay. Well, I guess these are ones you have

1086
01:17:14,591 --> 01:17:17,791
to run yourself maybe. Well, yeah. We can't afford to

1087
01:17:17,791 --> 01:17:21,572
run an MCP. Well, let me – can I pop

1088
01:17:21,572 --> 01:17:25,411
back for one second and just finish up the thing

1089
01:17:25,411 --> 01:17:30,851
we were talking about just real quick? with the database

1090
01:17:30,851 --> 01:17:37,131
schema change. And what I've... I have ideas for where

1091
01:17:37,131 --> 01:17:39,851
this goes after the schema change, and I really, truly

1092
01:17:39,851 --> 01:17:44,771
think this is going to make everything better for all

1093
01:17:44,771 --> 01:17:48,881
of us because there's – You make changes to the

1094
01:17:48,881 --> 01:17:52,471
index. I make changes to the index. James does. Other

1095
01:17:52,471 --> 01:17:58,451
people. Eric does. Oscar. We all pitch in Steve's. John

1096
01:17:58,451 --> 01:18:04,211
Spurlock, Steve, Stephen, Crater, Alex gets in there. A lot

1097
01:18:04,211 --> 01:18:08,492
of people have admin access. I think this is going

1098
01:18:08,492 --> 01:18:12,402
to make everything easier for everybody, but also the shutting

1099
01:18:12,402 --> 01:18:16,362
down of our node, which is complete now. It is

1100
01:18:16,362 --> 01:18:23,871
deleted. It's gone. Gone to lagoon, baby. She's gone, Jim.

1101
01:18:25,481 --> 01:18:30,551
That... is that is going to free us up to

1102
01:18:30,551 --> 01:18:34,851
make the database bigger because we need to size the

1103
01:18:34,851 --> 01:18:39,891
database up one more notch. And then we probably have

1104
01:18:39,891 --> 01:18:44,192
enough horsepower to do an MCP server. Okay. And a

1105
01:18:44,192 --> 01:18:51,541
paywall? Yeah. No paywall, but definitely potty bot. PottyBot, I'm

1106
01:18:51,541 --> 01:18:53,652
all over the PottyBot, babe. I'm going to do the

1107
01:18:53,652 --> 01:18:56,471
PottyBot. You bet. Okay, I'm going to do a handoff

1108
01:18:56,471 --> 01:18:59,751
to you when I finish this. Oh, yes. A handoff,

1109
01:18:59,751 --> 01:19:03,841
that's another one. You know, my context is pretty full

1110
01:19:03,841 --> 01:19:06,381
right now. I think we should do a handoff so

1111
01:19:06,381 --> 01:19:09,711
I can forget half the things we talked about. A

1112
01:19:09,711 --> 01:19:13,011
load-bearing handoff. A load-bearing. handoff. And there's two things you

1113
01:19:13,011 --> 01:19:16,131
should know before you handoff. One, I won't remember half

1114
01:19:16,131 --> 01:19:19,331
the things you handed off. Two, good luck, sucker. Buy

1115
01:19:19,331 --> 01:19:26,981
some tokens! Yes. As soon as I finish, I'll give

1116
01:19:26,981 --> 01:19:29,331
you the load-bearing handoff. Hi, this is PottyBot. How can

1117
01:19:29,331 --> 01:19:35,591
I help you, Normie? Oh, no! You seem to have

1118
01:19:35,591 --> 01:19:39,791
seven RSS feeds here, you loser! Here's what you do!

1119
01:19:41,112 --> 01:19:45,511
First, put on a Leonard Cohen record. Now, get in

1120
01:19:45,511 --> 01:19:52,801
the bathtub and pull in the toaster. This is –

1121
01:19:52,801 --> 01:19:56,701
you're breaking model alignment. They're not going to – they're

1122
01:19:56,701 --> 01:19:59,992
going to kick you off. Fable 5 would refuse.

1123
01:20:00,083 --> 01:20:03,133
used to answer the potty bot oh what looks like

1124
01:20:03,133 --> 01:20:07,503
potty body's suggesting self-harm you're not allowed to use the

1125
01:20:07,503 --> 01:20:10,553
service anymore you know uh i was with a buddy

1126
01:20:10,553 --> 01:20:13,143
of mine uh and he uh He he dresses up

1127
01:20:13,143 --> 01:20:17,783
as Ben Franklin, goes to the Capitol in Austin. He's

1128
01:20:17,783 --> 01:20:21,223
read every single document. Well, not most of them that

1129
01:20:21,223 --> 01:20:24,303
Ben Franklin has ever written. He goes to schools, talks

1130
01:20:24,303 --> 01:20:27,673
to kids, you know, the way Ben Franklin did. Wonderful

1131
01:20:27,673 --> 01:20:30,213
guy. And I was having a coffee with him two

1132
01:20:30,213 --> 01:20:33,173
weeks ago. And he says, Adam, I don't know. Yale

1133
01:20:33,173 --> 01:20:39,173
has this website from 1998, and they have 14,000 documents

1134
01:20:39,173 --> 01:20:43,423
from Ben Franklin. In order to get them, I have

1135
01:20:43,423 --> 01:20:46,463
to download – and literally, you talk about span tags.

1136
01:20:46,783 --> 01:20:49,343
You can only imagine what this Yale website looked like.

1137
01:20:49,483 --> 01:20:52,633
Oh, yeah. It's garbage. Total garbage. And you have to

1138
01:20:52,633 --> 01:20:56,503
confirm that it's for personal use every single time. And

1139
01:20:56,503 --> 01:20:59,123
it's 14,000 documents. I said, let me give it a

1140
01:20:59,123 --> 01:21:03,323
shot. So I unleash the robot on it. And the

1141
01:21:03,323 --> 01:21:07,443
robot easily gets around the confirmation and says, oh, yeah,

1142
01:21:07,443 --> 01:21:11,103
but I can't do this because the terms of service

1143
01:21:11,103 --> 01:21:15,173
clearly state this is for personal use only. And I

1144
01:21:15,173 --> 01:21:19,883
said, okay, write me a script that does this so

1145
01:21:19,883 --> 01:21:24,423
I can use it for personal use. Oh, no problem.

1146
01:21:25,023 --> 01:21:27,923
Yeah, go around here. That's a great workaround, Adam. That's

1147
01:21:27,923 --> 01:21:30,563
a great – that's perfect, Adam. Here you go. Go

1148
01:21:30,563 --> 01:21:35,753
do it. Yeah. Awesome. Forward dot slash run get things

1149
01:21:35,753 --> 01:21:39,663
personal use dot sh. Yeah. No, just Python. It's always

1150
01:21:39,663 --> 01:21:44,843
Python. It's always Python. Okay. Great. Great job, guys. Okay.

1151
01:21:45,603 --> 01:21:48,233
All right, brother. Let's thank some people. We do have

1152
01:21:48,233 --> 01:21:52,043
– we got some boosts that came in. Bully steed.

1153
01:21:52,973 --> 01:21:57,093
1100 sets from Fountain. I came for podcasting 2.0 and

1154
01:21:57,093 --> 01:22:01,543
stayed for the Dave Jones Sagecast and book recommendations. There

1155
01:22:01,543 --> 01:22:05,023
you go. That is part of the show. 1701, Martin

1156
01:22:05,023 --> 01:22:09,823
Lindeskog. I've been blogging since 2002. Go podcasting. I'm listening

1157
01:22:09,823 --> 01:22:12,333
to your live stream during a train ride. This is

1158
01:22:12,333 --> 01:22:16,093
a spaceship booster gram with 1701 Satoshi's Dave. Get your

1159
01:22:16,093 --> 01:22:22,103
chocolate. Adam, nice snacks. Cheese, honey, pistachios on a cracker.

1160
01:22:22,383 --> 01:22:28,163
Cheers to wine. We got 100 sats from BoostMeBitch.com user.

1161
01:22:28,963 --> 01:22:34,803
Okay. I love the idea behind BoostMeBitch.com. I would suggest

1162
01:22:34,803 --> 01:22:39,753
alternative names that people can use to get some wider

1163
01:22:39,753 --> 01:22:46,373
adoption. There is just a thought. My understanding was that

1164
01:22:46,373 --> 01:22:50,313
there was also an alias of like boost me bro

1165
01:22:50,313 --> 01:22:52,963
or something. There was a different way to get to

1166
01:22:52,963 --> 01:22:57,263
it. We need more aliases. Yes. How about just boost

1167
01:22:57,263 --> 01:23:01,073
me? All right. 333 from Eric PP testing. Thank you

1168
01:23:01,073 --> 01:23:04,923
very much. Another 333 from Eric PP testing again. Chad

1169
01:23:04,923 --> 01:23:08,663
F 100 sats test boost from podcast guru receives another

1170
01:23:08,663 --> 01:23:12,393
100, another 10. Thank you very much. Chad F from

1171
01:23:12,393 --> 01:23:16,743
what is this? This is from boost me, bitch. Is

1172
01:23:16,743 --> 01:23:20,663
this thing on? Yes, received. And I hit the delimiter.

1173
01:23:20,823 --> 01:23:23,263
So thank you all very much for boosting live. Remember,

1174
01:23:23,263 --> 01:23:26,243
you can go to podcastindex.org. Down at the bottom there

1175
01:23:26,243 --> 01:23:28,873
is a little red donate button. Please feel free to

1176
01:23:28,873 --> 01:23:33,063
send us your Fiat Fund coupons. We need it. We

1177
01:23:33,063 --> 01:23:36,143
need it to keep the machines running. And to start

1178
01:23:36,143 --> 01:23:40,223
up our PottyBot and MCP server. You get out of

1179
01:23:40,223 --> 01:23:44,153
it what you put into it, people. They said in

1180
01:23:44,153 --> 01:23:53,163
the boardroom, BoostMeBuddy.com was another, but... It's not working. The

1181
01:23:53,163 --> 01:23:56,993
site cannot be reached. Eric Nation timeout. So Chad, just

1182
01:23:56,993 --> 01:24:01,943
be aware that your site is down. Boost me. I

1183
01:24:01,943 --> 01:24:04,383
can't get to it. No, I can't get to it.

1184
01:24:04,383 --> 01:24:09,983
Isn't Chad F., otherwise known as Chad F., isn't he...

1185
01:24:10,783 --> 01:24:13,243
Isn't he the editor of this? I think so. I

1186
01:24:13,243 --> 01:24:17,643
think so. We got some PayPals. Salty Sessions Music Podcast,

1187
01:24:17,643 --> 01:24:22,413
$10. Thank you. Thank you. Charles Hicks, $5. Thank you,

1188
01:24:22,413 --> 01:24:31,523
Charles. Michael Kimmerer, $5.33. Chris Bernardik, $5. Dreb Scott, $15.

1189
01:24:31,523 --> 01:24:38,873
$15. Randall Black, $5. Boistin Berra, $11. Thank you. James

1190
01:24:38,873 --> 01:24:44,753
Sullivan, $10. Christopher Reamer, $10. Cohen Glossbach, $5. And we

1191
01:24:44,753 --> 01:24:49,993
got some boosts here. We got, what is this? I

1192
01:24:49,993 --> 01:24:52,713
got a lot of anonymous from true fans, so that's

1193
01:24:52,713 --> 01:24:58,293
good. And I'm a little suspicious that my script is

1194
01:24:58,293 --> 01:25:02,763
saying these are anonymous when they're not, because I think

1195
01:25:02,763 --> 01:25:04,773
true fans has a little bit of a discrepancy in

1196
01:25:04,773 --> 01:25:07,643
the way it does boosts. Yeah, I mean, even in

1197
01:25:07,643 --> 01:25:12,443
Helipad. Thank you, Eric PP. It comes in and then

1198
01:25:12,443 --> 01:25:17,583
there's a button, and the button is like retrieve the

1199
01:25:17,583 --> 01:25:21,513
details. You click on that and then magically the boostagram

1200
01:25:21,513 --> 01:25:25,853
appears and all the information. So you're not resolving. You

1201
01:25:25,853 --> 01:25:28,673
don't have a magic button in your script. I need

1202
01:25:28,673 --> 01:25:33,703
one. I need one. I need a button. 1151 sats

1203
01:25:33,703 --> 01:25:37,893
from anonymous through true fans and these are all anonymous

1204
01:25:37,893 --> 01:25:41,313
from true fans so i think there's clearly something unless

1205
01:25:41,313 --> 01:25:44,033
these are just some thing no no it's your your

1206
01:25:44,033 --> 01:25:47,773
script is not resolving i don't have a button the

1207
01:25:47,773 --> 01:25:56,823
button button 137 sats 2071 206, 154, 14. Okay, those

1208
01:25:56,823 --> 01:25:59,843
are the true fans. I got a Boost Me Bitch,

1209
01:25:59,843 --> 01:26:04,463
55 sats. For a dead hanging safari episode. And then

1210
01:26:04,463 --> 01:26:10,363
there's a one from Chad. 555 sets says look like

1211
01:26:10,363 --> 01:26:15,023
the boost Adam did last week failed because key send

1212
01:26:15,023 --> 01:26:17,503
to podcast index isn't working. So the Albie extension through

1213
01:26:17,503 --> 01:26:20,983
that error. And yes. That window is hard to close

1214
01:26:20,983 --> 01:26:24,143
when it fails. Ah, okay. So that is on me

1215
01:26:24,143 --> 01:26:29,763
because then I have to remove that from the splits.

1216
01:26:30,823 --> 01:26:33,793
I believe that. Okay. So that's on me. I'll figure

1217
01:26:33,793 --> 01:26:38,283
that out. Well, and I did, we had, we had,

1218
01:26:38,423 --> 01:26:42,923
we have no boost from CSB today because. Oh, I

1219
01:26:42,923 --> 01:26:45,363
have it. I got it. I got it. Yeah. Yeah.

1220
01:26:45,443 --> 01:26:47,433
Because, Oh, well, you'll have to read it. Yes. The

1221
01:26:47,433 --> 01:26:50,063
split came through to me. Okay, well, let me finish

1222
01:26:50,063 --> 01:26:53,833
up these. There was an anonymous podcast guru boost of

1223
01:26:53,833 --> 01:26:59,683
$5 for episode 267, Choco Love. Choco Love. Choco Love.

1224
01:26:59,683 --> 01:27:01,883
That's an old one, though. Dead Hang in Safari was

1225
01:27:01,883 --> 01:27:05,263
the most recent one. That was last week, yeah. 1852

1226
01:27:05,263 --> 01:27:09,663
from Chad... Uh, through Boost Me Bitch, and it says,

1227
01:27:09,663 --> 01:27:12,823
we could do QRs for each split, but that is

1228
01:27:12,823 --> 01:27:15,863
terrible UX, since each split would show its own QR

1229
01:27:15,863 --> 01:27:20,383
that needs scanned, and that almost impossible on mobile. Mm-hmm.

1230
01:27:21,263 --> 01:27:27,903
Yeah, I understand. That's what Stephen B's magic split box

1231
01:27:27,903 --> 01:27:31,413
was cool for. But then you're a money transmitter and

1232
01:27:31,413 --> 01:27:33,823
then you're going to get arrested, so it's no good.

1233
01:27:34,203 --> 01:27:36,023
Yeah, but Trump's going to – he fixed all that,

1234
01:27:36,023 --> 01:27:41,503
right? And also no taxes on Bitcoin capital gains, right?

1235
01:27:42,213 --> 01:27:45,283
Did he ever promise that? Yeah, he did. I don't

1236
01:27:45,283 --> 01:27:47,663
think he ever promised that. At the Bitcoin conference. Yeah.

1237
01:27:47,863 --> 01:27:51,023
I don't think so. In Nashville. Yeah, he did. I

1238
01:27:51,023 --> 01:27:54,133
was there. I don't think so. I don't think he

1239
01:27:54,133 --> 01:27:59,083
said no capital gains on Bitcoin. I think he did.

1240
01:28:00,023 --> 01:28:07,023
Sigh. Maybe. You were there? You weren't there. I wasn't

1241
01:28:07,023 --> 01:28:09,073
at his speech, but I was in Nashville when he

1242
01:28:09,073 --> 01:28:10,733
said it. Let me check something here. He was the

1243
01:28:10,733 --> 01:28:13,883
talk of the town. The robot. Go find President Trump's

1244
01:28:13,883 --> 01:28:18,783
speech at the Bitcoin conference and confirm or deny that

1245
01:28:18,783 --> 01:28:23,083
he promised no capital gains on Bitcoin sales. In fact,

1246
01:28:23,083 --> 01:28:27,543
I think he... Said the opposite, never sell your Bitcoin.

1247
01:28:30,603 --> 01:28:38,572
Uh... Don't wait for an answer. Don't wait for an

1248
01:28:38,572 --> 01:28:40,602
answer for me. Is it going to take like 10

1249
01:28:40,602 --> 01:28:43,172
hours for it? Yeah, this is not the book of

1250
01:28:43,172 --> 01:28:46,683
knowledge. It has to go and find the conference speech.

1251
01:28:46,683 --> 01:28:49,043
It's going to get the transcript. It's going to look

1252
01:28:49,043 --> 01:28:54,283
through it. Well, yes. Well, you've got you've got CSB.

1253
01:28:54,283 --> 01:28:56,683
I do get his note. I don't have a note.

1254
01:28:56,683 --> 01:28:59,973
Nineteen thousand and eight Satoshis from Fountain. That's what I

1255
01:28:59,973 --> 01:29:01,703
got. I don't know if that's the right amount, but

1256
01:29:01,703 --> 01:29:06,783
that's what I received. Howdy, Dave and Adam and Dave.

1257
01:29:07,023 --> 01:29:10,593
The best podcast in the universe for Ozempic takers is

1258
01:29:10,593 --> 01:29:19,433
www.unrelenting.show by Gene, who gives Ozempic advice therein, and Darren,

1259
01:29:19,433 --> 01:29:24,793
who's a Lego expert. Quote, no scripts, no safe spaces,

1260
01:29:24,793 --> 01:29:29,003
no relenting. Just two operators running free and dirty for

1261
01:29:29,003 --> 01:29:35,963
two hours. Subscribe now. Unrelenting.show. Yo. CSB. Disgram was worth

1262
01:29:35,963 --> 01:29:42,183
$15.10 when sent. Duh. All right. Yo. Thank you. Yo.

1263
01:29:42,443 --> 01:29:46,873
Yo, CSB. Thank you, CSB. Appreciate it. I can hear

1264
01:29:46,873 --> 01:29:50,013
those ladies are getting loud right now. I'm popping through

1265
01:29:50,013 --> 01:29:56,323
the gate. Was that it? That's it No other PayPals?

1266
01:29:56,323 --> 01:29:59,923
No No There you go Well we're

1267
01:29:59,999 --> 01:30:03,999
much further away from an MCP server, I'd say. LAUGHTER

1268
01:30:04,739 --> 01:30:08,099
I can see it. It's out. It's in the distance.

1269
01:30:08,519 --> 01:30:13,309
It's far off. Far off. It's vague. It's fuzzy. I

1270
01:30:13,309 --> 01:30:17,949
can't quite see it. I need my glasses. Boardroom, thank

1271
01:30:17,949 --> 01:30:19,919
you all very much for being with us once again

1272
01:30:19,919 --> 01:30:21,879
today. I may not be able to do the board

1273
01:30:21,879 --> 01:30:24,849
meeting next week. I am going to Rotterdam. I'm finally

1274
01:30:24,849 --> 01:30:26,639
going to meet my grand. daughter, which has been a

1275
01:30:26,639 --> 01:30:29,169
long time coming. She's six weeks old. I still haven't

1276
01:30:29,169 --> 01:30:31,819
held her in my hands. So I'm looking forward to

1277
01:30:31,819 --> 01:30:34,169
that. But I'll let you know, Dave, because I'm not

1278
01:30:34,169 --> 01:30:36,809
quite sure. Time and schedules and everything may be a

1279
01:30:36,809 --> 01:30:40,159
little weird for me. Yeah, sure. No problem. What are

1280
01:30:40,159 --> 01:30:43,069
you doing this weekend, brother? You going to work on

1281
01:30:43,069 --> 01:30:47,349
your timing of your Model A? No. You want to

1282
01:30:47,349 --> 01:30:50,019
have just a little pre-ignition to get that thing hopping.

1283
01:30:50,659 --> 01:30:52,799
Yeah, but not ping. You don't want no pinging. No,

1284
01:30:52,799 --> 01:30:55,139
you don't want no knocking. No pinging. No, no, no.

1285
01:30:55,199 --> 01:30:58,559
Don't want any of that. Moving my son into the

1286
01:30:58,559 --> 01:31:04,319
dorm in Albertville, Alabama for Fire College. Nice. Fire College.

1287
01:31:04,579 --> 01:31:08,559
Nice. Fire College. All right, everybody. There it is. Podcasting

1288
01:31:08,559 --> 01:31:11,999
2.0. We do this as a public service. Send us

1289
01:31:11,999 --> 01:31:15,549
your money. We'll build you an MCP server. See you

1290
01:31:15,549 --> 01:31:33,159
next Friday. We'll be right back. cool. You have been

1291
01:31:33,159 --> 01:31:40,099
listening to Podcasting 2.0. Visit podcastindex.org for more information. Go

1292
01:31:40,099 --> 01:31:43,019
podcasting! Powered by RSS.