1
00:00:00,960 --> 00:00:06,679
Podcasting 2.0 for October 16th, 2026, episode 275, Off the

2
00:00:06,679 --> 00:00:12,140
Rails. Hello everybody, it's cold in Texas, but that doesn't

3
00:00:12,140 --> 00:00:14,900
matter because it's time for the board meeting The official

4
00:00:14,900 --> 00:00:18,530
podcasting 2.0 board meeting where we let you know what

5
00:00:18,530 --> 00:00:20,910
we're up to And we also find out what we're

6
00:00:20,910 --> 00:00:22,800
up to It's great We're kind of crazy that way.

7
00:00:23,079 --> 00:00:25,850
However, we are the only board meeting that can flip

8
00:00:25,850 --> 00:00:28,320
upside down from the halfpipe, that's for sure. I'm Adam

9
00:00:28,320 --> 00:00:30,649
Curry here in the heart of the Texas Hill Country,

10
00:00:30,649 --> 00:00:33,820
and in Alabama, the man who is mentally exhausted from

11
00:00:33,820 --> 00:00:37,179
chaperoning his robots. Say hello to my friend on the

12
00:00:37,179 --> 00:00:44,109
other end, the one, the only, Mr. Dave Jones! Why

13
00:00:44,109 --> 00:00:47,079
you laughing? Why you laughing? Why you roughing? Why you

14
00:00:47,079 --> 00:00:51,280
roughing? Why you roughing? Why you roughing? Don't roughing. Shut

15
00:00:51,280 --> 00:00:54,070
up. Don't roughing. Shut up. Don't roughing. You're going to

16
00:00:54,070 --> 00:00:56,229
have to play that clip so that at some point

17
00:00:56,229 --> 00:00:59,420
people understand what the heck we're even referencing. Roughing. Let

18
00:00:59,420 --> 00:01:05,500
me see if I have a roughing. I'm laughing because...

19
00:01:05,670 --> 00:01:10,019
the uh what what are you like why are you

20
00:01:10,019 --> 00:01:13,920
laughing man why are you laughing um the you know

21
00:01:13,920 --> 00:01:16,040
that thing that i was showing you the last week

22
00:01:16,040 --> 00:01:18,010
that was like looking up stuff for me in real

23
00:01:18,010 --> 00:01:21,750
time based on the transcripts like yeah like the it's

24
00:01:21,750 --> 00:01:25,120
my real time jamie yeah oh yeah that thing yes

25
00:01:25,120 --> 00:01:30,469
yes yes Now, for some reason it says, Dave, I

26
00:01:30,469 --> 00:01:35,200
don't even know what it's referencing. It says, Dave, that's

27
00:01:35,200 --> 00:01:39,019
just AI agent scope creep. Oh, no. You ask it

28
00:01:39,019 --> 00:01:40,980
to delete your junk mail, and next thing you know,

29
00:01:40,980 --> 00:01:44,200
it's managing your 401k and your relationship with your mother-in-law.

30
00:01:44,379 --> 00:01:46,849
Yeah. What does that even mean? Where did it get

31
00:01:46,849 --> 00:01:49,379
that from? I have no idea what that means. It's

32
00:01:49,379 --> 00:01:53,620
bad. I don't know. That doesn't sound right. Let me

33
00:01:53,620 --> 00:01:56,340
see. What am I doing? What is it trying to

34
00:01:56,340 --> 00:02:02,459
tell me? No, this is your running thing? That's what

35
00:02:02,459 --> 00:02:05,599
this is? Yes. Yes, it's supposed to be like looking

36
00:02:05,599 --> 00:02:08,870
up things that I say. If I make a reference,

37
00:02:08,870 --> 00:02:10,819
just trying to figure out if like go look us

38
00:02:10,819 --> 00:02:13,620
up something on the Internet and see, you know, because

39
00:02:13,620 --> 00:02:15,120
if I say like Trump said so and so and

40
00:02:15,120 --> 00:02:17,830
you're like, no, he didn't. It's supposed to be like,

41
00:02:17,830 --> 00:02:20,889
here, go. Here's your fact check. Yeah. Oh, you know,

42
00:02:20,889 --> 00:02:24,340
for some reason, AIFF doesn't play on the curry casser.

43
00:02:24,340 --> 00:02:30,990
Well, that is bad. Eighth. Yeah, the don't rough is

44
00:02:30,990 --> 00:02:36,460
an A.I.F.F. file. That's how old it is. Oh, weird.

45
00:02:36,919 --> 00:02:43,460
Well, let's say, what is .A.I.F.F.? Isn't that audio instructions?

46
00:02:43,780 --> 00:02:47,819
It's old. Features. It's very old. That's what that is.

47
00:02:48,000 --> 00:02:50,719
Oh, I got that. That's a little neat. A new

48
00:02:50,719 --> 00:02:56,259
version. gotta make a new version let me see where's

49
00:02:56,259 --> 00:02:59,659
podcasting 2.0 there we go let me get it let

50
00:02:59,659 --> 00:03:04,139
me get back into my folders here okay How are

51
00:03:04,139 --> 00:03:06,240
you doing, Dave? How are you doing? I'm good. By

52
00:03:06,240 --> 00:03:12,460
the way, excellent, excellent interview on Power. Oh, thank you.

53
00:03:12,979 --> 00:03:17,580
Thank you. Yeah, you gave me... tons to think about.

54
00:03:19,020 --> 00:03:24,699
It's interesting you say that because I don't typically listen

55
00:03:24,699 --> 00:03:27,750
to my own interviews. I was there. I kind of

56
00:03:27,750 --> 00:03:31,490
know what I said. But I was going to listen

57
00:03:31,490 --> 00:03:34,460
to the... I listened to Pod News Weekly Review anyway,

58
00:03:34,460 --> 00:03:37,460
even though there's this... This belief out there that I

59
00:03:37,460 --> 00:03:40,960
only listen to the bits where I'm mentioned. Yes, this

60
00:03:40,960 --> 00:03:44,430
is a belief. My robot did tell me, hey, you're

61
00:03:44,430 --> 00:03:49,129
on the show. he was like wait what yeah that's

62
00:03:49,129 --> 00:03:52,090
different uh so i wanted to hear how sam because

63
00:03:52,090 --> 00:03:54,169
i know i know sam had to edit it and

64
00:03:54,169 --> 00:03:55,889
he did a great job i only heard one edit

65
00:03:55,889 --> 00:03:57,949
and like how could there it is i don't know

66
00:03:57,949 --> 00:04:00,020
what he edited out um but that but i had

67
00:04:00,020 --> 00:04:05,300
some observations as well why don't you go first Well,

68
00:04:05,300 --> 00:04:10,659
um... I think I was already, you know, I've clearly

69
00:04:10,659 --> 00:04:15,550
already been thinking about all of this stuff, but. It

70
00:04:15,550 --> 00:04:18,560
was good to hear you sort of flesh out. One

71
00:04:18,560 --> 00:04:26,769
second. It's okay. We're not live or anything. Sorry, I

72
00:04:26,769 --> 00:04:31,759
dropped my package in the floor. But I was thinking

73
00:04:31,759 --> 00:04:38,399
about this already, and... You had said last week that

74
00:04:39,000 --> 00:04:45,170
You told me that you thought you were... Disappointed that

75
00:04:45,170 --> 00:04:51,560
the conversation about the MCP interface went straight to Ad

76
00:04:51,560 --> 00:04:58,899
removal. Yes. But missing the context of what You know,

77
00:04:58,899 --> 00:05:03,430
you were talking like missing your full thinking. It was

78
00:05:03,430 --> 00:05:08,040
not a criticism. It was I was mad at myself.

79
00:05:08,040 --> 00:05:11,410
I'm like, I should have avoided that. Yeah, no, I'm

80
00:05:11,410 --> 00:05:13,949
good. Yeah, I kind of picked up on that. But

81
00:05:13,949 --> 00:05:17,120
I was it was good to hear you flesh all

82
00:05:17,120 --> 00:05:25,250
that out. And I guess what – I guess what

83
00:05:25,250 --> 00:05:28,689
I was thinking about this morning as I was listening

84
00:05:28,689 --> 00:05:37,079
was – How the interfaces for podcast apps... I need

85
00:05:37,079 --> 00:05:42,879
to – the problem here is these are like non-formed

86
00:05:42,879 --> 00:05:46,750
thoughts. These are just like impressions, and I'm trying to

87
00:05:46,750 --> 00:05:50,970
put words on them for the first time. I think

88
00:05:50,970 --> 00:05:56,819
one thing I took away is that the podcast apps

89
00:05:56,819 --> 00:06:03,579
– are going to have to allow you to do

90
00:06:03,579 --> 00:06:08,810
more And let's let's for the moment, let's just put

91
00:06:08,810 --> 00:06:11,579
the I said the podcast apps. Let's just kind of

92
00:06:11,579 --> 00:06:13,699
put that to the side for a second. Whatever that

93
00:06:13,699 --> 00:06:17,709
might be. The podcast apps are going to have to

94
00:06:17,709 --> 00:06:21,990
let you actually do more with the content. And this

95
00:06:21,990 --> 00:06:26,860
also fits into the advertising removal or whatever you want.

96
00:06:27,980 --> 00:06:32,930
So – I, again, this is like with your theme

97
00:06:32,930 --> 00:06:36,050
with Sam, a lot of this is like you have

98
00:06:36,050 --> 00:06:38,910
a clear vision of what the future – of the

99
00:06:38,910 --> 00:06:45,379
shape of the future. But you can't know specifics. We

100
00:06:45,379 --> 00:06:48,009
just can't know. No, I'm just talking out of my

101
00:06:48,009 --> 00:06:53,709
butt, obviously. This is just what I'm seeing. Yeah, you're

102
00:06:53,709 --> 00:06:58,050
like, well, in the future, this is going to be

103
00:06:58,050 --> 00:07:02,529
the case, but – Well, maybe this will help. Maybe

104
00:07:02,529 --> 00:07:08,620
this will help. So the one thing, my takeaway actually

105
00:07:08,620 --> 00:07:14,199
came after the interview and Sam and James were discussing

106
00:07:14,199 --> 00:07:17,620
it. And there was this moment where it's like, well,

107
00:07:17,620 --> 00:07:20,889
normal people won't do that. And you know how I

108
00:07:20,889 --> 00:07:25,310
kind of. trip over the concept of normies or normal

109
00:07:25,310 --> 00:07:30,100
people. Yeah, you shame me for using that word. Well,

110
00:07:30,100 --> 00:07:34,920
and they kind of missed the whole point of what

111
00:07:34,920 --> 00:07:38,889
I was saying. My whole point, not just about podcast

112
00:07:38,889 --> 00:07:42,259
apps, and we have one too. So, you know, we're

113
00:07:42,259 --> 00:07:48,670
in this, I'm thinking about this for us. is Where

114
00:07:48,670 --> 00:07:55,319
will apps be at all? And so... Right now, I'm

115
00:07:55,319 --> 00:08:02,009
finding my robot to be very, really helpful in telling

116
00:08:02,009 --> 00:08:06,019
me why there's this episode of something I subscribe to

117
00:08:06,019 --> 00:08:09,920
because it now keeps a subscription list as well. Why

118
00:08:09,920 --> 00:08:13,149
I want to listen to this one, why it's right

119
00:08:13,149 --> 00:08:19,529
up my alley, or why this completely, again, this is

120
00:08:19,529 --> 00:08:24,170
the discovery part, right? This is just the engine is

121
00:08:24,170 --> 00:08:29,399
running, and it's still giving me better offline with Ed

122
00:08:29,399 --> 00:08:33,269
Zitron information. And without ads, even though I never asked

123
00:08:33,269 --> 00:08:35,379
it to do that, but it just considers that to

124
00:08:35,379 --> 00:08:37,509
be something that I want now. And I haven't told

125
00:08:37,509 --> 00:08:41,950
it otherwise. It gave me a give me this suggestion

126
00:08:41,950 --> 00:08:45,720
this morning. We just see if I can find this

127
00:08:45,720 --> 00:08:48,929
real quick that I was surprised by because it was

128
00:08:48,929 --> 00:08:53,370
it was a Dutch podcast. And I've never I don't

129
00:08:53,370 --> 00:08:57,379
listen to any. Here it is. Daily rundown of the

130
00:08:57,379 --> 00:09:00,710
biggest AI developments in Dutch. The latest episode covers a

131
00:09:00,710 --> 00:09:03,639
Dutch provider using AI phone calls with no auto warning,

132
00:09:03,639 --> 00:09:07,570
blah, blah, blah, blah, blah. And so it just threw

133
00:09:07,570 --> 00:09:09,940
that at me. I'm like, oh, it actually says here,

134
00:09:09,940 --> 00:09:13,460
good Dutch listening practice ahead of January. I'm going to

135
00:09:13,460 --> 00:09:16,889
Holland in January to visit our granddaughter. You need to

136
00:09:16,889 --> 00:09:21,779
learn the language. And right in your AI skeptic wheelhouse,

137
00:09:21,779 --> 00:09:25,769
said the robot. um that oh it's getting that from

138
00:09:25,769 --> 00:09:29,139
zitron well it's it's it's getting it knows you listen

139
00:09:29,139 --> 00:09:31,240
to better offline and so it thinks you're an ai

140
00:09:31,240 --> 00:09:33,120
skeptic it knows a lot more about me it has

141
00:09:33,120 --> 00:09:36,179
access to a lot more data sources so my point

142
00:09:36,179 --> 00:09:40,320
is that it's already really good at recommending things for

143
00:09:40,320 --> 00:09:44,379
me how how long does it take until i'm like

144
00:09:44,549 --> 00:09:46,340
I really just want you to present it to me

145
00:09:46,340 --> 00:09:50,960
right here. in you play it for me and it

146
00:09:50,960 --> 00:09:54,539
already floats a player you know it can float images

147
00:09:54,539 --> 00:09:59,370
above the chat window that's my point You know, just

148
00:09:59,370 --> 00:10:01,830
like the school mom that all of a sudden built

149
00:10:01,830 --> 00:10:04,029
an app for her that does only the things she

150
00:10:04,029 --> 00:10:07,909
needs from some Adobe product. So that was my overall

151
00:10:07,909 --> 00:10:11,879
point. And what I'm saying is normal people are going

152
00:10:11,879 --> 00:10:16,360
to do this. This is built for normal people. And

153
00:10:16,360 --> 00:10:18,820
I was like, can you just make it play better?

154
00:10:19,450 --> 00:10:23,389
It will come up with ideas. And of course, it's

155
00:10:23,389 --> 00:10:27,450
not going to be just a podcast. It could be

156
00:10:27,450 --> 00:10:31,559
all kinds of different data sources. And what I'm really

157
00:10:31,559 --> 00:10:37,100
kind of delighted about is that this solidifies RSS. And

158
00:10:37,100 --> 00:10:40,559
all of our extra tags and all the metadata that

159
00:10:40,559 --> 00:10:44,779
is flowing out through RSS feeds. That is the win

160
00:10:44,779 --> 00:10:48,480
here. I mean, wow. Wherever you get your podcast, I

161
00:10:48,480 --> 00:10:51,259
mean, my robot just plays it for me. I can

162
00:10:51,259 --> 00:10:54,330
literally tell my robot, play this on my Sonos. This

163
00:10:54,330 --> 00:10:57,070
podcast, I don't have to connect anything. It does all

164
00:10:57,070 --> 00:11:00,899
that for me. And so when people think of what

165
00:11:00,899 --> 00:11:05,440
crazy Adam's doing and, well, normal people won't do it.

166
00:11:05,519 --> 00:11:08,919
Well, yes, this is exactly what I'm trying to say.

167
00:11:11,330 --> 00:11:17,399
I mean, in one sense, like, Yeah, the phrase normal

168
00:11:17,399 --> 00:11:20,649
people won't do that, we've heard that for a long

169
00:11:20,649 --> 00:11:26,179
time. I mean, and sometimes that's true and sometimes that's

170
00:11:26,179 --> 00:11:29,299
not. Well, I think it used to be true. I

171
00:11:29,299 --> 00:11:35,149
think that's what's changing. Yeah, you can't always... You can't

172
00:11:35,149 --> 00:11:40,710
always predict. What, you know, what, quote, normal people will

173
00:11:40,710 --> 00:11:43,779
or will not do. And because there is no it's

174
00:11:43,779 --> 00:11:48,669
not monolithic. I mean, everybody's different. And I know. I

175
00:11:48,669 --> 00:11:53,100
know. In my own life, I need mental separation between

176
00:11:53,100 --> 00:11:59,379
concerns. Like, I don't – Me too, brother. That's a

177
00:11:59,379 --> 00:12:04,809
good statement. I need mental separation between concerns. Please stop

178
00:12:04,809 --> 00:12:08,409
it, honey. I don't – I want – like, I

179
00:12:08,409 --> 00:12:12,700
don't want to go to – here's – Some people

180
00:12:12,700 --> 00:12:16,759
have a, quote, combined inbox where they have four email

181
00:12:16,759 --> 00:12:20,710
accounts that all show up in the same thing. I

182
00:12:20,710 --> 00:12:24,769
can't handle that. I know. I know. Never. Never will

183
00:12:24,769 --> 00:12:28,049
I do that. Some people are like they you if

184
00:12:28,049 --> 00:12:32,240
I tell them, no, I have to have separate, distinct

185
00:12:32,240 --> 00:12:36,580
email inboxes that keep everything siloed into their own container.

186
00:12:37,320 --> 00:12:40,309
They look at me like I'm nuts. No, I'm with

187
00:12:40,309 --> 00:12:43,019
you. I'm with you. I wasn't like that, but I've

188
00:12:43,019 --> 00:12:46,700
definitely become that way. And it's to help me keep

189
00:12:46,700 --> 00:12:50,409
my sanity because I can't. I'm always afraid I'm going

190
00:12:50,409 --> 00:12:52,269
to. Oh, I'm going to be here and I'm going

191
00:12:52,269 --> 00:12:54,960
to respond from the wrong thing with this wrong account.

192
00:12:54,960 --> 00:12:58,960
I don't trust myself. And so and I like that.

193
00:12:59,389 --> 00:13:04,289
So I like having a podcast app. Mm-hmm. Where I

194
00:13:04,289 --> 00:13:08,139
can – I'm in podcast mode. That's why I don't

195
00:13:08,139 --> 00:13:09,950
– that's one of the reasons I don't use things

196
00:13:09,950 --> 00:13:12,740
like Spotify that are like a super app that have

197
00:13:12,740 --> 00:13:15,850
all these things they do that offer audiobooks and podcasts

198
00:13:15,850 --> 00:13:17,919
and music and all this kind of – I go

199
00:13:17,919 --> 00:13:25,419
– I like having myself visually locked – visually connected.

200
00:13:25,889 --> 00:13:31,100
My visual environment is my mental environment. And so if

201
00:13:31,100 --> 00:13:37,340
I'm visually in a podcast app, then I'm in listen-to-podcast

202
00:13:37,340 --> 00:13:43,059
mode of thinking. Mm-hmm. And so I think that at

203
00:13:43,059 --> 00:13:48,029
least for me, I really don't want to sort of

204
00:13:48,029 --> 00:13:51,120
like mash all this stuff up into a big bowl

205
00:13:51,120 --> 00:13:55,230
and let it spit things out to me. I don't

206
00:13:55,230 --> 00:13:59,590
really feel comfortable in that world, but I don't know

207
00:13:59,590 --> 00:14:03,299
that we necessarily have to go one extreme or the

208
00:14:03,299 --> 00:14:08,350
other. You know, the thing about it is. And this

209
00:14:08,350 --> 00:14:12,100
is kind of where I heard what you said, and

210
00:14:12,100 --> 00:14:17,679
I'm thinking, okay, well, there is like a medium here.

211
00:14:17,799 --> 00:14:23,220
There's like a midpoint where my podcast – I can

212
00:14:23,220 --> 00:14:29,830
still have a podcast app. And My daily driver for

213
00:14:29,830 --> 00:14:31,600
a long time, even though I check out new apps

214
00:14:31,600 --> 00:14:33,610
all the time, but my daily driver forever has been

215
00:14:33,610 --> 00:14:39,720
Cast-O-Matic. Well, maybe Cast-O-Matic just needs to give me more

216
00:14:39,720 --> 00:14:44,009
control. And I actually think Franco's really good about doing

217
00:14:44,009 --> 00:14:46,529
things like this with his app. Maybe it just needs

218
00:14:46,529 --> 00:14:51,740
to give me more control. Like, basically, it becomes a

219
00:14:51,740 --> 00:14:56,879
layer on top of... The agentic things that happen within

220
00:14:56,879 --> 00:14:59,440
the world of podcasting. And so.

221
00:15:00,110 --> 00:15:02,779
Maybe Castamatic hooks into the Podcast Index robot on the

222
00:15:02,779 --> 00:15:06,289
backside, or maybe it hooks into your Muse agent on

223
00:15:06,289 --> 00:15:11,909
the backside and lets Muse control it. Because, see, then

224
00:15:11,909 --> 00:15:15,460
that way… You know, I told you last week I

225
00:15:15,460 --> 00:15:20,620
was going to start building this ad removal specification. Yeah,

226
00:15:20,620 --> 00:15:23,059
you didn't get around to it, though. There's no way

227
00:15:23,059 --> 00:15:25,740
you had time to do that. No, I've been kicking

228
00:15:25,740 --> 00:15:32,919
it. I've been sort of like – Right before I

229
00:15:32,919 --> 00:15:37,460
leave from doing something else, I will flip over to

230
00:15:37,460 --> 00:15:40,259
that agent and And then just like give it an

231
00:15:40,259 --> 00:15:43,669
extra little hit and then I walk away. You're micro

232
00:15:43,669 --> 00:15:47,320
dosing. I'm micro dosing. Yeah. I keep, I pop the

233
00:15:47,320 --> 00:15:48,710
beach ball up in the air and then I come

234
00:15:48,710 --> 00:15:51,090
back for it later to catch it. You're vibe coding

235
00:15:51,090 --> 00:15:53,919
by micro dosing. Yes, I got it. I got it.

236
00:15:53,919 --> 00:15:56,980
And I've actually gotten a very long way, a very

237
00:15:56,980 --> 00:16:01,539
long way by doing this. Because that's one good thing

238
00:16:01,539 --> 00:16:05,639
about running a local Quinn model. With a Pi agent,

239
00:16:05,639 --> 00:16:09,049
it hardly ever asks you any questions. It just runs

240
00:16:09,049 --> 00:16:14,569
for hours and days by itself without asking questions. And

241
00:16:14,569 --> 00:16:17,769
so I've actually gotten very far. This may take this

242
00:16:17,769 --> 00:16:20,600
may take a month or two. I don't know. Because

243
00:16:20,600 --> 00:16:25,879
I'm not going to publish anything until it's exactly 100

244
00:16:25,879 --> 00:16:31,509
percent reliable. And there is a specification for removing dynamic

245
00:16:31,509 --> 00:16:36,740
ads from podcasts that do not. That faithfully never touch

246
00:16:36,740 --> 00:16:41,659
the actual content. And that's the way that – and

247
00:16:41,659 --> 00:16:44,299
I'm just not going to release any kind of half-assed

248
00:16:44,299 --> 00:16:47,009
thing. So when – the day that it comes where

249
00:16:47,009 --> 00:16:50,559
that thing can run through 75 podcasts and never make

250
00:16:50,559 --> 00:16:54,860
a mistake, that's when I'll know it's ready. But –

251
00:16:55,029 --> 00:16:57,950
So I've been doing this, and I thought, well, okay,

252
00:16:57,950 --> 00:17:02,220
think about all the permutations of this. Think about a

253
00:17:02,220 --> 00:17:10,139
person who wants to listen to the – okay. Let

254
00:17:10,139 --> 00:17:12,869
me just – I'm going to ramble here for a

255
00:17:12,869 --> 00:17:15,639
second, so just stop me if you need to –

256
00:17:15,639 --> 00:17:20,920
if I'm running on – So, My irritation with something

257
00:17:20,920 --> 00:17:26,869
like Better Offline is not really the ads themselves. It's

258
00:17:26,869 --> 00:17:29,920
the fact that it just gives – it keeps giving

259
00:17:29,920 --> 00:17:34,059
me ads that are completely – A, completely irrelevant to

260
00:17:34,059 --> 00:17:43,500
my life. And B, repeat endlessly. So I've heard the

261
00:17:43,500 --> 00:17:48,740
same ad, 30-second ad, for a local Indian tribe here

262
00:17:48,740 --> 00:17:54,639
in Alabama. for weeks and it's it plays three or

263
00:17:54,639 --> 00:17:57,970
four times per episode what is the pitch of this

264
00:17:57,970 --> 00:18:00,920
indian tribe just want this is ad recall test do

265
00:18:00,920 --> 00:18:03,700
you remember what the indian is it a casino is

266
00:18:03,700 --> 00:18:07,180
it a it's the porch creek indians okay and what

267
00:18:07,180 --> 00:18:10,099
alabama porch creek indians what do they want you to

268
00:18:10,099 --> 00:18:16,980
buy Nothing. It's like brand uplift. That is annoying. Yeah,

269
00:18:16,980 --> 00:18:20,079
it's like – I can tell you exactly – the

270
00:18:20,079 --> 00:18:22,980
ad starts off with, what does it mean for a

271
00:18:22,980 --> 00:18:27,799
nation to be successful? That's exactly what she says. Here

272
00:18:27,799 --> 00:18:29,829
at the Porch Creek Indians, we blah, blah, blah, blah,

273
00:18:29,829 --> 00:18:32,259
blah. It's crazy. And I'm like, what is the point

274
00:18:32,259 --> 00:18:39,160
of this? Okay. Okay. I mean, and I've heard the

275
00:18:39,160 --> 00:18:45,309
same ad for like some kind of eczema medication for

276
00:18:45,309 --> 00:18:49,900
weeks now. And it's again, it's multiple times per episode.

277
00:18:51,200 --> 00:18:54,309
And I think that this is the this is the

278
00:18:54,309 --> 00:19:00,150
advertising irritation thing. So I'm sort of analyzing myself and

279
00:19:00,150 --> 00:19:04,589
I'm saying it's not necessarily that there's ads because I

280
00:19:04,589 --> 00:19:06,819
listen to other shows that have ads into them and

281
00:19:06,819 --> 00:19:09,160
they don't irritate me nearly as much as this thing

282
00:19:09,160 --> 00:19:13,339
does. So like I could listen to an episode of

283
00:19:13,339 --> 00:19:15,960
accidental tech or whatever, and the ads are fine. I

284
00:19:15,960 --> 00:19:18,500
mean, I just listen through it or whatever. Sometimes I

285
00:19:18,500 --> 00:19:20,660
skip them. Sometimes I don't. It's not a big deal,

286
00:19:20,759 --> 00:19:24,470
but this particular show and a few others are just

287
00:19:24,470 --> 00:19:29,279
off the chain. So if my podcast app, If I

288
00:19:29,279 --> 00:19:33,710
could just tell it something like, hey, this show is

289
00:19:33,710 --> 00:19:40,869
giving me endlessly duplicate podcast ads – Please take them

290
00:19:40,869 --> 00:19:43,130
out or take – please take out – or if

291
00:19:43,130 --> 00:19:46,190
– while there's an ad playing, if it could tag

292
00:19:46,190 --> 00:19:48,500
it and it could say – it could tag it

293
00:19:48,500 --> 00:19:51,880
as Portsharek Indians and I could hit it and say,

294
00:19:51,880 --> 00:19:57,000
hey, never play that ad again. Or, hey, I don't

295
00:19:57,000 --> 00:19:59,829
want to hear any medication ads because I'm not in

296
00:19:59,829 --> 00:20:04,400
the medication needs business right now. My health is fine.

297
00:20:05,259 --> 00:20:09,930
I don't need GLP-1s. I'm good. If you could do

298
00:20:09,930 --> 00:20:14,670
things like that within your podcast app – That's this

299
00:20:14,670 --> 00:20:19,160
nice halfway point because you still have this podcast app

300
00:20:19,160 --> 00:20:22,599
experience, but you don't have – but you are now

301
00:20:22,599 --> 00:20:26,289
beginning to – like your app is giving you services

302
00:20:26,289 --> 00:20:29,670
on top of the content that help to customize it

303
00:20:29,670 --> 00:20:33,230
for you to make it more of an enjoyable listening

304
00:20:33,230 --> 00:20:38,410
experience. For you, and that actually deepens your relationship with

305
00:20:38,410 --> 00:20:41,700
the show you're listening to, because it's not that you're

306
00:20:41,700 --> 00:20:44,190
saying, take out all the ads, I never want to

307
00:20:44,190 --> 00:20:47,380
hear another ad again. Well, I mean, some people may

308
00:20:47,380 --> 00:20:51,299
want that, and that's fine. That's fine. That's where –

309
00:20:51,299 --> 00:20:53,119
the future is going to end up there. That's where

310
00:20:53,119 --> 00:20:56,369
we're going to get to. But – But there's another

311
00:20:56,369 --> 00:21:01,240
level of this that says, you know, I – I

312
00:21:01,240 --> 00:21:07,220
really like this show, but... I'm not going to buy

313
00:21:07,220 --> 00:21:11,450
lakefront property. That's not what I'm looking for. So please

314
00:21:11,450 --> 00:21:14,119
don't ever let me hear this ad again. And if

315
00:21:14,119 --> 00:21:17,279
you're able to do it, you don't have to feel

316
00:21:17,279 --> 00:21:21,710
like you're suffering through this show's irrelevant ad load for

317
00:21:21,710 --> 00:21:24,970
you. And so like – so this is why –

318
00:21:24,970 --> 00:21:29,089
that's just one thing that's on my mind, an example

319
00:21:29,089 --> 00:21:32,860
of a way that a podcast app could actually become

320
00:21:32,860 --> 00:21:39,569
very relevant – To the future agentic world. And they

321
00:21:39,569 --> 00:21:43,230
could eat and it can get its recommendations from your

322
00:21:43,230 --> 00:21:46,599
agents. Like if you have a muse or something like

323
00:21:46,599 --> 00:21:49,920
that, it can it could run out and say, hey,

324
00:21:49,920 --> 00:21:55,029
hey, muse agent, Adams muse agent. So whenever you come

325
00:21:55,029 --> 00:21:57,839
up with a good suggestion for a podcast he needs

326
00:21:57,839 --> 00:21:59,730
to have, let me know so I can pop it

327
00:21:59,730 --> 00:22:01,690
up and help and see if he wants to one-click

328
00:22:01,690 --> 00:22:06,630
subscribe in Castamatic or Podcast Guru. I guess what I'm

329
00:22:06,630 --> 00:22:07,880
saying is I don't think it has to be an

330
00:22:07,880 --> 00:22:12,329
all or nothing. Either the future has no podcast apps

331
00:22:12,329 --> 00:22:17,440
or everything stays the same. They're – There could be

332
00:22:17,440 --> 00:22:25,639
a very – Oh, please. Uh-oh. Go away. There could

333
00:22:25,639 --> 00:22:29,019
be a very fertile middle ground is what I'm saying.

334
00:22:29,839 --> 00:22:31,759
And I think Sam was actually – I think that's

335
00:22:31,759 --> 00:22:34,940
where maybe he was picking up on in the interview

336
00:22:34,940 --> 00:22:37,839
was he was saying, okay, we need to build these

337
00:22:37,839 --> 00:22:41,509
agents into our thing. The Kevin and Kelly thing he

338
00:22:41,509 --> 00:22:45,869
was talking about. I think he's seeing that... But maybe

339
00:22:45,869 --> 00:22:49,740
the agents don't necessarily have to be baked into your

340
00:22:49,740 --> 00:22:53,819
product. Maybe your product can just speak to them. Okay.

341
00:22:54,000 --> 00:22:56,690
So let me jump in. You have a buzz again

342
00:22:56,690 --> 00:23:01,269
today. Move to Choco Love. It's only me hearing these

343
00:23:01,269 --> 00:23:03,829
things, so don't worry about it, but I just hear

344
00:23:03,829 --> 00:23:08,519
it. Oh, there you go. Fixed it. It's like the

345
00:23:08,519 --> 00:23:11,799
Dutch media is trying to get a hold of me.

346
00:23:12,920 --> 00:23:16,000
They heard you're coming. They heard you're listening to their

347
00:23:16,000 --> 00:23:19,920
podcast. Well, I posted this picture of me on X.

348
00:23:20,880 --> 00:23:24,319
with a t-shirt and the t-shirt says jesus is my

349
00:23:24,319 --> 00:23:28,950
exit strategy okay and so i'm also opening a shopify

350
00:23:28,950 --> 00:23:30,779
store as we speak so i can sell it there's

351
00:23:30,779 --> 00:23:32,820
too many people who want it it was just ai

352
00:23:32,820 --> 00:23:37,389
people anyway um i can't just just make your own

353
00:23:37,389 --> 00:23:43,519
ai picture pretend you bought one um Yes, I will

354
00:23:43,519 --> 00:23:48,570
agree. So the perfect example is my Sonos system. I'm

355
00:23:48,570 --> 00:23:53,480
not having my robot play my playlist on my phone.

356
00:23:53,480 --> 00:23:55,320
I want it to play on my on my Sonos

357
00:23:55,320 --> 00:23:59,130
system. I'm, you know, I really don't, you know, yeah,

358
00:23:59,130 --> 00:24:02,259
I can Chromecast and all that. But I'd really just

359
00:24:02,259 --> 00:24:06,889
like to say, Robot pop-up West Wing most recent episode

360
00:24:06,889 --> 00:24:10,759
on my TV. So I'm in complete agreement that that

361
00:24:10,759 --> 00:24:14,299
is not necessary and maybe not always wanted. So I

362
00:24:14,299 --> 00:24:18,139
think I was conflating two things. The first one is

363
00:24:18,139 --> 00:24:24,110
I absolutely see a future without apps. Because people will

364
00:24:24,110 --> 00:24:28,380
eventually, even normal people, will eventually realize the power of

365
00:24:28,380 --> 00:24:31,329
creating something that you just want and you want it

366
00:24:31,329 --> 00:24:35,130
to work a certain way. That may be more productivity,

367
00:24:35,130 --> 00:24:38,849
business. You know, I don't see a future for shopping

368
00:24:38,849 --> 00:24:42,099
apps, you know, for to-do lists or any of that.

369
00:24:42,170 --> 00:24:44,869
I think that that is the first thing people will

370
00:24:44,869 --> 00:24:46,279
do is, oh, I wish I had a to do

371
00:24:46,279 --> 00:24:49,269
list that worked like this. And it will just build

372
00:24:49,269 --> 00:24:53,200
it for you and whether you somehow can run it.

373
00:24:53,420 --> 00:24:55,320
And that, of course, is going to be the problem.

374
00:24:55,519 --> 00:24:57,820
You know, I don't think Apple or Google are going

375
00:24:57,820 --> 00:25:00,990
to give up their app stores very easily. But I've

376
00:25:00,990 --> 00:25:04,320
already seen this power on my computer. And, you know,

377
00:25:04,320 --> 00:25:07,559
now go look at what Microsoft is doing with a

378
00:25:07,559 --> 00:25:11,610
new Surface laptop with built in with an RTX Blackwell

379
00:25:11,610 --> 00:25:15,650
chip built in. And you're Satya Nadella saying, oh, look,

380
00:25:15,650 --> 00:25:18,200
I made an app, the one I wanted in here.

381
00:25:18,299 --> 00:25:20,039
And it just works and it runs on my window.

382
00:25:20,200 --> 00:25:26,119
So this is going to come. But experientially, I'm in

383
00:25:26,119 --> 00:25:32,220
agreement that you don't necessarily have to recreate the functions

384
00:25:32,220 --> 00:25:38,420
of, for example, Podcast Guru, my daily driver, and certainly

385
00:25:38,420 --> 00:25:43,980
not CarPlay. I have Android Auto. All that stuff. No,

386
00:25:43,980 --> 00:25:46,720
that's a pain in the butt to build that. It

387
00:25:46,720 --> 00:25:49,250
may get easier one day, but really, all the work

388
00:25:49,250 --> 00:25:52,639
is already done. I'm quite happy with it. Would I

389
00:25:52,639 --> 00:25:56,579
want it changed? Maybe. What you're talking about is a

390
00:25:56,579 --> 00:26:01,779
connector. And I've been through this path now with most

391
00:26:01,779 --> 00:26:05,190
of the robot agents. And you need to submit and

392
00:26:05,190 --> 00:26:09,230
there's all this stuff and, you know, that hopefully will

393
00:26:09,230 --> 00:26:12,289
get better. And who knows? Maybe there will be, you

394
00:26:12,289 --> 00:26:15,179
know, people will play favorites and there's going to be

395
00:26:15,179 --> 00:26:18,289
blocking, you know, so you can't connect to Amazon, but

396
00:26:18,289 --> 00:26:23,159
you can connect to Shopify. Why? Well, Shopify is smart.

397
00:26:23,159 --> 00:26:25,809
They want your agent to be looking for stuff and

398
00:26:25,809 --> 00:26:32,170
buying things for you, etc. So, yes, the connector you

399
00:26:32,170 --> 00:26:36,779
want is really, I would say, it's kind of twofold.

400
00:26:37,380 --> 00:26:41,019
You want people to be able to connect their robot

401
00:26:41,019 --> 00:26:45,059
to your app so the robot can then automatically use

402
00:26:45,059 --> 00:26:52,559
the index. Yeah. to the podcast index robot to do

403
00:26:52,559 --> 00:26:55,619
all the discovery stuff. Because again, we're talking about ads.

404
00:26:55,659 --> 00:26:59,240
I'm just going to refuse. I don't care. The exciting

405
00:26:59,240 --> 00:27:02,840
thing is that it's finding things for me based upon

406
00:27:02,840 --> 00:27:06,019
what it knows about me. My podcast app does not,

407
00:27:06,019 --> 00:27:09,610
will not, should not know everything about me. However, as

408
00:27:09,610 --> 00:27:13,539
an input device, To send signals back to my robot,

409
00:27:13,539 --> 00:27:18,070
highly relevant. And then for the general experience of how

410
00:27:18,070 --> 00:27:21,000
it works and, you know, when video pops, all that

411
00:27:21,000 --> 00:27:26,240
stuff is great. I love Podcast Guru for that. Yeah.

412
00:27:26,900 --> 00:27:30,619
So, yes, there there it's not even an interim step.

413
00:27:30,619 --> 00:27:34,220
It's a very valid step of a play out experience

414
00:27:34,220 --> 00:27:38,170
of a real world, you know, because the minute it

415
00:27:38,170 --> 00:27:42,110
goes away from text, almost you're pushing things, you're pushing

416
00:27:42,110 --> 00:27:45,889
audio through the air or Bluetooth signal or whatever. Yeah,

417
00:27:45,889 --> 00:27:51,000
I think that's relevant. Um, What you don't want, of

418
00:27:51,000 --> 00:27:54,059
course, is you don't want to have to bake in

419
00:27:54,059 --> 00:27:57,820
any AI stuff into your app. You know, no. Have

420
00:27:57,820 --> 00:28:03,789
people connect your app to their robot and give their

421
00:28:03,789 --> 00:28:07,599
robot the command. Here's where you search. Here's the pod

422
00:28:07,599 --> 00:28:11,299
ping fire hose. Here's all the things you can do.

423
00:28:11,490 --> 00:28:13,889
And then when you have something, send it back to

424
00:28:13,889 --> 00:28:18,740
me. Absolutely. And I think developers should be looking into

425
00:28:18,740 --> 00:28:24,460
that right away. Now, I was going to say, will

426
00:28:24,460 --> 00:28:27,779
it make them any more money? Highly doubtful. You know,

427
00:28:27,779 --> 00:28:30,579
I'm always looking for this. I'm always looking for how

428
00:28:30,579 --> 00:28:35,779
can we make money for the app developers? I'm not

429
00:28:35,779 --> 00:28:39,740
seeing it yet. No, I mean, I don't see that

430
00:28:39,740 --> 00:28:45,200
yet either, but... I mean, it's possible that there is

431
00:28:45,200 --> 00:28:51,329
– And... It's possible that you – if your app

432
00:28:51,329 --> 00:28:56,960
does this very well, that you could start by just

433
00:28:56,960 --> 00:29:02,279
– it gets very popular. It makes – you know,

434
00:29:02,279 --> 00:29:07,670
you just sell more of it. Yeah. And that's at

435
00:29:07,670 --> 00:29:12,400
least something. I mean, the – but if the future

436
00:29:12,400 --> 00:29:17,460
evolves into L402 and these kinds of things – then

437
00:29:17,460 --> 00:29:21,539
that's at least an easier path for the app to

438
00:29:21,539 --> 00:29:23,659
have a share of something. I don't know what that

439
00:29:23,659 --> 00:29:31,039
looks like. But let's be realistic. The podcast apps are

440
00:29:31,039 --> 00:29:33,909
never going to make a dime out of the stack

441
00:29:33,909 --> 00:29:39,960
of podcast industry money. Unless there's programmable money involved. As

442
00:29:39,960 --> 00:29:43,230
long as it's basically the same system that there is

443
00:29:43,230 --> 00:29:47,659
now of money changing hands through advertising revenues and contracts

444
00:29:47,659 --> 00:29:49,670
and all these kinds of things, it's never going to

445
00:29:49,670 --> 00:29:52,880
happen. They're never going to get a dime. So unless

446
00:29:52,880 --> 00:29:59,779
– if there is an intermediary layer – then...

447
00:30:00,500 --> 00:30:04,450
At least like I can I can imagine if we're

448
00:30:04,450 --> 00:30:11,569
in the future. And no agenda was still around. Let's

449
00:30:11,569 --> 00:30:14,750
just use this show, a better example. A few years

450
00:30:14,750 --> 00:30:18,049
from now, things have progressed agentically, and this show is

451
00:30:18,049 --> 00:30:23,039
still asking for donations. And there's some sort of programmable

452
00:30:23,039 --> 00:30:28,980
money involved where Cast-O-Matic – is has gone out and

453
00:30:28,980 --> 00:30:36,319
connected to a user's robot. And that user that user's

454
00:30:36,319 --> 00:30:41,900
robot suggests podcasting 2.0 that they've subscribed to the boardroom.

455
00:30:42,359 --> 00:30:47,539
And then we could somehow. Filter that back and then

456
00:30:47,539 --> 00:30:50,470
that user gives us a donation. We could filter that

457
00:30:50,470 --> 00:30:53,960
back through to Cast-O-Matic in some way. Yeah, by becoming

458
00:30:53,960 --> 00:30:59,180
a money transmitter? No, but I mean you see what

459
00:30:59,180 --> 00:31:01,950
I mean. Well, I mean it's a donate. We could

460
00:31:01,950 --> 00:31:05,559
donate back. It's like thank you for the traffic. Thank

461
00:31:05,559 --> 00:31:08,640
you for the – That's called being a money –

462
00:31:08,640 --> 00:31:12,400
yeah, there's – I'm sorry. There's actually rules about that.

463
00:31:13,440 --> 00:31:15,500
No, I mean no. What I'm saying is that user

464
00:31:15,500 --> 00:31:20,029
gives us a donation through PayPal, and our robot says,

465
00:31:20,029 --> 00:31:23,519
oh, this user came in through Castomatic. We're going to

466
00:31:23,519 --> 00:31:26,619
donate back to his PayPal. That's not a money transmitter.

467
00:31:26,740 --> 00:31:33,430
That's just donations. Okay. Okay. Um, You seem irritated by

468
00:31:33,430 --> 00:31:38,349
this. Irritated? Annoyed, I guess. No, no, no, not at

469
00:31:38,349 --> 00:31:42,970
all. I'm just saying that that's not programmable money. That's

470
00:31:42,970 --> 00:31:51,200
fees with PayPal. The... The obvious thing that's going to

471
00:31:51,200 --> 00:32:00,799
happen is – okay. It's not irritated. It's sadness. I'm

472
00:32:00,799 --> 00:32:04,210
making you perpetually sad. No, no, no, no. I'm sorry,

473
00:32:04,210 --> 00:32:07,539
brother. No. Why do you say that? No, I'm sad.

474
00:32:07,559 --> 00:32:09,289
I made you sad with my ad talk, and I'm

475
00:32:09,289 --> 00:32:12,339
making you sad. No, that was – well, that's not

476
00:32:12,339 --> 00:32:18,000
you. I'm sad that – I'm sad for the work

477
00:32:18,000 --> 00:32:22,950
that goes into apps. Because I just don't see the

478
00:32:22,950 --> 00:32:27,180
future of them. And I just don't want to lie

479
00:32:27,180 --> 00:32:30,319
about it and struggle to find a way where now

480
00:32:30,319 --> 00:32:36,380
we're donating back to apps. The future is because I've

481
00:32:36,380 --> 00:32:40,190
seen it. And I've been actually was working a little

482
00:32:40,190 --> 00:32:44,069
bit today. It's been a busy day to tell my

483
00:32:44,069 --> 00:32:47,539
robot when I'm when I'm when I want to send

484
00:32:47,539 --> 00:32:50,880
I want to send a boost to gram to this

485
00:32:50,880 --> 00:32:55,420
podcast just like we did on the last time just.

486
00:32:55,849 --> 00:32:58,259
Send, you know, take care of it. You know, don't

487
00:32:58,259 --> 00:33:00,059
worry about, you know, just look at all the payments

488
00:33:00,059 --> 00:33:02,099
and look at the percentages to send it to them.

489
00:33:02,460 --> 00:33:06,539
LNURL, fine. Keysend, fine. Just send it all. Just take

490
00:33:06,539 --> 00:33:09,960
care of it for me. It has to be direct

491
00:33:09,960 --> 00:33:14,380
from the user to the splits, to the end users.

492
00:33:14,380 --> 00:33:19,700
That's the beauty of it. We can't be an intermediary.

493
00:33:19,700 --> 00:33:22,599
I mean, we can, but that's just not what it's

494
00:33:22,599 --> 00:33:29,789
going to be. And I am worried that apps are

495
00:33:29,789 --> 00:33:35,329
going to get cut out of that again. So that's

496
00:33:35,329 --> 00:33:39,309
my sadness. My sadness is we have a constituency of

497
00:33:39,309 --> 00:33:45,500
podcasting 2.0 who pour their heart into developing great apps.

498
00:33:46,119 --> 00:33:48,539
And I have a hard time seeing if, you know,

499
00:33:48,539 --> 00:33:52,160
yes, I see what you're saying, but I'm just seeing

500
00:33:52,160 --> 00:33:56,910
people making their own apps. For everything. I mean, you

501
00:33:56,910 --> 00:34:00,299
know, we laugh about Adobe. Ha ha. Screw those guys.

502
00:34:00,599 --> 00:34:07,849
But it's the same problem. Yes. Let me... Let me

503
00:34:07,849 --> 00:34:12,519
do story time for a second. Oh, Dave, story time.

504
00:34:13,000 --> 00:34:14,849
You know what? You just brought a smile to my

505
00:34:14,849 --> 00:34:26,880
face. So, There was this – I'm trying to remember

506
00:34:26,880 --> 00:34:39,260
what year this was. Maybe 2000... Like... 14, 13, something

507
00:34:39,260 --> 00:34:45,130
like that, maybe. Yeah, that feels right. So I had

508
00:34:45,130 --> 00:34:49,110
this And maybe that's right. But anyway, I had this

509
00:34:49,110 --> 00:34:56,789
sort of career crisis. thing that happened. And what it

510
00:34:56,789 --> 00:35:01,590
was, was the, at the, at the time, Everything, you

511
00:35:01,590 --> 00:35:06,720
know, everything's moving to the cloud. And I had started

512
00:35:06,720 --> 00:35:12,940
my career in IT sysadmin at a large multi-state insurance

513
00:35:12,940 --> 00:35:17,820
brokerage headquartered here in Alabama. I had started in their

514
00:35:17,820 --> 00:35:27,360
IT department. In 1997, late 97. And so I had

515
00:35:27,360 --> 00:35:35,179
been in... Like on-prem hardware, software, you know, everybody had,

516
00:35:35,179 --> 00:35:37,590
you had the day, you had your, your, your quote,

517
00:35:37,590 --> 00:35:41,420
server room. This is the way all businesses work. You

518
00:35:41,420 --> 00:35:44,860
had a server room. And so then like long about

519
00:35:44,860 --> 00:35:52,320
2012, 2013 or something like that. Every – the, quote,

520
00:35:52,320 --> 00:35:57,699
move to the cloud was going gangbusters, and everybody was

521
00:35:57,699 --> 00:36:03,420
all in on your digital transformation journey or whatever they

522
00:36:03,420 --> 00:36:09,510
were calling it back then. And at first I sort

523
00:36:09,510 --> 00:36:13,119
of like ignored it and was like, well, this is

524
00:36:13,119 --> 00:36:15,579
not – I mean we'll adopt some cloud stuff when

525
00:36:15,579 --> 00:36:17,679
we need it and we won't when we don't and

526
00:36:17,679 --> 00:36:21,590
these kinds of things. And – but then there was

527
00:36:21,590 --> 00:36:24,480
like this – I don't know. I had this –

528
00:36:25,320 --> 00:36:30,599
Vision of the future. Where me as a sysadmin, where

529
00:36:30,599 --> 00:36:37,269
I was completely irrelevant because – The story I was

530
00:36:37,269 --> 00:36:43,510
being told every single day by the tech-oriented press and

531
00:36:43,510 --> 00:36:46,489
the financial press and everything was the cloud is the

532
00:36:46,489 --> 00:36:51,440
future. You don't need Joe. Yeah. Who needs a local

533
00:36:51,440 --> 00:36:56,699
IT guy anymore? And then Microsoft said maybe in 2014,

534
00:36:56,699 --> 00:36:59,340
2015 that they were going to – they had this

535
00:36:59,340 --> 00:37:01,440
big push where they were going to do – start

536
00:37:01,440 --> 00:37:05,789
doing support directly to small businesses. And the story around

537
00:37:05,789 --> 00:37:12,139
that was, well, who needs IT people anymore? Because –

538
00:37:12,199 --> 00:37:17,779
Who's better at managing Microsoft's products than Microsoft? Right. And

539
00:37:17,779 --> 00:37:21,570
there was this whole narrative that lasted for a decade

540
00:37:21,570 --> 00:37:24,929
of why IT people and sysadmins are just not going

541
00:37:24,929 --> 00:37:27,340
to – are just the future. You guys – you

542
00:37:27,340 --> 00:37:30,760
all need to go find like a different career path

543
00:37:30,760 --> 00:37:35,510
because we don't need you anymore. Nobody is running email

544
00:37:35,510 --> 00:37:39,470
servers on their system, so all you Exchange admins, y'all

545
00:37:39,470 --> 00:37:45,079
go get a different job. Learn woodworking. Learn to code.

546
00:37:45,739 --> 00:37:50,679
Yeah, exactly. Learn to code, things like that. And so

547
00:37:50,679 --> 00:37:52,820
I had this – I really had like a mini

548
00:37:52,820 --> 00:37:56,260
freakout for a couple of months. Like it sort of

549
00:37:56,260 --> 00:37:59,599
– it finally got into my head, and I'm like,

550
00:37:59,599 --> 00:38:06,539
my job's over. The future is like everybody's just –

551
00:38:06,769 --> 00:38:09,929
When businesses start, they're just going to launch a few

552
00:38:09,929 --> 00:38:13,210
servers in the cloud, subscribe to Office 365, and they're

553
00:38:13,210 --> 00:38:17,300
done, and I'm never going to be needed again. And

554
00:38:17,300 --> 00:38:20,130
that turned out to be completely not true. Right. And

555
00:38:20,130 --> 00:38:23,400
so – and now we – if anything, we have

556
00:38:23,400 --> 00:38:27,489
a shortage of IT people, and we have – we've

557
00:38:27,489 --> 00:38:30,840
had a chronic shortage of IT people for a long

558
00:38:30,840 --> 00:38:37,559
time because what really happened was things became hybrid. And

559
00:38:37,559 --> 00:38:42,269
– There's lots of reasons why local things run... There's

560
00:38:42,269 --> 00:38:45,269
lots of reasons to have a thing local, and then

561
00:38:45,269 --> 00:38:47,880
there's other reasons to have a thing in the cloud.

562
00:38:48,199 --> 00:38:50,260
And as soon as you split that, now you have

563
00:38:50,260 --> 00:38:53,349
complexity because now you have to have those two things

564
00:38:53,349 --> 00:38:56,019
talk to each other. But you don't want to give

565
00:38:56,019 --> 00:38:58,730
up this great thing over here that runs really well

566
00:38:58,730 --> 00:39:00,889
locally, and you don't want to give up your great

567
00:39:00,889 --> 00:39:03,199
thing over here that runs really well in the cloud

568
00:39:03,199 --> 00:39:06,400
locally. But they really do have to connect. And as

569
00:39:06,400 --> 00:39:08,570
soon as you have a system like that, you have

570
00:39:08,570 --> 00:39:10,920
to have a person who understands the way all this

571
00:39:10,920 --> 00:39:14,239
stuff works that can actually make it function properly and

572
00:39:14,239 --> 00:39:17,429
well and get the business running. And so I guess

573
00:39:17,429 --> 00:39:23,050
what I'm saying, like. I was panicking, starting thinking about

574
00:39:23,050 --> 00:39:27,289
other jobs, other careers. And – but I think what

575
00:39:27,289 --> 00:39:30,800
that taught me was that, like, the – it's not

576
00:39:30,800 --> 00:39:35,039
that these visions of the future are wrong. It's that

577
00:39:35,039 --> 00:39:40,139
they're incomplete. They just don't take all of the considerations

578
00:39:40,139 --> 00:39:44,949
of human nature into account. And while it is possible

579
00:39:44,949 --> 00:39:49,260
that there's going to be a future with like no

580
00:39:49,260 --> 00:39:55,179
podcast apps, um, I'm not so sure that – I

581
00:39:55,179 --> 00:39:59,400
just don't think it's very likely because I think what

582
00:39:59,400 --> 00:40:03,070
happens over time is it takes – there's this lag

583
00:40:03,070 --> 00:40:08,960
period where it takes – Time for people to understand

584
00:40:08,960 --> 00:40:13,900
their own use case for these things, for these technologies.

585
00:40:14,760 --> 00:40:21,869
And the podcast apps – The... Like I don't envision

586
00:40:21,869 --> 00:40:27,139
myself – I don't really want – to not to

587
00:40:27,139 --> 00:40:29,739
listen to podcasts in something other than a podcast app.

588
00:40:30,380 --> 00:40:34,159
But if my podcast app just stagnates and never changes,

589
00:40:34,800 --> 00:40:38,320
maybe something else in the future would entice me away

590
00:40:38,320 --> 00:40:42,809
from that mindset. But if my podcast app continues to

591
00:40:42,809 --> 00:40:46,929
give me more and more options – Going forward to

592
00:40:46,929 --> 00:40:49,130
where I can feel more in control and I can

593
00:40:49,130 --> 00:40:50,970
feel like I'm a part of this new thing that's

594
00:40:50,970 --> 00:40:55,340
happening. Then I don't really have – I don't feel

595
00:40:55,340 --> 00:41:01,099
a big pull to change. So, like, I think that...

596
00:41:01,099 --> 00:41:04,739
Whoa, whoa. That's my buzz. Yeah, your buzz is big.

597
00:41:04,880 --> 00:41:09,789
There you go. Oh. Oh. We got one of these

598
00:41:09,789 --> 00:41:12,579
days we'll find the source of this. I don't know

599
00:41:12,579 --> 00:41:17,420
what it is, but. So I think there's something like,

600
00:41:17,420 --> 00:41:21,029
you know, like, like, you know, Fountain and Podcast Guru

601
00:41:21,029 --> 00:41:27,449
and Castomatic and TrueFans, like, they, these are apps that,

602
00:41:27,449 --> 00:41:33,179
you know, are run by very, very smart people Who

603
00:41:33,179 --> 00:41:36,139
like to be on the cutting edge of things. And

604
00:41:36,139 --> 00:41:39,029
I think that they can integrate a lot of the

605
00:41:39,029 --> 00:41:47,010
things that we love about. About agentic capabilities into their

606
00:41:47,010 --> 00:41:49,250
app and that makes you want to go use the

607
00:41:49,250 --> 00:41:56,579
app. Um, So the reason I was talking about advertising

608
00:41:56,579 --> 00:41:59,869
so much is because I think it's such – it's

609
00:41:59,869 --> 00:42:03,679
this thorny issue. It's not that I think that is

610
00:42:03,679 --> 00:42:11,889
the main issue. It's that it's such a watershed-type in-your-face

611
00:42:11,889 --> 00:42:16,449
annoyance. And I went back – remember a few months

612
00:42:16,449 --> 00:42:19,239
ago I talked about – I brought up this idea

613
00:42:19,239 --> 00:42:21,940
of what if we could come up with some sort

614
00:42:21,940 --> 00:42:26,210
of protocol where anytime I download an episode, I could

615
00:42:26,210 --> 00:42:29,210
ping out to some service. I was talking about Daniel

616
00:42:29,210 --> 00:42:32,539
J. Lewis' Chapters API. I could ping out to his

617
00:42:32,539 --> 00:42:36,389
API, have it generate a chapter set for me and

618
00:42:36,389 --> 00:42:40,470
bring it back for this episode. And what it was

619
00:42:40,470 --> 00:42:45,039
doing, my idea was give the apps the ability –

620
00:42:45,599 --> 00:42:50,059
To augment the content content that I that it's getting

621
00:42:50,059 --> 00:42:53,970
on its on its app for my benefit. Well, this

622
00:42:53,970 --> 00:42:57,829
is valid. This is the this this is like that

623
00:42:57,829 --> 00:43:03,789
on steroids. I agree. I agree. And it's simple. It's

624
00:43:03,789 --> 00:43:07,320
simple to implement. You've got to become a connector in

625
00:43:07,320 --> 00:43:12,210
all of these rope, all these robots. which is not

626
00:43:12,210 --> 00:43:18,349
simple. It's like submitting to 10 app stores. It's a

627
00:43:18,349 --> 00:43:22,019
pain in the butt. And the process is, of course,

628
00:43:22,019 --> 00:43:26,420
managed by AI on the other end. So... But why

629
00:43:26,420 --> 00:43:30,989
can't – so you have a robot. You have a

630
00:43:30,989 --> 00:43:35,630
Muse agent. Why can't your Muse agent expose some sort

631
00:43:35,630 --> 00:43:39,500
of interface or post a file somewhere or something like

632
00:43:39,500 --> 00:43:44,130
that? As long as it's a standardized format, Castomatic can

633
00:43:44,130 --> 00:43:47,340
then go and just look at that. There's a setting

634
00:43:47,340 --> 00:43:51,779
in Castomatic that says, here's the URL of my agent.

635
00:43:53,570 --> 00:43:56,920
And Castomatic, every time it wakes up, it goes and

636
00:43:56,920 --> 00:43:59,250
checks with your agent and says, hey, give me a

637
00:43:59,250 --> 00:44:01,720
bunch of information to go on. Is there any new

638
00:44:01,720 --> 00:44:05,279
podcasts? No, you're right. But in robot land, that's called

639
00:44:05,279 --> 00:44:10,110
a connector. So you have to connect. It doesn't just

640
00:44:10,110 --> 00:44:14,250
mean I've done this like, oh, set up a cloud

641
00:44:14,250 --> 00:44:17,730
flare. Oh, okay. So it did a test for me

642
00:44:17,730 --> 00:44:21,590
on Cloudflare. Cloudflare, you can set up like a 10-minute

643
00:44:21,590 --> 00:44:24,070
website that just works for 10 minutes and then it

644
00:44:24,070 --> 00:44:26,619
goes away. And I did that for a couple hours

645
00:44:26,619 --> 00:44:29,000
and then it was like, oh, I can't do that

646
00:44:29,000 --> 00:44:36,019
anymore. So on your own system, no problem. But these

647
00:44:36,019 --> 00:44:41,980
cloud systems, these cloud-based systems like RockBot and Muse and

648
00:44:41,980 --> 00:44:45,610
more to come, you know, ChatGPT, funny enough, was the

649
00:44:45,610 --> 00:44:48,909
hardest. You know, it's like you got to upload your

650
00:44:48,909 --> 00:44:52,300
left testicle. Okay, here it is. It's hard to do

651
00:44:52,300 --> 00:44:55,779
over the Internet. Yeah. Yeah. Um, it has to be,

652
00:44:55,779 --> 00:44:58,619
I'm just saying, I'm just giving, I'm, I'm leapfrogging saying

653
00:44:58,619 --> 00:44:59,960
the process is

654
00:45:00,239 --> 00:45:03,380
You have to allow people to connect their robot to

655
00:45:03,380 --> 00:45:07,210
your app. That's it. What about this? And I'm thinking

656
00:45:07,210 --> 00:45:10,170
of ways to get around that. Okay. So what about

657
00:45:10,170 --> 00:45:15,380
your Muse agent just knows, here's an object storage URL.

658
00:45:17,340 --> 00:45:20,880
And I want you to always post the latest, your

659
00:45:20,880 --> 00:45:27,340
latest findings about podcasts. in this specific format to this

660
00:45:27,340 --> 00:45:30,960
url and then you just point castamatic at that url

661
00:45:30,960 --> 00:45:34,159
well i can try it i'm just saying that these

662
00:45:34,159 --> 00:45:41,400
these uh These robot companies, they're getting cautious with that.

663
00:45:42,389 --> 00:45:45,780
You know, if you want to access a website, it

664
00:45:45,780 --> 00:45:49,139
pops up a card now or always allow, you know,

665
00:45:49,139 --> 00:45:51,320
and that seems to pop up a lot. You know,

666
00:45:51,320 --> 00:45:53,280
even if you say always allow, well, this is a

667
00:45:53,280 --> 00:45:57,840
little different URL. OK, always. I'm just saying that the

668
00:45:57,840 --> 00:46:02,090
process I'm with you. Of course, technically, I can see

669
00:46:02,090 --> 00:46:06,869
it. The process is become a connector. Jump ahead, just

670
00:46:06,869 --> 00:46:11,400
become a connector. Once you're a connector, that's like Sonos,

671
00:46:11,400 --> 00:46:14,349
the same thing. You have to go into Sonos. You

672
00:46:14,349 --> 00:46:16,289
have to approve it. Then it connects. You have to

673
00:46:16,289 --> 00:46:20,599
build a little app on Sonos, developer. It's fairly simple.

674
00:46:20,699 --> 00:46:23,219
The robot walked me through it. But that's how it

675
00:46:23,219 --> 00:46:25,960
connects then. And then once that connection is made, it's

676
00:46:25,960 --> 00:46:30,829
good. There was no standard connection already allowed. So you

677
00:46:30,829 --> 00:46:34,420
still have to make that connection for these robots to

678
00:46:34,420 --> 00:46:38,550
actually do it properly. See, I thought that the whole

679
00:46:38,550 --> 00:46:42,579
point of the Muse thing was that it allowed you

680
00:46:42,579 --> 00:46:48,309
to do – It allowed more flexibility. So that you

681
00:46:48,309 --> 00:46:53,400
could tell it something like always post your latest podcast

682
00:46:53,400 --> 00:46:58,119
recommendations or whatever to a to this URL. And here's

683
00:46:58,119 --> 00:47:06,210
your object storage keys. possibly... Possibly. But, you know, remember,

684
00:47:06,210 --> 00:47:08,780
we want this to be done by, quote, normal people.

685
00:47:08,780 --> 00:47:11,199
And the way it works now is connect to my

686
00:47:11,199 --> 00:47:14,989
Gmail. OK, connect. And it says affirm, confirm with your

687
00:47:14,989 --> 00:47:19,010
Gmail confirmed. OK, do you want your calendar? Yes, confirm.

688
00:47:19,010 --> 00:47:22,420
This is the process. I'm just saying that's the process.

689
00:47:22,420 --> 00:47:25,849
It's not it's not horrible. But you have to go

690
00:47:25,849 --> 00:47:28,989
through it. Just like submitting to the App Store, you

691
00:47:28,989 --> 00:47:32,860
have to become a connector. And, you know, when one

692
00:47:32,860 --> 00:47:35,079
or two are there, everyone else will jump in and

693
00:47:35,079 --> 00:47:37,139
everyone will have a connector. I'm just saying that that's

694
00:47:37,139 --> 00:47:42,690
the process. Become a connector. Mm-hmm. And technically what you're

695
00:47:42,690 --> 00:47:45,179
saying is exactly the same thing, but it has to

696
00:47:45,179 --> 00:47:46,940
go through the – that's just what they call it.

697
00:47:47,360 --> 00:47:49,820
They call it a connector. If I look at –

698
00:47:49,820 --> 00:47:52,599
let me see. If I look at Muse, let me

699
00:47:52,599 --> 00:48:02,550
see. What do I have? Um... Uh, Where's my... my

700
00:48:02,550 --> 00:48:06,969
settings here, settings, okay. Connectors. There you go. And it

701
00:48:06,969 --> 00:48:12,920
has preset connectors. It has Google Drive, Instagram, WithThings, Gmail,

702
00:48:12,920 --> 00:48:17,559
Google Calendar, Plaid, That's what you want. You want Plaid.

703
00:48:17,860 --> 00:48:22,219
This is the perfect example. Castomatic is always the canary

704
00:48:22,219 --> 00:48:24,150
in the coal mine. That's why I keep coming back

705
00:48:24,150 --> 00:48:26,489
to it so often. It's because it has no back-end

706
00:48:26,489 --> 00:48:32,500
servers. It's purely an on-device app. I understand. So it

707
00:48:32,500 --> 00:48:35,480
can't be a connector because there's nothing to connect to.

708
00:48:36,139 --> 00:48:38,949
It has to do the connection. It has to connect

709
00:48:38,949 --> 00:48:42,650
back to the agent. Yeah. Yeah. And so if that's

710
00:48:42,650 --> 00:48:46,579
like, well, we podcast be something we describe. We can

711
00:48:46,579 --> 00:48:49,639
build that spec. We can we can become we already

712
00:48:49,639 --> 00:48:53,409
are a connector now. I mean, I don't see us

713
00:48:53,409 --> 00:48:57,039
pre selected here. You know, there's no let me see

714
00:48:57,039 --> 00:49:01,800
if we have podcast. Let's see. No connectors found. Yeah.

715
00:49:01,960 --> 00:49:06,079
So I am connected through Muse because it's just doing,

716
00:49:06,079 --> 00:49:13,579
you know, HTTP calls to the MCP server. So a

717
00:49:13,579 --> 00:49:17,159
podcast index could become a connector, a general connector, and

718
00:49:17,159 --> 00:49:21,440
you say, okay, select you know, select podcast gurus. So,

719
00:49:21,440 --> 00:49:24,159
like, people are still going to have to select something.

720
00:49:24,840 --> 00:49:27,639
See, it just doesn't fit. It doesn't. My idea doesn't

721
00:49:27,639 --> 00:49:33,099
work. No, your idea. Bingo. Your idea doesn't work because

722
00:49:33,099 --> 00:49:36,619
that's not the. I mean, it may in the future

723
00:49:36,619 --> 00:49:39,769
if everybody's. If everybody has their own robot and it

724
00:49:39,769 --> 00:49:41,940
does exactly what they tell them to do, but these

725
00:49:41,940 --> 00:49:44,840
guys, they're for a whole bunch of different reasons, are

726
00:49:44,840 --> 00:49:47,929
going to... You know, put gates up to make sure

727
00:49:47,929 --> 00:49:50,820
that you know what you're doing or they can warn

728
00:49:50,820 --> 00:49:54,400
you like, well, you're connecting to this thing, you know,

729
00:49:54,400 --> 00:49:57,860
you're connecting to to plaid. So, well, you know, that

730
00:49:57,860 --> 00:50:00,779
means that your robot can look at your bank account.

731
00:50:02,599 --> 00:50:06,050
You see my point? Well, I think you just –

732
00:50:06,050 --> 00:50:09,420
my problem though here is that you just described how

733
00:50:09,420 --> 00:50:14,489
your future vision doesn't materialize because you're saying that they're

734
00:50:14,489 --> 00:50:20,519
going to block everybody. No, no, no. And if Muse

735
00:50:20,519 --> 00:50:24,760
is – Go ahead. If Muse is – The way

736
00:50:24,760 --> 00:50:29,260
that you're envisioning future things to evolve so that normal,

737
00:50:29,260 --> 00:50:34,590
quote unquote, normal people begin to interact with things like

738
00:50:34,590 --> 00:50:38,670
podcasting through an agent. But if that agent makes them

739
00:50:38,670 --> 00:50:40,940
jump through a whole bunch of hoops to do anything

740
00:50:40,940 --> 00:50:43,920
like this, well, then that's what good is it? My

741
00:50:43,920 --> 00:50:46,869
future is where everybody has their own agent running on

742
00:50:46,869 --> 00:50:49,500
their own hardware and it does stuff and you're in

743
00:50:49,500 --> 00:50:53,710
total control. That's the future future. This interim step is

744
00:50:53,710 --> 00:50:55,760
where everybody has to go. And a lot of people

745
00:50:55,760 --> 00:50:58,480
might never leave this interim step. They may feel very

746
00:50:58,480 --> 00:51:02,650
comfortable renting an agent that runs in the cloud and

747
00:51:02,650 --> 00:51:05,599
it's not on their own device. We're already seeing with

748
00:51:05,599 --> 00:51:09,659
Microsoft, just as the first example, hybrid. So that's what

749
00:51:09,659 --> 00:51:12,599
they're saying is hybrid. We believe most of this stuff

750
00:51:12,599 --> 00:51:14,970
works. that you're going to do locally on your own

751
00:51:14,970 --> 00:51:18,880
computer it'll build literally i was just watching nadella say

752
00:51:18,880 --> 00:51:21,779
this you build your own apps the apps you want

753
00:51:21,779 --> 00:51:25,630
locally on your computer sometimes you need something from the

754
00:51:25,630 --> 00:51:28,210
cloud and otherwise it's running on your computer so i

755
00:51:28,210 --> 00:51:30,900
see that as the future i don't know how quickly

756
00:51:30,900 --> 00:51:34,039
that's going to come to handheld devices but in the

757
00:51:34,039 --> 00:51:37,380
meantime I'm just saying the connector is how you do

758
00:51:37,380 --> 00:51:41,519
it today. And this this see this idea is like

759
00:51:41,519 --> 00:51:44,590
I keep hearing this. It's like everybody's going to build

760
00:51:44,590 --> 00:51:47,029
be able to build their own apps, but you can't

761
00:51:47,029 --> 00:51:50,949
even upload a file to an object storage. Like, how

762
00:51:50,949 --> 00:51:53,369
is this? I'm trying to make sense out of these

763
00:51:53,369 --> 00:51:56,340
two narratives I'm being told. No, I'm talking about a

764
00:51:56,340 --> 00:51:59,599
future that isn't here for everybody right now. It's here

765
00:51:59,599 --> 00:52:02,920
for me. I'm building my own apps. But yeah, I'm

766
00:52:02,920 --> 00:52:06,529
not a normal person. But it's going to come. But

767
00:52:06,529 --> 00:52:11,619
today, right now, we are in baby shoes, training wheels.

768
00:52:14,659 --> 00:52:17,360
Nathan said Muse will either let normies listen directly in

769
00:52:17,360 --> 00:52:18,970
the app or it will host an RSS feed for

770
00:52:18,970 --> 00:52:21,139
them to listen wherever they want. See, I just don't

771
00:52:21,139 --> 00:52:26,460
think that's enough. I don't think that's enough. To me,

772
00:52:26,460 --> 00:52:30,250
it's like... But we're arguing over implementation as it is

773
00:52:30,250 --> 00:52:35,279
today, not over what is going to come. What's going

774
00:52:35,279 --> 00:52:37,519
to come is going to be a very different world.

775
00:52:37,619 --> 00:52:41,380
But today, if you want to get started, just add

776
00:52:41,380 --> 00:52:44,440
your app. as a connector and then you can tell

777
00:52:44,440 --> 00:52:49,460
that person's app the robot to go connect to the

778
00:52:49,460 --> 00:52:52,929
podcast index robot to do all the calls and then

779
00:52:52,929 --> 00:52:56,360
you have a two-way street With feedback from the app

780
00:52:56,360 --> 00:52:59,000
and stuff going to the app. I mean, it's exactly

781
00:52:59,000 --> 00:53:01,860
what you're saying. It's just. No, it has. But it's

782
00:53:01,860 --> 00:53:04,500
not. It is. It's not. It is exactly the same.

783
00:53:05,360 --> 00:53:09,340
False. Well, fact check false. What do you mean? It's

784
00:53:09,340 --> 00:53:13,599
because what I'm saying is I'm trying to say the

785
00:53:13,599 --> 00:53:19,820
full vision of what you are. What you fleshed out.

786
00:53:20,500 --> 00:53:25,420
The full vision of what you flashed was I have

787
00:53:25,420 --> 00:53:29,980
this thing that can do – that will do whatever

788
00:53:29,980 --> 00:53:35,230
I tell it to. There's this thing operating on my

789
00:53:35,230 --> 00:53:39,820
behalf where I can just go and tell it, hey,

790
00:53:39,820 --> 00:53:43,320
I like this kind of thing, and it just –

791
00:53:44,269 --> 00:53:46,400
gets it for me and does things for me and

792
00:53:46,400 --> 00:53:49,630
all these kinds. It's operating constantly in the background on

793
00:53:49,630 --> 00:53:54,760
my behalf. The podcast index MCP, as amazing as it

794
00:53:54,760 --> 00:53:59,739
is, it is not operating on Nathan's behalf. It is

795
00:53:59,739 --> 00:54:03,070
general. It's general. And what I'm saying is the only

796
00:54:03,070 --> 00:54:05,880
thing that's ever going to operate on Nathan's behalf is

797
00:54:05,880 --> 00:54:09,639
Nathan's robot. What do you mean? What do you mean?

798
00:54:09,639 --> 00:54:15,029
It's not the podcast index robot does nothing but proxy

799
00:54:15,029 --> 00:54:19,639
the API calls. My robot is doing what I want.

800
00:54:20,050 --> 00:54:22,489
Right, and yes, that's what I'm saying, but I'm saying

801
00:54:22,489 --> 00:54:25,639
in order for the app, the podcast app, to have

802
00:54:25,639 --> 00:54:30,329
the benefit, to have the power that it needs. That

803
00:54:30,329 --> 00:54:32,179
it needs to be able to connect to the robot.

804
00:54:32,880 --> 00:54:35,059
It needs to be able to connect – to nathan's

805
00:54:35,059 --> 00:54:38,300
robot not the podcast no but that's what i'm saying

806
00:54:38,300 --> 00:54:41,900
that's what a connector is you connect your robot to

807
00:54:41,900 --> 00:54:44,940
the app well and right but what i'm saying is

808
00:54:44,940 --> 00:54:50,269
there is no connector back to castomatic All Cast-O-Matic has

809
00:54:50,269 --> 00:54:53,289
to do is say, well, okay, because you mean because

810
00:54:53,289 --> 00:54:56,529
Cast-O-Matic, well, even that, I don't see why that's a

811
00:54:56,529 --> 00:55:01,010
problem. No, it is a problem because, okay, you're right,

812
00:55:01,010 --> 00:55:05,320
Cast-O-Matic, if there's no server side on the app itself,

813
00:55:06,150 --> 00:55:10,909
That... can talk to or can be talked to, I

814
00:55:10,909 --> 00:55:18,050
see the problem. Now, there's a possibility that... But this

815
00:55:18,050 --> 00:55:23,500
is OS level that the robot can interact with other

816
00:55:23,500 --> 00:55:28,909
apps, inter-app communication. That's already happening because it can read

817
00:55:28,909 --> 00:55:32,199
notifications. But that is another thing you have to set

818
00:55:32,199 --> 00:55:36,460
up. It's not out of the box and for good

819
00:55:36,460 --> 00:55:40,619
reason. So Castamatic is a is the outlier, but it

820
00:55:40,619 --> 00:55:44,199
is also the most important outlier. I understand what you're

821
00:55:44,199 --> 00:55:48,970
saying. But let's just stick for a second with Nathan

822
00:55:48,970 --> 00:55:53,289
needs to connect his app to his robot that can

823
00:55:53,289 --> 00:55:56,900
be done today. No matter no matter what else he

824
00:55:56,900 --> 00:56:01,739
connects to. You know, I'm done with the boardroom. Why?

825
00:56:01,900 --> 00:56:05,559
The boardroom is so full of crap. Why? This is

826
00:56:05,559 --> 00:56:09,380
AI 2.0. How about that funding tag? How's that coming

827
00:56:09,380 --> 00:56:12,059
along? It's all robot now. You know what? We've been

828
00:56:12,059 --> 00:56:15,360
talking about nothing but podcasting since we started this episode.

829
00:56:16,139 --> 00:56:18,970
That's all we have talked about. The future of podcast

830
00:56:18,970 --> 00:56:25,150
apps. This is fundamental. We're talking about potentially building a

831
00:56:25,150 --> 00:56:29,000
protocol that lets podcast apps talk to their agents. I

832
00:56:29,000 --> 00:56:33,940
mean, what else do you people want? I almost cussed.

833
00:56:34,000 --> 00:56:39,519
I'm not going to do it. It's because I'm flipping

834
00:56:39,519 --> 00:56:43,300
back over here to my to my my showrunner thing.

835
00:56:43,739 --> 00:56:44,949
Yeah. So I can so I can look up stuff

836
00:56:44,949 --> 00:56:48,940
on the Internet. Well, these are. But what you're seeing

837
00:56:48,940 --> 00:56:53,909
is people who are hurt and disillusioned and who hate

838
00:56:53,909 --> 00:57:00,500
A.I. because they also know what's coming. We're trying to

839
00:57:00,500 --> 00:57:06,840
find... Great solutions. And if you just want to say,

840
00:57:06,840 --> 00:57:11,900
oh, it's AI 2.0, well, check the calendar, dude. This

841
00:57:11,900 --> 00:57:14,440
is what's happening in the world. We are at the

842
00:57:14,440 --> 00:57:20,610
beginning of an amazing, amazing golden age where I believe

843
00:57:20,610 --> 00:57:23,369
people will have a lot of leverage and a lot

844
00:57:23,369 --> 00:57:28,570
of power. Time to grab land now. That's what's going

845
00:57:28,570 --> 00:57:33,139
on here. I mean, in case anyone hadn't noticed, the

846
00:57:33,139 --> 00:57:38,159
amount of independent app usage is going down rapidly. Why?

847
00:57:38,779 --> 00:57:41,220
Well, I don't know. But maybe we should try and

848
00:57:41,220 --> 00:57:46,110
offer something that other companies can't offer. Maybe we should

849
00:57:46,110 --> 00:57:49,989
just not ever talk about AI. And watch all of

850
00:57:49,989 --> 00:57:53,559
the independent podcast apps disappear off the face of the

851
00:57:53,559 --> 00:57:56,369
earth because of AI, and then we'll all just look

852
00:57:56,369 --> 00:58:00,670
at each other and wonder what happened. Or we could

853
00:58:00,670 --> 00:58:03,889
actually try to face the future as it stands, as

854
00:58:03,889 --> 00:58:08,630
it's coming, and build on top of it so that

855
00:58:08,630 --> 00:58:13,150
all this remains in some sense. It's no sweat off

856
00:58:13,150 --> 00:58:23,079
my balls. Johnny D. Straight from heaven. But this is

857
00:58:23,079 --> 00:58:25,920
my point. You can't laugh one day about what happened

858
00:58:25,920 --> 00:58:28,980
to Adobe and then not think about your own backyard,

859
00:58:28,980 --> 00:58:34,199
which includes Adam and Dave. Yes, it includes all of

860
00:58:34,199 --> 00:58:37,110
us. Yeah, it's all of us. And here we are

861
00:58:37,110 --> 00:58:40,779
talking about what we can actually do. Anyway, whatever. I'm

862
00:58:40,779 --> 00:58:44,360
useless. I was I was talking to a friend of

863
00:58:44,360 --> 00:58:49,920
mine this week who is has been a. a highly

864
00:58:49,920 --> 00:58:57,159
successful sales team. manager in the tech world for many,

865
00:58:57,159 --> 00:59:05,099
many years. This person has worked for every... Silicon Valley,

866
00:59:05,099 --> 00:59:13,179
big Silicon Valley name that you know. And they... At

867
00:59:13,179 --> 00:59:20,329
every... They just started working for a new company back

868
00:59:20,329 --> 00:59:27,519
in April and inherited a team of salespeople. And so

869
00:59:27,519 --> 00:59:32,750
– We were talking last night. And they were saying

870
00:59:32,750 --> 00:59:39,949
that the... The amount of stuff that they are replacing

871
00:59:39,949 --> 00:59:47,489
internally, they have stopped hiring out all kinds of consulting

872
00:59:47,489 --> 00:59:51,550
work. to like the big four consulting firms like Deloitte

873
00:59:51,550 --> 00:59:57,079
and all these kinds of things. This is all because

874
00:59:57,079 --> 00:59:59,960
they're doing it all with AI because they used to

875
00:59:59,960 --> 00:59:59,960
have

876
01:00:00,030 --> 01:00:03,320
All of this work that they could not process on

877
01:00:03,320 --> 01:00:07,039
their own, and it was more cost-efficient to just hire

878
01:00:07,039 --> 01:00:11,550
it out. And now they've brought it back in-house, and

879
01:00:11,550 --> 01:00:15,239
they're able to put a small team on it, and

880
01:00:15,239 --> 01:00:19,840
they're able to essentially do months of work in weeks.

881
01:00:19,840 --> 01:00:23,739
Mm-hmm. And because most of it is just compiling data

882
01:00:23,739 --> 01:00:29,090
and just moving data around. Well, this is I mean,

883
01:00:29,090 --> 01:00:35,250
we're talking about major economic shifts that are about to

884
01:00:35,250 --> 01:00:39,510
happen. If things are happening in the in the in

885
01:00:39,510 --> 01:00:44,179
the economy. Up in the billions of dollars range. Do

886
01:00:44,179 --> 01:00:47,139
we think that are we crazy enough to think that

887
01:00:47,139 --> 01:00:50,619
it's not going to affect podcast apps? Give me a

888
01:00:50,619 --> 01:00:54,670
break. Of course it is. Things are going to things

889
01:00:54,670 --> 01:00:57,980
are changing and they are going to change. And I

890
01:00:57,980 --> 01:01:02,000
just would rather I would rather actually I would rather

891
01:01:02,000 --> 01:01:06,400
meet it head on. And discuss it so that we

892
01:01:06,400 --> 01:01:13,019
can at least give podcast app developers the chance to

893
01:01:13,019 --> 01:01:17,070
adapt their apps in a way where people still find

894
01:01:17,070 --> 01:01:21,800
them very useful. Whatever we have to build to do

895
01:01:21,800 --> 01:01:25,670
that, we need to do it. Let's do it. You're

896
01:01:25,670 --> 01:01:29,860
the one that's getting mad, not me. I'm talking to

897
01:01:29,860 --> 01:01:32,400
the world. I'm not talking to you. I'm talking to

898
01:01:32,400 --> 01:01:36,570
the world. I'm just saying that like this – because

899
01:01:36,570 --> 01:01:39,539
the thought of – Yeah, I want to do –

900
01:01:39,539 --> 01:01:42,110
of course. Let's do a phase nine of the namespace

901
01:01:42,110 --> 01:01:44,570
and let's throw the contact tag in. Let's fix key

902
01:01:44,570 --> 01:01:48,219
send. And I've got a few tags that I think

903
01:01:48,219 --> 01:01:51,570
are ready to go, and I want to do that

904
01:01:51,570 --> 01:01:55,039
work. Let me just say – let me remind us

905
01:01:55,039 --> 01:02:00,340
of something. We started Podcast Index for a reason, and

906
01:02:00,340 --> 01:02:03,110
it's going to turn out to be a great reason

907
01:02:03,110 --> 01:02:06,980
because RSS is going to be more important than ever

908
01:02:06,980 --> 01:02:11,469
with, in my opinion, with what is coming. Tags are

909
01:02:11,469 --> 01:02:14,940
going to be super important for what is coming. As

910
01:02:14,940 --> 01:02:19,610
I scoffed about AEO, the ask engine optimization is going

911
01:02:19,610 --> 01:02:23,309
to be a real thing. And so when robots are

912
01:02:23,309 --> 01:02:27,139
already running around and when they're looking for a certain

913
01:02:27,139 --> 01:02:30,210
person on the podcast and you've got a person tag,

914
01:02:30,210 --> 01:02:33,269
you're going to be found, which has always been my

915
01:02:33,269 --> 01:02:37,820
mission here is discovery, discovery, discovery, reasons to get to

916
01:02:37,820 --> 01:02:42,739
get things that I want to hear. Making that work

917
01:02:43,460 --> 01:02:46,659
is a part of the podcast app developers, which I

918
01:02:46,659 --> 01:02:49,980
still believe is very relevant, as I just said, you

919
01:02:49,980 --> 01:02:55,440
know, Sonos, television, podcast app, all of that. Stay ahead

920
01:02:55,440 --> 01:02:59,980
of the game. We're going to be great. We may

921
01:02:59,980 --> 01:03:02,719
have nobody who's going to donate to us anymore, but

922
01:03:02,719 --> 01:03:07,360
we'll be great. We'll have servers. We'll have servers. We

923
01:03:07,360 --> 01:03:10,940
can't pay for it, but we'll have servers. Well, hosting

924
01:03:10,940 --> 01:03:12,980
companies are going to be great. That's still going to

925
01:03:12,980 --> 01:03:17,250
be needed. It feels like we just pontificate about what

926
01:03:17,250 --> 01:03:19,019
could happen with AI. There's great things we can do

927
01:03:19,019 --> 01:03:20,949
with it now, so let's do them. I agree. I

928
01:03:20,949 --> 01:03:31,300
understand that, Eric. I think – but what – What

929
01:03:31,300 --> 01:03:33,710
did we do with the namespace? What did we all

930
01:03:33,710 --> 01:03:36,780
collectively do with the namespace? We got out ahead of

931
01:03:36,780 --> 01:03:41,840
things and created something that was brand new. We created

932
01:03:41,840 --> 01:03:45,869
a thing – we created micropayments and transcripts and all

933
01:03:45,869 --> 01:03:50,840
these things that had never existed before in podcasting. And

934
01:03:50,840 --> 01:03:53,139
that's what I'm saying we should do right now. I'm

935
01:03:53,139 --> 01:03:55,980
saying that we should do things like – here's another

936
01:03:55,980 --> 01:04:01,699
idea. that I had. Sam has been talking about for

937
01:04:01,699 --> 01:04:07,400
a long time About using activity streams and activity pubs.

938
01:04:07,400 --> 01:04:12,409
He has always wanted a future where podcast actions or

939
01:04:12,409 --> 01:04:19,630
activities are – where they ripple through the Fediverse. And

940
01:04:19,630 --> 01:04:24,420
what has always been the big wall that's kept that

941
01:04:24,420 --> 01:04:31,090
from happening is mastodon. Mastodon does not show custom activity

942
01:04:31,090 --> 01:04:35,840
streams or custom activity pub types. It doesn't show them

943
01:04:35,840 --> 01:04:40,220
up in their native format. It just sort of like

944
01:04:40,220 --> 01:04:45,960
transmogrifies them into a note is what it's called. So

945
01:04:45,960 --> 01:04:52,269
everything just becomes a note. Well, we have now this

946
01:04:52,269 --> 01:04:59,779
power. to perhaps change that. Yes. Maybe we can begin

947
01:04:59,779 --> 01:05:05,220
to roll out new Fediverse compatible software I built the

948
01:05:05,220 --> 01:05:09,829
AP, the Activity Pub Podcast Index Bridge a few years

949
01:05:09,829 --> 01:05:14,940
ago, the hard way by hand. I built that thing,

950
01:05:14,940 --> 01:05:20,170
and it works. Why don't we begin to actually publish

951
01:05:20,170 --> 01:05:23,170
some of these – why can't apps begin to actually

952
01:05:23,170 --> 01:05:26,409
publish some of this Activity Pub stuff? In its native

953
01:05:26,409 --> 01:05:30,670
format, and then we will build Mastodon-like software that layers

954
01:05:30,670 --> 01:05:32,829
on top of it and actually shows it in its

955
01:05:32,829 --> 01:05:37,220
native format. And what do we do with that? Well,

956
01:05:37,220 --> 01:05:42,119
I mean, that could be something that podcast platforms bake

957
01:05:42,119 --> 01:05:45,279
in or podcast apps bake into their stuff. They could

958
01:05:45,279 --> 01:05:48,750
subscribe. Cast-O-Matic, let's just keep rolling with Cast-O-Matic since it's

959
01:05:48,750 --> 01:05:53,420
the canary in the coal mine. Cast-O-Matic could bake ActivityPub

960
01:05:53,420 --> 01:05:59,199
into itself where it shows native content. native format activity

961
01:05:59,199 --> 01:06:04,079
streams coming out of podcasting. into in its own interface

962
01:06:04,079 --> 01:06:06,880
so one of the things you said in sam's i'm

963
01:06:06,880 --> 01:06:09,019
sorry i'm talking so much i just you gave me

964
01:06:09,019 --> 01:06:11,300
a lot of ideas no keep going i like it

965
01:06:11,300 --> 01:06:15,320
one of the things you said in your uh In

966
01:06:15,320 --> 01:06:19,360
your interview with Sam is that newsletters are so critically

967
01:06:19,360 --> 01:06:23,400
important to donations for podcasts and keeping people interested. That's

968
01:06:23,400 --> 01:06:27,720
one sub stack. That's why they're on a roll. And...

969
01:06:28,889 --> 01:06:33,880
Maybe your podcast app If the if, you know, people

970
01:06:33,880 --> 01:06:37,099
are getting email fatigue and people are beginning to filter

971
01:06:37,099 --> 01:06:39,360
out a lot of these things in emails, which I'm

972
01:06:39,360 --> 01:06:42,000
doing, I've really I've really gotten a handle on my

973
01:06:42,000 --> 01:06:45,559
email and filtering out a ton of stuff now. Maybe

974
01:06:45,559 --> 01:06:50,480
the podcast app becomes a – Sort of more than

975
01:06:50,480 --> 01:06:53,400
just a podcast, but a news feed into your pod

976
01:06:53,400 --> 01:06:57,570
into the podcast world that you are interested in. And

977
01:06:57,570 --> 01:07:00,000
so that your newsletter is not just coming through your

978
01:07:00,000 --> 01:07:02,300
email where it's going to land in your spam box.

979
01:07:02,400 --> 01:07:04,210
It's also good that maybe your newsletter comes through your

980
01:07:04,210 --> 01:07:07,980
podcast app. I mean, true fans does that already. But

981
01:07:07,980 --> 01:07:11,800
but if we had the activity pub section of that,

982
01:07:11,800 --> 01:07:14,500
it could be posted as an act as as a

983
01:07:14,500 --> 01:07:19,039
map as an activity pub. Yeah. Object on the Fediverse

984
01:07:19,039 --> 01:07:23,539
and you're following your podcast as an activity pub actor.

985
01:07:23,760 --> 01:07:27,019
And now you get the the the the newsletter as

986
01:07:27,019 --> 01:07:32,980
well. I'm just brainstorming stuff. Mm hmm. I'm brainstorming ways

987
01:07:32,980 --> 01:07:38,679
that podcast apps can keep themselves relevant because, like you

988
01:07:38,679 --> 01:07:43,079
said, they are podcast, independent podcast app usage is declining.

989
01:07:43,420 --> 01:07:48,039
Yeah. So whether or not AI is the future, regardless

990
01:07:48,039 --> 01:07:53,710
of that, something's wrong and something needs to change. So

991
01:07:53,710 --> 01:07:57,690
we got things that are – we have things that

992
01:07:57,690 --> 01:07:59,960
are more – what I'm saying is I think we

993
01:07:59,960 --> 01:08:02,779
have things that are more structural right now than just

994
01:08:02,779 --> 01:08:10,269
namespace design. Because namespaces are great, but if we already

995
01:08:10,269 --> 01:08:15,960
have – Some ability, and we do, new phones have

996
01:08:15,960 --> 01:08:18,899
models on board that can hook in and do some

997
01:08:18,899 --> 01:08:24,479
small model type stuff already. If they can themselves begin

998
01:08:24,479 --> 01:08:27,989
to figure out these things like – Yeah, what the

999
01:08:27,989 --> 01:08:31,229
activity is and what that means for your behavior. For

1000
01:08:31,229 --> 01:08:35,149
what you want and what you... So, for instance, if

1001
01:08:35,149 --> 01:08:44,609
I skip ahead on all those ads... Yes. My robot

1002
01:08:44,609 --> 01:08:50,899
would know to do that automatically. Or... If the and

1003
01:08:50,899 --> 01:08:55,819
this is, again, why I'm saying that the podcast namespace

1004
01:08:55,819 --> 01:09:00,159
may not be. As high on the priority list right

1005
01:09:00,159 --> 01:09:03,239
now as this other stuff is if your podcast app

1006
01:09:03,239 --> 01:09:06,809
sees that there is not a person tag listed in

1007
01:09:06,809 --> 01:09:09,470
your feed, but it can still use its local model

1008
01:09:09,470 --> 01:09:13,559
to go figure out who these people are. It doesn't

1009
01:09:13,559 --> 01:09:17,970
matter anymore. We already saw this with transcripts. Transcripts are

1010
01:09:17,970 --> 01:09:21,109
being done on device now. Yep. It's great that there's

1011
01:09:21,109 --> 01:09:25,619
a transcript tag, but it's now become almost irrelevant. Look

1012
01:09:25,619 --> 01:09:28,520
at how fast that went. Yeah, it went from –

1013
01:09:28,520 --> 01:09:31,829
within a year, it went from transcript tag is awesome

1014
01:09:31,829 --> 01:09:37,539
to transcript tag is completely unnecessary. Mm-hmm. That's right. And

1015
01:09:37,539 --> 01:09:40,579
the only people that care to put a transcript tag

1016
01:09:40,579 --> 01:09:43,510
in their feed by hand anymore are going to be

1017
01:09:43,510 --> 01:09:48,180
like the .00001% of people who still code by hand.

1018
01:09:48,239 --> 01:09:51,600
Yes, not normal people. Yeah. And so like I'm saying

1019
01:09:51,600 --> 01:09:54,309
– yeah, exactly. What I'm saying is like we need

1020
01:09:54,309 --> 01:09:57,640
to figure out what the future looks like. Not the

1021
01:09:57,640 --> 01:10:00,260
future. Sorry. I'm sorry. We need to figure out what

1022
01:10:00,260 --> 01:10:04,329
right now looks like. for podcast, indie podcast apps to

1023
01:10:04,329 --> 01:10:07,579
try to get some traction back and make these things

1024
01:10:07,579 --> 01:10:10,800
better. Because the other flip side to this is the

1025
01:10:10,800 --> 01:10:14,369
big apps, they're not doing very much either. Spotify's not

1026
01:10:14,369 --> 01:10:17,300
doing anything in that regard. And the beauty of us,

1027
01:10:17,739 --> 01:10:23,760
collectively, is that What we do with the podcast index

1028
01:10:23,760 --> 01:10:26,059
and how we tie into all of that, we do

1029
01:10:26,059 --> 01:10:30,029
for all apps. Apple can't do that. Well, I mean,

1030
01:10:30,029 --> 01:10:33,460
technically they can. They're not going to. They're always going

1031
01:10:33,460 --> 01:10:37,970
to promote their app. Always. Forever. They're always going to

1032
01:10:37,970 --> 01:10:42,239
promote Apple TV. Forever. That's their system. That's how they

1033
01:10:42,239 --> 01:10:46,279
live. So we can promote for everybody and make it

1034
01:10:46,279 --> 01:10:50,039
work for everybody and bring that a huge leap forward,

1035
01:10:50,039 --> 01:10:55,010
I think. But be careful because Apple is going to

1036
01:10:55,010 --> 01:10:58,260
tie in their local AI models to their devices, and

1037
01:10:58,260 --> 01:11:00,100
they're going to give it all kinds of priority, and

1038
01:11:00,100 --> 01:11:02,149
then we'll sue them for 10 years, and then we'll

1039
01:11:02,149 --> 01:11:05,449
get access to it. So you might as well hook

1040
01:11:05,449 --> 01:11:11,069
your people in now. I apologize up front. I'm sure

1041
01:11:11,069 --> 01:11:16,720
Sam is half a bottle in and boosting away. I

1042
01:11:16,720 --> 01:11:22,440
thought that if I upgraded my Start9 StartOS embassy server

1043
01:11:22,440 --> 01:11:26,690
to 4.0, which I was quite excited about because it

1044
01:11:26,690 --> 01:11:29,630
includes networking, I thought, well, I can do that in

1045
01:11:29,630 --> 01:11:32,399
the morning, which I did. I didn't realize that it

1046
01:11:32,399 --> 01:11:36,779
has to go through completely changing the entire file system.

1047
01:11:37,340 --> 01:11:40,460
And I'm just now booting up LND server, which is

1048
01:11:40,460 --> 01:11:44,329
taking quite a while. So I'm not getting any booster

1049
01:11:44,329 --> 01:11:49,130
grams of anything. Oh, well, I mean, I got our

1050
01:11:49,130 --> 01:11:51,600
I got I'll get as many boosts as I can.

1051
01:11:51,840 --> 01:11:56,039
OK. I don't know. Where's the stupid bus? It's a

1052
01:11:56,039 --> 01:11:59,970
USB cable somewhere near your mic cable. Something is near

1053
01:11:59,970 --> 01:12:04,399
your mic cable, and it sounds like USB. It never...

1054
01:12:04,399 --> 01:12:06,500
stays on long enough for me to actually trace it.

1055
01:12:06,559 --> 01:12:07,789
Because the minute you move... I get the roadcaster up

1056
01:12:07,789 --> 01:12:09,460
and wave it around in the air and it doesn't

1057
01:12:09,460 --> 01:12:13,819
change anything. No, it's something with your mic cable. Your

1058
01:12:13,819 --> 01:12:16,729
mic cable is running next to a dimmer or a

1059
01:12:16,729 --> 01:12:20,529
USB or LMNOP. It's doing... My mic cable is running

1060
01:12:20,529 --> 01:12:23,440
through every electronic. Yeah, well, there it is. There it

1061
01:12:23,440 --> 01:12:28,440
is. There's nothing it's not touching. Nailed it. I mean,

1062
01:12:28,440 --> 01:12:31,140
it is literally touching everything in this room, I think.

1063
01:12:35,220 --> 01:12:40,920
Open UI. Oh, okay. Did this work? Let me see.

1064
01:12:41,059 --> 01:12:46,800
Is my Albie hub back up? Oh, LND, not waiting

1065
01:12:46,800 --> 01:12:50,800
to start. RPC servers is not available yet. I got

1066
01:12:50,800 --> 01:12:55,899
you. Okay. Well, that sucks. Why is it taking L&D

1067
01:12:55,899 --> 01:13:00,199
so long to start up? Well, it's not the podcast

1068
01:13:00,199 --> 01:13:04,380
index node, so it should be quicker. Mm-hmm. I don't

1069
01:13:04,380 --> 01:13:09,760
know what it's doing. I have no idea. Why log?

1070
01:13:09,840 --> 01:13:13,420
Oh, logs. Whoa! Whoa! What do I see in here?

1071
01:13:14,039 --> 01:13:16,909
Waiting to start. RPC service is not available. Why is

1072
01:13:16,909 --> 01:13:21,569
it not available? Oh, it had to migrate the SQL

1073
01:13:21,569 --> 01:13:27,470
schema to version 1. Six? Oh my gosh. That sounds

1074
01:13:27,470 --> 01:13:33,520
fun. No, that sounds bad. That was very bad. Okay.

1075
01:13:34,840 --> 01:13:39,579
The... Have you heard... Have you heard the Dick and

1076
01:13:39,579 --> 01:13:43,300
Paul show? No, can't say that I have. It's pretty

1077
01:13:43,300 --> 01:13:46,890
good. The Dick and Paul show? Oh, man, this is

1078
01:13:46,890 --> 01:13:52,340
really bad, Dave. What am I doing? Okay. Let's see.

1079
01:13:53,340 --> 01:13:58,479
Okay. oh my gosh i got turned the i'm gonna

1080
01:13:58,479 --> 01:14:01,159
turn the noise gate off for this this is too

1081
01:14:01,159 --> 01:14:04,470
fun oh it went away don't move it's because i

1082
01:14:04,470 --> 01:14:08,760
muted myself so okay so now we know it's definitely

1083
01:14:08,760 --> 01:14:11,199
the mic it's the mic yeah so if i mute

1084
01:14:11,199 --> 01:14:20,440
myself it's the mic yeah of course Wait, is it?

1085
01:14:21,140 --> 01:14:25,079
Let me unplug the mic again. I'm plugging the mic.

1086
01:14:25,279 --> 01:14:33,619
Yeah. Well. What is going on? What is this happening?

1087
01:14:36,260 --> 01:14:40,500
Now it won't stop. And I'm blinding myself because the

1088
01:14:40,500 --> 01:14:44,140
lampshade fell off the lamp. Okay. Now it stopped again.

1089
01:14:44,659 --> 01:14:50,520
Oh, my gosh. Okay. Okay. Ah! We're off the rails!

1090
01:14:52,260 --> 01:14:57,819
Okay, alright. I'm back. The lamp kept self-destructing. I don't

1091
01:14:57,819 --> 01:14:59,940
know what's going on. Okay, I'll have to.

1092
01:15:00,699 --> 01:15:03,000
I'm going to have to reroute this mic cable or

1093
01:15:03,000 --> 01:15:05,699
something after the show. That's the problem. That's the problem.

1094
01:15:06,479 --> 01:15:09,279
The Dick and Paul show, do you remember Dick Costolo?

1095
01:15:10,699 --> 01:15:16,159
Yeah. The Twitter CEO. Oh, yes. Oh, yes, yes, yes.

1096
01:15:16,260 --> 01:15:18,920
After he was the first guy after Dorsey, wasn't he?

1097
01:15:19,399 --> 01:15:22,510
Yeah, that dude is funny. Oh, really? Yeah, so it's

1098
01:15:22,510 --> 01:15:25,920
him and this guy named Paul Kudrowski, who's an economist.

1099
01:15:26,979 --> 01:15:29,890
And the show is them just roasting people. stuff all

1100
01:15:29,890 --> 01:15:32,119
the time about Silicon Valley and that kind of thing.

1101
01:15:32,380 --> 01:15:34,880
It's worth a listen. Okay. I'd like to stick it

1102
01:15:34,880 --> 01:15:36,880
in our pod roll. I'll check this for a second.

1103
01:15:37,060 --> 01:15:38,460
I'd like to just cram that one right in the

1104
01:15:38,460 --> 01:15:40,869
old pod roll. Subscribe to the Dick and Paul Show

1105
01:15:40,869 --> 01:15:44,039
podcast. Boom, done. Didn't even have to think about it.

1106
01:15:44,119 --> 01:15:51,020
Sorry. Didn't have to search or anything. I, um, Let's

1107
01:15:51,020 --> 01:15:56,739
see. So I probably don't have much time left, but

1108
01:15:56,739 --> 01:16:01,890
– I think what I've been saying – so Christopher

1109
01:16:01,890 --> 01:16:06,710
Issen, the Swedish trickler, has been doing a lot of

1110
01:16:06,710 --> 01:16:14,779
curation work on the index. Yes. He is nuking feeds

1111
01:16:14,779 --> 01:16:17,199
at an astonishing rate. He is a good man. He

1112
01:16:17,199 --> 01:16:19,260
is a good man. Yes. He's doing the Lord's work

1113
01:16:19,260 --> 01:16:25,920
there. Yes. He has scripts doing all sorts of important

1114
01:16:25,920 --> 01:16:32,090
things. And so – I guess my question is, are

1115
01:16:32,090 --> 01:16:39,659
we doing enough? for the podcast ecosystem with this, with

1116
01:16:39,659 --> 01:16:44,640
how like we, we, I would like to let people

1117
01:16:44,640 --> 01:16:48,430
know because I sent a whole batch of feeds to

1118
01:16:48,430 --> 01:16:52,500
Podbean this week. I mean, these are just egregious spam

1119
01:16:52,500 --> 01:16:59,760
feeds. That were like, you know, just like full movie

1120
01:16:59,760 --> 01:17:05,039
downloads of Blu-ray. Yes. How is he? How is he?

1121
01:17:05,119 --> 01:17:06,819
Is he searching for those? Or how does he do

1122
01:17:06,819 --> 01:17:13,569
it? Is he watching the fire hose? I don't know.

1123
01:17:13,569 --> 01:17:15,920
I think he sent me. I have not checked my

1124
01:17:15,920 --> 01:17:18,359
signal yet, but I think he sent me some details.

1125
01:17:18,359 --> 01:17:20,149
I got to go check them. I'm going to check

1126
01:17:20,149 --> 01:17:22,920
the PP monitor. I'm still upright. I'm still on this

1127
01:17:22,920 --> 01:17:28,250
thing. Oh, yeah. Curry compound. I'm still. Yeah, I'm still

1128
01:17:28,250 --> 01:17:31,569
a participant. OK, good. Yeah, you're in the you're in

1129
01:17:31,569 --> 01:17:34,949
the mesh. Yeah. Warm embrace. I am. I'm moving around

1130
01:17:34,949 --> 01:17:38,439
in that mesh. Very cool. Well, I'm going to be.

1131
01:17:40,399 --> 01:17:43,119
I got news coming on the PP on the on

1132
01:17:43,119 --> 01:17:48,220
the pod, the pod ping front. Hopefully by the next

1133
01:17:48,220 --> 01:17:52,920
show, I will be... Publishing some different – some things

1134
01:17:52,920 --> 01:17:54,800
on a – it will not be on the main

1135
01:17:54,800 --> 01:17:58,119
Podping topic, a gossip topic, but it will be on

1136
01:17:58,119 --> 01:18:03,189
a side topic. So that you can, you'll be able

1137
01:18:03,189 --> 01:18:07,720
to subscribe to some stuff that is index specific. So

1138
01:18:07,720 --> 01:18:13,260
I will have more to reveal. Oh, revealing stuff. More

1139
01:18:13,260 --> 01:18:17,180
to come. I like it. I like it. Yep. So

1140
01:18:17,180 --> 01:18:23,229
that will be... Chad F. had a really... sweet post

1141
01:18:23,229 --> 01:18:27,220
on Twitter. Mastodon, he was like, you know, I wish

1142
01:18:27,220 --> 01:18:30,739
we could help Dave more. Um, it's coming, Chad. I'm

1143
01:18:30,739 --> 01:18:32,590
going to help. I don't want anybody to think of

1144
01:18:32,590 --> 01:18:37,189
this as helping me. It's more just, uh... A lot

1145
01:18:37,189 --> 01:18:40,010
of the things I'm doing right now are the building

1146
01:18:40,010 --> 01:18:43,260
blocks for how this will become the work that we

1147
01:18:43,260 --> 01:18:46,359
all do. So it's not going to be helping a

1148
01:18:46,359 --> 01:18:50,760
certain person or whatever. But I'm really grateful for the

1149
01:18:50,760 --> 01:18:55,699
people who do help, like Christopher and Chad and Eric

1150
01:18:55,699 --> 01:19:00,500
and David Marzal. Oh, he does a ton of stuff.

1151
01:19:00,659 --> 01:19:05,239
Nathan. I mean, just everybody who pitches in and does

1152
01:19:05,239 --> 01:19:12,359
things. I'm very appreciative for everybody. But hopefully what... In

1153
01:19:12,359 --> 01:19:15,289
the next few months, this will will be able to

1154
01:19:15,289 --> 01:19:18,439
put the stuff in place so that everybody can so

1155
01:19:18,439 --> 01:19:21,100
we can just all do this together. So we don't

1156
01:19:21,100 --> 01:19:23,899
have to like there won't be one person running the

1157
01:19:23,899 --> 01:19:26,439
whole ship and then everybody has to help that person

1158
01:19:26,439 --> 01:19:29,720
because we don't want that. Right. The case. Right. So

1159
01:19:29,720 --> 01:19:32,289
if we can distribute it. But I'll have I'll I'll

1160
01:19:32,289 --> 01:19:34,640
lay that out more next week. And but but in

1161
01:19:34,640 --> 01:19:37,819
the meantime, like and that the spam topic is part

1162
01:19:37,819 --> 01:19:40,560
of that is why I brought it up. I'd like

1163
01:19:40,560 --> 01:19:43,300
to push things. You know, Chris is doing all that

1164
01:19:43,300 --> 01:19:46,789
work. But then can we do more? I mean, is

1165
01:19:46,789 --> 01:19:49,899
there a way we can distribute this so that. Like,

1166
01:19:49,899 --> 01:19:52,630
can we get an efficient system for how to label

1167
01:19:52,630 --> 01:19:55,119
spam and then report that back to the hosting company?

1168
01:19:56,600 --> 01:20:01,079
I want everybody to be thinking about this because we

1169
01:20:01,079 --> 01:20:04,579
don't just care about podcast apps. We also care about

1170
01:20:04,579 --> 01:20:08,920
the podcast ecosystem as a whole. It doesn't help anybody

1171
01:20:08,920 --> 01:20:14,130
in the podcasting 2.0 or podcasting in general if Podbean

1172
01:20:14,130 --> 01:20:18,560
has 500 spam feeds on their system. Are they the

1173
01:20:18,560 --> 01:20:23,010
worst offender? No, no, not by any means. But it's

1174
01:20:23,010 --> 01:20:28,600
really spread. It's really equally spread across the whole system.

1175
01:20:29,300 --> 01:20:31,800
I just wonder if anybody has any bright ideas about

1176
01:20:31,800 --> 01:20:35,399
how we can make that – We have that information.

1177
01:20:35,560 --> 01:20:38,279
We see that it's spam. It takes us a while

1178
01:20:38,279 --> 01:20:43,770
to recognize it as such. But... You know, I don't

1179
01:20:43,770 --> 01:20:46,220
know, Eric, maybe you talk about like Jev or something

1180
01:20:46,220 --> 01:20:48,210
like that. I don't know if anybody wants to code

1181
01:20:48,210 --> 01:20:50,420
something like that up. Let's let's try to figure out.

1182
01:20:51,100 --> 01:20:53,149
Well, I can help. I'm going to have a lot

1183
01:20:53,149 --> 01:20:55,880
more time on my hands end of the month. You

1184
01:20:55,880 --> 01:20:57,659
want to say a quick you got anything to say

1185
01:20:57,659 --> 01:21:00,880
about that? I mean, like I heard I heard that

1186
01:21:00,880 --> 01:21:04,510
you were ending at the end of the month. 29th.

1187
01:21:04,510 --> 01:21:09,319
One show after the 19th anniversary. Okay. Yeah. End of

1188
01:21:09,319 --> 01:21:13,529
an era. end of an era i totally understand i

1189
01:21:13,529 --> 01:21:16,449
totally understand where you're coming from i mean if i

1190
01:21:16,449 --> 01:21:18,930
mean if something happened to you i mean i wouldn't

1191
01:21:18,930 --> 01:21:21,460
be doing this show with anybody else i mean the

1192
01:21:21,460 --> 01:21:24,369
show is the people oh if you're gone right away

1193
01:21:24,369 --> 01:21:27,680
i got eric pp in here in a heartbeat that

1194
01:21:27,680 --> 01:21:36,329
mother Are you still there? Yeah. Oh, I thought you

1195
01:21:36,329 --> 01:21:40,859
left. I got so angry I stormed out. Rage quit.

1196
01:21:41,619 --> 01:21:47,020
Yeah. Yeah, it was time. It's time. It makes sense.

1197
01:21:47,300 --> 01:21:50,430
Yeah. It makes sense. We got customers with needs now

1198
01:21:50,430 --> 01:21:55,090
at Godcaster. uh yeah we do yes we do they

1199
01:21:55,090 --> 01:21:59,060
got needs man i was like okay yeah i'm meeting

1200
01:21:59,060 --> 01:22:02,079
with people like they got needs okay we can do

1201
01:22:02,079 --> 01:22:05,369
that for you yeah one day one day we need

1202
01:22:05,369 --> 01:22:09,680
to like we build a lot of stuff in godcaster

1203
01:22:09,680 --> 01:22:13,380
that i think other people would be interested in and

1204
01:22:13,380 --> 01:22:16,920
uh That's really cool, but we never talk about it

1205
01:22:16,920 --> 01:22:19,380
here because it doesn't feel appropriate. But one day we

1206
01:22:19,380 --> 01:22:21,979
should just talk about it because I think people would

1207
01:22:21,979 --> 01:22:26,319
find it pretty neat. Like the fractional program director and

1208
01:22:26,319 --> 01:22:30,600
all that stuff. That stuff's cool, man. Yeah. It's going

1209
01:22:30,600 --> 01:22:35,149
to be interesting times. Paul's coming in town Sunday. He's

1210
01:22:35,149 --> 01:22:36,869
coming through Birmingham. Me and him are going to eat

1211
01:22:36,869 --> 01:22:41,520
some supper. Oh, that's cool. So I can't find... Oh,

1212
01:22:41,520 --> 01:22:44,539
I see. It's the what's the name of the show?

1213
01:22:44,539 --> 01:22:48,399
The Dick and Paul show. The Dick and Paul show.

1214
01:22:49,119 --> 01:22:52,970
Dick Costolo said that he... He had to name it

1215
01:22:52,970 --> 01:22:57,739
something different on YouTube because YouTube rejected his name. Because

1216
01:22:57,739 --> 01:23:02,350
I had just yelled at the robot and said, and

1217
01:23:02,350 --> 01:23:06,460
it transmorgified it to subscribe to the Deacon Paul show.

1218
01:23:06,460 --> 01:23:09,060
I'm like, no, no. I'm like, what is this? So

1219
01:23:09,060 --> 01:23:13,020
now it's hearing me differently. Oh, no. It's Curry yelling

1220
01:23:13,020 --> 01:23:15,720
at me. What kind of religious language is he using?

1221
01:23:15,899 --> 01:23:21,289
Dick must be deacon. This, by the way, this Liquid

1222
01:23:21,289 --> 01:23:27,350
Studios thing... This is the dumbest thing. Well, this is

1223
01:23:27,350 --> 01:23:30,020
the stuff that you can do at home. I mean,

1224
01:23:30,020 --> 01:23:34,489
please. Yeah, okay, I got it. I'm not believing for

1225
01:23:34,489 --> 01:23:39,119
one second. Did they build that entire Inception Point AI

1226
01:23:39,119 --> 01:23:42,350
just as a proof of concept to really go and

1227
01:23:42,350 --> 01:23:46,430
build a video converter? No. Give me a break. No,

1228
01:23:46,430 --> 01:23:49,000
not at all. This is a VC pivot is what

1229
01:23:49,000 --> 01:23:52,420
this is if I've ever seen one. Big time. Yeah.

1230
01:23:53,340 --> 01:23:57,470
Whatever. Yeah, I don't care. That's exactly the kind of

1231
01:23:57,470 --> 01:24:00,840
stuff. You can say, oh, turn this podcast into video

1232
01:24:00,840 --> 01:24:03,800
and just assemble some stuff. My thing here at home

1233
01:24:03,800 --> 01:24:08,190
will do it, run it on the Asus. Okay. I

1234
01:24:08,190 --> 01:24:12,279
promise you we built 25,000 synthetic feeds on Spreaker getting

1235
01:24:12,279 --> 01:24:15,890
ad revenue, but it really wasn't the point. No, it

1236
01:24:15,890 --> 01:24:17,500
was – We really just wanted to build a video

1237
01:24:17,500 --> 01:24:21,250
converter. So now we can have a video version of

1238
01:24:21,250 --> 01:24:26,020
PodNews. Yeah, sure. Yeah. Which, of course – Blow that

1239
01:24:26,020 --> 01:24:29,869
smoke somewhere else. Nobody watches. We need to thank some

1240
01:24:29,869 --> 01:24:33,100
people. Is it that time already? What time are we?

1241
01:24:33,140 --> 01:24:35,539
Oh, my goodness. Yes. Well, I have nothing. I have.

1242
01:24:35,800 --> 01:24:38,750
I'm sorry. I'm looking at. Let me take a look

1243
01:24:38,750 --> 01:24:42,859
at my where I'm at right now. Oh, OK. So

1244
01:24:42,859 --> 01:24:47,159
L&D is running. Mm hmm. But of course, I lost

1245
01:24:47,159 --> 01:24:51,180
all my channels because it was down so long. And

1246
01:24:51,180 --> 01:24:59,140
AlbiHub is running. That's good. Hold on. and helipad is

1247
01:24:59,140 --> 01:25:01,109
running i think hold on let me just check for

1248
01:25:01,109 --> 01:25:03,940
a second do i have any channels left there's my

1249
01:25:03,940 --> 01:25:08,420
channels let me channel wallet node node yes no i

1250
01:25:08,420 --> 01:25:11,149
got a pew pew i got a node pew pew

1251
01:25:11,149 --> 01:25:17,010
pew came back amazing So you're back in business. Who

1252
01:25:17,010 --> 01:25:22,600
runs Pew Pew? Who runs Pew Pew Pew? I think

1253
01:25:22,600 --> 01:25:25,720
it is. Well, thank you very much. I mean, that

1254
01:25:25,720 --> 01:25:29,309
thing came back. That's astounding. Now let me take a

1255
01:25:29,309 --> 01:25:37,340
helipad. Task required. What? Set reset password. Okay, hold on.

1256
01:25:38,399 --> 01:25:44,970
Uh... Oh, brother. Okay, I'll need that password really to

1257
01:25:44,970 --> 01:25:50,619
log into Helipad. Okay, let's see if I got it.

1258
01:25:50,699 --> 01:25:52,979
Maybe I got something in. Maybe it worked. Hold on.

1259
01:25:53,059 --> 01:25:56,350
Let's check it. Check it. I'm checking it. Here we

1260
01:25:56,350 --> 01:25:59,779
go. Password. Stay logged in for 30 days, which we

1261
01:25:59,779 --> 01:26:07,380
know never works. Now I'm. Ooh. But it's somehow it's

1262
01:26:07,380 --> 01:26:09,989
oh, there we go. Oh, is it going to now

1263
01:26:09,989 --> 01:26:13,390
fill up the I literally am getting 29th of May,

1264
01:26:13,390 --> 01:26:16,930
30th of May. Oh, bro. This is going to pew

1265
01:26:16,930 --> 01:26:20,750
all the way through to October. Now, are you just

1266
01:26:20,750 --> 01:26:23,359
going to get a machine gun of pew? That's that's

1267
01:26:23,359 --> 01:26:26,050
exactly what's happening. I don't hear any sound for some

1268
01:26:26,050 --> 01:26:29,350
reason, but. Yeah, it's now it's it's now it's a

1269
01:26:29,350 --> 01:26:34,140
June. Oh, June 2023. Okay, well, we'll let that Lord,

1270
01:26:34,140 --> 01:26:38,029
we'll let that sit for I guess it didn't migrate

1271
01:26:38,029 --> 01:26:42,690
the, I don't know, helipad, air PP, what is repopulating?

1272
01:26:42,690 --> 01:26:47,100
Yeah, that'll take quite a while for that to repopulate.

1273
01:26:47,300 --> 01:26:51,800
All right. You got to read them, Dave. I'm just

1274
01:26:51,800 --> 01:26:54,510
trying to get my buzz to go. No, the buzz

1275
01:26:54,510 --> 01:26:56,520
is, you know what? We're just going to live with

1276
01:26:56,520 --> 01:26:59,220
the buzz. We're just going to love the buzz. Wait,

1277
01:26:59,220 --> 01:27:02,399
maybe I found it. I may have found it. No.

1278
01:27:03,500 --> 01:27:05,710
I know you still hear it, but it's much less

1279
01:27:05,710 --> 01:27:08,460
than it was. No. It was blowing your head off.

1280
01:27:09,220 --> 01:27:12,619
No, it's pretty much the same. No, well, I could

1281
01:27:12,619 --> 01:27:15,640
hear it, but I don't know. It's back. Okay, all

1282
01:27:15,640 --> 01:27:17,720
right. I'm going to reroute the cable, I promise. Oh,

1283
01:27:17,720 --> 01:27:21,829
it's okay. It's fine. I'm happy. Let's see. What am

1284
01:27:21,829 --> 01:27:25,260
I doing? Oh, yeah. Oh, PayPal. Yeah, okay. PayPal. PayPal.

1285
01:27:26,539 --> 01:27:30,079
We got Timothy Voice, $10. Thank you, Timothy. Thanks, Timothy.

1286
01:27:30,079 --> 01:27:36,210
Michael Hall, $5.50. Gene Liverman, $5. Thank you, Gene. Todd

1287
01:27:36,210 --> 01:27:42,710
Cochran, straight from heaven, $30. Thank you, Todd. Jeremy Gerds,

1288
01:27:42,710 --> 01:27:48,010
$5. Derek J. Visker, $21. Thank you. Best name in

1289
01:27:48,010 --> 01:27:54,640
podcasting. Paul Saltzman, $22.22. Thank you, Paul. Silicon Florist, $10.

1290
01:27:54,960 --> 01:28:01,319
Thank you. Christopher Cowan, Thanks, Chris. $5. Terry Keller, $5.

1291
01:28:01,319 --> 01:28:08,319
Damon Kasajak, $15. And Chris Riedel, $5. $20. Thank you.

1292
01:28:08,420 --> 01:28:11,239
Thank you all very much. This makes a difference. You

1293
01:28:11,239 --> 01:28:15,979
keep machines running with that. Now that we've integrated our

1294
01:28:15,979 --> 01:28:20,930
Linodes, like I'm an admin on yours, you're an admin

1295
01:28:20,930 --> 01:28:23,940
on mine, which is why we get all those emails.

1296
01:28:25,159 --> 01:28:27,550
So the other day I was... I was looking in

1297
01:28:27,550 --> 01:28:31,100
a different email box. I'm like, holy crap. Why do

1298
01:28:31,100 --> 01:28:37,529
I have to pay $800 to Linode? Okay. surprise like

1299
01:28:37,529 --> 01:28:41,510
what is going on what happened i'm sweating i'm like

1300
01:28:41,510 --> 01:28:44,760
where does this come from something's going awry my agent

1301
01:28:44,760 --> 01:28:47,399
has set up something i don't know what's going on

1302
01:28:47,399 --> 01:28:52,440
you've pushed 400 terabytes of data this month oh it's

1303
01:28:52,440 --> 01:28:57,319
podcast index oh okay Got it. What is our spend

1304
01:28:57,319 --> 01:28:59,289
right now? I think it's about, it's close to nine,

1305
01:28:59,289 --> 01:29:03,069
right? It's up there, yeah. Yeah, it's a lot. And

1306
01:29:03,069 --> 01:29:07,859
that's without, you know, the podcast index.social is 200 something.

1307
01:29:09,300 --> 01:29:14,520
Is it $200 now? Yeah. Well, unless you want me

1308
01:29:14,520 --> 01:29:20,500
to start deleting the database, you're paying for database and

1309
01:29:20,500 --> 01:29:24,220
for searchability. People do like to search, and otherwise old

1310
01:29:24,220 --> 01:29:28,829
messages go away. Is that a big deal? I mean,

1311
01:29:28,829 --> 01:29:33,220
how old? That just seems like a lot of money

1312
01:29:33,220 --> 01:29:38,079
to pay for a month. Well, we can have a

1313
01:29:38,079 --> 01:29:45,390
meeting. Okay. I mean, $200? Yikes. And you're paying for

1314
01:29:45,390 --> 01:29:47,659
that out of your own pocket? No, no, no. We

1315
01:29:47,659 --> 01:29:51,720
switched that. We switched that. Okay. We switched it. I

1316
01:29:51,720 --> 01:29:58,059
feel like we could bring that down. Well, you know...

1317
01:29:58,359 --> 01:29:59,960
It all depends on how many

1318
01:30:00,000 --> 01:30:03,140
what kind of history you want to keep. I mean,

1319
01:30:03,140 --> 01:30:10,720
I don't feel like... You're preserving... something for future generations

1320
01:30:10,720 --> 01:30:14,399
to see how this stuff came about. It's not yet

1321
01:30:14,399 --> 01:30:18,310
on GitHub. Does that even matter? Because people are going

1322
01:30:18,310 --> 01:30:22,029
to make it up anyway. Because the history of how

1323
01:30:22,029 --> 01:30:26,010
podcasting came about is perfectly preserved. But people say Adam

1324
01:30:26,010 --> 01:30:30,239
Carolla did it. Yeah. Well, where is it perfectly preserved?

1325
01:30:31,500 --> 01:30:36,789
On scripting.com or something. Yeah, exactly. He only has no

1326
01:30:36,789 --> 01:30:41,380
HTTPS, so he's no longer future-proof. No one can see

1327
01:30:41,380 --> 01:30:45,449
the history. Yeah, it's perfectly preserved for people who use

1328
01:30:45,449 --> 01:30:49,239
the Lynx browser in the terminal. Oh, yeah, there's Daniel

1329
01:30:49,239 --> 01:30:51,760
J. Lewis. Yeah, we'll move to Slack. There you go.

1330
01:30:52,020 --> 01:30:58,500
No. Discord. Discord. No, I think podcast index.social is part

1331
01:30:58,500 --> 01:31:01,239
of the success. It's part of the formula. It's been

1332
01:31:01,239 --> 01:31:05,039
fantastic. Anyway, it was stuff to talk about. Stuff to

1333
01:31:05,039 --> 01:31:08,180
talk about. Yeah, we'll have to have a meeting. True

1334
01:31:08,180 --> 01:31:13,439
Fans Anonymous stuff, 39 sats, 406 sats, 13 sats, 220

1335
01:31:13,439 --> 01:31:18,449
sats, 7 sats, 406, 13. Thank you, True Fans Anonymous

1336
01:31:18,449 --> 01:31:24,409
people. Drev Scott, 774 sats. He says... Anyone else notice

1337
01:31:24,409 --> 01:31:28,140
the Podfriend V3 test flight drop this week? Oh, I

1338
01:31:28,140 --> 01:31:32,439
don't have the test flight. I don't have Apple stuff.

1339
01:31:34,220 --> 01:31:40,170
Boost. I'm checking. I'm checking to see if I have

1340
01:31:40,170 --> 01:31:44,850
it. Test. I've got too many things in TestFlight. I

1341
01:31:44,850 --> 01:31:49,140
got Buzzsprout stuff. I got Godcaster stuff. I got I'm

1342
01:31:49,140 --> 01:31:52,899
off the chain. Got a podcast guru. I got Overcast,

1343
01:31:52,899 --> 01:31:57,159
Castomatic. Oh, there it is. Podfriend. Yes. V3, V3, V3.

1344
01:31:57,760 --> 01:32:00,100
All right. I'm checking it out. Yep. I got V3.

1345
01:32:01,560 --> 01:32:03,779
Let's see. What is what is old Martin say? Okay.

1346
01:32:05,289 --> 01:32:08,949
Cross device resume playback position from another device is no

1347
01:32:08,949 --> 01:32:14,079
longer dropped. New episode notifications podcast with two RSS sources

1348
01:32:14,079 --> 01:32:17,600
now merge. Don't know what that means. Search is more

1349
01:32:17,600 --> 01:32:21,640
resilient when the podcast director is rate limiting and podcast

1350
01:32:21,640 --> 01:32:25,960
owners duplicate listings now hide. All right. I'll give it

1351
01:32:25,960 --> 01:32:33,319
a shot. Jody at Fountain.fm. 3,154 sats. Thank you, Jody.

1352
01:32:34,220 --> 01:32:36,180
Jody says, Dave, that was a good interview on Pod

1353
01:32:36,180 --> 01:32:39,899
News Weekly Review. I'm looking forward to hearing more future

1354
01:32:39,899 --> 01:32:42,550
plans for community replication of the index. Here's a little

1355
01:32:42,550 --> 01:32:45,590
value as I empty out my fountain wallet. Well... It's

1356
01:32:45,590 --> 01:32:47,920
good timing because we'll be talking about that hopefully in

1357
01:32:47,920 --> 01:32:53,880
the next few weeks. Yay. Chad F. Hey, Chad, 185

1358
01:32:53,880 --> 01:32:58,359
sets. He says, this show's lost the plot. What was

1359
01:32:58,359 --> 01:33:03,130
the plot? We had no plot. I'm at June 2023

1360
01:33:03,130 --> 01:33:08,819
on Helipat. Yeah, you got a few years ago. Helipat.

1361
01:33:08,920 --> 01:33:13,380
Forever. We need a fast forward in Helipad. I do

1362
01:33:13,380 --> 01:33:19,289
like the new Start OS. It's pretty good. Now they

1363
01:33:19,289 --> 01:33:22,920
built in wire guard and everything, so you don't have

1364
01:33:22,920 --> 01:33:27,800
to be reliant on Tor. Oh, tail scale. No, it's

1365
01:33:27,800 --> 01:33:32,829
WireGuard. So not tail scale. I thought WireGuard was the

1366
01:33:32,829 --> 01:33:36,340
tail scale used. It's not tail scale. It's WireGuard. Yeah.

1367
01:33:36,420 --> 01:33:39,859
So tail scale uses WireGuard. This is WireGuard, I think.

1368
01:33:39,979 --> 01:33:44,449
Yeah. Yeah. I've heard that head scale is good, but

1369
01:33:44,449 --> 01:33:48,079
I have not tried it. Mm-hmm. It's like a self-hosted

1370
01:33:48,079 --> 01:33:52,319
tail scale. Let me see. Oh, yeah, I have. Because

1371
01:33:52,319 --> 01:33:54,449
it gives you access control lists and that kind of

1372
01:33:54,449 --> 01:33:58,569
thing that overlay on the wire guard. Mm-hmm. Yeah. Well,

1373
01:33:58,569 --> 01:34:02,449
yeah, Tailscale has a lot of extra, extra ditties. Use

1374
01:34:02,449 --> 01:34:09,760
gateway. Ditties. Duties. Extra ditties. Extra ditties and duties. Chat

1375
01:34:09,760 --> 01:34:13,579
F, 185 sats, giving AlbiHub a boost budget is cool,

1376
01:34:13,579 --> 01:34:17,020
but not everyone can afford to run AlbiHub. It's true.

1377
01:34:17,119 --> 01:34:18,979
It's free though, right? Can't you run it free? But

1378
01:34:18,979 --> 01:34:23,100
you got to run it on a machine. Normal people.

1379
01:34:23,239 --> 01:34:26,579
Normal people can't run it, Dave. Normal people can't run

1380
01:34:26,579 --> 01:34:29,859
it. Normal people. Chad F has machines. He's got lots

1381
01:34:29,859 --> 01:34:33,779
of machines. Chad F, 185, says all hell is going

1382
01:34:33,779 --> 01:34:35,239
to break loose and you're going to need an Albie

1383
01:34:35,239 --> 01:34:41,260
hug. Where is that? Manning Bitcoin. That's what it is.

1384
01:34:41,319 --> 01:34:45,100
Here we go. Here we go. They're saying that all

1385
01:34:45,100 --> 01:34:47,670
hell is gonna break loose and you're gonna need a

1386
01:34:47,670 --> 01:34:53,789
Bitcoin. Yeah. What are you going to do with all

1387
01:34:53,789 --> 01:34:57,289
those jingles after October? No, I'm going to use them

1388
01:34:57,289 --> 01:34:58,939
for this show. What do you mean? This show is

1389
01:34:58,939 --> 01:35:01,640
continuing. I've got plenty of stuff to use it for.

1390
01:35:01,760 --> 01:35:05,539
It's great. It's 185 sass again from Chad. He says,

1391
01:35:05,539 --> 01:35:09,319
send in boosts with Albie isn't anything new. Okay. Okay.

1392
01:35:09,960 --> 01:35:12,750
I'm not sure what reference that was to you. Just

1393
01:35:12,750 --> 01:35:17,399
so you know. Okay. Just letting everybody know. Chad F185,

1394
01:35:17,399 --> 01:35:21,880
he says, I stand with CSB++. Okay. We all stand

1395
01:35:21,880 --> 01:35:25,100
with CSB. Yeah, all the time. Mm-hmm. And guess what?

1396
01:35:25,100 --> 01:35:29,399
We got a commentary blogger, 10,556 sats. There he is.

1397
01:35:29,439 --> 01:35:33,560
Through Fountain. He says, howdy, Adam and Dave. Today I

1398
01:35:33,560 --> 01:35:40,640
recommend a podcast, Unrelenting, from www.unrelenting.show, by Gene, who has

1399
01:35:40,640 --> 01:35:44,460
an IQ of 187, and by Darren, who is much

1400
01:35:44,460 --> 01:35:48,560
taller than Adam. It's a great podcast. Just jibber jabber

1401
01:35:48,560 --> 01:35:52,880
about health, tech and life. No clips. Yo, CSB, Ozempic

1402
01:35:52,880 --> 01:35:56,989
Taker. P.S. This gram was worth when sent $15.59 equals

1403
01:35:56,989 --> 01:36:03,350
19,000 satoshis. Thank you, comics or blogger. And he alerted

1404
01:36:03,350 --> 01:36:07,260
me to the fact. So I figured out that. or

1405
01:36:07,260 --> 01:36:10,520
my robot. I unleashed the robot on my start nine.

1406
01:36:10,640 --> 01:36:14,140
Like, why is my torque failing? And it says, well,

1407
01:36:14,140 --> 01:36:17,460
I see here in the log that, you know, this

1408
01:36:17,460 --> 01:36:21,239
version, it literally says this version will soon stop working.

1409
01:36:21,239 --> 01:36:27,810
Right. okay and that's what happened so stop working so

1410
01:36:27,810 --> 01:36:30,500
now i should be okay i should be okay okay

1411
01:36:30,500 --> 01:36:35,729
for the A few hours before next Friday, Helipad will

1412
01:36:35,729 --> 01:36:39,789
have repropagated everything up to 2026. It'll be fun to

1413
01:36:39,789 --> 01:36:44,720
watch. Maybe. You're really sticking your neck out on that.

1414
01:36:44,779 --> 01:36:47,300
Eric PP, do I have to keep Helipad open now?

1415
01:36:47,899 --> 01:36:50,289
Do I have to keep the interface up, or will

1416
01:36:50,289 --> 01:36:54,180
that work in the background? Do I need to keep

1417
01:36:54,180 --> 01:36:57,470
the browser window open? You know, honestly, it's amazing that

1418
01:36:57,470 --> 01:37:01,010
it even does that. Oh, it's phenomenal. I mean. Going

1419
01:37:01,010 --> 01:37:05,220
back that far? Well, that's the whole L&D database. It's

1420
01:37:05,220 --> 01:37:08,319
reparsing it all. That's really cool. I think it's phenomenal.

1421
01:37:08,560 --> 01:37:11,460
Yeah. It's just it's not very fast because right now

1422
01:37:11,460 --> 01:37:15,939
we are at. Yeah. Let me see. Oops. I didn't

1423
01:37:15,939 --> 01:37:20,020
mean to do that. Helipad. Open up the helipads. We

1424
01:37:20,020 --> 01:37:26,800
are at June, 15th of June, 2023. Let me go

1425
01:37:26,800 --> 01:37:31,460
look real quick. He says it'll run in the background.

1426
01:37:31,460 --> 01:37:35,350
Cool. Okay. Thank you. Let me see how big the

1427
01:37:35,350 --> 01:37:41,220
podcast index node database was. Oh, that thing was probably

1428
01:37:41,220 --> 01:37:46,869
600 gigabytes or some massive number like that. Trying to

1429
01:37:46,869 --> 01:37:50,069
see us. Of course, I saved it in case we

1430
01:37:50,069 --> 01:37:54,539
ever needed it for tax stuff. I want to I

1431
01:37:54,539 --> 01:37:56,569
can't really look at it right now, but I think

1432
01:37:56,569 --> 01:37:59,850
I want to say it was like 60 gigs. Oh,

1433
01:37:59,850 --> 01:38:04,029
no, that's not that big then. But it's 60 gigs

1434
01:38:04,029 --> 01:38:08,939
of a B-Bolt database. That's a big B-Bolt database. That's

1435
01:38:08,939 --> 01:38:12,369
great. A 60 gig MySQL database is nothing, but that

1436
01:38:12,369 --> 01:38:15,180
thing was not in the good format. It's like a

1437
01:38:15,180 --> 01:38:18,319
60 gig Fox Pro database. You're like, you don't want

1438
01:38:18,319 --> 01:38:23,920
to touch that thing. Amazing. Lightning message board. What is

1439
01:38:23,920 --> 01:38:29,420
that? Was that it, Dave? That's all I got, man.

1440
01:38:29,600 --> 01:38:32,869
Okay. Well, thank you all very much. Remember, the podcast

1441
01:38:32,869 --> 01:38:36,940
index runs by your grace. Go to podcast. It was

1442
01:38:36,940 --> 01:38:41,059
CSB says, damn, $200 a month for this Fediverse instance.

1443
01:38:41,180 --> 01:38:45,800
Let's keep no history. Delete it all. Okay. That's fine.

1444
01:38:46,319 --> 01:38:50,399
It'll still do it. Okay. Torch it. You know, I

1445
01:38:50,399 --> 01:38:54,039
upgraded first and foremost because people want, I can't search.

1446
01:38:54,600 --> 01:38:57,869
I can't search. That's how it works. You got to

1447
01:38:57,869 --> 01:39:01,440
upgrade to another tier just to get search. I say

1448
01:39:01,440 --> 01:39:06,090
we downgrade that thing. Okay. I'll take a look. I'll

1449
01:39:06,090 --> 01:39:08,800
see what the options are. I mean, it's our tool,

1450
01:39:08,800 --> 01:39:13,949
man. It's our tool. Sometimes you have to adjust your

1451
01:39:13,949 --> 01:39:18,109
tool. Well, on that note, everybody, I'm going to go

1452
01:39:18,109 --> 01:39:21,979
adjust my tool. I suggest you all do the same.

1453
01:39:22,059 --> 01:39:25,239
We'll be back next week on Friday with more Podcasting

1454
01:39:25,239 --> 01:39:40,069
2.0. We'll be right back. Thank you. I think they're

1455
01:39:40,069 --> 01:39:47,699
cool. You have been listening to Podcasting 2.0. Visit podcastindex.org

1456
01:39:47,699 --> 01:39:53,539
for more information. Go podcasting! We're off the rails!