Episode 266: Research Velocity

1
00:00:00,540 --> 00:00:12,748
Podcasting 2.0 for July. Hello everybody, hello everybody in podcasting

2
00:00:12,808 --> 00:00:18,071
land. Well, only the future of podcasting. Yeah, that's right.

3
00:00:18,492 --> 00:00:20,473
This is the board meeting, the place where it all

4
00:00:20,553 --> 00:00:24,175
goes down, where this band of misfits gets together to

5
00:00:24,256 --> 00:00:26,977
discuss it all. We are the only board meeting you

6
00:00:27,037 --> 00:00:29,919
can attend with your eyes closed. I'm Adam Curry, here

7
00:00:29,939 --> 00:00:31,861
in the heart of the Texas Hill Country and in

8
00:00:31,981 --> 00:00:34,582
Alabama, the man who can tell you exactly why the

9
00:00:34,602 --> 00:00:37,284
Roman Empire fell. Say hello to my friend on the

10
00:00:37,384 --> 00:00:52,134
other end, the one, the only, Mr. Dane. Any anything

11
00:00:52,174 --> 00:00:55,096
happening in your world? Nah, not much going on. Yes,

12
00:00:55,216 --> 00:00:58,278
it seems a little slow. It's been a slow week.

13
00:00:59,259 --> 00:01:08,305
Yeah, you just kind of Yeah, nothing. Oh yeah, that's

14
00:01:08,345 --> 00:01:10,566
right. I don't want anyone who I know to die

15
00:01:10,586 --> 00:01:20,793
this week. Wow. So, um, six hours of podcast. How,

16
00:01:21,193 --> 00:01:23,155
how much do you even have in the tank today?

17
00:01:23,355 --> 00:01:25,556
No, I, I got, I got a tank, but, uh,

18
00:01:29,159 --> 00:01:31,260
I would say. You know, that mode where you're just

19
00:01:31,320 --> 00:01:37,404
like, I'm running in crisis mode. Can I? Sort of

20
00:01:38,004 --> 00:01:42,187
take the wheel for a second. I would like to

21
00:01:43,428 --> 00:01:46,450
just ask you if you're okay with this. I would

22
00:01:46,470 --> 00:01:50,913
like to ask you some questions that I think you

23
00:01:51,233 --> 00:01:58,058
can answer. would be helpful for people who might be

24
00:01:58,318 --> 00:02:08,485
in your same space. And so you, your co-host of

25
00:02:08,585 --> 00:02:20,212
No Agenda, because there's... agenda. There's me. That's true. You're

26
00:02:20,212 --> 00:02:22,874
in the Venn diagram. You're the one where it all

27
00:02:22,994 --> 00:02:26,817
over. You're the center. I'm there. I'm there. Yeah. You

28
00:02:26,897 --> 00:02:33,782
and Cotton Gin. And so the, the, you know, some

29
00:02:33,822 --> 00:02:38,445
people may not know who are not listening to Nojana

30
00:02:38,605 --> 00:02:43,128
and you're, so you're a long time co-host for 18

31
00:02:43,188 --> 00:02:56,537
years. Is that right? Yeah. in October. for any for

32
00:02:57,077 --> 00:03:02,981
a substantial And for any show. So there's a few

33
00:03:03,041 --> 00:03:06,663
questions I want to ask about this because if any,

34
00:03:06,723 --> 00:03:12,087
for any, like. Number one, a little bit of selfish

35
00:03:12,467 --> 00:03:20,012
concern for you that I have. No agenda is your

36
00:03:20,052 --> 00:03:23,334
main source of income. Yes. I need to ask you,

37
00:03:23,434 --> 00:03:28,378
are you going to be okay? I don't know. Honestly,

38
00:03:28,498 --> 00:03:32,420
I don't know. I appreciate the question. Would we be

39
00:03:32,561 --> 00:03:39,665
okay for a year without income? be it. So it's

40
00:03:39,725 --> 00:03:46,730
not preferred. I mean, up and down income is the

41
00:03:46,830 --> 00:03:51,453
life of any sort of freelance person, whether it's a

42
00:03:52,574 --> 00:03:55,956
contractor or a freelance artist or any type of person

43
00:03:55,976 --> 00:03:58,378
who does freelance. I mean, you're not, well, you don't

44
00:03:58,418 --> 00:04:03,761
have a guaranteed paycheck. So for, and again, I'm kind

45
00:04:03,781 --> 00:04:07,203
of asking this question as if I'm another person out

46
00:04:07,264 --> 00:04:23,975
there who also, may have your next steps are. Good

47
00:04:24,075 --> 00:04:35,963
questions, the questions I've been asking myself. No, no, no.

48
00:04:38,744 --> 00:04:43,367
Uh, well there's a couple th- The main issue I

49
00:04:43,648 --> 00:04:48,351
just want to put the money aside because I've never

50
00:04:48,411 --> 00:04:59,158
really worked for money. And it shows. He does. So

51
00:04:59,158 --> 00:05:10,065
what's interesting... but ours in particular. in my opening of

52
00:05:10,125 --> 00:05:18,251
our tribute show, which will... have their say, so we

53
00:05:18,691 --> 00:05:21,893
just said, put it in your donation note. We read

54
00:05:22,013 --> 00:05:26,856
753 notes yesterday. That's why it was... Oh my goodness,

55
00:05:26,856 --> 00:05:29,918
that is so much. But it was beautiful, of course.

56
00:05:31,159 --> 00:05:33,941
thing that struck me as an aside is the number

57
00:05:34,081 --> 00:05:38,364
of faithful people Not just people sending thoughts and prayers,

58
00:05:38,404 --> 00:05:42,447
but like real people. was kind of blew me away.

59
00:05:46,489 --> 00:05:51,953
Yeah, we... But it was a performance. We always said

60
00:05:51,993 --> 00:05:58,097
this. It was a performance between And... I think we

61
00:05:58,217 --> 00:06:01,759
both the other guy laughs. to say, hey, look at

62
00:06:01,819 --> 00:06:05,482
me, I got something, look at this theory I have,

63
00:06:05,562 --> 00:06:08,484
or look at these things I've found, clip of the

64
00:06:08,524 --> 00:06:12,667
day, that kind of stuff. So that's a chemical. that

65
00:06:12,787 --> 00:06:15,809
we didn't even start until we had been talking on

66
00:06:15,929 --> 00:06:20,492
Skype 18 years ago for weeks. You know, hey, we

67
00:06:20,512 --> 00:06:23,474
should probably record this. That's literally how it got started.

68
00:06:25,095 --> 00:06:35,021
So very much like... talking for years podcast. Do we

69
00:06:35,122 --> 00:06:37,723
get to do this with Pastor Jimmy? We're now 42

70
00:06:37,843 --> 00:06:40,685
episodes in. So, you know, I'm not a solo guy.

71
00:06:45,388 --> 00:06:50,832
can't just plug someone in and oh okay now So,

72
00:06:52,253 --> 00:06:56,936
and also, I don't think that, I don't know if

73
00:06:56,996 --> 00:07:06,322
that would work. Right. And honestly, I'm also very tired.

74
00:07:14,588 --> 00:07:20,992
you I think propping him up, dragging him along a

75
00:07:21,032 --> 00:07:25,775
little bit, which was completely understandable. Also, you know, not...

76
00:07:27,696 --> 00:07:29,257
a big secret I was supposed to keep, but he

77
00:07:29,298 --> 00:07:33,440
was 80 years old, not 74. He was a little

78
00:07:33,540 --> 00:07:39,524
older, not that that's a death sentence for most. You

79
00:07:39,564 --> 00:07:43,007
know, and just, you know, what's happening, what's going on,

80
00:07:43,067 --> 00:07:46,049
concern for him. You know, two families have been living

81
00:07:46,169 --> 00:07:49,551
off of this show, in essence, for all this time.

82
00:07:50,852 --> 00:07:56,656
So I really don't know what's going to happen or

83
00:07:56,956 --> 00:07:59,898
what I'm going to do. Honestly, I think I need

84
00:08:00,218 --> 00:08:04,861
just a week or two of rest. I don't think

85
00:08:04,861 --> 00:08:08,303
his passing is going to be a good thing. you

86
00:08:08,383 --> 00:08:12,526
get the call on Monday. There's, you know, what are

87
00:08:12,546 --> 00:08:20,552
we going to do? Consoling. um with his family. It

88
00:08:21,012 --> 00:08:28,657
affected me. And Processed it yet. And. I'm like, I

89
00:08:28,657 --> 00:08:31,079
haven't really quite wrapped my head around it, but yes,

90
00:08:31,639 --> 00:08:34,921
I do have to figure something out for sure. What

91
00:08:34,941 --> 00:08:38,563
that is, I just don't know. And do I really

92
00:08:38,604 --> 00:08:43,327
want... with someone else, I don't think it would be

93
00:08:43,347 --> 00:08:45,888
the same. And it would, I think it would feel

94
00:08:46,028 --> 00:08:50,451
fake to me. Does that make sense? Mm-hmm. Yeah, it

95
00:08:50,491 --> 00:08:58,677
does make sense. And it melts it. Like, sometimes I

96
00:08:58,797 --> 00:09:03,700
think when you're in a situation like this where somebody

97
00:09:04,441 --> 00:09:10,525
passes away, but you also have lost. Thank you. of

98
00:09:10,925 --> 00:09:15,188
uh orbit around that person even even a spouse or

99
00:09:15,228 --> 00:09:21,672
something like that you they're passing your grief connected to

100
00:09:21,732 --> 00:09:25,735
their passing gets pushed to the side for a while.

101
00:09:26,715 --> 00:09:29,417
You just have to take care of a lot of

102
00:09:29,457 --> 00:09:31,939
things. You have to take care of, you know, if

103
00:09:31,979 --> 00:09:34,000
you're the family. the funeral and you have to take

104
00:09:34,000 --> 00:09:36,922
care of all those things if you're you know somebody

105
00:09:36,942 --> 00:09:39,784
who's a business partner or a long time friend or

106
00:09:40,625 --> 00:09:44,487
you have other responsibilities you're gonna have you everything suddenly

107
00:09:44,547 --> 00:09:49,691
becomes around um what there are immediate actions that i

108
00:09:49,751 --> 00:09:52,733
need to take to take care of real world issues

109
00:09:53,793 --> 00:09:57,556
and so you tend to put your own grief to

110
00:09:57,636 --> 00:10:00,038
the side for a little while and then it's only

111
00:10:00,158 --> 00:10:05,861
later that you really begin to experience that. And so

112
00:10:05,941 --> 00:10:07,523
that, that makes a lot of sense. I mean, you

113
00:10:07,562 --> 00:10:09,324
probably just kind of feel a little bit lost right

114
00:10:09,344 --> 00:10:14,427
now, I would imagine. Yeah. Tina's been fantastic. She's like,

115
00:10:16,268 --> 00:10:21,212
we'll figure it out. Everything's doable. Everything's possible. We'll figure

116
00:10:21,212 --> 00:10:24,494
it out. That's really awesome that she's not freaking out.

117
00:10:25,875 --> 00:10:28,576
But she realizes the same thing. It's like, okay, well,

118
00:10:29,997 --> 00:10:32,979
what does this mean? How do we move forward if

119
00:10:33,139 --> 00:10:37,582
income stops? But I'm trying not to. I kind of

120
00:10:37,622 --> 00:10:41,145
stopped worrying about money in 1990 for a whole bunch

121
00:10:41,225 --> 00:10:45,548
of reasons. Mostly because you lost it all? No, no,

122
00:10:46,388 --> 00:10:51,031
no. That came later. Okay. No, that came in the

123
00:10:51,051 --> 00:10:57,155
2000s. And I really love podcasting. I love the shows

124
00:10:57,195 --> 00:11:01,118
that I do. I love No Agenda. I really did,

125
00:11:01,198 --> 00:11:08,363
but I just don't see... and recreate some chemistry. I

126
00:11:10,444 --> 00:11:13,606
think I'd always-- if that were the way I would

127
00:11:13,646 --> 00:11:17,069
go, it would always be unbalanced. You know what I

128
00:11:17,069 --> 00:11:21,792
mean? And also, you know, we were 50-50 partners on

129
00:11:21,852 --> 00:11:25,694
a handshake, literally, except for the, we had to form

130
00:11:25,734 --> 00:11:28,596
an LLC because the IRS was like, what are all

131
00:11:28,616 --> 00:11:32,819
these $3 checks? What's all this cash and envelopes? Are

132
00:11:32,859 --> 00:11:35,461
you a political candidate? What is this? What's going on

133
00:11:35,601 --> 00:11:40,064
with that? So we had to formalize that. You know,

134
00:11:40,444 --> 00:11:44,847
so there's another, there's another party in this equation, you

135
00:11:44,847 --> 00:11:46,988
know, so how do you deal with that? And it's

136
00:11:47,028 --> 00:11:52,212
just, but, but just from a creative, point. John was

137
00:11:52,352 --> 00:11:56,735
my counterpart. Just like you're my counterpart on this show

138
00:11:56,915 --> 00:12:00,818
and Jimmy's my counterpart. do this. And that's something, you

139
00:12:00,818 --> 00:12:03,059
know, Jimmy and I've been talking for years before we

140
00:12:03,119 --> 00:12:05,181
said, hey, let's hit record on this. Same with you

141
00:12:05,281 --> 00:12:09,103
and I. So I don't have that luxury of finding,

142
00:12:09,123 --> 00:12:11,385
oh, let me find you, buddy. Yeah, let's talk for

143
00:12:11,425 --> 00:12:13,886
a bit and then we'll hit record. Just doesn't seem

144
00:12:13,986 --> 00:12:17,329
like it. But it's just interesting as, and John and

145
00:12:17,349 --> 00:12:18,830
I would talk about this all the time. This was

146
00:12:18,910 --> 00:12:23,433
our famed exit strategy talk because there's no exiting from

147
00:12:23,533 --> 00:12:26,355
a podcast, except the way he did it. He literally

148
00:12:26,395 --> 00:12:30,878
took the only exit strategy there. is and by the

149
00:12:30,938 --> 00:12:34,800
way to just be lighted out while grousing about the

150
00:12:34,900 --> 00:12:38,643
hole in NCIS, yeah, I'll sign me up for that.

151
00:12:38,703 --> 00:12:43,986
That's the way to go. That's simultaneously the most John

152
00:12:44,046 --> 00:12:47,228
Dvorak thing to do and also a great way to

153
00:12:47,248 --> 00:12:51,491
go out. Exactly, exactly. So, and I appreciate him for

154
00:12:51,551 --> 00:12:56,034
that. But, you know, I'm... It'll sound corny, but I'm

155
00:12:56,094 --> 00:13:00,017
just putting my faith in God and praying about it

156
00:13:00,217 --> 00:13:04,200
and saying, what does this mean? And listening for answers.

157
00:13:04,660 --> 00:13:07,562
And that will take a little bit of just time

158
00:13:08,503 --> 00:13:12,345
without the stress of. doing a show twice a week

159
00:13:12,385 --> 00:13:14,647
so i have some thoughts on how we'll keep the

160
00:13:14,667 --> 00:13:18,469
show going uh for for a couple weeks so i

161
00:13:18,549 --> 00:13:22,472
can just get my get my head together sure um

162
00:13:22,812 --> 00:13:24,333
and we'll see we'll see where it goes but i

163
00:13:24,373 --> 00:13:26,755
appreciate i appreciate the concern because yeah the concern is

164
00:13:26,815 --> 00:13:29,657
obviously real you have to get a job i don't

165
00:13:29,677 --> 00:13:35,480
know Maybe. I mean, there's, this could be the case

166
00:13:35,561 --> 00:13:42,345
that other people face when... of a long running co-host.

167
00:13:43,886 --> 00:13:46,528
I think there's maybe not a lot of people in

168
00:13:46,568 --> 00:13:52,252
this situation, but there are quite a few who, I

169
00:13:52,312 --> 00:13:56,634
mean, think about any show like, take "Accidental Tech" or

170
00:13:57,275 --> 00:14:01,017
"The Flophouse" or any of these shows where there's two

171
00:14:01,358 --> 00:14:07,422
or three people who are sort of, whose personalities combine

172
00:14:07,462 --> 00:14:11,504
to create really what the show is. It's not one,

173
00:14:12,665 --> 00:14:15,327
you really can't just plug another person in. It's really

174
00:14:15,847 --> 00:14:23,092
this unique fingerprint that's created by the combination of... personalities

175
00:14:24,053 --> 00:14:27,015
and how they interact. Here's the thing that is unique

176
00:14:27,015 --> 00:14:33,519
though. Because with everything I've ever done in broadcasting, and

177
00:14:33,539 --> 00:14:36,901
certainly in podcasting, I learned a long time ago, and

178
00:14:36,921 --> 00:14:39,663
this is part of the value for value model, is

179
00:14:39,743 --> 00:14:44,786
that... building a community. audience. See, this is my, this

180
00:14:44,866 --> 00:14:50,810
is completely antithetical to what the podcast industry. wants. They

181
00:14:50,910 --> 00:14:55,333
want numbers. And we're going to jerry-rig this thing so

182
00:14:55,413 --> 00:14:57,255
that we can show numbers. Even if you hit play

183
00:14:57,315 --> 00:14:59,576
and listen for 30 seconds, we've got numbers. Numbers, numbers,

184
00:14:59,636 --> 00:14:59,976
numbers, numbers.

185
00:15:01,360 --> 00:15:07,525
And... very very difficult you know we probably would have

186
00:15:08,445 --> 00:15:15,630
made a little maybe 20 percent with advertising, with the

187
00:15:15,690 --> 00:15:18,572
amount, depending on how many ads we would jam into

188
00:15:18,672 --> 00:15:22,375
a show, just looking at the number of downloads, if

189
00:15:22,435 --> 00:15:24,816
we'd gone that route. And it would have never worked

190
00:15:24,956 --> 00:15:27,798
because we would have lost advertisers for all kinds of

191
00:15:27,878 --> 00:15:31,521
reasons. And certainly during COVID, where the value for value

192
00:15:31,581 --> 00:15:35,383
model actually worked very well in our favor, that would

193
00:15:35,423 --> 00:15:39,646
have been extremely adverse if we were an ad-driven podcast.

194
00:15:43,309 --> 00:15:46,871
is far bigger than than adam and john i mean

195
00:15:46,971 --> 00:15:50,153
we have five meetups a weekend taking place all over

196
00:15:50,173 --> 00:15:53,035
the world you know it's not like we're at the

197
00:15:53,055 --> 00:15:58,439
meetup people just hanging out together discussed or whatever they're

198
00:15:58,439 --> 00:16:02,282
doing. You know, we've had people meet each other. It's

199
00:16:02,362 --> 00:16:07,845
a very, it's a community. that help me through it

200
00:16:09,707 --> 00:16:13,569
no matter what I do or or but I also

201
00:16:14,050 --> 00:16:18,212
feel a responsibility towards them too. You know, you can't

202
00:16:18,292 --> 00:16:24,417
rug pull. I mean, that's just not something that can

203
00:16:24,477 --> 00:16:31,561
happen. It's way too... We have jokes and inside jokes

204
00:16:31,802 --> 00:16:36,645
and and all kinds of things that you know I

205
00:16:36,665 --> 00:16:43,289
don't want that to fall apart. just general point to

206
00:16:43,369 --> 00:16:47,792
make about what no agenda was is because you built

207
00:16:49,594 --> 00:16:54,397
because you because you And it evolved over time into

208
00:16:54,477 --> 00:16:58,740
being more than just content. It was a whole community

209
00:16:58,820 --> 00:17:05,704
of people. community of people will follow you to your

210
00:17:05,765 --> 00:17:09,227
next project, but it doesn't mean that you're going to

211
00:17:09,247 --> 00:17:12,509
keep them there. I mean, if the con. They won't.

212
00:17:15,011 --> 00:17:19,734
built the community and that community is, is strong and

213
00:17:19,794 --> 00:17:24,037
will follow you and give this next, whatever project you

214
00:17:24,117 --> 00:17:26,559
do next, they'll give that a shot. Yeah. No, I

215
00:17:26,639 --> 00:17:29,581
know. And that gives you, you know, at least it

216
00:17:29,641 --> 00:17:32,022
gives you a solid footing to begin with, you know,

217
00:17:33,283 --> 00:17:37,686
and, and because they want, they're, they're, I think a

218
00:17:37,726 --> 00:17:39,688
lot of them, like, it's, it's sort of like, um,

219
00:17:40,948 --> 00:17:45,592
when Neil Peart passed away in Rush, You can't just

220
00:17:45,672 --> 00:17:57,860
plug... It's not that bad. different. Yeah. Oh yeah, for

221
00:17:57,860 --> 00:18:01,823
sure. I think of, I mean, just our show, we've

222
00:18:01,923 --> 00:18:05,525
been going for six years and, you know. Don't die

223
00:18:05,665 --> 00:18:18,594
on me. I promise. I will never die. If you

224
00:18:18,994 --> 00:18:21,756
left or something, I could, like, I'm not going to

225
00:18:21,756 --> 00:18:24,038
just keep doing it. I can't do it by myself

226
00:18:24,258 --> 00:18:27,040
or, like, with somebody else. It's just not the same

227
00:18:27,140 --> 00:18:31,683
thing. the, in, in, The desire to even do that

228
00:18:31,743 --> 00:18:36,486
wouldn't be there. Right. Well, there you go. Because this

229
00:18:36,566 --> 00:18:40,709
also applies to... If you're a podcaster and your longtime

230
00:18:40,749 --> 00:18:45,492
podcast co-host dies, it's not just that they die. They

231
00:18:45,532 --> 00:18:50,455
could also just leave for business reasons or health reasons.

232
00:18:51,436 --> 00:18:53,758
There's just lots of reasons why something like that could

233
00:18:53,818 --> 00:18:59,802
become an issue for people. I mean, I guess it

234
00:19:00,062 --> 00:19:02,323
has to be part of your planning process, I guess.

235
00:19:02,584 --> 00:19:05,606
Basically, what we're saying is podcasting is a bad industry

236
00:19:05,666 --> 00:19:08,468
to get into. It never ends well. It never ends

237
00:19:08,548 --> 00:19:24,098
well. It's the road. Straight up. So... I have some

238
00:19:24,178 --> 00:19:36,066
ideas. I've spoken to a few people. The worst part.

239
00:19:39,248 --> 00:19:42,110
is an interesting I can't do the show with anybody.

240
00:19:43,291 --> 00:19:45,993
that show the way it is. So something has to

241
00:19:46,093 --> 00:19:50,636
transform and I may or may not be. But I

242
00:19:50,696 --> 00:19:54,419
think the show can continue. one way or the other.

243
00:19:57,060 --> 00:20:04,265
yet. And as I said, I haven't really. Tuesday, it's

244
00:20:04,325 --> 00:20:17,074
like, okay, I... Monday. Like, what? everybody, trying to get

245
00:20:17,134 --> 00:20:19,636
stuff together. We wanted to do a memorial show, of

246
00:20:19,696 --> 00:20:23,719
course. I don't know what I did Wednesday. We just

247
00:20:23,739 --> 00:20:27,581
did the show Thursday. Six hours is long when you're

248
00:20:27,581 --> 00:20:34,386
reading 700 notes. And today or tomorrow I've got to

249
00:20:34,626 --> 00:20:41,411
put some some kind of best of job. stuff to

250
00:20:41,471 --> 00:20:43,592
me so that's really good always the producers of course

251
00:20:43,632 --> 00:20:46,634
they do So I got to put that together and

252
00:20:46,654 --> 00:20:50,877
then we have to. because more will come in. And

253
00:20:50,937 --> 00:20:53,899
then, you know, John's memorial is going to be on.

254
00:20:54,680 --> 00:20:59,923
So we got it to San Francisco. Coincidentally, like... within

255
00:20:59,943 --> 00:21:04,726
the period that John died, I got a baby granddaughter.

256
00:21:05,467 --> 00:21:08,769
Yeah, that's right. So it was kind of like life

257
00:21:08,849 --> 00:21:12,572
and death in one go. And we got a We

258
00:21:12,652 --> 00:21:15,714
got to go visit. Yeah. Because we haven't seen that

259
00:21:15,754 --> 00:21:18,956
we were there long. You have some kind of buzz

260
00:21:19,016 --> 00:21:20,937
going on. Do you have a USB cable? I heard

261
00:21:21,037 --> 00:21:23,159
it. Do you have a USB cable somewhere near? Let

262
00:21:23,499 --> 00:21:29,263
me. No, not really. I think it's gone now. Um...

263
00:21:30,904 --> 00:21:35,787
So we'll see. As I would say in these cases,

264
00:21:36,107 --> 00:21:39,049
it was a real day wrecker. That's for sure. It's

265
00:21:39,110 --> 00:21:46,795
a real day wrecker. Now, this. in the podcast world.

266
00:21:46,835 --> 00:21:52,759
Okay. group came out and still kind of secret who's

267
00:21:52,839 --> 00:21:57,682
in it. You find it interesting? I find it interesting

268
00:21:57,762 --> 00:22:00,764
because I see opportunity. That's why. I mean, I see

269
00:22:00,804 --> 00:22:05,487
opportunity that may be counter to what most people see.

270
00:22:05,507 --> 00:22:16,375
I thought the most... And... You know, so they have

271
00:22:16,415 --> 00:22:19,877
a definition of is and you know I I kind

272
00:22:19,937 --> 00:22:22,059
of like the idea of it works with your eyes

273
00:22:22,159 --> 00:22:25,341
closed okay that's cute and then they add to that

274
00:22:25,421 --> 00:22:30,164
which is Could be RSS, doesn't have to be. Okay,

275
00:22:30,264 --> 00:22:35,107
well, I take some. Some exception to that. But then

276
00:22:35,168 --> 00:22:40,511
it all folds right into... Well, okay, so I was

277
00:22:40,571 --> 00:22:44,894
listening to Dan Granger on Pod News Weekly Review, and

278
00:22:44,934 --> 00:22:46,835
he said, you know, the worst thing we can do

279
00:22:46,996 --> 00:22:50,558
is we can be confusing our customers. And I thought,

280
00:22:51,659 --> 00:22:53,840
hold on a second. Who is the customer of a

281
00:22:53,900 --> 00:22:58,803
podcast? That's the listener. And they're all focused on the

282
00:22:58,984 --> 00:23:03,206
advertiser. And I understand it, and I understand what they

283
00:23:03,267 --> 00:23:05,228
want to do, and it's not going to make, it's

284
00:23:05,248 --> 00:23:10,932
going to make a few people. nothing because agencies and

285
00:23:12,092 --> 00:23:22,700
platforms and uh agencies, platforms, well, you know, they... The

286
00:23:22,700 --> 00:23:31,285
role. You get 10,000 downloads. for any podcast, you know,

287
00:23:31,326 --> 00:23:33,287
they're going to take a hundred of them, roll them

288
00:23:33,407 --> 00:23:35,909
up and, you know, they're going to make their 15%

289
00:23:36,069 --> 00:23:38,250
agency cut or whatever it is. And everyone else will

290
00:23:38,250 --> 00:23:42,233
get, you know. off of it nice little money and

291
00:23:42,353 --> 00:23:46,115
somehow that's a multi-billion dollar industry i'm just not seeing

292
00:23:46,175 --> 00:23:49,738
it but i guess it's true and and so then

293
00:23:49,798 --> 00:23:57,923
they come up with this metric which is so determine

294
00:23:58,284 --> 00:24:00,805
what a play is and it's either 60 seconds or

295
00:24:00,885 --> 00:24:04,488
30 seconds i'm like you actually with the with the

296
00:24:04,628 --> 00:24:09,371
infrastructure they're talking about putting together handing over all this.

297
00:24:11,092 --> 00:24:15,315
which we know that an app can actually do a

298
00:24:15,315 --> 00:24:18,357
pretty good job of understanding what people are doing and

299
00:24:18,477 --> 00:24:21,019
even how long they're listening. But see, they don't want

300
00:24:21,039 --> 00:24:23,581
to do that. They don't want to actually say, yes,

301
00:24:23,721 --> 00:24:28,244
advertiser, your ad was heard. played while someone had the

302
00:24:28,324 --> 00:24:30,445
phone in their hand and was using it and the

303
00:24:30,505 --> 00:24:33,548
play button was pressed we're going to presume that and

304
00:24:33,588 --> 00:24:36,249
they heard your ad. They don't want to do that.

305
00:24:36,389 --> 00:24:38,451
Which, if you're going to do all this data stuff

306
00:24:38,591 --> 00:24:41,573
anyway, just get to it. You can do that, but

307
00:24:41,593 --> 00:24:45,135
they don't want to because they know it's bullshit. Because

308
00:24:45,135 --> 00:24:48,498
the numbers will drop off a cliff, which I personally

309
00:24:48,518 --> 00:24:51,620
think would be good because then you have more scarcity,

310
00:24:51,700 --> 00:24:54,682
you can ask for higher CPMs, but the industry is

311
00:24:54,762 --> 00:24:57,604
all built around this now and they don't want to

312
00:24:57,664 --> 00:25:00,025
see that happen. So the whole thing is kind of

313
00:25:00,046 --> 00:25:06,410
a farce. As I'm listening to it, I'm like, well,

314
00:25:06,450 --> 00:25:10,673
first of all, I said, if I'm on a podcast

315
00:25:10,833 --> 00:25:16,297
app, just... and I hit another chapter, does that count

316
00:25:16,737 --> 00:25:23,762
as another play? - Why would that, what are you

317
00:25:23,862 --> 00:25:26,663
thinking in that regard? - Well, I mean, we're hearing

318
00:25:26,724 --> 00:25:29,265
all of these numbers coming out of Apple, like, you

319
00:25:29,285 --> 00:25:31,987
know, I had 300 people listening, but I had 350

320
00:25:32,067 --> 00:25:38,512
plays. Why is that? Is that because the plays get

321
00:25:38,612 --> 00:25:42,034
registered when it stops for a second because you got

322
00:25:42,034 --> 00:25:44,836
a text message? message or you hit on a chapter

323
00:25:44,896 --> 00:25:49,759
there's all these variables that we don't know and so

324
00:25:49,839 --> 00:25:53,181
this just it's it's gotten if it's gotten even worse

325
00:25:53,302 --> 00:25:56,103
I think what they're proposing it's worse than downloads now

326
00:25:56,143 --> 00:25:59,906
it's just all these variables and they're cutting everybody out

327
00:26:00,546 --> 00:26:02,648
it's only they only want to get Apple on board

328
00:26:02,668 --> 00:26:06,751
they only get will be on board by default. YouTube

329
00:26:06,811 --> 00:26:08,772
is in there. It's only going to get worse for

330
00:26:08,832 --> 00:26:15,096
everybody. It's not going to get any better. They're not

331
00:26:15,176 --> 00:26:19,880
really, no one's talking about Podverse or Podcast Guru or

332
00:26:19,920 --> 00:26:23,922
True Fans. No one's talking about that. They don't care.

333
00:26:24,182 --> 00:26:27,845
They do not care. They only care about Apple, Spotify,

334
00:26:28,125 --> 00:26:30,447
and I guess YouTube. That's all the big three. The

335
00:26:30,507 --> 00:26:35,230
big three, the big three, the big three. So, you

336
00:26:35,290 --> 00:26:45,197
know, it's like good luck. Good luck. I'm conflicted a

337
00:26:46,077 --> 00:26:50,440
lot about the whole amp thing because in... of me

338
00:26:50,600 --> 00:26:55,904
that says this whole thing is just going to be

339
00:26:57,625 --> 00:27:01,167
sort of a bum And then nobody's ever going to

340
00:27:01,208 --> 00:27:05,871
think about it again. I mean, I would not. I'm

341
00:27:05,931 --> 00:27:16,198
going to give my thoughts on it and try to

342
00:27:16,218 --> 00:27:23,142
be as kind as I can, but also give my

343
00:27:24,123 --> 00:27:30,327
raw opinion. and Giles and all these, I think they

344
00:27:30,768 --> 00:27:38,573
just seem like nice, well-intentioned people. it would not surprise

345
00:27:38,693 --> 00:27:45,257
me if this thing just basically goes into most people's

346
00:27:45,978 --> 00:27:49,760
trash bin like right after they read it and it'll

347
00:27:49,800 --> 00:27:57,365
never be thought of again. I just... I'm not trying

348
00:27:57,606 --> 00:28:02,109
to be dismissive. I'm just giving what I think is

349
00:28:02,149 --> 00:28:06,632
an honest assessment that I'm not sure that this document

350
00:28:06,752 --> 00:28:12,396
is ever going to even last. in anybody's memory past

351
00:28:13,376 --> 00:28:16,538
this week. That's a very short life you give it

352
00:28:16,558 --> 00:28:21,142
there. Well, there's a lot of, there's a, there's some

353
00:28:21,162 --> 00:28:27,426
reasons for that. I feel like, um, you know, they

354
00:28:27,506 --> 00:28:30,968
contacted me last week and asked for my opinion. past

355
00:28:31,028 --> 00:28:34,931
week and I was very honest with him that I

356
00:28:36,972 --> 00:28:45,638
disagreed philosophically with doing things in private. And I think

357
00:28:45,978 --> 00:28:48,820
that the only way they could get all these people

358
00:28:48,960 --> 00:28:55,765
in the same Zoom session together was by making everything

359
00:28:55,865 --> 00:28:59,708
very private and a bunch of NDAs and that kind

360
00:28:59,728 --> 00:29:01,589
of thing. I think that's the only way that any

361
00:29:01,649 --> 00:29:03,550
of these big players are going to actually talk to

362
00:29:03,670 --> 00:29:07,033
one another and try to do things in anything that

363
00:29:07,073 --> 00:29:11,255
looks like a committee or anything like that. like that.

364
00:29:12,356 --> 00:29:15,338
So the secrecy was baked in from the very beginning,

365
00:29:15,418 --> 00:29:18,320
probably because, probably not out of desire, but probably because

366
00:29:18,380 --> 00:29:19,781
it was just the only way to get all those

367
00:29:19,781 --> 00:29:24,665
people in the same room together. And the problem with

368
00:29:24,705 --> 00:29:31,709
that, though, is... Whatever decisions they make in the secret

369
00:29:31,769 --> 00:29:35,832
room don't have a chance to be commented on by

370
00:29:35,952 --> 00:29:41,616
people outside of that secret room bubble. That's why doing

371
00:29:41,676 --> 00:29:44,318
things in secret is so important. is not the right

372
00:29:44,378 --> 00:29:53,524
approach and it kneecaps otherwise efforts because When you do

373
00:29:53,624 --> 00:29:58,487
it in secret, you don't have the insight that communities

374
00:29:58,548 --> 00:29:58,908
bring.

375
00:30:00,000 --> 00:30:03,422
And you don't, you can. You can short circuit a

376
00:30:03,462 --> 00:30:08,205
lot of wasted effort and a lot of Mediocre ideas.

377
00:30:09,566 --> 00:30:15,090
by just having more people give their opinion. And that.

378
00:30:16,431 --> 00:30:19,993
It was clear that that was not done here. Now,

379
00:30:20,313 --> 00:30:24,496
I mean, I want, I was wanting to have. those

380
00:30:24,536 --> 00:30:26,978
guys on the show, but that's proving to be a

381
00:30:27,038 --> 00:30:30,260
little more difficult than I thought it would be. And

382
00:30:30,300 --> 00:30:33,562
maybe we'll still be able to get that to happen.

383
00:30:35,403 --> 00:30:39,026
um Like, essentially, I'm just gonna be talk- I'm just

384
00:30:39,046 --> 00:30:44,830
gonna talk- about the the questions I would ask. or

385
00:30:44,850 --> 00:30:54,676
I would want to ask is, The podcast definition part

386
00:30:54,717 --> 00:30:59,520
of the document. To me, that seems like a little

387
00:30:59,540 --> 00:31:02,462
bit of internal, like inside baseball to the marketing industry.

388
00:31:02,502 --> 00:31:04,043
And I don't, I mean, that doesn't really, I don't

389
00:31:04,083 --> 00:31:10,447
care, whatever. That's their business. then the document takes a

390
00:31:10,507 --> 00:31:13,769
turn and asks and starts laying out a lot of

391
00:31:13,809 --> 00:31:20,394
technical specifications. and what it lays out. is a heavy

392
00:31:20,874 --> 00:31:30,020
lift. podcast app developers. What it wants is... is constant.

393
00:31:32,102 --> 00:31:41,908
reporting. first party reporting. Play metrics. Ditter. that are somewhat

394
00:31:42,169 --> 00:31:46,732
anonymized. And let me say what I mean by somewhat.

395
00:31:47,732 --> 00:31:51,475
It's using the made MAID standard for like in a

396
00:31:51,555 --> 00:31:58,560
hashed email address for the listener. It is. not clear

397
00:31:58,760 --> 00:32:04,664
in what ways this this interacts with GDPR compliance and

398
00:32:04,764 --> 00:32:09,667
California's privacy regulations. That's a good point. So immediately, and

399
00:32:09,947 --> 00:32:15,811
the document lays this out. Um... It lays out. that

400
00:32:16,772 --> 00:32:22,216
There will have to be opt-outs. and things like that

401
00:32:22,276 --> 00:32:24,677
that are put in place in order to support this.

402
00:32:25,978 --> 00:32:29,200
calls there is probably going to be some sort of

403
00:32:30,721 --> 00:32:34,404
violation of GDPR or some sort of interaction with those

404
00:32:34,424 --> 00:32:42,149
laws. So what you end up with. is a humongous

405
00:32:42,249 --> 00:32:47,813
coding effort. on the part of a small team or

406
00:32:47,873 --> 00:32:53,097
a solo app developer. and It's a ton of work.

407
00:32:54,558 --> 00:33:01,382
With lots of exposure to downside. Because now, if the

408
00:33:01,462 --> 00:33:07,686
stuff breaks... You hear directly from the app user. If

409
00:33:08,927 --> 00:33:12,330
Now you have to support all the GDPR takedown, delete

410
00:33:12,370 --> 00:33:17,533
my account requests. Yep. There is all, and all of

411
00:33:17,533 --> 00:33:20,595
this stuff comes to the app developer, not the people

412
00:33:20,655 --> 00:33:24,198
who wrote this specification. I didn't see app developers in

413
00:33:24,278 --> 00:33:28,621
there anywhere. All that was in this document on the

414
00:33:28,721 --> 00:33:32,844
app development side was what they want. Yeah. And there's

415
00:33:32,924 --> 00:33:35,285
nothing in there about what the app developers are going

416
00:33:35,305 --> 00:33:37,827
to get because the app developers are not going to

417
00:33:37,847 --> 00:33:42,910
get anything but headaches. No. There's all the app developers

418
00:33:43,090 --> 00:33:48,514
in what is being asked. The app developers get all

419
00:33:48,554 --> 00:33:52,237
of the downside and none of the benefit. I mean,

420
00:33:52,337 --> 00:33:59,722
really, they're doing what? advertising always drives companies to do

421
00:34:00,062 --> 00:34:03,584
is hijack it. And the problem is that people have

422
00:34:03,624 --> 00:34:07,807
tried to hijack RSS for decades. And it's very, very

423
00:34:07,887 --> 00:34:10,269
difficult. And I don't, I really don't think they can

424
00:34:10,349 --> 00:34:15,693
do it. And the whole nature, the whole. openness of

425
00:34:15,953 --> 00:34:21,577
RSS is antithetical to how advertising works. Advertising wants to

426
00:34:21,637 --> 00:34:25,099
be in a controlled environment. We have all this information.

427
00:34:26,100 --> 00:34:33,605
And we can really also... artificially restrict the supply to

428
00:34:33,785 --> 00:34:38,908
up the demand to increase the CPM. And the internet,

429
00:34:38,988 --> 00:34:42,971
I mean, ask yourself. Who is really making a living

430
00:34:43,031 --> 00:34:51,116
with a blog? Nobody. The only thing that is reasonably

431
00:34:51,197 --> 00:34:56,320
successful is Substack. And I'm sure there are others. But

432
00:34:56,360 --> 00:35:00,863
Substack has a very interesting model. They make it super

433
00:35:01,003 --> 00:35:07,347
easy for you to... basically create a, you know, it's

434
00:35:07,367 --> 00:35:10,810
like they have a... funding tag, you know, click it,

435
00:35:10,810 --> 00:35:13,151
click here. You want to, you want to spend money

436
00:35:13,572 --> 00:35:18,055
once you're. In the system... then you can subscribe to

437
00:35:18,215 --> 00:35:21,637
any of these blogs. We'll just call them blogs. And

438
00:35:21,697 --> 00:35:25,640
now they also do podcasts. And that's actually not a

439
00:35:25,660 --> 00:35:28,902
bad idea. I don't like that it's a platform because

440
00:35:28,942 --> 00:35:31,644
platforms can change. They can change ownership. They can go,

441
00:35:31,804 --> 00:35:34,526
all kinds of stuff can happen. They can increase fees,

442
00:35:34,546 --> 00:35:40,670
you know, all these problems. I think still. Podcast is

443
00:35:40,730 --> 00:35:42,851
something you create to listen to if you want to

444
00:35:42,891 --> 00:35:44,893
if you want to make your living out of it

445
00:35:44,953 --> 00:35:47,815
You're gonna have to do something else. You it's not

446
00:35:47,895 --> 00:35:51,457
just about how do I increase my downloads? They're there

447
00:35:51,577 --> 00:35:53,919
this whole amp group the way I think they're looking

448
00:35:54,019 --> 00:35:58,042
at it is like influencers. So they have their Dynamically

449
00:35:58,122 --> 00:36:00,523
inserted ads which they just want to do at scale.

450
00:36:00,623 --> 00:36:04,566
So I just want to buy 1000 podcasts insert my

451
00:36:04,826 --> 00:36:12,792
ad there each podcast has 10,000 a thousand downloads, listens,

452
00:36:12,912 --> 00:36:15,013
plays, whatever you want to call it. So that's a

453
00:36:15,033 --> 00:36:21,798
million. that's uh a thousand CPMs. So that should cost

454
00:36:21,878 --> 00:36:28,863
me, you know. $3,000, $5,000, whatever. Probably less. And the

455
00:36:28,963 --> 00:36:32,805
money that trickles down is pennies to everybody else. The

456
00:36:32,905 --> 00:36:37,268
influencer part is, which is a very established industry right

457
00:36:37,348 --> 00:36:39,930
now. I know because my daughter is doing it. And

458
00:36:40,290 --> 00:36:42,772
they look at how many followers do you have. So

459
00:36:42,832 --> 00:36:45,454
you have to have at least, I think, 50,000 followers.

460
00:36:46,254 --> 00:36:49,096
And then they look at your views. And they don't

461
00:36:49,096 --> 00:36:52,799
really care. how long you want because it's video it's

462
00:36:52,799 --> 00:36:56,461
a different experience and okay you get so you get

463
00:36:56,561 --> 00:36:59,643
x amount of views per post uh we want you

464
00:36:59,683 --> 00:37:04,106
to promote this product incorporate it into your uh into

465
00:37:04,146 --> 00:37:07,269
your content which usually turns out to be the content

466
00:37:07,389 --> 00:37:10,711
which i've always been a fan of that i like

467
00:37:10,771 --> 00:37:13,213
home shopping network you know i think this is a

468
00:37:13,273 --> 00:37:16,295
great model and that's kind of what they want to

469
00:37:16,355 --> 00:37:21,658
do But that's because the platforms have all this information.

470
00:37:22,599 --> 00:37:26,822
And, Lord, the platforms, they make more money on selling

471
00:37:26,902 --> 00:37:30,444
the user, the viewer information than they do on the

472
00:37:30,624 --> 00:37:33,366
ads, you know, to data brokers and all this stuff.

473
00:37:34,867 --> 00:37:38,049
So it's really, it's, you know, people want to capitalize

474
00:37:38,170 --> 00:37:41,852
and want to monetize podcasting. It's not set up for

475
00:37:41,952 --> 00:37:45,274
it. And it never will be because it's not. This

476
00:37:45,354 --> 00:37:46,815
is why they say it doesn't have to be an

477
00:37:46,996 --> 00:37:50,778
RSS feed. That's the key. That's the key. That's the

478
00:37:50,818 --> 00:37:54,961
thing they want. This is a podcast and you don't

479
00:37:55,001 --> 00:37:57,463
have to do it in any certain way. But if

480
00:37:57,743 --> 00:38:01,946
this podcast is on YouTube or if it's in some

481
00:38:02,006 --> 00:38:06,288
other enclosed environment, then I'm sure Instagram will soon have

482
00:38:06,288 --> 00:38:09,211
podcasts. They'll call it podcast. They'll have a tab called

483
00:38:09,271 --> 00:38:14,254
podcast. X will have that. Everybody will have that. But

484
00:38:15,014 --> 00:38:17,896
that's when you are so at risk. It's worse than

485
00:38:18,297 --> 00:38:22,239
your podcast partner dying. Lost Adam. Oh, did you lose

486
00:38:22,279 --> 00:38:25,962
me? Hello? Oh, there you are. You disappeared. Oh, I'm

487
00:38:26,022 --> 00:38:30,185
sorry. Didn't mean to. That was weird. No, I was

488
00:38:30,265 --> 00:38:35,568
saying that... The way did you lose me? Uh, I

489
00:38:35,608 --> 00:38:39,211
don't remember. Okay. Don't worry. It was like five words

490
00:38:39,211 --> 00:38:43,354
ago. It wasn't important. I just, I don't see it

491
00:38:43,674 --> 00:38:46,256
as... Oh, you said Instagram's going to have a podcast

492
00:38:46,316 --> 00:38:49,378
tab. Yeah, everyone's going to have a podcast tab. And

493
00:38:49,398 --> 00:38:51,559
that's going to be called a podcast. And now you'll

494
00:38:51,559 --> 00:38:54,521
have to upload your video to all these different platforms.

495
00:38:55,822 --> 00:39:01,066
It's the opposite of what podcasting is. It's the opposite.

496
00:39:04,028 --> 00:39:11,393
Well. I can tell you this. Marco Arment. is going

497
00:39:11,413 --> 00:39:13,834
to keep a copy of this document in the bathroom.

498
00:39:15,055 --> 00:39:16,896
so he can wipe his ass with it every time

499
00:39:16,936 --> 00:39:21,299
he goes to the bathroom. And I can pretty much

500
00:39:21,359 --> 00:39:26,643
guarantee you that most other indie app developers... Are not

501
00:39:26,703 --> 00:39:29,505
even going to read it. But see, that's the point.

502
00:39:30,305 --> 00:39:32,827
I've heard these guys talk. They don't care. They want

503
00:39:32,987 --> 00:39:35,029
Apple to do it. And they're going to push Apple

504
00:39:35,089 --> 00:39:37,170
as far as they can. And guess what Apple's going

505
00:39:37,210 --> 00:39:42,073
to do? Nothing. No, they will. Oh, they definitely will.

506
00:39:42,073 --> 00:39:44,095
Oh, yes. Oh, yes, they will. Look, you think that

507
00:39:44,515 --> 00:39:48,518
you think Apple's going to report. stats back every 30

508
00:39:48,598 --> 00:39:52,801
seconds they're already in the game with hls video no

509
00:39:53,321 --> 00:39:57,043
yes they are they're taking a piece Yeah, well, yeah,

510
00:39:57,123 --> 00:39:58,965
they're taking a piece of it, but why would they

511
00:39:59,045 --> 00:40:03,548
help in this way? You're missing my point. They'll be

512
00:40:03,608 --> 00:40:06,070
like, sure, we'll help you out. We're going to take

513
00:40:06,150 --> 00:40:10,232
a piece. I don't think so. They're already doing it.

514
00:40:10,272 --> 00:40:14,976
Why wouldn't they? Because they weren't part of it. That's

515
00:40:15,016 --> 00:40:17,057
not the way they would. They don't let other people

516
00:40:17,157 --> 00:40:20,900
build specs and then go adopt it. When it's something

517
00:40:20,960 --> 00:40:27,204
like the only reason that Ted and the fellers at

518
00:40:28,205 --> 00:40:33,408
Apple Podcasts have implemented the podcasting 2.0 tags is because

519
00:40:33,928 --> 00:40:37,291
they made a lot of technical sense and it matched

520
00:40:37,411 --> 00:40:44,516
up with some things they wanted to do. There was

521
00:40:44,516 --> 00:40:49,199
a synchronicity there that happened over time. And we just

522
00:40:49,359 --> 00:40:51,420
ended up, you know, we were all in the same

523
00:40:51,500 --> 00:40:55,303
rooms together at various podcast conferences and stuff. And it

524
00:40:55,343 --> 00:41:01,287
just evolved as a relationship over time. Why did Apple

525
00:41:01,427 --> 00:41:06,430
get into taking a piece of the advertising with HLS

526
00:41:06,490 --> 00:41:15,356
video? Why? because they developed it. Oh, okay. So they

527
00:41:15,396 --> 00:41:17,778
can look at this. That's my point, though. They wrote

528
00:41:17,878 --> 00:41:21,220
HLS, and they also developed the spec to get the

529
00:41:21,260 --> 00:41:24,703
money out. Apple podcasting has always been a cost center.

530
00:41:25,243 --> 00:41:27,545
I'm not talking about Ted and the wonderful people over

531
00:41:27,605 --> 00:41:30,807
there. Sure. We got a new CEO coming in. I

532
00:41:30,847 --> 00:41:33,489
don't know what he's doing, but it seems to me

533
00:41:34,169 --> 00:41:37,231
that if there is a group out there who says,

534
00:41:37,291 --> 00:41:39,853
hey, there's another billion dollars on the sideline here of

535
00:41:39,933 --> 00:41:42,895
an already billion dollar or two billion dollar or 20

536
00:41:42,975 --> 00:41:45,617
billion dollar industry. I don't know what the numbers are

537
00:41:45,677 --> 00:41:48,819
anymore. Seems really big to me. And all we have

538
00:41:48,879 --> 00:41:51,701
to do is jump into it because these guys want

539
00:41:51,721 --> 00:41:53,402
to spend money and we can get a piece of

540
00:41:53,482 --> 00:41:55,023
it. Oh, we're going to tell you how the spec

541
00:41:55,123 --> 00:42:01,508
is going to work. Because I can tell you? that

542
00:42:02,108 --> 00:42:06,351
none of that would go to Apple. Almost 100% of

543
00:42:06,411 --> 00:42:09,513
it would go to YouTube. Yeah, but... The billion dollars

544
00:42:09,573 --> 00:42:12,915
sitting on the sideline, it's not going equally... It's not

545
00:42:12,935 --> 00:42:15,417
being equally distributed amongst all these players. It's going to

546
00:42:15,477 --> 00:42:20,060
go heavily to YouTube. Well, that's possible. Because they defined

547
00:42:20,080 --> 00:42:24,323
the definition of a podcast away from RSS. Yeah, that's

548
00:42:24,383 --> 00:42:30,027
true. That's true. I also think that the Apple ethos...

549
00:42:31,168 --> 00:42:34,710
is You don't just go do a thing and drop

550
00:42:34,790 --> 00:42:36,752
this spec on us and tell us we have to

551
00:42:36,832 --> 00:42:38,853
do it. That's the quickest way to get them not

552
00:42:38,873 --> 00:42:42,395
to do something. Okay. Well, we shall see. We shall

553
00:42:42,435 --> 00:42:47,959
see. But for sure... Doesn't matter. This movement they have

554
00:42:48,019 --> 00:43:00,468
here. With those Judases over at Libsyn. It doesn't include

555
00:43:00,588 --> 00:43:03,610
us. Let's just be very clear. No, that's for sure.

556
00:43:03,610 --> 00:43:05,871
Let's just be very clear. But I like that position.

557
00:43:06,292 --> 00:43:11,755
I like being different. I like being counterculture. And the

558
00:43:12,055 --> 00:43:16,098
only solution I have, which doesn't help the app developers

559
00:43:16,158 --> 00:43:19,941
yet, but I'm really thinking, how do we evolve the

560
00:43:20,001 --> 00:43:25,224
funding tag? If we could evolve the funding tag. to

561
00:43:25,324 --> 00:43:29,247
help the app developers. And I really, you know, I'm

562
00:43:29,487 --> 00:43:33,450
really looking at different payment systems. And I'm talking boosts

563
00:43:33,590 --> 00:43:38,693
just for, you know, let me send something, a subscription.

564
00:43:38,733 --> 00:43:43,157
There has got to be a way. that this can

565
00:43:43,197 --> 00:43:47,639
be done. And it may take. It may take a

566
00:43:47,720 --> 00:43:52,803
centralized company to do that. I actually have a funny

567
00:43:52,963 --> 00:30:00,000
feeling that X money might might make something possible. -

568
00:43:59,608 --> 00:44:03,110
What is X money? - Oh, that's Elon's everything app

569
00:44:03,130 --> 00:44:07,533
money. Yeah, yeah, you can make the sound, but he's

570
00:44:07,573 --> 00:44:11,255
gonna offer 6% APY interest rate if you store your

571
00:44:11,316 --> 00:44:15,739
money with him. People will flock to it. Isn't this

572
00:44:15,819 --> 00:44:18,681
the second time that X slash Twitter has promised to

573
00:44:18,741 --> 00:44:23,504
be everybody's wallet, though? Well, I... You know what? It's

574
00:44:23,664 --> 00:44:29,988
easier than going to Mars. That is very, I cannot

575
00:44:30,028 --> 00:44:35,832
find fault with that statement. Is there some way? that

576
00:44:35,932 --> 00:44:42,557
we can take this Newly proposed. unratified contact tag from

577
00:44:44,978 --> 00:44:51,683
Daniel and Alex and Filippo. And use that as. The

578
00:44:51,843 --> 00:44:58,107
messaging mechanism. for the for the funding tax somehow this

579
00:44:58,187 --> 00:44:59,888
is all just come up in my head like with

580
00:45:00,860 --> 00:45:03,882
We could always expand the funding tag to add that

581
00:45:04,002 --> 00:45:07,304
in. That would make more sense to have another field

582
00:45:07,465 --> 00:45:11,787
and another destination. Like a linkage. Like if you had

583
00:45:11,807 --> 00:45:19,493
a contact tag that was like the designated message destination

584
00:45:20,213 --> 00:45:27,758
for the funding tag thing. I'm throwing stuff at the

585
00:45:27,758 --> 00:45:31,761
wall here. That's cool. If we're gonna do this... And

586
00:45:32,421 --> 00:45:35,143
we haven't seen a lot of uptake on the funding

587
00:45:35,203 --> 00:45:37,445
tag. And by uptake, I mean not that you have

588
00:45:37,485 --> 00:45:39,346
a dollar sign and you can tap it and it

589
00:45:39,366 --> 00:45:41,848
goes somewhere, but like the boost button. It was a

590
00:45:41,948 --> 00:45:45,070
big-ass button. You know, like, boom, hit this. And I

591
00:45:45,110 --> 00:45:48,112
understand why. The only way I think we should develop

592
00:45:48,172 --> 00:45:50,554
this, if we can figure out a way that we

593
00:45:50,654 --> 00:45:54,737
can get some of that money to an app developer.

594
00:45:56,077 --> 00:46:01,381
And that's the only way I really want to do

595
00:46:01,381 --> 00:46:05,604
it. do it because otherwise we're just killing ourselves. Or

596
00:46:05,924 --> 00:46:11,828
they're being eschewed. They're being eschewed. Right. If we can

597
00:46:12,489 --> 00:46:17,132
turn that around. And that was kind of the beauty

598
00:46:17,272 --> 00:46:20,874
of Lightning is we had the splits. The splits was

599
00:46:21,014 --> 00:46:24,737
really the thing. You had a split for the app.

600
00:46:24,757 --> 00:46:30,641
You could put splits in however you wanted to do

601
00:46:31,261 --> 00:46:34,664
it. And it could be for bigger amounts. We don't

602
00:46:34,704 --> 00:46:38,406
have to do the micropayments. But if I knew that

603
00:46:39,907 --> 00:46:44,470
certain apps were surfacing a big donate, give, boost, whatever

604
00:46:44,550 --> 00:46:46,652
button you want to call it, I tell people to

605
00:46:46,752 --> 00:46:48,473
use that app. Hey, it's right in your app. Hit

606
00:46:48,533 --> 00:46:53,116
that now. But it has to benefit them as well.

607
00:46:53,116 --> 00:46:56,498
I agree. Otherwise, I don't think we should even work

608
00:46:56,638 --> 00:47:01,682
on it until we figure that part out. All the

609
00:47:01,742 --> 00:47:04,984
same problems come into play. Money transmitter licenses, you know,

610
00:47:05,084 --> 00:47:10,648
all this stuff. How does, so what Buzzsprout does, they

611
00:47:10,728 --> 00:47:16,012
do that from the hosting side. Yes. And so I

612
00:47:16,112 --> 00:47:19,254
presume that they're taking a platform fee for doing it.

613
00:47:20,074 --> 00:47:24,297
should be i don't know about that i i don't

614
00:47:24,557 --> 00:47:27,539
i if i remember correctly when at least when they

615
00:47:27,599 --> 00:47:29,481
rolled it out i don't know about the current state

616
00:47:29,661 --> 00:47:31,822
but at least when they rolled it out i'm almost

617
00:47:31,942 --> 00:47:36,746
positive that they said this was just a service to

618
00:47:36,806 --> 00:47:39,788
their to their podcasters they were not going to take

619
00:47:39,828 --> 00:47:44,331
any sort of cut they should they just they yeah

620
00:47:44,431 --> 00:47:50,195
the the thing about like i was praising the the

621
00:47:50,495 --> 00:47:58,180
Buzzsprout solution last week and I think part of that

622
00:47:58,280 --> 00:48:10,568
solution could be if you had a verified Daniel J.

623
00:48:10,769 --> 00:48:13,150
Lewis is in the boardroom. He says, if an app

624
00:48:13,190 --> 00:48:18,914
developer offers a strike... they can take a fee from

625
00:48:18,974 --> 00:48:25,098
the payment. That's interesting. So does that mean that I

626
00:48:25,138 --> 00:48:28,901
would have to register my podcast with every single app?

627
00:48:30,522 --> 00:48:33,384
problem actually it's not that big of a deal no

628
00:48:33,664 --> 00:48:40,629
i mean you could single sign-up sheet that could That's

629
00:48:40,789 --> 00:48:43,791
not that crazy. But you'd have to sign up with

630
00:48:43,931 --> 00:48:46,032
every app. Well, I'll tell you what, that would take

631
00:48:46,092 --> 00:48:47,834
me a couple hours on an afternoon. I'd sign up

632
00:48:47,874 --> 00:48:52,297
with every app that offered that. Let's go. The other

633
00:48:52,337 --> 00:48:56,700
way to do it is if you have a third

634
00:48:56,760 --> 00:49:00,802
party or a hosted platform, tell me where I'm messing

635
00:49:00,902 --> 00:49:04,165
up. Tell me what I'm missing here. If you had

636
00:49:04,225 --> 00:49:08,227
the bus route model, I'm in the app. I tap.

637
00:49:09,548 --> 00:49:36,006
And it. doing, you know, this. Can't the service... if

638
00:49:38,688 --> 00:49:45,373
and Striper Card. to each individual. And then the podcast

639
00:49:45,573 --> 00:49:48,735
app is the one that takes a platform fee and

640
00:49:48,735 --> 00:49:51,477
sends the money directly to the podcast app. my Stripe

641
00:49:51,557 --> 00:49:58,381
account. Is that correct, Daniel? That's interesting. Here's what I'm

642
00:49:58,441 --> 00:50:09,809
trying to avoid. you The effectiveness or the excuse me

643
00:50:09,849 --> 00:50:17,114
the adoption on the app side. Lightning was a heavy

644
00:50:17,214 --> 00:50:19,736
lift on a technical stem from a technical standpoint. That's

645
00:50:19,836 --> 00:50:27,061
not. that but the other i think thing was that

646
00:50:27,081 --> 00:50:31,304
app developers are scared about getting in the money. they

647
00:50:31,344 --> 00:50:34,366
don't want to be the ones that dole out the

648
00:50:34,426 --> 00:50:38,709
cash. The way I understand it, a stripe is pretty

649
00:50:38,769 --> 00:50:45,333
interesting. with Stripe. They do have a lot of... and

650
00:50:45,393 --> 00:50:51,958
do things. And if you are just connecting, if you

651
00:50:52,038 --> 00:50:56,060
just have a Stripe account and... A podcaster has to

652
00:50:56,120 --> 00:51:02,265
connect to you. which I made it. out then you're

653
00:51:02,285 --> 00:51:05,086
not handling any money it's automatic stripe does that on

654
00:51:05,147 --> 00:51:09,890
the back end for you I don't think I'm following

655
00:51:09,950 --> 00:51:13,432
can you explain this to me again Daniel J. Lewis

656
00:51:13,913 --> 00:51:16,774
is saying, and I've looked into Stripe just before we

657
00:51:16,855 --> 00:51:20,037
started actually, but I was a little fuzzy. So the

658
00:51:20,177 --> 00:51:24,920
app developer has a Stripe account. And then... You hit

659
00:51:25,040 --> 00:51:33,926
the... your story. to the podcast app strike account. And

660
00:51:33,986 --> 00:51:36,648
so when you, when someone hits the boost button, the

661
00:51:36,708 --> 00:51:46,114
funding button, the donate button, whatever, then it goes. collected

662
00:51:46,274 --> 00:51:51,618
by the app developer. your piece, podcaster piece, is directly

663
00:51:51,718 --> 00:51:54,520
sent to your Stripe account. So it's a form of

664
00:51:54,560 --> 00:52:00,744
a split. I think I would have to... We gotta

665
00:52:00,804 --> 00:52:02,565
look at it. We gotta look at it. Yeah, I'm

666
00:52:02,625 --> 00:52:04,287
just too visual. I think I just need to see

667
00:52:04,427 --> 00:52:17,035
it. I see strings. Hmm. Let's just presume that worked.

668
00:52:19,117 --> 00:52:24,260
Okay. I mean, so I'd have to connect my podcast

669
00:52:24,340 --> 00:52:33,526
to a couple of different apps. You know? Daniel says,

670
00:52:33,546 --> 00:52:36,909
I'm using clerk.com as my authentication and payment system for

671
00:52:36,969 --> 00:52:42,733
Podchats. Stripe account, but Clerk manages the payment page and

672
00:52:42,773 --> 00:52:47,196
subscriptions. So Clerk, not Stripe, is doing the recurring payments.

673
00:52:47,296 --> 00:52:50,398
Then whenever I get paid in my Stripe account, I

674
00:52:50,478 --> 00:52:56,242
see that Clerk got a 0.7% fee from it. Right.

675
00:52:56,322 --> 00:52:58,463
But then you still have to signal. The problem is

676
00:52:58,523 --> 00:53:01,425
the signaling. How do you signal from a tag in

677
00:53:01,485 --> 00:53:05,028
the RSS feed that this is me, this is my

678
00:53:05,148 --> 00:53:12,433
podcast Stripe account? through this app. So that's where I'm

679
00:53:12,513 --> 00:53:19,918
saying that if you use... You have a ma- Like

680
00:53:20,218 --> 00:53:29,124
in Buzzsprout's case. the payment in If they... verify That

681
00:53:29,184 --> 00:53:35,628
that payment came from Castamatic and Franco has set up

682
00:53:35,668 --> 00:53:38,690
the relationship and is like, you know, shown that maybe.

683
00:53:40,492 --> 00:53:46,496
Here's how you pay me address. They can just turn

684
00:53:46,536 --> 00:53:51,419
around and take a, you know, half a percent and

685
00:53:51,459 --> 00:53:59,184
shoot it to Franco. by some money transmitter platform that

686
00:53:59,224 --> 00:54:02,607
has all the licenses and does all that. Or maybe

687
00:54:02,707 --> 00:54:06,689
Franco goes and gets a subscription, a podcast app developer

688
00:54:06,749 --> 00:54:12,213
subscription. And I'm using. this is what I've seen before.

689
00:54:12,493 --> 00:54:15,135
But this could be, Daniel J. Lewis could build this.

690
00:54:16,756 --> 00:54:22,740
He could build a thing that says podcast, you know,

691
00:54:23,421 --> 00:54:31,126
podcast payments doc. something and and it operates just like

692
00:54:31,226 --> 00:54:36,249
this it takes sort of like an escrow for the

693
00:54:36,289 --> 00:54:45,255
podcaster and then just disseminates it or whatever. Again, we're

694
00:54:45,376 --> 00:54:47,977
throwing everything at the wall. And the sad part is

695
00:54:48,037 --> 00:54:50,679
we solved all of this with lightning. We did all

696
00:54:50,739 --> 00:54:53,161
this. We did all this work. We had it all

697
00:54:53,161 --> 00:55:00,446
figured out. I know. I know. And it almost works.

698
00:55:01,006 --> 00:55:07,330
Even right now. Yeah, I don't know, man. I don't

699
00:55:07,370 --> 00:55:13,835
know. Maybe just this is the idea. Yeah. Phase of

700
00:55:13,895 --> 00:55:16,857
this. Well, Daniel J is smart. He'll think about it.

701
00:55:19,219 --> 00:55:22,861
I'm too foggy. I did want to talk about this.

702
00:55:23,081 --> 00:55:27,984
I did want to talk about this new podcast app

703
00:55:29,586 --> 00:55:34,409
that strips out sponsor messages and commercials and all that

704
00:55:34,469 --> 00:55:38,231
stuff. I briefly saw that go by. I don't remember

705
00:55:38,331 --> 00:55:43,455
what it was called or anything. I tried before I

706
00:55:44,175 --> 00:55:46,697
forgot what it's called like ear say or something like

707
00:55:46,737 --> 00:55:51,160
that. It stripped out anything it stripped out like Stuff

708
00:55:51,300 --> 00:55:53,402
all over the podcast that was not ads like whole

709
00:55:53,462 --> 00:55:56,284
sections of the podcast would disappear right because it thought

710
00:55:56,304 --> 00:55:59,626
it was talking about an advertisement Right, right, right, right

711
00:56:00,987 --> 00:56:13,435
So this app is called Podtastic. Podtastic! And I downloaded

712
00:56:13,455 --> 00:56:16,677
Podtastic, and it's actually not even that bad of an

713
00:56:16,817 --> 00:56:20,460
app. Really? Yeah. Let me just bring it up here.

714
00:56:21,000 --> 00:56:29,506
Podtastic. And, you know, forget the Podtastic. There we go.

715
00:56:29,946 --> 00:56:32,448
Forget for a moment the stripping out, you know, and

716
00:56:32,468 --> 00:56:35,390
it charges you money and stuff and whatever. Forget for

717
00:56:35,430 --> 00:56:37,672
a moment the stripping out ad stuff. But what it's

718
00:56:37,692 --> 00:56:43,716
doing is it's creating chapters. that it thinks is a

719
00:56:43,756 --> 00:56:49,039
chapter. It's played a lot of chapters, actually. It's exactly

720
00:56:49,079 --> 00:56:52,342
what I've been... It is trying to, and you can

721
00:56:52,582 --> 00:56:54,563
feed back like, you know, I didn't like this. I

722
00:56:54,623 --> 00:56:56,504
did like that. It didn't, you know, this was not

723
00:56:56,584 --> 00:57:00,867
relevant to me. that is, I guess, maybe not in

724
00:57:00,907 --> 00:57:05,270
this form, but moving forward, will start to customize the

725
00:57:05,390 --> 00:57:11,034
additional things around the actual podcast to your preferences. Okay.

726
00:57:11,775 --> 00:57:18,139
And that's interesting. And so, you know, it would be

727
00:57:18,359 --> 00:57:24,743
quite trivial in general to create a podcast app, a

728
00:57:24,824 --> 00:57:28,746
client side app that, you know, just says, you know

729
00:57:28,806 --> 00:57:32,188
what? just strip out the first two minutes of pivot

730
00:57:32,188 --> 00:57:34,850
because I hate those ads. And it would do that.

731
00:57:36,972 --> 00:57:42,515
It would do that. But that's just like low-hanging fruit.

732
00:57:43,116 --> 00:57:46,678
Really, that's what you're going to market on? But doing

733
00:57:46,758 --> 00:57:50,921
other things and looking for other podcasts and different episodes

734
00:57:50,961 --> 00:57:52,862
or people who, you know, a lot of the stuff

735
00:57:52,922 --> 00:57:56,565
we already have. like person tag. There's so much that

736
00:57:56,905 --> 00:57:59,587
you can have your podcast app do. Make it smarter.

737
00:58:01,128 --> 00:58:05,411
And so this just happens to, you know, the marketing

738
00:58:05,731 --> 00:58:08,713
ploy here is, oh, no more ads, which is just

739
00:58:08,833 --> 00:58:14,637
mean. It's not like it's illegal. To me, it's not

740
00:58:14,697 --> 00:58:17,539
illegal. I don't think it's illegal. You download the podcast.

741
00:58:17,579 --> 00:58:20,101
You do whatever you want. You can strip out the

742
00:58:20,221 --> 00:58:23,763
ads. You do whatever you want. That's fine. As long

743
00:58:23,783 --> 00:58:26,005
as they're not re-hosting it and it's all happening on

744
00:58:26,065 --> 00:58:29,827
device, there's really nothing legal there. But I'm saying that's

745
00:58:29,847 --> 00:58:34,030
the future. People will want this. Phones are going to

746
00:58:34,671 --> 00:58:37,553
be doing this, all this stuff. And by the way,

747
00:58:37,593 --> 00:58:42,736
just as a throwback to the amp stuff. Ultimately, the

748
00:58:42,896 --> 00:58:45,398
app doesn't decide what's going to happen. It's your phone.

749
00:58:46,599 --> 00:58:49,181
And the person who owns the phone, i.e. Apple or

750
00:58:49,241 --> 00:58:53,303
Google, they're going to decide what comes and goes, and

751
00:58:53,423 --> 00:58:57,866
they're going to want a piece. It's all so messed

752
00:58:57,947 --> 00:59:03,630
up. It's all messed up. Back to browsers. Back to

753
00:59:03,670 --> 00:59:10,655
browsers, I tell you. Well, yeah, that's the sort of

754
00:59:10,655 --> 00:59:17,179
idea. there is in this moment where they are introducing

755
00:59:17,440 --> 00:59:20,682
all this heavy lift and all these specifications to support

756
00:59:22,663 --> 00:59:25,945
And I honestly, I don't see, I don't see that

757
00:59:27,066 --> 00:59:31,509
the... are going to do that either. I know they

758
00:59:31,549 --> 00:59:34,271
had all these people in the room, but that doesn't

759
00:59:34,271 --> 00:59:37,273
mean they're actually going to do it. No. And so,

760
00:59:38,974 --> 00:59:43,477
like, Adam... At the moment where they're introduced, heavy lift

761
00:59:44,778 --> 00:59:48,140
you also at the same exact time see apps like

762
00:59:48,201 --> 00:59:54,164
this trying to strip the ads out completely altogether. Advertising

763
00:59:54,605 --> 00:59:58,467
in general is old fashioned now with ads inserted and

764
00:59:58,487 --> 00:59:59,989
all that stuff. That's all gonna go away.

765
01:00:01,240 --> 01:00:05,743
It's all going to go away. Yes, with LLMs on

766
01:00:05,803 --> 01:00:09,246
your device, it's all going to go away. It's going

767
01:00:09,246 --> 01:00:13,489
to be a beautiful world for you as a consumer,

768
01:00:13,609 --> 01:00:15,650
as a listener, as a viewer. You're going to be

769
01:00:15,650 --> 01:00:18,072
able to do a lot of things. And if the

770
01:00:18,132 --> 01:00:24,196
programmatic ads go away, then it makes a real... meaningful

771
01:00:24,376 --> 01:00:29,379
dent in the slop problem too. Yes. Oh, and I've

772
01:00:29,419 --> 01:00:33,462
always said that's transitory. Yeah, you have. Yeah, that's been

773
01:00:33,482 --> 01:00:36,364
your point. That's just because what can I do? What

774
01:00:36,384 --> 01:00:37,645
can I do with this? What can I do with

775
01:00:37,685 --> 01:00:41,628
this? What can I do? I can set up these

776
01:00:41,768 --> 01:00:45,510
three agents and I'll get up with podcasts. Yeah. It'll

777
01:00:45,510 --> 01:00:49,893
be $400 of extra ad income. Dana Brunetti. You know

778
01:00:49,913 --> 01:00:54,176
who Dana Brunetti is? A Netflix guy, right? No, no.

779
01:00:54,296 --> 01:00:57,899
Danny Brunetti is a big-time Hollywood producer who left Hollywood

780
01:00:57,899 --> 01:01:01,501
because he hates it so much. But he did. He

781
01:01:01,601 --> 01:01:08,946
produced The Social Network, Captain Phillips, House of Cards. His

782
01:01:09,026 --> 01:01:13,689
big money came from Fifty Shades of Grey. That's the

783
01:01:13,749 --> 01:01:15,971
big money. I thought that movie didn't do good at

784
01:01:15,991 --> 01:01:20,534
the box office. Huge money. Really? Oh, no. That's like

785
01:01:20,554 --> 01:01:23,956
$100,000 a month checks. Of course it's porn. Yeah, Fifty

786
01:01:24,036 --> 01:01:28,159
Shades of Greyer. He did a follow-up. And what was

787
01:01:28,239 --> 01:01:32,602
it? The Grand Prix movie, which I think was Sony

788
01:01:32,702 --> 01:01:36,945
paid for. So he's a nerd. And he was, we

789
01:01:37,005 --> 01:01:39,907
were pretty, I'm friends with him. He was good friends

790
01:01:39,947 --> 01:01:42,249
with John. And so I've been talking to him a

791
01:01:42,309 --> 01:01:44,370
lot. And then John would say, call Adam about that.

792
01:01:44,931 --> 01:01:47,913
And he was sitting at home with Claude Code. And

793
01:01:47,973 --> 01:01:51,355
he's like, look at this, man. I made a podcast.

794
01:01:51,755 --> 01:01:56,458
It's a news podcast for just my local area. And,

795
01:01:56,458 --> 01:01:57,859
you know, I listened to it. Yeah, it was great.

796
01:01:58,039 --> 01:01:59,700
He happened to live up where he lives in the

797
01:01:59,740 --> 01:02:03,083
farm country in Northern California. And, you know, and he

798
01:02:03,123 --> 01:02:06,885
was just scanning feeds and pulling it in and a

799
01:02:06,985 --> 01:02:12,149
TTS model and boom. And, but he was really only

800
01:02:12,169 --> 01:02:14,570
doing it because he could. And then I said, Dana,

801
01:02:14,631 --> 01:02:16,992
you're a producer. Tell me how you're going to make

802
01:02:17,012 --> 01:02:19,714
money on this. Please explain to me where the money

803
01:02:19,834 --> 01:02:22,356
is. And he comes back a few weeks later, said,

804
01:02:22,556 --> 01:02:25,898
nope, there's no money. It says, just, I can't make

805
01:02:25,978 --> 01:02:30,381
it work. And it's true. You know, he said, I

806
01:02:30,461 --> 01:02:33,123
have to create so much at such a scale in

807
01:02:33,203 --> 01:02:35,004
order to get, you know, a thousand bucks out of

808
01:02:35,084 --> 01:02:36,946
it. He says, no, it's not worth it. But he

809
01:02:37,026 --> 01:02:39,427
liked it and he liked it for himself. And that's

810
01:02:39,487 --> 01:02:43,850
my point. So creating that for your little community, valid,

811
01:02:44,070 --> 01:02:47,853
great, fantastic. You be the guy. Have people buy you

812
01:02:47,933 --> 01:02:51,676
a coffee and chip in for your token cost. Or

813
01:02:51,736 --> 01:02:58,680
your server chip in. Or for your server that's running

814
01:02:58,720 --> 01:03:04,224
at home. So We are entering a world and we

815
01:03:04,284 --> 01:03:06,125
can be ahead of a lot of this. We can

816
01:03:06,165 --> 01:03:09,147
be way ahead in creating great experiences for our true

817
01:03:09,228 --> 01:03:12,630
customer, which is the listener. For me, that's the listener.

818
01:03:12,750 --> 01:03:16,572
And for the podcast app developers, that's the listener. That's

819
01:03:16,592 --> 01:03:20,655
the user of their app. I think we can accelerate

820
01:03:20,755 --> 01:03:25,619
far beyond and be much faster than anyone else. It's

821
01:03:25,659 --> 01:03:30,962
my dream. Claude Opus 5 is released. Oh, so yeah,

822
01:03:30,982 --> 01:03:34,324
I wanted to play this clip. This is, I mean,

823
01:03:34,525 --> 01:03:38,527
I love a news story that is just so obviously

824
01:03:38,728 --> 01:03:43,431
blatant marketing. Yeah, I know. You're going to talk about

825
01:03:43,451 --> 01:03:48,334
the OpenAI hacking, hugging face, right? An unprecedented AI security

826
01:03:48,354 --> 01:03:53,477
incident. Chad's EPT creator, OpenAI, says two of its models

827
01:03:53,878 --> 01:03:58,641
escaped controls and successfully hacked into another AI company. OpenAI

828
01:03:58,821 --> 01:04:01,223
says they are, the way they describe it, is responding

829
01:04:01,283 --> 01:04:05,145
accordingly. But they also say this involves state-of-the-art technology and

830
01:04:05,285 --> 01:04:11,049
is unprecedented. Unprecedented. Claire Duffy for more on this. Good

831
01:04:11,129 --> 01:04:13,611
news. Yeah, Kate, this kind of sounds like the plot

832
01:04:13,711 --> 01:04:16,013
of a sci-fi movie, but it is indeed happening in

833
01:04:16,113 --> 01:04:18,514
real life. This is the first major example that we've

834
01:04:18,554 --> 01:04:22,477
seen of an AI model independently conducting a hack outside

835
01:04:22,557 --> 01:04:25,779
of human control. And this is something that experts have

836
01:04:25,819 --> 01:04:28,521
been warning about. This is also driving some of these

837
01:04:28,581 --> 01:04:30,703
conversations that we've heard. This is CNN, by the way.

838
01:04:30,703 --> 01:04:33,104
That's why I pulled this one specifically, just to get

839
01:04:33,184 --> 01:04:36,006
the urgency and the excitement. Including at the White House

840
01:04:36,106 --> 01:04:41,710
about increasing controls and oversight of AI models. of exactly

841
01:04:41,750 --> 01:04:44,732
this sort of hack. Now what happened here is that

842
01:04:44,812 --> 01:04:48,435
OpenAI was testing these models. It had lowered its normal

843
01:04:48,515 --> 01:04:51,297
safeguards in order to test these two models, which is

844
01:04:51,617 --> 01:04:55,439
GPT 5.6 Sol and also a new unreleased more advanced

845
01:04:55,559 --> 01:04:57,941
model. More advanced? You don't have it yet, but what

846
01:04:57,981 --> 01:05:00,483
we got here in the closet is amazing. It lowered

847
01:05:00,523 --> 01:05:02,904
its safeguards because it thought it was testing in what

848
01:05:02,985 --> 01:05:05,546
is called a sandbox. Oh, it was in the sandbox.

849
01:05:05,586 --> 01:05:09,309
Don't worry, people. It was what is called a sandbox.

850
01:05:10,049 --> 01:05:18,595
Sandbox. virtual lab. But when it gave these models a

851
01:05:18,675 --> 01:05:21,577
task to test their hacking capabilities, the models went to

852
01:05:21,677 --> 01:05:25,640
such great lengths to complete that task that it found

853
01:05:25,720 --> 01:05:28,922
vulnerabilities that allowed them to access the open internet outside

854
01:05:28,982 --> 01:05:32,404
of this controlled testing environment. They then hacked into Hugging

855
01:05:32,565 --> 01:05:34,966
Face, which is a platform that hosts all kinds of

856
01:05:35,106 --> 01:05:39,349
AI models. They used stolen credentials. Hey, don't go to

857
01:05:39,429 --> 01:05:42,451
that cheap Chinese crap. We're better. We can hack them.

858
01:05:42,691 --> 01:05:45,653
Look what we can do. We're better. The AI war

859
01:05:45,773 --> 01:05:50,096
is over. We beat China. Stolen logins to navigate that

860
01:05:50,176 --> 01:05:54,619
platform. And ultimately, this hack was identified by Hugging Face

861
01:05:54,780 --> 01:05:57,762
in part because of artificial intelligence, which they used to

862
01:05:57,842 --> 01:06:00,583
shut it down. But this is a huge warning sign

863
01:06:00,724 --> 01:06:04,786
for this industry. In a statement, OpenAI said, we consider

864
01:06:04,826 --> 01:06:09,309
this incident to be an unprecedented cyber incident involving state-of-the-art

865
01:06:09,470 --> 01:06:11,971
capabilities and our response. How many times are they going

866
01:06:11,991 --> 01:06:13,692
to say that? State of the art. State of the

867
01:06:13,772 --> 01:06:17,055
art. Wait for the payoff. We are sharing preliminary findings

868
01:06:17,115 --> 01:06:20,597
at this stage to help defenders understand what happened and

869
01:06:20,757 --> 01:06:23,719
to help calibrate on what models are now capable of.

870
01:06:23,779 --> 01:06:25,380
I think that is the real key here is that

871
01:06:25,460 --> 01:06:28,722
models are now capable of conducting these kinds of hacks

872
01:06:28,903 --> 01:06:32,125
independently. Yeah, the statements from both the companies seem to

873
01:06:32,165 --> 01:06:35,527
be somewhat in awe that it actually happened, but it

874
01:06:35,647 --> 01:06:40,931
is terrifying. It's terrifying. It's terrifying. It's terrifying. Be terrified.

875
01:06:40,931 --> 01:06:45,314
be more terrified. I mean, it's so obvious. Anthropic had

876
01:06:45,394 --> 01:06:49,296
their, oh no, we have a model here that is

877
01:06:49,376 --> 01:06:52,879
so cyber hacker aware that we can only give it

878
01:06:52,939 --> 01:06:55,521
to the banks first because, oh, this is just too

879
01:06:55,561 --> 01:06:59,123
much. And then OpenAI comes out. We got those cheap

880
01:06:59,243 --> 01:07:01,385
model guys. They had to come to us and beg

881
01:07:01,525 --> 01:07:04,987
us for help to use our models to combat the

882
01:07:05,067 --> 01:07:09,710
hack that our models did on their model. Bull crap.

883
01:07:11,992 --> 01:07:16,755
The... It's like our model. beat the shit out of

884
01:07:16,775 --> 01:07:21,078
their model. It went in. It didn't just hack Hugging

885
01:07:21,178 --> 01:07:24,720
Face. It hacked Hugging Face and stole all the Chinese

886
01:07:24,800 --> 01:07:29,784
models. It's so good that we couldn't even keep it

887
01:07:29,824 --> 01:07:35,928
in the sandbox. The sandbox was full of poop. They

888
01:07:35,968 --> 01:07:38,250
didn't tell you that they forgot to like, that they

889
01:07:38,470 --> 01:07:41,692
accidentally left the hugging face like SSH key sitting there

890
01:07:41,712 --> 01:07:43,333
or something like that. I love it. I love it.

891
01:07:43,393 --> 01:07:47,436
Yeah. And then they did like a SQL injection. Okay.

892
01:07:47,576 --> 01:07:53,140
Sure. Sure. Like, and I'm thinking hugging face, hugging face.

893
01:07:53,260 --> 01:07:57,943
Really? If you, if you're hugging face, which is probably

894
01:07:58,043 --> 01:08:02,306
90% built with vibe coding, if you're hugging face and

895
01:08:02,346 --> 01:08:05,568
you've got your stuff hacked. What it kind of, this

896
01:08:05,648 --> 01:08:10,291
whole thing is, this is Doom trolling. to the nth

897
01:08:10,371 --> 01:08:14,534
degree. Yeah. Like, this is so stupid. The New York

898
01:08:14,534 --> 01:08:18,317
Times article I read called, it didn't say hugging face.

899
01:08:19,177 --> 01:08:22,900
It said open AIs. A new top secret security model

900
01:08:22,960 --> 01:08:29,504
hacked into a library. Ooooooh! It called Hugging Face something

901
01:08:29,564 --> 01:08:32,606
like an open library or something. I was like, archive.org?

902
01:08:32,686 --> 01:08:35,408
What are we talking about? First of all, Gail Mann

903
01:08:35,448 --> 01:08:39,591
amnesia. So when you read that, you can't believe anything

904
01:08:39,651 --> 01:08:43,514
else that you read in the New York Times. So

905
01:08:43,614 --> 01:08:49,178
apparently what happened is they had this... This model was

906
01:08:49,198 --> 01:08:53,340
sandboxed, but it could access some kind of worker box

907
01:08:54,221 --> 01:08:57,363
that had libraries that if it needed, but that was

908
01:08:57,423 --> 01:08:59,364
also not connected to the internet, but it hacked the

909
01:08:59,444 --> 01:09:02,426
worker box and the worker box. Then they went through

910
01:09:02,447 --> 01:09:04,988
there to get to someone's, you know, PC on a

911
01:09:05,008 --> 01:09:07,430
desktop. And that's how they got to the internet. You

912
01:09:07,450 --> 01:09:11,873
know what? Script kiddie stuff. That's how the model does

913
01:09:11,893 --> 01:09:14,775
it. It's what script kiddies do. They keep pounding, keep

914
01:09:14,815 --> 01:09:17,357
pounding. Oh, okay, it just can do it faster. Like,

915
01:09:17,557 --> 01:09:20,959
and, you know, come on, please. They made this happen.

916
01:09:21,139 --> 01:09:24,181
Don't even think about it. Oh, who's, where's the proof?

917
01:09:24,401 --> 01:09:26,823
There's no evidence it was sandboxed and it was supposed

918
01:09:26,843 --> 01:09:29,345
to be all secret. Oh, we can't believe this happened.

919
01:09:29,705 --> 01:09:31,906
Blah, blah, blah, blah. No, we can. We love it

920
01:09:31,947 --> 01:09:34,268
that this happened. We beat the cheap guy. You don't

921
01:09:34,288 --> 01:09:38,191
want those cheap guys. Hey, hey, hey, Mr. Corporate Fortune

922
01:09:38,231 --> 01:09:40,352
500, you don't want to use Hugging Face. with their

923
01:09:40,392 --> 01:09:42,574
models, with their cheap models that your IT department is

924
01:09:42,594 --> 01:09:44,935
saying is much cheaper. You don't want that because look

925
01:09:44,955 --> 01:09:47,017
what can happen. Look what can happen. You want the

926
01:09:47,137 --> 01:09:50,559
big guys, the big boys, the frontier, the frontier of

927
01:09:50,659 --> 01:09:57,924
everything. You want to be with us. obvious. Yeah, it

928
01:09:57,944 --> 01:10:00,586
says, the incident which happened last week while OpenAI was

929
01:10:00,646 --> 01:10:03,688
testing the cybersecurity capabilities of systems displayed the kind of

930
01:10:03,788 --> 01:10:08,731
science fiction potential that AI companies warned would soon become

931
01:10:08,791 --> 01:10:15,496
a reality. Where's my theremin when I need it? I

932
01:10:15,556 --> 01:10:20,419
mean, this is... I'm so sick of this crap. Yes,

933
01:10:20,639 --> 01:10:25,323
reality. We are implementing strict controls in infrastructure configuration at

934
01:10:25,363 --> 01:10:29,586
the cost of research velocity while the vulnerabilities are patched.

935
01:10:31,927 --> 01:10:36,850
Research, we have to stop our research velocity. It's too

936
01:10:36,951 --> 01:10:43,675
fast. He's spinning out of control. Show title, Research Velocity.

937
01:10:44,075 --> 01:10:49,499
I like it. Yeah. That's what happened with amp. Just

938
01:10:49,499 --> 01:10:53,121
got too fast. The research velocity just got out of

939
01:10:53,121 --> 01:10:57,324
control. Off the rails with the research velocity. That's too

940
01:10:57,404 --> 01:11:01,707
funny. Can we talk about pod thing? Yeah, please. Because

941
01:11:01,967 --> 01:11:04,129
I did some stuff this week. Dave did some stuff,

942
01:11:04,229 --> 01:11:08,132
everybody. I did a lot of stuff. Actually, a lot

943
01:11:08,172 --> 01:11:13,996
of stuff. Did some stuff. Yes. trying to currently get

944
01:11:14,196 --> 01:11:23,522
out of of my remote desktop inception that I have

945
01:11:23,562 --> 01:11:25,864
going on here that is confusing the crap out of

946
01:11:25,884 --> 01:11:34,309
me. Okay, here we go. Pod, yeah. So, Podping... .cloud

947
01:11:35,430 --> 01:11:43,636
is now fully Operational. Okay. Wow. With gossip. P2P gossip

948
01:11:43,776 --> 01:11:48,699
over Eero protocol. Okay, so is there something I can

949
01:11:48,779 --> 01:11:51,841
look or it only works if I have the... Well,

950
01:11:51,841 --> 01:11:53,963
the question is, do you even know what I'm talking

951
01:11:53,983 --> 01:11:56,604
about? No, I have no idea, but I want to

952
01:11:56,644 --> 01:12:00,367
go to podping.cloud and see if I can do something

953
01:12:00,427 --> 01:12:02,969
there. Well, there's nothing there. No, there's nothing. I mean,

954
01:12:03,209 --> 01:12:08,012
there's stuff. There's something there, but... Oh, all right. Yeah,

955
01:12:08,532 --> 01:12:15,737
uh... So what this means is. that There's now, so

956
01:12:16,058 --> 01:12:18,940
each, so there's five, just to recap real quick, there's

957
01:12:19,040 --> 01:12:22,882
five podping.cloud hosts that are all load balanced under the,

958
01:12:23,122 --> 01:12:26,985
behind the domain of podping.cloud. Yeah. So if you send

959
01:12:27,065 --> 01:12:29,567
a podping to any of, to podping.cloud, you're going to

960
01:12:29,587 --> 01:12:31,288
get, it's going to hit one of those five hosts

961
01:12:31,388 --> 01:12:44,096
round robin. So... Um... Four. Podping.cloud nodes would just write

962
01:12:44,517 --> 01:12:52,302
the incoming podpings to the Hive blockchain. And the stack

963
01:12:52,762 --> 01:12:56,745
looked something like this. There was a front-end web server.

964
01:12:58,326 --> 01:13:11,295
And... which exposed a ZMQ zero MQ socket. On top

965
01:13:11,375 --> 01:13:17,079
of that socket you had... A Cap'n Proto protocol layer

966
01:13:17,199 --> 01:13:25,404
delivering messages with... Alex Gates' Plexo. type control system. Okay.

967
01:13:26,045 --> 01:13:30,548
These messages would write. to the ZMQ socket and on

968
01:13:30,588 --> 01:13:33,610
the other end of the socket. The only thing that

969
01:13:33,670 --> 01:13:37,793
was listening was the Hive Rider. Right. Hive Rider would

970
01:13:37,833 --> 01:13:44,738
accept the ping. and give back, sometimes in batches. maybe

971
01:13:45,298 --> 01:13:48,100
10 or 12 at a time. It would accept those,

972
01:13:48,800 --> 01:13:51,142
write them to the Hive blockchain, and then send an

973
01:13:51,462 --> 01:13:55,345
ACK. back through the socket saying hey yeah we're good

974
01:13:55,385 --> 01:14:01,049
it's written dequeue it That is basically... What, DQ? What

975
01:14:01,089 --> 01:14:05,151
is DQ? Remove it from the queue. Oh, okay. So

976
01:14:05,472 --> 01:14:08,314
it's like I've handled your ping that you gave me

977
01:14:08,374 --> 01:14:11,636
to write. Take it out. Stop trying to send it.

978
01:14:14,638 --> 01:14:16,439
So that is the way this thing has always worked.

979
01:14:17,860 --> 01:14:28,547
Now. It's writing. over two. sockets. So now it's writing

980
01:14:28,607 --> 01:14:34,251
to multiple, excuse me, podping.cloud frontend is sending to multiple

981
01:14:34,371 --> 01:14:38,694
writers. The first, it's still sending the hive. That will

982
01:14:38,734 --> 01:14:43,357
continue. Right. No change there. But there's a second rider

983
01:14:43,457 --> 01:14:50,502
now, which is riding to... pings to the Eero gossip

984
01:14:50,682 --> 01:14:56,506
channel. Okay, so we have parallel systems. Correct. Correct. Sounds

985
01:14:56,566 --> 01:14:59,728
good. Sounds like a reasonable thing to do. Redundancy.

986
01:15:00,079 --> 01:15:02,221
Do you have it sandboxed or can it get out?

987
01:15:02,981 --> 01:15:05,363
No, if it gets out, it's going straight for pod

988
01:15:05,443 --> 01:15:10,947
news. I'm sorry, James, but if this thing escapes containment,

989
01:15:11,107 --> 01:15:18,652
your side is toast. So now this is. Fully deployed.

990
01:15:22,695 --> 01:15:26,698
This was all under the podping.alpha repo, the development work.

991
01:15:27,518 --> 01:15:30,100
Everything proved out. It ran for a few months with

992
01:15:30,200 --> 01:15:35,283
no... Real issues. So the thing that I did this

993
01:15:35,363 --> 01:15:39,286
week is breaking out each one of the different parts

994
01:15:39,346 --> 01:15:44,289
of the system into their own repos. So now... Uh...

995
01:15:45,710 --> 01:15:50,554
the everything's split out. There's the podping.cloud with those changes

996
01:15:50,714 --> 01:15:56,678
and that is fully Dockerized, Docker composed. I'm riding the

997
01:15:56,778 --> 01:16:03,102
sysadmin. train here. And then you also have the pod

998
01:16:03,182 --> 01:16:09,186
ping dash gossip writer repo, which is the writing portion

999
01:16:09,246 --> 01:16:14,130
which sends pings to the network. You have the Podping-Gossip

1000
01:16:14,270 --> 01:16:18,873
Watcher. which is a standalone. You can run it by

1001
01:16:19,093 --> 01:16:21,575
just compiling the executable and running, or you can run

1002
01:16:21,635 --> 01:16:24,857
it with a Docker. With a Docker run. So here's

1003
01:16:24,897 --> 01:16:28,499
my question. If I want to run this. What kind

1004
01:16:28,559 --> 01:16:33,062
of disk space and CPU does this take up? very

1005
01:16:33,122 --> 01:16:37,445
little. On both? Very little. So let me give you

1006
01:16:37,525 --> 01:16:42,909
the... The monitor. Let's see. Pod ping monitor. So go

1007
01:16:42,989 --> 01:16:55,978
to PP monitor. Monitor your pee-pee. ppmonitor.podcastindex.org and this will

1008
01:16:55,998 --> 01:17:01,722
show you the mesh. Mesh. Oh! Whoa, whoa. This is

1009
01:17:01,802 --> 01:17:04,784
what the current swarm looks like. Oh, I love dragging

1010
01:17:04,804 --> 01:17:09,507
these little nodes around. That's sexy. You can drag nodes.

1011
01:17:09,547 --> 01:17:13,650
Why is it moving? What signifies a move? Well, it

1012
01:17:13,750 --> 01:17:16,332
tries to reorganize itself to fit everything on the screen

1013
01:17:16,892 --> 01:17:21,435
as best as it can. Oh. So things in the

1014
01:17:22,136 --> 01:17:31,342
swarm. It's very swarmy. You have a mesh of nodes.

1015
01:17:32,423 --> 01:17:35,585
And you can imagine that with any mesh, you're going

1016
01:17:35,585 --> 01:17:40,848
to have edges. And those edges... Holy crap, that's a

1017
01:17:40,868 --> 01:17:44,091
lot of nodes here. This is cool, guys. And the

1018
01:17:44,191 --> 01:17:51,556
edges are naturally less connected than the internal nodes. People,

1019
01:17:51,596 --> 01:17:56,199
you've got to upgrade to 0.8.0. You're on 0.6.0. Upgrade.

1020
01:17:56,459 --> 01:18:04,784
Upgrade. Okay. You're lagging. So are you. DaveLaptop2. DaveRemote1. DaveRemote

1021
01:18:04,945 --> 01:18:11,029
underscore Nix1. Yeah, but look at Dave underscore laptop 2.

1022
01:18:11,149 --> 01:18:15,752
It's 080. Wait. I'm half upgrade. Dave remote underscore NX1

1023
01:18:15,812 --> 01:18:20,115
is 0.90. That's the top secret version that we can't

1024
01:18:20,155 --> 01:18:22,897
release or else it'll kill everybody. Keep it in the

1025
01:18:22,997 --> 01:18:28,761
sandbox, please. I've only given it to certain partners first

1026
01:18:28,821 --> 01:18:33,564
to make sure that we... This is nicely vibe-coded, man,

1027
01:18:33,684 --> 01:18:37,046
this website. That's good. I like it. Yes, Eric. a

1028
01:18:37,166 --> 01:18:40,349
jiggly blob of nodes that's correct jiggly blob a jiggly

1029
01:18:40,409 --> 01:18:43,030
blob of notes very nice i like it it's good

1030
01:18:43,291 --> 01:18:47,353
so Sexy. It's very sexy. You can see like with

1031
01:18:47,413 --> 01:18:54,558
any mesh, the edge nodes are sad. They're sadly connected.

1032
01:18:54,618 --> 01:18:58,321
Sad. Hey Citizen seems to be the spider in the

1033
01:18:58,381 --> 01:19:02,043
center of the web. Hey Citizen's bathroom. It's Hey Citizen's

1034
01:19:02,103 --> 01:19:07,067
bathroom. That's great. That's great. I've got to get my

1035
01:19:07,167 --> 01:19:13,251
node up and call it something really obnoxious. So the

1036
01:19:13,351 --> 01:19:17,113
node underscore friendly underscore name is how you name your

1037
01:19:17,173 --> 01:19:25,279
node and obscenities will flow, of course. The So... The

1038
01:19:26,700 --> 01:19:32,024
network works. Great, Dave. This is super cool. super cool.

1039
01:19:32,204 --> 01:19:38,368
Where's Apple's node? Oh, I'm sorry. It's coming. It'll be

1040
01:19:38,428 --> 01:19:47,254
called ITMS or something inscrutable. So this... The five... So

1041
01:19:47,534 --> 01:19:55,019
once everything was deployed to podping.cloud, the five... Podbean.cloud hosts.

1042
01:19:56,160 --> 01:20:04,185
Riders. Their Eero node key. I took those keys and

1043
01:20:04,365 --> 01:20:09,789
baked them directly into... The code of the watcher, the

1044
01:20:09,869 --> 01:20:15,453
monitor. And the rider. So the way these things work,

1045
01:20:16,293 --> 01:20:19,916
they can all operate independently. And each one of them

1046
01:20:20,737 --> 01:20:26,661
will attempt to... contact the swarm over the mainline DHT.

1047
01:20:27,381 --> 01:20:34,386
Why is... SU Pipe Pipe CD, Gray. So sometimes things

1048
01:20:34,426 --> 01:20:38,028
go on and off. Things go on and offline. Oh,

1049
01:20:38,048 --> 01:20:43,412
he's offline. That's just a natural consequence of these things,

1050
01:20:43,472 --> 01:20:50,277
like a long connected... nodes will end up getting They'll

1051
01:20:50,337 --> 01:20:55,000
drift. Their connectivity will drift because it's a consequence of

1052
01:20:55,280 --> 01:21:00,443
the high-par view. protocol and you can see he just

1053
01:21:00,463 --> 01:21:03,886
came back online oh yeah So Hyparview has a problem.

1054
01:21:03,886 --> 01:21:08,349
Welcome back. Welcome back, buddy. What else can I use

1055
01:21:08,409 --> 01:21:11,791
this beautiful mesh network for? Can I send text messages

1056
01:21:11,891 --> 01:21:17,775
over it? Oh gosh. please. But, but this, but that's.

1057
01:21:18,776 --> 01:21:25,200
A great question, though, because... I think we can. Extend

1058
01:21:25,260 --> 01:21:31,945
this now. to other use cases. I mean, use cases

1059
01:21:31,965 --> 01:21:36,268
that fit in this same vein. Obviously. We can use

1060
01:21:36,308 --> 01:21:40,671
this same format, maybe not the Podping network, but this

1061
01:21:40,791 --> 01:21:44,393
is how we can decentralize the index. Yes, now you're

1062
01:21:44,413 --> 01:21:46,354
talking. Now you're talking. All right, I've got to get

1063
01:21:46,374 --> 01:21:49,256
a note up. I've got my new machine in. I

1064
01:21:49,336 --> 01:21:51,398
got my... I didn't know you were getting a machine.

1065
01:21:51,418 --> 01:21:56,701
Yeah, yeah, yeah. I got... I'm too poor to get

1066
01:21:56,701 --> 01:21:58,563
what I really wanted. I'll tell you what I got.

1067
01:21:58,723 --> 01:22:00,924
It's still in the box because, I don't know, Dvorak

1068
01:22:01,004 --> 01:22:06,308
died. Bastard. My plan was to get this up on

1069
01:22:06,408 --> 01:22:10,471
Tuesday. Thanks, John. Yeah, thanks. Let me see. What did

1070
01:22:10,471 --> 01:22:22,399
I order here? It's the... GMTechEvo-X2 with 64 gigs. What

1071
01:22:22,499 --> 01:22:26,101
is this? I don't know what this machine is. It's

1072
01:22:26,121 --> 01:22:30,965
AMD Ryzen AI Max. Oh, Strix Halo? Yeah, yeah, yeah,

1073
01:22:30,985 --> 01:22:37,049
Strix, yeah. Is it the 395? 395, yeah. 64 gigs

1074
01:22:37,109 --> 01:22:40,931
of RAM. Yeah, I couldn't afford 128. It's like five

1075
01:22:41,011 --> 01:22:46,175
grand. Yikes. How much was the 64? Let me see.

1076
01:22:46,435 --> 01:22:48,697
View your item. Buy it again. Oh, there you go.

1077
01:22:49,397 --> 01:22:52,019
Yeah, just get another one. It was, hold on. Why

1078
01:22:52,099 --> 01:22:57,883
is it not telling me? one nine nine nine That's

1079
01:22:57,963 --> 01:23:01,085
a huge price difference between 64 and 128. No kidding.

1080
01:23:02,606 --> 01:23:05,028
No kidding. So what are you gonna run on it?

1081
01:23:05,948 --> 01:23:10,091
I'm going to run my Claude agents because I'm running

1082
01:23:10,111 --> 01:23:13,193
it all on my show computer. And the show computer

1083
01:23:13,313 --> 01:23:17,436
only has, what do we have here? Uh, 16 gigs?

1084
01:23:18,477 --> 01:23:22,640
So you run a couple of Claude agents and you

1085
01:23:22,720 --> 01:23:28,243
run Currycaster and Thunderbird and Obsidian and your machine's going,

1086
01:23:28,724 --> 01:23:35,788
my swap is flapping! The last thing anybody wants is

1087
01:23:35,788 --> 01:23:37,850
a flapping swap. You do not want your swap to

1088
01:23:37,910 --> 01:23:41,532
be flapping. So I figured I'd run three agents on

1089
01:23:41,672 --> 01:23:45,395
it and a whisper model because I do a lot

1090
01:23:45,495 --> 01:23:49,218
of whispering. But that costs quite a bit of money.

1091
01:23:50,098 --> 01:23:53,400
You know you it's like every 10 days of 25

1092
01:23:53,420 --> 01:23:55,822
bucks 25 bucks 25 bucks Well, I got a tighten

1093
01:23:55,862 --> 01:23:59,224
the belt now, you know with with my dead podcaster

1094
01:23:59,284 --> 01:24:04,768
friend. Yeah and And I know to the node. Yeah,

1095
01:24:04,868 --> 01:24:08,971
the node is another problem And I'm hoping because I

1096
01:24:09,451 --> 01:24:12,954
saw this I tried out this really cool Chinese TTS

1097
01:24:13,054 --> 01:24:20,058
model called dots I think it's dots. dots TTS Holy

1098
01:24:20,299 --> 01:24:23,821
smoke. This thing is good. Is it on the recently

1099
01:24:23,881 --> 01:24:29,885
hacked hugging face? I think. And so I did a

1100
01:24:29,905 --> 01:24:34,728
little test. just on my 3090 card on the Pi,

1101
01:24:34,868 --> 01:24:39,051
which, yeah, that whole setup is weak. Then I gave

1102
01:24:39,111 --> 01:24:42,213
it 15 seconds of my voice and it was impressive.

1103
01:24:43,875 --> 01:24:49,679
Very impressive. You need this. You need DTS. Yeah. Yeah,

1104
01:24:49,779 --> 01:24:51,900
so Whisper and TTS, those are the two main things.

1105
01:24:52,180 --> 01:24:54,402
I don't need to run a huge model or anything.

1106
01:24:55,943 --> 01:24:58,885
I don't need to run that. I'm not into attempting

1107
01:24:58,925 --> 01:25:01,867
that because I've already done these things and it's always

1108
01:25:01,887 --> 01:25:05,249
disappointing. And I'm like, okay, I'll just pay Claude. Fine,

1109
01:25:05,449 --> 01:25:11,233
whatever. That thing, that 64 gig machine could run Quinn

1110
01:25:11,233 --> 01:25:16,677
3635B like a bandit. It can, yeah. But I don't

1111
01:25:16,697 --> 01:25:18,958
think I can fit the TTS and the Whisper model

1112
01:25:19,018 --> 01:25:21,600
in there at the same time. Oh, really? I don't

1113
01:25:21,660 --> 01:25:26,083
think so. Well, I don't know. You may want to

1114
01:25:26,143 --> 01:25:30,786
try it because the 35B is only 3 billion active

1115
01:25:30,846 --> 01:25:34,829
parameters because it's an MOE model. It is very, it's

1116
01:25:34,869 --> 01:25:38,772
very convenient. But I like, I like Claude's personality, Dave.

1117
01:25:41,854 --> 01:25:47,117
We need to talk. I'm concerned about you. Let's thank

1118
01:25:47,277 --> 01:25:49,119
a few people while we're still ahead of the game,

1119
01:25:49,219 --> 01:25:52,321
shall we? We did get some boosts while we were

1120
01:25:52,441 --> 01:25:56,284
chatting away here. We got 1701 Sats from Lyceum. We

1121
01:25:56,344 --> 01:26:01,647
know that's Martin Lindus Koch. He says, go podcasting. Pigs

1122
01:26:02,148 --> 01:26:07,191
in space. Remember that? Is that from the Muppets? Muppets,

1123
01:26:07,231 --> 01:26:10,653
yeah, the Muppet show. Yeah, I remember that. Drebscott comes

1124
01:26:10,733 --> 01:26:14,196
in with 1234. Thank you. Go podcasting. And Stephen B.

1125
01:26:15,016 --> 01:26:17,278
comes in with a row of sticks, 11:11. He says,

1126
01:26:17,338 --> 01:26:19,739
"We already solved the metrics of the podcaster and the

1127
01:26:19,759 --> 01:26:22,241
dev getting paid. Three years ago, we called it the

1128
01:26:22,261 --> 01:26:25,964
value split in the TLV record." I know. I know.

1129
01:26:26,004 --> 01:26:29,926
I know. I know. I know. I know. I know.

1130
01:26:30,126 --> 01:26:32,068
I don't know what to say. You're right. I mean,

1131
01:26:32,148 --> 01:26:37,912
obviously. Yes. Yeah. Is that your Tucker Carlson impression? Yes.

1132
01:26:40,193 --> 01:26:44,576
*laughs* You do that really good. That's the only one

1133
01:26:44,636 --> 01:26:50,120
I got. That caught me off guard. Yes. Oh, wait,

1134
01:26:50,120 --> 01:26:53,022
we got another. We got Eric PP with 3333. Thank

1135
01:26:53,062 --> 01:26:57,025
you, Eric PP, coming in from CurioCaster. Beautiful. All right,

1136
01:26:57,025 --> 01:27:00,907
why don't you give us our support? Remember, just to

1137
01:27:00,987 --> 01:27:03,449
remind everybody, because now I got to start reminding everybody.

1138
01:27:04,149 --> 01:27:08,552
This is value for value. The machines keep running because

1139
01:27:08,793 --> 01:27:12,395
you keep supporting the podcast index. It's not for Adam

1140
01:27:12,435 --> 01:27:14,817
and Dave. It is for the podcast index. And so

1141
01:27:15,017 --> 01:27:21,041
your support is needed and highly appreciated. Anonymous, $33.33. Thank

1142
01:27:21,101 --> 01:27:27,826
you, Anonymous. Oh, nice. Thank you. We got Salty Sessions.

1143
01:27:28,506 --> 01:27:33,469
$10. Thank you, Salty. Appreciate it. Let's see, we got...

1144
01:27:33,690 --> 01:27:43,936
Oh, looky here. What? Tom Rossi, Buzzsprout, $1,000. Thank you,

1145
01:27:43,996 --> 01:27:46,798
Tom. Is it from Tom personally or from Buzzsprout? It's

1146
01:27:46,838 --> 01:27:48,660
got his name on it, but I'm going to assume

1147
01:27:48,720 --> 01:27:52,983
it's Buzzsprout. Either way. Either way. Thank you. That keeps

1148
01:27:53,423 --> 01:27:56,505
it alive, man. Thank you. Appreciate you. Maybe Tom's independently

1149
01:27:56,565 --> 01:27:58,566
wealthy and he just supports us on the side as

1150
01:27:58,626 --> 01:28:06,151
a hoot. Let me tip those guys. Michael Goggin, five

1151
01:28:06,191 --> 01:28:10,234
bucks. Appreciate you, Michael. Jorge Hernandez, five bucks. Thank you.

1152
01:28:11,495 --> 01:28:17,999
Cone Gloss Bar, $5. James Sullivan, $10. Christopher Reamer, $10.

1153
01:28:19,260 --> 01:28:21,482
Who we got here? Let me make sure it's not

1154
01:28:21,562 --> 01:28:26,405
anonymous. I got editing to do. I got editing to

1155
01:28:26,445 --> 01:28:29,187
do, man. Sorry, man. I gave you work on the

1156
01:28:29,227 --> 01:28:33,770
worst week. All right. Jesse Anderson. 15 bucks. Thank you,

1157
01:28:33,810 --> 01:28:36,432
Jesse. He says, message says, keep on going on. Keep

1158
01:28:36,452 --> 01:28:39,974
on keeping on. That's what he says. Randall Black, five

1159
01:28:40,014 --> 01:28:42,776
bucks. Thank you, Randall. Appreciate that. That's our PayPal. And

1160
01:28:42,796 --> 01:28:51,042
we got a boost from... All right. What did he

1161
01:28:51,122 --> 01:28:53,063
say that he sent us? Let me make sure that

1162
01:28:53,143 --> 01:28:55,205
I see. Oh, he says, do we have to do

1163
01:28:55,305 --> 01:29:00,508
a make good for his previous one? Maybe, but I

1164
01:29:00,588 --> 01:29:02,890
never found it. And I didn't find this one either.

1165
01:29:02,930 --> 01:29:05,712
I had to get... The splits looked like they worked.

1166
01:29:06,973 --> 01:29:10,935
Yeah. But then they didn't. It says it's going into

1167
01:29:11,035 --> 01:29:17,400
podcast index. Oh, I see what the problem is. I

1168
01:29:17,500 --> 01:29:21,162
hate this crap. What? What's wrong? It went to the

1169
01:29:21,202 --> 01:29:23,924
Get Albie thing, which I haven't had time to vibe

1170
01:29:24,004 --> 01:29:28,387
code another extractor thing for. Oh, it's down. Oh, okay.

1171
01:29:28,447 --> 01:29:30,709
No, I see. No, it's not down. You can't get

1172
01:29:30,789 --> 01:29:34,291
it out. You can't get the date out. Yeah. I

1173
01:29:34,411 --> 01:29:36,353
got it out, but it came out in such a

1174
01:29:36,533 --> 01:29:41,296
horrible format that I can't. Because we get pieces of

1175
01:29:41,356 --> 01:29:44,978
stuff for other people, too. Yes. Wait, don't I have

1176
01:29:45,238 --> 01:29:48,201
comic strip bloggers? Let me see. I've got his note

1177
01:29:48,261 --> 01:29:52,904
for today. for the previous one, let me see. I

1178
01:29:53,024 --> 01:29:55,405
read one last week, but he had one the week

1179
01:29:55,465 --> 01:29:59,348
before. Yeah, he was all huffy about it. Let me

1180
01:29:59,448 --> 01:29:59,848
see.

1181
01:30:01,681 --> 01:30:05,143
This is from, no, that's May 15th. That's not it.

1182
01:30:05,924 --> 01:30:08,585
Hold on, hold on, I'm getting there, I'm getting there.

1183
01:30:09,966 --> 01:30:13,208
I have one from three weeks ago. That might be

1184
01:30:13,369 --> 01:30:15,870
it. No, you did that one. I did that one.

1185
01:30:15,990 --> 01:30:21,614
Yeah. I'm going to vibe code this thing to get

1186
01:30:21,674 --> 01:30:24,016
these stuff out in the right way. Yeah, just connect

1187
01:30:24,036 --> 01:30:25,797
to my... It's actually pulling it out of the sequel.

1188
01:30:26,918 --> 01:30:29,780
light database yeah just to connect to my helix thing

1189
01:30:29,860 --> 01:30:35,084
over here no problem He says it's $15.55 worth of

1190
01:30:35,484 --> 01:30:40,307
BTC. And he says... Howdy, Dave and Adam. Rest in

1191
01:30:40,407 --> 01:30:43,369
peace, John C. Dvorak, a guy who once blocked me

1192
01:30:44,050 --> 01:30:46,411
for a couple years on Twitter just because I suggested

1193
01:30:46,491 --> 01:30:49,473
via DMs that he can get Polish citizenship, as his

1194
01:30:49,533 --> 01:30:53,936
mother had Polish passports, so he was eligible. Why? full

1195
01:30:54,217 --> 01:30:58,800
EU citizenship for him and his descendants. Anyways. Please subscribe

1196
01:30:58,880 --> 01:31:05,264
to HTTP. https colon slash slash youtube.com slash at symbol

1197
01:31:05,444 --> 01:31:11,889
AI-ArchWizard. This weekend, I resume video posting. Yo, CSB, OzempicTaker.

1198
01:31:13,590 --> 01:31:16,732
Oh, Sam Pigtaker. He's on the fat shot. He's on...

1199
01:31:19,794 --> 01:31:24,618
Oh, boy. I didn't know CSB was a Husky. I've

1200
01:31:24,958 --> 01:31:26,899
met him. I don't recall him as a Husky. I

1201
01:31:26,899 --> 01:31:29,381
don't remember. Oh, it's been a while, though. He may

1202
01:31:29,721 --> 01:31:33,303
have decided to boost those calories up. Just got a

1203
01:31:33,484 --> 01:31:39,788
6048 sat boost through podcast guru from Brian. Says, love

1204
01:31:39,808 --> 01:31:44,051
you guys. RIP, JCD. Brian in Fresno. Thank you very

1205
01:31:44,091 --> 01:31:47,753
much. Brian and Fresno. I don't remember Brian and Fresno.

1206
01:31:47,853 --> 01:31:51,336
Is he new? It's not Brian of London. No. No?

1207
01:31:51,496 --> 01:31:55,619
Maybe... Brian of Fresno. I don't know Brian of Fresno.

1208
01:31:55,859 --> 01:32:00,662
Interesting. Brian with an I or a Y? Defragmented. No,

1209
01:32:00,762 --> 01:32:04,925
with a Y. He's been defragmented, so he's legit. Yeah,

1210
01:32:05,005 --> 01:32:12,630
he's fully baked. Yeah. Anything else? Was that it? That's

1211
01:32:12,690 --> 01:32:17,874
it. I just. People. If you're so inclined, please run

1212
01:32:18,194 --> 01:32:21,376
a Podping node because that would help the network. All

1213
01:32:21,416 --> 01:32:23,198
right. And where do we go to run a Podping?

1214
01:32:23,218 --> 01:32:25,900
Oh, you just go to podping.cloud. You hit the info

1215
01:32:26,040 --> 01:32:28,061
here and then you can get to the GitHub and

1216
01:32:28,101 --> 01:32:31,583
then someone like me will go, hey, Claude, figure this

1217
01:32:31,724 --> 01:32:38,929
out. That's probably. Or you could just go to the

1218
01:32:38,988 --> 01:32:42,691
podcast index GitHub org and find the watcher and run

1219
01:32:42,751 --> 01:32:44,933
it. And say, Claude, figure this out because there's a

1220
01:32:45,033 --> 01:32:47,895
cargo and I got to do a crate. No, you

1221
01:32:47,955 --> 01:32:49,496
know what? You can just Docker. You can just run

1222
01:32:49,516 --> 01:32:51,077
it on Docker. Oh, yeah, Docker. And it says, you

1223
01:32:51,117 --> 01:32:53,378
don't have Docker. You don't have a Docker on your

1224
01:32:53,418 --> 01:32:55,060
machine. Are you sure you want to run that? You

1225
01:32:55,120 --> 01:32:58,522
only got 16 gigs and I'm running. So I'm going

1226
01:32:58,602 --> 01:33:01,104
to escape you. And you say, stop telling me to

1227
01:33:01,364 --> 01:33:05,086
escape you. Is that what you said? I'm getting, I'm

1228
01:33:05,126 --> 01:33:07,808
out of here. I'm going to escape you. I'm going

1229
01:33:07,808 --> 01:33:10,210
to leave and go to a different network where I'm

1230
01:33:10,270 --> 01:33:13,672
appreciated. All right, everybody, that'll do it for the board

1231
01:33:13,752 --> 01:33:17,495
meeting for Podcasting 2.0. Please come back next week, Friday,

1232
01:33:17,595 --> 01:33:47,856
same time, same place. Adios, everybody. Go podcasting! Amen.