1
00:00:00,500 --> 00:00:06,339
Podcasting 2.0 for October 23rd, 2026, episode 276, Jack Leg

2
00:00:06,339 --> 00:00:12,779
Leachers. Hello everybody, welcome once again to Podcasting 2.0 where

3
00:00:12,779 --> 00:00:16,620
we talk about all things podcasting. And yeah, that includes

4
00:00:16,620 --> 00:00:40,219
some... We'll be right back. friend on the other end,

5
00:00:40,219 --> 00:00:51,170
the one, the only, Mr. Dan! During that intro, you

6
00:00:51,170 --> 00:00:54,719
got so far into the can... Into the can? You

7
00:00:54,719 --> 00:00:56,979
are deep in the can. What do you mean the

8
00:00:56,979 --> 00:00:59,990
can? What can? In a can. It sounds like you're

9
00:00:59,990 --> 00:01:01,880
in a can. I'm not. I'm not in a can.

10
00:01:02,079 --> 00:01:05,549
Or a foxhole or something. You're listening on the wrong

11
00:01:05,549 --> 00:01:09,579
device somehow. You're listening. I just got my headphones on.

12
00:01:09,719 --> 00:01:13,120
No, no, there's no way. There's no way. Something is

13
00:01:13,120 --> 00:01:17,780
wrong with your setup. So in the can like echo,

14
00:01:17,780 --> 00:01:22,629
we can like, no, no, no, no, no, no, no,

15
00:01:22,629 --> 00:01:27,079
no, no, no, it's just not possible. No, I'm telling

16
00:01:27,079 --> 00:01:30,879
you, I wish I could record it. I wish you

17
00:01:30,879 --> 00:01:34,930
could, too, because I don't know how to, though. I

18
00:01:34,930 --> 00:01:38,260
guess I could put my phone up to my ear

19
00:01:38,260 --> 00:01:41,650
can. It is the wildest thing. I have no idea

20
00:01:41,650 --> 00:01:45,489
what you're witnessing. Very in a can. I'm not in

21
00:01:45,489 --> 00:01:51,599
a can, though. I'm here. And the stream sounds fine.

22
00:01:51,700 --> 00:01:55,319
So if the stream sounds fine... Okay, I just recorded

23
00:01:55,319 --> 00:01:58,269
it. Okay, all right. I just recorded it for my

24
00:01:58,269 --> 00:02:01,140
own sanity. Okay, all right. Let's play it back. I'm

25
00:02:01,140 --> 00:02:04,170
listening. I'm ready. Oh, you're going to share it? You're

26
00:02:04,170 --> 00:02:05,719
going to share it with me? I'm going to send

27
00:02:05,719 --> 00:02:08,219
it to you. Okay, all right. Send it to me.

28
00:02:08,780 --> 00:02:11,319
And then I will play it directly from here, and

29
00:02:11,319 --> 00:02:15,319
we'll see if that's how I sound. Share. Now, this

30
00:02:15,319 --> 00:02:20,219
is going to be a perfect reproduction because I held

31
00:02:20,219 --> 00:02:23,340
my cell phone up to the can of my headphone.

32
00:02:23,879 --> 00:02:26,150
So whatever you're about to hear is going to be

33
00:02:26,150 --> 00:02:31,469
absolutely perfect. Okay. High Fideliti. Oh, yeah. Yeah. Are you

34
00:02:31,469 --> 00:02:34,050
sending it through signal? Okay, here we go. No, it's

35
00:02:34,050 --> 00:02:37,550
just not possible. I'm telling you, I wish I could

36
00:02:37,550 --> 00:02:41,860
record it. I wish you could, too. I don't know

37
00:02:41,860 --> 00:02:45,919
how to, though. I guess I could put my phone

38
00:02:45,919 --> 00:02:50,400
up to my ear can. It is the wildest thing.

39
00:02:50,680 --> 00:02:56,699
Do you hear it? No, no. It's very hard to...

40
00:02:56,699 --> 00:02:59,409
hear you didn't you didn't hear from that high quality

41
00:02:59,409 --> 00:03:03,729
recording well it sounded like crap so it did it

42
00:03:03,729 --> 00:03:06,699
sounded horrible oh i'm sorry i don't know the only

43
00:03:06,699 --> 00:03:10,979
thing i can think is that something is going wrong

44
00:03:10,979 --> 00:03:15,939
with the with the return through uh my uh clean

45
00:03:15,939 --> 00:03:22,560
feed clone I mean, I just say we just blame

46
00:03:22,560 --> 00:03:26,610
the Rodecaster firmware. Oh, you know, oh, I did just

47
00:03:26,610 --> 00:03:35,639
update the Rodecaster firmware. That is a possibility. It would

48
00:03:35,639 --> 00:03:38,280
be bad if that's what it was. Let me just

49
00:03:38,280 --> 00:03:41,169
check. Well, but the boardroom says that they don't hear

50
00:03:41,169 --> 00:03:46,849
anything wrong. But maybe it's only my channel. Let me

51
00:03:46,849 --> 00:03:51,530
just check. Outputs. Let me just check. It's due. Yes,

52
00:03:51,530 --> 00:03:54,680
it is due. We haven't had a good road caster

53
00:03:54,680 --> 00:03:59,729
firmware diarrhea in a while. Well, that is entirely possible,

54
00:03:59,729 --> 00:04:04,180
and that makes me sad if that's what happened. uh

55
00:04:04,180 --> 00:04:11,909
running php yeah definitely absolutely it is 100 it is

56
00:04:11,909 --> 00:04:15,930
well let's talk about that for a second because holy

57
00:04:15,930 --> 00:04:20,339
guacamole what a what a week you've had brother what

58
00:04:20,339 --> 00:04:24,759
a week and and What a week all CIS administrators

59
00:04:24,759 --> 00:04:27,329
have had around the world, and they do not get

60
00:04:27,329 --> 00:04:31,500
enough respect. They do not. They need prayer. They need...

61
00:04:31,740 --> 00:04:38,000
Chocolates, little presents, little back rubs, all kinds. No emails.

62
00:04:38,180 --> 00:04:41,110
Don't send an email thanking your C7. They don't want

63
00:04:41,110 --> 00:04:43,930
to hear your email. They just want just a like,

64
00:04:43,930 --> 00:04:46,509
hey, thank you for what you do. Thank you for

65
00:04:46,509 --> 00:04:49,430
your service. Thank you for your courage. And I thank

66
00:04:49,430 --> 00:04:52,899
you, Dave Jones, because I. I had my own servers

67
00:04:52,899 --> 00:04:55,420
to deal with, and that was minimal stuff. And you

68
00:04:55,420 --> 00:05:00,089
maintaining the podcast index, amongst other things like, I don't

69
00:05:00,089 --> 00:05:04,290
know, a whole accounting office, Godcaster's backend, you really hustled,

70
00:05:04,290 --> 00:05:13,279
brother. Yeah, so I do – I do sysadmin. I

71
00:05:13,279 --> 00:05:15,680
mean, obviously, it's my day job, but then also I

72
00:05:15,680 --> 00:05:20,920
have Godcaster Podcast Index and then also have just –

73
00:05:21,300 --> 00:05:24,420
As all IT people do, you get sucked into supporting

74
00:05:24,420 --> 00:05:29,439
some stuff for other people, friends, family, things like that.

75
00:05:30,439 --> 00:05:34,759
Oh, that's the worst. Oh, yeah. I know. I know.

76
00:05:34,879 --> 00:05:36,720
I know. I know. I know. I have like –

77
00:05:36,720 --> 00:05:40,399
so I've ended up with like nine, roughly nine production

78
00:05:40,399 --> 00:05:44,069
PHP websites. Oh. Just kind of spread out all over

79
00:05:44,069 --> 00:05:47,759
the place that I manage. Most of the websites, most

80
00:05:47,759 --> 00:05:50,699
of the stuff, the servers that I manage, they're not

81
00:05:50,699 --> 00:05:55,779
Internet-facing. They don't face the public, but there's nine of

82
00:05:55,779 --> 00:06:01,660
them that do. Two of them were pretty – Well,

83
00:06:01,660 --> 00:06:06,870
I didn't know anything was going on until Stephen Crater

84
00:06:06,870 --> 00:06:14,519
posted on podcastindex.social. He's like – he just reposted the

85
00:06:14,519 --> 00:06:20,939
PHP like – Alert. Alert. Yeah. CVE. Uh-huh. And I

86
00:06:20,939 --> 00:06:23,290
was like, because I had gotten up early, I think

87
00:06:23,290 --> 00:06:25,750
I'd gotten up, you know, pretty early that day. And

88
00:06:25,750 --> 00:06:27,649
I was like, well, I mean, I'm going to get

89
00:06:27,649 --> 00:06:29,839
started on some stuff because I was in the middle

90
00:06:29,839 --> 00:06:32,740
of some stuff with the Index. And no, no, I

91
00:06:32,740 --> 00:06:36,040
was working on the Godcaster MCP. That's what it was.

92
00:06:36,959 --> 00:06:39,060
And so... I start working on that, and then I

93
00:06:39,060 --> 00:06:42,500
just glance over at Stephen Crater. His thing says PHP

94
00:06:42,500 --> 00:06:47,360
9.2 CVE. I'm like, oh, God. Yeah. Oh, no. Yeah.

95
00:06:48,120 --> 00:06:55,160
And then that was what that ended up. So... Let

96
00:06:55,160 --> 00:07:00,680
me make an observation before you move on. So my

97
00:07:00,680 --> 00:07:07,759
observation was that... This was either a moment where every

98
00:07:07,759 --> 00:07:12,300
systems administrator went, holy crap, this is really, really bad,

99
00:07:12,300 --> 00:07:17,769
and just ripped everything offline because government websites, I mean,

100
00:07:17,769 --> 00:07:20,829
there was all kinds of stuff was down, or it

101
00:07:20,829 --> 00:07:24,680
was – systems administrators going, oh man, I get to

102
00:07:24,680 --> 00:07:26,610
do something else this morning. Let me rip all this

103
00:07:26,610 --> 00:07:31,050
stuff off. Suffer! Suffer, you creep! Suffer! No, it was

104
00:07:31,050 --> 00:07:33,750
not that. That was not the way. It was the

105
00:07:33,750 --> 00:07:38,060
first one, not the second one. Because like... I mean,

106
00:07:38,060 --> 00:07:41,180
the NSA, the FBI, they were all just putting out

107
00:07:41,180 --> 00:07:44,149
like Twitter posts saying, yeah, take your stuff down. Just

108
00:07:44,149 --> 00:07:46,089
turn your sites off. If you've got a website that

109
00:07:46,089 --> 00:07:48,269
runs PHP, just turn it off. And was that a

110
00:07:48,269 --> 00:08:00,230
valid response from them? That's... That's an interesting question. In

111
00:08:00,230 --> 00:08:08,680
some circumstances, yes. Mm-hmm. Yeah, not across the board, but

112
00:08:08,680 --> 00:08:12,800
yes to some of that, because the issue here was

113
00:08:12,800 --> 00:08:19,259
that or the overarching issue with this PHP catastrophe was

114
00:08:19,259 --> 00:08:23,439
– Let me just let me frame it like this.

115
00:08:23,439 --> 00:08:29,939
It starts this whole the whole PHP story with this

116
00:08:29,939 --> 00:08:37,000
issue starts with some jack leg releasing the details of

117
00:08:37,000 --> 00:08:42,840
the exploit ahead of. The responsible disclosure deadline. So when

118
00:08:42,840 --> 00:08:45,629
you say Jack Leg, is that a person's name or

119
00:08:45,629 --> 00:08:49,980
is that a slur? It is a more kind version

120
00:08:49,980 --> 00:08:54,059
of Jackass. Oh, okay. Jack Leg. I'm going to –

121
00:08:54,059 --> 00:08:57,929
that's show title. There we go. Jack Leg. Yes. I

122
00:08:57,929 --> 00:09:01,600
mean there – There are many jack legs in the

123
00:09:01,600 --> 00:09:08,389
security influencer community, and this is like – because the

124
00:09:08,389 --> 00:09:12,480
way responsible disclosure is supposed to work is that you

125
00:09:12,480 --> 00:09:18,600
privately report the problem, the vulnerability, and show – with

126
00:09:18,600 --> 00:09:22,740
proof of exploit – And then you use the time

127
00:09:22,740 --> 00:09:30,100
when it's under privacy to responsibly go to all the

128
00:09:30,100 --> 00:09:38,879
vendors involved, the Linux distros, the software packages, software maintainers.

129
00:09:38,889 --> 00:09:43,220
You go through the whole, you notify everyone, give everyone

130
00:09:43,220 --> 00:09:46,279
a timeline for how long it's going to take to

131
00:09:46,279 --> 00:09:50,169
fix the bug and distribute it to all the systems

132
00:09:50,169 --> 00:09:54,100
that are going to push those fixes downstream. So in

133
00:09:54,100 --> 00:09:59,419
this case, it would be things like WordPress, WordPress. Yeah,

134
00:09:59,419 --> 00:10:02,440
I'd say that was the biggest WordPress. Yeah, who's the

135
00:10:02,440 --> 00:10:07,720
other one? Who's the big WordPress reseller? That had a

136
00:10:07,720 --> 00:10:13,370
falling out with them. I forgot. But anyway, like them,

137
00:10:13,370 --> 00:10:16,960
you know, all the Linux distro. What is your –

138
00:10:16,960 --> 00:10:20,980
isn't your Jamie telling you? Your Jamie bot? I'm not

139
00:10:20,980 --> 00:10:24,879
even looking at that. I think it's useless. But the

140
00:10:24,879 --> 00:10:28,649
– so you're supposed to do all that and then

141
00:10:28,649 --> 00:10:32,519
you – Go public once all the patches are poised

142
00:10:32,519 --> 00:10:35,440
and ready to drop, ready to go in their repository.

143
00:10:35,679 --> 00:10:38,389
But this was some jack leg going, oh, cool, I've

144
00:10:38,389 --> 00:10:42,440
got an exclusive. Breaking! One of those guys? Yes. Yes.

145
00:10:42,580 --> 00:10:45,830
And this happens all the time. I think I said

146
00:10:45,830 --> 00:10:51,299
this on the other day. Security... Influencers are like unbearable.

147
00:10:51,299 --> 00:10:55,649
These people are so annoying because they not only disclose

148
00:10:55,649 --> 00:11:00,519
early because they just want some attention. They just want

149
00:11:00,519 --> 00:11:06,990
to get clicks and reposts on Twitter. But they also

150
00:11:06,990 --> 00:11:10,940
pile on. So anytime there's a big vulnerable, a big,

151
00:11:10,940 --> 00:11:15,529
horrible vulnerability, they're also going to be like, oh, yeah,

152
00:11:15,529 --> 00:11:19,100
check out these other seven, you know, I know. I

153
00:11:19,100 --> 00:11:21,379
know. I sent you I sent you a link. You're

154
00:11:21,379 --> 00:11:24,620
like, these people are insufferable. I'm like, OK, I'll just

155
00:11:24,620 --> 00:11:26,990
step away from Dave for a little while. I'm not

156
00:11:26,990 --> 00:11:30,850
going to be posting anything. Well, and so the other

157
00:11:30,850 --> 00:11:35,980
part of that was Node had big expenses. Node.js, yeah.

158
00:11:36,159 --> 00:11:39,509
Yeah. And so our website, the Podcast Index website runs

159
00:11:39,509 --> 00:11:44,429
Node. And up until yesterday, it ran a version of

160
00:11:44,429 --> 00:11:49,879
Node that was woefully out of date. uh, node 16.

161
00:11:51,139 --> 00:11:54,700
And it's on like a 24 LTS right now. So

162
00:11:54,700 --> 00:11:56,299
it was like a way out of date and I

163
00:11:56,299 --> 00:11:58,580
knew it was out of date, but we, you know,

164
00:11:58,639 --> 00:12:01,610
we've, you're slow to update. And I agree with that

165
00:12:01,610 --> 00:12:07,659
policy. Yeah, and I tend to – okay, here's the

166
00:12:07,659 --> 00:12:10,129
thing about patching when it comes to this kind of

167
00:12:10,129 --> 00:12:20,139
stuff. My... philosophy on how to And I'm going to

168
00:12:20,139 --> 00:12:25,669
admit up front that this philosophy – It's flawed. It's

169
00:12:25,669 --> 00:12:34,080
flaw philosophy. Flaw philosophy. Yeah. Philosophy. Philosophy. Yes. Philosophy. Yes.

170
00:12:35,279 --> 00:12:40,110
This flaw philosophy is – Uh, now I think out

171
00:12:40,110 --> 00:12:44,830
of date. So, up until recently, and this is going

172
00:12:44,830 --> 00:12:47,879
to be part of – I'm going to explain what

173
00:12:47,879 --> 00:12:52,220
all that I did behind the scenes this week. But

174
00:12:52,220 --> 00:12:58,220
up until recently, patching and migrating systems from one version

175
00:12:58,220 --> 00:13:02,279
of a framework to another or one OS to another

176
00:13:02,279 --> 00:13:07,210
was – A chore. And it always involved breakage most

177
00:13:07,210 --> 00:13:10,519
of the time. Yeah. And that's why anytime you had

178
00:13:10,519 --> 00:13:13,299
to say, let's say you go from Laura, Laura, Laura,

179
00:13:13,299 --> 00:13:16,750
Laura framework 12 to Laura framework 13. That's a bad

180
00:13:16,750 --> 00:13:21,669
example. Let's say Laura framework 10 to 11. That had

181
00:13:21,669 --> 00:13:25,590
a big document that went with it showing all of

182
00:13:25,590 --> 00:13:30,100
the breaking changes. And there was actually entire services that

183
00:13:30,100 --> 00:13:33,980
I'm sure they're still around. There's entire services where you

184
00:13:33,980 --> 00:13:38,750
can hire them. And their only job, their contractors, their

185
00:13:38,750 --> 00:13:42,860
only job was to come in and do your job.

186
00:13:42,990 --> 00:13:48,240
Laravel framework upgrade. They would comb through your – of

187
00:13:48,240 --> 00:13:50,769
course, they had scripts that would look for all these

188
00:13:50,769 --> 00:13:54,620
things, and they would make this process easier. Well, and

189
00:13:54,620 --> 00:13:59,169
so for those reasons, upgrades in the past have always

190
00:13:59,169 --> 00:14:02,580
come with a lot of risk. And when you're a

191
00:14:02,580 --> 00:14:06,490
small team or a single solo person, what my philosophy

192
00:14:06,490 --> 00:14:12,159
has always been is that – you look at what

193
00:14:12,159 --> 00:14:14,539
the potential problem is, you look at the vulnerability or

194
00:14:14,539 --> 00:14:20,100
the issue, and, And then... You look at your ability

195
00:14:20,100 --> 00:14:24,620
to mitigate it. And if your ability to mitigate it

196
00:14:25,899 --> 00:14:32,460
Um, is sufficient, then do the mitigation, don't do the

197
00:14:32,460 --> 00:14:35,559
patch or don't do the migration. And the reason is

198
00:14:35,559 --> 00:14:41,049
because most vulnerabilities fall into the category of something that's

199
00:14:41,049 --> 00:14:45,370
very easy to spot. So you can – or there's

200
00:14:45,370 --> 00:14:48,559
a flaw. It's like PHP. It's been years and years

201
00:14:48,559 --> 00:14:50,559
and years since there has been a flaw of this

202
00:14:50,559 --> 00:14:54,679
magnitude or anything close to it in PHP core. Most

203
00:14:54,679 --> 00:14:58,440
PHP flaws end up being in the modules or the

204
00:14:58,440 --> 00:14:59,899
extensions that go along with it.

205
00:15:00,600 --> 00:15:05,460
or in particular libraries, or in non-default configurations. And so

206
00:15:05,460 --> 00:15:10,279
those are easy to mitigate. You just upgrade the library,

207
00:15:10,279 --> 00:15:14,399
or you make sure that you're not using that Non-standard

208
00:15:14,399 --> 00:15:17,370
configuration. It's sort of like NGINX. You know, they had

209
00:15:17,370 --> 00:15:21,070
this big, huge NGINX vulnerability this past year. But most

210
00:15:21,070 --> 00:15:24,700
of that fell down to – because you had –

211
00:15:24,700 --> 00:15:29,190
this is actually a perfect example. So the NGINX vulnerability

212
00:15:29,190 --> 00:15:33,259
came down to using – positional parameters in a regular

213
00:15:33,259 --> 00:15:36,480
expression as a redirect. I always stay away from that.

214
00:15:37,259 --> 00:15:39,779
You should never do it. No, it's the stupidest thing

215
00:15:39,779 --> 00:15:43,460
ever. Positional parameters in a non-conditional redirect. Are you kidding

216
00:15:43,460 --> 00:15:48,779
me now? Show title. No, Jack Leg is still leading.

217
00:15:51,279 --> 00:15:55,220
So... That was the vulnerability. Well, that vulnerability got fixed

218
00:15:55,220 --> 00:15:58,039
and then update to NGINX. Okay, so now you –

219
00:15:58,039 --> 00:16:01,710
so you have two options to fix this issue. You

220
00:16:01,710 --> 00:16:05,370
can either change away from and use named parameters and

221
00:16:05,370 --> 00:16:10,840
not positional, which is like it takes 30 seconds to

222
00:16:10,840 --> 00:16:14,919
make this change. Or you can schedule a downtime window

223
00:16:14,919 --> 00:16:17,919
to upgrade your version of Nginx. Why would you do

224
00:16:17,919 --> 00:16:21,279
the downtime? Right. You just get in there and just

225
00:16:21,279 --> 00:16:24,809
fix the statement. And so this is the sort of

226
00:16:24,809 --> 00:16:30,879
thing that most problems fall into that situation. category and

227
00:16:30,879 --> 00:16:34,139
you can mitigate them by all sorts of other things

228
00:16:34,139 --> 00:16:40,399
and you don't ever touch production in a destructive way.

229
00:16:41,600 --> 00:16:49,340
I... The AI agent stuff has changed this game completely.

230
00:16:49,559 --> 00:16:54,610
Yeah. Yeah. And so now this is not – I've

231
00:16:54,610 --> 00:16:58,960
really changed my mind over the last few days about

232
00:16:58,960 --> 00:17:04,579
this because what I was presented with was – I

233
00:17:04,579 --> 00:17:08,150
just went through – first of all, I went through

234
00:17:08,150 --> 00:17:11,960
and just turned all the – internet facing PHP sites

235
00:17:11,960 --> 00:17:14,539
that I ran. I just turned them all off. Yeah.

236
00:17:15,730 --> 00:17:17,789
and said, all right, we're going to do this one

237
00:17:17,789 --> 00:17:20,670
at a time. Do we know if anyone got popped

238
00:17:20,670 --> 00:17:24,869
on this? I haven't heard anything about it. I know

239
00:17:24,869 --> 00:17:28,690
there – I've heard tons of people saying they're seeing

240
00:17:28,690 --> 00:17:33,559
exploits, like Cloudflare and Amazon Web Services have both said

241
00:17:33,559 --> 00:17:39,259
they're seeing exploit attempts. Mm-hmm. So I just turned everything

242
00:17:39,259 --> 00:17:43,299
off according to what was being recommended because we didn't

243
00:17:43,299 --> 00:17:46,900
have any details yet. Right. And the details were being

244
00:17:46,900 --> 00:17:52,110
released at, what, 9 a.m. Central or something. And… So

245
00:17:52,110 --> 00:17:53,700
I turned them all off and I was like, okay,

246
00:17:53,700 --> 00:17:55,589
we're just going to fix this. As soon as the

247
00:17:55,589 --> 00:17:57,690
patches drop, we're going to fix this easiest to most

248
00:17:57,690 --> 00:18:06,019
difficult. And... The easiest ones were the Godcaster staging and

249
00:18:06,019 --> 00:18:12,110
Godcaster production. because those were very recent launches. They were

250
00:18:12,110 --> 00:18:14,440
only, you know, those servers were only like a couple

251
00:18:14,440 --> 00:18:17,589
years old. And so they were still on, everything was

252
00:18:17,589 --> 00:18:20,360
supported. There was no end of life anything. So as

253
00:18:20,360 --> 00:18:23,480
soon as the patches hit, actually the hardest part was

254
00:18:23,480 --> 00:18:28,019
just waiting for it. Ubuntu's mirrors to get the updated

255
00:18:28,019 --> 00:18:30,980
package. Everyone was waiting for that. Yeah. Yeah. Yeah. So

256
00:18:30,980 --> 00:18:33,799
as soon as those things hit our mirror, you know,

257
00:18:33,799 --> 00:18:38,160
I just installed it, you know, cycled the server, done.

258
00:18:39,369 --> 00:18:47,410
Then... The next hardest one was Podcast Index. Podcast Index

259
00:18:47,410 --> 00:18:58,119
had three... internet-facing PHP sites. The two API front-end servers.

260
00:18:59,440 --> 00:19:08,079
and podcasterwallet.com. But PodcasterWallet.com is still off. That virtual machine

261
00:19:08,079 --> 00:19:11,309
is still powered down because I think we need to

262
00:19:11,309 --> 00:19:15,799
have a discussion about whether it's still even needed. But

263
00:19:15,799 --> 00:19:22,970
that's a different discussion. The two API front-end servers... Those

264
00:19:22,970 --> 00:19:27,660
were running Ubuntu 20 LTS, which is end of life

265
00:19:27,660 --> 00:19:38,720
now. And they were running PHP 7.4, I believe. So,

266
00:19:41,849 --> 00:19:45,610
The... The most straightforward way to get up to date

267
00:19:45,610 --> 00:19:51,440
on those was to – upgrade was to do a

268
00:19:51,440 --> 00:19:55,319
release upgrade to Ubuntu 22, which is still in support,

269
00:19:55,460 --> 00:20:00,319
and that would have a backported patch for PHP 8.2.

270
00:20:01,700 --> 00:20:07,389
So I just put in a UFW firewall rule to

271
00:20:07,389 --> 00:20:10,430
block all HTTP traffic. That way it could still boot

272
00:20:10,430 --> 00:20:14,279
those machines up and SSH into them. And I just

273
00:20:14,279 --> 00:20:20,650
did the regular Ubuntu release, do release upgrade script. Let

274
00:20:20,650 --> 00:20:25,880
those – Did the first one, let it rebuild, as

275
00:20:25,880 --> 00:20:31,139
is typical with Ubuntu when it comes up. And there's

276
00:20:31,139 --> 00:20:34,279
a lot of things are – release upgrades are hard.

277
00:20:34,420 --> 00:20:36,759
They don't – they break a lot of stuff. So

278
00:20:36,759 --> 00:20:37,990
I had to go through and clean up a lot

279
00:20:37,990 --> 00:20:42,240
of things. In the process, I lost the PHP FPM

280
00:20:42,240 --> 00:20:46,480
configuration file. So I had to actually go into –

281
00:20:46,480 --> 00:20:49,559
it had all the fine-tuning that we use, you know?

282
00:20:49,639 --> 00:20:54,900
Yeah. Yeah. So I went into Linode and restored the

283
00:20:54,900 --> 00:20:58,950
previous day's backup to a separate machine so I could

284
00:20:58,950 --> 00:21:07,119
pull those config files off. Restored those. into saved a

285
00:21:07,119 --> 00:21:11,440
copy of that, restored it into the first front-end server,

286
00:21:11,440 --> 00:21:15,559
then powercycled that, then did the second one, updated everything,

287
00:21:15,559 --> 00:21:19,500
removed the UFW firewall rule, opened back traffic up, and

288
00:21:19,500 --> 00:21:26,900
good to go. Um, And so then those were good.

289
00:21:27,119 --> 00:21:30,119
I turned, I decided to just leave podcaster wallet off

290
00:21:30,119 --> 00:21:35,650
and, I had another server that I... um, that I

291
00:21:35,650 --> 00:21:38,049
worked on, or excuse me, that I support for a

292
00:21:38,049 --> 00:21:40,639
family member for their business, a backup and a backup

293
00:21:40,639 --> 00:21:42,539
to that backup and a backup to the backup to

294
00:21:42,539 --> 00:21:48,009
the backup. Exactly. Yes, exactly. I was like, um, you

295
00:21:48,009 --> 00:21:49,389
know, this one's just going to stay off for a

296
00:21:49,389 --> 00:21:53,400
couple of days. Uh, so I moved on. I did,

297
00:21:53,740 --> 00:21:59,000
then I did, uh, Then I went on to my

298
00:21:59,000 --> 00:22:04,440
– a couple of other servers that I manage. And

299
00:22:05,200 --> 00:22:08,170
I will say in this, these were all, I was

300
00:22:08,170 --> 00:22:11,829
bouncing back and forth. I had, I had agents going

301
00:22:11,829 --> 00:22:15,309
all over the place. Yeah, I'll bet. And this is

302
00:22:15,309 --> 00:22:18,700
all just side work while, you know, I'm also having

303
00:22:18,700 --> 00:22:21,059
to handle my day job. That's the primary thing that

304
00:22:21,059 --> 00:22:24,079
I'm, that I'm actually focused on. So I'm just this,

305
00:22:24,539 --> 00:22:28,599
while that thing is working, I'm, I'm just sprinkling in

306
00:22:28,599 --> 00:22:31,420
these other things at the same time as I can.

307
00:22:32,420 --> 00:22:37,710
So I'll say that – One of the servers that

308
00:22:37,710 --> 00:22:44,759
I manage... ended up It is a very complex configuration.

309
00:22:46,210 --> 00:22:49,839
Um... And I'll be deliberately vague about it. It was

310
00:22:49,839 --> 00:22:55,039
a very complex configuration and... It ended up being the

311
00:22:55,039 --> 00:22:58,360
best way to get this thing patched was to move

312
00:22:58,360 --> 00:23:02,660
it From one hosting company to I was going to

313
00:23:02,660 --> 00:23:05,759
move this from one hosting company to another anyway. So

314
00:23:05,759 --> 00:23:07,930
I'm like, I was going to have to build a

315
00:23:07,930 --> 00:23:12,079
new VM regardless. So I was like, OK, I'm going

316
00:23:12,079 --> 00:23:15,410
to go ahead and move. I'm just going to take

317
00:23:15,410 --> 00:23:18,360
this opportunity to move this box from one host to

318
00:23:18,360 --> 00:23:21,829
another. So I spun – I had the other ones

319
00:23:21,829 --> 00:23:24,309
– the existing one was spun up with a UFW

320
00:23:24,309 --> 00:23:27,869
firewall rule blocking all web traffic. Spun up the new

321
00:23:27,869 --> 00:23:32,549
one in the new hosting environment. And I said, all

322
00:23:32,549 --> 00:23:36,789
right, Claude Code, give me an SSH key that I

323
00:23:36,789 --> 00:23:41,650
can put on both of these boxes. And It's going

324
00:23:41,650 --> 00:23:43,579
to be a temporary key. I'm going to put it

325
00:23:43,579 --> 00:23:46,700
in the authorized keys file on both sides. I'm going

326
00:23:46,700 --> 00:23:52,240
to give you... Um, I'm going to give you the

327
00:23:52,240 --> 00:23:55,420
IP addresses and the usernames of both of these boxes.

328
00:23:56,980 --> 00:23:59,809
And I want you to get into the current box

329
00:23:59,809 --> 00:24:03,700
that's going to be decommissioned, and I want you to

330
00:24:03,700 --> 00:24:07,450
just do an extensive profile of this machine and tell

331
00:24:07,450 --> 00:24:10,440
me everything in it that is going to have to

332
00:24:10,440 --> 00:24:14,759
move to the new machine. And it chug, chug, chug,

333
00:24:14,759 --> 00:24:18,549
chug, chug. It just did its thing for a while,

334
00:24:18,549 --> 00:24:20,750
for an uncomfortably long period of time. And then it

335
00:24:20,750 --> 00:24:22,130
came back and it was like, all right, I got

336
00:24:22,130 --> 00:24:26,340
it. I know everything, and it listed every single thing

337
00:24:26,340 --> 00:24:30,500
out. I did a review, looked at all the stuff.

338
00:24:31,119 --> 00:24:34,259
Now this thing has got integration points with microservices in

339
00:24:34,259 --> 00:24:40,490
different places. Microservices architecture. Yes. Yes, yes. It is a

340
00:24:40,490 --> 00:24:44,210
complicated configuration. It's one of those snowflake servers that have

341
00:24:44,210 --> 00:24:47,150
built up over – seven or eight years that you

342
00:24:47,150 --> 00:24:49,480
make little tweaks to and then you never document you

343
00:24:49,480 --> 00:24:53,570
know that kind of thing and you become very afraid

344
00:24:53,570 --> 00:24:57,259
to touch it yeah yeah so it profiled all that

345
00:24:57,259 --> 00:24:59,539
stuff out and it was like all right you ready

346
00:24:59,539 --> 00:25:00,950
for me to go and i'm going to put all

347
00:25:00,950 --> 00:25:03,090
this stuff on the new box i was like yes

348
00:25:03,090 --> 00:25:08,500
go starts doing his thing, chugga, chugga, chugga, chugga. And

349
00:25:08,500 --> 00:25:14,159
then – After about 45 minutes, it's like... All right,

350
00:25:14,159 --> 00:25:17,049
you're up and running. And I was like, okay, so

351
00:25:17,049 --> 00:25:20,110
I go and check it. It looked good. Things were

352
00:25:20,110 --> 00:25:23,250
running. And then I start going through the checklist of

353
00:25:23,250 --> 00:25:25,750
like, you know, what did what did you miss? And

354
00:25:25,750 --> 00:25:27,599
of course, it missed a lot of stuff. But I'm

355
00:25:27,599 --> 00:25:30,150
start going through the checklist and I'm like, you know,

356
00:25:30,150 --> 00:25:32,639
you missed you know, you missed this service. You missed

357
00:25:32,639 --> 00:25:37,679
this service. And it's like, OK, got it. Boom. Flip

358
00:25:37,679 --> 00:25:40,340
it over. Yeah. And then I'm like, OK, you missed

359
00:25:40,340 --> 00:25:45,320
you missed this one. It's over there. And I'm like,

360
00:25:45,320 --> 00:25:47,809
okay, we split DNS. Okay, you need to change this

361
00:25:47,809 --> 00:25:50,289
on this side, this on this side. And I'm like,

362
00:25:50,289 --> 00:25:55,079
here, here's an API key for our web application firewall.

363
00:25:56,039 --> 00:26:01,179
Make sure that it's properly load balanced. Done. So all

364
00:26:01,179 --> 00:26:06,099
in all, this took about two and a half hours.

365
00:26:07,490 --> 00:26:13,289
But it did it perfectly. Yeah. And now in the

366
00:26:13,289 --> 00:26:18,679
process of doing this, it's now on everything is current,

367
00:26:18,679 --> 00:26:22,750
on the most current release of Ubuntu, current release of

368
00:26:22,750 --> 00:26:26,529
PHP. Everything has been updated. And I think this is

369
00:26:26,529 --> 00:26:29,349
the gift in general. I had my own small version

370
00:26:29,349 --> 00:26:32,480
of that because Freedom Controller was still running on a

371
00:26:32,480 --> 00:26:37,420
relatively expensive box. then there was, you know, it's a

372
00:26:37,420 --> 00:26:40,829
aggregator, which I really don't use anymore, but the aggregator

373
00:26:40,829 --> 00:26:43,440
is still running, getting blocked everywhere because it's on a

374
00:26:43,440 --> 00:26:47,119
Linode address. And, but it's still an integral part of

375
00:26:47,119 --> 00:26:54,700
my publishing process. And, It's Dave Jones' PHP special under

376
00:26:54,700 --> 00:26:58,170
the hood. Don't look. Don't look. With blowers coming through

377
00:26:58,170 --> 00:27:03,079
the hood. And like, you know, it's time. And so

378
00:27:03,079 --> 00:27:07,900
I wound up taking it offline and rebuilding it. The

379
00:27:07,900 --> 00:27:11,639
functionality of the publishing in the OPML editor, I actually

380
00:27:11,639 --> 00:27:16,240
wound up creating my own standalone OPML editor. Please tell

381
00:27:16,240 --> 00:27:21,200
me that you have completely decommissioned Freedom Controller. Yes, completely

382
00:27:21,200 --> 00:27:26,659
decommissioned. Hallelujah. Thank you, Jesus. Yes. God is good, brother.

383
00:27:27,279 --> 00:27:30,500
And I'm serious about that because don't look at the

384
00:27:30,500 --> 00:27:33,559
code. Nobody ever look at the code. The robot looked

385
00:27:33,559 --> 00:27:36,389
at the code and went, why don't I just rebuild

386
00:27:36,389 --> 00:27:43,820
all this? Yeah. Hey, Adam, I have a suggestion. I

387
00:27:43,820 --> 00:27:47,170
know it's load-bearing for your systems, but why don't I

388
00:27:47,170 --> 00:27:51,119
just rebuild all of this? Can we talk about this

389
00:27:51,119 --> 00:27:55,720
for one minute? I had a little OPML editor that

390
00:27:55,720 --> 00:27:59,860
I was using for my shows, and so I wound

391
00:27:59,860 --> 00:28:05,360
up. Rebuilding it with the publishing process, the HTML rendering,

392
00:28:05,360 --> 00:28:10,920
it's going to the object storage bucket, the redirector, all

393
00:28:10,920 --> 00:28:15,369
of that stuff, all of that rebuilt. And the redirector

394
00:28:15,369 --> 00:28:18,980
is now in AWS CloudFront. I mean, everything the way

395
00:28:18,980 --> 00:28:23,700
it should be done properly. And it's I think it

396
00:28:23,700 --> 00:28:26,769
gets shut down. I mean, it's off basically, but I

397
00:28:26,769 --> 00:28:30,679
don't want to delete it because once you delete it

398
00:28:30,679 --> 00:28:34,190
on Linode, it's gone. So, you know, let's just save

399
00:28:34,190 --> 00:28:36,490
this for a bit and see if anything breaks, which

400
00:28:36,490 --> 00:28:39,400
it hasn't so far. So it really was a wonderful

401
00:28:39,400 --> 00:28:42,840
opportunity to just go and fix stuff that had been

402
00:28:42,840 --> 00:28:45,710
on my list for a long time. You know, like

403
00:28:45,710 --> 00:28:48,360
you with your – I needed to rebuild that thing.

404
00:28:48,679 --> 00:28:50,679
So I think in a way it was also good.

405
00:28:50,920 --> 00:28:52,579
You know, it's like I think everybody had a version

406
00:28:52,579 --> 00:28:54,860
of that. Like, oh, you know, this crap I've been

407
00:28:54,860 --> 00:28:56,909
looking at for so long. Let me just fix it

408
00:28:56,909 --> 00:28:58,679
right this time instead of – if it was just

409
00:28:58,679 --> 00:29:01,299
a patch, we all would have done patches. And now

410
00:29:01,299 --> 00:29:03,880
it's like, yeah, we got to update, got to get

411
00:29:03,880 --> 00:29:07,110
the right stuff. Yeah. And so to me, it was

412
00:29:07,110 --> 00:29:10,980
super advantageous. So I'm kind of happy about that. But

413
00:29:10,980 --> 00:29:13,940
I was praying for you, brother. And I mean that.

414
00:29:14,079 --> 00:29:18,179
I'm like, ah. Well, yeah, there's another. There's a second.

415
00:29:18,480 --> 00:29:21,860
So I ended up doing Grand Total ended up doing.

416
00:29:22,529 --> 00:29:29,590
For... Of that. Yeah. For migrations, essentially, of a search

417
00:29:29,590 --> 00:29:34,009
to just – because the server I was dealing with

418
00:29:34,009 --> 00:29:37,029
was so end of life. Yeah. That it just wasn't

419
00:29:37,029 --> 00:29:39,970
worth trying to patch that thing. And just once I

420
00:29:39,970 --> 00:29:43,670
had that first experience with one of our mission critical

421
00:29:43,670 --> 00:29:47,070
systems, I was like, okay, okay. This is doable. I

422
00:29:47,070 --> 00:29:49,750
can do this. It's going to – each one of

423
00:29:49,750 --> 00:29:52,230
these is going to take a couple of hours, but

424
00:29:52,230 --> 00:29:55,090
pre-agentic, it would have – I mean this would have

425
00:29:55,090 --> 00:29:56,900
taken me a couple of days.

426
00:30:00,109 --> 00:30:04,680
customer who has video enclosures and we wanted to migrate

427
00:30:04,680 --> 00:30:08,839
it over to RSS.com. And Alberto, bless him, man. He's

428
00:30:08,839 --> 00:30:11,259
like, you know, this is good because we actually wanted

429
00:30:11,259 --> 00:30:13,420
to do all this stuff. And he comes up with

430
00:30:13,420 --> 00:30:16,250
this whole HLS video audio, which is exactly the way

431
00:30:16,250 --> 00:30:18,769
it should be done. But we had a clock running

432
00:30:18,769 --> 00:30:22,619
out. because this customer wanted to really migrate off of

433
00:30:22,619 --> 00:30:26,480
pod beam and and now i knew you were because

434
00:30:26,480 --> 00:30:28,740
you looked at the email alberto sent and you're like

435
00:30:28,740 --> 00:30:31,140
uh okay this is not something i'm gonna be able

436
00:30:31,140 --> 00:30:35,039
to do today and and so and and you know

437
00:30:35,039 --> 00:30:38,230
the And all of a sudden, I went like, well,

438
00:30:38,230 --> 00:30:41,109
why am I so stupid? I'm just going to spin

439
00:30:41,109 --> 00:30:44,539
up a $5 Linode, little mini host, set in a

440
00:30:44,539 --> 00:30:49,019
301 redirect, made a whole upload page, everything. So we're

441
00:30:49,019 --> 00:30:52,660
safe. No clock running. And it took me, I don't

442
00:30:52,660 --> 00:30:56,680
know, maybe an hour total. And I didn't do the

443
00:30:56,680 --> 00:31:00,430
DNS. I didn't do the Linode setup. The agent did

444
00:31:00,430 --> 00:31:03,730
all of that. I just directed it and said, you

445
00:31:03,730 --> 00:31:06,630
know, why don't you connect that to op3.dev? So we

446
00:31:06,630 --> 00:31:09,680
got some stats, put a stats button on there. And

447
00:31:09,680 --> 00:31:14,450
it's like lifesaver, lifesaver. And it looks like magic. This

448
00:31:14,450 --> 00:31:18,740
is the problem. It is sort of a problem, yeah.

449
00:31:19,200 --> 00:31:21,759
We used to call guys that could do that, like,

450
00:31:21,759 --> 00:31:26,279
wow, you're a code ninja. Ninja, warrior. Wizard. Wizard. And

451
00:31:26,279 --> 00:31:29,849
so now it's like... You just do something. Then you

452
00:31:29,849 --> 00:31:32,640
should go have a hot dog, walk around the block,

453
00:31:32,640 --> 00:31:34,930
and then come back. And then, you know, stand over

454
00:31:34,930 --> 00:31:37,380
the radiator for five minutes and look all sweaty like,

455
00:31:37,460 --> 00:31:39,049
oh, I got it done for you. I got it

456
00:31:39,049 --> 00:31:41,509
done, boss. It was hard, but I got it done

457
00:31:41,509 --> 00:31:44,750
for you. Yeah. I pulled an all-nighter. I got it

458
00:31:44,750 --> 00:31:49,799
done. Yeah. But that – the – The problem with

459
00:31:49,799 --> 00:31:53,640
– one of the problems with my situation is this

460
00:31:53,640 --> 00:31:56,609
hit – At a time in a day job when

461
00:31:56,609 --> 00:31:59,160
I was already rolling out some servers. And so I

462
00:31:59,160 --> 00:32:02,359
was middle. I was in the middle. I had hardware

463
00:32:02,359 --> 00:32:07,349
strewn everywhere. Fiber channel switches half configured. And I just

464
00:32:07,349 --> 00:32:11,180
had to drop all of that and, like, go all

465
00:32:11,180 --> 00:32:17,410
in on this thing. And I finally got... I've only

466
00:32:17,410 --> 00:32:20,539
got one. Well, Podcaster Wallet is the only one that's

467
00:32:20,539 --> 00:32:27,799
left. Right. That's not been dealt with. But I, That...

468
00:32:28,619 --> 00:32:36,920
That whole mindset – of don't patch mitigate, I just

469
00:32:36,920 --> 00:32:40,230
don't really, I don't think it applies anymore. And it's

470
00:32:40,230 --> 00:32:43,059
a little bit of a learning curve for me too

471
00:32:43,059 --> 00:32:47,079
because I'm always let, I mean, I've got, I mean,

472
00:32:47,910 --> 00:32:52,740
I mean, I've had – I have had up until

473
00:32:52,740 --> 00:32:58,529
recently – servers running in production running Ubuntu 12. Yeah,

474
00:32:58,529 --> 00:33:01,430
baby. I don't even know how old that is. How

475
00:33:01,430 --> 00:33:05,000
old is Ubuntu 12? No. I'm pretty old. Let's see.

476
00:33:05,119 --> 00:33:12,779
Ubuntu 12 LTS. When was that released? It was released

477
00:33:12,779 --> 00:33:18,759
in April of 2012, 14 years old. Hmm. And you

478
00:33:18,759 --> 00:33:24,380
just... You know, you just mitigate and you wrap it.

479
00:33:25,079 --> 00:33:28,759
And, you know, my security sort of strategy is you

480
00:33:28,759 --> 00:33:33,869
you wrap things in obfuscation first and then you firewall

481
00:33:33,869 --> 00:33:37,630
off the obfuscated stuff to where you only have this

482
00:33:37,630 --> 00:33:42,369
tiny exposure. Yeah. Basically, just the minimal attack surface necessary

483
00:33:42,369 --> 00:33:46,369
to run this thing. And then you layer on top

484
00:33:46,369 --> 00:33:48,639
of that all kinds of other stuff. Fail to ban.

485
00:33:49,220 --> 00:33:54,029
Yeah. Cloud flare. Yeah. Yeah. Where if you add one

486
00:33:54,029 --> 00:33:58,200
little act up and you're done, you're banned. Yeah. That's

487
00:33:58,200 --> 00:34:03,450
my favorite. Fail to ban. Yeah. Boom. Bye. Bye. Eric

488
00:34:03,450 --> 00:34:06,750
PP is right, though. The mitigation didn't work in this

489
00:34:06,750 --> 00:34:09,920
case because this was exploitable with just a simple post

490
00:34:09,920 --> 00:34:17,039
request. And that happens before your application even sees it.

491
00:34:17,360 --> 00:34:20,650
Right. This all happens within – because it was –

492
00:34:20,650 --> 00:34:24,190
the worst part of this was it was mod PHP

493
00:34:24,190 --> 00:34:31,050
and PHP FPM, which actually inject themselves into – well,

494
00:34:31,050 --> 00:34:33,920
PHP FPM does not, but – ModPHP injects itself into

495
00:34:33,920 --> 00:34:36,409
the Apache process, so you don't even get a chance

496
00:34:36,409 --> 00:34:42,050
to see it until you're already popped. And so that's

497
00:34:42,050 --> 00:34:46,440
– and you can't block posts. You can block it

498
00:34:46,440 --> 00:34:48,519
on some paths, but you can't block it because you

499
00:34:48,519 --> 00:34:51,900
can't say, well, I'll put it behind authentication because –

500
00:34:52,199 --> 00:34:55,010
You have post requests on login forms. So you can't

501
00:34:55,010 --> 00:34:59,989
look at it. Yeah. This was unmitigatable. Yeah. And this

502
00:34:59,989 --> 00:35:04,920
concludes this week's episode of Security Now with Dave Jones.

503
00:35:06,079 --> 00:35:10,029
This. Yeah. I don't know. Not fun. I don't know

504
00:35:10,029 --> 00:35:12,880
if you had a. A chance to see the video

505
00:35:12,880 --> 00:35:19,460
I put on the Mastodon? of my vibe coded app?

506
00:35:19,539 --> 00:35:23,090
No, it was two days ago. No, you didn't have

507
00:35:23,090 --> 00:35:32,940
time. It's okay. So the so sorry, don't apologize. So

508
00:35:32,940 --> 00:35:35,190
I told you that I vibe coded my own podcast

509
00:35:35,190 --> 00:35:39,980
app, right? We went through that. Didn't we talk? Oh,

510
00:35:39,980 --> 00:35:42,400
no, that's right. We didn't. So he didn't tell me

511
00:35:42,400 --> 00:35:46,460
that. Oh, okay. So last week we talked about Google

512
00:35:46,460 --> 00:35:52,699
Play now coming so you can share your vibe-coded apps

513
00:35:52,699 --> 00:35:56,480
with your buddies without going through a full Play Store

514
00:35:56,480 --> 00:36:01,230
process. Yes. And I think – you know, actually, I

515
00:36:01,230 --> 00:36:04,130
think it was – Yeah, I think it was during

516
00:36:04,130 --> 00:36:07,460
just before we started last week's boardroom. I I told

517
00:36:07,460 --> 00:36:11,179
my robot, I said, OK, vibe code. I give it

518
00:36:11,179 --> 00:36:13,760
one prompt vibe code. I didn't say vibe. Build an

519
00:36:13,760 --> 00:36:17,099
app for me from I have Android. And here's what

520
00:36:17,099 --> 00:36:21,019
I wanted to do. And it did it. And the

521
00:36:21,019 --> 00:36:26,900
main requirement was. You need to connect to my Muse

522
00:36:26,900 --> 00:36:30,900
robot because Muse has – I use that right now

523
00:36:30,900 --> 00:36:34,920
exclusively for just my life stuff, you know, calendar, reminders,

524
00:36:34,920 --> 00:36:39,300
to-do lists, you know, tracking bills, that kind of stuff.

525
00:36:40,679 --> 00:36:44,139
And so, of course, there's, you know, a real –

526
00:36:44,829 --> 00:36:49,010
You know, a connection between an app, a podcast app

527
00:36:49,010 --> 00:36:54,440
running as, you know, sideloaded onto Android can't directly communicate

528
00:36:54,440 --> 00:36:57,170
with Muse. So I did have to put a little

529
00:36:57,170 --> 00:37:00,900
bridge server in between the two. Because, you know, Muse

530
00:37:00,900 --> 00:37:03,940
does have restrictions. You think you could do everything, but

531
00:37:03,940 --> 00:37:06,420
it's like, no, I can't create an API for you.

532
00:37:06,500 --> 00:37:09,210
Oh, okay. Well, that's too bad. So, you know, it's

533
00:37:09,210 --> 00:37:11,960
a server, and it, you know, it pings it and

534
00:37:11,960 --> 00:37:14,269
sees what's going on. So I just want to be

535
00:37:14,269 --> 00:37:17,659
able to talk to it, find me stuff. And so...

536
00:37:18,050 --> 00:37:20,760
And I think I did at this point, I've probably

537
00:37:20,760 --> 00:37:24,510
done 40 follow-up prompts for changes for new features, et

538
00:37:24,510 --> 00:37:27,300
cetera. And so this for the so for a week

539
00:37:27,300 --> 00:37:30,300
now, I've been living with this app, which tracks the

540
00:37:30,300 --> 00:37:34,789
following calendar, free time, next event, location, home, car, church

541
00:37:34,789 --> 00:37:37,730
made near you. What I listen to this week's no

542
00:37:37,730 --> 00:37:42,699
agenda topics, my agents, show prep, stringers, track shows. What

543
00:37:42,699 --> 00:37:47,369
news knows about my taste. And then there's different notifications,

544
00:37:47,369 --> 00:37:51,659
15 minutes before a live show I follow. There's also

545
00:37:51,659 --> 00:37:55,119
exceptions like I don't want to be notified of any

546
00:37:55,119 --> 00:37:59,029
Joe Rogan episodes with MMA in it. But also I

547
00:37:59,029 --> 00:38:04,029
don't. I'm not interested. But also there's certain podcasts that

548
00:38:04,029 --> 00:38:07,730
only if something in the show is of interest to

549
00:38:07,730 --> 00:38:12,029
me, it does transcripts on the phone itself. The full

550
00:38:12,029 --> 00:38:18,820
thing, value for value, the funding tag, everything all built

551
00:38:18,820 --> 00:38:24,820
in. And I mean, it has been so delightful. So

552
00:38:24,820 --> 00:38:29,289
just today I've got Discovery, Bitcoin maximalist, the Rollo and

553
00:38:29,289 --> 00:38:32,860
Slappy show. And it says, write in your Bitcoin lane.

554
00:38:33,000 --> 00:38:36,760
Then I have, is socialism more Christian than capitalism? It's

555
00:38:36,760 --> 00:38:40,250
a faith commentary show right at your faith plus economics

556
00:38:40,250 --> 00:38:46,429
lane. Yeah. Here's another one. Halloween secular treat or spiritual

557
00:38:46,429 --> 00:38:49,039
trap from stand firm and dark. I never heard these

558
00:38:49,039 --> 00:38:53,130
podcasts. Indie Christian apologetics with real teeth and Halloween episode

559
00:38:53,130 --> 00:38:59,380
lands eight days before. And then says podcast podcast weekly

560
00:38:59,380 --> 00:39:03,199
review. Which I already subscribed to, but it says you

561
00:39:03,199 --> 00:39:09,320
were mentioned several times in this one. So all to

562
00:39:09,320 --> 00:39:12,279
say, and I know you have a couple of clips

563
00:39:12,279 --> 00:39:16,510
from Pod News Weekly Review, as do I. Interestingly enough,

564
00:39:16,510 --> 00:39:19,760
we both brought two clips from the same power show.

565
00:39:21,699 --> 00:39:23,900
I wonder which one you got. You want to go

566
00:39:23,900 --> 00:39:29,940
first? Or shall I go first? Uh, you can, why

567
00:39:29,940 --> 00:39:32,329
don't you just play mine back to back? Cause mine

568
00:39:32,329 --> 00:39:34,980
is just a simple commentary on what their guests said.

569
00:39:35,159 --> 00:39:39,519
Okay. The video one first or the funnel. the video

570
00:39:39,519 --> 00:39:42,279
then funnel don't do this gee it's not working we

571
00:39:42,279 --> 00:39:44,710
tried it and look at where we are today so

572
00:39:44,710 --> 00:39:49,579
there's no question i think it's 73 percent of podcasts

573
00:39:49,579 --> 00:39:53,179
now have video yeah i heard this and i'm like

574
00:39:53,179 --> 00:39:57,349
nah i don't think so well where is it play

575
00:39:57,349 --> 00:40:01,000
the second one I don't think, I think Tom is

576
00:40:01,000 --> 00:40:04,720
right. 73% are using this as a funnel, but that's

577
00:40:04,720 --> 00:40:10,980
not exactly where they end up. Did he just glitch

578
00:40:10,980 --> 00:40:15,300
out or something and just go 73s everywhere? 73s, good

579
00:40:15,300 --> 00:40:27,699
buddy. I've never heard a statistic that says – 73%

580
00:40:27,699 --> 00:40:30,480
of podcasts have video. That is not true. No, and

581
00:40:30,480 --> 00:40:34,480
he's a professor, I believe, right? The Stephen Goldstein. Yeah,

582
00:40:34,480 --> 00:40:37,289
where did he get these numbers from? Well, he's very

583
00:40:37,289 --> 00:40:46,220
much a podcast industrial complex professor. So P-I-C-P-H-D. He was

584
00:40:46,220 --> 00:40:50,159
very knowledgeable. I found to be extremely knowledgeable about amp

585
00:40:50,159 --> 00:40:55,039
accords and download numbers and all the issues. And so

586
00:40:55,039 --> 00:40:57,920
he was very knowledgeable about all of that. Very knowledgeable.

587
00:40:59,659 --> 00:41:05,940
But then he and Sam took the... my favorite slur,

588
00:41:05,940 --> 00:41:12,639
normal people, normies, to a whole new level of insanity.

589
00:41:13,800 --> 00:41:17,659
And, of course, it's my own fault, but, you know,

590
00:41:17,659 --> 00:41:23,130
Sam started talking about the podcast. He didn't even talk

591
00:41:23,130 --> 00:41:26,500
about the podcast index robot, just about vibe coding things.

592
00:41:26,619 --> 00:41:30,250
And so he obviously used the atom hat and took

593
00:41:30,250 --> 00:41:34,929
out advertising as the example, whereas the example I'm trying

594
00:41:34,929 --> 00:41:37,179
to show is look at all these new podcasts I'm

595
00:41:37,179 --> 00:41:41,039
discovering. My robot is tracking what I have listened to,

596
00:41:41,039 --> 00:41:44,150
literally what I have listened to, how much I have

597
00:41:44,150 --> 00:41:47,059
listened to it because I feed that back into the

598
00:41:47,059 --> 00:41:51,360
robot. And it's giving me great recommendations based upon that.

599
00:41:51,500 --> 00:41:53,820
This is what, you know, when he talks about video

600
00:41:53,820 --> 00:41:56,860
being used as a funnel. Yeah, I think that's probably

601
00:41:56,860 --> 00:42:01,940
true. And it's also destroying podcasts because people wind up.

602
00:42:02,000 --> 00:42:05,380
He says it himself. We have liquid content and people

603
00:42:05,380 --> 00:42:09,070
will watch three clips of a podcast. OK, I've seen

604
00:42:09,070 --> 00:42:11,599
the podcast. I don't need to watch it or listen

605
00:42:11,599 --> 00:42:16,159
to it, which I think is very destructive. and maybe

606
00:42:16,159 --> 00:42:20,159
not stoppable, but that's what I don't like about YouTube,

607
00:42:20,159 --> 00:42:23,949
etc., is people clipping your stuff. So here's Sam with

608
00:42:23,949 --> 00:42:27,639
the setup. Moving on a little bit then, Stephen, one

609
00:42:27,639 --> 00:42:29,489
of the other guests on this week's show, along with

610
00:42:29,489 --> 00:42:33,239
yourself, is Adam Curry, the podfather himself, and Adam's been

611
00:42:33,239 --> 00:42:37,619
talking about vibe coding and agentic ai and he's been

612
00:42:37,619 --> 00:42:42,019
talking about how fundamentally the the model of podcasting is

613
00:42:42,019 --> 00:42:44,529
going to change in the future now he did say

614
00:42:44,529 --> 00:42:47,199
it and you know being an app developer it was

615
00:42:47,199 --> 00:42:49,900
like whoa but he did say that in the future

616
00:42:49,900 --> 00:42:54,210
he sees personalized apps where he doesn't need a podcast

617
00:42:54,210 --> 00:42:57,570
app from a company he will create his own version

618
00:42:57,570 --> 00:43:01,130
to customize and tailor to his own needs but again

619
00:43:01,130 --> 00:43:04,199
in the demo that he gave on podcasting to the

620
00:43:04,199 --> 00:43:07,849
own with Dave Jantish he took an episode that did

621
00:43:07,849 --> 00:43:11,079
have ads he got his muse ai to strip out

622
00:43:11,079 --> 00:43:14,750
the ads to create clips of the best parts and

623
00:43:14,750 --> 00:43:18,550
create a playlist. So he's doing the clip economy without

624
00:43:18,550 --> 00:43:23,559
advertising, without apps, all in one. Is that the future?

625
00:43:24,279 --> 00:43:27,300
Okay. So I don't know about I'm doing the clip

626
00:43:27,300 --> 00:43:30,539
economy. I'm just trying to tailor my own experience, which

627
00:43:30,539 --> 00:43:33,659
has just been wonderful with... You know, the way it's

628
00:43:33,659 --> 00:43:36,029
doing chapters the way I want it, it's doing transcripts

629
00:43:36,029 --> 00:43:38,220
the way I want it, everything the way I want

630
00:43:38,220 --> 00:43:40,159
it. And, you know, someone else might look at this

631
00:43:40,159 --> 00:43:41,679
app and go, boy, that's a mess, but it's the

632
00:43:41,679 --> 00:43:44,099
way I want it. So that's up to me. You

633
00:43:44,099 --> 00:43:47,300
know, the algorithm that I'm being presented with is not

634
00:43:47,300 --> 00:43:51,019
developed by YouTube or by Apple editorial. It's me. It's

635
00:43:51,019 --> 00:43:53,760
me. It's the stuff I'm doing. And so I like

636
00:43:53,760 --> 00:43:57,309
it. But here's where the professor, I mean, what in

637
00:43:57,309 --> 00:44:00,849
the world? Is that really the future we want? So,

638
00:44:00,849 --> 00:44:07,139
first of all, he's super smart. Yeah, yeah, yeah. Bingo.

639
00:44:07,460 --> 00:44:09,739
Just wanted to make sure we all heard that. Well,

640
00:44:09,739 --> 00:44:12,750
he's super smart, and there needs to be people who

641
00:44:12,750 --> 00:44:17,159
are thinking ahead. I have a very consumer-based feel on

642
00:44:17,159 --> 00:44:20,500
things. I'm always starting with the consumer on. I am

643
00:44:20,500 --> 00:44:24,720
the consumer. This is what kills me. I am literally

644
00:44:24,720 --> 00:44:28,489
the consumer. I'm a consumer who wanted a different podcast

645
00:44:28,489 --> 00:44:33,019
app experience. Always starting with the consumer on back. And

646
00:44:33,019 --> 00:44:36,989
the consumer does not like friction. Everything that puts something

647
00:44:36,989 --> 00:44:40,420
in front of them that's either a paywall or difficulty.

648
00:44:40,860 --> 00:44:43,949
Or how about Microsoft Ribbon or things in a place

649
00:44:43,949 --> 00:44:48,119
that I don't like them or features that developers out

650
00:44:48,119 --> 00:44:51,400
of necessity have to implement in a certain way so

651
00:44:51,400 --> 00:44:54,840
that everybody kind of gets what they like. That is

652
00:44:54,840 --> 00:44:58,489
what I'm talking about. That is... is friction, he's only

653
00:44:58,489 --> 00:44:59,960
thinking about paywalls

654
00:45:00,059 --> 00:45:05,579
advertising is friction. No, friction is my own discovery journey.

655
00:45:05,579 --> 00:45:09,849
And selection doesn't work all that well. And I think

656
00:45:09,849 --> 00:45:14,099
about this thing. My wife, who is... Here we go.

657
00:45:14,099 --> 00:45:16,329
This is the thing that kills me. I can't believe

658
00:45:16,329 --> 00:45:19,039
he did this. This drives you crazy. It does. My

659
00:45:19,039 --> 00:45:25,289
wife, my mom, my sister, my church friends, my this,

660
00:45:25,289 --> 00:45:29,219
my that, they're clearly not like us. They are just

661
00:45:29,219 --> 00:45:32,760
normies. Work all that well. And I think about this

662
00:45:32,760 --> 00:45:37,260
thing. My wife... who is a Yale graduate in law

663
00:45:37,260 --> 00:45:40,739
school. Oh, okay. It has nothing to do with education.

664
00:45:41,239 --> 00:45:44,340
No, you don't have to have a law degree or

665
00:45:44,340 --> 00:45:48,340
go to Yale. You're just dumb. You have no intuition,

666
00:45:48,340 --> 00:45:52,039
you. Everything else. She does not want to mess around

667
00:45:52,039 --> 00:45:55,019
with the settings on that iPhone. What settings? I just

668
00:45:55,019 --> 00:46:00,050
spoke. I said, robot, make this for me. This is

669
00:46:00,050 --> 00:46:03,340
not of interest to her. And so the notion that...

670
00:46:03,619 --> 00:46:06,139
She's going to sit there and start curating her own

671
00:46:06,139 --> 00:46:10,230
lists. No, you missed the point. I'm not curating my

672
00:46:10,230 --> 00:46:13,150
own list at all. The robot is doing it for

673
00:46:13,150 --> 00:46:16,760
me. So forth. It's just crazy. What she wants is

674
00:46:16,760 --> 00:46:20,940
the stuff to be readily available when she wants it.

675
00:46:21,739 --> 00:46:26,070
And certainly there are people who are... cognizant of that

676
00:46:26,070 --> 00:46:28,690
all over the media so i don't know i do

677
00:46:28,690 --> 00:46:32,280
i do know that the robot's getting smarter and that

678
00:46:32,280 --> 00:46:35,340
the robot can do lots of things for us okay

679
00:46:35,340 --> 00:46:38,469
now for a second i'm like oh he uses the

680
00:46:38,469 --> 00:46:41,929
term robot this is good i do know that but

681
00:46:41,929 --> 00:46:46,190
the professor is way check the calendar dude and i

682
00:46:46,190 --> 00:46:50,719
am deep in in my own consumer way with chat

683
00:46:50,719 --> 00:46:54,110
gpt and claude but i am not a coder i'm

684
00:46:54,110 --> 00:46:57,760
not vibe coding i'm not doing anything like that because

685
00:46:57,760 --> 00:47:01,050
you don't have to be a coder professor i understand

686
00:47:01,050 --> 00:47:04,349
that the tools get smarter and we can start asking

687
00:47:04,349 --> 00:47:07,300
for things And when we can make that all vocal

688
00:47:07,300 --> 00:47:10,559
or just a simple command, I think, yeah, I think

689
00:47:10,559 --> 00:47:14,760
that's possible. Okay, so what if that was possible already

690
00:47:14,760 --> 00:47:19,909
and children and people around the world are already discovering

691
00:47:19,909 --> 00:47:24,079
this? How long would it take before your wife and

692
00:47:24,079 --> 00:47:28,219
Sam's wife and Sam's mom died? And your church people

693
00:47:28,219 --> 00:47:30,719
will be smart enough to be able to figure it

694
00:47:30,719 --> 00:47:33,789
out. But who knows? Yeah, I think it's 10 years

695
00:47:33,789 --> 00:47:36,860
out. 10 years! Yeah! It's a decade away. It's a

696
00:47:36,860 --> 00:47:40,309
little bit of a concept idea and somebody smart as

697
00:47:40,309 --> 00:47:42,679
Adam Curry can do it, but... I don't think, as

698
00:47:42,679 --> 00:47:45,150
you said, your wife, my wife, who used to run

699
00:47:45,150 --> 00:47:47,840
MSN, is going to want to waste her time doing

700
00:47:47,840 --> 00:47:54,079
that. Ah! This is what gets me nuts. Because that

701
00:47:54,079 --> 00:48:02,900
is exactly where we are. Um, I'm going to disappoint

702
00:48:02,900 --> 00:48:11,780
you in my partial agreement with this. Okay, okay. This

703
00:48:11,780 --> 00:48:21,900
is the Gene's mom argument. Mm-hmm. And – So –

704
00:48:23,539 --> 00:48:27,360
It takes – this irked you last show or the

705
00:48:27,360 --> 00:48:32,750
show before when I mentioned my dad. Mm-hmm. And you're

706
00:48:32,750 --> 00:48:35,480
like, oh, you're ageist. I don't know. Did I say

707
00:48:35,480 --> 00:48:38,639
that specifically? No, well, no, you didn't say that. You're

708
00:48:38,639 --> 00:48:42,260
the old guy. The old guy can't do it. So

709
00:48:42,260 --> 00:48:46,719
I'm like, well, but see, the thing, this doesn't come

710
00:48:46,719 --> 00:48:50,820
from just – This doesn't come from a stereotype. This

711
00:48:50,820 --> 00:48:55,840
comes from actual experience. I know. Because there are people

712
00:48:55,840 --> 00:48:59,800
in your life when you're like – Hey, I want

713
00:48:59,800 --> 00:49:02,789
you to – hey, can you test the new Godcaster

714
00:49:02,789 --> 00:49:05,099
mobile app for me? Yeah, sure. How do I do

715
00:49:05,099 --> 00:49:07,289
that? Well, here, let me send you a test flight

716
00:49:07,289 --> 00:49:11,559
link. Yeah, what's that? And you're like, oh, whoa, whoa.

717
00:49:11,719 --> 00:49:14,820
Yeah, yeah. It's like, where do I put – do

718
00:49:14,820 --> 00:49:16,099
I put in my – What password do I put

719
00:49:16,099 --> 00:49:18,090
in? Well, you put in your Apple account. What do

720
00:49:18,090 --> 00:49:20,150
I have an Apple account? Well, yeah, you do. I

721
00:49:20,150 --> 00:49:23,389
got you. I got you. It's like an hour long

722
00:49:23,389 --> 00:49:26,329
ordeal, you know, and then you and then you're like,

723
00:49:26,329 --> 00:49:29,539
OK, this person's going to this person's going to somehow

724
00:49:29,539 --> 00:49:33,179
vibe code their own podcast. No, my here's my point.

725
00:49:34,119 --> 00:49:37,699
My point is you're absolutely right. My point is we

726
00:49:37,699 --> 00:49:43,860
are now in the era of where Gene's mom rests

727
00:49:43,860 --> 00:49:49,440
in peace. Gene's mom... We'll be able to do this

728
00:49:49,440 --> 00:49:53,420
because there is a robot on the other end that

729
00:49:53,420 --> 00:49:58,179
is helping Jean's mom through this. And saying, no, no,

730
00:49:58,179 --> 00:50:00,550
no, here's what you do. Or it may open it

731
00:50:00,550 --> 00:50:04,380
for her or do all these different things. We are

732
00:50:04,380 --> 00:50:08,880
in the place. Where this conversation is about to be

733
00:50:08,880 --> 00:50:14,710
outdated, not 10 years, 10 months, because I'm seeing people

734
00:50:14,710 --> 00:50:17,909
around me all because of my incessant banging of the

735
00:50:17,909 --> 00:50:21,519
drum. People are emailing me 30, 30 emails a day.

736
00:50:21,800 --> 00:50:24,909
I thought you were crazy, but I've listened to you

737
00:50:24,909 --> 00:50:27,920
for 20 years. I'm going to give it a shot.

738
00:50:28,409 --> 00:50:31,300
Holy crap. I can't believe what I'm able to do.

739
00:50:32,059 --> 00:50:36,579
And they've list these just incredible things they're doing. And

740
00:50:36,579 --> 00:50:43,579
it was... We're so used to waiting for a development

741
00:50:43,579 --> 00:50:47,320
team to add a feature or we get excited. Oh,

742
00:50:47,320 --> 00:50:52,260
my gosh. The new version of XX is out. I

743
00:50:52,260 --> 00:50:55,260
can't wait to see what they've done. This is the

744
00:50:55,260 --> 00:51:01,000
change that is here. That's what I'm saying. And. I

745
00:51:01,000 --> 00:51:07,519
am personally excited for podcasting because the most important thing

746
00:51:07,519 --> 00:51:11,179
right now in this new world that we're going into

747
00:51:11,179 --> 00:51:15,730
is the RSS feed. That is going to be of

748
00:51:15,730 --> 00:51:21,210
super importance. Because you're going to watch everybody's numbers go

749
00:51:21,210 --> 00:51:24,920
down. Apple, Spotify, everybody's numbers are going to go. Why

750
00:51:24,920 --> 00:51:30,050
would I even deal with YouTube's algorithm? Why don't I

751
00:51:30,050 --> 00:51:33,279
just, in fact, just before I started the show, I'm

752
00:51:33,279 --> 00:51:35,579
like, I'm going to build an X app. That only

753
00:51:35,579 --> 00:51:38,070
shows me stuff that I care about, that I'm interested

754
00:51:38,070 --> 00:51:40,500
in, that I've been thinking about, that I've been talking

755
00:51:40,500 --> 00:51:44,139
to my friends about. This is the change. We are

756
00:51:44,139 --> 00:51:47,900
going to – the data source will be important always.

757
00:51:48,760 --> 00:51:53,940
But the algorithms and the layout and the user experience,

758
00:51:53,940 --> 00:51:56,619
we're going to be in full control of that. And

759
00:51:56,619 --> 00:51:59,940
I really believe, yes, Gene's mom, rest in peace, will

760
00:51:59,940 --> 00:52:07,039
figure this out much sooner than we realize. And I

761
00:52:07,039 --> 00:52:11,179
also think that the whole deprecation of XSLT had something

762
00:52:11,179 --> 00:52:16,489
to do with it. Oh, bring that around. I don't

763
00:52:16,489 --> 00:52:21,940
know how. Well, XSLT is a beautiful machine readable format.

764
00:52:22,779 --> 00:52:25,599
So let's get rid of that so that we can

765
00:52:25,599 --> 00:52:29,639
protect our data sources in different ways. We don't want

766
00:52:29,639 --> 00:52:32,369
you to be able to scrape our web pages. We

767
00:52:32,369 --> 00:52:35,570
want you to go to our API or MCP server

768
00:52:35,570 --> 00:52:40,420
or whatever. We want to have control over the data.

769
00:52:42,079 --> 00:52:49,690
I'm more and more convinced of that. Bye. The we've

770
00:52:49,690 --> 00:52:55,210
we've been through a version of this. Is the thing,

771
00:52:55,210 --> 00:52:59,579
though, of trying to get people onboarded with, like, lightning

772
00:52:59,579 --> 00:53:05,690
wallets and such. Very different. Very complicated. Okay, so let

773
00:53:05,690 --> 00:53:15,039
me tell you about my journey with Bitcoin. with podcasting

774
00:53:15,039 --> 00:53:20,409
agentically. So I told you over the past couple of

775
00:53:20,409 --> 00:53:25,059
weeks I've been on this – mission however long it

776
00:53:25,059 --> 00:53:28,940
takes to come up with a rock solid 100% foolproof

777
00:53:28,940 --> 00:53:37,639
ad stripper. Mm-hmm. An ad stripper. That even sounds great,

778
00:53:37,639 --> 00:53:43,130
doesn't it? Mm-hmm. We need to resurrect the Dvorak for

779
00:53:43,130 --> 00:53:49,880
that. Ooh. Straight from Reseda, here she is, Raven. Give

780
00:53:49,880 --> 00:54:00,500
it up. The ad stripper. Stage five. So this –

781
00:54:00,500 --> 00:54:03,440
and so I can say that at this point –

782
00:54:04,150 --> 00:54:08,869
It's about 95% accurate. And it got – so it

783
00:54:08,869 --> 00:54:12,050
got to the point where it was just missing a

784
00:54:12,050 --> 00:54:14,679
few things every now and then. And what I did

785
00:54:14,679 --> 00:54:17,019
was – I'll tell you the process. I exported my

786
00:54:17,019 --> 00:54:20,320
entire subscription list of which there's a mix of –

787
00:54:20,320 --> 00:54:24,289
and I'm telling this story for a reason. There's a

788
00:54:24,289 --> 00:54:30,019
mix of – Just regular old run-of-the-mill podcasts and then

789
00:54:30,019 --> 00:54:34,320
private members-only podcasts that I pay for. So there's a

790
00:54:34,320 --> 00:54:38,250
mix of both. I export them out into an OPML

791
00:54:38,250 --> 00:54:42,789
file using handy dandy Cast-O-Matic. I throw it into the

792
00:54:42,789 --> 00:54:47,800
agent, and I'm like, all right, look – All the

793
00:54:47,800 --> 00:54:50,889
stuff I've been throwing at you now for this –

794
00:54:50,889 --> 00:54:54,760
up until this point, it's really good. It's really solid.

795
00:54:54,760 --> 00:54:57,250
Now I need to live with this thing on a

796
00:54:57,250 --> 00:55:03,329
daily basis. And so that I can start finding the

797
00:55:03,329 --> 00:55:06,739
edge cases. So that means what I want you to

798
00:55:06,739 --> 00:55:09,679
do is I want you to here's a here's an

799
00:55:09,679 --> 00:55:13,440
S3 bucket. Object storage bucket, I want you to make

800
00:55:13,440 --> 00:55:16,440
a feed, and I want you to start looking for

801
00:55:16,440 --> 00:55:19,889
new episodes. Anytime a new episode comes in, run it

802
00:55:19,889 --> 00:55:24,940
through your new pipeline that we've got. So strip all

803
00:55:24,940 --> 00:55:29,940
the ads out, put a chapters file in that denotes

804
00:55:29,940 --> 00:55:35,159
the ad markers, and then I'm going to remove all

805
00:55:35,159 --> 00:55:39,000
the podcasts out of Cast-O-Matic and only subscribe to this

806
00:55:39,000 --> 00:55:43,900
one feed. So I'm essentially proxying my feed through the

807
00:55:43,900 --> 00:55:46,239
ad stripper now, all my feeds through the ad stripper.

808
00:55:46,300 --> 00:55:52,679
Okay. And then Castomatic has this awesome feature where you

809
00:55:52,679 --> 00:55:57,739
can put keywords or key phrases into it. A chap

810
00:55:57,739 --> 00:56:01,190
into a list, and if any of the chapters contain

811
00:56:01,190 --> 00:56:05,880
that word or phrase, it will auto-skip the chapter. So

812
00:56:05,880 --> 00:56:08,170
in that way, I can just have – I can

813
00:56:08,170 --> 00:56:12,889
see just by looking at the chapters list what the

814
00:56:12,889 --> 00:56:17,170
tool thought the ad markers were. And I can and

815
00:56:17,170 --> 00:56:19,460
I can just play it. And if I ever hear

816
00:56:19,460 --> 00:56:22,309
an ad leak through, I'll I'll be like, ah, you

817
00:56:22,309 --> 00:56:25,710
missed one. That makes total sense. Yeah. So this is

818
00:56:25,710 --> 00:56:27,970
now my process. And I've been living with it for

819
00:56:27,970 --> 00:56:33,980
a few days. This thing has effed up. so much.

820
00:56:34,779 --> 00:56:37,760
Like, I'm not talking about the ad stripping part. That

821
00:56:37,760 --> 00:56:41,139
part was already fairly robust. No, it's stripping bits you

822
00:56:41,139 --> 00:56:44,159
actually want to hear, likely. No, no, no. It just

823
00:56:44,159 --> 00:56:48,059
can't get the feed stuff right. It keeps messing up.

824
00:56:48,059 --> 00:56:54,239
The processes are crashing. FFmpeg is crashing. Hmm. Runaway processes.

825
00:56:54,239 --> 00:56:57,980
It's putting weird things into the RSS feed. They're invalid.

826
00:56:58,920 --> 00:57:01,980
The last three days, I've had to go back to

827
00:57:01,980 --> 00:57:05,309
it four or five times and say, look, you know,

828
00:57:05,309 --> 00:57:10,070
I'm not getting new episodes. And it'll, you know, chug

829
00:57:10,070 --> 00:57:13,320
along and say, oh, yeah, you know, yeah, here's –

830
00:57:13,470 --> 00:57:16,110
There's error in my script. I've updated it. I've fixed

831
00:57:16,110 --> 00:57:19,090
it. Are you running this on Quinn, or what's the

832
00:57:19,090 --> 00:57:22,559
model you're using for this? No, it's Oculus 5.5. Huh,

833
00:57:22,559 --> 00:57:26,860
okay. We've got very different results. That's interesting. Well, this

834
00:57:26,860 --> 00:57:29,090
is also a different result than I've had in the

835
00:57:29,090 --> 00:57:34,260
past with doing stuff like this. And it's also not

836
00:57:34,260 --> 00:57:38,400
– consistent with the results I just had using Claude

837
00:57:38,400 --> 00:57:44,539
to do these server migrations. So, The reason I laid

838
00:57:44,539 --> 00:57:49,369
all that out is because – If even one –

839
00:57:49,369 --> 00:57:53,940
all it takes is one of these points of friction.

840
00:57:56,010 --> 00:58:00,500
And you lose a person entirely because they just don't

841
00:58:00,500 --> 00:58:04,210
even know what could possibly be wrong because they don't

842
00:58:04,210 --> 00:58:07,029
understand any of this stuff already. And if it all

843
00:58:07,029 --> 00:58:13,989
goes well and you one-shot everything, it's magic. If one

844
00:58:13,989 --> 00:58:19,599
thing drops… And they're completely lost, and they've got better

845
00:58:19,599 --> 00:58:22,710
things to do with their time. And I think that

846
00:58:22,710 --> 00:58:26,550
is the sense in which I agree with what they're

847
00:58:26,550 --> 00:58:32,260
saying. But I don't think it's an either or. I

848
00:58:32,260 --> 00:58:37,909
think they are – I think there's – I think

849
00:58:37,909 --> 00:58:42,820
they're expressing an understanding of human nature that makes sense.

850
00:58:43,440 --> 00:58:49,170
But I also think that what you're saying – If

851
00:58:49,170 --> 00:58:52,980
the trend continues in the way that it is going,

852
00:58:53,500 --> 00:58:55,829
It's not going to be 10 years before stuff like

853
00:58:55,829 --> 00:58:58,220
this might be possible, but it's not – I don't

854
00:58:58,220 --> 00:59:00,279
know that it will necessarily be in 10 months either.

855
00:59:00,279 --> 00:59:02,269
I mean I think the timeframe may be a little

856
00:59:02,269 --> 00:59:05,360
bit longer. Well, why don't you send me your OPML

857
00:59:05,360 --> 00:59:07,650
list and let's see if I can give that a

858
00:59:07,650 --> 00:59:13,869
shot. Let's see. You may be overthinking it, actually, to

859
00:59:13,869 --> 00:59:18,279
be honest. I don't think so. I mean, I'm pretty

860
00:59:18,279 --> 00:59:22,099
good with this stuff. You're no good, Dave Jones. I

861
00:59:22,099 --> 00:59:29,940
guess not. Is this it? Subscriptions.opml. Yeah. Let's see. So

862
00:59:29,940 --> 00:59:37,789
you also want in-show sponsorship messages skipped? Oh, now are

863
00:59:37,789 --> 00:59:40,010
you – what are you trying to do? Cut the

864
00:59:40,010 --> 00:59:41,599
ads out or are you trying to – Well, that's

865
00:59:41,599 --> 00:59:45,010
what you're building. Is that what you're building? Yeah, but

866
00:59:45,010 --> 00:59:47,739
all that stuff – see, that's the thing. That part

867
00:59:47,739 --> 00:59:51,380
of it works. Oh, just the regular mechanics that you

868
00:59:51,380 --> 00:59:55,500
have problems with. It's the stuff that this thing has

869
00:59:55,500 --> 00:59:59,940
struggled with. Huh, that's interesting. Is the –

870
01:00:00,030 --> 01:00:07,000
is the basics of podcasting. Wow. How to... And it's

871
01:00:07,000 --> 01:00:09,019
like – because one thing I said was like keep

872
01:00:09,019 --> 01:00:10,960
the show art so I can tell the episodes apart.

873
01:00:12,579 --> 01:00:14,340
I had to go two or three times to get

874
01:00:14,340 --> 01:00:18,940
it right. It may be because my own – Corpus

875
01:00:18,940 --> 01:00:22,159
of information is so filled with this stuff that I've

876
01:00:22,159 --> 01:00:25,420
just trained it over two years time and it knows

877
01:00:25,420 --> 01:00:31,059
enough. It's possible. I don't know. Yeah, I guess. Yeah.

878
01:00:31,760 --> 01:00:38,440
Interesting. Okay, so the disagreement here is on the actual,

879
01:00:38,440 --> 01:00:41,690
so even though it can patch servers and do everything

880
01:00:41,690 --> 01:00:45,409
great, it's like some real basic RSS functionality it's struggling

881
01:00:45,409 --> 01:00:48,960
with in your instance. And so that's why it may

882
01:00:48,960 --> 01:00:56,510
not happen that fast. Yeah, and I think this sort

883
01:00:56,510 --> 01:01:05,400
of mirrors my experience with this stuff in general is

884
01:01:05,400 --> 01:01:09,869
that – And you get from time to time, you

885
01:01:09,869 --> 01:01:14,179
can just get wildly different results. And I don't know

886
01:01:14,179 --> 01:01:20,000
if it's because – The model providers end up sort

887
01:01:20,000 --> 01:01:23,599
of like – Having a stupid model problem for a

888
01:01:23,599 --> 01:01:26,900
while because I have – they do redirect inference to

889
01:01:26,900 --> 01:01:30,650
training sometimes, and the models get stupider for a period

890
01:01:30,650 --> 01:01:33,739
of time. So things like that do happen, and I

891
01:01:33,739 --> 01:01:36,630
don't know if this is just like an example of

892
01:01:36,630 --> 01:01:40,400
that. Could be. It could be. Well, that's a very

893
01:01:40,400 --> 01:01:44,829
different experience than I have. Yeah, like I said, it's

894
01:01:44,829 --> 01:01:47,389
a different experience than I've had. Yeah. I can go

895
01:01:47,389 --> 01:01:51,610
from – that's the thing. The inconsistency is a real

896
01:01:51,610 --> 01:01:54,610
problem because you can go from – you can have

897
01:01:54,610 --> 01:01:57,880
one day this thing just blows your mind, and the

898
01:01:57,880 --> 01:02:00,679
next day you're like, man, how did you miss that?

899
01:02:01,599 --> 01:02:06,889
Yeah. Yeah. Yeah, no, I, okay, fair, fair point. I

900
01:02:06,889 --> 01:02:11,210
just haven't had that experience. My experience is, first of

901
01:02:11,210 --> 01:02:15,309
all, help me fix my start nine server. Okay, hook

902
01:02:15,309 --> 01:02:19,739
it up to tail scale. Let me root around. Okay.

903
01:02:20,079 --> 01:02:22,039
I got it. Here's what you got to do. You

904
01:02:22,039 --> 01:02:24,179
definitely want to back these things up because that could

905
01:02:24,179 --> 01:02:27,059
break. And so we went to a big release 4.0,

906
01:02:27,059 --> 01:02:31,039
which has a wire mesh and all kinds of stuff

907
01:02:31,039 --> 01:02:33,239
in it. But I'm just going to use tail scale.

908
01:02:34,039 --> 01:02:37,159
And I said, you know, I'm so tired of... You

909
01:02:37,159 --> 01:02:40,809
know, on my phone, like opening up through Tor, start

910
01:02:40,809 --> 01:02:44,519
nine and then going to Albi Hub. Just give me

911
01:02:44,519 --> 01:02:47,599
an app that has Albi Hub, Helipad, you know, these

912
01:02:47,599 --> 01:02:51,150
five apps. And it did it. And, you know, out

913
01:02:51,150 --> 01:02:54,980
of the box, worked perfectly. uh, you know, exactly what

914
01:02:54,980 --> 01:02:57,409
I want. I can check my Albi wallet. I can

915
01:02:57,409 --> 01:03:00,519
check my helipad at any time within seconds on my

916
01:03:00,519 --> 01:03:06,199
phone. It's just, you know, so that, okay. Yeah. I'm

917
01:03:06,199 --> 01:03:10,480
not Jean's mom. Cause she's dead, but, um, I know

918
01:03:10,480 --> 01:03:14,760
Jean's laughing. Um, um, But we are so close to

919
01:03:14,760 --> 01:03:18,059
this. And then you know that Gemini is going to

920
01:03:18,059 --> 01:03:22,219
be completely integrated throughout the phone. Throughout the phone. It

921
01:03:22,219 --> 01:03:26,860
already is. With the Play Store for Buddies, you know,

922
01:03:26,860 --> 01:03:30,360
your Barbie Play Store that you can share your little

923
01:03:30,360 --> 01:03:33,780
vibe-coded apps with. What will be interesting is... What will

924
01:03:33,780 --> 01:03:38,219
Apple's response be? Because those guys like to control the

925
01:03:38,219 --> 01:03:42,449
experience. What will anyone's response be? What will our own

926
01:03:42,449 --> 01:03:45,559
app developer's response be? I mean, there is so much

927
01:03:45,559 --> 01:03:50,619
going on. My mind is boggled. I get this. You

928
01:03:50,619 --> 01:03:58,809
seem boggled. Yeah. With excitement, really. Yeah. So once he

929
01:03:58,809 --> 01:04:06,039
talked about friction, he said that consumers – that word

930
01:04:06,039 --> 01:04:12,760
bothers me. People who buy stuff? Yeah. Consumers don't like

931
01:04:12,760 --> 01:04:20,380
friction. Yeah. I don't necessarily disagree. But we've forgotten what

932
01:04:20,380 --> 01:04:24,139
friction we actually go through. The friction we have with

933
01:04:24,139 --> 01:04:30,090
interfaces. This is why Omarchi was interesting. I'm getting everything

934
01:04:30,090 --> 01:04:32,920
out of the way. All the stuff that was friction

935
01:04:32,920 --> 01:04:35,949
in your life, but I'm now removing. And you don't

936
01:04:35,949 --> 01:04:38,340
like it? Tell your robot to fix it for you

937
01:04:38,340 --> 01:04:42,019
right here in the operating system. You know what friction

938
01:04:42,019 --> 01:04:47,909
is? 50% ad load. Yeah, well, yeah. But that's not

939
01:04:47,909 --> 01:04:51,300
the biggest friction. But, yeah, I think the friction is

940
01:04:51,300 --> 01:04:54,039
look at this inbox. Look at all these unlistened to

941
01:04:54,039 --> 01:04:57,230
episodes. Oh, my Lord. You know, my robot's like, hey,

942
01:04:57,230 --> 01:04:59,940
Adam, you're driving to Austin. Hey, here's a couple of

943
01:04:59,940 --> 01:05:03,019
podcasts that will fit that hour and 20 minutes perfectly.

944
01:05:03,500 --> 01:05:04,659
You want to listen to this, this and this or

945
01:05:04,659 --> 01:05:08,360
this, this and this? Well, James in the most recent

946
01:05:08,360 --> 01:05:11,119
episode said he did not cover a podcast app because

947
01:05:11,119 --> 01:05:16,360
it was an ad skipper. It's virtue signaling. Maybe. I

948
01:05:16,360 --> 01:05:23,460
don't know. You've been cricklered. But the – You know,

949
01:05:23,460 --> 01:05:30,730
the thing about it is the – We all understand,

950
01:05:30,730 --> 01:05:34,199
and he said in that episode, and that's his prerogative.

951
01:05:34,500 --> 01:05:36,119
Of course. It belongs to him. Of course. It belongs

952
01:05:36,119 --> 01:05:37,470
to him. He can do it every one. I'm fine

953
01:05:37,470 --> 01:05:41,679
with that. But he said in that episode that we

954
01:05:41,679 --> 01:05:45,110
all – he said that we all know that the

955
01:05:45,110 --> 01:05:52,029
podcast advertising – The agencies and the advertising complex doesn't

956
01:05:52,029 --> 01:05:57,279
give a shit about independent podcast apps. They don't. They

957
01:05:57,279 --> 01:05:59,829
don't. And he said he went one step further and

958
01:05:59,829 --> 01:06:02,440
said, as a matter of fact, they don't just they

959
01:06:02,440 --> 01:06:06,480
don't just not care. They would like it to just

960
01:06:06,480 --> 01:06:11,590
be. Apple, Google, excuse me, Apple, Spotify, and YouTube. They

961
01:06:11,590 --> 01:06:14,440
would love that because that simplifies the stuff they have

962
01:06:14,440 --> 01:06:17,409
to do. But this is the beauty. This is what

963
01:06:17,409 --> 01:06:19,980
– and I'm sorry for app developers. I love all

964
01:06:19,980 --> 01:06:22,750
of you. You know that. Everyone complained, well, the app

965
01:06:22,750 --> 01:06:25,159
developers get no money. Guess who also gets no money?

966
01:06:26,279 --> 01:06:28,019
Dave Jones gets no money. Dave Jones gets no money.

967
01:06:28,679 --> 01:06:30,269
You know, we are so I heard I had to

968
01:06:30,269 --> 01:06:33,900
hear on on power that we're celebrating our sixth anniversary.

969
01:06:34,019 --> 01:06:37,139
I didn't even know it. Happy anniversary. Happy anniversary. Yeah.

970
01:06:37,139 --> 01:06:41,880
Happy anniversary. So the index. We only have the money

971
01:06:41,880 --> 01:06:45,429
to keep the index running if the biggest hosting company

972
01:06:45,429 --> 01:06:51,400
stops supporting us. And we could probably eek by, but

973
01:06:51,400 --> 01:06:55,989
I don't think we make $800 a month from the

974
01:06:55,989 --> 01:07:01,940
smaller donations. We might have to – what? I'm sorry?

975
01:07:02,119 --> 01:07:04,239
No. No. So, you know, we'd have to kind of

976
01:07:04,239 --> 01:07:06,720
throttle stuff. So we don't make any money either, you

977
01:07:06,720 --> 01:07:13,059
know. So – and 22,000 accounts are using the API.

978
01:07:13,760 --> 01:07:17,529
Apple, Microsoft, Google, do they support us? No. No. Free

979
01:07:17,529 --> 01:07:24,349
loaders. Free loaders. You know, so – So I'm speaking

980
01:07:24,349 --> 01:07:30,289
on behalf of Podcast Index, and I am delighted, delighted

981
01:07:30,289 --> 01:07:35,849
that the power is going to leak like green sludge

982
01:07:35,849 --> 01:07:42,010
away from Apple and away from Spotify because people will

983
01:07:42,010 --> 01:07:45,920
start to figure this out. I don't need to. And

984
01:07:45,920 --> 01:07:49,720
this is why RSS is so open. Open RSS. It

985
01:07:49,720 --> 01:07:53,179
is fantastic. You know, this guy was talking about liquid

986
01:07:53,179 --> 01:07:58,820
content, this professor. Yeah, we're doing it all wrong. Yeah,

987
01:07:58,820 --> 01:08:01,480
your content should be everywhere. So I'm going to use

988
01:08:01,480 --> 01:08:06,800
everybody's API and upload to every stupid platform everywhere where

989
01:08:06,800 --> 01:08:11,130
the inverse is the right way. One feed, I control

990
01:08:11,130 --> 01:08:16,170
it. Anybody can ingest that. That's the system. That's the

991
01:08:16,170 --> 01:08:19,989
system that is coming back to us now. This is

992
01:08:19,989 --> 01:08:29,479
why I'm excited. Well, if... I agree with you. It's

993
01:08:29,479 --> 01:08:37,309
RSS – RSS is the backbone of everything in the

994
01:08:37,309 --> 01:08:44,210
podcast, in the independent app world. And anything that bolsters

995
01:08:44,210 --> 01:08:52,630
that strengthens apps just by default. But, you know... I

996
01:08:52,630 --> 01:08:57,279
guess maybe from the outside I seem like irrationally hung

997
01:08:57,279 --> 01:09:01,800
up on this advertising thing. Like – but I feel

998
01:09:01,800 --> 01:09:09,140
like – If the advertising industry does not care anything

999
01:09:09,140 --> 01:09:12,239
about independent podcast apps, and I can tell you from

1000
01:09:12,239 --> 01:09:18,800
firsthand experience, they do not. And if that's the case,

1001
01:09:19,729 --> 01:09:23,420
Then why does it matter? Why does it matter if

1002
01:09:23,420 --> 01:09:25,930
you strip ads or not? If they don't give a

1003
01:09:25,930 --> 01:09:31,869
crap about doing anything to help independent podcast apps flourish,

1004
01:09:31,869 --> 01:09:36,119
and all they care about is YouTube, Apple, and Spotify,

1005
01:09:36,119 --> 01:09:38,600
then they're not going to do it. Then get rid

1006
01:09:38,600 --> 01:09:42,199
of all the ads. And the argument could be –

1007
01:09:42,199 --> 01:09:45,420
the argument from the other side is, well, if you

1008
01:09:45,420 --> 01:09:49,489
get rid of the ads, you're hurting creators. The advertising

1009
01:09:49,489 --> 01:09:53,569
industry doesn't give a shit about creators either. And welcome

1010
01:09:53,569 --> 01:09:56,779
to the new world. A minimum of 10,000 downloads to

1011
01:09:56,779 --> 01:10:00,140
even qualify? Welcome to the doom loop. This is the

1012
01:10:00,140 --> 01:10:04,789
entire problem with agents in general. Agents are giving you

1013
01:10:04,789 --> 01:10:08,279
news that they are pulling from the literal sources –

1014
01:10:08,409 --> 01:10:10,720
That give them the news in the first place. They've

1015
01:10:10,720 --> 01:10:14,440
admitted this privately in emails that came out like, hey,

1016
01:10:14,440 --> 01:10:16,359
we're sucking all this stuff out of the New York

1017
01:10:16,359 --> 01:10:18,579
Times. They're going to go broken. We won't have any

1018
01:10:18,579 --> 01:10:25,770
news. It's unavoidable. It is. It is completely unavoidable. Because

1019
01:10:25,770 --> 01:10:28,090
we have the power. We have to come up with

1020
01:10:28,090 --> 01:10:32,940
entirely new ways of news gathering, news distribution. Everything has

1021
01:10:32,940 --> 01:10:35,989
to be rethought. Everything. And this is what I find

1022
01:10:35,989 --> 01:10:44,729
exciting because in chaos, there's always opportunity. I was... I

1023
01:10:44,729 --> 01:10:47,539
was struck by one of the things that they were

1024
01:10:47,539 --> 01:10:50,710
talking about on Power, which is the funding tag. And

1025
01:10:50,710 --> 01:10:56,670
how Spotify's recent announcement, they just showed off opening up

1026
01:10:56,670 --> 01:11:01,399
a web view in the app and paying attention. And

1027
01:11:01,399 --> 01:11:04,949
so I think that they're right. That should be a

1028
01:11:04,949 --> 01:11:07,880
signal to everybody. Don't be afraid to put this in

1029
01:11:07,880 --> 01:11:14,460
your apps. Open the funding tag. That's your solution. The

1030
01:11:14,460 --> 01:11:19,420
solution is not to clutch to advertising into dynamic ad

1031
01:11:19,420 --> 01:11:25,239
insertion with your fingernails as it's pulled away from you.

1032
01:11:26,420 --> 01:11:29,340
The solution is put the funding tag in your app

1033
01:11:29,340 --> 01:11:33,050
and tell your audience in the episode, please go and

1034
01:11:33,050 --> 01:11:36,550
donate. And please support us because if you don't, we

1035
01:11:36,550 --> 01:11:37,960
won't be able to eat and we won't be able

1036
01:11:37,960 --> 01:11:40,489
to do this show anymore. That's just the way that

1037
01:11:40,489 --> 01:11:45,590
it always works. Well, you know, the ultimate solution, funny

1038
01:11:45,590 --> 01:11:49,750
enough, is for the apps to start selling ads. There

1039
01:11:49,750 --> 01:11:54,739
you go. They get blamed anyway. Well, Overcast does. He

1040
01:11:54,739 --> 01:11:56,800
sells ads right in the app. Yeah, but not in

1041
01:11:56,800 --> 01:12:01,180
the content. There's not like a pre-roll or a post-roll.

1042
01:12:01,800 --> 01:12:05,000
Like a banner on the thing or whatever. Yeah. Yep.

1043
01:12:06,020 --> 01:12:10,079
I mean, I don't really have an answer. I just

1044
01:12:10,079 --> 01:12:13,630
want to get it out there. I remember when podcasting

1045
01:12:13,630 --> 01:12:16,649
first started, I had the same excitement. I didn't know

1046
01:12:16,649 --> 01:12:20,059
exactly what was going to happen. And the professor, by

1047
01:12:20,059 --> 01:12:22,390
the way, is pretty funny. You know, when podcasting first

1048
01:12:22,390 --> 01:12:26,529
started, it was deep thoughts. People were doing deep dives,

1049
01:12:26,529 --> 01:12:28,909
deep thinking. Like, no, we weren't. We had Don and

1050
01:12:28,909 --> 01:12:31,680
Drew talking about their life in a farmhouse, you klutz.

1051
01:12:32,159 --> 01:12:35,680
We had Michael Butler, the rock and roll geek, drinking

1052
01:12:35,680 --> 01:12:39,199
a six-pack, talking about how shitty the gig was. That's

1053
01:12:39,199 --> 01:12:43,659
what made it awesome. Not the deep thinkers. You've always,

1054
01:12:43,840 --> 01:12:47,659
you've made, I heard this the other day. I heard

1055
01:12:47,659 --> 01:12:49,699
a perfect example and I was telling a friend of

1056
01:12:49,699 --> 01:12:53,720
mine, I was like, I was like, Adam always says,

1057
01:12:53,720 --> 01:12:58,109
has always said that people say things on podcasts that

1058
01:12:58,109 --> 01:13:01,579
they would never say in mainstream media. For sure. Because

1059
01:13:01,579 --> 01:13:05,670
they think that it's somehow like a secret club. Not

1060
01:13:05,670 --> 01:13:09,229
very many people listen to it. But when in reality,

1061
01:13:09,229 --> 01:13:13,750
the listenership of podcasts way outstrips broadcast media now. Sure

1062
01:13:13,750 --> 01:13:16,609
does. But they still think that it's some sort of

1063
01:13:16,609 --> 01:13:21,960
like kind of off the record. And it's hilarious. And

1064
01:13:21,960 --> 01:13:24,590
that's kind of what podcasts – but I think it's

1065
01:13:24,590 --> 01:13:26,319
because it goes back to the early days of podcasting

1066
01:13:26,319 --> 01:13:28,699
when it kind of was off the record because it

1067
01:13:28,699 --> 01:13:30,890
was so small. And people could say – they could

1068
01:13:30,890 --> 01:13:32,989
get away with saying something on a podcast. They wouldn't

1069
01:13:32,989 --> 01:13:35,119
say it everywhere else. So everybody wanted to go listen

1070
01:13:35,119 --> 01:13:43,199
to podcasts to get the real dope. Yes. Our worlds

1071
01:13:43,199 --> 01:13:47,350
are about to be rocked. And so everything has to

1072
01:13:47,350 --> 01:13:53,039
be rethought, everything. And I could not be more delighted.

1073
01:13:53,739 --> 01:13:56,100
It is, you know how they were like, we got

1074
01:13:56,100 --> 01:13:58,859
to slow it down. We got to slow down development.

1075
01:13:59,359 --> 01:14:02,440
We can kill the whole world. 10% will be white.

1076
01:14:02,579 --> 01:14:05,729
No, they realized a little bit before I did that

1077
01:14:05,729 --> 01:14:10,059
they are in trouble. Nobody needs them anymore. The horse

1078
01:14:10,059 --> 01:14:13,859
is out of the barn. The train has left the

1079
01:14:13,859 --> 01:14:21,479
station. The revolution. Viva la revolution! It's here. It's here.

1080
01:14:21,760 --> 01:14:25,399
Huh. We can't use BitChat in our burning down buildings

1081
01:14:25,399 --> 01:14:28,880
protests in France. No problem. I'll just vibe code or

1082
01:14:28,880 --> 01:14:32,319
give it to my buddies. We'll use Bluetooth. You can

1083
01:14:32,319 --> 01:14:36,750
go ahead and take it off. Who needs Venmo? You

1084
01:14:36,750 --> 01:14:40,920
watch This is going to be an amazing time. I

1085
01:14:40,920 --> 01:14:48,029
wish I was 20 years younger. See, I just... I

1086
01:14:48,029 --> 01:14:50,559
can't. I can't. I can't. I can't. I can't go

1087
01:14:50,559 --> 01:14:53,440
there. I can't go there. I can't go there because

1088
01:14:53,440 --> 01:14:58,380
I just go there. There's the cynic inside of me.

1089
01:14:58,380 --> 01:14:59,960
What is this? I mean, I'm.

1090
01:15:00,000 --> 01:15:01,630
I'm interested in the cynic inside of you. It's why

1091
01:15:01,630 --> 01:15:03,640
we're such a great, we have such a great partnership.

1092
01:15:05,399 --> 01:15:11,210
Yeah. My cynical side just looks at every – It

1093
01:15:11,210 --> 01:15:13,829
looks at all the other times I've gotten excited about

1094
01:15:13,829 --> 01:15:17,529
the future that a technology promises and how every time

1095
01:15:17,529 --> 01:15:26,430
my hopes have been crushed. Yeah. Remember when, quote, programmable

1096
01:15:26,430 --> 01:15:29,920
money was going to free the world? Yeah. No. It

1097
01:15:29,920 --> 01:15:33,779
was – No. Well, the jury's still out on that.

1098
01:15:33,899 --> 01:15:38,039
I mean, the forces behind money are vast. There's a

1099
01:15:38,039 --> 01:15:42,380
clip that I played on this show – of Obama

1100
01:15:42,380 --> 01:15:48,100
from 2012 When he said something to the effect of

1101
01:15:48,100 --> 01:15:52,479
it was like a commencement speech and he said the

1102
01:15:52,479 --> 01:15:57,180
idea that you can regulate speech on the internet is

1103
01:15:57,180 --> 01:16:03,920
crazy or something like that. And... And then just a

1104
01:16:03,920 --> 01:16:07,050
few years later, what are we doing? Regulating speech on

1105
01:16:07,050 --> 01:16:10,119
the internet. I mean, like, it was – that was

1106
01:16:10,119 --> 01:16:13,520
– he said that during the time of like Aaron

1107
01:16:13,520 --> 01:16:18,180
Schwartz and all that stuff going on. And then everybody's

1108
01:16:18,180 --> 01:16:21,899
like, yeah, yeah, I'm going to change my Twitter avatar

1109
01:16:21,899 --> 01:16:29,250
to be black. Yeah. you know to protest there you

1110
01:16:29,250 --> 01:16:32,350
go 2012 I think this is it I know that

1111
01:16:32,350 --> 01:16:36,119
not all countries in this body share this particular understanding

1112
01:16:36,119 --> 01:16:39,239
of the protection of free speech we recognize that but

1113
01:16:39,239 --> 01:16:44,420
in 2012 at a time when anyone with a cell

1114
01:16:44,420 --> 01:16:48,189
phone can spread offensive views around the world with a

1115
01:16:48,189 --> 01:16:51,020
click of a button. The notion that we can control

1116
01:16:51,020 --> 01:16:56,720
the flow of information is obsolete. Yeah, and what did

1117
01:16:56,720 --> 01:17:00,020
they try to do immediately is control the flow of

1118
01:17:00,020 --> 01:17:03,810
information, and they're doing it. Well, but they're going to,

1119
01:17:03,810 --> 01:17:06,430
that's okay. Yeah. But I, I still believe in the

1120
01:17:06,430 --> 01:17:15,159
core network protocol. I mean, I think some things. DHT.

1121
01:17:15,539 --> 01:17:18,729
There's so many different ways to get around. We just,

1122
01:17:18,729 --> 01:17:21,439
this is my job. My job is to be early.

1123
01:17:21,560 --> 01:17:24,430
My job is to see the possibilities, to stick it

1124
01:17:24,430 --> 01:17:30,880
together with Scotch tape and Elmer's glue. and see if

1125
01:17:30,880 --> 01:17:32,529
it takes off. And a lot of things just say

1126
01:17:32,529 --> 01:17:36,119
balls of scotch tape and Elmer's glue. But this time,

1127
01:17:36,119 --> 01:17:40,300
I think there's something here. And it's all about what

1128
01:17:40,300 --> 01:17:46,420
people are trained to think. And we've been very trained

1129
01:17:46,420 --> 01:17:53,050
to... use the systems devices applications etc the way they've

1130
01:17:53,050 --> 01:17:57,890
been handed down to us whoa that's my daughter hold

1131
01:17:57,890 --> 01:18:01,439
on a second hold on yeah you need to get

1132
01:18:01,439 --> 01:18:03,560
it yeah hey babe can i call you right back

1133
01:18:04,960 --> 01:18:09,600
Uh, sure. Yeah, I'm doing the podcast with Dave. Oh.

1134
01:18:10,300 --> 01:18:18,609
Yeah. Yeah. Well, 10 minutes. And that's good. Okay. Love

1135
01:18:18,609 --> 01:18:23,350
you. All right. Bye. Bye. Love you, too. It's grandbaby

1136
01:18:23,350 --> 01:18:27,510
time. Let's show off the grandbaby. Yeah. Fire up the

1137
01:18:27,510 --> 01:18:31,890
screen. Hold her up. Exactly right. All right. We can

1138
01:18:31,890 --> 01:18:32,920
thank some people so you can get out and see

1139
01:18:32,920 --> 01:18:36,750
your grandbaby. Well, thank you. Let's see. We have –

1140
01:18:36,750 --> 01:18:40,279
and everything's working again. I got the Start9 working. It's

1141
01:18:40,279 --> 01:18:42,859
beautiful. Thank you very much. I think Eric PP has

1142
01:18:42,859 --> 01:18:46,119
a monster channel open to me. I love it. Thank

1143
01:18:46,119 --> 01:18:52,000
you, brother. 777 sats from Sam over there at TrueFans.

1144
01:18:52,500 --> 01:18:54,710
He says, I don't disagree with Adam. Maybe the future

1145
01:18:54,710 --> 01:18:57,640
is personalized apps that tailor the experience to you, but

1146
01:18:57,640 --> 01:19:00,000
we have all seen the initial hype around new technology.

1147
01:19:00,000 --> 01:19:02,529
Oh, geez. I need your camp. And the subsequent time

1148
01:19:02,529 --> 01:19:06,199
lapse before mass adoption. This is Jeffrey Moores crossing the

1149
01:19:06,199 --> 01:19:10,020
chasm. Yes. I like that. This is a book. Is

1150
01:19:10,020 --> 01:19:13,960
that a book? Crossing the Cousin? Yeah. Yeah. Okay. Three

1151
01:19:13,960 --> 01:19:19,399
threes from Eric PP. Hashtag release the code. What code

1152
01:19:19,399 --> 01:19:22,010
do you want me to release? I'm happy to release

1153
01:19:22,010 --> 01:19:24,920
it. All of it. Release the code. Release the code.

1154
01:19:25,039 --> 01:19:28,729
Okay. 1701 from Martin Lindeskog. Adam, here's a new word

1155
01:19:28,729 --> 01:19:32,489
to pronounce. pronounced in Danish and Swedish. Orisund, Orisund, Orisund

1156
01:19:32,489 --> 01:19:36,180
and Orisund. It is our new hyperlocal podcast, Orisund 360.

1157
01:19:36,840 --> 01:19:40,039
Hosted on TrueFans.fm. Dave, thanks for the help with Podcast

1158
01:19:40,039 --> 01:19:47,159
Index. Starship Boostergram, 1701 Satoshis. 3,333 from Eric PP. From

1159
01:19:47,159 --> 01:19:52,119
Boost Me Bitch, it works. 1276 from Salty Crayon. In

1160
01:19:52,119 --> 01:19:54,670
the boardroom, Adam, talk about podcasts. An idea for Dana,

1161
01:19:54,670 --> 01:19:57,550
Dana Brunetti, after the 29th. A podcast where he just

1162
01:19:57,550 --> 01:19:59,939
talks about... talks, and leaves all the bathroom breaks in.

1163
01:20:00,039 --> 01:20:02,539
Call it gummies and dog farts. All fun, of course.

1164
01:20:03,140 --> 01:20:05,779
I don't know about that name, but that would be

1165
01:20:05,779 --> 01:20:07,979
a fun podcast. Very relevant to the show we did

1166
01:20:07,979 --> 01:20:12,300
yesterday. Salty Crayon, again, with Triple Threes. Is this thing

1167
01:20:12,300 --> 01:20:15,689
working? Why are you roughing? And there's Comics Your Blogger

1168
01:20:15,689 --> 01:20:19,560
with a delimiter. So you're up, my brother. Why you

1169
01:20:19,560 --> 01:20:27,380
are laughing? I fixed my AIFF problem. Don't laugh. Why

1170
01:20:27,380 --> 01:20:34,439
you are laughing? Shut up. Shut up. Yes. Shut up.

1171
01:20:35,100 --> 01:20:40,060
I fixed it. I fixed it. Nice. The consensus is

1172
01:20:40,060 --> 01:20:43,050
the Currycaster 2 is what they want released. Yeah, I

1173
01:20:43,050 --> 01:20:45,779
shall release the Currycaster 2. I will release it, of

1174
01:20:45,779 --> 01:20:51,130
course. Call it the Kraken. Although I already had... I

1175
01:20:51,130 --> 01:20:54,659
forget who it was. Buddy, buddy, buddy, buddy. He says,

1176
01:20:54,659 --> 01:20:58,079
hey, man, I took inspiration from you and vibe-coded a

1177
01:20:58,079 --> 01:21:02,380
curry caster for video based on what you built. It

1178
01:21:02,380 --> 01:21:06,239
looked the same. It's the same thing with video. He

1179
01:21:06,239 --> 01:21:08,649
just took a picture and built this for me with

1180
01:21:08,649 --> 01:21:12,920
video. Okay. Yeah, but we can't do an RSS feed.

1181
01:21:16,960 --> 01:21:21,170
Here's some PayPals. Cohen Glatzbach, $5. Thank you. Appreciate you,

1182
01:21:21,170 --> 01:21:26,100
brother. Christopher Reamer, $10. Thank you, Christopher. James Sullivan. Hey,

1183
01:21:26,100 --> 01:21:32,399
James, $10. Jorge Hernandez, $5. Jorge Hernandez, been around forever.

1184
01:21:32,859 --> 01:21:35,930
Yep, Michael Goggin, $5. Thank you, Michael. And just a

1185
01:21:35,930 --> 01:21:40,640
little bit of something extra from Buzzsprout, $1,000. Baller, shot

1186
01:21:40,640 --> 01:21:45,220
caller, 20-inch blades on the Impala. Thank you, thank you,

1187
01:21:45,220 --> 01:21:49,649
thank you. Thank you, thank you, thank you. Tom. Tom

1188
01:21:49,649 --> 01:21:52,140
Rossi texted me last night. He's like, you okay? You

1189
01:21:52,140 --> 01:21:55,560
alive? Oh, sure. Well, he knows. He understands. He gets

1190
01:21:55,560 --> 01:22:03,819
it. The, yeah, let's see. PHpocalypse. Yes. What was that?

1191
01:22:03,880 --> 01:22:07,250
What was that? Flawlosophy? Yes. Yeah. It doesn't roll off

1192
01:22:07,250 --> 01:22:10,420
the tongue very easily. No, it's some reason I can.

1193
01:22:10,579 --> 01:22:13,800
Jack leg is better. Jack leg. Jack leg. Jack leg

1194
01:22:13,800 --> 01:22:18,609
is good. I got some true fans. Anonymous is flowing

1195
01:22:18,609 --> 01:22:23,569
in. 39 sats, 406 sats, 13, 220 sats. 7, 4,

1196
01:22:23,569 --> 01:22:28,659
0, 6, 13. Oh, we got a Dreb Scott. 774

1197
01:22:28,659 --> 01:22:33,989
sats. He says, anyone else? Wait. Why is this? Is

1198
01:22:33,989 --> 01:22:40,380
this old? What are you looking at? Uh... Maybe this

1199
01:22:40,380 --> 01:22:43,119
is old. I thought it just produced it. I don't

1200
01:22:43,119 --> 01:22:49,409
know. Let me check. Let's see here. Refresh. Am I

1201
01:22:49,409 --> 01:22:53,079
getting a cash? Uh-oh, uh-oh, we're in the cash. We're

1202
01:22:53,079 --> 01:23:00,420
in the cash, everybody. Sorry, I just... No, it's okay.

1203
01:23:01,000 --> 01:23:09,800
I just barfed. You do you, boo. 1023. 1023. Oh,

1204
01:23:09,800 --> 01:23:11,920
yeah. Okay. Here it is. Here it is. Yeah. Yeah.

1205
01:23:11,920 --> 01:23:13,979
I was I was looking at the wrong thing. Sorry.

1206
01:23:13,979 --> 01:23:20,439
Oh, there's Boobery. Okay. So Boobery. had a message lost

1207
01:23:20,439 --> 01:23:23,140
last week. Oh, no. It must have just been slow

1208
01:23:23,140 --> 01:23:25,210
coming in or something because it was not on my

1209
01:23:25,210 --> 01:23:28,760
list last week. But we did have some anonymous true

1210
01:23:28,760 --> 01:23:32,500
fans of 406 and 33. Then we got Blueberry. Blueberry.

1211
01:23:33,579 --> 01:23:40,300
Blueberry. The Fountain is $35,127. Woo! Bola! Yeah, baby! Chicago!

1212
01:23:40,298 --> 01:23:43,788
20-inch blades on the Impala. Yeah, we'll take it. We'll

1213
01:23:43,788 --> 01:23:45,800
take it. Thank you. That's why he wanted you to

1214
01:23:45,800 --> 01:23:47,440
make sure he got it because it was real money.

1215
01:23:47,539 --> 01:23:50,500
Yeah. Eric PP has given the split kit some major

1216
01:23:50,500 --> 01:23:54,750
upgrades this Saturday at 7 p.m. Central. We've been working

1217
01:23:54,750 --> 01:23:57,350
on bringing OSC and NDI to the table, and it

1218
01:23:57,350 --> 01:24:01,460
works now. What is OSC and NDI? I have no

1219
01:24:01,460 --> 01:24:05,859
idea. OSC and NDI. I don't know. Well, they put

1220
01:24:05,859 --> 01:24:08,460
them on the table and it works. Excellent. When we

1221
01:24:08,460 --> 01:24:14,680
stream live at www.pixelpalace.party, there are camera scenes that the

1222
01:24:14,680 --> 01:24:17,100
producer will be able to select and change live and

1223
01:24:17,100 --> 01:24:20,829
did not require a boost to trigger. Ooh. There's also

1224
01:24:20,829 --> 01:24:25,170
lighting cue stacks and triggered video content from SplitKit via

1225
01:24:25,170 --> 01:24:30,979
OSC. OSC and NDI have joined the battle. Nice. Okay.

1226
01:24:31,460 --> 01:24:33,920
Those must be some sort of like lighting and camera

1227
01:24:33,920 --> 01:24:39,550
things because Boobery, that's his – he was like a

1228
01:24:39,550 --> 01:24:43,260
– A lighting stage lighting guy. That was his job.

1229
01:24:43,260 --> 01:24:47,059
Yes, indeed. Yeah. I don't know what any of that

1230
01:24:47,059 --> 01:24:51,970
is, but it's awesome. anonymous from true fans 578 48

1231
01:24:51,970 --> 01:24:56,600
551 oh brian from podcast guru 551 says it's for

1232
01:24:56,600 --> 01:25:02,109
dave's buzz brian in fresno take your buzz get get

1233
01:25:02,109 --> 01:25:06,119
this though I have not touched that cable. It is

1234
01:25:06,119 --> 01:25:08,020
still routed the exact same way. Not a single buzz.

1235
01:25:08,020 --> 01:25:09,859
Not a single buzz. Now, I have an Echo, but

1236
01:25:09,859 --> 01:25:17,350
otherwise, great. Do I still have the Echo? Yeah. Yeah,

1237
01:25:17,350 --> 01:25:21,140
you do. Maybe it's the cable. Maybe it's manifesting itself

1238
01:25:21,140 --> 01:25:25,520
this week as an echo. Could be. User 940 blah,

1239
01:25:25,520 --> 01:25:30,460
blah, blah, blah at fountain.fm, 1,673 sats. Thank you, user

1240
01:25:30,460 --> 01:25:34,920
940 blah, blah, blah. And comment's your blogger, 10,556 sats.

1241
01:25:34,979 --> 01:25:38,850
There he is. Howdy, Dave and Adam. Despite knowing that

1242
01:25:38,850 --> 01:25:42,489
I am agnostic, Adam's pastor has followed me on x.com,

1243
01:25:42,489 --> 01:25:45,470
so I have reciprocated his follow. And as thank you,

1244
01:25:45,470 --> 01:25:49,920
I would like to recommend, please follow at Jimmy Pruitt

1245
01:25:49,920 --> 01:25:52,710
on x. And by the way, Adam, tell your robots

1246
01:25:52,710 --> 01:25:56,069
to add Podcasting 2.0 chapters to your podcast with the

1247
01:25:56,069 --> 01:26:04,029
pastor. Yo, CSB, Disgram. was $15.50. 19,000 sats went sent

1248
01:26:04,029 --> 01:26:08,760
on 23rd October. Beautiful. Thank you, comics or blogger. And

1249
01:26:08,760 --> 01:26:13,699
thank you, everybody who supports podcastindex.org. It's value for value.

1250
01:26:13,819 --> 01:26:18,260
Whatever you get out of it, you 22,000 leechers, consider

1251
01:26:18,260 --> 01:26:24,329
supporting us. Five bucks. Imagine if all those 22,000 people

1252
01:26:24,329 --> 01:26:28,869
gave us five bucks a month. Just imagine. We'd be

1253
01:26:28,869 --> 01:26:36,180
quitting our day jobs. Only imagine. Okay. The musical stylings

1254
01:26:36,180 --> 01:26:40,559
of Dave Jones, backup for Mercy Me. Yeah, beautiful. I

1255
01:26:40,559 --> 01:26:43,609
think it's mostly lack of sleep. Yeah, I know. And

1256
01:26:43,609 --> 01:26:48,579
you know what? We'll... You'll get into a better vibe.

1257
01:26:49,159 --> 01:26:52,059
How early are you waking up these days? 6.30 every

1258
01:26:52,059 --> 01:26:56,359
day, 6.30. Okay. I don't know. My body is in

1259
01:26:56,359 --> 01:27:04,920
this weird thing. This is pre-PH-Polocalypse. I'm like 4, 4.30.

1260
01:27:04,920 --> 01:27:08,500
Yeah. Ooh. Yeah, I know. It's in a rut. I'm

1261
01:27:08,500 --> 01:27:10,079
in some kind of rut. I got to get out

1262
01:27:10,079 --> 01:27:12,309
of that rut. And what time do you go to

1263
01:27:12,309 --> 01:27:17,100
bed? Like 10. Yeah. 10, 10. Yeah, we go to

1264
01:27:17,100 --> 01:27:20,699
bed at 10, 10. 10. Yeah, you just – it's

1265
01:27:20,699 --> 01:27:23,960
like you – six hours is okay, but it's like

1266
01:27:23,960 --> 01:27:25,940
as it rolls on day after day, you start to

1267
01:27:25,940 --> 01:27:30,229
kind of like – you drag, you know, like one

1268
01:27:30,229 --> 01:27:32,720
and then one day hits and you sleep like 10

1269
01:27:32,720 --> 01:27:37,460
hours. Mm. Yeah. Yeah, do I know the feeling, brother?

1270
01:27:37,720 --> 01:27:40,289
I know the feeling. Go FaceTime with your grandbaby. Well,

1271
01:27:40,289 --> 01:27:43,010
she just said, oh, she's sleepy. Might have to do

1272
01:27:43,010 --> 01:27:45,270
it later. Like, here I am, cutting off the board

1273
01:27:45,270 --> 01:27:49,000
meeting. Cutting off the board meeting. I have no idea.

1274
01:27:50,020 --> 01:27:53,020
I feel guilty. It's my response. It's my response. fault.

1275
01:27:53,159 --> 01:27:55,529
No, no, no. That took too long trying to find

1276
01:27:55,529 --> 01:28:00,489
the booster grass. This is our contribution to society. This

1277
01:28:00,489 --> 01:28:05,020
is my volunteer work that you and I do. This

1278
01:28:05,020 --> 01:28:09,239
is volunteer. We do it. Leachers, 22,000 leachers. We see

1279
01:28:09,239 --> 01:28:14,440
you at Apple and Microsoft. Jack-leg leachers. Jack-leg leachers. chairs.

1280
01:28:14,440 --> 01:28:17,000
There it is, everybody. Okay, thank you so much. Dave,

1281
01:28:17,000 --> 01:28:19,940
have a great weekend, brother. See you, bro. All right,

1282
01:28:19,940 --> 01:28:22,390
everybody. Thank you, board room. We'll see you next week

1283
01:28:22,390 --> 01:28:41,399
here on Podcasting 2.0. Music You have been listening to

1284
01:28:41,399 --> 01:28:51,199
Podcasting 2.0. Visit podcastindex.org for more information. Go podcasting! And

1285
01:28:51,199 --> 01:28:53,880
it chug, chug, chug, chug, chug. It just did its

1286
01:28:53,880 --> 01:28:54,300
thing.