Episode 271: Foot Terminal

1
00:00:00,500 --> 00:00:06,860
Podcasting 2.0 for September 18th, 2026, episode 271, Foot Terminal.

2
00:00:06,860 --> 00:00:11,449
Foot Terminal. Hello, everybody. Hey, guess what? We're not in

3
00:00:11,449 --> 00:00:15,000
New York. No, we're not in New York. We're in

4
00:00:15,000 --> 00:00:18,350
the boardroom. It is time for Podcasting 2.0. This is

5
00:00:18,350 --> 00:00:22,440
where the true future of podcasting is discussed because, hey,

6
00:00:22,440 --> 00:00:24,800
we're the people that build it, believe it or not.

7
00:00:24,800 --> 00:00:27,460
So we don't need to be hanging out in Manhattan.

8
00:00:27,660 --> 00:00:29,940
No, no, no. In fact, we are the only board

9
00:00:29,940 --> 00:00:34,210
meeting that doesn't need government regulation, the IPO. I'm Adam

10
00:00:34,210 --> 00:00:36,060
Curry here in the heart of the Texas Hill Country

11
00:00:36,060 --> 00:00:38,950
and in Alabama, the man who flipped four endpoints in

12
00:00:38,950 --> 00:00:41,649
four days, watched the logs until morning, and beat a

13
00:00:41,649 --> 00:00:44,420
coding agent with a pen and paper. Say hello to

14
00:00:44,420 --> 00:00:50,820
my friend on the other end, Dave Jones. They get

15
00:00:50,820 --> 00:00:53,369
better, right? P and P. P and P? What's P

16
00:00:53,369 --> 00:00:55,259
and P? Oh, pen and paper. Pen and paper. Pen

17
00:00:55,259 --> 00:00:58,219
and paper, baby. Yeah. That was good. I like that.

18
00:00:58,340 --> 00:01:01,210
That was excellent. Of course, the pen is mightier than

19
00:01:01,210 --> 00:01:04,310
the sword. Of course, the sick thing is, is that

20
00:01:04,310 --> 00:01:10,000
my robot wrote that whole sentence. Oh, well. I love

21
00:01:10,000 --> 00:01:13,560
the robot. I've taught the robot well. The robot knows.

22
00:01:13,680 --> 00:01:15,549
It's like, okay, I need a little thing about what

23
00:01:15,549 --> 00:01:18,129
Dave has been doing. And it goes through all of

24
00:01:18,129 --> 00:01:21,579
your podcast index.social posts and says, and it came up

25
00:01:21,579 --> 00:01:23,689
with that whole line. The man who flipped four endpoints

26
00:01:23,689 --> 00:01:25,819
in four days. Watch the logs until morning and beat

27
00:01:25,819 --> 00:01:29,409
a coding agent with a pen and paper. You need,

28
00:01:29,409 --> 00:01:35,900
you really need to, um, start putting those promos out

29
00:01:35,900 --> 00:01:39,469
in some place that that somebody else can hear it

30
00:01:39,469 --> 00:01:42,650
like tacking onto the front or something like that because

31
00:01:42,650 --> 00:01:45,620
that one last week was hilarious but it turns out

32
00:01:45,620 --> 00:01:48,159
it was it turns out YOLO guy was running the

33
00:01:48,159 --> 00:01:51,450
index the whole time that was that was also written

34
00:01:51,450 --> 00:01:54,799
by the robot That was cracking me up, man. Yeah.

35
00:01:54,879 --> 00:01:57,780
The robot has humor without even knowing it because it

36
00:01:57,780 --> 00:02:00,849
doesn't. It doesn't know anything. It's stupid. It's the humor

37
00:02:00,849 --> 00:02:05,659
of a three-year-old who does something and everybody in the

38
00:02:05,659 --> 00:02:08,819
room starts laughing, but they don't know why. Yeah, exactly.

39
00:02:09,039 --> 00:02:12,199
You nailed it. That's exactly right. That's exactly what's happening.

40
00:02:12,960 --> 00:02:19,099
Toddler humor. How you doing, brother? I'm good. Okay. Yeah,

41
00:02:19,099 --> 00:02:21,000
I'm good. You took a pause there. I was a

42
00:02:21,000 --> 00:02:23,330
little concerned. Took a pause. No, no, no. Not a

43
00:02:23,330 --> 00:02:27,169
bad pause. Just a pause to internally assess whether I

44
00:02:27,169 --> 00:02:31,719
am good or not. So I've been watching some of

45
00:02:31,719 --> 00:02:36,199
the podcast week, as James has called. We didn't have

46
00:02:36,199 --> 00:02:40,719
a Pod News Weekly review. Yeah. That kind of sucked.

47
00:02:42,129 --> 00:02:45,960
They skipped it, but I did have a... What are

48
00:02:45,960 --> 00:02:52,110
we going to talk about? The Buzzcast, do you consume

49
00:02:52,110 --> 00:02:59,800
Buzzcast? Irregularly. Irregularly. What did the Buzzcast... I did not

50
00:02:59,800 --> 00:03:01,800
hear it this week. What did the Buzzcast have? What

51
00:03:01,800 --> 00:03:05,060
did the Buzzcast have? Before I said it, Can I

52
00:03:05,060 --> 00:03:07,389
ask you a question about Omarchi first, real quick? Of

53
00:03:07,389 --> 00:03:09,680
course. If I don't right now, I'm going to forget.

54
00:03:09,759 --> 00:03:11,960
Okay, are you hanging in there because they saw, like,

55
00:03:12,020 --> 00:03:14,319
well, maybe you should go to Fedora. I'm going to

56
00:03:14,319 --> 00:03:18,000
do this. And there's Sir Bemrose. No, Alex Gates coming

57
00:03:18,000 --> 00:03:22,370
in right away. This is no good. This sucks. HFF

58
00:03:22,370 --> 00:03:30,099
is a hypester. I'm not a DHH fan. The way

59
00:03:30,099 --> 00:03:35,419
he talks, his volume and intensity has turned up to

60
00:03:35,419 --> 00:03:39,060
11 all day long, and I just cannot handle it.

61
00:03:39,120 --> 00:03:42,110
No, you're not supposed to. You're just supposed to install

62
00:03:42,110 --> 00:03:44,400
a Marchie, and then you need to look at the

63
00:03:44,400 --> 00:03:47,080
other calm guys, like that one guy who has a...

64
00:03:47,229 --> 00:03:49,479
is always drinking his coffee. He's not really that calm.

65
00:03:49,800 --> 00:03:51,979
I'm just watching all these other- Network Chuck. Yeah, Network

66
00:03:51,979 --> 00:03:56,699
Chuck. I like that guy. Network Chuck, he's my go-to

67
00:03:56,699 --> 00:03:59,800
source. Yeah, that guy and the other guy who is

68
00:03:59,800 --> 00:04:02,770
always testing all the AI models. I forget who he

69
00:04:02,770 --> 00:04:06,610
is. Yeah, Network Chuck is definitely my man. Yeah, I

70
00:04:06,610 --> 00:04:09,219
like him. I take a lot of advice from Network

71
00:04:09,219 --> 00:04:19,699
Chuck. Network Chuck. So my question is, I've been living

72
00:04:19,699 --> 00:04:22,759
with the Marche lifestyle for a couple of weeks now.

73
00:04:23,000 --> 00:04:27,860
It's an alternative lifestyle, mind you. It is alternative lifestyle.

74
00:04:29,720 --> 00:04:35,490
And I've got my desktop really dialed in. I've got

75
00:04:35,490 --> 00:04:39,649
all... I've got all the five default workspaces. I'm sure

76
00:04:39,649 --> 00:04:41,600
I could add more if I needed them. Yeah, you

77
00:04:41,600 --> 00:04:44,939
just hit super key six and it'll add one. Well,

78
00:04:44,939 --> 00:04:48,100
let me try that right now. Super keys. Bam! Okay.

79
00:04:48,980 --> 00:04:55,199
Bam, he says. Yes. So, so, I need to know,

80
00:04:55,199 --> 00:04:59,629
since I have this set up perfectly, Mm-hmm. I need

81
00:04:59,629 --> 00:05:04,279
to know how to make this exact configuration of window

82
00:05:04,279 --> 00:05:10,430
positions on workspaces come back at boot every time. Oh,

83
00:05:10,430 --> 00:05:15,959
okay. That's very easy. Okay. You ready? Yes. Open a

84
00:05:15,959 --> 00:05:22,439
terminal. Wait, I'm going to go... Super six and then

85
00:05:22,439 --> 00:05:25,740
you can just use, you can just super enter, super

86
00:05:25,740 --> 00:05:28,259
enter gives you a terminal. Yeah, but I don't want

87
00:05:28,259 --> 00:05:30,360
to, I don't want it to cram itself into it.

88
00:05:30,379 --> 00:05:32,160
So I'm going to get a super six and then

89
00:05:32,160 --> 00:05:34,540
super enter to give me a terminal. Now, let me

90
00:05:34,540 --> 00:05:38,420
just give you a little shortcut. Let me, uh, let

91
00:05:38,420 --> 00:05:41,800
me, uh, give you a little cool hint here. Uh,

92
00:05:42,060 --> 00:05:47,500
Do super tea. That's what they used to call me

93
00:05:47,500 --> 00:05:52,459
in high school. Did you do Super T? Yeah, I'm

94
00:05:52,459 --> 00:05:55,920
full screen now, baby. Well, you should be able to

95
00:05:55,920 --> 00:06:01,129
super right-click and reposition that window. So Super T basically

96
00:06:01,129 --> 00:06:06,110
makes it hovering. Oh, yeah. Okay. All right. I got

97
00:06:06,110 --> 00:06:07,639
you. And now if you do Super T again, it

98
00:06:07,639 --> 00:06:10,240
goes full screen. So it's not tiling. That's what it

99
00:06:10,240 --> 00:06:13,449
is. Sometimes I find a terminal window in a workspace

100
00:06:13,449 --> 00:06:17,579
by itself is too big. It's too big. Okay. Okay.

101
00:06:17,740 --> 00:06:19,779
Now you type in. It's too wide. It's too wide.

102
00:06:19,899 --> 00:06:24,000
Yes. Now you type in the following. Clawed. Okay. Okay.

103
00:06:24,000 --> 00:06:29,439
No, no, no, no, no. Negative. I refuse to comply

104
00:06:29,439 --> 00:06:33,360
with this. Literally, all you do is you say, Claude.

105
00:06:33,420 --> 00:06:37,000
It's built into the system. It has omarchie skills. But

106
00:06:37,000 --> 00:06:41,550
I have pi. I'm living the pi life. So I

107
00:06:41,550 --> 00:06:43,720
can do, you're going to tell me to get the

108
00:06:43,720 --> 00:06:47,939
agent to save my configuration. Yes, exactly. But okay, look,

109
00:06:47,939 --> 00:06:51,319
I've got Pi. Maybe Pi can do it. Okay, well,

110
00:06:51,319 --> 00:06:54,240
let's see. That was a funny joke, though, wasn't it?

111
00:06:54,319 --> 00:06:57,620
That was a funny joke. Yes. No, you got me.

112
00:06:57,680 --> 00:07:01,720
You got me. Okay, I'm going to go to, let's

113
00:07:01,720 --> 00:07:05,399
see, sandbox. I'm going to launch Pi. And you tell

114
00:07:05,399 --> 00:07:08,389
me what you want me to tell to... Save my

115
00:07:08,389 --> 00:07:15,339
current five workspaces configuration so it restores upon boot. Enter.

116
00:07:16,060 --> 00:07:22,670
Configuration so that all windows and their positions are restored

117
00:07:22,670 --> 00:07:26,899
upon boot. Okay. I'm going to just prepend this for

118
00:07:26,899 --> 00:07:32,769
my own clarity. I'm going to prepend this with this

119
00:07:32,769 --> 00:07:38,620
is an Omarchi system. Okay. okay all right we'll see

120
00:07:38,620 --> 00:07:42,550
so while you're doing that so while you're doing i

121
00:07:42,550 --> 00:07:45,279
may go down during the show what what uh what

122
00:07:45,279 --> 00:07:48,370
model are you running it on you're running on the

123
00:07:48,370 --> 00:07:52,259
on the spark um we're using a a variation of

124
00:07:52,259 --> 00:07:58,259
the uh quin 3.7b it's it's a new one called

125
00:07:58,829 --> 00:08:05,709
uh yukasai yukasai it's yukasai swift quinn 3.8 27b with

126
00:08:05,709 --> 00:08:10,290
uses 58 fewer thinking tokens with less than one percent

127
00:08:10,290 --> 00:08:12,730
quality loss of output so i find i figured it

128
00:08:12,730 --> 00:08:15,569
out it hit me this morning it just hit me

129
00:08:15,569 --> 00:08:21,100
i'm like oh i understand now The whole reason these

130
00:08:22,269 --> 00:08:26,279
Frontier Labs, which makes it sound... I mean, why don't

131
00:08:26,279 --> 00:08:29,759
we just say dudes in cubicles? But okay. Frontier Labs,

132
00:08:29,759 --> 00:08:32,509
they want to slow down. Yeah, we need to slow

133
00:08:32,509 --> 00:08:36,159
it down. I figured it out. It's so obvious. The

134
00:08:36,159 --> 00:08:41,370
models are not improving. They're just not improving. You know,

135
00:08:41,370 --> 00:08:44,200
in fact, the bigger the model is, the stupider it

136
00:08:44,200 --> 00:08:50,190
gets. The harnesses. Well, yes, because there's nothing left. They're

137
00:08:50,190 --> 00:08:52,019
all saying it. Well, there's nothing left on the Internet.

138
00:08:52,340 --> 00:08:54,759
There's nothing left to suck in. There's no, you know,

139
00:08:54,759 --> 00:08:58,080
all we can use is synthetic data. It's unimportant. It's

140
00:08:58,080 --> 00:09:03,460
the harness. The harness is the thing now. That's the

141
00:09:03,460 --> 00:09:05,919
only thing they have, and they know it, and they

142
00:09:05,919 --> 00:09:09,809
want to slow it down. It's collusion. It is absolutely,

143
00:09:09,809 --> 00:09:13,620
it should be deemed anti-competitive. They want to slow it

144
00:09:13,620 --> 00:09:16,860
down because they want all the open source models to

145
00:09:16,860 --> 00:09:19,220
stay four months behind. Don't catch up to us because

146
00:09:19,220 --> 00:09:24,480
if they don't move forward, nobody does. because they know

147
00:09:24,480 --> 00:09:27,870
that anything they do after this will just suck. And

148
00:09:27,870 --> 00:09:30,610
they have IPOs that they've already moved out, and there

149
00:09:30,610 --> 00:09:33,059
is nothing left for them to do but change the

150
00:09:33,059 --> 00:09:37,779
harness. And that's the beauty. Pi, your harness, you completely

151
00:09:37,779 --> 00:09:42,379
control. The weights on the model, you completely control. They're

152
00:09:42,379 --> 00:09:47,820
no longer necessary. So that's why they're doing dangerous regulation.

153
00:09:48,159 --> 00:09:51,970
That's it. Yeah. That's it. There's nothing else. I agree

154
00:09:51,970 --> 00:09:54,840
with you. I agree. I mean, it's like, it's hit

155
00:09:54,840 --> 00:09:57,970
me like, oh, this is so obvious. Do you remember

156
00:09:57,970 --> 00:09:59,980
this? And you, you just.

157
00:10:00,000 --> 00:10:03,009
disagreed with me and maybe you still do. We had

158
00:10:03,009 --> 00:10:08,840
a disagreement that I, my position is, Has been that

159
00:10:08,840 --> 00:10:12,559
part of the plan. Now, I don't believe that the

160
00:10:12,559 --> 00:10:16,860
big frontier labs had a plan. I don't believe that.

161
00:10:16,960 --> 00:10:20,850
I think that they're really just winging this whole thing

162
00:10:20,850 --> 00:10:23,039
as from day to day. I'm with you on that.

163
00:10:23,159 --> 00:10:28,419
Yeah. Yeah. But the... But I think part of the

164
00:10:28,419 --> 00:10:32,549
plan that evolved that they have now really become dependent

165
00:10:32,549 --> 00:10:37,539
upon is hardware prices. As the hardware prices have gone

166
00:10:37,539 --> 00:10:42,820
up, they have realized that that is a moat for

167
00:10:42,820 --> 00:10:49,509
them because local inference – It's really difficult if you

168
00:10:49,509 --> 00:10:53,980
can't afford to buy any equipment because a stick of

169
00:10:53,980 --> 00:10:58,370
rim costs $3,000. Absolutely. Did I disagree with you at

170
00:10:58,370 --> 00:11:01,799
the time? You did. What did I say? You said

171
00:11:01,799 --> 00:11:07,860
I disagree with you. Okay. But like the... I don't

172
00:11:07,860 --> 00:11:10,360
think that was the initial plan, but I think this

173
00:11:10,360 --> 00:11:13,769
has now become something they're dependent on. And the confirmation

174
00:11:13,769 --> 00:11:20,450
I got for that belief... was. An interview I heard

175
00:11:20,450 --> 00:11:25,059
with Ed Zitron talking about a Bloomberg report that just

176
00:11:25,059 --> 00:11:30,419
came out that says that to date, Microsoft has only

177
00:11:30,419 --> 00:11:36,419
built two gigawatts of AI capacity. Mm-hmm. In the grand

178
00:11:36,419 --> 00:11:43,899
scheme of things, if they've actually bought... enough GPUs to

179
00:11:43,899 --> 00:11:48,569
build out the 12 gigawatts that they have said that

180
00:11:48,569 --> 00:11:52,980
they have, which they actually haven't built, then that means

181
00:11:52,980 --> 00:11:58,680
they have... $100 billion worth of GPUs sitting in a

182
00:11:58,680 --> 00:12:03,110
warehouse somewhere. I don't believe that that's the case. These

183
00:12:03,110 --> 00:12:10,600
are more likely... purchase futures they've they've bought they've bought

184
00:12:10,600 --> 00:12:14,840
the they've contracted to buy gpus in the future and

185
00:12:14,840 --> 00:12:18,240
that is just pushing prices up and up and up

186
00:12:18,240 --> 00:12:21,680
and i don't think that they can afford to slow

187
00:12:21,680 --> 00:12:24,769
down because it's if there's a gpu market crash oh

188
00:12:24,769 --> 00:12:30,039
then everybody's running models everywhere Everybody gets models for nothing.

189
00:12:30,220 --> 00:12:32,899
Well, there's... Okay. So I'm going to... I don't know

190
00:12:32,899 --> 00:12:35,039
why I disagreed with you then, but I'm going to

191
00:12:35,039 --> 00:12:39,659
completely agree now because that is indeed a great extra

192
00:12:39,659 --> 00:12:46,059
benefit to them and NVIDIA. But AMD just acquired a

193
00:12:46,059 --> 00:12:50,559
company. And if we just take the premise that, okay,

194
00:12:50,559 --> 00:12:53,899
the models, basically the models are just okay now. The

195
00:12:53,899 --> 00:12:55,769
models are good. It's all in the harness. It's all

196
00:12:55,769 --> 00:12:58,110
in the weights, right? I mean, that's, I think you

197
00:12:58,110 --> 00:13:01,240
and I agree on that. So, again, there's incremental improvement

198
00:13:01,240 --> 00:13:04,569
here and there. But in general, I think we're pretty

199
00:13:04,569 --> 00:13:10,529
good. Yeah, pretty good. So they just bought a company,

200
00:13:10,529 --> 00:13:14,740
AMD acquired a company called Talos. And here is a

201
00:13:14,740 --> 00:13:17,909
clip from Tech Tech Potato, because yeah, it's not just

202
00:13:17,909 --> 00:13:22,569
Network Chuck. I also watch Tech Tech Potato, as you

203
00:13:22,569 --> 00:13:27,220
should. Listen to this. Now, the metrics kind of sound

204
00:13:27,220 --> 00:13:31,309
a bit insane. Just going off the website here, we

205
00:13:31,309 --> 00:13:36,419
have a... Technology demonstrator chip. This chip is built on

206
00:13:36,419 --> 00:13:40,669
TSMC 6 nanometer at near reticle size, 815 square mil,

207
00:13:40,669 --> 00:13:43,990
with 53 billion transistors. And you put enough of them

208
00:13:43,990 --> 00:13:47,159
to fill a 2.5 kilowatt server. So we're probably looking

209
00:13:47,159 --> 00:13:50,370
at something around eight chips. And it's running the Lama

210
00:13:50,370 --> 00:13:57,129
3.1 8 billion parameter model. it looks like a PCI

211
00:13:57,129 --> 00:13:59,569
card, there's a lot of power delivery there that's probably

212
00:13:59,569 --> 00:14:03,639
why it's got a high volt 12 power rail there

213
00:14:03,639 --> 00:14:06,600
so it's hitting at least 300 watts per card but

214
00:14:06,600 --> 00:14:11,269
the numbers here are what's insane. Tokens per second per

215
00:14:11,269 --> 00:14:16,039
user. We're seeing NVIDIA H200 at around 230. We're seeing

216
00:14:16,039 --> 00:14:20,700
Grok at 600. We're seeing Cerebrus at 2000, numbers that

217
00:14:20,700 --> 00:14:24,879
I can verify actually exist. Talos are saying they can

218
00:14:24,879 --> 00:14:31,100
do 17,000 tokens per second on this chip. And of

219
00:14:31,100 --> 00:14:36,860
course, nobody believed them. until they built a website around

220
00:14:36,860 --> 00:14:39,819
their chip. You can go check this out now. It's

221
00:14:39,819 --> 00:14:46,639
called chatjimmy.ai. I know, it's pretty gay. Let's hopefully we

222
00:14:46,639 --> 00:14:51,350
won't death hug the website. It says, chatjimmy, how can

223
00:14:51,350 --> 00:14:54,420
I help you today? And let's ask it a question.

224
00:14:55,079 --> 00:15:06,620
Say... What is in the... bubbles in pop. Generated in

225
00:15:06,620 --> 00:15:12,200
33 milliseconds, the answer came at a speed of 14,200

226
00:15:12,200 --> 00:15:16,899
tokens per second. So this is, of course, the next

227
00:15:16,899 --> 00:15:22,019
level. is just bake the model into the chip. It's

228
00:15:22,019 --> 00:15:26,440
perfect. What more do you need? Every computer will come

229
00:15:26,440 --> 00:15:32,129
with this. If I mean, no offense to tech, tech

230
00:15:32,129 --> 00:15:35,789
potato, but I don't I don't think he has to

231
00:15:35,789 --> 00:15:39,039
worry about death hugging anybody on his live stream. I

232
00:15:39,039 --> 00:15:44,730
just I just like the term death hugging. I thought

233
00:15:44,730 --> 00:15:47,490
that was funny. Yeah, I don't think that one's going

234
00:15:47,490 --> 00:15:50,600
to be a big concern for you, bro. No. But

235
00:15:50,600 --> 00:15:57,860
what an awesome idea. Yeah, I mean, the... Because at

236
00:15:57,860 --> 00:16:03,289
some point, the model just ceases to be irrelevant. We're

237
00:16:03,289 --> 00:16:07,059
there. We're peak model. That's it. You don't need to

238
00:16:07,059 --> 00:16:10,240
do much more. We already have all the information. It's

239
00:16:10,240 --> 00:16:14,440
all about the tools now. It's like, get the tools,

240
00:16:14,440 --> 00:16:19,680
execute the tools. Speak English. What more do you need?

241
00:16:20,420 --> 00:16:25,149
Or speak Python. That's all you need. It's there. It's

242
00:16:25,149 --> 00:16:29,559
done. It's over. These guys are over. Unless, of course,

243
00:16:29,559 --> 00:16:32,879
they're going to try all kinds of shenanigans, of course.

244
00:16:33,920 --> 00:16:37,759
But to me, it's like I'm running Quinn 3.8, I

245
00:16:37,759 --> 00:16:44,559
think. 27? Yes, for all my stuff. It's great. It

246
00:16:44,559 --> 00:16:47,910
is good. You should switch to this Swift version of

247
00:16:47,910 --> 00:16:53,420
that. Okay. Because it's... it is quicker with very little

248
00:16:53,420 --> 00:16:55,660
slowdown. I think it's the number one model on Pugging

249
00:16:55,660 --> 00:16:59,970
Face right now. And now I went back and I

250
00:16:59,970 --> 00:17:05,039
listened to that Alex Karp crazy interview on CNBC. He

251
00:17:05,039 --> 00:17:10,360
looks so much like that dude from Ancient Aliens. Yes.

252
00:17:10,519 --> 00:17:13,000
Tell me he doesn't. Yeah, he does. He does. And

253
00:17:13,000 --> 00:17:17,529
now I understand what he was saying. It's like... The

254
00:17:17,529 --> 00:17:21,019
value is no longer in the model. The value is

255
00:17:21,019 --> 00:17:24,440
in the application. It's in the harness. That's where the

256
00:17:24,440 --> 00:17:28,980
value is. And anybody can create those. See, Hermes, Hermes,

257
00:17:28,980 --> 00:17:34,079
and Pi. Well, the model, the agent itself can create

258
00:17:34,660 --> 00:17:36,860
The tools and the sandboxes and all those kinds of

259
00:17:36,860 --> 00:17:38,759
things. Exactly. If it needs them. I've seen it do

260
00:17:38,759 --> 00:17:43,460
it so many times at this point. Yeah. And even

261
00:17:43,460 --> 00:17:48,690
the best models still on their own make just the

262
00:17:48,690 --> 00:17:53,720
sloppiest mistakes. I've been living this for the last three

263
00:17:53,720 --> 00:17:56,619
weeks. You and me both, brother. Of course. Of course

264
00:17:56,619 --> 00:17:59,210
we've been living that. Of course. In fact, I think

265
00:17:59,210 --> 00:18:03,380
the newer the model, the more mistakes it makes. I

266
00:18:03,380 --> 00:18:07,309
think you're, I think you might be right. I, Because

267
00:18:07,309 --> 00:18:12,250
there's really no discernible difference to me between... I think

268
00:18:12,250 --> 00:18:15,680
the newer models become better at the benchmarks, but they

269
00:18:15,680 --> 00:18:20,539
don't actually become better at their regular general use output.

270
00:18:21,799 --> 00:18:26,180
You know, and that's Been clear because I've used, I've

271
00:18:26,180 --> 00:18:31,259
been going through this database refactor for weeks now. And

272
00:18:31,259 --> 00:18:33,829
as I switch between the different levels of models, I

273
00:18:33,829 --> 00:18:37,139
just get the same, basically the same results. I don't

274
00:18:37,139 --> 00:18:40,299
see any difference. No, there is none. So that's it.

275
00:18:40,420 --> 00:18:44,299
You know, we can stop hyping. It's fantastic. We build

276
00:18:44,299 --> 00:18:49,320
our own. You know, we pack together our own harnesses

277
00:18:49,320 --> 00:18:52,779
and our own weights for each application specifically. Then we're

278
00:18:52,779 --> 00:18:55,360
good to go. I don't think there's anything else coming.

279
00:18:56,460 --> 00:18:59,279
We're good. We're good. We're good. We're good. It's all

280
00:18:59,279 --> 00:19:03,750
good. And I'm happy. I'm like, okay, I'm now a

281
00:19:03,750 --> 00:19:05,980
software developer and I'm good. You can turn it off

282
00:19:05,980 --> 00:19:08,240
now. You can shut the companies down. We're good. Are

283
00:19:08,240 --> 00:19:14,340
you completely off of cloud models now? I still use

284
00:19:14,340 --> 00:19:21,409
Claude code to create certain things, but all inference runs

285
00:19:21,409 --> 00:19:29,259
on the Asus. Oh, okay. Oh, the GB or GX10.

286
00:19:29,259 --> 00:19:32,940
Yeah. Yeah. Okay. And, uh, and I run my harnesses

287
00:19:32,940 --> 00:19:38,090
on the Helix. So I do have those separated. Yeah,

288
00:19:38,090 --> 00:19:40,099
because I got a lot of different agents running. So

289
00:19:40,099 --> 00:19:43,320
I want them to have lots of RAM. Yeah, Eric,

290
00:19:43,320 --> 00:19:48,559
there actually is a pretty big difference. You only really

291
00:19:48,559 --> 00:19:52,990
see it if you're... It's clear when you're looking at

292
00:19:52,990 --> 00:19:59,099
it through Pi with this model because Pi is real

293
00:19:59,099 --> 00:19:59,980
good.

294
00:20:00,019 --> 00:20:04,460
good about showing you the various, like we call those

295
00:20:04,460 --> 00:20:08,940
like the placeholders for the, for the tool calling and

296
00:20:08,940 --> 00:20:11,130
the thinking blocks and all that kind of stuff. And

297
00:20:11,130 --> 00:20:15,920
you can see what it's better at is it doesn't

298
00:20:15,920 --> 00:20:20,359
cycle as much through the same thing. types of things.

299
00:20:20,619 --> 00:20:22,680
So rather than you may, you're still going to have

300
00:20:22,680 --> 00:20:25,539
long thinking because that's just what that model does. But

301
00:20:25,539 --> 00:20:29,759
the thinking is becomes, it's, it doesn't get stuck on

302
00:20:29,759 --> 00:20:32,640
the same parts over and over. It tends to move

303
00:20:32,640 --> 00:20:36,039
on faster to the, to other things. So you overall

304
00:20:36,039 --> 00:20:40,000
over like through a, through a full session of something,

305
00:20:40,500 --> 00:20:46,180
you'll end up with considerably quicker results. So I think,

306
00:20:46,180 --> 00:20:48,619
I mean, I think it's worth it. And there, that

307
00:20:48,619 --> 00:20:52,759
seems that from what I've seen on the different Reddit

308
00:20:52,759 --> 00:20:55,160
threads and that kind of thing, this is everybody's experience

309
00:20:55,160 --> 00:20:56,920
is roughly the same. You're still going to have a

310
00:20:56,920 --> 00:20:59,279
lot of thinking, but you're going to end up with

311
00:20:59,279 --> 00:21:06,200
an output that comes sooner. Yeah, I mean, this... I

312
00:21:06,200 --> 00:21:14,569
don't know about... I don't really understand what is going

313
00:21:14,569 --> 00:21:18,619
on with Cloudflare. Oh? I think they're spending so much

314
00:21:18,619 --> 00:21:22,210
time doing AI bullcrap that they've really, they're starting to

315
00:21:22,210 --> 00:21:27,559
like... lose the plot what do you mean what are

316
00:21:27,559 --> 00:21:32,900
they doing Well, I mean... I'm just, I'm pretty annoyed.

317
00:21:33,180 --> 00:21:35,740
So Melissa says that I have like, she told me

318
00:21:35,740 --> 00:21:38,400
the other day, she's like, you really have like a.

319
00:21:39,099 --> 00:21:43,359
simmering low-level annoyance all the time. And you say, yeah,

320
00:21:43,359 --> 00:21:50,420
how long have we been married? No, I don't. Exactly.

321
00:21:50,859 --> 00:21:56,039
What are you talking about? And I told him, like,

322
00:21:56,039 --> 00:21:59,799
you know what? It's tech. I've always had a love-hate

323
00:21:59,799 --> 00:22:05,180
relationship with tech. I mean, I love, I'm a tinkerer.

324
00:22:05,380 --> 00:22:09,119
I love technology. But I also hate technology at the

325
00:22:09,119 --> 00:22:14,779
same time because it's so – the more you integrate

326
00:22:14,779 --> 00:22:17,369
it into your life, the more you start to have

327
00:22:17,369 --> 00:22:21,730
death by a thousand paper cuts. Mm-hmm. And you're just

328
00:22:21,730 --> 00:22:27,480
spending all of your time, you know, with home automation.

329
00:22:28,639 --> 00:22:31,440
I got rid of that a long time ago. Yeah.

330
00:22:31,639 --> 00:22:33,759
It's like, man, I just want a bowl of cereal.

331
00:22:34,019 --> 00:22:35,440
Like, why do I have to put in my two

332
00:22:35,440 --> 00:22:39,160
factor? Do you know what I mean? Like, it's that

333
00:22:39,160 --> 00:22:41,789
kind of crap that you just have to, it's. It

334
00:22:41,789 --> 00:22:47,960
drains your vitality. Yes. When you begin to live as

335
00:22:47,960 --> 00:22:52,519
a machine. And that's, I think it's, I think it's

336
00:22:52,519 --> 00:22:55,200
that in this cloud flare thing is a perfect example

337
00:22:55,200 --> 00:23:00,019
of this because it's, They, they've had this program, you

338
00:23:00,019 --> 00:23:01,360
know, they came out, it was a couple of years

339
00:23:01,360 --> 00:23:05,519
ago with this thing, the bot identification program where you

340
00:23:05,519 --> 00:23:09,809
could register your, your bot. Oh yeah. This is, this

341
00:23:09,809 --> 00:23:12,039
is in your, this is stuck in your craw this

342
00:23:12,039 --> 00:23:16,639
one because you, yeah, I understand. And it's, so I

343
00:23:16,639 --> 00:23:20,529
went through all of their things. I submitted the podcast

344
00:23:20,529 --> 00:23:25,210
index aggregator as a feed crawling bot. I did all

345
00:23:25,210 --> 00:23:30,450
of that under the old regime regime. They, it was

346
00:23:30,450 --> 00:23:35,779
months, no response. Right. Right. After like eight or nine

347
00:23:35,779 --> 00:23:39,369
months, no response. Well, then they come out with this

348
00:23:39,369 --> 00:23:45,380
blog post saying, hey, we've heard your feedback. We've heard

349
00:23:45,380 --> 00:23:50,740
your feedback. I'm sure they did. Yeah, they heard it.

350
00:23:50,860 --> 00:23:53,099
They changed it. They heard it. They didn't care about

351
00:23:53,099 --> 00:23:55,730
you, but they heard it. Yeah. And they're like, we've

352
00:23:55,730 --> 00:23:59,860
changed our system. Now you're going to get status updates.

353
00:24:00,860 --> 00:24:03,579
There's a different way to submit your stuff. So go

354
00:24:03,579 --> 00:24:07,660
submit your bot again under the new system. So I

355
00:24:07,660 --> 00:24:09,670
went through and I did it all under the new

356
00:24:09,670 --> 00:24:17,450
system. Yes. And zero feedback. It's been pending review for

357
00:24:17,450 --> 00:24:21,309
about three weeks. Yeah. And I've done it exactly to

358
00:24:21,309 --> 00:24:25,900
the modern standard that they wanted it done, which is

359
00:24:25,900 --> 00:24:32,289
we do HTTP request signing. with a public key. Man,

360
00:24:32,289 --> 00:24:37,180
I jumped through so many hoops to get Cloudflare to

361
00:24:37,180 --> 00:24:40,289
give us the time of day, and they do not

362
00:24:40,289 --> 00:24:45,500
care because they're too busy recreating WordPress, which nobody will

363
00:24:45,500 --> 00:24:49,799
ever use. What do you mean recreating WordPress? They cloned

364
00:24:49,799 --> 00:24:53,079
WordPress with a bunch of AI agents. Why? I don't

365
00:24:53,079 --> 00:24:57,839
know. That was their big press release. Cloudflare did that?

366
00:24:58,299 --> 00:25:03,670
Yes. Well, that's odd. I mean, like they were they

367
00:25:03,670 --> 00:25:06,839
were super proud of this, of this, that they vibe

368
00:25:06,839 --> 00:25:11,660
coded a solution to WordPress and WordPress and Next.js. And

369
00:25:11,660 --> 00:25:14,940
they called it something. What did they call it here?

370
00:25:15,980 --> 00:25:20,460
The spiritual M dash, the spiritual successor to WordPress that

371
00:25:20,460 --> 00:25:28,059
solves plugin security. Yeah. Like, That's what they're spending their

372
00:25:28,059 --> 00:25:33,630
time on. We recently rebuilt Next.js in one week using

373
00:25:33,630 --> 00:25:36,089
AI coding agents, but for the past two months, our

374
00:25:36,089 --> 00:25:38,529
agents have been working on an even more ambitious project,

375
00:25:38,529 --> 00:25:45,130
rebuilding WordPress. Oh, my goodness. Why? Why? What is the

376
00:25:45,130 --> 00:25:50,660
point? I don't get it, man. WordPress exists. Why do

377
00:25:50,660 --> 00:25:53,079
you have to make another one? Okay, I hear the

378
00:25:53,079 --> 00:25:57,930
low-level anger, irritation coming out there. She's right. Our new

379
00:25:57,930 --> 00:26:02,950
name for this CMS is M-Dash. How original. Yeah, nobody's

380
00:26:02,950 --> 00:26:06,220
ever used that before. It's entirely written in TypeScript. It's

381
00:26:06,220 --> 00:26:08,380
serverless, but you can run it on your own hardware,

382
00:26:08,380 --> 00:26:12,119
any platform you choose. I bet they have 10 users

383
00:26:12,119 --> 00:26:15,559
of this product for years, and then they kill it

384
00:26:15,559 --> 00:26:19,490
because it's dumb. Well, they have Google-itis is what they

385
00:26:19,490 --> 00:26:23,869
have. It's like you're really good at one thing. Like

386
00:26:23,869 --> 00:26:27,369
search. And then you got to build rockets and do

387
00:26:27,369 --> 00:26:33,639
all kinds of other stuff. Yeah. Those thermostats. Yeah. Cameras.

388
00:26:33,819 --> 00:26:37,670
Yeah. Yeah. This is all dumb, but it is actually

389
00:26:37,670 --> 00:26:40,779
annoying to me because we, this is a real problem

390
00:26:40,779 --> 00:26:45,119
that we have. We sometimes get blocked by Cloudflare's bot

391
00:26:45,119 --> 00:26:49,250
blocker. And we're a feed crawler. We live and die

392
00:26:49,250 --> 00:26:52,940
by the aggregators. Right. We have to be able to

393
00:26:52,940 --> 00:26:55,930
have some sort of allowance for that, and they will

394
00:26:55,930 --> 00:26:58,559
not look at my emails. So we're still running up

395
00:26:58,559 --> 00:27:02,759
against issues hitting Cloudflare with our crawlers, and we just

396
00:27:02,759 --> 00:27:05,680
can't get through? Is that what you're saying? It's rare.

397
00:27:06,099 --> 00:27:08,740
It's not a ton of them, but it does happen.

398
00:27:08,900 --> 00:27:12,119
I see it. I've been deep. still deep in the

399
00:27:12,119 --> 00:27:16,539
bowels of the index. And I'm still seeing it because

400
00:27:16,539 --> 00:27:20,220
I'm hitting edge cases every day with this refactor. And

401
00:27:20,220 --> 00:27:22,720
one of the ones I hit yesterday was this problem.

402
00:27:23,059 --> 00:27:25,759
Well, before we get into the refactor, I thought there

403
00:27:25,759 --> 00:27:27,549
was kind of a win because I had been paying

404
00:27:27,549 --> 00:27:34,279
attention to what's happening at... Podcast week. podcast movement. Tom

405
00:27:34,279 --> 00:27:40,119
Webster from Sounds Profitable He did a whole speech. It

406
00:27:40,119 --> 00:27:43,420
was pretty interesting, actually. And he threw up this slide.

407
00:27:43,559 --> 00:27:48,130
Actually, James wrote a post about it. And this is

408
00:27:48,130 --> 00:27:51,730
on the screen. There's a slide. None of the top

409
00:27:51,730 --> 00:27:56,329
three is a dedicated podcast platform. And it shows YouTube,

410
00:27:56,329 --> 00:28:00,779
Spotify, and Netflix. Which is where everybody has to be.

411
00:28:00,839 --> 00:28:02,410
You got to be there because that's where the audience

412
00:28:02,410 --> 00:28:05,160
is. It's got to be there. Where did Netflix come

413
00:28:05,160 --> 00:28:09,500
from? Oh, Netflix has been acquiring podcasts. And in fact,

414
00:28:09,500 --> 00:28:12,420
if you get a deal with Netflix, you have to

415
00:28:12,420 --> 00:28:14,750
take your stuff off of YouTube. And then if you

416
00:28:14,750 --> 00:28:19,230
turn on Netflix, there's, I don't know, there's a... Failed

417
00:28:19,230 --> 00:28:25,019
television people like who's the guy? Brian Williams. You know,

418
00:28:25,019 --> 00:28:29,680
they've all got podcasts now. And so what Netflix is

419
00:28:29,680 --> 00:28:31,740
trying to do is they're trying to get daytime viewing

420
00:28:31,740 --> 00:28:35,490
numbers up. And in fact, they're actually not doing that

421
00:28:35,490 --> 00:28:39,029
great. Netflix's numbers are not doing well because they're focusing

422
00:28:39,029 --> 00:28:43,000
on podcasts, morons. But there was this... I got this

423
00:28:43,000 --> 00:28:45,190
little bit, which I thought was kind of interesting. And

424
00:28:45,190 --> 00:28:49,820
this just solidified the whole idea of RSS people. I

425
00:28:49,820 --> 00:28:52,210
will say just a little bit more on the controversial

426
00:28:52,210 --> 00:28:55,500
side that, you know, this does show you the platforms

427
00:28:55,500 --> 00:28:57,079
don't have all the power which I think is so

428
00:28:57,079 --> 00:29:00,059
cool that you know podcasting really is a meritocracy everyone

429
00:29:00,059 --> 00:29:02,110
wants it to be this thing that it isn't there's

430
00:29:02,110 --> 00:29:04,659
too much revenue on the top 500,000 shows we have

431
00:29:04,659 --> 00:29:06,420
a lot of big shows I shouldn't be saying that

432
00:29:06,420 --> 00:29:08,759
but in the mid-size to the long there's so much

433
00:29:08,759 --> 00:29:11,880
value for brands in many cases you'll be the 100%

434
00:29:11,880 --> 00:29:14,500
share of voice for the foreseeable future so I think

435
00:29:14,500 --> 00:29:16,869
there's so much upside there. Now, the idea that the

436
00:29:16,869 --> 00:29:19,170
platforms can't just decide to do this, we had a

437
00:29:19,170 --> 00:29:22,590
really, really large UK publisher of ours that said, hey,

438
00:29:22,590 --> 00:29:25,210
they were more upset than we were about this. And

439
00:29:25,210 --> 00:29:26,789
it's not my place to talk them out of it

440
00:29:26,789 --> 00:29:29,630
or defend it. If they want to pause their distribution

441
00:29:29,630 --> 00:29:32,139
on Spotify, that's what they did. And that's what we

442
00:29:32,139 --> 00:29:34,490
will support them in that. So that just shows that

443
00:29:34,490 --> 00:29:37,710
you can't do this, right? I also worked in an

444
00:29:37,710 --> 00:29:40,450
industry where, you know, if you're just beholden to somebody

445
00:29:40,450 --> 00:29:43,139
like Facebook, I watched them turn off 25% of our

446
00:29:43,139 --> 00:29:45,799
revenue with just an algorithmic change that they couldn't explain.

447
00:29:46,259 --> 00:29:48,539
So the idea that our creators won't be relying on

448
00:29:48,539 --> 00:29:51,070
any one platform, that if they make a mistake, there's

449
00:29:51,070 --> 00:29:53,240
other places to go, I think is really important and

450
00:29:53,240 --> 00:29:55,059
kind of a good check and balance on the industry.

451
00:29:55,420 --> 00:29:58,320
Hallelujah. I don't know what industry you're talking about, about,

452
00:29:58,320 --> 00:30:00,000
but hallelujah.

453
00:30:01,000 --> 00:30:05,910
Decaf, man. Well, it's the podcast industrial complex. It runs

454
00:30:05,910 --> 00:30:10,390
on caffeine. But Tina asked me this the other day,

455
00:30:10,390 --> 00:30:13,289
and we're talking about Godcaster, and she says, well, what's

456
00:30:13,289 --> 00:30:17,839
the point? Yeah. I always love those kinds of questions.

457
00:30:17,839 --> 00:30:19,420
It's like, cause you have to stop and think about

458
00:30:19,420 --> 00:30:22,069
it for a second. What's the point? Why would anyone

459
00:30:22,069 --> 00:30:24,839
want this when they can just go to Apple and

460
00:30:24,839 --> 00:30:27,440
then listen to the podcast? And now, and whenever she

461
00:30:27,440 --> 00:30:30,259
says this, I am very happy. This is, this is,

462
00:30:30,440 --> 00:30:33,490
This is the best news I could receive because Tina

463
00:30:33,490 --> 00:30:35,759
was also, and she's told me this, we weren't together.

464
00:30:36,279 --> 00:30:40,789
She said, I remember thinking, what's the point of having

465
00:30:40,789 --> 00:30:44,759
a card to pay with? What's the point? When you've

466
00:30:44,759 --> 00:30:47,269
got a pocket full of cash. Yes. And the next

467
00:30:47,269 --> 00:30:49,609
one was, what is the point of being able to

468
00:30:49,609 --> 00:30:53,000
make a phone call on the street? Yes. So whenever

469
00:30:53,000 --> 00:30:56,809
she says this, I'm happy. You're like, yes, we've made

470
00:30:56,809 --> 00:31:00,339
it. And of course, then I said, well, you'd be

471
00:31:00,339 --> 00:31:04,650
surprised that 30 to 35% of women actually, they just

472
00:31:04,650 --> 00:31:09,200
listened to a podcast episode in a web browser. And

473
00:31:09,200 --> 00:31:14,759
of course, there's also another 30% of women who are

474
00:31:14,759 --> 00:31:22,099
bots, who are posing as a web browser. So, you

475
00:31:22,099 --> 00:31:24,970
know, it's like wherever, wherever you get your podcast is

476
00:31:24,970 --> 00:31:30,220
still the most powerful sentence in broadcasting today. And so

477
00:31:30,220 --> 00:31:33,609
when people are starting to realize in the podcast industrial

478
00:31:33,609 --> 00:31:38,150
complex that, you know, being able to go anywhere is

479
00:31:38,150 --> 00:31:42,230
a plus and your audience will go where you tell

480
00:31:42,230 --> 00:31:46,920
them, they will. And so, you know, of course, RSS

481
00:31:46,920 --> 00:31:51,109
isn't actually mentioned in the clip. But that is the

482
00:31:51,109 --> 00:31:54,200
beauty of podcasting. And people are starting to find out.

483
00:31:54,380 --> 00:31:58,500
I mean, Spotify. Oh, good Lord. They have taken down

484
00:31:58,500 --> 00:32:01,890
so many episodes of No Agenda now. Every day I

485
00:32:01,890 --> 00:32:04,579
get a new, oh, we took this one down. We

486
00:32:04,579 --> 00:32:07,059
took this one down. Because it's got music in it.

487
00:32:07,390 --> 00:32:11,250
And we got AI songs that people make themselves. Oh,

488
00:32:11,250 --> 00:32:14,610
this music, take it off. I thought y'all weren't on

489
00:32:14,610 --> 00:32:18,319
Spotify. We weren't. And then we decided before John died,

490
00:32:18,319 --> 00:32:20,619
we decided to, that's probably what killed him. Put him

491
00:32:20,619 --> 00:32:25,839
on Spotify. That's it. It polished him off. Same. You

492
00:32:25,839 --> 00:32:27,980
need to be on YouTube. Put it on YouTube. Put

493
00:32:27,980 --> 00:32:29,619
it on YouTube. Okay. Why don't you put it on

494
00:32:29,619 --> 00:32:32,670
YouTube? And hey, man, I took it off YouTube because

495
00:32:32,670 --> 00:32:34,940
I got two strikes. I can't have another strike. Well,

496
00:32:34,940 --> 00:32:38,309
what'd you get strikes for? Copyright violation. Oh, you mean

497
00:32:38,309 --> 00:32:41,579
the completely legal fair use case of us playing clips

498
00:32:41,579 --> 00:32:45,849
of news organizations? Yeah, well, of course. I like what

499
00:32:45,849 --> 00:32:50,069
that guy said in that clip. He's like the middle

500
00:32:50,069 --> 00:32:56,119
of the podcast, not in the top 500,000 or whatever

501
00:32:56,119 --> 00:33:02,039
he said. That's exactly how I want to be remembered.

502
00:33:03,000 --> 00:33:07,139
In the future, looking back on my work is, man,

503
00:33:07,139 --> 00:33:08,900
I'm so proud of what I did because I was

504
00:33:08,900 --> 00:33:16,360
so valuable to brands. That's funny. It just makes my

505
00:33:16,360 --> 00:33:19,529
heart warm. I was valuable. Think of how valuable I

506
00:33:19,529 --> 00:33:24,460
was to brands. Valuable to brands. Baby, I'm going to

507
00:33:24,460 --> 00:33:26,599
miss you, but at least we were valuable to brands.

508
00:33:28,559 --> 00:33:31,400
Let me see. So first of all, Daniel J. Lewis

509
00:33:31,400 --> 00:33:34,360
is always trying to rebrand everything. It's not good enough

510
00:33:34,360 --> 00:33:37,579
to have super chapters. I don't like saying wherever you

511
00:33:37,579 --> 00:33:40,680
get your podcasts. I say, in your favorite podcast app.

512
00:33:40,759 --> 00:33:44,680
No. No. No, no, because it could also be a

513
00:33:44,680 --> 00:33:46,700
route. Let me just take a look at no agenda.

514
00:33:46,799 --> 00:33:48,940
Let me see how many episodes have been taken down.

515
00:33:49,420 --> 00:33:52,150
Like, did they take them down or just notify? No,

516
00:33:52,150 --> 00:33:54,700
they take it down. Let's see. What am I missing

517
00:33:54,700 --> 00:34:05,759
here? Uh... 1892 is gone. Uh... Oh, we got to

518
00:34:05,759 --> 00:34:10,820
go. 1879 is gone. Yeah, they just take it down,

519
00:34:10,820 --> 00:34:13,980
man. They just take it down. Or someone reports you

520
00:34:13,980 --> 00:34:19,639
for something. Bimrose. I get my podcast through WGit. That's

521
00:34:19,639 --> 00:34:25,440
my podcast app. You know, who's my buddy over here?

522
00:34:25,639 --> 00:34:30,000
My buddy. Let me see. Where's my buddy? My buddy.

523
00:34:30,000 --> 00:34:34,630
My buddy. He built something interesting. Why can't I find

524
00:34:34,630 --> 00:34:41,070
them now? Um, he built a podcast app, Jonathan, here

525
00:34:41,070 --> 00:34:47,210
we go. Let me see. In fact, it's a media

526
00:34:47,210 --> 00:34:52,340
player. It automatically censors words from a list of profanity.

527
00:34:54,090 --> 00:34:58,369
What? Yeah. So it's a media player. And he's just

528
00:34:58,369 --> 00:35:02,170
getting, this is like alpha alpha. He's just messing around

529
00:35:02,170 --> 00:35:05,880
with stuff. Okay. It's like, you know, because I play

530
00:35:05,880 --> 00:35:08,360
stuff. I don't want my kids to hear certain things

531
00:35:08,360 --> 00:35:11,210
while I'm listening to it. So, hey, you know, what's

532
00:35:11,210 --> 00:35:14,340
wrong with that? Yeah. I mean, there's some, there's some

533
00:35:14,340 --> 00:35:17,279
episodes that really wouldn't, that it'd skip the whole episode.

534
00:35:18,320 --> 00:35:21,130
You'd get a word every few seconds. Yeah. But I

535
00:35:21,130 --> 00:35:22,789
mean, this is the kind of stuff that people are

536
00:35:22,789 --> 00:35:24,769
thinking about. Like, you know, Hey, I can, but he

537
00:35:24,769 --> 00:35:28,659
says, Oh, this is interesting. It works on modest hardware.

538
00:35:29,300 --> 00:35:31,440
He says he worked out a way to share fingerprints

539
00:35:31,440 --> 00:35:33,789
of the scans to servers so the app will just

540
00:35:33,789 --> 00:35:35,309
look to see if someone else has already scanned the

541
00:35:35,309 --> 00:35:38,579
media and produced a fingerprint. There's all kinds of interesting

542
00:35:38,579 --> 00:35:42,480
things taking place. Because, yeah, just because I don't mind

543
00:35:42,480 --> 00:35:46,239
what, you know, what languages use, maybe someone else doesn't

544
00:35:46,239 --> 00:35:51,779
want to hear it. We're in a whole new era

545
00:35:51,779 --> 00:35:58,750
of stuff. It reminds me of... What I was started

546
00:35:58,750 --> 00:36:03,079
to bring up and forgot was the latest buzzcast. Yes.

547
00:36:03,599 --> 00:36:06,340
And that the reason I had brought it up was

548
00:36:06,340 --> 00:36:10,599
because they're talking about how they're their vibe coding, their

549
00:36:10,599 --> 00:36:14,980
own remote recording tool to do their podcasts. Oh, sure.

550
00:36:15,099 --> 00:36:19,070
Why wouldn't you? And this, so the first thing I

551
00:36:19,070 --> 00:36:21,510
thought of when they were talking about this and they're,

552
00:36:21,510 --> 00:36:24,849
they're evidently going to release it, you know, into some

553
00:36:24,849 --> 00:36:28,800
kind of beta for their, for their hosting customers. And

554
00:36:28,800 --> 00:36:34,510
I can see over time as this thing matures, There's

555
00:36:34,510 --> 00:36:39,210
definitely going to be... A lot of their customers that

556
00:36:39,210 --> 00:36:44,670
use this product. Of course. This is really interesting to

557
00:36:44,670 --> 00:36:48,210
me because what we saw over the last couple of

558
00:36:48,210 --> 00:36:53,099
years were remote recording tools like Riverside and these other

559
00:36:53,099 --> 00:36:56,760
companies. Adding hosting and now the tables have been flipped.

560
00:36:57,369 --> 00:37:04,110
Yeah, touche. Okay, D'Artagnan. That's right. I mean, two can

561
00:37:04,110 --> 00:37:07,099
play at that game, right? Well, I mean, this might

562
00:37:07,099 --> 00:37:09,639
be a big deal. I created my entire own play

563
00:37:09,639 --> 00:37:13,420
out system. You know, I was... You did, you did.

564
00:37:13,519 --> 00:37:17,159
I was stuck on Windows because I was using... Gosh,

565
00:37:17,159 --> 00:37:20,519
I don't remember the name of it now. Yeah. What

566
00:37:20,519 --> 00:37:23,329
was that play out system? Well, it was a Windows-based

567
00:37:23,329 --> 00:37:25,840
app. M Air List. Yeah, M Air List. Yes, thank

568
00:37:25,840 --> 00:37:28,220
you. And it was a good product, you know, and

569
00:37:28,220 --> 00:37:30,940
I paid my license fee. It was like 300 bucks.

570
00:37:31,940 --> 00:37:36,239
Not cheap, but it really worked well. And I was

571
00:37:36,239 --> 00:37:39,360
stuck on Windows because of it. And then I moved

572
00:37:39,360 --> 00:37:44,800
to Linux. I'm sorry. Omache. I'm sorry. GNU Linux. GNU

573
00:37:44,800 --> 00:37:51,940
Linux. Omache. Arch. And in an afternoon, I put the

574
00:37:51,940 --> 00:37:56,199
whole thing together. And I even made a remote version

575
00:37:56,199 --> 00:37:59,449
of it. Spun up a $5.00 Linode and said, "Hey,

576
00:37:59,449 --> 00:38:02,400
make this work on a web interface. It's all Python."

577
00:38:03,300 --> 00:38:08,619
Done. That's how fast it went. Done. Is somebody going

578
00:38:08,619 --> 00:38:15,579
to replace... You know, they're an entire ERP, Oracle ERP

579
00:38:15,579 --> 00:38:19,760
in an enterprise. No, but is, but this is where

580
00:38:19,760 --> 00:38:22,720
the, this right here is where the danger zone is

581
00:38:22,720 --> 00:38:27,409
for me. Like the, that Descript company, they got like

582
00:38:27,409 --> 00:38:30,460
some, they got something like, yeah. I want to say

583
00:38:30,460 --> 00:38:34,840
it's like $100 million of venture capital. Yeah. There's a

584
00:38:34,840 --> 00:38:37,579
lot of money tied up in some of these outfits,

585
00:38:37,579 --> 00:38:40,900
man. Yeah. Oh, yeah. And those guys are in the

586
00:38:40,900 --> 00:38:44,730
crosshairs of just like a few afternoons of vibe coding

587
00:38:44,730 --> 00:38:48,480
some stuff. Well, the way... I don't think there's going

588
00:38:48,480 --> 00:38:52,599
to be huge businesses of people making new software and

589
00:38:52,599 --> 00:38:55,139
selling it. You know, I always kind of chuckle at

590
00:38:55,139 --> 00:38:58,599
all these people who are making AI services. I'm like,

591
00:38:58,599 --> 00:39:01,369
okay, maybe, I don't know. But if you have an

592
00:39:01,369 --> 00:39:05,539
existing business and you just need something... And you want

593
00:39:05,539 --> 00:39:07,980
it to work a certain way. Yeah, Vibe. That's why

594
00:39:07,980 --> 00:39:13,420
I like Omachi GNU, Linux, Arch. Is because the agents

595
00:39:13,420 --> 00:39:16,400
just sit there and do it on your computer. You

596
00:39:16,400 --> 00:39:20,519
know, it doesn't have to work with Microsoft DLLs. Whatever.

597
00:39:21,000 --> 00:39:28,099
Microsoft. O-L-E. Yeah. Ole. Ole. No. No, it doesn't have

598
00:39:28,099 --> 00:39:30,260
to work with any of that. And it just works

599
00:39:30,260 --> 00:39:33,500
great. And Python is the language of these models. It

600
00:39:33,500 --> 00:39:37,389
just works fabulously well. You create something. And then, like

601
00:39:37,389 --> 00:39:40,519
yesterday, I was looking for a clip. I was doing

602
00:39:40,519 --> 00:39:43,610
the show with Rob Dew. I'm like, oh man, this

603
00:39:43,610 --> 00:39:46,610
is, it's not giving me the results I want. Cause

604
00:39:46,610 --> 00:39:49,800
I didn't know exactly how it was spelled. So, you

605
00:39:49,800 --> 00:39:52,289
know, you've got search, you got fuzzy search. And I

606
00:39:52,289 --> 00:39:54,110
just, you know, but hold on a second. I'm just

607
00:39:54,110 --> 00:39:57,250
going to bake a model search in here. And I

608
00:39:57,250 --> 00:39:59,980
literally did it while, while the robot was,

609
00:40:00,019 --> 00:40:03,610
doing the chapters. I'm like, oh, okay, boom. It just

610
00:40:03,610 --> 00:40:08,010
works. Perfect. It does exactly what I want it to

611
00:40:08,010 --> 00:40:11,280
do. And think about if you have to talk to

612
00:40:11,280 --> 00:40:13,980
the developer, got to put in a request, and maybe

613
00:40:13,980 --> 00:40:18,079
wait a couple months. And now it's just whatever I

614
00:40:18,079 --> 00:40:21,269
want. It just does it. And I'm not a software

615
00:40:21,269 --> 00:40:24,900
guy, but here I am. You're going to need an

616
00:40:24,900 --> 00:40:30,260
R. You may need. I don't necessarily think coders are

617
00:40:30,260 --> 00:40:33,269
going to lose their jobs. No, this is going to

618
00:40:33,269 --> 00:40:37,780
create a lot of extra productivity and probably more jobs.

619
00:40:38,139 --> 00:40:42,179
But it's definitely going to require an army of IT

620
00:40:42,179 --> 00:40:46,420
people and site reliability and SRE site reliability engineers to

621
00:40:46,420 --> 00:40:51,820
keep all this new flood of software going. humming. So,

622
00:40:51,820 --> 00:40:55,860
I mean, this is going to be an interesting thing

623
00:40:55,860 --> 00:40:58,380
to watch because I do think turnabout is fair play.

624
00:40:59,380 --> 00:41:06,519
Turnabout? Yeah, like... Like they're going to... You know, the

625
00:41:06,519 --> 00:41:08,739
hosting companies are going to start pushing back and all

626
00:41:08,739 --> 00:41:11,730
these other people that added hosting. Because you're going to,

627
00:41:11,730 --> 00:41:15,460
you already see people making apps, podcast apps, stuff like

628
00:41:15,460 --> 00:41:17,579
that. I mean, we're going to see, I think we're

629
00:41:17,579 --> 00:41:20,559
going to see an explosion of software. Yes. Oh, we're

630
00:41:20,559 --> 00:41:23,599
already seeing that. We know from Paul. Just the delays

631
00:41:23,599 --> 00:41:25,920
on the app stores. Or if you don't need Paul,

632
00:41:25,920 --> 00:41:29,610
just go look at what's his face from. What's his

633
00:41:29,610 --> 00:41:33,210
face? Yeah. From the, what's his face? The Apple guy

634
00:41:33,210 --> 00:41:38,340
with his podcast app and his 5,000 Mac minis. Oh,

635
00:41:38,340 --> 00:41:42,030
Marco. Marco. What's his face? Marco. What's his face? You

636
00:41:42,030 --> 00:41:44,480
know, he's like, oh, it was taking forever to get

637
00:41:44,480 --> 00:41:49,380
my app approved. Yeah. That's because everyone's baking apps. And

638
00:41:49,380 --> 00:41:52,679
that's going to be, eventually, where this will wind up,

639
00:41:52,679 --> 00:41:54,880
everyone's going back to the browser. It's going to be

640
00:41:54,880 --> 00:42:00,559
too many apps. True. The browser is perfect. The pie

641
00:42:00,559 --> 00:42:07,170
came back. Yes. It says done. Reboot. Reboot. Reboot. All

642
00:42:07,170 --> 00:42:11,679
right. I'm rebooting right now. Reboot. Your five workspace layout

643
00:42:11,679 --> 00:42:13,789
is now saved and will be restored at boot. Here's

644
00:42:13,789 --> 00:42:16,159
what's in place. Blah, blah, blah, blah, blah. It says

645
00:42:16,159 --> 00:42:21,699
how it restores at boot. Your dot local slash bin

646
00:42:21,699 --> 00:42:25,679
hyper session restore hooked via a bunch of stuff. I

647
00:42:25,679 --> 00:42:28,920
don't understand. A bunch of a bunch of hyper hyper

648
00:42:28,920 --> 00:42:36,130
land startup configuration. Yeah, that sounds right. Yeah. Verified are

649
00:42:36,130 --> 00:42:40,219
clean and blah, blah, blah. All right. After the show.

650
00:42:40,559 --> 00:42:43,159
You're going to do it, man. I'm going to reboot.

651
00:42:43,480 --> 00:42:45,730
Yeah. I mean, there's little things that I've had to

652
00:42:45,730 --> 00:42:50,150
do. Like, I want Workspace 9 to be on the

653
00:42:50,150 --> 00:42:54,360
secondary monitor on the right. You can hard code that

654
00:42:54,360 --> 00:42:58,239
in. So, you know, because we have multiple monitors and

655
00:42:58,239 --> 00:43:02,400
you start off with vanilla. See, the hard part is

656
00:43:02,400 --> 00:43:05,730
I want the apps and everything to start themselves. Launching

657
00:43:05,730 --> 00:43:08,829
Brave is fine, but I want it to go right

658
00:43:08,829 --> 00:43:11,659
back into Pi. It'll do it. Yeah, it'll do it.

659
00:43:11,659 --> 00:43:13,780
It'll do all that. It'll do all that. And it

660
00:43:13,780 --> 00:43:20,590
will make you an Americano. a pour over I'm sorry

661
00:43:20,590 --> 00:43:23,460
we only have pour over alright so let's talk about

662
00:43:23,460 --> 00:43:27,559
the scary stuff That sounds like you're talking about refactor.

663
00:43:27,699 --> 00:43:31,199
That's exactly what I'm talking about. The scary stuff. Yeah.

664
00:43:31,699 --> 00:43:35,780
So now do we have 11,000 podcasts that need to

665
00:43:35,780 --> 00:43:38,210
be reconciled? Is that where we're at now and someone

666
00:43:38,210 --> 00:43:42,829
has to go through this list? no no no not

667
00:43:42,829 --> 00:43:47,050
necessarily if that's true you're doing it not me here's

668
00:43:47,050 --> 00:43:49,889
what everybody wants we want docs man give us docs

669
00:43:49,889 --> 00:43:52,449
what are you doing do we have to refactor our

670
00:43:52,449 --> 00:44:00,820
whole podcast app what's happening dave docs the So... Let

671
00:44:00,820 --> 00:44:05,699
me see. Where are we? The... I keep hitting edge

672
00:44:05,699 --> 00:44:10,070
cases. Not many. Two or three. Spurlock sent me one

673
00:44:10,070 --> 00:44:12,900
a couple days ago and got that one figured out.

674
00:44:13,340 --> 00:44:16,800
It affected four podcasts. That's the point we're at now.

675
00:44:16,980 --> 00:44:22,139
We're talking about twos and threes and fours. Okay. Um,

676
00:44:24,000 --> 00:44:26,769
So Mitch was asking, do I have to refactor the

677
00:44:26,769 --> 00:44:30,470
entire pod verse next gen for this thing? And no,

678
00:44:30,470 --> 00:44:32,989
the answer is if I did my job right, then

679
00:44:32,989 --> 00:44:40,630
no. Right. Which is a very comforting answer. I tried

680
00:44:40,630 --> 00:44:45,320
to express that through a couple of very hard to

681
00:44:45,320 --> 00:44:50,679
understand scanned Pieces of paper with drawings all over them.

682
00:44:51,000 --> 00:44:54,199
It didn't help the comfort zone. I'll be honest about

683
00:44:54,199 --> 00:44:57,239
it. It looked like you're building a nuclear device. And

684
00:44:57,239 --> 00:45:00,420
it was like the little circles and bits and bobs

685
00:45:00,420 --> 00:45:04,760
and like, okay, I guess that's good. I hope it

686
00:45:04,760 --> 00:45:12,239
is. Um, so... The... What I was trying to express

687
00:45:12,239 --> 00:45:19,389
with those poor drawings is... that there is a... As

688
00:45:19,389 --> 00:45:24,730
we've talked about before, there's the new podcast table with

689
00:45:24,730 --> 00:45:30,730
this notion of... of a podcast that can point to

690
00:45:30,730 --> 00:45:35,920
a feed. It's not it's not everything's not just feeds.

691
00:45:37,909 --> 00:45:43,769
And so that brings up some interesting sort of internal

692
00:45:43,769 --> 00:45:49,659
routing stuff. Mm-hmm. And you can think of it –

693
00:45:49,659 --> 00:45:54,159
so think about it from the API's direction, okay? The

694
00:45:54,159 --> 00:45:58,449
API gives some endpoints. One of them is podcasts by

695
00:45:58,449 --> 00:46:04,179
feed URL. And another one is podcast by feed ID.

696
00:46:07,059 --> 00:46:14,400
And when... If you think about What you're asking, you're

697
00:46:14,400 --> 00:46:19,139
saying, okay, I want information about podcasts by feed ID,

698
00:46:19,139 --> 00:46:21,699
and the ID I'm going to give you is 920666,

699
00:46:21,699 --> 00:46:26,970
which is this show. When you come in, what the

700
00:46:26,970 --> 00:46:30,869
expectation has been in the past when you make that

701
00:46:30,869 --> 00:46:34,389
call to the API is that you are asking for

702
00:46:34,389 --> 00:46:40,429
a podcast RSS feed with ID 920666. And you don't

703
00:46:40,429 --> 00:46:43,029
care what the URL is. You don't know what the

704
00:46:43,029 --> 00:46:47,619
URL is. You just know that. You know that this...

705
00:46:48,529 --> 00:46:53,349
Feed ID is 920666. Well, this is a pretty exact

706
00:46:53,349 --> 00:47:00,599
analogy to the podcast identity. Because from the outside, you

707
00:47:00,599 --> 00:47:06,750
quickly start to think of... ID 920666, not as the

708
00:47:06,750 --> 00:47:11,900
feed, but as the podcast. Right. No agenda is 41504.

709
00:47:12,059 --> 00:47:19,260
Podcasting 2.0 is 920666. And... That you begin to mentally

710
00:47:19,260 --> 00:47:23,800
associate that with the show, not the feed. So that's,

711
00:47:23,800 --> 00:47:28,369
you could call that the ID entrance. Okay, so you

712
00:47:28,369 --> 00:47:32,639
think about, I'm coming in through the door that is

713
00:47:32,639 --> 00:47:36,500
the ID of the show. Then you have sort of

714
00:47:36,500 --> 00:47:40,010
another door into the database or into the index, which

715
00:47:40,010 --> 00:47:44,119
is the URL. So now you're saying I want to

716
00:47:44,119 --> 00:47:48,989
come in on – you're saying give me the URL

717
00:47:48,989 --> 00:47:58,659
podcast by feed URL. And it's feeds.podcastindex.org slash pc20.xml. So

718
00:47:58,659 --> 00:48:05,050
that's our RSS feed. Depending on which sort of route

719
00:48:05,050 --> 00:48:09,639
you take into the index through the API, whether it's

720
00:48:09,639 --> 00:48:15,309
through the ID, the GUID, the URL, you should always

721
00:48:15,309 --> 00:48:22,239
get the same response or the same data back. Because...

722
00:48:22,329 --> 00:48:25,470
If you're at what you're really wanting is a show,

723
00:48:25,470 --> 00:48:29,559
no matter how you slice it, you're wanting that show.

724
00:48:31,130 --> 00:48:37,199
Because you don't necessarily... The index is acting in an

725
00:48:37,199 --> 00:48:44,239
authoritative role. So, you may have an old feed URL.

726
00:48:45,809 --> 00:48:49,860
And that feed URL may be a 404 now, but

727
00:48:49,860 --> 00:48:53,380
what you're wanting is the show. And so if you

728
00:48:53,380 --> 00:48:56,380
ask for that feed URL, you're going to be a

729
00:48:56,380 --> 00:49:00,199
404 now. from the index, what it's going to do

730
00:49:01,440 --> 00:49:06,389
is it's going to route you to the correct current

731
00:49:06,389 --> 00:49:11,699
feed URL. It's going to still give you information about

732
00:49:11,699 --> 00:49:15,159
that old one. Like, hey, it's dead. But – and

733
00:49:15,159 --> 00:49:18,570
it's going to intelligently say, okay, this feed URL you're

734
00:49:18,570 --> 00:49:23,039
wanting, that thing's dead now. But the show continues with

735
00:49:23,039 --> 00:49:27,960
this other feed. And so you can think of it

736
00:49:27,960 --> 00:49:36,869
sort of like, like, you know, Since this... This new

737
00:49:36,869 --> 00:49:40,550
approach is sort of like, it's not entirely like an

738
00:49:40,550 --> 00:49:45,269
apophatic process, but it's much more balanced in how it

739
00:49:45,269 --> 00:49:49,820
traces the request criteria through the API to give you

740
00:49:49,820 --> 00:49:57,139
a response. And that... So what I mean is if

741
00:49:57,139 --> 00:49:59,699
you come in through the ID door,

742
00:50:00,059 --> 00:50:02,179
It's just going to walk up the chain to the

743
00:50:02,179 --> 00:50:06,949
podcast's table and, and give you back. It's going to

744
00:50:06,949 --> 00:50:10,329
walk up to the podcast table, find the current, see

745
00:50:10,329 --> 00:50:15,679
if those IDs match. The podcast ID matches the feed

746
00:50:15,679 --> 00:50:19,349
ID you asked for. If they do, it's just going

747
00:50:19,349 --> 00:50:23,010
to give you the same data back. If they don't

748
00:50:23,010 --> 00:50:23,980
match, you're going to give you the same data back.

749
00:50:25,000 --> 00:50:28,969
It's going to then go find what the current feed

750
00:50:28,969 --> 00:50:32,059
ID is and serve you that one. So that's the

751
00:50:32,059 --> 00:50:37,320
desired behavior. That's correct. Yeah. So that means that the

752
00:50:37,320 --> 00:50:42,460
people consuming the API... should not have to change anything

753
00:50:42,460 --> 00:50:46,510
about the way that they are calling it. They're just

754
00:50:46,510 --> 00:50:50,420
always going to get the correct data now. Yeah, it's

755
00:50:50,420 --> 00:50:54,320
the ISBN number for podcasts. Which is what we wanted

756
00:50:54,320 --> 00:50:57,010
to make. From day one. From day one. Why didn't

757
00:50:57,010 --> 00:50:59,210
we do that? What happened? Why did we decide against

758
00:50:59,210 --> 00:51:02,980
that? Well, it's just that this concept was a little

759
00:51:02,980 --> 00:51:07,679
bit too blurry. We weren't powerful enough. I don't think

760
00:51:07,679 --> 00:51:11,840
it was that. I think it's... So think of it

761
00:51:11,840 --> 00:51:17,239
this way. Since the podcast is... Since a podcast, excuse

762
00:51:17,239 --> 00:51:22,519
me, is just a concept we infer... From the data

763
00:51:22,519 --> 00:51:26,679
that's inside of a feed. What you end up is

764
00:51:26,679 --> 00:51:31,840
sometimes you're hamstrung. So what if the show changes its

765
00:51:31,840 --> 00:51:35,070
name? It's like, what if, what if no agenda changed

766
00:51:35,070 --> 00:51:39,659
its name to Adam's, Adam's on fire? Is it still

767
00:51:39,659 --> 00:51:49,139
the same show? Maybe? Sort of? Like, it's what you...

768
00:51:49,900 --> 00:51:52,489
It's what you intended, but it doesn't really match like

769
00:51:52,489 --> 00:51:55,739
normal expectation. There's a tension there is what I'm trying

770
00:51:55,739 --> 00:51:58,960
to say. And there's different degrees of this. So like

771
00:51:58,960 --> 00:52:02,519
you, there's a podcast I listen to called The Incomparable.

772
00:52:03,260 --> 00:52:05,480
And it changed its name a few years ago to

773
00:52:05,480 --> 00:52:09,329
be The Incomparable Mothership because then they have some spinoff

774
00:52:09,329 --> 00:52:14,780
shows. Well, clearly that. show, The Incomparable Mothership, is intended

775
00:52:14,780 --> 00:52:17,420
to be the same show. It just changed its name.

776
00:52:18,539 --> 00:52:23,019
Now, I understand that, but there's other shows that really

777
00:52:23,019 --> 00:52:25,610
just use the value of the feed, and it's a

778
00:52:25,610 --> 00:52:30,860
different show altogether. If you just key on – if

779
00:52:30,860 --> 00:52:34,780
you just key on the data inside the feed, it's

780
00:52:34,780 --> 00:52:38,670
very difficult to make some of these determinations. So what

781
00:52:38,670 --> 00:52:45,659
we tried to do all these years was – I

782
00:52:45,659 --> 00:52:49,190
didn't follow redirections. Of course, we're still doing that, all

783
00:52:49,190 --> 00:52:52,719
that kind of stuff. Follow the redirects. Look at the

784
00:52:52,719 --> 00:52:56,260
iTunes new feed URL tag, all these kinds of things.

785
00:52:56,280 --> 00:52:59,760
We're trying to follow these things. But then at some

786
00:52:59,760 --> 00:53:03,599
point, like the feed itself, you fall back and say,

787
00:53:03,599 --> 00:53:05,659
okay, you've got to tell me what you are now

788
00:53:05,659 --> 00:53:08,800
because we don't know. So the feed becomes sort of

789
00:53:08,800 --> 00:53:11,699
this technical authority, even though it may not always be

790
00:53:11,699 --> 00:53:18,980
telling you a full story. About what's happening. This new

791
00:53:18,980 --> 00:53:27,760
layout... Yeah, it gives you a... A breadcrumb trail. Yes.

792
00:53:28,539 --> 00:53:31,809
Like I said, it's an apophatic process. So it's really

793
00:53:31,809 --> 00:53:35,179
telling you what it is. You've said this twice now.

794
00:53:35,880 --> 00:53:38,860
Well, it's a little annoying. I'm sorry. Hold on. I

795
00:53:38,860 --> 00:53:41,869
don't. Hold on a second. Book of Knowledge. Give me

796
00:53:41,869 --> 00:53:48,099
the definition of apophatic. Thank you. I need to understand.

797
00:53:48,480 --> 00:53:51,429
According to the Book of Knowledge, apophatic refers to a

798
00:53:51,429 --> 00:53:55,719
theological method of describing God or the divine by negation.

799
00:53:55,800 --> 00:53:59,460
What? Stating only what cannot be said about the divine

800
00:53:59,460 --> 00:54:03,500
rather than what can, since the divine transcends all human

801
00:54:03,500 --> 00:54:09,179
concepts and language. Huh? Thus... It has been written. Okay.

802
00:54:09,559 --> 00:54:13,519
Did I get the wrong definition? No, it's right. But

803
00:54:13,519 --> 00:54:17,789
I think it's used more generally than that. Like, because

804
00:54:17,789 --> 00:54:22,059
basically it's trying to decide what something is by clearly

805
00:54:22,059 --> 00:54:27,760
expressing what it's not. Ah, describing God or the divine

806
00:54:27,760 --> 00:54:31,860
by negation. Okay. So just right. Okay. Apophatic. I'm going

807
00:54:31,860 --> 00:54:36,440
to use this. You are not ugly, Tina. Is that

808
00:54:36,440 --> 00:54:41,349
a correct apophatic? You're not going to get lucky that

809
00:54:41,349 --> 00:54:46,949
way, but you can try it. Okay. I think it's

810
00:54:46,949 --> 00:54:50,079
just like this is more this takes more of the

811
00:54:50,079 --> 00:54:54,670
negative side of these things into account because now you're

812
00:54:54,670 --> 00:54:58,309
saying we know it's we know that whatever this show

813
00:54:58,309 --> 00:55:01,889
is, we know it's not these it's not these other

814
00:55:01,889 --> 00:55:05,309
things. We know it's not these other feeds. And so

815
00:55:05,309 --> 00:55:09,849
that becomes sort of an important factor in trying to

816
00:55:09,849 --> 00:55:14,420
define what it is. is first expressing what it is

817
00:55:14,420 --> 00:55:19,059
not. Okay. Because if you have potentially five different feeds

818
00:55:19,059 --> 00:55:21,800
that all claim to be a particular show, if you

819
00:55:21,800 --> 00:55:24,980
know which four aren't that show, the one that's left

820
00:55:24,980 --> 00:55:30,039
logically is the thing that you... is correct. Mm-hmm. And

821
00:55:30,039 --> 00:55:36,360
then you just... work your process back from that. And

822
00:55:36,360 --> 00:55:42,239
express that in what the podcast table is. Right. So

823
00:55:42,239 --> 00:55:46,289
it's more, like I say, it's not totally a negative

824
00:55:46,289 --> 00:55:53,279
thing. process, but it's balanced. Whereas before we're just like,

825
00:55:53,279 --> 00:55:55,420
okay, well, these five feeds, they all tell me they're

826
00:55:55,420 --> 00:55:57,519
this. I don't know which one's right. I mean, it

827
00:55:57,519 --> 00:55:59,800
could be this one. It could be this other one.

828
00:55:59,800 --> 00:56:03,949
I don't know. I mean, I guess we're just going

829
00:56:03,949 --> 00:56:08,559
to leave it or make funky columns with duplicate of

830
00:56:08,559 --> 00:56:12,920
IDs in them. So I feel like this is a

831
00:56:12,920 --> 00:56:17,820
more robust process, except you have a third factor in

832
00:56:17,820 --> 00:56:21,360
there, which is the iTunes ID. And that's and excuse

833
00:56:21,360 --> 00:56:24,250
me, even if we have a fourth factor, too, which

834
00:56:24,250 --> 00:56:27,670
is the podcast good. So we're having to sort of

835
00:56:27,670 --> 00:56:34,659
like mung all these things together. And some things are

836
00:56:34,659 --> 00:56:41,470
not... Some things are not here, like heuristically munchable, you

837
00:56:41,470 --> 00:56:44,960
know, like, I mean, they're, they're not really, they don't,

838
00:56:44,960 --> 00:56:48,210
they don't really make that process very easy. So that's

839
00:56:48,210 --> 00:56:51,630
where all these edge cases are coming from. And it's

840
00:56:51,630 --> 00:56:54,119
just like, say, it's two, three, four here and there.

841
00:56:54,260 --> 00:56:56,679
It's not the end of the world, but what's going

842
00:56:56,679 --> 00:57:00,039
to come out of this in the. And people, there

843
00:57:00,039 --> 00:57:02,809
are some people who really want to see the history

844
00:57:02,809 --> 00:57:05,970
of all the feeds. That is still there. It still

845
00:57:05,970 --> 00:57:09,470
exists. The feeds table is still complete. All that's still,

846
00:57:09,470 --> 00:57:13,070
the weekly database dump is a dump of the feeds

847
00:57:13,070 --> 00:57:18,000
table. It just has podcast IDs as a separate column

848
00:57:18,000 --> 00:57:23,460
now. Mm-hmm. And so you can trace what happens. And

849
00:57:23,460 --> 00:57:28,989
one of the greatest things about this refactor has been

850
00:57:28,989 --> 00:57:34,519
that as the farther down this trail we go, the

851
00:57:34,519 --> 00:57:42,750
auditing of this stuff becomes so much better. Like it's

852
00:57:42,750 --> 00:57:47,019
already amazing to, to be able to troubleshoot this because

853
00:57:47,019 --> 00:57:49,699
I, in trying to find these edge cases, I had

854
00:57:49,699 --> 00:57:52,320
to this, I had a show this morning that I

855
00:57:52,320 --> 00:57:55,720
was trying to figure out what was going on with.

856
00:57:56,579 --> 00:57:58,599
And I've got a script now that I can run

857
00:57:58,599 --> 00:58:01,699
and it gives you like a narrative overview. It's like,

858
00:58:02,099 --> 00:58:05,699
Oh, well, here's what this feed was born on this

859
00:58:05,699 --> 00:58:09,539
date and then on transistor. And then it went to

860
00:58:09,539 --> 00:58:12,769
anchor and then it did. And then it went to

861
00:58:12,769 --> 00:58:15,980
RSS.com on this date. And then it's a good change.

862
00:58:15,980 --> 00:58:19,800
It's like you get a full like, like, like biography

863
00:58:19,800 --> 00:58:24,500
of every podcast podcast. And all the feeds that it

864
00:58:24,500 --> 00:58:27,889
has lived under this whole time, it's going to be

865
00:58:27,889 --> 00:58:33,340
a really cool thing when it's done. And we're almost

866
00:58:33,340 --> 00:58:37,349
there. We're almost there. I got... The endpoints, I've got

867
00:58:37,349 --> 00:58:40,570
to finish pushing those out. The reader endpoints, the ingestion

868
00:58:40,570 --> 00:58:46,369
pipelines already built. But the just like data reading endpoints,

869
00:58:46,369 --> 00:58:49,619
those are what's going on. And every, before I do

870
00:58:49,619 --> 00:58:53,849
it, I've got, like, I'm very dependent on AI coding

871
00:58:53,849 --> 00:58:57,239
for this thing, for this refactor. And every time I,

872
00:58:57,239 --> 00:58:59,970
before I push out a new, an endpoint, I pushed

873
00:58:59,970 --> 00:59:03,199
out the, what was it? iTunes ID one this morning.

874
00:59:04,199 --> 00:59:06,210
And before I push each one out, I just do

875
00:59:06,210 --> 00:59:10,279
like, I'm like, okay, do a full court press review

876
00:59:10,279 --> 00:59:13,800
on this code, find any bugs. Right. Right. Let's run,

877
00:59:13,800 --> 00:59:16,619
you know, look for test gaps. And I just try

878
00:59:16,619 --> 00:59:19,050
to try to hit it over and over. And inevitably,

879
00:59:19,050 --> 00:59:22,489
it always finds a couple of things. And so that's

880
00:59:22,489 --> 00:59:25,690
why I'm doing them at most one day, one per

881
00:59:25,690 --> 00:59:31,820
day. And then watch the logs overnight, check it again.

882
00:59:32,619 --> 00:59:36,860
And then there's a couple scripts I'm running that will

883
00:59:36,860 --> 00:59:42,929
look for drift. And there's usually one or two a

884
00:59:42,929 --> 00:59:47,880
day. So things are looking really good, but there's also

885
00:59:47,880 --> 00:59:51,949
some cron jobs now running that try to auto clean

886
00:59:51,949 --> 00:59:58,260
the. Yeah, make no mistakes. Yeah, that's the critical point.

887
00:59:58,340 --> 00:59:59,340
You got to tell it not to make mistakes.

888
01:00:00,320 --> 01:00:03,809
Um, so then you, but there's a couple of cron

889
01:00:03,809 --> 01:00:06,260
jobs now that are running that will try to auto

890
01:00:06,260 --> 01:00:10,480
correct this, this thing. So we, we have so much

891
01:00:10,480 --> 01:00:18,000
data now that is corroborative. So you have the URLs.

892
01:00:18,170 --> 01:00:22,570
of the feeds. You have the podcast table. You got

893
01:00:22,570 --> 01:00:28,340
the redirects, GUIDs, iTunes IDs. There's a rich body of

894
01:00:29,469 --> 01:00:33,360
things to pull from to make a determination about what,

895
01:00:33,360 --> 01:00:36,900
about what is the correct feed URL for this podcast

896
01:00:36,900 --> 01:00:40,280
at this moment. Man, we are fixing you, not we,

897
01:00:40,380 --> 01:00:45,820
but you are fixing everybody else's mistakes. that's basically what's

898
01:00:45,820 --> 01:00:48,579
happening. There's going to be a few manual, you know,

899
01:00:48,599 --> 01:00:49,769
there's going to, there's going to be always be a

900
01:00:49,769 --> 01:00:53,019
few, but I'm hoping it's just not, it's the, I'm

901
01:00:53,019 --> 01:00:59,739
hoping to, here's my, here's my, wish hmm is that

902
01:00:59,739 --> 01:01:02,039
we have, is that at the end of this process,

903
01:01:02,039 --> 01:01:06,199
we end up with a pipeline. of excuse me not

904
01:01:06,199 --> 01:01:15,269
a pipeline a feed of of podcasts which changed, which

905
01:01:15,269 --> 01:01:21,019
we cannot automatically correct And there's just maybe a handful

906
01:01:21,019 --> 01:01:24,239
a week. And it's enough to where we can all

907
01:01:24,239 --> 01:01:27,539
just pitch in, eyeball it a couple times a week,

908
01:01:27,539 --> 01:01:32,519
and it's very easily maintainable. Okay. That would be the

909
01:01:32,519 --> 01:01:41,110
great outcome. A community dashboard. Oh, yes. Community dashboard. That's

910
01:01:41,110 --> 01:01:43,619
what I like driving with everybody looking at the dashboard.

911
01:01:43,860 --> 01:01:46,070
I love that. That's my favorite. And heads up, the

912
01:01:46,070 --> 01:01:49,969
feed management dashboard on the API, that thing's going to

913
01:01:49,969 --> 01:01:52,480
have to change. Do you have access to go there

914
01:01:52,480 --> 01:01:55,960
and look at it right now? Yeah. I need to,

915
01:01:55,960 --> 01:01:57,789
because I need to tell you something. Okay. Hold on

916
01:01:57,789 --> 01:02:03,500
a second. All right. Dashboard. Which, where do I want

917
01:02:03,500 --> 01:02:05,889
to be? Where do I want to be? Just search

918
01:02:05,889 --> 01:02:13,059
for a feed, like a 920666. 920666. Boom. Okay. That's

919
01:02:13,059 --> 01:02:17,960
not us. Oh, that was 820. Hold on. 920666. Okay.

920
01:02:18,099 --> 01:02:22,639
Podcasting 2.0. I'm there. Yeah. Okay. Okay. Look right next

921
01:02:22,639 --> 01:02:27,409
to the number. You see it says podcast 920666 with

922
01:02:27,409 --> 01:02:30,469
a little badge. Yeah. And a little question mark pops

923
01:02:30,469 --> 01:02:34,119
up. Yeah, if you hover over it, it should say

924
01:02:34,119 --> 01:02:37,800
this feed is its current feed, which is a terrible

925
01:02:37,800 --> 01:02:41,559
grammar. I'm disappointed that you put two dashes instead of

926
01:02:41,559 --> 01:02:44,750
an M dash, but okay, I'll accept it. Okay, so

927
01:02:44,750 --> 01:02:51,130
this currently this in the dashboard is how you associate

928
01:02:51,130 --> 01:02:59,860
this feed. With a podcast. Got it. Um... 920666 is

929
01:02:59,860 --> 01:03:03,179
the feed ID. And what this is telling you is

930
01:03:03,179 --> 01:03:09,710
the podcast ID is 920666 also. Mm-hmm. If you want

931
01:03:09,710 --> 01:03:16,940
to see a different version of that, then go to...

932
01:03:18,210 --> 01:03:29,480
Search search for 803 803-4392. Okay. Ruben Comics Podcast. Ah,

933
01:03:29,480 --> 01:03:32,679
this feed is its current feed. Reach through Merged Away

934
01:03:32,679 --> 01:03:39,179
Podcast, 803-4392. Okay, I see it. This is telling you

935
01:03:39,179 --> 01:03:50,590
that feed 803-4392 is the feed for podcast 567-3693. That

936
01:03:50,590 --> 01:03:55,679
is very confusing. Mm-hmm. But it's only confusing because this

937
01:03:55,679 --> 01:04:01,639
dashboard was never engineered to show you a podcast layer.

938
01:04:01,780 --> 01:04:04,210
It was meant to show you feeds. And that's what

939
01:04:04,210 --> 01:04:06,969
it's still showing you. So there's going to have to

940
01:04:06,969 --> 01:04:10,389
be a refactoring of this dashboard after this whole thing

941
01:04:10,389 --> 01:04:15,380
is finished to make it podcast centric instead of podcast.

942
01:04:15,000 --> 01:04:17,340
Feed-centric so that you're going to see the podcast and

943
01:04:17,340 --> 01:04:21,820
then you'll see the feeds as sort of children underneath

944
01:04:21,820 --> 01:04:28,900
them. Mm-hmm. So for now, this is confusing, but it's,

945
01:04:28,900 --> 01:04:32,599
it at least gives you some sense of, of what

946
01:04:32,599 --> 01:04:34,829
you're looking at, even though it's going to take a

947
01:04:34,829 --> 01:04:38,599
few seconds to register what's happening in your brain. Yeah.

948
01:04:41,220 --> 01:04:44,500
Yeah, so that's where things stand. We're getting close. We're

949
01:04:44,500 --> 01:04:49,260
getting close. Well, you are my hero, Dave Jones, I

950
01:04:49,260 --> 01:04:51,599
have to say. I should be no one's hero. You

951
01:04:51,599 --> 01:04:53,920
are my hero. You are. You are the wind beneath

952
01:04:53,920 --> 01:04:59,679
my wings. Ha ha ha. Thank you, Barbara. Was that

953
01:04:59,679 --> 01:05:04,279
Barbara Streisand? No, that was... You are the... No, Bette

954
01:05:04,279 --> 01:05:09,920
Midler. Bette Midler, that's right. Beaches. What else do we

955
01:05:09,920 --> 01:05:13,199
need to talk about today? Is there anything else that

956
01:05:13,199 --> 01:05:18,429
was... What have you got? I've been talking. What do

957
01:05:18,429 --> 01:05:21,230
you got? No, I got nothing. I'm just, I'm just

958
01:05:21,230 --> 01:05:27,989
here to run the board. That, um, Pod ping, I

959
01:05:27,989 --> 01:05:34,139
haven't forgotten about pod ping. Yes. It's just... And this,

960
01:05:34,139 --> 01:05:36,739
this just became the most important thing. No, I understand.

961
01:05:37,099 --> 01:05:41,070
I think everybody understands. As happening. I mean, hey, Citizen

962
01:05:41,070 --> 01:05:43,970
updated his bathroom. So I think we're good. The bathroom

963
01:05:43,970 --> 01:05:48,820
is updated. We're good. It's up to date. And so

964
01:05:48,820 --> 01:05:55,320
we will all get back to that project soon. But

965
01:05:55,320 --> 01:06:01,110
I think we have to finish this up. Man, you

966
01:06:01,110 --> 01:06:04,510
do an incredible amount of work with your one hour

967
01:06:04,510 --> 01:06:07,840
a day. It's truly unbelievable. And it's been a little

968
01:06:07,840 --> 01:06:10,579
bit more than that lately. I've been throwing some night

969
01:06:10,579 --> 01:06:13,099
work in too, but I try not to do that

970
01:06:13,099 --> 01:06:16,920
because I want to spend some family time. Yeah. It's

971
01:06:16,920 --> 01:06:20,779
just I got to get this... project off the board.

972
01:06:20,920 --> 01:06:24,059
I just hope that I can know that somehow we

973
01:06:24,059 --> 01:06:30,029
can remove the very low level irritation, anger from your

974
01:06:30,029 --> 01:06:32,889
life because that's not good. That's not healthy. It's just

975
01:06:32,889 --> 01:06:36,380
not good. It's not good. I've always been that way

976
01:06:36,380 --> 01:06:40,739
because and I think it's just I really do think

977
01:06:40,739 --> 01:06:44,360
it's the technology thing. Technology is a two-edged sword, man.

978
01:06:44,960 --> 01:06:48,420
Yeah. I really do hate, in my younger years, it

979
01:06:48,420 --> 01:06:53,340
was exciting enough and dopamine, what's that word, dopaminergic enough?

980
01:06:53,480 --> 01:06:57,440
Yeah. To where you just sort of get, you overlook

981
01:06:57,440 --> 01:07:02,139
the frustration and the annoyance. annoying parts. Yeah. But as

982
01:07:02,139 --> 01:07:07,630
you get older and life becomes more varied and Your

983
01:07:07,630 --> 01:07:12,550
responsibilities go all over the place. Those small things that

984
01:07:12,550 --> 01:07:15,900
you used to overlook become just, they become such a

985
01:07:15,900 --> 01:07:21,590
pain. And, you know, if I, there's too much, I

986
01:07:21,590 --> 01:07:25,500
think there's generally speaking too much technology in every, in

987
01:07:25,500 --> 01:07:30,289
all of our lives. Oh, of course. Absolutely. I'm blown

988
01:07:30,289 --> 01:07:34,440
away by screen time numbers still to this day. Seven

989
01:07:34,440 --> 01:07:38,610
hours a day, people are on their screens. Wow. And

990
01:07:38,610 --> 01:07:41,679
that's their phone or their iPad. It's not like a

991
01:07:41,679 --> 01:07:44,750
computer. If you're at work, I understand you got screen

992
01:07:44,750 --> 01:07:49,220
time because you're doing stuff. But I'm just like, it's

993
01:07:49,220 --> 01:07:54,179
not good. What is my screen time? Let's see. That's

994
01:07:54,179 --> 01:07:56,750
why podcasting is so good because you just turn the

995
01:07:56,750 --> 01:07:59,699
screen off, put it in your pocket, and you're good

996
01:07:59,699 --> 01:08:04,579
to go. Bob's your uncle. Let's see. One hour and

997
01:08:04,579 --> 01:08:11,029
34 minutes. For today? That's average. Really? What were you

998
01:08:11,029 --> 01:08:19,020
doing? That's probably toilet scrolling. Let me see screen time.

999
01:08:19,100 --> 01:08:24,250
Do I have that screen? Why does it not show

1000
01:08:24,250 --> 01:08:29,720
up here? Screen time. Would it be usage? Usage. Can

1001
01:08:29,720 --> 01:08:32,909
you get that on Android? Yeah, of course. Usage and

1002
01:08:32,909 --> 01:08:41,829
diagnostics. Okay. Usage. Uh... No. That's got to be in

1003
01:08:41,829 --> 01:08:50,250
here. It's probably under apps or something. Mmm. Huh. An

1004
01:08:50,250 --> 01:08:53,039
hour and 34 minutes. That seems high. I don't even

1005
01:08:53,039 --> 01:09:00,079
know where that is. Maybe apps. Apps. Oh, come on.

1006
01:09:00,100 --> 01:09:01,460
There's got to be a way to do it. What

1007
01:09:01,460 --> 01:09:04,440
are we looking for? I'm looking for. Go to Claude.

1008
01:09:05,720 --> 01:09:09,789
I'm looking for. Oh, yes, I agree. I agree. I'm

1009
01:09:09,789 --> 01:09:16,680
looking for screen time. See, this is a perfect example

1010
01:09:16,680 --> 01:09:20,079
of like, I agree, I agree. It's like all these

1011
01:09:20,079 --> 01:09:25,300
paper. Oh, yeah. No, it's horrible. Okay. Screen time today.

1012
01:09:26,100 --> 01:09:31,859
My Lord. Well, that's not entirely fair. What is it?

1013
01:09:31,920 --> 01:09:34,359
Come on, fess up. It's three hours and 41 minutes,

1014
01:09:34,359 --> 01:09:39,100
of which two hours and eight minutes is Obsidian. Obsidian.

1015
01:09:39,300 --> 01:09:43,039
Yeah. That's my whole life. My life runs on Obsidian.

1016
01:09:43,199 --> 01:09:47,140
Thank you very much, Alex Gates. It runs on Obsidian.

1017
01:09:47,239 --> 01:09:49,520
So I'm listening to clips, you know, that I store

1018
01:09:49,520 --> 01:09:54,079
stuff in Obsidian. Brave, only 25 minutes, and Canine Male,

1019
01:09:54,079 --> 01:09:58,940
only 14 minutes. So I feel pretty good. Canine male?

1020
01:09:59,279 --> 01:09:59,979
What is...

1021
01:10:00,010 --> 01:10:02,920
Is this a web mail? No, it's open source Android

1022
01:10:02,920 --> 01:10:07,600
email client. I've been using that for years. It's great.

1023
01:10:08,560 --> 01:10:12,310
Okay. Yeah. Okay. So that's good. But Obsidian, that's just

1024
01:10:12,310 --> 01:10:15,720
where I have my to-do lists. And so it's functional.

1025
01:10:15,720 --> 01:10:19,979
It's not like I'm not, you notice there's no X

1026
01:10:19,979 --> 01:10:22,760
or anything like that in the list. Ha ha. No.

1027
01:10:22,880 --> 01:10:29,500
I can't. That thing's a train wreck. Yeah. Yeah, there's

1028
01:10:29,500 --> 01:10:33,720
so many. I think we just have too much of

1029
01:10:33,720 --> 01:10:36,279
this stuff in our life. I mean, even podcasts, honestly.

1030
01:10:36,500 --> 01:10:40,060
I mean, I love podcasts, but I have found myself

1031
01:10:40,060 --> 01:10:44,270
just becoming less. I just consume less and less of

1032
01:10:44,270 --> 01:10:47,060
it. Oh, of course. You can only really listen to

1033
01:10:47,060 --> 01:10:50,319
a little bit. each day. You know, I think I

1034
01:10:50,319 --> 01:10:54,220
still probably my go-to is pod news weekly review because

1035
01:10:54,220 --> 01:10:57,850
it's short. It's like, Oh, that's nice. And, uh, I

1036
01:10:57,850 --> 01:10:59,710
might listen to power and I listened to this week

1037
01:10:59,710 --> 01:11:02,560
in Bitcoin, but I only get to the boost segment.

1038
01:11:02,560 --> 01:11:06,520
Um, Because the walk with the dog isn't long enough.

1039
01:11:07,520 --> 01:11:11,689
That's still half an hour. And I find myself annoyed

1040
01:11:11,689 --> 01:11:18,319
by ads. Well, this is not true. Uh-huh. Hold on

1041
01:11:18,319 --> 01:11:21,970
a second. Let me see if I have this clip

1042
01:11:21,970 --> 01:11:25,939
from Tom Webster. Tom Webster. Here we go. This is

1043
01:11:25,939 --> 01:11:29,859
unreleased. This is also from the podcast Landscape 2026. We

1044
01:11:29,859 --> 01:11:32,649
asked people, how much do they agree with this? Are

1045
01:11:32,649 --> 01:11:36,050
ads a fair trade for getting podcasts for free? Well,

1046
01:11:36,050 --> 01:11:40,060
nobody disagrees with that, right? 37% strongly agreed with that.

1047
01:11:40,159 --> 01:11:43,359
81% agreed in total that ads are a fair trade.

1048
01:11:43,560 --> 01:11:47,949
Again, we have not... disrupted the ad bargain. - Okay,

1049
01:11:47,949 --> 01:11:50,010
wait, this is a better clip. - In the course

1050
01:11:50,010 --> 01:11:55,739
of those 35 published studies, We have interviewed 42,000 consumers.

1051
01:11:56,079 --> 01:12:00,069
42,000 consumers. Here are their names, so I can prove

1052
01:12:00,069 --> 01:12:03,560
it. This is all of them. Their addresses are in

1053
01:12:03,560 --> 01:12:07,199
the appendix. No, we really don't do that. What I

1054
01:12:07,199 --> 01:12:09,439
thought would be fun was to take a little bit

1055
01:12:09,439 --> 01:12:11,680
of, I'm not going to call it a victory lap

1056
01:12:11,680 --> 01:12:14,800
because we are far from done. but sort of a

1057
01:12:14,800 --> 01:12:18,159
review of the top 10 findings from all of the

1058
01:12:18,159 --> 01:12:19,800
work that we have done that I think are the

1059
01:12:19,800 --> 01:12:21,829
most germane to this room. And I'll start with the

1060
01:12:21,829 --> 01:12:24,640
first one, which is actually yet to be published, and

1061
01:12:24,640 --> 01:12:28,720
that is that podcasts carry the lowest... perceived ad load

1062
01:12:28,720 --> 01:12:30,659
of any medium that we test. This is from a

1063
01:12:30,659 --> 01:12:36,390
survey of over 5,000 Americans, in fact over 5,400 Americans,

1064
01:12:36,390 --> 01:12:37,810
18 plus, And the thing that I love about this

1065
01:12:37,810 --> 01:12:40,699
particular slide, at the top you see that the people

1066
01:12:40,699 --> 01:12:43,569
who think that podcasts have far too many, yeah, that's

1067
01:12:43,569 --> 01:12:46,840
lower than the other media platforms that we tested. But

1068
01:12:46,840 --> 01:12:51,270
it's that big gray bar at 51% that says, about

1069
01:12:51,270 --> 01:12:57,039
right. So it's about right. It's about right. Well, I

1070
01:12:57,039 --> 01:13:00,489
will say Tina and I tried to watch the Emmy

1071
01:13:00,489 --> 01:13:05,439
Awards, but was it Monday night? I think I remember

1072
01:13:05,439 --> 01:13:08,920
when it was. And oh man, the ads just because

1073
01:13:08,920 --> 01:13:13,479
we don't watch broadcast TV hardly except I got the

1074
01:13:13,479 --> 01:13:17,680
quad screen going on. It's just ad after ad after

1075
01:13:17,680 --> 01:13:24,840
ad after ad. It's like, whoa, it's too much. that's

1076
01:13:24,840 --> 01:13:28,439
it's like I see I feel like this that's like

1077
01:13:28,439 --> 01:13:34,899
comparing what you're what you're comparing podcasting to is the

1078
01:13:34,899 --> 01:13:39,420
most horrible ad-driven media that's ever existed in humankind and

1079
01:13:39,420 --> 01:13:41,850
saying, well, it's not that bad. But you see, these

1080
01:13:41,850 --> 01:13:46,680
aren't podcast listeners. These are consumers, you see. Okay. We

1081
01:13:46,680 --> 01:13:52,140
talk to consumers. They're not actually people. They're consumers. Okay.

1082
01:13:53,020 --> 01:13:56,470
Rogan is always talking about fans. It's like, so you're

1083
01:13:56,470 --> 01:14:00,239
fans. They support the shows. They're not fans, Joe. They

1084
01:14:00,239 --> 01:14:04,699
understand value for value. They support the show. They're producers.

1085
01:14:04,979 --> 01:14:07,739
They are actual producers, like producers. They put up money

1086
01:14:07,739 --> 01:14:13,920
up front. I listened to the latest Ed Zitron episode

1087
01:14:13,920 --> 01:14:17,899
this morning. Oh, must be jacked with ads. It was

1088
01:14:17,899 --> 01:14:22,579
a 15-minute podcast with six minutes of ads. No, really?

1089
01:14:23,960 --> 01:14:29,130
It was like three minutes and 30 seconds before. That's

1090
01:14:29,130 --> 01:14:34,770
12 skips taps. Yeah. It was three. The actual content

1091
01:14:34,770 --> 01:14:39,640
didn't start until 3.30. And then it ended at 12

1092
01:14:39,640 --> 01:14:42,250
minutes and there was another three and a half minutes

1093
01:14:42,250 --> 01:14:46,060
of ads. There was an interesting comment about the skips

1094
01:14:46,060 --> 01:14:48,689
and ads and... See if you agree with this. And

1095
01:14:48,689 --> 01:14:52,000
my big thing about this is a skip button is

1096
01:14:52,000 --> 01:14:55,350
a symptom level response. If your ads suck and the

1097
01:14:55,350 --> 01:15:00,779
technology that they're developing is allowing people to skip past

1098
01:15:00,779 --> 01:15:04,399
content that other people skip, maybe you should do better.

1099
01:15:04,720 --> 01:15:09,840
do better, do better ads, do better ads. Yeah. It's

1100
01:15:09,840 --> 01:15:12,170
like, how do you climb, how do you climb, rock

1101
01:15:12,170 --> 01:15:16,510
climb better? Just don't fall. Fall, fall less. It'd be

1102
01:15:16,510 --> 01:15:24,529
better. Yeah. Stop falling. Content. This, of course, this... I

1103
01:15:24,529 --> 01:15:29,090
mean, like I said, this would be like, well... You

1104
01:15:29,090 --> 01:15:34,220
know, Aston Martin is the greatest car that's ever, you

1105
01:15:34,220 --> 01:15:38,060
know, the most reliable car, you know, in Europe. Well,

1106
01:15:38,060 --> 01:15:41,859
yeah, well, compared to everything else, of course. Yeah. But

1107
01:15:41,859 --> 01:15:44,539
it's like, you know, but we're not, you know, we're

1108
01:15:44,539 --> 01:15:47,170
not comparing them to, you know, that's not a fair

1109
01:15:47,170 --> 01:15:51,640
comparison is what I'm saying. This is just because broadcast

1110
01:15:51,640 --> 01:15:57,800
radio and television has a 70% ad load doesn't mean

1111
01:15:57,800 --> 01:16:02,680
that podcasting is great because it's only 50%. Mm-hmm. And

1112
01:16:02,680 --> 01:16:05,810
just, it's just not like, and of course this is

1113
01:16:05,810 --> 01:16:08,840
a lot of this is coming from I heart. Right.

1114
01:16:09,060 --> 01:16:14,039
And those podcasts are just unlistenable almost. And but then

1115
01:16:14,039 --> 01:16:18,000
I love the tagline guaranteed human. And then it's like

1116
01:16:18,000 --> 01:16:20,789
a voice over the ads. Every every one of them

1117
01:16:20,789 --> 01:16:26,149
is an AI voice now. Have you heard this, the

1118
01:16:26,149 --> 01:16:31,760
guaranteed human tagline? No. That's iHeart's catchphrase now. Oh, really?

1119
01:16:32,199 --> 01:16:36,800
Yeah. iHeart Podcast, guaranteed human. Oh, goodness gracious. Yeah. And

1120
01:16:36,800 --> 01:16:39,979
then the next ad you hear is an AI voice.

1121
01:16:40,920 --> 01:16:47,590
Okay. Yeah. Oh, well. We're still pretty human. And people

1122
01:16:47,590 --> 01:16:51,020
will always love humans. I'm not too worried about that.

1123
01:16:51,140 --> 01:16:56,500
I've been spoiled, I think, in retrospect, because... Thank you.

1124
01:16:57,270 --> 01:17:02,750
My experience with podcasts... really since the beginning has almost

1125
01:17:02,750 --> 01:17:09,220
entirely been donation supported shows. And I think I've just

1126
01:17:09,220 --> 01:17:13,899
really been spoiled. I've never, the shows I listened to

1127
01:17:13,899 --> 01:17:18,060
have never really had any ads until in the last,

1128
01:17:18,060 --> 01:17:20,899
you know, A couple of years, I've started listening to

1129
01:17:20,899 --> 01:17:24,579
some shows that had advertising in them. And that's, it's

1130
01:17:24,579 --> 01:17:30,779
just like, it's hard to listen to. Because I mean,

1131
01:17:30,779 --> 01:17:36,100
like historically I listened to, um, I mean, I still,

1132
01:17:36,220 --> 01:17:37,880
I listen to a lot of shows about like, like,

1133
01:17:37,979 --> 01:17:41,210
uh, Lord of the, like the Lord of spirits, no

1134
01:17:41,210 --> 01:17:46,899
ads, no agenda, no ads. Um, the daily, uh, the,

1135
01:17:47,600 --> 01:17:51,880
the daily tech report, uh, or cybersecurity report, no ads.

1136
01:17:51,920 --> 01:17:54,949
I mean, like, And as soon as I had a

1137
01:17:54,949 --> 01:17:57,500
show that had, well, the Twitch shows had ads, but

1138
01:17:57,500 --> 01:17:59,140
as soon as they let me opt out, I opted

1139
01:17:59,140 --> 01:18:01,390
out of them. Right. I don't know. It's just, I

1140
01:18:01,390 --> 01:18:04,439
just don't think the ad load, and historically the ad

1141
01:18:04,439 --> 01:18:07,859
load in podcasts has always been pretty low. It's only

1142
01:18:07,859 --> 01:18:10,779
really in the last probably three to five years that

1143
01:18:10,779 --> 01:18:13,779
it's ramped up to the… level that it has now,

1144
01:18:13,779 --> 01:18:19,640
which is off the chain. Yeah. This low-level frustration. There

1145
01:18:19,640 --> 01:18:21,779
it is. There it is. It's back. Well, I'm sorry.

1146
01:18:22,020 --> 01:18:25,579
I mean, I always felt that low-level frustration entered my

1147
01:18:25,579 --> 01:18:28,920
life when I had kids. For you, it's technology. I

1148
01:18:28,920 --> 01:18:32,890
don't know. Well, it's the kids, too. Kids aren't that

1149
01:18:32,890 --> 01:18:36,649
great. Let's be honest. Kids aren't that great. Yeah. My

1150
01:18:36,649 --> 01:18:40,920
son, so he calls me. He's currently in fire college

1151
01:18:40,920 --> 01:18:46,440
in North Alabama. Yeah. He calls me. Yeah. night before

1152
01:18:46,440 --> 01:18:50,369
last and he's like, hey, it's at 9.30. I was

1153
01:18:50,369 --> 01:18:52,920
like, okay. So he's been up there for, this is

1154
01:18:52,920 --> 01:18:57,020
week three of Fire College. He's been, he's like, hey.

1155
01:18:57,180 --> 01:19:02,300
Wait, can you Venmo me some money. No, no, no,

1156
01:19:02,300 --> 01:19:04,859
no, no. No, he said, hey, you're probably going to

1157
01:19:04,859 --> 01:19:07,590
get a hospital bill. What? I was like, what? What

1158
01:19:07,590 --> 01:19:13,550
happened? And he was like, well... I, uh, like didn't

1159
01:19:13,550 --> 01:19:18,319
drink enough water. It's 95, 97 degrees here in Alabama.

1160
01:19:18,319 --> 01:19:23,100
Uh, during, during his whole thing, I didn't drink enough

1161
01:19:23,100 --> 01:19:26,220
water and I got really dehydrated and I passed out

1162
01:19:26,220 --> 01:19:29,720
on the doing, doing my, doing the fire test. Do

1163
01:19:29,720 --> 01:19:34,520
you know what a consumption drill is? No. Okay. So

1164
01:19:34,520 --> 01:19:38,720
consumption drill in fire college is where they, you put

1165
01:19:38,720 --> 01:19:45,289
on your, your SCBA, your breathing apparatus. Yes. Self-contained breathing

1166
01:19:45,289 --> 01:19:47,770
apparatus. And they give you a certain amount of oxygen

1167
01:19:47,770 --> 01:19:50,979
in your bottle. Right. And you have to complete the

1168
01:19:50,979 --> 01:19:55,170
obstacle course. Right. and not run out of oxygen. So

1169
01:19:55,170 --> 01:19:57,899
you got to regulate your breathing and still run fast.

1170
01:19:57,899 --> 01:20:00,000
Exactly. You have to do everything as fast as you

1171
01:20:00,000 --> 01:20:00,000
can.

1172
01:20:00,000 --> 01:20:03,029
as possible but not too fast that you run out

1173
01:20:03,029 --> 01:20:05,920
of oxygen wow and people the first time people do

1174
01:20:05,920 --> 01:20:09,000
this are passing out left and right this is school

1175
01:20:09,000 --> 01:20:13,060
that's interesting i like this school school of hard knocks

1176
01:20:13,060 --> 01:20:16,029
and so he so he's been practicing for days now

1177
01:20:16,029 --> 01:20:18,680
and get and he's he's got he's like a hat

1178
01:20:18,680 --> 01:20:21,819
he's got it dialed in he's he's like running the

1179
01:20:21,819 --> 01:20:27,850
course perfectly. And then, uh, It was like 97 here

1180
01:20:27,850 --> 01:20:31,779
on Tuesday. Oh, yeah. And he just didn't drink enough.

1181
01:20:31,859 --> 01:20:33,729
He's like drank like half a bottle of water the

1182
01:20:33,729 --> 01:20:37,590
whole day. And he said, he said, the fire captain

1183
01:20:37,590 --> 01:20:41,180
said that he was like, that he, he like flipped

1184
01:20:41,180 --> 01:20:43,060
over a tire a bunch of times and then goes

1185
01:20:43,060 --> 01:20:45,710
and starts rolling up a fire hose. Yeah. And he

1186
01:20:45,710 --> 01:20:47,829
just stops and he's on his knees and he's just

1187
01:20:47,829 --> 01:20:52,340
kind of sits there. And the captain was like, Grant.

1188
01:20:53,760 --> 01:20:56,869
And he didn't say anything. He was like, Grant, are

1189
01:20:56,869 --> 01:21:00,510
you going to quit? And Grant said, never. He yelled,

1190
01:21:00,510 --> 01:21:03,399
never. And then, like, took two steps and just fell

1191
01:21:03,399 --> 01:21:05,739
and just completely, like, cold as a wedge on the

1192
01:21:05,739 --> 01:21:08,579
ground. Oh, goodness gracious. And so then he wakes up

1193
01:21:08,579 --> 01:21:11,619
in the hospital. And they gave him, like, three bags

1194
01:21:11,619 --> 01:21:14,689
of fluid. Oh, man. Of IV. Oh, that's going to

1195
01:21:14,689 --> 01:21:17,899
be $800. $800. Oh, yeah, at least. Yeah, for sure.

1196
01:21:18,199 --> 01:21:21,000
And I'm like, man, at least he was surrounded by

1197
01:21:21,000 --> 01:21:23,729
EMTs. Right. It's just like, you know, coming out of

1198
01:21:23,729 --> 01:21:28,180
the woods. So, yeah, it's not just technology. It's also

1199
01:21:28,180 --> 01:21:30,090
kids. They try to kill you. They try to kill

1200
01:21:30,090 --> 01:21:32,840
themselves. Yeah, they're just not that great. I mean, let's

1201
01:21:32,840 --> 01:21:35,250
just be honest about it. Everyone says you'll grow a

1202
01:21:35,250 --> 01:21:38,300
heart outside of your body. Yeah, sure. It's not great.

1203
01:21:39,159 --> 01:21:44,600
Yeah. They want to, yeah, you just hope that at

1204
01:21:44,600 --> 01:21:48,979
some point, They don't die and they don't kill you.

1205
01:21:49,220 --> 01:21:55,119
Yes. And exactly. So you need to move your chocolate.

1206
01:21:55,720 --> 01:21:59,460
I don't understand what this thing is doing. I hear

1207
01:21:59,460 --> 01:22:02,539
it. It only lasts for a second. No, it's lasting.

1208
01:22:03,060 --> 01:22:06,279
No, still there. No, that's not it. It's always a

1209
01:22:06,279 --> 01:22:10,300
USB cable for some reason. Maybe it's the spark. Oh,

1210
01:22:10,300 --> 01:22:15,029
you know what it is? What is it? The XLR

1211
01:22:15,029 --> 01:22:21,479
cable. Yeah. And it's near a USB cable. it's near

1212
01:22:21,479 --> 01:22:25,579
lots of cables. There is a Choco Love on top

1213
01:22:25,579 --> 01:22:27,520
of it, but I don't think it's the Choco Love.

1214
01:22:27,819 --> 01:22:31,390
It's always the Choco Love. Speaking of Choco Love, we

1215
01:22:31,390 --> 01:22:33,920
love a lot of Choco Love from people who love

1216
01:22:33,920 --> 01:22:38,439
the podcast index. Excuse me. Which is everybody. Everybody loves

1217
01:22:38,439 --> 01:22:43,319
it. I mean, we are number two usually number two,

1218
01:22:43,420 --> 01:22:47,699
number three behind who behind Apple and YouTube. For some

1219
01:22:47,699 --> 01:22:49,880
reason, YouTube is great now. I don't know, but I

1220
01:22:49,880 --> 01:22:53,800
don't understand it. Sure. Yeah. As an index. Well, good

1221
01:22:53,800 --> 01:22:57,770
luck with that. So we ask you to support the

1222
01:22:57,770 --> 01:23:01,539
index and it supports just the machinery. Then we'll keep

1223
01:23:01,539 --> 01:23:03,739
it running for a long time. Adam and Dave buy

1224
01:23:03,739 --> 01:23:07,119
their own Choco Loves. So it just supports the machinery.

1225
01:23:07,840 --> 01:23:10,800
You can go to podcastindex.org. Down at the bottom, there's

1226
01:23:10,800 --> 01:23:13,500
a big red button. You hit that donate button. You

1227
01:23:13,500 --> 01:23:15,069
can go to our PayPal and you can support us

1228
01:23:15,069 --> 01:23:19,609
that way. Um... You can also, if you're in a

1229
01:23:19,609 --> 01:23:24,029
modern podcast app, hit the donation button. What does it

1230
01:23:24,029 --> 01:23:27,979
show up as a... What does it show up as?

1231
01:23:28,560 --> 01:23:31,409
uh paypal i think no i know but i mean

1232
01:23:31,409 --> 01:23:35,640
um let me see podcasting because you can change the

1233
01:23:35,640 --> 01:23:38,560
i wonder if it says support the show or what

1234
01:23:38,560 --> 01:23:42,699
because you can change the value of that podcasting 2.0

1235
01:23:42,699 --> 01:23:44,970
here we go let me see what it says value

1236
01:23:44,970 --> 01:23:47,140
for value is what it says oh that's kind of

1237
01:23:47,140 --> 01:23:49,989
cool So you hit the value for value on your

1238
01:23:49,989 --> 01:23:54,060
modern podcast app. Boom! There you go. You're right there

1239
01:23:54,060 --> 01:23:57,279
at the PayPal. Bam. It's beautiful. It's fantastic. You got

1240
01:23:57,279 --> 01:24:00,500
to log in, I see. Okay. So let me see.

1241
01:24:00,680 --> 01:24:02,630
I think we got some boosts coming in during the

1242
01:24:02,630 --> 01:24:04,850
show, which is another way you can support us with

1243
01:24:04,850 --> 01:24:11,939
your boostograms. 12-71 from Salty Crayon. Show number boost. In

1244
01:24:11,939 --> 01:24:17,189
the pipe. That's right. 2-71. Eric PP with 3333. 777

1245
01:24:17,189 --> 01:24:20,649
from Lyceum. I didn't hear the harp music. I wonder

1246
01:24:20,649 --> 01:24:24,350
what happened there, Lyceum. Then another boost from Lyceum, that's

1247
01:24:24,350 --> 01:24:27,819
Martin Lindus Kug, 1776, all coming in through True Friends.

1248
01:24:27,920 --> 01:24:30,680
Here's a short and sweet episode of Power with birthday

1249
01:24:30,680 --> 01:24:32,939
greetings for Sam Sethi from Podcast Movement New York. Oh,

1250
01:24:32,939 --> 01:24:35,979
yeah. Happy birthday, Sam. Happy birthday, Sam. Yeah. One minute

1251
01:24:35,979 --> 01:24:42,510
and 39 seconds. Well, it counts as a show. Rove

1252
01:24:42,510 --> 01:24:45,989
Sticks from Lyceum. Oh, he's busy today. I like the

1253
01:24:45,989 --> 01:24:48,579
pen and paper reference. We have a podcast, which is

1254
01:24:48,579 --> 01:24:54,279
archived, called Penner Möter Papar, which is pen meets paper

1255
01:24:54,279 --> 01:24:57,659
in Swedish. Penner Möter Papar. I'm going to just use

1256
01:24:57,659 --> 01:25:03,279
that wherever I go. Johan Gustafsson. Johan Gudmundsen, and yours

1257
01:25:03,279 --> 01:25:06,090
truly, Martin Lindeskog. Go take a look at it. Penner,

1258
01:25:06,090 --> 01:25:09,850
murder, papa! Sounds like a winner. And with that, I

1259
01:25:09,850 --> 01:25:13,300
hit the delimiter, Dave, so you're up. What's a foot

1260
01:25:13,300 --> 01:25:19,859
terminal? A foot terminal? Uh-huh. Why do you ask? Because

1261
01:25:19,859 --> 01:25:22,199
that's what the Pi thing is telling me. It says,

1262
01:25:22,199 --> 01:25:29,020
here's your nine windows across five workspaces. Workspace one, foot

1263
01:25:29,020 --> 01:25:36,050
terminal, chromium, foot Pi sandbox. And then it says workspace

1264
01:25:36,050 --> 01:25:41,500
two signal and foot terminal foot terminal. Uh, workspace three

1265
01:25:41,500 --> 01:25:44,239
is Romina. That's correct. Workspace four is a foot terminal

1266
01:25:44,239 --> 01:25:46,630
and workspace five is a foot terminal. What is a

1267
01:25:46,630 --> 01:25:50,279
foot terminal book of knowledge? What is a foot terminal?

1268
01:25:50,279 --> 01:25:52,539
Um, Might as well ask the Book of Knowledge. I

1269
01:25:52,539 --> 01:25:54,359
mean, that's what it's there for. It's going to make

1270
01:25:54,359 --> 01:25:56,949
up some... According to the Book of Knowledge, a foot

1271
01:25:56,949 --> 01:26:01,180
terminal is a specialized railway or transit station located at

1272
01:26:01,180 --> 01:26:04,609
the end of a line, particularly at the waterfront or

1273
01:26:04,609 --> 01:26:09,310
shore, where passengers transfer between land-based transport and ferries or

1274
01:26:09,310 --> 01:26:15,350
other water vessels. Thus, it has been written. Yeah, clearly

1275
01:26:15,350 --> 01:26:18,340
I have five of those on my desktop. Foot Terminal.

1276
01:26:18,479 --> 01:26:20,390
I think Foot Terminal has to be the title of

1277
01:26:20,390 --> 01:26:25,170
the show. foot foot terminal there's i've got at least

1278
01:26:25,170 --> 01:26:28,050
one foot terminal in every workspace well i'm happy to

1279
01:26:28,050 --> 01:26:30,270
hear that that's good it's good for you it might

1280
01:26:30,270 --> 01:26:34,640
get rid of that low level irritation I need, there's

1281
01:26:34,640 --> 01:26:36,800
not enough of them in my life is the problem.

1282
01:26:37,579 --> 01:26:39,630
Okay. Well, here we go. I'm going to go to

1283
01:26:39,630 --> 01:26:43,819
command, excuse me, super three. All right. Here we go.

1284
01:26:43,899 --> 01:26:47,760
Super three. Scott old gave us $30 through PayPal. Oh,

1285
01:26:47,760 --> 01:26:50,069
you have, you have your work, your workspace all set

1286
01:26:50,069 --> 01:26:53,109
up with the boost and everything. Nice. Oh, I'm a

1287
01:26:53,109 --> 01:26:59,079
pro now. Workspaces is cool, man. I'm telling you. It's

1288
01:26:59,079 --> 01:27:01,199
the way to go. It's the way of the future.

1289
01:27:01,300 --> 01:27:04,239
All the kids are doing it. I've never used workspaces

1290
01:27:04,239 --> 01:27:10,609
in Linux. Xwindows, x.org, I've had workspaces since the dawn

1291
01:27:10,609 --> 01:27:13,100
of time, and I've never used them until the tiling

1292
01:27:13,100 --> 01:27:16,920
window manager. Now it feels natural. Yes, it is. And

1293
01:27:16,920 --> 01:27:20,640
HFF is going to send you some chocko love. With

1294
01:27:20,640 --> 01:27:25,500
a foot terminal. Yeah. Thank you for relighting my passion

1295
01:27:25,500 --> 01:27:28,619
for podcasting, says Scott Auld. All right, Scott. He says,

1296
01:27:28,619 --> 01:27:32,619
I was podcasting my pastor's sermons in 2007. He says,

1297
01:27:32,619 --> 01:27:34,720
Adam was spreading the word long before he was a

1298
01:27:34,720 --> 01:27:37,939
believer. That's right. I took a three-year break, but you

1299
01:27:37,939 --> 01:27:41,420
two have fired me up for distributed free speech again.

1300
01:27:41,579 --> 01:27:44,689
Scott Aul, Winning the Week podcast. Very nice. I get

1301
01:27:44,689 --> 01:27:48,600
booths whenever there's a booth nearby. Yeah. We all do.

1302
01:27:49,399 --> 01:27:55,180
Timothy Voice, $10. Thank you, Timothy. Todd Cochran, RIP, $30.

1303
01:27:55,619 --> 01:28:02,539
Todd got all kinds of... memorial salute during podcast week

1304
01:28:02,539 --> 01:28:07,600
in New York. Oh, good. He deserves it. Michael Hall,

1305
01:28:07,600 --> 01:28:16,659
$5.50. Gene Liverman, $5.00. Jeremy Gertz, $5.00. Jeff Seabold, $11.00.

1306
01:28:17,399 --> 01:28:21,729
Derek J. Visker, Best name in podcasting, $21. Paul Saltzman,

1307
01:28:21,729 --> 01:28:29,159
$22.22. Who's this? Silicon Florist, $10. And Christopher Cowan, $5.

1308
01:28:29,479 --> 01:28:32,440
That's our PayPal. And you know what? These numbers, they

1309
01:28:32,440 --> 01:28:35,840
matter. Thank you so much. This keeps machines running, crawlers,

1310
01:28:35,840 --> 01:28:40,670
all kinds of stuff. It's highly appreciated. Uh, we got

1311
01:28:40,670 --> 01:28:44,300
some booster grams. Let's got, oh, Dreb's got 716 sets.

1312
01:28:44,359 --> 01:28:48,029
He says serpentine belt. Almost done. If I can get

1313
01:28:48,029 --> 01:28:51,329
the belt and the tensioner to cooperate. Oh, this is,

1314
01:28:51,329 --> 01:28:54,940
this is a car, a truck talk thing. Yeah. Do

1315
01:28:54,940 --> 01:29:00,699
Dreb, do you have a welder? If you do not.

1316
01:29:00,699 --> 01:29:03,850
Uh, Go to Harbor Freight and buy one for like

1317
01:29:03,850 --> 01:29:08,270
$100. And then you can build or you can weld

1318
01:29:08,270 --> 01:29:14,500
up any serpentine belt tensioner tool you need. And you

1319
01:29:14,500 --> 01:29:19,440
will be set for life. the welder and the material

1320
01:29:19,440 --> 01:29:22,600
to make it will cost you less than a buying

1321
01:29:22,600 --> 01:29:26,020
a, or about the same as buying a serpentine belt

1322
01:29:26,020 --> 01:29:33,000
tool from the store. Let's see. Magnolia Mayhem, 1526 sats.

1323
01:29:33,279 --> 01:29:36,100
Cool news about VLC. Oh, yes, that is kind of

1324
01:29:36,100 --> 01:29:39,859
cool. Have we heard back from those guys? Nope. Okay.

1325
01:29:40,239 --> 01:29:41,690
I feel like I'm going back to the days of

1326
01:29:41,690 --> 01:29:45,059
2013 where I downloaded MP3s of podcasts and listened to

1327
01:29:45,059 --> 01:29:48,699
them through VLC. Also, just had to replace the serpentine

1328
01:29:48,699 --> 01:29:51,500
belt in my car, in my mail car. Good to

1329
01:29:51,500 --> 01:29:55,800
know I'm not alone. Mail car, nice. Yep. Hashtag car

1330
01:29:55,800 --> 01:29:59,859
talk. Mm-hmm. I'm always up for car talk.

1331
01:30:00,619 --> 01:30:05,680
You see 5,018 sets from user 9041 blah, blah, blah,

1332
01:30:05,680 --> 01:30:10,220
blah, blah through fountain. Appreciate it. No note. And a

1333
01:30:10,220 --> 01:30:17,789
delimiter, common street blogger. There he is. 11,111 sats. He

1334
01:30:17,789 --> 01:30:21,939
says, how did Dave and Adam? Today, I recommend not

1335
01:30:21,939 --> 01:30:25,670
a podcast, but Adam's friend. Please go to X or

1336
01:30:25,670 --> 01:30:31,020
Twitter and follow at Dana Brunetti. Dana has a woman-like

1337
01:30:31,020 --> 01:30:34,819
first name, but is not a woman. He's active on

1338
01:30:34,819 --> 01:30:39,380
X. He followed me, CSB, first on X, so buy

1339
01:30:39,380 --> 01:30:42,239
this Bitcoin gram and... I'm saying thank you to him.

1340
01:30:42,859 --> 01:30:47,449
He's in movie industry or something. Yo, CSB still stonewalled

1341
01:30:47,449 --> 01:30:55,840
by Adam Curry. This gram was $15.61 when sent. I'm

1342
01:30:55,840 --> 01:31:01,399
going to have to do this. Stonewaller. I'm a stonewaller.

1343
01:31:01,460 --> 01:31:03,630
It's not because I don't love him. It's just I'm

1344
01:31:03,630 --> 01:31:06,189
a busy guy. There's a lot going on. My podcast

1345
01:31:06,189 --> 01:31:09,199
host died. There's just stuff happening in my life. I

1346
01:31:09,199 --> 01:31:12,899
got a granddaughter. I've been traveling. I got low-level anger

1347
01:31:12,899 --> 01:31:18,600
management issues. I'm glad it's not just me. It's not

1348
01:31:18,600 --> 01:31:21,939
just you, Dave. Dave. All right, brother. Have a great

1349
01:31:21,939 --> 01:31:24,720
weekend. Hope you don't get any calls from the kids.

1350
01:31:25,319 --> 01:31:27,479
Me too. All right, everybody. Thank you, Boardroom. See you

1351
01:31:27,479 --> 01:31:44,590
next Friday. . Thank you. . Cool. You have been

1352
01:31:44,590 --> 01:31:52,579
listening to Podcasting 2.0. Visit podcastindex.org for more information. Go

1353
01:31:52,579 --> 01:31:56,470
podcasting! It's like, man, I just want a bowl of

1354
01:31:56,470 --> 01:31:57,279
cereal.