1
00:00:00,600 --> 00:00:06,280
Podcasting 2.0 for August 21st, 2026, episode 268, Dead Hanging

2
00:00:06,280 --> 00:00:12,640
Safari. We'll be right back. It's summer. That's right, everybody.

3
00:00:12,640 --> 00:00:15,480
And when it's summer, it's time to do a podcast.

4
00:00:15,480 --> 00:00:18,500
It's time to do a podcast. This is Podcasting 2.0,

5
00:00:18,500 --> 00:00:21,360
the board meeting of all of the boys and girls

6
00:00:21,360 --> 00:00:24,760
who make up the band of misfits that create better

7
00:00:24,760 --> 00:00:28,150
podcasting for you. This is where we meet. In fact,

8
00:00:28,150 --> 00:00:30,530
we are the only board meeting you can't find on

9
00:00:30,530 --> 00:00:33,220
a map. I'm Adam Curry here in the heart of

10
00:00:33,220 --> 00:00:36,300
the Texas Hill Country, and in Alabama, the man whose

11
00:00:36,300 --> 00:00:40,660
database is still backfilling longitude and latitude digits, say hello

12
00:00:40,660 --> 00:00:43,570
to my friend on the other end, the one, the

13
00:00:43,570 --> 00:00:52,600
only, the Podsage, Mr. Dave Jones! You've got... something happened

14
00:00:52,600 --> 00:00:56,600
with the audio there. Oh? What happened? I don't know.

15
00:00:56,600 --> 00:01:00,360
Suddenly you got very... you got far away. I got

16
00:01:00,360 --> 00:01:04,180
far away? Now you sound normal again. Oh, I know.

17
00:01:04,180 --> 00:01:06,500
But when you went into the intro... Yeah, hold on.

18
00:01:06,500 --> 00:01:09,380
Hold on. I know what it is. Hold on. Okay.

19
00:01:09,480 --> 00:01:12,740
Okay, this may help. I had to... I had to

20
00:01:12,740 --> 00:01:17,610
set it to voice only yesterday for Rob. Do I

21
00:01:17,610 --> 00:01:20,820
had Sir Dusa for Rob do on no agenda? OK,

22
00:01:20,820 --> 00:01:24,700
and he had he was probably the Alex Jones studio

23
00:01:24,700 --> 00:01:27,140
and had some kind of crappy connection. So I had

24
00:01:27,140 --> 00:01:30,100
to drop him down to voice only on clean feed

25
00:01:30,100 --> 00:01:33,490
so that we wouldn't have a delay. Okay, it was

26
00:01:33,490 --> 00:01:36,980
wigging me out because you sounded normal and then you

27
00:01:36,980 --> 00:01:38,780
went to the intro and it was like... I was

28
00:01:38,780 --> 00:01:41,760
like, wait, where'd you go? You're like in the next

29
00:01:41,760 --> 00:01:44,060
room. I'm here, I'm here, I'm here, don't worry, I'm

30
00:01:44,060 --> 00:01:47,590
here. It was that, but faint. I'm like, wait, this

31
00:01:47,590 --> 00:01:49,980
can't be, this is not right. I'm sorry, I'm sorry.

32
00:01:50,560 --> 00:01:52,880
Do you mute me while you're doing the intro? No,

33
00:01:52,880 --> 00:01:54,930
you can jump up and down and do all kinds

34
00:01:54,930 --> 00:01:58,630
of stuff. Have you considered doing it? I've considered lots

35
00:01:58,630 --> 00:02:04,710
of things, but I was getting – I was eating

36
00:02:04,710 --> 00:02:09,980
some chips. And some potato chips. And I was like,

37
00:02:09,980 --> 00:02:11,760
wait. Oh, no, you'd never hear that. Am I coming

38
00:02:11,760 --> 00:02:14,500
through? No, no, you'd never hear that. No. Why? Why

39
00:02:14,500 --> 00:02:19,240
would you never hear that? Because my processing is overriding

40
00:02:19,240 --> 00:02:23,600
you. Oh, so you would not get any of that?

41
00:02:23,820 --> 00:02:27,850
Probably not. No, probably not. People don't understand. When you

42
00:02:27,850 --> 00:02:30,240
do a podcast, you've got to process that thing, man.

43
00:02:30,280 --> 00:02:32,960
You've got to process it. Process it hard. You've got

44
00:02:32,960 --> 00:02:34,740
to process it. I need a flat line on the

45
00:02:34,740 --> 00:02:41,290
waveform. I don't even know what that means. Nothing. You're

46
00:02:41,290 --> 00:02:45,360
gating me out. If you look at the waveform of

47
00:02:45,360 --> 00:02:49,360
any podcast I produce, you won't see peaks and valleys.

48
00:02:49,500 --> 00:02:52,140
You just see a flat top and a flat bottom.

49
00:02:53,720 --> 00:03:01,100
That's compression. That's compression. Exactly. I'm a little heartbroken. Uh,

50
00:03:01,100 --> 00:03:05,760
I'm here for you. I know you are. I'm just

51
00:03:05,760 --> 00:03:10,800
tell me, tell me, tell me where you were hurt.

52
00:03:11,420 --> 00:03:17,840
I was so excited to see radar.rss.io, which is, of

53
00:03:17,840 --> 00:03:24,340
course, um, The boys over there at RSS.com. They made

54
00:03:24,340 --> 00:03:27,920
a beautiful map out of the location data, out of

55
00:03:27,920 --> 00:03:31,240
the endpoint that you provided. I was so excited. I'm

56
00:03:31,240 --> 00:03:36,600
going on the map. I use RSS.com. I could not

57
00:03:36,600 --> 00:03:41,520
find my podcast anywhere. Which one? Okay, let's do this.

58
00:03:41,600 --> 00:03:48,310
We get to do this. Radar. Is on RSS.com. I

59
00:03:48,310 --> 00:03:54,060
diligently fill out location every single show. Well, maybe you've

60
00:03:54,060 --> 00:03:58,560
not been picked up yet by the index. Oh, well,

61
00:03:58,560 --> 00:04:04,340
then that's an incomplete release. Yeah, of course it is.

62
00:04:05,680 --> 00:04:09,200
Look, I make no promises, okay? Oh, well, I was

63
00:04:09,200 --> 00:04:14,810
disappointed. If somebody... If somebody's at fault here, it's clearly

64
00:04:14,810 --> 00:04:20,150
me and not Alberto. It's a beautiful vibe-coded project. I

65
00:04:20,150 --> 00:04:23,250
presume it's vibe-coded. Oh, I doubt it is. I bet

66
00:04:23,250 --> 00:04:25,470
you it's not. Do you think he went in there

67
00:04:25,470 --> 00:04:28,510
with a text editor and did all that? I think

68
00:04:28,510 --> 00:04:32,620
that... Well, it says there's a link to the GitHub.

69
00:04:32,880 --> 00:04:38,040
Let's see if we can see anything. Contributors, Alberto. If

70
00:04:38,040 --> 00:04:42,380
you look at my GitHub. All Claude. It all lists,

71
00:04:42,380 --> 00:04:49,120
Claude lists itself. Yeah. I don't think, I think, Alberto

72
00:04:49,120 --> 00:04:53,110
is a... I mean, I think he's got like a

73
00:04:53,110 --> 00:04:56,030
PhD or something in computer science. No, he does not

74
00:04:56,030 --> 00:04:59,660
need it. He has a PhD in AI, man. I

75
00:04:59,660 --> 00:05:03,260
think he actually studied for that stuff. Maybe he wrote

76
00:05:03,260 --> 00:05:06,520
the course. I don't know. Yeah, he knows what he's

77
00:05:06,520 --> 00:05:11,840
talking about. I just feel like there may be some...

78
00:05:12,140 --> 00:05:14,570
Some help from AI or something, maybe. Oh, hold on

79
00:05:14,570 --> 00:05:16,310
a second. But I feel like 90% of this is

80
00:05:16,310 --> 00:05:18,540
him. Hold on a second. So Eric PP, this is

81
00:05:18,540 --> 00:05:23,040
interesting. Eric PP says it needs podcast location tag at

82
00:05:23,040 --> 00:05:27,340
the channel level. Yeah. Oh, yes. That is true. That

83
00:05:27,340 --> 00:05:29,980
was not explained to me. Is yours not at the

84
00:05:29,980 --> 00:05:32,830
channel level? Well, let me take a look. I fear

85
00:05:32,830 --> 00:05:39,260
now. This is only channel level. Let me see. I'm

86
00:05:39,260 --> 00:05:44,990
afeard. I'm afeard. There is no interface on RSS.com to

87
00:05:44,990 --> 00:05:48,530
add it at the channel level. Well, this is an

88
00:05:48,530 --> 00:05:52,090
outrage. No, that's not true. What do you mean it's

89
00:05:52,090 --> 00:05:55,460
not true? It's not true. What do you mean? I'm

90
00:05:55,460 --> 00:06:00,160
looking at it. This is misinformation. Hold on. Oh, wait.

91
00:06:00,260 --> 00:06:02,300
Oh, wait. Hold on a second. Hold on a second.

92
00:06:02,320 --> 00:06:05,130
See, I told you. Well, it's not where you'd expect

93
00:06:05,130 --> 00:06:09,520
it to be. You are going to show up on

94
00:06:09,520 --> 00:06:18,460
NewsGuard. Like gonna? Really? Gonna? Yeah, that's true. You're in

95
00:06:18,460 --> 00:06:22,540
the list already. Okay, location added success. I'll tell you

96
00:06:22,540 --> 00:06:26,360
why I didn't see it. Because if you go to

97
00:06:26,360 --> 00:06:33,080
your dashboard, the dashboard, the RSS.com dashboard, Yes. I go

98
00:06:33,080 --> 00:06:36,200
to the dashboard. Yeah. Then I select my podcast and

99
00:06:36,200 --> 00:06:39,050
says, edit my podcast. I edit the podcast and it

100
00:06:39,050 --> 00:06:43,980
says, edit podcast title, description, public website and podcast feed.

101
00:06:43,980 --> 00:06:49,740
Then it has podcast details, category, language, author details, copyright

102
00:06:49,740 --> 00:06:55,230
notice. So, no, but then you go to settings, which

103
00:06:55,230 --> 00:06:58,190
I then guess, does that go for all of my

104
00:06:58,190 --> 00:07:05,100
podcasts? Which is wrong. Probably not. I wouldn't think so.

105
00:07:05,580 --> 00:07:07,030
I wouldn't think that would be all of them, would

106
00:07:07,030 --> 00:07:10,900
it? Well, so here on settings, let me see if

107
00:07:10,900 --> 00:07:13,620
it changes, if I change it to a different podcast.

108
00:07:13,860 --> 00:07:15,920
Let me see. I bet it does. Well, let's check

109
00:07:15,920 --> 00:07:19,000
it out. Check it out. Yeah, you're right. You're right.

110
00:07:19,060 --> 00:07:22,000
I'm wrong. I'm wrong as usual. You've been wrong twice,

111
00:07:22,000 --> 00:07:24,030
and we're only 10 minutes into this podcast. Not even

112
00:07:24,030 --> 00:07:30,140
10 minutes in. Okay. So how soon before this updates?

113
00:07:30,420 --> 00:07:36,010
Am I there yet? let's see I could probably run

114
00:07:36,010 --> 00:07:38,200
it let me see if I would have to did

115
00:07:38,200 --> 00:07:42,280
you pod ping I don't know You made a change.

116
00:07:42,360 --> 00:07:45,760
I bet the pod ping went out. Let me give

117
00:07:45,760 --> 00:07:48,910
it like 10 minutes, and then I'll rerun it. Let

118
00:07:48,910 --> 00:07:50,980
me check my feed here for a second. Let me

119
00:07:50,980 --> 00:07:56,580
see if it's in there already. Location, location, location. I

120
00:07:56,580 --> 00:08:00,000
don't think it's in. Oh, yeah, location. Yeah, location is

121
00:08:00,000 --> 00:08:03,400
in there. It's in. Yeah, I'm in. Location is in.

122
00:08:04,000 --> 00:08:06,910
All right, let me run. Yeah, run it, baby. Then

123
00:08:06,910 --> 00:08:08,960
I'm going to go. I want to see myself pop

124
00:08:08,960 --> 00:08:14,550
up. But that is an interesting point. If I'm doing

125
00:08:14,550 --> 00:08:18,680
a podcast from different locations around the world, That's not

126
00:08:18,680 --> 00:08:22,660
going to show up because the item level is ignored.

127
00:08:23,280 --> 00:08:27,260
It's just like a second-class citizen. Yeah, well, why is

128
00:08:27,260 --> 00:08:31,560
that a problem, though? Well, isn't the whole beauty point,

129
00:08:31,560 --> 00:08:36,900
beauty part, the whole beautiness of having location? Because there's

130
00:08:36,900 --> 00:08:39,230
two ways you can use it. You can use it,

131
00:08:39,230 --> 00:08:44,140
and both of those interfaces are Surface on RSS.com's interface.

132
00:08:44,700 --> 00:08:47,090
You can use it where this podcast is created or

133
00:08:47,090 --> 00:08:50,690
what this podcast is about, a boot. So if I'm

134
00:08:50,690 --> 00:08:53,220
in Canada and I want to show people that this

135
00:08:53,220 --> 00:08:57,970
is a boot Canada, and the week after I'm in

136
00:08:57,970 --> 00:09:03,370
Rotterdam, You can't do that by individual level. This is

137
00:09:03,370 --> 00:09:06,940
just, this is a thought mistake. This is clearly a

138
00:09:06,940 --> 00:09:15,000
violation of all of the Cridler's standards. What do you

139
00:09:15,000 --> 00:09:19,150
want to say? What do you say to that? What

140
00:09:19,150 --> 00:09:21,380
I say to that is I just noticed something. What

141
00:09:21,380 --> 00:09:25,900
did you notice? That we've crossed the 8 million mark

142
00:09:25,900 --> 00:09:30,260
on podcast index ID numbers. Holy moly. That's a lot.

143
00:09:31,060 --> 00:09:35,270
Congratulations. The newest one that just went. Yeah. Congratulations to

144
00:09:35,270 --> 00:09:40,720
nobody. The most recent. one that we just went in

145
00:09:40,720 --> 00:09:48,760
is 8,757,000. We didn't even have a banquet or a...

146
00:09:48,760 --> 00:09:50,990
No, we did not have a celebration at all. No

147
00:09:50,990 --> 00:09:54,640
celebration at all. No, nothing. One of those ones where

148
00:09:54,640 --> 00:09:57,670
when your car rolls over to a million miles or

149
00:09:57,670 --> 00:09:59,900
whatever that you get out and

150
00:10:00,072 --> 00:10:02,702
Push it the last tenth of a mile just to

151
00:10:02,702 --> 00:10:07,192
celebrate. We needed to do that. I'm trying to check

152
00:10:07,192 --> 00:10:10,682
to see which one. You know who's there? Paul's Wildwood

153
00:10:10,682 --> 00:10:16,582
Assembly podcast shows up. Nice. Nice. He's there. But I'm

154
00:10:16,582 --> 00:10:19,002
still not. Podcast location. Well, I'm about to run the

155
00:10:19,002 --> 00:10:23,772
thing. Run the thing. Right. Generate location list.php. Enter. This

156
00:10:23,772 --> 00:10:26,982
is very cool, though. I like this. But still, I

157
00:10:26,982 --> 00:10:30,642
think there's a, you know, are we not going to

158
00:10:30,642 --> 00:10:36,482
do episode level location tags? Yeah. I mean, I. i

159
00:10:36,482 --> 00:10:41,902
can't speak i'm not alberto i cannot speak but wait

160
00:10:41,902 --> 00:10:45,522
are you are you exposing those though is my question

161
00:10:45,522 --> 00:10:49,782
well i he he wanted you're putting this on alberto

162
00:10:49,782 --> 00:10:53,612
this you are pushing off responsibility onto a man who

163
00:10:53,612 --> 00:11:00,072
doesn't even he's not even from america It's a disability.

164
00:11:00,412 --> 00:11:04,552
It is a disability. Yeah. What does he even know

165
00:11:04,552 --> 00:11:07,352
about podcasting? He's not Merkin. Seriously, he's not Merkin. No.

166
00:11:08,492 --> 00:11:13,342
Why is he even in this company? So, yes, I'm

167
00:11:13,342 --> 00:11:18,462
going to – I'll load all of the problems that

168
00:11:18,462 --> 00:11:21,752
I can't explain onto him because he's not here. It's

169
00:11:21,752 --> 00:11:24,102
super easy to do that. Don't say that because then

170
00:11:24,102 --> 00:11:25,482
I'd be like, hey, I want to be on the

171
00:11:25,482 --> 00:11:27,332
show next week to talk about why I'm to blame

172
00:11:27,332 --> 00:11:30,102
for everything. I want to blame for everything. Can't have

173
00:11:30,102 --> 00:11:36,932
that. The location stuff picked me right up, KDAV. Boom.

174
00:11:36,932 --> 00:11:41,932
Right on the top. Yeah. There's other things. There's one

175
00:11:41,932 --> 00:11:45,342
in Homewood. Yeah, but I don't care. I want to

176
00:11:45,342 --> 00:11:47,262
see me. I'm trying to find you. This is so

177
00:11:47,262 --> 00:11:51,092
unimportant. I'm trying to find you. How do you search?

178
00:11:51,652 --> 00:11:56,512
Globe. No, I'm doing a near me. Near me. All,

179
00:11:56,512 --> 00:12:06,962
I've even set 30 miles. Where's the radar.rss.io? But there's

180
00:12:06,962 --> 00:12:09,672
a search where you can search by name, right? No,

181
00:12:09,672 --> 00:12:11,532
I don't see a search. Where do I see a

182
00:12:11,532 --> 00:12:14,892
search? I could have sworn I saw that. Okay, here,

183
00:12:14,892 --> 00:12:18,542
do this. Go back to the homepage, radar.rss.io, and do

184
00:12:18,542 --> 00:12:24,632
force refresh at the bottom. Okay. to make it pull

185
00:12:24,632 --> 00:12:26,792
the newest cash from where I just rebuilt it. Oh,

186
00:12:26,792 --> 00:12:31,002
okay. My number went up. 3,339 located podcasts. Number went

187
00:12:31,002 --> 00:12:35,022
up? Number go up? Number go up. Cash locally zero

188
00:12:35,022 --> 00:12:39,502
minutes ago. No. Okay. Now try to find yourself. I'm

189
00:12:39,502 --> 00:12:43,602
looking at it. There's nothing. You did the podcast near

190
00:12:43,602 --> 00:12:45,862
me and it's still not. What is your location set

191
00:12:45,862 --> 00:12:50,922
to? My location is right here in Fredericksburg. I clicked

192
00:12:50,922 --> 00:12:54,002
a little location thingy. I'll do it again. You say,

193
00:12:54,002 --> 00:12:57,302
I got a map. You are here. Okay. That looks

194
00:12:57,302 --> 00:13:04,562
accurate. I am here. Reset. Made here, about here. I'm

195
00:13:04,562 --> 00:13:08,372
on a bozo filter. That's what's going on here. I'm

196
00:13:08,372 --> 00:13:12,202
being shadow banned. I'm being shadow banned. You're shadow banning

197
00:13:12,202 --> 00:13:16,752
me. That's what that's Alberto's like, we can't have him

198
00:13:16,752 --> 00:13:20,132
on here. This is just not going to work. It

199
00:13:20,132 --> 00:13:23,572
violates his terms of service. I'm getting as far as

200
00:13:23,572 --> 00:13:27,792
Austin, Texas and Dripping Springs. So I should be, which

201
00:13:27,792 --> 00:13:32,282
is which is actually incorrect because I'm set to 15

202
00:13:32,282 --> 00:13:36,202
miles and I should not be getting Austin. Because it

203
00:13:36,202 --> 00:13:44,412
even says 21 miles. The whole thing is bogus. We

204
00:13:44,412 --> 00:13:47,862
get to do this, right? Dude, we get to do

205
00:13:47,862 --> 00:13:51,692
this. There's no search, though. There's no search bar. I'm

206
00:13:51,692 --> 00:13:54,052
looking. I don't know what you're talking about. I see

207
00:13:54,052 --> 00:13:58,992
no search. No, I was wrong about the search. I

208
00:13:58,992 --> 00:14:00,702
could have sworn there was one, but I guess I'm

209
00:14:00,702 --> 00:14:03,932
thinking of something different. I'm trying to find your podcast

210
00:14:03,932 --> 00:14:08,122
index ID. It's 747-3440. That's what I was about to

211
00:14:08,122 --> 00:14:14,722
say. Uh-huh. Now, let me look. I'm looking directly in

212
00:14:14,722 --> 00:14:18,852
the... In the database. You're looking in my personal table.

213
00:14:19,572 --> 00:14:25,292
In the NF locations table. Search. Feed ID. Okay, yeah,

214
00:14:25,292 --> 00:14:27,812
you're in there now. Okay, so now let me regenerate

215
00:14:27,812 --> 00:14:31,002
it. Okay. You may get picked up after I did

216
00:14:31,002 --> 00:14:36,852
it. Okay, so generate. Now, currently, I have 3,339 located

217
00:14:36,852 --> 00:14:40,152
podcasts listed on the page, so I'm going to refresh.

218
00:14:40,872 --> 00:14:44,632
Force refresh. Oh, it went up by one. 3340. Okay.

219
00:14:45,232 --> 00:14:46,772
So I'll refresh. All right, you do it now. You

220
00:14:46,772 --> 00:14:49,152
do force refresh, and let's see if you get 3340.

221
00:14:49,332 --> 00:14:54,972
Force refresh. What do you mean? 43, 4340 located podcasts

222
00:14:54,972 --> 00:14:58,752
ready to search right there, like above the force refresh

223
00:14:58,752 --> 00:15:04,032
button, like in the little box. Where it says all

224
00:15:04,032 --> 00:15:07,182
made here, about here, right under that, I should tell

225
00:15:07,182 --> 00:15:10,602
you. Oh, 3,340. Okay, yeah, so now see if you

226
00:15:10,602 --> 00:15:16,912
show up. Nope. really no really i'll uh i'll refresh

227
00:15:16,912 --> 00:15:21,952
i'll refresh force refresh i got new brawn falls lake

228
00:15:21,952 --> 00:15:25,692
travis uh lots of austin i should be at the

229
00:15:25,692 --> 00:15:29,722
top no is your did you put your coordinate geo

230
00:15:29,722 --> 00:15:33,812
coordinates in there Did he ask for that? No, it

231
00:15:33,812 --> 00:15:36,072
just – it gives you a list. You type in

232
00:15:36,072 --> 00:15:40,292
your – you type in your, like, Fredericksburg, Texas. It

233
00:15:40,292 --> 00:15:43,512
gives you the – it auto-completes. So there you go,

234
00:15:43,512 --> 00:15:50,472
Fredericksburg, Texas, Gillespie County, 78624. I select – It was

235
00:15:50,472 --> 00:15:54,432
probably not even in the feed. Well, let's find out.

236
00:15:55,392 --> 00:15:57,172
We got to get to the bottom of this. I

237
00:15:57,172 --> 00:16:01,392
agree because the whole point is that you get the

238
00:16:01,392 --> 00:16:06,242
RSS.com dude. Who made this is all jitty about how

239
00:16:06,242 --> 00:16:12,362
cool it is. And then his customers, actual customers. okay

240
00:16:12,362 --> 00:16:15,122
geo geo not yet it's all in there it's in

241
00:16:15,122 --> 00:16:18,202
there yeah yeah i see it it's in there i'm

242
00:16:18,202 --> 00:16:24,662
in this geo geo geo geo i am geo 30.2752011

243
00:16:24,662 --> 00:16:30,982
comma minus nine or eight dot 8719843 and how far

244
00:16:30,982 --> 00:16:36,652
away are you from me Fredericksburg About four hours in

245
00:16:36,652 --> 00:16:41,832
my airplane I can't type that into Google What is

246
00:16:41,832 --> 00:16:49,212
OSM? I'm an OSM OpenStreetMap Oh, cool Yeah Finally, you're

247
00:16:49,212 --> 00:16:55,002
enjoying something. No, I am enjoying this debugging process. This

248
00:16:55,002 --> 00:16:59,142
is exactly how we have always done everything. Okay, you

249
00:16:59,142 --> 00:17:02,992
are 862 miles away from me. So I'm going to

250
00:17:02,992 --> 00:17:09,262
extend my search to 1,200 miles and say find podcasts

251
00:17:09,262 --> 00:17:13,062
near me, which is actually not a very accurate statement

252
00:17:13,062 --> 00:17:15,892
now that I've exerted it. None of this is near

253
00:17:15,892 --> 00:17:21,402
me. uh 138 miles what's the show we get to

254
00:17:21,402 --> 00:17:25,512
do this all right i'm up to 347 i have

255
00:17:25,512 --> 00:17:30,932
my location my open street map everything is in everything

256
00:17:30,932 --> 00:17:34,672
is good but yet but i'm up to 613 miles

257
00:17:34,672 --> 00:17:40,582
no no let's keep going 658 707 i'm just gonna

258
00:17:40,582 --> 00:17:43,402
go to true fans i'm sure they support it yes

259
00:17:43,402 --> 00:17:49,112
you know you know that they do 862 miles okay

260
00:17:49,112 --> 00:17:57,012
we're in the ballpark now please hey true 860 miles

261
00:17:57,332 --> 00:18:02,332
Truefans.com is something different. That's interesting. Did it change? No,

262
00:18:02,332 --> 00:18:05,092
it's, I don't think it's, I think it's .fm. There

263
00:18:05,092 --> 00:18:09,712
we go. Oh, yeah, .fm. Truefans.com is, what is that?

264
00:18:09,732 --> 00:18:16,812
Probably. Let me see what that is. Hmm. uh 2027

265
00:18:16,812 --> 00:18:21,342
be the tailwind we get to what is this i

266
00:18:21,342 --> 00:18:23,952
say it's there i'm looking at it we get to

267
00:18:23,952 --> 00:18:26,102
do this it's right here in the list says it's

268
00:18:26,102 --> 00:18:29,812
744 miles away from me okay fredericksburg gillespie county texas

269
00:18:29,812 --> 00:18:34,272
well how come i'm not seeing it online It was

270
00:18:34,272 --> 00:18:41,002
very, very strange. Matt, we'll see. Yep, links out to

271
00:18:41,002 --> 00:18:45,202
the map. Yep, there's Fredericksburg. Yeah, I see it. Now

272
00:18:45,202 --> 00:18:47,152
I see it, but it says, oh, okay, I see

273
00:18:47,152 --> 00:18:54,432
the problem. Apparently... This podcast made here. And I am

274
00:18:54,432 --> 00:18:59,402
literally, I'm literally five minutes from the church is 62

275
00:18:59,402 --> 00:19:05,272
miles away from me. Well, it's a – Fredericksburg is

276
00:19:05,272 --> 00:19:10,142
a big area. It's a big town. I mean, you're

277
00:19:10,142 --> 00:19:13,762
just putting in Fredericksburg. You didn't give it the exact

278
00:19:13,762 --> 00:19:17,042
street address of the church. That would have been more

279
00:19:17,042 --> 00:19:22,692
accurate. But Fredericksburg is – no. You're almost – No.

280
00:19:22,932 --> 00:19:27,902
No. No. 62 miles away, you're almost in Austin. So

281
00:19:27,902 --> 00:19:31,282
– I don't know why it has me. Well, where

282
00:19:31,282 --> 00:19:33,802
does it think? But it's using your browser location. Where

283
00:19:33,802 --> 00:19:37,262
does your browser think that it is? Well, how do

284
00:19:37,262 --> 00:19:43,742
I ask it that? Use the robot or something. Where

285
00:19:43,742 --> 00:19:46,372
are you? Let me go to maps. Let me see.

286
00:19:46,452 --> 00:19:48,362
Let me go to maps. Let's see what Google thinks

287
00:19:48,362 --> 00:19:53,532
I am. Google? Google? Ask Maps. What is this? Ask

288
00:19:53,532 --> 00:19:58,312
Maps? Oh, brother. More AI slob. Google crap. Yeah. Yeah.

289
00:19:59,282 --> 00:19:59,992
Uh...

290
00:20:00,054 --> 00:20:03,104
Well, it puts me... It puts me... I bet you

291
00:20:03,104 --> 00:20:06,024
it puts you somewhere goofy, like Austin. No, not at

292
00:20:06,024 --> 00:20:09,434
all. No, it puts me... Where are you getting this

293
00:20:09,434 --> 00:20:13,484
information? What do you mean? I'm just... From Google Maps?

294
00:20:14,024 --> 00:20:17,084
Yeah, I'm just opening up Google Maps, and then it

295
00:20:17,084 --> 00:20:23,794
shows... What does it show me? I mean, it opened

296
00:20:23,794 --> 00:20:28,854
up Fredericksburg approximately where I am, so... I'm just wondering,

297
00:20:28,854 --> 00:20:32,824
like, yeah, it's if you deal. It's centered right here.

298
00:20:33,164 --> 00:20:35,744
This is it says I am a 30 dot three

299
00:20:35,744 --> 00:20:40,104
one one six two eight eight comma minus ninety eight

300
00:20:40,104 --> 00:20:43,134
eight eight three nine nine four eight. Ah, that's your

301
00:20:43,134 --> 00:20:46,424
problem. No, it's not. It should be a three three

302
00:20:46,424 --> 00:20:50,484
one four seven dot seven seven. Bingo. Bingo. Anyway, we

303
00:20:50,484 --> 00:20:53,424
just debug this in real time. That's clearly the problem.

304
00:20:54,104 --> 00:20:57,644
No matter what you say, it's not 62 miles away.

305
00:20:58,144 --> 00:21:04,824
It's the lat-line triangulation hypothalamus inversion. That's your problem. Okay.

306
00:21:05,164 --> 00:21:11,444
Well, we're fixed now. Hmm. This is a beautiful product.

307
00:21:11,784 --> 00:21:15,414
It's a beautiful product. Yes, it is. Is the stream

308
00:21:15,414 --> 00:21:19,334
going down? Is it? Oh, it looks like it did

309
00:21:19,334 --> 00:21:23,244
go down for a minute. Yeah. It's back up. Yeah,

310
00:21:23,244 --> 00:21:29,244
it's back up. Okay. Yeah. Stuff happens. Anyway. Stuff happens.

311
00:21:30,184 --> 00:21:35,004
Radar.rss.io. Your results may vary due to road and weather

312
00:21:35,004 --> 00:21:38,724
conditions, but it's a beautiful product. It's a beautiful product.

313
00:21:39,084 --> 00:21:45,014
Due to browser geolocation and static. Yeah. Okay. But it's

314
00:21:45,014 --> 00:21:47,994
great, though. I love it. I can't wait to see

315
00:21:47,994 --> 00:21:52,104
what else people make with this wonderful new endpoint. I

316
00:21:52,104 --> 00:21:57,544
guarantee you this was handcrafted line by line by Alberto

317
00:21:57,544 --> 00:22:04,514
in the way that somebody would coil a coffee mug

318
00:22:04,514 --> 00:22:10,014
on a – On a one of those clay spinner

319
00:22:10,014 --> 00:22:19,204
things. Anyway, I. Are you ingesting episode level geolocation? Oh,

320
00:22:19,204 --> 00:22:21,244
yeah. Okay. For sure. All right. We were doing that

321
00:22:21,244 --> 00:22:24,024
first before we did the channel level. Okay. Okay. And

322
00:22:24,024 --> 00:22:26,854
so all that stuff is in there. Okay. Actually, the

323
00:22:26,854 --> 00:22:31,764
part I had to build was the channel. Right. Location.

324
00:22:32,444 --> 00:22:39,024
It's interesting, though, that it has to be channeled. That's

325
00:22:39,024 --> 00:22:41,854
not you. That's not you. That's not you. That's not

326
00:22:41,854 --> 00:22:45,104
you. No, I would assume that he's probably just going

327
00:22:45,104 --> 00:22:50,324
to, you know, add that later or something. Well, this

328
00:22:50,324 --> 00:22:51,574
is a new podcast. Or maybe this is a proof

329
00:22:51,574 --> 00:22:53,634
of concept. This is a new podcast app the way

330
00:22:53,634 --> 00:22:55,424
I see it. How come I can't play a podcast?

331
00:22:56,604 --> 00:22:59,424
Oh, good question. This is what I would be doing.

332
00:22:59,594 --> 00:23:02,194
Very good question. Well, I mean, you can click through

333
00:23:02,194 --> 00:23:04,424
the podcast index website, but we don't want to we

334
00:23:04,424 --> 00:23:07,034
don't want to be your player. No, no, we're not

335
00:23:07,034 --> 00:23:12,974
a good player. No, it's a player. We're not that

336
00:23:12,974 --> 00:23:17,724
either. We're not very good at that. This should be

337
00:23:17,724 --> 00:23:22,804
integrated into pod dot link. Daniel J. Lewis, stop it.

338
00:23:23,744 --> 00:23:29,844
Just stop. What did he say? What did he say?

339
00:23:30,024 --> 00:23:34,104
He said, are you ingesting chapter level location information? Man,

340
00:23:34,104 --> 00:23:37,204
I've only got so many hours in the day, brother.

341
00:23:37,314 --> 00:23:41,624
Like, I'm lucky to have gotten out what I got

342
00:23:41,624 --> 00:23:44,424
out this week, which this is not – location is

343
00:23:44,424 --> 00:23:50,004
not the only location. thing that I provided to the

344
00:23:50,004 --> 00:23:52,974
world this week. No, what you provided to the world

345
00:23:52,974 --> 00:23:59,454
this week, an unbelievable, just an amazing... Now I'm not

346
00:23:59,454 --> 00:24:04,404
sure what you're about to say. You fixed a bug.

347
00:24:05,984 --> 00:24:09,384
That not only did you fix it, but it was

348
00:24:09,384 --> 00:24:14,434
it was merged within like a week. Pretty quick. To

349
00:24:14,434 --> 00:24:18,324
a repo where there's a bunch of probably like –

350
00:24:18,674 --> 00:24:22,164
I don't want to say anything disparaging, but most of,

351
00:24:22,164 --> 00:24:25,184
you know, kind of like, you know, who are you,

352
00:24:25,184 --> 00:24:28,284
man? We know what we're doing over here. The WebKit

353
00:24:28,284 --> 00:24:33,784
people. And you want to explain this? Because this was

354
00:24:33,784 --> 00:24:35,444
merged with, and seriously, I think it was in a

355
00:24:35,444 --> 00:24:38,244
week or something. It's a little bit longer than that.

356
00:24:38,324 --> 00:24:41,164
It's a couple weeks. Explain the problem and how you

357
00:24:41,164 --> 00:24:44,274
fix it. Because this is a, you're right, it's a

358
00:24:44,274 --> 00:24:49,224
gift to the world. I provided the well it's July

359
00:24:49,224 --> 00:24:54,854
30th so what three weeks yes I did provide a

360
00:24:54,854 --> 00:25:00,154
gift to the world in the form of a bug

361
00:25:00,154 --> 00:25:06,194
submission to the WebKit repository. So let me explain what

362
00:25:06,194 --> 00:25:10,144
was happening. So as part of the work we're doing

363
00:25:10,144 --> 00:25:15,884
with Godcaster, we were ingesting a lot of live 365

364
00:25:15,884 --> 00:25:22,614
audio streams. And... The first issue that we had was

365
00:25:22,614 --> 00:25:29,104
getting the metadata out of the ICY interleave that happens

366
00:25:29,104 --> 00:25:34,794
in the – so these Live365 broadcasts a few different

367
00:25:34,794 --> 00:25:38,564
stream types. They do HLS as well, but – The

368
00:25:38,564 --> 00:25:42,284
main one that most people ingest is the MP3 stream.

369
00:25:43,044 --> 00:25:47,784
And that stream is just... uh mp3 frames um you

370
00:25:47,784 --> 00:25:51,744
know in in an endless stream just so it's basically

371
00:25:51,744 --> 00:25:56,084
the it's essentially the same file format as the mp3

372
00:25:56,084 --> 00:26:00,274
file itself and then you if you want to get

373
00:26:00,274 --> 00:26:05,864
metadata so like album art and uh, song title. Yeah.

374
00:26:05,884 --> 00:26:07,974
All the groovy stuff, the stuff, all the cool stuff

375
00:26:07,974 --> 00:26:10,514
looks good. Yeah. Yeah. If you want to get all

376
00:26:10,514 --> 00:26:16,264
that to display, then you have to, uh, you have

377
00:26:16,264 --> 00:26:19,054
to request it from the icy Y serve, sir, from

378
00:26:19,054 --> 00:26:23,004
the ice cast server. Um, And the way you do

379
00:26:23,004 --> 00:26:29,184
that is through a request is sending a header. along

380
00:26:29,184 --> 00:26:37,394
with the request of ICY-Metadata1. And so when you do

381
00:26:37,394 --> 00:26:41,074
that, the stream that you get back, the response, the

382
00:26:41,074 --> 00:26:44,164
byte stream response that you get back from the ICAST

383
00:26:44,164 --> 00:26:50,154
server will contain the metadata interleaved into the frames, the

384
00:26:50,154 --> 00:26:59,584
MP3 frames. All right, well... The problem with This the

385
00:26:59,584 --> 00:27:03,894
problem with the number one problem is cores. But wait

386
00:27:03,894 --> 00:27:06,684
a minute. It wasn't DNS because that's always the number

387
00:27:06,684 --> 00:27:09,574
one problem. But we ruled that one out. The number

388
00:27:09,574 --> 00:27:15,024
two problem is cores. So cores, a C-O-R-S is cross

389
00:27:15,024 --> 00:27:20,654
origin resource sharing. And that means it's. It's a core

390
00:27:20,654 --> 00:27:24,504
part of the security principles that govern web browsers and

391
00:27:24,504 --> 00:27:31,694
how they operate. So for security, the main browser firewall

392
00:27:31,694 --> 00:27:40,084
against shenanigans is cross-origin. So you cannot execute code in

393
00:27:40,084 --> 00:27:44,354
one domain directly. That came from another domain unless it's

394
00:27:44,354 --> 00:27:51,364
permitted. Yes. By the server of that other domain. So

395
00:27:51,364 --> 00:27:57,744
you had the solution to allow this in certain trusted

396
00:27:57,744 --> 00:28:02,634
cases that was settled upon was CORS, C-O-R-S, cross-origin resource

397
00:28:02,634 --> 00:28:10,234
sharing. So a server can... Send A course or a

398
00:28:10,234 --> 00:28:15,024
course request. And if – excuse me – a client

399
00:28:15,024 --> 00:28:18,874
can send a CORS request, and if the server supports

400
00:28:18,874 --> 00:28:21,844
CORS, if it wants to allow its code to be

401
00:28:21,844 --> 00:28:25,804
touched by other domains, it can say, yes, this is

402
00:28:25,804 --> 00:28:28,824
fine. And it can – there's a whole protocol for

403
00:28:28,824 --> 00:28:31,384
how to respond to that with – in the response

404
00:28:31,384 --> 00:28:42,444
headers. Mm-hmm. So... The issue is... So cores by default

405
00:28:42,444 --> 00:28:52,614
only responds with get requests. I believe by default, maybe

406
00:28:52,614 --> 00:28:58,734
post, but there's only a certain set of methods and

407
00:28:58,734 --> 00:29:01,754
headers that are sort of part that are part of

408
00:29:01,754 --> 00:29:05,254
like the base default. So a course request is allowed

409
00:29:05,254 --> 00:29:08,124
to think to do get and post and also by

410
00:29:08,124 --> 00:29:17,264
default and also. have certain base headers like range request,

411
00:29:17,264 --> 00:29:25,774
date, all the normal headers, content type, content disposition. If

412
00:29:25,774 --> 00:29:30,214
you add any headers in your course request that are

413
00:29:30,214 --> 00:29:33,964
not part of the standard set, you have to do

414
00:29:33,964 --> 00:29:38,064
a second call before you do that call to alert

415
00:29:38,064 --> 00:29:43,454
the browser of what this course request is going to

416
00:29:43,454 --> 00:29:47,384
be capable of sending. So if we want to send

417
00:29:47,384 --> 00:29:50,404
from our – this begins to get pretty complicated. No

418
00:29:50,404 --> 00:29:56,054
kidding. If we want to send – so think about

419
00:29:56,054 --> 00:29:59,164
this app, okay?

420
00:30:00,530 --> 00:30:05,290
If this browser app wants to start playing a live

421
00:30:05,290 --> 00:30:12,220
365 audio stream with metadata, it's The browser page code

422
00:30:12,220 --> 00:30:19,220
itself has to send a course request to... Because it's

423
00:30:19,220 --> 00:30:22,830
going to be sending this ICY metadata header, which is

424
00:30:22,830 --> 00:30:25,480
nonstandard. And you want to display it in the player,

425
00:30:25,480 --> 00:30:27,910
which is on the webpage. I'll just help you around

426
00:30:27,910 --> 00:30:31,540
here. Exactly. So if you're going to send that nonstandard

427
00:30:31,540 --> 00:30:35,620
ICY metadata header, you have to send what's called a

428
00:30:35,620 --> 00:30:43,960
CORS pre-flight request. Pre-flight? Why is it pre-flight? Because it's

429
00:30:43,960 --> 00:30:47,840
before your main request. Why is it before your main

430
00:30:47,840 --> 00:30:52,570
request? Because it's going to check with the server ahead

431
00:30:52,570 --> 00:30:56,850
of time to see... If that header, if those headers

432
00:30:56,850 --> 00:31:00,820
you're requesting are supported by cores. Ah, okay. I got

433
00:31:00,820 --> 00:31:06,020
you. So headers, and this is just as an aside,

434
00:31:06,020 --> 00:31:12,660
headers can be dangerous. Some people may not realize this.

435
00:31:13,100 --> 00:31:17,290
But headers themselves can be dangerous in certain circumstances. Buffer

436
00:31:17,290 --> 00:31:20,580
overflows can happen that way. Dave, hold on a second.

437
00:31:20,680 --> 00:31:24,450
I've got a buzz. Are you eating chocolate again? No,

438
00:31:24,450 --> 00:31:27,510
no. No chocolate love today. Take the chocolate love away,

439
00:31:27,510 --> 00:31:32,570
man. Okay, you're good. Okay. So headers themselves can be

440
00:31:32,570 --> 00:31:37,130
dangerous. And that's why cores limits them and call. And

441
00:31:37,130 --> 00:31:39,350
so you have to go. You're like, OK, I'm going

442
00:31:39,350 --> 00:31:42,190
to call 365. I'm going to call live 365 with

443
00:31:42,190 --> 00:31:45,360
the IC metadata header. When you do that, the browser

444
00:31:45,360 --> 00:31:49,100
is going to send a course preflight request. Right. And

445
00:31:49,100 --> 00:31:55,970
that uses the HTTP options method. Wow. So the options

446
00:31:55,970 --> 00:32:03,620
method is sent to the destination host with the request

447
00:32:03,620 --> 00:32:11,010
headers that you're asking for. The server then will either

448
00:32:11,010 --> 00:32:19,810
deny it or respond with the appropriate header saying, yeah,

449
00:32:19,810 --> 00:32:27,190
this is fine. That is just standard behavior. Right. As

450
00:32:27,190 --> 00:32:33,000
part of the core's documentation, I think, What it says

451
00:32:33,000 --> 00:32:36,840
is that the body of the response of this options

452
00:32:36,840 --> 00:32:44,800
pre-flight response, the body can be – a text description

453
00:32:45,300 --> 00:32:48,990
Of some sort, like like a header allowed or this

454
00:32:48,990 --> 00:32:52,310
is fine or just some piece of text. Here's what

455
00:32:52,310 --> 00:32:54,750
I think happened. You put in this you put in

456
00:32:54,750 --> 00:32:57,980
this PR, you put in this pull request and the

457
00:32:57,980 --> 00:33:01,740
guys who are maintaining would like to this guy sounds

458
00:33:01,740 --> 00:33:06,010
so knowledgeable. Just merge it. Just merge it already. That

459
00:33:06,010 --> 00:33:08,730
is not. I promise you that's not what happened. Merge

460
00:33:08,730 --> 00:33:12,300
it in. I'm sure this is exactly right. Whatever Dave

461
00:33:12,300 --> 00:33:17,680
Jones is saying, merge it. Yeah, that's – whatever happened,

462
00:33:17,680 --> 00:33:23,840
that's not it. Okay, so you fixed it. Well, let

463
00:33:23,840 --> 00:33:29,360
me finish. Let me finish. We're going super nerd here.

464
00:33:29,360 --> 00:33:34,490
The members of the board are falling asleep. No, this

465
00:33:34,490 --> 00:33:38,100
– even Eric PP said this is way too complicated.

466
00:33:38,420 --> 00:33:41,290
Yeah. So – oh, he said, what happens if you

467
00:33:41,290 --> 00:33:44,690
just throw the headers at the server without the options

468
00:33:44,690 --> 00:33:48,110
check? Well, it's the browser that's enforcing this. Yeah, and

469
00:33:48,110 --> 00:33:51,650
that's Safari specifically, right? Well, you can't – all of

470
00:33:51,650 --> 00:33:55,070
them. Oh, okay. You can't stop – It from sending

471
00:33:55,070 --> 00:33:57,800
this. If you if you have nonstandard headers, it's going

472
00:33:57,800 --> 00:34:00,760
to check. It's going to send a pre-flight request no

473
00:34:00,760 --> 00:34:03,710
matter what you do. So you have to deal with

474
00:34:03,710 --> 00:34:08,910
this. And the so what was happening was every time

475
00:34:08,910 --> 00:34:15,060
you send the request, every time we sent this request.

476
00:34:15,050 --> 00:34:18,000
It would work. First, we had to get Live 365

477
00:34:18,000 --> 00:34:20,260
to fix – to add cores properly. And props to

478
00:34:20,260 --> 00:34:23,360
those people over there at Live 365. Props to them,

479
00:34:23,360 --> 00:34:25,900
man. That was beautiful. And I love that they just

480
00:34:25,900 --> 00:34:29,020
went, oh, yeah, okay, we'll work on this. And they

481
00:34:29,020 --> 00:34:31,530
didn't quite do it at the first time. Then the

482
00:34:31,530 --> 00:34:33,780
second time, like, oh, okay, we'll fix it. They did

483
00:34:33,780 --> 00:34:36,310
it. That was really – I was impressed by –

484
00:34:36,310 --> 00:34:39,300
that was the internet of the old days, like 90s.

485
00:34:39,960 --> 00:34:42,550
Hey, man. Oh, so much. Your stuff is broken. Okay,

486
00:34:42,550 --> 00:34:44,610
I'll fix it. That was beautiful. And they're not a

487
00:34:44,610 --> 00:34:49,960
small company. But the two attempts to fix it actually

488
00:34:49,960 --> 00:34:52,520
is – is part of this story. That's what caused

489
00:34:52,520 --> 00:34:55,800
us to find this bug. Exactly. So did you credit

490
00:34:55,800 --> 00:34:58,700
them on the PR? No. Absolutely. Oh, you did? No,

491
00:34:58,700 --> 00:35:03,060
I did. Yes, I did. I totally did. Yes, I

492
00:35:03,060 --> 00:35:06,580
said. Well, if you call credit saying that it was

493
00:35:06,580 --> 00:35:09,720
their fault. Give me some credit, man. Give me some

494
00:35:09,720 --> 00:35:14,300
credit. It was their fault. I just need some credit.

495
00:35:16,650 --> 00:35:20,440
The – okay, so the first time – You've got

496
00:35:20,440 --> 00:35:25,850
me giggling now. Did Adam even read the PR? Of

497
00:35:25,850 --> 00:35:28,540
course he didn't read the PR. He read it. You

498
00:35:28,540 --> 00:35:31,120
know what I did? I said, robot, give me a

499
00:35:31,120 --> 00:35:38,050
summary of what just happened here. So – The issue

500
00:35:38,050 --> 00:35:39,660
– the first – so what I did was I

501
00:35:39,660 --> 00:35:43,210
contacted them and I said, look, I can't – it

502
00:35:43,210 --> 00:35:48,130
was weird because they – the way their system works

503
00:35:48,130 --> 00:35:51,620
is they have a sort of a front door node.

504
00:35:51,740 --> 00:35:54,360
I mean this is typical CDN behavior. They had like

505
00:35:54,360 --> 00:35:57,460
a front door – A node that you would hit,

506
00:35:57,460 --> 00:36:02,500
so something.live3c5.com or FM or whatever it is, you would

507
00:36:02,500 --> 00:36:06,210
hit that trying to get the audio stream, and that

508
00:36:06,210 --> 00:36:10,810
node, that server would respond properly with a course response

509
00:36:10,810 --> 00:36:15,890
saying, yeah, you're good. Hmm. The next thing it does

510
00:36:15,890 --> 00:36:18,890
is it 302 redirects you to an edge node on

511
00:36:18,890 --> 00:36:22,380
their CDN. So you get bounced to a different server.

512
00:36:22,500 --> 00:36:25,680
And that's where it failed. That server would deny the

513
00:36:25,680 --> 00:36:29,200
course request. Right. Got it. And so this to us

514
00:36:29,200 --> 00:36:32,870
looks like. That's exactly what I read in the pull

515
00:36:32,870 --> 00:36:38,820
request. You did not. So this... So what we told

516
00:36:38,820 --> 00:36:41,720
them was like, hey, look, this looks like maybe a

517
00:36:41,720 --> 00:36:46,760
misconfiguration on your part because you clearly are allowing cores

518
00:36:46,760 --> 00:36:50,300
in the front door. But then when you bounce over

519
00:36:50,300 --> 00:36:54,430
to the actual stream box, it's killing it. And whoever

520
00:36:54,430 --> 00:36:58,450
I talked to said, oh, let me – Let me

521
00:36:58,450 --> 00:37:00,480
check with the engineer team And they were like yeah

522
00:37:00,480 --> 00:37:06,410
We've got it fixed now And so they – what

523
00:37:06,410 --> 00:37:09,740
they did – and now this part is total guesswork

524
00:37:09,740 --> 00:37:12,900
on me, and Paul thinks this is the case as

525
00:37:12,900 --> 00:37:17,040
well, but we don't have any way of knowing this.

526
00:37:17,700 --> 00:37:23,040
I think what they did was they just cloned –

527
00:37:23,940 --> 00:37:29,400
And the – not clone. They aliased all the possible

528
00:37:29,400 --> 00:37:34,280
– Oh, to the main server. Routes. Yeah. Yeah, so

529
00:37:34,280 --> 00:37:37,810
what they did was they like – they made get,

530
00:37:37,810 --> 00:37:42,020
post, all the – basically all the different methods of

531
00:37:42,020 --> 00:37:46,650
HTTP respond the same way. Mm-hmm. So if you think

532
00:37:46,650 --> 00:37:55,390
about this for a second – If. If you have

533
00:37:55,390 --> 00:38:00,060
a box that responds over HTTP to a GET request

534
00:38:00,060 --> 00:38:05,480
for audio streams... When I send you a GET request,

535
00:38:05,480 --> 00:38:09,200
it's going to begin streaming MP3, endless MP3 bytes to

536
00:38:09,200 --> 00:38:17,240
me. If I also make that same get request... Respond

537
00:38:17,240 --> 00:38:21,450
that route on the server if I make that same

538
00:38:21,450 --> 00:38:27,160
route respond also to options request or head request or

539
00:38:27,160 --> 00:38:32,610
any other HTTP method. All of those methods are just

540
00:38:32,610 --> 00:38:35,350
going to begin to get the same thing. They're going

541
00:38:35,350 --> 00:38:38,440
to get a stream of MP3 bytes. So they just

542
00:38:38,440 --> 00:38:43,480
aliased options method to respond in the same way that

543
00:38:43,480 --> 00:38:48,500
a get request responds. Which could be a security issue.

544
00:38:50,200 --> 00:38:53,380
I mean, maybe. I just threw that out there. I

545
00:38:53,380 --> 00:38:56,360
have no idea what I'm talking about. I mean, it's

546
00:38:56,360 --> 00:39:01,980
possible, but I don't. But here's the confusing part. So

547
00:39:01,980 --> 00:39:03,840
when he came back and he said, yeah, it's fixed.

548
00:39:04,060 --> 00:39:08,330
We got you covered. I ran the tests, the little

549
00:39:08,330 --> 00:39:12,730
demo to check all the things. Yeah, you even gave

550
00:39:12,730 --> 00:39:15,370
them a little demo app to check. You're so good,

551
00:39:15,370 --> 00:39:17,550
man. I saw it. So I ran that, and I

552
00:39:17,550 --> 00:39:21,190
was like, okay, yeah, it works. I checked it on

553
00:39:21,190 --> 00:39:24,820
Chrome. I'm like, this is great. And I checked it

554
00:39:24,820 --> 00:39:28,620
on Android. It looks great. And on iPhone, it just

555
00:39:28,620 --> 00:39:33,340
crapped out. Bombed. It just crapped. And I was like,

556
00:39:33,340 --> 00:39:37,920
wait, this something doesn't make sense. And I could not

557
00:39:37,920 --> 00:39:41,020
figure this out. And so I had to go –

558
00:39:41,020 --> 00:39:44,980
I had to get into the clawed session, and I'm

559
00:39:44,980 --> 00:39:48,320
like, look, I'm trying to play this thing on the

560
00:39:48,320 --> 00:39:51,490
iPhone. I cannot figure out why this thing is not

561
00:39:51,490 --> 00:39:58,530
working. And so it starts just hitting it with different

562
00:39:58,530 --> 00:39:59,980
things, you know, like it,

563
00:40:00,032 --> 00:40:02,532
It starts following the chain over and over and over.

564
00:40:03,632 --> 00:40:08,772
And it finally came back and it said – It

565
00:40:08,772 --> 00:40:12,182
said it basically said this is strange because when I

566
00:40:12,182 --> 00:40:17,292
send an options method request to the CDN edge node.

567
00:40:18,522 --> 00:40:21,972
It responds with a 200, but then it also starts

568
00:40:21,972 --> 00:40:26,472
streaming audio. Ooh. Is that when it said, ugh, I

569
00:40:26,472 --> 00:40:30,042
confuse myself. Let me do this carefully. No, that was

570
00:40:30,042 --> 00:40:34,572
it. I love those. I love those little stupid things.

571
00:40:35,312 --> 00:40:37,352
This was not it, though. But he said, and I

572
00:40:37,352 --> 00:40:41,642
was like, wait, that's probably not good, I guess. Well,

573
00:40:41,642 --> 00:40:49,382
it turns out that Chrome and Firefox... They... Properly, and

574
00:40:49,382 --> 00:40:53,112
I say properly in very loose quotes because this is

575
00:40:53,112 --> 00:40:59,472
actually not very well specified in the CORS documentation. So

576
00:40:59,472 --> 00:41:02,572
this really doesn't come down to a matter of WebKit

577
00:41:02,572 --> 00:41:07,452
Safari not following the core spec because this actually is

578
00:41:07,452 --> 00:41:12,212
ambiguous in the spec. Hmm. It's more of an issue

579
00:41:12,212 --> 00:41:18,252
of it's just... Probably the best behavior because if you

580
00:41:18,252 --> 00:41:22,392
don't ignore the body, what was happening was Safari was

581
00:41:22,392 --> 00:41:27,102
properly sending the course preflight request, and the request was

582
00:41:27,102 --> 00:41:32,332
replying with an MP3 string. Not what we wanted. And

583
00:41:32,332 --> 00:41:36,302
what that was doing, that was dead-hanging Safari. It would

584
00:41:36,302 --> 00:41:41,712
never move past the pre-flight. So the page itself would

585
00:41:41,712 --> 00:41:48,172
just freeze. It could not move past that. Whereas Chrome,

586
00:41:48,172 --> 00:41:52,092
what it does, and Firefox and other browsers, as soon

587
00:41:52,092 --> 00:41:55,572
as they see the 200 or the 202 come back.

588
00:41:55,672 --> 00:41:59,122
They're good. They move on. They're like, good. They completely

589
00:41:59,122 --> 00:42:02,272
ignore the body. They don't try to ingest it. Is

590
00:42:02,272 --> 00:42:05,302
a dead-hanging safari, is that a mission trip I can

591
00:42:05,302 --> 00:42:13,352
take to Africa? It's a ride at Disney World. You're

592
00:42:13,352 --> 00:42:16,522
sharp today, Dave Jones. I like it. I like this

593
00:42:16,522 --> 00:42:20,452
Dave Jones. Yeah. I got my chocolate. It's not Choco

594
00:42:20,452 --> 00:42:25,032
Love, though. No Choco Love. No Choco Love money back.

595
00:42:26,512 --> 00:42:29,642
So, yeah, so that was the bug report. The bug

596
00:42:29,642 --> 00:42:35,362
report was basically you're getting hung up. By the sir

597
00:42:35,362 --> 00:42:38,312
that if you want to boil it down to what

598
00:42:38,312 --> 00:42:42,532
the problem is, the problem is Safari was letting the

599
00:42:42,532 --> 00:42:47,002
server dictate its behavior. Yeah. And you get that's no

600
00:42:47,002 --> 00:42:49,642
good. You can't do that. Right. And so they fixed

601
00:42:49,642 --> 00:42:53,522
it. And this will help other people, not just Live

602
00:42:53,522 --> 00:42:57,412
365 and browsers? This will be helpful for other applications

603
00:42:57,412 --> 00:43:01,632
in the future or current? Yeah, absolutely. Yeah, that's great.

604
00:43:02,072 --> 00:43:04,402
I think what's – I could not find this bug

605
00:43:04,402 --> 00:43:07,972
reported anywhere. Clearly it wasn't because it got accepted and

606
00:43:07,972 --> 00:43:11,072
merged. So I couldn't find this bug reported anywhere anywhere.

607
00:43:11,602 --> 00:43:14,852
And the – so I think probably what happens is

608
00:43:14,852 --> 00:43:18,412
people just – it was such a confusing thing to

609
00:43:18,412 --> 00:43:23,192
watch that it was hard to diagnose, and people probably

610
00:43:23,192 --> 00:43:27,032
just figured out a workaround or just made do with

611
00:43:27,032 --> 00:43:32,392
never fixing it. Yeah. But the product that we're building

612
00:43:32,392 --> 00:43:35,872
specifically for this, though, that was like a complete deal

613
00:43:35,872 --> 00:43:38,932
killer. It was going to be very hard to work

614
00:43:38,932 --> 00:43:44,312
around that. So we really had to fix this. And

615
00:43:44,312 --> 00:43:50,392
this concludes Dave's Bug Report of the Day. Dave. of

616
00:43:50,392 --> 00:43:54,812
the month. Of the month, baby. Thank you, Eric PP.

617
00:43:55,412 --> 00:43:59,132
And then, of course, you introduced the bug into Podping

618
00:43:59,132 --> 00:44:03,062
and ate up everybody's RAM. That was great. RAM is

619
00:44:03,062 --> 00:44:08,542
so cheap right now. It shouldn't matter. Wow. Just throw

620
00:44:08,542 --> 00:44:12,382
more at it. Just throw more. We'll get there. I

621
00:44:12,382 --> 00:44:16,882
got it. I'm not even halfway done yet. What? You

622
00:44:16,882 --> 00:44:20,112
got more? Yeah, I did more this week. Oh, no,

623
00:44:20,112 --> 00:44:22,672
I thought you had more on the on the Coors

624
00:44:22,672 --> 00:44:27,672
Report. The Coors Report. There's another great podcast title. Welcome

625
00:44:27,672 --> 00:44:31,532
to the Coors Report. The most boring podcast ever. The

626
00:44:31,532 --> 00:44:39,572
Coors Report. The Coors Report. Okay. What else you got,

627
00:44:39,572 --> 00:44:43,982
man? What else did you do? Oh, well, I... A

628
00:44:43,982 --> 00:44:49,992
podcast person tag. Wait before you get there. Okay. Pausing.

629
00:44:50,552 --> 00:44:56,652
Thank you. Thank you, John Spurlock. You know, Spurlock just

630
00:44:56,652 --> 00:44:58,842
I always when the first thing I do in the

631
00:44:58,842 --> 00:45:01,582
morning, I wake up. It's like, let me go see

632
00:45:01,582 --> 00:45:04,812
what what Spurlock put to what he posted about, except

633
00:45:04,812 --> 00:45:08,252
when he when he's going through like that. Here's all

634
00:45:08,252 --> 00:45:11,752
the Apple. What is the what is Apple's IDE? What

635
00:45:11,752 --> 00:45:16,472
is that called? Oh, Xcode. Yeah. Here's all the Xcode

636
00:45:16,472 --> 00:45:22,352
diffs. Like, no, no. That's horrible stuff. No, no, no.

637
00:45:22,432 --> 00:45:25,322
That is horrible. That is like that just that's a

638
00:45:25,322 --> 00:45:31,962
pollution of my browser. But he posted a link. To

639
00:45:31,962 --> 00:45:41,472
the, what is it, the ASD-STE100 Simplified Technical English. which

640
00:45:41,472 --> 00:45:45,612
you can tell your robot to use, and it has

641
00:45:45,612 --> 00:45:53,832
improved my quality of life just with a magnitude. And

642
00:45:53,832 --> 00:45:58,002
I'm so grateful for that. Please describe this. Well, if

643
00:45:58,002 --> 00:46:00,592
you've been using Claude Code as your robot, which I

644
00:46:00,592 --> 00:46:05,212
do, um... And Claude is just, it's so chatty and

645
00:46:05,212 --> 00:46:08,532
it's like, I found the smoking gun. This is the

646
00:46:08,532 --> 00:46:11,052
load-bearing issue we need to look at. But in my

647
00:46:11,052 --> 00:46:13,732
honest opinion, hey, just say the word. I'll go and

648
00:46:13,732 --> 00:46:16,652
fix that. Wait, I have the full picture now. You're

649
00:46:16,652 --> 00:46:21,002
right to push back. This shapes the entire conversation. I

650
00:46:21,002 --> 00:46:28,312
was so sick of that nonsense. Gated? Everything's gated. Well,

651
00:46:28,312 --> 00:46:32,092
the gates I kind of like because I have a

652
00:46:32,092 --> 00:46:34,402
lot of – Load bearing. Well, the gates are important

653
00:46:34,402 --> 00:46:37,442
for me because gates is like, well, this thing doesn't

654
00:46:37,442 --> 00:46:39,752
pass the gate. And then I know what it is.

655
00:46:39,752 --> 00:46:42,432
Okay, so I understand what the gate is doing. The

656
00:46:42,432 --> 00:46:44,092
gate means you don't go to the next step. I'm

657
00:46:44,092 --> 00:46:48,732
okay with that. But just this on and on and

658
00:46:48,732 --> 00:46:53,402
on, I just... And every single time I'd say, please,

659
00:46:53,402 --> 00:46:57,892
just speak in simple English. Don't talk like an agent.

660
00:46:58,512 --> 00:47:03,052
And they're right. My bad. And then it writes, let

661
00:47:03,052 --> 00:47:05,612
me record this to memory so I don't do it

662
00:47:05,612 --> 00:47:10,712
again. Five minutes later. It's back to, but when you...

663
00:47:11,102 --> 00:47:14,712
See, what is the... Claude, the right – wait a

664
00:47:14,712 --> 00:47:18,862
minute. What is it? There's – here. You post into

665
00:47:18,862 --> 00:47:25,032
Claude, only report to me an ASD-STE100 simplified technical English.

666
00:47:25,732 --> 00:47:28,732
And you tell it to make a memory of this.

667
00:47:29,412 --> 00:47:31,442
It does it. It does it. And now it's like

668
00:47:31,442 --> 00:47:35,392
it's still chatty, but it's not as annoying. It's a

669
00:47:35,392 --> 00:47:39,092
big difference. I feel it's a big, big difference. I'm

670
00:47:39,092 --> 00:47:43,292
happy with it. Thank you, John Spurlock. Let's see. I'll

671
00:47:43,292 --> 00:47:49,912
just post that at ASDSTE100. Dash, dash, dash, STE100. We

672
00:47:49,912 --> 00:47:52,262
have to say make a memory of it. You got

673
00:47:52,262 --> 00:47:56,372
to say make a memory of it. European Union trademark.

674
00:47:57,012 --> 00:48:00,312
I don't know what you're looking at. I'm on the

675
00:48:00,312 --> 00:48:03,642
– they got a homepage. They do? Oh, yeah. Yeah,

676
00:48:03,642 --> 00:48:11,992
asd-ste100.org. Yeah. Simplified standards for technical documentation. Yes. Hey, request

677
00:48:11,992 --> 00:48:15,982
your free official copy. This is nice. This seems very

678
00:48:15,982 --> 00:48:19,832
European to me. Well, I don't know what it is,

679
00:48:19,832 --> 00:48:23,582
but it is stop my robot from spewing out verbal

680
00:48:23,582 --> 00:48:30,902
diarrhea. Very, very pleased with it. Very pleased. Yeah. I

681
00:48:30,902 --> 00:48:34,112
like how part of the definition of this thing, I

682
00:48:34,112 --> 00:48:36,892
can't – you sent me this, and I looked it

683
00:48:36,892 --> 00:48:40,472
up. It's a fact. Let's see what their fact is.

684
00:48:40,472 --> 00:48:46,992
Fact. What is ASD, SDE 100 Simplified Technical English? It

685
00:48:46,992 --> 00:48:51,582
says something about the dictionary. Approved words that a writer

686
00:48:51,582 --> 00:48:54,862
can use. The approved words were selected because they were

687
00:48:54,862 --> 00:48:58,942
simple, easy to recognize. In general, each word has only

688
00:48:58,942 --> 00:49:01,732
one meaning and is approved with only one part of

689
00:49:01,732 --> 00:49:05,882
speech. Nice. Nice. For example, to fall has the approved

690
00:49:05,882 --> 00:49:08,832
meaning of to move down by the force of gravity

691
00:49:08,832 --> 00:49:12,252
and not to decrease. I don't know about – this

692
00:49:12,252 --> 00:49:15,982
seems like a stretch to me, but if it makes

693
00:49:15,982 --> 00:49:20,212
the robot less stupid, then fine. Oh, yeah. You can

694
00:49:20,212 --> 00:49:25,142
always undo it. Yeah, sure, yeah. Maybe, maybe there for

695
00:49:25,142 --> 00:49:28,472
every standard, there's always a competing standard. So I wonder

696
00:49:28,472 --> 00:49:31,872
what the competing standard to the ASD SDE 100 is.

697
00:49:32,612 --> 00:49:36,432
Speaking of what happened to what happened to Dave Weiner?

698
00:49:37,092 --> 00:49:40,292
Something happened to Dave Weiner. What do you mean happened?

699
00:49:41,022 --> 00:49:43,782
Uh, he like blew up half his stuff. Yeah. I

700
00:49:43,782 --> 00:49:45,792
think that's what happened. Is that because of Claude? Yeah,

701
00:49:45,852 --> 00:49:49,592
probably. Claude wrote test file. Oh yeah. Yeah. Okay. Yeah.

702
00:49:49,612 --> 00:49:53,872
He blew away like important things. I have no idea

703
00:49:53,872 --> 00:49:57,232
how useful these things would be if it destroyed stuff

704
00:49:57,232 --> 00:49:59,992
and deployed projects with real users. Uh,

705
00:50:00,074 --> 00:50:03,724
It will do it. That's what it does. Yep. Which

706
00:50:03,724 --> 00:50:06,964
brings me to some things that I've been working on.

707
00:50:07,204 --> 00:50:14,614
Okay. But wait, there's more. Ew. The well, I'll we'll

708
00:50:14,614 --> 00:50:16,884
talk about the person tag in a second. So one

709
00:50:16,884 --> 00:50:19,264
thing I've been doing, I'm not I'm not going to

710
00:50:19,264 --> 00:50:23,164
actually say what the project is. Yeah. Alex Gates, he

711
00:50:23,164 --> 00:50:27,604
spotted a little bit of it. But I'm trying to

712
00:50:27,604 --> 00:50:34,994
challenge myself to not really use AI more because I

713
00:50:34,994 --> 00:50:38,814
use it every day in various ways. Oh, I know

714
00:50:38,814 --> 00:50:42,044
what this is. You deployed a Linode and had Claude

715
00:50:42,044 --> 00:50:47,144
do something. Yeah. No, no, no, not Claude. Not Claude.

716
00:50:47,144 --> 00:50:55,474
Oh, pie. Pie? Pie. Pie. Yes. So. Which according to

717
00:50:55,474 --> 00:50:59,604
ASD is a tasty dessert treat. There's only one meaning.

718
00:50:59,604 --> 00:51:06,384
There's only one meaning. Apple pie. Yes. So one thing

719
00:51:06,384 --> 00:51:10,764
I've not done much of because it just terrifies me.

720
00:51:10,844 --> 00:51:13,864
Because you don't live like me on the edge. I'm

721
00:51:13,864 --> 00:51:17,544
not a YOLO kind of fellow. Oh, I'm not YOLO.

722
00:51:17,544 --> 00:51:22,474
Uh-uh. I'm not YOLO. What would you use? What's a

723
00:51:22,474 --> 00:51:25,254
better term then for the way that you handle your

724
00:51:25,254 --> 00:51:30,024
robot? Dangerous would be the term. Dangerous. That's worse than

725
00:51:30,024 --> 00:51:37,124
YOLO. Dangerous. That's intentionally sketchy. Completely dangerous, yes. Right. reckless.

726
00:51:37,964 --> 00:51:41,604
Reckless, yes. Reckless is good. Hashtag reckless. I'm like, Gordon,

727
00:51:41,604 --> 00:51:46,494
go ahead. Deploy to customers. I'm good. It works. The

728
00:51:46,494 --> 00:51:49,764
interaction between you two is really funny because you're like,

729
00:51:49,764 --> 00:51:52,714
wait, wait, you put this live on a customer? He's

730
00:51:52,714 --> 00:51:55,884
like, yeah. And you're like, you weren't supposed to do

731
00:51:55,884 --> 00:51:58,804
that, and then like five minutes. later you're like, oh,

732
00:51:58,804 --> 00:52:01,804
I'm fixing it. Don't worry about it. It's all good.

733
00:52:02,164 --> 00:52:06,474
We're doing it live. You're like, hey, that actually worked

734
00:52:06,474 --> 00:52:10,814
out. Let's keep going. Yeah, exactly. Exactly. Okay. So what

735
00:52:10,814 --> 00:52:16,524
I did was I... I created a Linode VM in

736
00:52:16,524 --> 00:52:20,864
an account that had nothing else in it. Okay. Oh,

737
00:52:20,864 --> 00:52:24,004
wow. So this thing is in a silo. It's walled

738
00:52:24,004 --> 00:52:29,684
off. It's siloed. Yes. It's gated. It's behind a gate.

739
00:52:29,684 --> 00:52:36,004
It's gated. It's gated. So I did that, and then

740
00:52:36,004 --> 00:52:41,764
I've had this idea for a project forever. I mean,

741
00:52:41,764 --> 00:52:45,764
for like I don't know, three years now. Oh, wow.

742
00:52:46,604 --> 00:52:49,164
It's always been in the back of my mind, and

743
00:52:49,164 --> 00:52:51,364
I've always kind of thought, hmm, I wonder if that

744
00:52:51,364 --> 00:52:57,884
would work. And I actually started writing it before AI

745
00:52:57,884 --> 00:53:02,784
was even a thing. or LLMs or even a thing.

746
00:53:03,244 --> 00:53:08,364
And so maybe, I don't know, 2022 or something. And

747
00:53:08,364 --> 00:53:11,904
I had some stuff written, and I was like, you

748
00:53:11,904 --> 00:53:16,574
know, this would be a really good project to test

749
00:53:16,574 --> 00:53:23,084
out like a fully autonomous agent setup. Because that's something

750
00:53:23,084 --> 00:53:26,434
I just really never do. The way I use AI

751
00:53:26,434 --> 00:53:28,844
is I have this – I have – a problem

752
00:53:28,844 --> 00:53:31,334
that I can't solve, and I go and I get

753
00:53:31,334 --> 00:53:36,704
some help with it. and that's because I just don't

754
00:53:36,704 --> 00:53:40,044
trust it. Are you familiar with the Claude setting that

755
00:53:40,044 --> 00:53:44,204
is basically go ahead, do anything you want, live dangerously?

756
00:53:44,384 --> 00:53:48,244
That will never happen. I'll never do that. It's awesome.

757
00:53:48,244 --> 00:53:51,744
No, no. Well, that's what pie does out of the

758
00:53:51,744 --> 00:53:55,174
box. Oh, okay, good. Yeah, that's basically it in a

759
00:53:55,174 --> 00:54:00,754
nutshell. It has no guardrails. And so I thought, OK,

760
00:54:00,754 --> 00:54:04,664
well, let me just point this thing at this repo

761
00:54:04,664 --> 00:54:08,934
that I've been having cities that has sitting here for

762
00:54:08,934 --> 00:54:14,824
years. And so this is Pi connected to – what

763
00:54:14,824 --> 00:54:22,414
I use Pi for mostly is podcast index-related things, so

764
00:54:22,414 --> 00:54:31,724
helping me build the model – The local model for

765
00:54:31,724 --> 00:54:38,084
on the DGX Spark for classification, spam classification. It runs

766
00:54:38,084 --> 00:54:43,634
the classifier. So it's basically anything podcast index related is

767
00:54:43,634 --> 00:54:48,774
usually I don't typically do clawed stuff with that. And

768
00:54:48,774 --> 00:54:52,294
sometimes the only project I've really done on that is

769
00:54:52,294 --> 00:54:55,604
– help with that is Podping because I just didn't

770
00:54:55,604 --> 00:54:58,904
understand Eero enough. So I've had – I did that.

771
00:54:58,984 --> 00:55:04,244
But everything really like core podcast index related usually goes

772
00:55:04,244 --> 00:55:08,964
through the local DGX with Pi. And I thought, okay.

773
00:55:09,514 --> 00:55:13,764
I want to try out this new Quinn 3.827B model.

774
00:55:14,624 --> 00:55:18,724
It's supposed to be the new hotness. And I also

775
00:55:18,724 --> 00:55:23,714
want to get a feeling for just like autonomous agent

776
00:55:23,714 --> 00:55:28,424
stuff. So I threw the 27B model onto the DGX,

777
00:55:28,424 --> 00:55:32,874
and I just aimed pi at this repo of this

778
00:55:32,874 --> 00:55:36,704
project that I've been brainstorming for years and said –

779
00:55:37,394 --> 00:55:42,524
Here's a VM in Linode. Here's an SSH key. Go

780
00:55:42,524 --> 00:55:46,964
try to build this thing. And I was just like,

781
00:55:46,964 --> 00:55:48,884
I'm just going to step back and go have lunch

782
00:55:48,884 --> 00:55:53,804
and come back later and just see what it did.

783
00:55:54,384 --> 00:56:00,134
This thing worked for like three hours. Wow. Non-stop. Chugging

784
00:56:00,134 --> 00:56:04,024
non-stop. Didn't ask you to... Is this okay? Can I

785
00:56:04,024 --> 00:56:06,314
move ahead? None of them. Never asked me a single

786
00:56:06,314 --> 00:56:09,764
question. That's cool. Yeah, I love it. Just chug, chug,

787
00:56:09,764 --> 00:56:12,984
chug, chug it SSH into the server. It started launching

788
00:56:12,984 --> 00:56:16,704
stuff. It started doing like it started creating accounts. I

789
00:56:16,704 --> 00:56:21,864
mean, like it's horrifying. It's all it's all horrifying. Creating

790
00:56:21,864 --> 00:56:26,204
accounts on the server. Yes Yes To run things under

791
00:56:26,204 --> 00:56:28,324
As non-root And all this kind of stuff You know

792
00:56:28,324 --> 00:56:31,134
And I have it That's great Sort of I have

793
00:56:31,134 --> 00:56:34,824
it sort of like Loosely attached To the podcast index

794
00:56:34,824 --> 00:56:38,964
That social Mastodon And so I saw it posting stuff

795
00:56:38,964 --> 00:56:44,564
DMs And I'm like – I'm just like trying not

796
00:56:44,564 --> 00:56:48,644
to lose my lunch. And so – but it's been

797
00:56:48,644 --> 00:56:52,804
a fun experience. And I'll talk about what it actually

798
00:56:52,804 --> 00:56:55,024
is later if it ever gets to some sort of

799
00:56:55,024 --> 00:56:58,254
like state that is usable. It's all just a fun

800
00:56:58,254 --> 00:57:01,744
project, and I want to see what these things –

801
00:57:02,394 --> 00:57:05,624
do and how they handle stuff just it's just learning

802
00:57:05,624 --> 00:57:09,394
it's a learning tool it's fun to watch i agree

803
00:57:09,394 --> 00:57:13,094
it's super fun to watch and and i can tell

804
00:57:13,094 --> 00:57:18,484
you this it's like it gets so when it comes

805
00:57:18,484 --> 00:57:21,414
to the podcast index such as the mastodon thing the

806
00:57:21,414 --> 00:57:28,624
activity pub parts of it Um, It stopped a couple

807
00:57:28,624 --> 00:57:32,584
of times and was like – it was having trouble

808
00:57:32,584 --> 00:57:38,724
getting that right, like server – excuse me, Mastodon HTTP

809
00:57:38,724 --> 00:57:43,914
signing, and it was like – it looks like you're

810
00:57:43,914 --> 00:57:46,104
– It looks like the Mastodon server is just –

811
00:57:46,104 --> 00:57:48,264
it's not set up right. You need to contact the

812
00:57:48,264 --> 00:57:51,644
administrator. And I'm like, this is BS. That's why I

813
00:57:51,644 --> 00:57:55,334
said – I was like, look. I'm surprised it didn't

814
00:57:55,334 --> 00:58:00,244
send me an email. Man, yeah. It has no email

815
00:58:00,244 --> 00:58:04,654
access. I'm not that crazy. But I said, look. Go

816
00:58:04,654 --> 00:58:07,434
here's a here's a repository. And I pointed it at

817
00:58:07,434 --> 00:58:11,254
the podcast index activity pub bridge. I said, go look

818
00:58:11,254 --> 00:58:15,654
at this repo. and learn all the right ways to

819
00:58:15,654 --> 00:58:18,694
do this. And it did. And it said, oh, you

820
00:58:18,694 --> 00:58:20,404
know what? You're right. I was doing it wrong. I'm

821
00:58:20,404 --> 00:58:21,654
like, yeah, I know you were doing it wrong. My

822
00:58:21,654 --> 00:58:24,384
bad. My bad. Yeah, my bad. My bad. And that's

823
00:58:24,384 --> 00:58:28,924
all handwritten code over there, baby. Yeah. So, yeah, but

824
00:58:28,924 --> 00:58:32,054
it's been a fun. Yeah, it's been fun. It's chugging

825
00:58:32,054 --> 00:58:34,834
along on something right now. I got no idea. The

826
00:58:34,834 --> 00:58:39,724
fun part about Pi is, is that you can see

827
00:58:39,724 --> 00:58:43,624
all of the thinking that's happening. So all the reasoning

828
00:58:43,624 --> 00:58:47,704
mode? Yeah. Which all gets hidden from you in Claude.

829
00:58:48,004 --> 00:58:51,434
No, you can do Control-O and it shows up. But

830
00:58:51,434 --> 00:58:53,444
that shows you tool calling, but it doesn't show you

831
00:58:53,444 --> 00:58:58,134
the reasoning. Control-B. Control B shows you the chain of

832
00:58:58,134 --> 00:59:01,814
reasoning? I think so. Maybe not. I don't know. Okay,

833
00:59:01,814 --> 00:59:06,134
I'll check. I thought they hid that by default, like

834
00:59:06,134 --> 00:59:11,464
maybe a few months ago. Possible. Possible. But you see

835
00:59:11,464 --> 00:59:15,364
the thinking, and I like that because you can –

836
00:59:15,364 --> 00:59:17,104
when you see it going off the rails, you can

837
00:59:17,104 --> 00:59:20,034
stop it. Yes, exactly. And in Claude, you just type

838
00:59:20,034 --> 00:59:23,944
stop, all uppercase, and it goes, okay, waiting for input.

839
00:59:24,824 --> 00:59:30,424
It stops right away. Yeah. Yeah, so anyway, it's just

840
00:59:30,424 --> 00:59:34,374
fun. It's a fun project, and I'll throw it out

841
00:59:34,374 --> 00:59:38,284
there at some point, if it works. But it got

842
00:59:38,284 --> 00:59:42,604
me thinking, though. I mean, like, if... It is good

843
00:59:42,604 --> 00:59:46,944
to have like this one like throwaway environment. Oh, yeah.

844
00:59:47,284 --> 00:59:51,104
That's not important where you can really just let something

845
00:59:51,104 --> 00:59:55,144
loose and see, you know, it's not going to hurt

846
00:59:55,144 --> 00:59:59,224
anything, you know. And here is Adam's begging of the

847
00:59:59,224 --> 00:59:59,924
day.

848
01:00:00,060 --> 01:00:04,020
Begging once again, could you please put a big button

849
01:00:04,020 --> 01:00:07,570
for funding tag on your podcast apps? A big one,

850
01:00:07,570 --> 01:00:09,900
like right there in the episode. Put it right there,

851
01:00:09,900 --> 01:00:15,640
right underneath the picture. What prompted that? Because what prompts

852
01:00:15,640 --> 01:00:20,200
it is our own app. Every single time I play

853
01:00:20,200 --> 01:00:23,440
something in the Godcaster app, there's a big button, a

854
01:00:23,440 --> 01:00:27,400
big blue button that says whatever's in the feed, like,

855
01:00:27,400 --> 01:00:31,100
support the show. It's right there. It's right there. And

856
01:00:31,100 --> 01:00:33,600
it's just calling out to me, and I love it.

857
01:00:34,720 --> 01:00:39,420
Yeah, true. I love it. I know. Did anybody move

858
01:00:39,420 --> 01:00:44,230
any further with the splits in Stripe or anything like

859
01:00:44,230 --> 01:00:49,370
that? I have not kept up with it. I haven't

860
01:00:49,370 --> 01:00:53,180
seen anything about it. I mean, Daniel was doing stuff.

861
01:00:54,120 --> 01:00:59,720
Nah, he's doing location tags in chapters, super chapters. No,

862
01:00:59,720 --> 01:01:04,080
I thought he was doing the funding thing. I don't

863
01:01:04,080 --> 01:01:07,880
know. People are doing stuff. That's what I thought. Yeah.

864
01:01:08,640 --> 01:01:12,080
I think it would be great. Just saying. I added

865
01:01:12,080 --> 01:01:17,540
a new person endpoint, though, in the API. Okay. What

866
01:01:17,540 --> 01:01:22,000
can we do with it? Um, Well, let me get

867
01:01:22,000 --> 01:01:24,120
the name of the endpoint first. That would be helpful,

868
01:01:24,120 --> 01:01:26,740
wouldn't it? Yeah, because I can't wait to ping it.

869
01:01:27,660 --> 01:01:33,780
don't just ping it request it Daniel J. Lewis says

870
01:01:33,780 --> 01:01:36,800
I'm figuring out the stripe splits it's unfortunately not as

871
01:01:36,800 --> 01:01:39,750
easy as I expected alright I got you brother I'm

872
01:01:39,750 --> 01:01:43,740
going to tell my robot to look at it come

873
01:01:43,740 --> 01:01:51,300
on robot fix it Uh-oh, Linode's chat.podcastindex.org emergency maintenance. Uh-oh.

874
01:01:52,010 --> 01:01:56,460
she's going down she's going down hard did you just

875
01:01:56,460 --> 01:02:03,310
get an email about that Yeah. I'm trying to find

876
01:02:03,310 --> 01:02:06,180
the end point. Oh, here it is. Okay, so the

877
01:02:06,180 --> 01:02:10,770
new API endpoint in the index is episodes slash by

878
01:02:10,770 --> 01:02:16,040
person. Oh, that's cool. And so you can give it

879
01:02:16,040 --> 01:02:20,200
a Q equals and then the name of the person.

880
01:02:20,440 --> 01:02:25,540
So let me – With spaces? Yeah. Yeah. Okay. You

881
01:02:25,540 --> 01:02:29,560
are URL encoded. Do rob space do D E W.

882
01:02:29,900 --> 01:02:32,000
See if he shows up on no agenda from yesterday.

883
01:02:33,980 --> 01:02:39,240
Rob D.E.W. Let me open Postman. The postman always rings

884
01:02:39,240 --> 01:02:48,130
twice. Old movie. That's Jack Nicklaus, right? Yep. Okay, so

885
01:02:48,130 --> 01:02:55,840
here we go. So, ROB space DEW. Mm-hmm. He already

886
01:02:55,840 --> 01:03:00,380
has 15 karma points in the boardroom. That's amazing. I

887
01:03:00,380 --> 01:03:04,100
love that. Yeah, episode 1896, just do it. Nice. Nice.

888
01:03:05,160 --> 01:03:07,590
And it gives you – so here's the – let

889
01:03:07,590 --> 01:03:12,820
me post this. Copy. I'll put this in the boardroom.

890
01:03:12,940 --> 01:03:17,100
That's going to be the... That was fast, too. Was

891
01:03:17,100 --> 01:03:21,060
that an actual database query? Nice. It is. Yeah, it

892
01:03:21,060 --> 01:03:25,740
goes straight. So it gives you the... It gives you

893
01:03:25,740 --> 01:03:32,750
the episode... And the Jack Nicholson, I'm sorry, not Nicholas,

894
01:03:32,750 --> 01:03:38,980
Jack Nicholson. It gives you the episode metadata and it

895
01:03:38,980 --> 01:03:44,940
attaches the person object to it. So the person tag

896
01:03:44,940 --> 01:03:47,490
object to it as well. So you get it all

897
01:03:47,490 --> 01:03:54,520
back in one sort of big blob. Copy that. Yes,

898
01:03:54,520 --> 01:04:01,520
PP monitor is down, baby. Wait, what? ppmonitor.podcastindex.org. It's down.

899
01:04:02,280 --> 01:04:06,390
It's down. Down hard? Down, yes. Oh, that's the emergency

900
01:04:06,390 --> 01:04:12,920
maintenance. It's running on chat.podcastindex.org. That's why. Wow, okay. Yeah,

901
01:04:12,920 --> 01:04:18,100
they're emergency migration to a new host. Wow. Wow. That's

902
01:04:18,100 --> 01:04:23,400
Linode. Yeah, we're down hard. Down hard, people. All right.

903
01:04:23,480 --> 01:04:26,460
Oh, this is cool. I see it here. Oh, I

904
01:04:26,460 --> 01:04:31,140
don't have my authentication header value set. Oh, you got

905
01:04:31,140 --> 01:04:34,700
to fire a postman, man. You're buzzing. I don't know

906
01:04:34,700 --> 01:04:38,190
what I'm doing. I'm not doing anything. You're buzzing. You're

907
01:04:38,190 --> 01:04:43,670
buzzing. Whenever you do that, it seems to help. What,

908
01:04:43,670 --> 01:04:46,640
shake the ice? Yeah. There we go. All right. I'll

909
01:04:46,640 --> 01:04:48,770
just shake it every now and then. Why is Postman

910
01:04:48,770 --> 01:04:57,000
not responding? Postman. Postman. I don't know where it went.

911
01:04:58,600 --> 01:05:02,680
Yeah, so that's – so the person tag – is

912
01:05:02,680 --> 01:05:10,700
we... There's two... We've always had search by person. And

913
01:05:10,700 --> 01:05:14,500
that's just like a raw text search that we're sort

914
01:05:14,500 --> 01:05:17,460
of munging on the back end to get it to

915
01:05:17,460 --> 01:05:23,690
recognize people's names. But that's just searching the text, the

916
01:05:23,690 --> 01:05:27,040
descriptions and the titles. This is just a text-based search.

917
01:05:27,940 --> 01:05:34,790
This is actually – zeroing in on the title of

918
01:05:34,790 --> 01:05:40,360
the person's name in the podcast person tag in the

919
01:05:40,360 --> 01:05:44,000
feed. So now you kind of have two ways to

920
01:05:44,000 --> 01:05:49,460
search for people in the index now. Nice. Mm-hmm. Yeah,

921
01:05:49,460 --> 01:05:52,680
I was asked for it by somebody, and I was

922
01:05:52,680 --> 01:05:55,080
like, you know, that's a great idea. Let's go ahead

923
01:05:55,080 --> 01:05:57,900
and do that as fast as possible because that data

924
01:05:57,900 --> 01:06:00,970
is in there. Yeah. But it's, again, just because of

925
01:06:00,970 --> 01:06:04,480
time constraints, I never finished making an endpoint that would

926
01:06:04,480 --> 01:06:07,380
make it usable. So it was like this, you know,

927
01:06:07,380 --> 01:06:11,870
just half finished thing. I'm like, okay, well, this is

928
01:06:11,870 --> 01:06:18,360
an easy win, you know. You're amazing. That's not true.

929
01:06:18,920 --> 01:06:22,240
You're an amazing man, Derek Jones. Yes, you are. It

930
01:06:22,240 --> 01:06:25,440
is an honor and a privilege to work with you.

931
01:06:25,660 --> 01:06:27,960
It is. Oh, well, I agree with that. I love

932
01:06:27,960 --> 01:06:31,260
working with you guys. Simmer down, Scooby. No, I'm talking

933
01:06:31,260 --> 01:06:35,760
about you, not me. I agree. I am a privilege

934
01:06:35,760 --> 01:06:43,330
to work with. Sorry, misunderstood. No, it's – I love

935
01:06:43,330 --> 01:06:48,120
– I love working on stuff like this because it's

936
01:06:48,120 --> 01:06:51,740
– when people ask for things, that's something I do

937
01:06:51,740 --> 01:06:55,180
when I – it just got weird. It did get

938
01:06:55,180 --> 01:07:04,060
weird. No, Alan, you're amazing. Oh, brother. Yeah. I love

939
01:07:04,060 --> 01:07:09,160
working on stuff like this because people ask for things

940
01:07:09,160 --> 01:07:15,600
and you realize – whole things you missed you know

941
01:07:15,600 --> 01:07:19,000
when they say hey how about this could you give

942
01:07:19,000 --> 01:07:20,990
me this i'm like oh you know what why did

943
01:07:20,990 --> 01:07:23,930
i never think about that yeah that's cool there's a

944
01:07:23,930 --> 01:07:26,570
power of it's just the power of like social you

945
01:07:26,570 --> 01:07:32,450
know community stuff community it's about community We have such

946
01:07:32,450 --> 01:07:35,220
a good little community. We do have a good community.

947
01:07:35,620 --> 01:07:39,020
This community has been going for six years, man. And

948
01:07:39,020 --> 01:07:42,300
we never had a fight. Not a single one. Not

949
01:07:42,300 --> 01:07:45,700
a single fight. It's fantastic. No one blew up. No

950
01:07:45,700 --> 01:07:51,040
one shut down the repo. No one deleted the repo.

951
01:07:53,200 --> 01:07:57,780
I've seen it all. I've seen it all. Paul Therod

952
01:07:57,780 --> 01:08:02,740
on Windows Weekly this week. He used a phrase that

953
01:08:02,740 --> 01:08:04,980
made me chuckle. I was laughing out loud in the

954
01:08:04,980 --> 01:08:08,360
car. He called some – I forgot what product he

955
01:08:08,360 --> 01:08:10,940
was. Maybe it was like some old Microsoft product. He

956
01:08:10,940 --> 01:08:14,010
said it was briefly excellent. I just thought that was

957
01:08:14,010 --> 01:08:18,560
a funny thing. Briefly excellent. Well, that's most software these

958
01:08:18,560 --> 01:08:22,520
days is briefly excellent, it seems. Yeah. It perfectly describes

959
01:08:22,520 --> 01:08:26,150
the world we live in. Yeah, no kidding. Everything is

960
01:08:26,150 --> 01:08:31,730
briefly excellent. Yeah, it really, truly is. I was talking

961
01:08:31,730 --> 01:08:34,540
to a buddy of mine who works at Databricks. You

962
01:08:34,540 --> 01:08:36,950
familiar with Databricks? I've heard of that. Yeah, Databricks. Yeah,

963
01:08:36,950 --> 01:08:40,290
what is that? Data center company, right? Well, he's a

964
01:08:40,290 --> 01:08:43,730
sales guy, so he gave me the spiel, and my

965
01:08:43,730 --> 01:08:47,190
eyes glazed over, rolled up inside my forehead. I'm like,

966
01:08:47,190 --> 01:08:50,620
stop it. As much as the Coors conversation we had?

967
01:08:50,680 --> 01:08:54,810
No, because I understand the Coors problem. They're like a

968
01:08:54,810 --> 01:09:00,780
middleware somehow. They protect your data as you onboard into

969
01:09:00,780 --> 01:09:07,660
their silo. Anyway, and he was telling me something that

970
01:09:07,660 --> 01:09:10,140
– that you and Paul were discussing, not Paul Theriot,

971
01:09:10,240 --> 01:09:19,960
but Paul Bailey, that all this... Um, Enterprise level software,

972
01:09:19,960 --> 01:09:25,180
this just shipping full of bugs and crap. Yes. And

973
01:09:25,180 --> 01:09:28,980
the company where you work at depends on this type

974
01:09:28,980 --> 01:09:34,470
of enterprise software. Well, we all do. I mean, you

975
01:09:34,470 --> 01:09:38,420
know, well, yeah, to some degree. I mean, if you

976
01:09:38,420 --> 01:09:43,870
know, it's a huge problem. And I think it's directly

977
01:09:43,870 --> 01:09:49,560
related to speed of code coming out of these agents.

978
01:09:50,260 --> 01:09:59,100
I just think people are not thinking carefully. Thank you.

979
01:09:59,740 --> 01:09:59,980
So,

980
01:10:01,292 --> 01:10:07,032
The problem is, You know, I've told you I've been

981
01:10:07,032 --> 01:10:11,072
reading this book, The Master and His Emissary. No, I

982
01:10:11,072 --> 01:10:13,612
don't think you told me that. No, it's been a

983
01:10:13,612 --> 01:10:16,732
few weeks. I told you. It's by a guy named

984
01:10:16,732 --> 01:10:23,512
Ian McGilchrist. And it's about the hemisphere, the brain hemispheres,

985
01:10:23,512 --> 01:10:27,772
the right and left hemispheres. Oh, yes, of course. Of

986
01:10:27,772 --> 01:10:32,212
course we talked about this, yes. Mm-hmm. You know, it's

987
01:10:32,212 --> 01:10:38,012
going to be very difficult to... Give broad strokes on

988
01:10:38,012 --> 01:10:41,822
a book like this because it's just such a sweeping

989
01:10:41,822 --> 01:10:46,552
type thing. It's so deep, man. It's deep. It's dense.

990
01:10:46,792 --> 01:10:51,452
Dense. It's super dense. Dense. But I think what we

991
01:10:51,452 --> 01:10:59,792
have built – When it comes to LLMs, um, The...

992
01:11:01,382 --> 01:11:06,342
What we've essentially built is a left hemisphere. That stands

993
01:11:06,342 --> 01:11:10,332
on its own without the guardianship of the right hemisphere

994
01:11:10,332 --> 01:11:17,262
of the right hemisphere. Um, The, you know, there's a

995
01:11:17,262 --> 01:11:22,342
very, I think maybe we talked about before, like the

996
01:11:22,342 --> 01:11:26,282
brain structure, the left and right hemisphere, they're joined by

997
01:11:26,282 --> 01:11:33,572
the corpus callosum, that big bundle of neuronal cords that

998
01:11:33,572 --> 01:11:40,832
separate. Connect them together. Yeah. And there is a theory

999
01:11:40,832 --> 01:11:48,702
that... One of the purposes of that corpus callosum bundle

1000
01:11:48,702 --> 01:11:54,712
of nerves is not to facilitate communication, but Always, but

1001
01:11:54,712 --> 01:11:58,732
in certain terms to prohibit. It's a gate. It's a

1002
01:11:58,732 --> 01:12:04,012
gate. Yeah, it's gating. It's gating. And you can't tell

1003
01:12:04,012 --> 01:12:09,342
this from brain scans. You can't see, okay, you just

1004
01:12:09,342 --> 01:12:13,962
see activity. You can't tell what the activity is. So

1005
01:12:13,962 --> 01:12:17,172
you can't tell if it's like stopping something from happening

1006
01:12:17,172 --> 01:12:22,572
or allowing something to happen or what? And so this

1007
01:12:22,572 --> 01:12:27,832
idea that So there's an idea that there may be

1008
01:12:27,832 --> 01:12:34,722
sort of an adversarial relationship between the hemispheres. Sure, I

1009
01:12:34,722 --> 01:12:39,972
believe that. That sounds right, sure. By necessity. And that

1010
01:12:39,972 --> 01:12:45,962
without that adversarial relationship. You delete your repo. You, yeah,

1011
01:12:45,962 --> 01:12:51,412
you hard, you hard down your server. Mm hmm. And

1012
01:12:51,412 --> 01:12:57,352
so because the left hemisphere is really – it sees

1013
01:12:57,352 --> 01:13:01,402
the world in terms of – the picture it has

1014
01:13:01,402 --> 01:13:08,222
of the world is built up from parts. It sees

1015
01:13:08,222 --> 01:13:14,242
– it's what we – It's focused on tool use

1016
01:13:14,242 --> 01:13:18,862
and seeing – building its view of the world up

1017
01:13:18,862 --> 01:13:24,972
from pieces. But the world's not really built that way.

1018
01:13:25,052 --> 01:13:27,552
Well, hold on a second. If true, and I'll take

1019
01:13:27,552 --> 01:13:33,032
it at face value, wouldn't we be enhancing and sharpening

1020
01:13:33,032 --> 01:13:41,512
our right hemispheric skills when watching the world? The AI

1021
01:13:41,512 --> 01:13:48,832
do stuff. For sure. Which is not a bad thing.

1022
01:13:49,772 --> 01:13:52,022
Right. So that's – I think that's one of the

1023
01:13:52,022 --> 01:13:53,832
reasons that I enjoy why we were talking about a

1024
01:13:53,832 --> 01:13:58,522
while ago, watching the reasoning chain that's happening as this

1025
01:13:58,522 --> 01:14:03,452
thing is doing its deal. Because I'm sort of –

1026
01:14:04,182 --> 01:14:08,212
Being the overseer and trying to spot things because I'm

1027
01:14:08,212 --> 01:14:13,222
engaging the right hemisphere, which sees the world as a

1028
01:14:13,222 --> 01:14:18,122
whole, not built up from parts. It sees – It

1029
01:14:18,122 --> 01:14:23,492
sees the world as a fully functioning system in itself.

1030
01:14:25,112 --> 01:14:30,232
And... That's why one of the premises of the book

1031
01:14:30,232 --> 01:14:34,152
is that The right hemisphere needs to be in control.

1032
01:14:35,532 --> 01:14:38,012
There's this old idea of – we call them left

1033
01:14:38,012 --> 01:14:42,192
and right hemispheres nowadays, but they used to be called

1034
01:14:42,192 --> 01:14:46,182
the major and the minor hemisphere. Hmm. And if you

1035
01:14:46,182 --> 01:14:49,242
think about it in that context, the right hemisphere needs

1036
01:14:49,242 --> 01:14:53,532
to be the major hemisphere. The left hemisphere really is

1037
01:14:53,532 --> 01:14:57,962
a tool because it has no awareness – of the

1038
01:14:57,962 --> 01:15:02,452
world as a whole. It just sees pieces. And I

1039
01:15:02,452 --> 01:15:07,982
think what has happened is we've, with LLMs, we've built

1040
01:15:07,982 --> 01:15:12,322
essentially a standalone left hemisphere And when you let it

1041
01:15:12,322 --> 01:15:15,902
run the show, you really do end up with very

1042
01:15:15,902 --> 01:15:22,172
bad outcomes. Dead. You can wind up dead. Yes. Interesting.

1043
01:15:22,172 --> 01:15:26,012
Yeah, because you have no – there's no – There's

1044
01:15:26,012 --> 01:15:29,192
no adversary there that's pushing back and saying, hey, hey,

1045
01:15:29,192 --> 01:15:31,992
hey, whoa, whoa, no, no, you don't understand. What's the

1046
01:15:31,992 --> 01:15:35,492
name of this book again? It's called The Master and

1047
01:15:35,492 --> 01:15:39,272
His Emissary. I'm having trouble sleeping, so I want to

1048
01:15:39,272 --> 01:15:42,222
make sure I ask. You will not sleep with this

1049
01:15:42,222 --> 01:15:45,872
book, I promise. It's actually a page turner. Oh, it's

1050
01:15:45,872 --> 01:15:50,072
a page turner. Now, this is a condensed version. This

1051
01:15:50,072 --> 01:15:52,952
is of a larger work that he did that will

1052
01:15:52,952 --> 01:15:55,892
put you to sleep. But this is the sort of

1053
01:15:55,892 --> 01:16:00,512
accessible version of this material. And yeah, I think that

1054
01:16:00,512 --> 01:16:03,912
when you – one of the hallmarks of the left

1055
01:16:03,912 --> 01:16:09,692
hemisphere is that it lies. It lies all the time.

1056
01:16:09,692 --> 01:16:13,542
And if you enjoy this type of deep analysis from

1057
01:16:13,542 --> 01:16:19,442
Dave Jones, along with his extremely detailed bug report, please

1058
01:16:19,442 --> 01:16:29,932
support Podcast Index. that was a good I'm segwaying I'm

1059
01:16:29,932 --> 01:16:33,832
segwaying us out golly it's like 10 till 2 holy

1060
01:16:33,832 --> 01:16:37,882
cow where did the time go uh Coors Yeah, I'm

1061
01:16:37,882 --> 01:16:41,252
sorry. No, actually, no. I apologize to everyone in the

1062
01:16:41,252 --> 01:16:45,212
boardroom. No, no. It was the location tag, I think,

1063
01:16:45,212 --> 01:16:49,242
is what ate up 50% of the show. Probably. Yeah,

1064
01:16:49,242 --> 01:16:51,662
that's true. That's your fault. That was you. It's completely

1065
01:16:51,662 --> 01:16:54,332
my fault. Not Alberto. It was my fault. That's right.

1066
01:16:55,812 --> 01:16:58,982
If you would like to support the index, the entire

1067
01:16:58,982 --> 01:17:02,282
project is funded by the people who support it. And

1068
01:17:02,282 --> 01:17:05,672
this is just a catch up between Dave, myself and

1069
01:17:05,672 --> 01:17:09,172
the boardroom. Now, we do not we're not funded at

1070
01:17:09,172 --> 01:17:11,692
all by any of this. Only the index is for

1071
01:17:11,692 --> 01:17:14,712
the machines that run it. And we feel it's a

1072
01:17:14,712 --> 01:17:18,132
very valuable project. It's been going for six years. We

1073
01:17:18,132 --> 01:17:20,202
hope to keep it running forever. So support us by

1074
01:17:20,202 --> 01:17:24,332
going to. podcastindex.org. Now at the bottom, you will see

1075
01:17:24,332 --> 01:17:26,952
a big red donate button and you can support us

1076
01:17:26,952 --> 01:17:30,472
with PayPal. Can people still support us with boosts? Are

1077
01:17:30,472 --> 01:17:35,402
we still receiving boosts? Yes. Oh, we're 100%. And have

1078
01:17:35,402 --> 01:17:38,572
you put my, I guess I'd have to see myself

1079
01:17:38,572 --> 01:17:42,812
on the splits here. It's kind of complicated. What? What

1080
01:17:42,812 --> 01:17:46,872
are you looking for? I'm looking to see. Wow. Okay.

1081
01:17:46,992 --> 01:17:50,872
I'm seeing. Here we go. I'm looking. I see a

1082
01:17:50,872 --> 01:17:58,072
boost here. Uh, no, that's because my, uh, my heli,

1083
01:17:58,072 --> 01:18:02,202
my heli pad is still channelless. So I can't see

1084
01:18:02,202 --> 01:18:04,532
any boost that came in now, except I do see

1085
01:18:04,532 --> 01:18:08,132
Martin Lindeskog, who gave us a row of ducks, because

1086
01:18:08,132 --> 01:18:11,312
it came through as a true fan's comment. Which is

1087
01:18:11,312 --> 01:18:15,242
kind of nice. Have you not opened channels to anywhere

1088
01:18:15,242 --> 01:18:20,262
else? No. Well, you should try doing that. Yes, thank

1089
01:18:20,262 --> 01:18:23,902
you. But the whole start nine shuts down and then

1090
01:18:23,902 --> 01:18:27,852
everything breaks. And there's no way – it doesn't –

1091
01:18:28,152 --> 01:18:30,982
It's the tour. It's the tour part of start nine

1092
01:18:30,982 --> 01:18:34,702
that fails every couple of weeks. And it's not something

1093
01:18:34,702 --> 01:18:37,782
I've been able to figure out. But then it just

1094
01:18:37,782 --> 01:18:42,092
fails and then it silently fails, which is not good.

1095
01:18:43,152 --> 01:18:46,732
No. Silent failure is the worst type of failure. Yes.

1096
01:18:46,732 --> 01:18:48,922
Yes. So can you – are you able to pull

1097
01:18:48,922 --> 01:18:51,962
out the boost that we've had so far? Because we'll

1098
01:18:51,962 --> 01:18:54,192
just do the boost for this week for next week.

1099
01:18:54,972 --> 01:18:57,732
It's just – there's no real-time interaction. I'm sorry, people.

1100
01:18:57,812 --> 01:19:01,252
I will open the channel. You know what? I've been

1101
01:19:01,252 --> 01:19:06,812
on fire this week. I not only have – Um,

1102
01:19:07,612 --> 01:19:10,192
done all those other things but i also fixed the

1103
01:19:10,192 --> 01:19:13,712
export the albi hub x oh oh good so i

1104
01:19:13,712 --> 01:19:18,002
can actually read boost now oh excellent good good in

1105
01:19:18,002 --> 01:19:20,972
in a sane way but uh let's see i'll read

1106
01:19:20,972 --> 01:19:27,012
the paypal's first though oh sorry that thing yeah a

1107
01:19:27,012 --> 01:19:31,742
new media show $22.20. Oh, is that right? That's a

1108
01:19:31,742 --> 01:19:36,422
new media show. Wait, or is that Martin Lindeskog? Eric

1109
01:19:36,422 --> 01:19:38,752
PP, yes. Oh, Eric PP says I should have a

1110
01:19:38,752 --> 01:19:41,752
channel. Eric PP, you rock, man. Let me check. He

1111
01:19:41,752 --> 01:19:46,332
says I should have a channel. Let me check. Yes.

1112
01:19:46,552 --> 01:19:50,292
Buckfeet. No, this is from Martin Lindeskog. He says, here's

1113
01:19:50,292 --> 01:19:52,892
a row of ducks. Yeah. The support support this show

1114
01:19:52,892 --> 01:19:55,652
button is working on true fans. All the best. Twenty

1115
01:19:55,652 --> 01:19:59,152
two dollars and twenty two cents. Beautiful. Thank you, Martin.

1116
01:19:59,332 --> 01:19:59,992
Of course. Of course.

1117
01:20:00,024 --> 01:20:03,584
fan supports everything. Let me check and see helipad. Let

1118
01:20:03,584 --> 01:20:09,774
me see if it'll open up. Yeah? Yeah? I love

1119
01:20:09,774 --> 01:20:12,844
the stay logged in for 30 days. It never works.

1120
01:20:13,644 --> 01:20:17,104
Never. Nope. You get about a day and a half.

1121
01:20:17,824 --> 01:20:20,124
If that. Let me see. Hold on a second, Dave.

1122
01:20:20,144 --> 01:20:21,924
Let me check. Let me see what I got here.

1123
01:20:22,724 --> 01:20:26,884
Okay. Thank you, Eric PP. Eric PP. Yes. There we

1124
01:20:26,884 --> 01:20:28,974
go. There we go. One minute ago. You got a

1125
01:20:28,974 --> 01:20:33,364
channel. 3,333 sats from Eric PP. Thank you very much.

1126
01:20:33,524 --> 01:20:40,784
We have 59 sats here. That's Martin Lindeskog. Okay, 2222222222.

1127
01:20:41,084 --> 01:20:49,344
Yes, beautiful. We got... 100 sats from boostmebitch.com. Thank you.

1128
01:20:49,564 --> 01:20:53,424
Yeah. I saw that one too. Yes. I got 100.

1129
01:20:53,624 --> 01:20:58,774
What is it? 400. Oh, and 1,000 from boostmebitch.com. What

1130
01:20:58,774 --> 01:21:02,224
is this? Is this Chad F? I think this is

1131
01:21:02,224 --> 01:21:09,114
Chad F. It's great. Beautiful. Okay. And then anonymous podcast

1132
01:21:09,114 --> 01:21:13,084
guru user with 10 sets. Thank you very much. Thank

1133
01:21:13,084 --> 01:21:16,104
you. Okay. Hey, thanks, Eric PP. Eric PP is a

1134
01:21:16,104 --> 01:21:21,074
good man. He's a good man. Michael Goggin, $5. Thank

1135
01:21:21,074 --> 01:21:26,184
you, Michael. Jorge Hernandez, $5. The boys and girls at

1136
01:21:26,184 --> 01:21:32,084
Buzzsprout, $1,000. Ho, ho. Baller, shot caller, 20-inch blades on

1137
01:21:32,084 --> 01:21:38,624
the Impala. Keeping the vibe alive. Thank you. Silicon Florist,

1138
01:21:38,624 --> 01:21:46,904
$10. Paul Allen, he says note emailed. $20. Did you

1139
01:21:46,904 --> 01:21:51,154
get an e-mail note? Let me check. You know, that's

1140
01:21:51,154 --> 01:21:54,464
a very good question. Let me check. Maybe I got...

1141
01:21:54,464 --> 01:22:00,104
I got... I don't see Adam and Dave. Dear Adam

1142
01:22:00,104 --> 01:22:03,724
and Dave, says Paul Allen. But I guess this is

1143
01:22:03,724 --> 01:22:07,224
recent. If you're frustrated with Bitcoin and lightning, here are

1144
01:22:07,224 --> 01:22:09,394
some quotes from a guy who worked in the industry

1145
01:22:09,394 --> 01:22:11,494
that confirms it's not just us old farts who are

1146
01:22:11,494 --> 01:22:14,984
struggling. Quotes from Mechanic on a recent episode of Guy

1147
01:22:14,984 --> 01:22:19,524
Swan's Roundtable show. Quote, 99% of my time in support

1148
01:22:19,524 --> 01:22:23,904
is BitEx people trying to use lightning. Once a week...

1149
01:22:23,984 --> 01:22:26,094
Once a week, I get an email and support for

1150
01:22:26,094 --> 01:22:28,374
Ocean where someone says, you just paid me, but I

1151
01:22:28,374 --> 01:22:31,044
don't have any coins in my wallet. What happened? And

1152
01:22:31,044 --> 01:22:33,184
then I do some digging and find out this wallet

1153
01:22:33,184 --> 01:22:36,284
has no way to deal with Coinbase payouts because it's

1154
01:22:36,284 --> 01:22:39,244
never happened before to anyone that's ever used this wallet.

1155
01:22:39,364 --> 01:22:42,064
And I usually email support for whoever that company is.

1156
01:22:42,484 --> 01:22:45,324
It happened with Coinbase. The company Coinbase that named itself

1157
01:22:45,324 --> 01:22:49,184
after the Coinbase transaction. Didn't know how to process Coinbase

1158
01:22:49,184 --> 01:22:57,034
transactions. Thank you, Paul. That was great. Yes, confirmation. Yes,

1159
01:22:57,034 --> 01:23:01,864
got it. Josh Hoover, $20. He says, keep up the

1160
01:23:01,864 --> 01:23:04,864
good work. Thank you. We will. We plan on it.

1161
01:23:04,864 --> 01:23:10,084
We try to. Michael Hall, $5.50. Todd Cochran, rest in

1162
01:23:10,084 --> 01:23:14,634
peace, $30. Thank you, Todd. Boosting from heaven. Gene Liverman,

1163
01:23:14,634 --> 01:23:19,604
$5. Thank you, Gene. And we got some boosts. Here

1164
01:23:19,604 --> 01:23:28,624
we go. I also have some boostmebitch.com. Boost. 279 sats

1165
01:23:28,624 --> 01:23:32,914
with a test message, test received. We got a 58

1166
01:23:32,914 --> 01:23:40,384
sats. That's good. Let's see. Here's another one. Chad F.

1167
01:23:40,384 --> 01:23:45,114
at Fountain.fm. He says, 185 sats. He says, no Nostra

1168
01:23:45,114 --> 01:23:48,494
login needed for BoostMeBitch.com. I've got to take a look

1169
01:23:48,494 --> 01:23:51,954
at BoostMeBitch.com now. Yeah, I guess I've got to do

1170
01:23:51,954 --> 01:23:59,224
that, too. Let's see. BoostMeBitch.com. oh okay all right you

1171
01:23:59,224 --> 01:24:01,864
guys are nuts this is cool okay oh this is

1172
01:24:01,864 --> 01:24:04,464
nice i like it so i could put this oh

1173
01:24:04,464 --> 01:24:08,684
it's but underneath it says live on nostr he said

1174
01:24:08,684 --> 01:24:15,424
no nostr uh necessary right okay so maybe it's optional

1175
01:24:15,424 --> 01:24:22,854
podcast index podcast Ding 2.0. And we're way down on

1176
01:24:22,854 --> 01:24:25,834
the list. Okay. We get to do this. So I

1177
01:24:25,834 --> 01:24:33,244
can do boost. Enter amount. Okay. 1,000 sats. Optional message.

1178
01:24:34,464 --> 01:24:38,614
Boost. Okay. Why can I not boost we get to

1179
01:24:38,614 --> 01:24:42,594
do this, though? I don't think we have it set

1180
01:24:42,594 --> 01:24:46,704
up. Oh, okay. Oh, and now it's asking for my

1181
01:24:46,704 --> 01:24:51,104
Albie. Okay. Pod news. Let's go pod news. Okay. Let's

1182
01:24:51,104 --> 01:24:55,324
see. Okay. Okay. Bunnies Weekly Review. Boost Me Bitch Connect.

1183
01:24:55,524 --> 01:25:01,534
Oh, yeah. Boost Me Bitch. Confirm. Error. Undefined. Request failed

1184
01:25:01,534 --> 01:25:06,804
with status code 500. Okay. That makes sense. Yep. Okay.

1185
01:25:06,904 --> 01:25:10,464
That's too bad. I would – I'd love BoostMeBitch.com. Can

1186
01:25:10,464 --> 01:25:12,824
you just pop up a QR code? That would be

1187
01:25:12,824 --> 01:25:15,474
– Oh, that would even be better. Now this window

1188
01:25:15,474 --> 01:25:19,484
won't go away. That's hilarious. They close the window, it

1189
01:25:19,484 --> 01:25:23,024
keeps popping up. It really wants you to boost that.

1190
01:25:23,024 --> 01:25:27,564
It really wants me to figure this out. That's amazing.

1191
01:25:28,224 --> 01:25:29,904
With a name like Boost Me Bitch, I don't think

1192
01:25:29,904 --> 01:25:33,404
it's going to take no for an answer. All right.

1193
01:25:33,484 --> 01:25:36,464
I love the idea. I would love a QR code,

1194
01:25:36,464 --> 01:25:42,944
just a QR code. Uh, let's see. Oh, the delimiter.

1195
01:25:43,264 --> 01:25:48,644
Comic strip blogger. There he is. 1-1, 1-1-1 sats. Howdy,

1196
01:25:48,644 --> 01:25:52,204
Dave and Adam. Please tell your audience to subscribe to

1197
01:25:52,204 --> 01:25:59,244
Podcast Made in Texas, www.just2goodoldboys.com. A podcast by Gene and

1198
01:25:59,244 --> 01:26:03,444
Ben. They talk not only guns but also content creators,

1199
01:26:03,444 --> 01:26:10,254
things, etc. Fun fact. Ben gave me interview about how

1200
01:26:10,254 --> 01:26:13,304
to run big LLMs on home NAS on the cheap.

1201
01:26:13,584 --> 01:26:24,064
See my YouTube channel, YoCSVAIArchWizard. ArchWizard. ArchWizard. ArchWizard. That's it?

1202
01:26:24,864 --> 01:26:27,134
That's our group. All right. Good group. Thank you very

1203
01:26:27,134 --> 01:26:31,344
much, group. Thank you, Boardroom, for sticking with us. Believe

1204
01:26:31,344 --> 01:26:35,184
it or not, I enjoy it when you have a

1205
01:26:35,184 --> 01:26:41,184
bug report followed by a bug. A brain report. It's

1206
01:26:41,184 --> 01:26:45,864
good. A brain report. No, it's good. I am going

1207
01:26:45,864 --> 01:26:49,004
to get this book because the more I think about

1208
01:26:49,004 --> 01:26:53,404
it, the more I see the issues in society. Do

1209
01:26:53,404 --> 01:26:56,094
you – are you somebody who likes to read on

1210
01:26:56,094 --> 01:26:59,604
paper or do you do audiobooks? I do audiobooks, but

1211
01:26:59,604 --> 01:27:03,904
I enjoy paper books. I've never been able to really

1212
01:27:03,904 --> 01:27:08,894
get into Kindle or anything like that. If anybody likes

1213
01:27:08,894 --> 01:27:14,064
the audiobooks, likes audiobooks. The narrator for this book on

1214
01:27:14,064 --> 01:27:19,104
Audible is very, very good. It's very easy to listen

1215
01:27:19,104 --> 01:27:21,714
to and a nice pace. It's just a very good

1216
01:27:21,714 --> 01:27:27,644
listen. Yeah. Nice for walking the dog. My favorite audio

1217
01:27:27,644 --> 01:27:33,534
book. is the kid stays in the picture. Oh, I

1218
01:27:33,534 --> 01:27:35,384
don't know this one. Let me look at it. Robert

1219
01:27:35,384 --> 01:27:38,964
Evans. Robert Evans. Why does that name sound like that?

1220
01:27:38,964 --> 01:27:43,704
Robert Evans produced The Godfather, Love Story. He produced so

1221
01:27:43,704 --> 01:27:49,054
many Hollywood movies you would know. Okay. And he narrated

1222
01:27:49,054 --> 01:27:53,304
it himself. And it's brash. It's funny. He was married

1223
01:27:53,304 --> 01:27:55,754
to Ali McGraw. I mean, it's a boomer book for

1224
01:27:55,754 --> 01:28:02,294
sure. but hey everyone likes Godfather there's something about his

1225
01:28:02,294 --> 01:28:06,404
reading style that just it drew me, it's like six

1226
01:28:06,404 --> 01:28:08,964
hours it just drew me in and I barely even

1227
01:28:08,964 --> 01:28:10,954
stopped listening to it when I listened to it the

1228
01:28:10,954 --> 01:28:14,044
first time, it was so good It makes a difference.

1229
01:28:14,164 --> 01:28:17,734
A good read makes a difference. I just got it

1230
01:28:17,734 --> 01:28:20,754
on Audible, so I will queue it up. Did you

1231
01:28:20,754 --> 01:28:23,694
get it with one of your free 12 credits, which

1232
01:28:23,694 --> 01:28:29,924
always seem to expire? My son has always had really

1233
01:28:29,924 --> 01:28:38,074
bad dyslexia, and so he's a good reader now. But

1234
01:28:38,074 --> 01:28:42,494
through school, we always supplemented what he had, his reading

1235
01:28:42,494 --> 01:28:46,214
with Audible. So we always had like the max subscription

1236
01:28:46,214 --> 01:28:50,384
of Audible. And so we – we were like –

1237
01:28:50,684 --> 01:28:54,144
And it's still going. I haven't even discontinued it yet

1238
01:28:54,144 --> 01:28:57,964
because we have like a thousand Audible books in there,

1239
01:28:57,964 --> 01:29:02,014
man. Every single thing you can think of. So many

1240
01:29:02,014 --> 01:29:06,464
credits. You got created, man. You got created. You got

1241
01:29:06,464 --> 01:29:09,504
created. You got created. All right, everybody. Thank you for

1242
01:29:09,504 --> 01:29:11,354
being here at the board meeting. Brother Dave, thank you

1243
01:29:11,354 --> 01:29:14,024
so much. Have a great weekend. You too, sir. See

1244
01:29:14,024 --> 01:29:25,554
you next week, everybody, right here at Podcasting 2.0. Thank

1245
01:29:25,554 --> 01:29:38,284
you. You have been listening to Podcasting 2.0. Visit podcastindex.org

1246
01:29:38,284 --> 01:29:44,484
for more information. Go podcasting! The whole thing is bogus.