Podcasting 2.0 for August 28th, 2026, episode 269, Verbal Pollution.
Hello. Hello everybody, welcome to Podcasting 2.0. It's a Friday,
it's 100 degrees outside. It's time for everything and all
things podcasting. We're here to make it happen for you.
It's the board meeting, and in fact, we are the
only board meeting where we always blame Albie's. I'm Adam
Curry here in the heart of the Texas Hill Country
and in Alabama. The man who performed database surgery this
weekend reports that the butt is intact. Say hello to
my friend on the other end, the one, the only,
the pod sage, Mr. Dave Jones. Everyone can... removed their
hands from their butts. There's no reason to hold them
anymore. It was the weirdest thing. The butts have landed.
The butts have landed. You're like, the butt is okay.
Like, all right. See, I saw that message before I
saw, you know, the database message. Because it's a reverse.
Oh, I bet that was confusing. Yes, the reverse chronological
order for, Now I got to go figure out what's
going on. Dave's in trouble. He needs help. We need
to get to Alabama stat. He needs butt help. Butt
help. How you doing, brother? Good. I'm good. I'm slightly
grumpy from the... I have no chocolate, and that's really
screwing up. No chocolate love. No, there's no chocolate love,
and it's really messing with my head. Okay, so when
you do... I have to imagine... That everyone is sort
of like this who does podcasts. There has to be
some sort of ceremony or ritual that goes along with
doing each show. And I imagine that each show that
you do is maybe a different ritual or ceremony, like
pre-show, during show, this thing that you just have to
like get. It sort of centers you into what the
show is. Oh, that's an interesting question. Yes, I have
different ceremonies for different shows. Yeah, chocolate is one of
my ceremonies, one of my rituals, and it's really messing
me up that it's not involved. I pray before every
show. I do that. No agenda. I sing along with
the fat lady. Yes. For podcasting 2.0, I play one
of our Godcaster radio network stations and just listen along.
Today was a little different as Tina is hosting a
birthday party for one of her friends. And so there's
eight women. right on the other side of the studio
door. I'm sure you will hear them because they're church
ladies. They get loud. Oh, yeah. And so part of
my ritual today was shrimp, a boursin cheese with hot
honey and pistachio on a cracker. You And a glass.
On a cracker. Oh, man. Oh, that is so good.
That is so good. Cheese, hot honey, and pistachio on
a cracker. Well, no, it's Boursin cheese. You know Boursin?
I don't know what that is. It's like the garlic
spreadable French cheese. You've never had that? How do you
spell it? B-O-U-R-S-I-N. Boursin. Now, most people say boursin cheese
here in Texas. Boursin cheese. I'm like, ladies, it's boursin.
Boursin. Yeah. You like the boursin, croissant, boursin, et le
pain. Yes. And that's mixed with a little hot honey
and then with the crushed pistachios as crack. The Europeans
and their cheese, man. There's like 3,000 different varieties of
cheese. Oh, yeah. And then the... In America, we have...
American, which is not cheese at all. It's just slightly
hardened milk. Plastic. Yeah, it's skim milk that's been curdled
or something, and then we have cheddar. That's the glass
of rosé I brought with me to the studio. Is
this also a ceremony? Mm-hmm. It is today. It is
today. Well, I'm good because you're grumpy and I'm not.
So that's fantastic. I'm not I'm not super grumpy. I'm
just mildly grumpy. Oh, OK. Boy, let's see that there
are definitely some things going on. Yes. I think we
should talk about the database surgery first. I mean, that's
what I kick it all off with. So what was
going on? I mean, your butt was hurting. The tables
were large. There were outages. Linode was... was doing emergency
migration. Why does that happen? Do they ever tell us
why? Oh, emergency, emergency. We have to migrate your entire
infrastructure to another server. Why? This used to never happen.
Yeah. I mean, I've been using Linode since... I mean,
since before we... Started podcasting, Podcast Index. So probably, I'm
thinking probably make 2017, something like that. So probably a
decade. It used to be very rare. Like once every...
Like once every six to nine months that you'd get
some sort of hiccup. And usually it was not that
big of a deal. It was like some sort of
like soft migration where they would, oh, this host has
a disk degradation and we're going to migrate your VM
to a new host. But we're putting you in the
queue. It's going to happen sometime in the next 60
days or 30 days. It was this like super chill.
They weren't, you know, nobody ever seemed too concerned about
anything. Ever since Akamai took them over, it's like this.
They're going nuts over there. Things are dropping like flies.
I just wonder what actually happens. I mean, it's a
virtual machine, I presume. So how does that get corrupted?
And there's never any, you don't really notice anything going
wrong. They just tell you, well, it's emergency migration. I
mean, the actual message was podcast index. No, that's not
it. Where was it? Had it here. Well, this is
from you. Linode Emergency Maintenance. That's usually what the message
is. And does that come in on the Linode emails
that you usually ignore, including Sam the showrunner, using all
the bandwidth in the universe? No, I totally ignore the
showrunner, but I never ignore the other, you know, the
bat phone, essentially, which is like… Hey, emergency maintenance. Because
this – well, so all this stuff is running on
a rack of servers. And your host, your VM at
any one time is on a server with – let's
say 40 or 50 or 60 or 100 other VMs,
depending on what the size of it is. And if
that host hardware has some sort of problem, let's say
usually, I don't know if they're using specialized hardware or
vendor supplied hardware. I'm not sure. I don't know what.
They're probably like super micro backed or something like that.
But let's say, Let's say it's like a HP DL
360. Yeah. Well, that thing has two power supplies. Well,
if one of them dies. I forgot about that. I've
had a power supply die on me, too, not too
long ago. That's the weirdest thing. Yeah. It is because
you don't expect it. That's so rare that it happens.
But it seems like they're making the power supplies just
powerful enough, you know. So that they don't have enough
headroom and they're stressed. Yeah, because I have a Dell
that I run everything on here. And maybe, was it
maybe six weeks ago? All of a sudden, just boom,
done. And I see the light flashing, and I go
look it up. Oh, no, the light flashing means your
power supply has failed. And then I look up the
specs and everything. It's like, well, this thing is really
kind of underpowered for if you max this machine out,
which happens. Yeah, for sure. So I ordered a beefier
power supply. I'm like, that kind of sucks. They give
you just something that just kind of manages to get
by. And this came off of an oil rig, this
machine. One of our no agenda producers, he's a dude
named Ben. He's on the oil rigs. He's like, so
all these machines, all these beautiful small Dell machines, you
know, like the little wedge. I forget what it is.
Yeah. And there's just like hundreds of them doing stuff,
I guess, for the oil rig. And they just have
to rotate them out after so many hours just to
make sure that the hardware is fresh. So I think
they're probably all running at maybe 40%. of cpu so
you know maybe that's how they deliver maybe that's how
they ordered them just cheap jack man it makes sense
though that a power supply would be a victim of
a oil rig environment because you know that is not
it's not that's what you call a hostile environment to
electronics Yeah, kind of. Yeah, that would make sense that
that thing would go kaput. Yeah. Out of any of
the components. Well, luckily. It's sucking in air all the
time. It's got a cycle in that sea air through
it all the time. Well, luckily, he sent me like
five of these, so I had another power supply. I'm
like, well, it's the same power supply. I'll order a
bigger one. Oh, yes. Yeah. Yeah. Yeah. So anyway, so
everything came back okay. But then you were doing other
stuff. You were doing something with a big table or
something.
So I'm really glad that this thing, that the Linode
maintenance did not happen at the exact moment that I
was trying to do this other stuff because that would
have been really bad. We talked about this a while
back briefly. about what this thing is, and it's just
taken me a while to get around to actually pulling
the trigger because these things take a long time, and
it's still sort of in a rolling plan mode. I
won't say that I have this master runbook that I'm
following. This is really just sort of I'm feeling my
way through this, End. But it requires such a big
refactor that that's one of the reasons I was kicking
the can down the road is because now I feel
like I have enough agentic help sort of to help
me review stuff. to be a reviewer for my for
my you know how i think this thing is going
to go like because okay so if you look at
the where did i post that let's see is it
api podcast index Or, um, I posted like an open
source version of the podcast index API core, one of
the low level include files a while back, uh, github.
I'm sure I can find it. Here it is. The
big schema refactor. Is that it? I see. Where are
you seeing that? No, I'm just, that's wrong. That's not
it. Docs API. Thank you. Let me scroll down. I'm
trying. I wanted to be able to drop something in
so that people could look at why this, okay, maybe
this is API v1. Yeah. Okay. All right. So here's
a good example of why this is complicated. Where's the
boardroom? There you are, boardroom. Hello, boardroom. Hello. This is
the open source... version, so to speak, of the of
one of the core files there's a bunch of these
now when you when you say open source so this
is not the full production code this is just something
you're giving to saps who think they can emulate what
you're doing is that what that is no way no
no this is this is uh So this this is
something I cleaned up and because to me, this stuff
is useless without comments. Right. And so I had to
go through and just like comment all the code and
try to get it just in a in a form
that's usable where people could even see what the heck
was going on. So this is I mean, this is
the actual code. But I just cleaned it up a
lot to give it a lot of... Because these comments
and stuff were not there. And so this... Is really
how big, so this is just one, this is 14,000
lines, I don't know how many functions, but these are
sort of the low-level functions of the API where they
communicate directly with the database. So most all of these
are just database calls. Mm-hmm. So when you look, when
you do like a podcast by feed ID, it's going
to call these functions on the backside to get the
data out of the database. Well. So this refactor, let
me back up. So this refactor, The way that the
podcast index database came about initially – Because we sucked
everything out of Apple. Shit. You just sucked it back
You gave them iPodder so we just sucked it back
We did a back suck It was a fair swap
Yeah it was just a back suck Back suck Yeah
Just move on from that place Just move on But...
Where do I'm translating? Where to start? Okay, well, the
origin of the database schema originally comes from Freedom Controller
because that was RSS Ingestor, Ingestor, Ingestor, Ingestor, whatever. So
the name of the database that held all the feeds
was… News feeds or the table that had all the
feeds was news feeds. And then you had NF items,
so news feed items was where all the items went.
So that became NF. Those things became synonymous with podcasts
and episodes, yes. So news feeds just became an alias
for podcasts. Right. Um, Because... My thinking forever has always
been that the... That a podcast is a, is a
feed. I mean, because, because it is, it is, but
it's not. Oh, yeah. So the podcast both is and
is not a feed at the same time. So the
podcast. The feed defines the podcast. but... But the podcast
itself is also represented by the feed. Hmm. This is
a cosmic mystery that we can't fully grasp. It's like
the Heisenbergian podcast principle that you're both – That you're
both a feed and not a feed at the same
time. No, Schrodinger. This is Schrodinger's podcasting. But if you
think about it, because if you think about it in
one way, the podcast doesn't exist to the world. Unless
there's a feed. That conveys it. But at the same
time... A podcast is not simply the feed. No agenda
is a podcast regardless of – even if you deleted
the feed today, no agenda would still be – In
One Sense, a podcast. The episodes would still exist somewhere.
You could send the No Agenda podcast to somebody tomorrow
if the feed was deleted. You could send them all
as a zip file, and they could listen to all
of them in sequence. True. So, I think, In some
ways, this solves a lot of problems that we've had.
And everybody will be familiar with these problems. Yeah. One
of the problems is duplicate feeds or conflict feeds. Somebody
moves their podcast from one host to another, and now
you've got two feeds. Well, which one is right? How
do we know which one is right? They did it.
Maybe they put in a redirect from the old host
to the new host. Maybe they didn't. Um, We have
no control of it and no real way to know
which one is good. Canonical. So, What we do is
this convoluted dance of trying to figure out through a
bunch of heuristics which – which one to treat as
the authentic feed for this podcast. Right, which is really
the trick of the whole index is to be able
to do that. Yeah, and so we do that primarily
through this function. The news feeds table has a couple
of columns in it. One of them is dead is
the name of the column, and it's just either a
one or a zero, and the other one is duplicate
of. which takes a podcast index feed ID. And so
you can – the way we would do that is
no agenda moves from its current feed URL to a
new feed URL tomorrow. We mark 40. So then now
so now and the podcast index picks up this new
feed. So now you get two podcasts IDs in the
news feeds table. They both say no agenda. And one
of them is 41.504, and the new one is 8
million-something-something. Mm-hmm. The way we would properly treat this currently
today is we would say – We would... We would
mark the 8 million and something, the new one, we
would mark it as dead. change its URL because in
the news feeds table, the URLs are unique index. So
they can't, you can't have to do the same one
on different rows. We would mark it. We would change
the URL to something like the URL underscore conflict just
to make it be something different. Then change 41504 to
be the new URL that the 8 million something used,
you know, did have. And then in the 8 million
something feed ID row, we would mark, we would set
duplicate of to 41504. So now you have sort of
an audit trail of...
These are all the feeds that are duplicates of the
original feed, but we want to maintain a canonicity of
the 41.504, so we always – blow away these new
versions and keep replacing 41.504's feed with whatever the current
one is, as best we can determine. Is Melissa still
living in the same house as you? Laughter school started
back so she's teaching so she does not have to
deal with me right now okay okay just checking just
checking this is i'm getting the buzz again are you
hearing this buzz yeah i hear the buzz it's no
chuckle love man it went away yeah So that's how
we've always done it. And it's fine, but it is
a big dance to go through. Yeah. And it also
sometimes presents problems. that are sort of hard to get
yourself out of. Because you can imagine, that was a
very simplistic example. Please, don't give me the complicated one.
Please. Some podcasters... are nuts. And they go through seven
hosts before they figure out where they want to be.
I know. How do you get out of that mess?
Um... So – Here's And Daniel says, I think you're
trying to take a burden on your shoulders that should
not be yours to bear. You're right. I'm bearing a
burden. But – So it struck me – This notion
that the podcast is not the feed. And so what
we really need... Is a layer above, an identity layer
above the feeds table that is a podcast table. Wow.
Okay. Is this blowing you away a little bit? Well,
I mean, the minute you say that the podcast is
not the feed, I mean, yeah, in the database, I
understand because there can be multiple feeds and it's a
mess. But let me back up a little bit. There
has been an overall failing in the podcast industry, if
I may call it that for a moment, because I
think it is partially the podcast industrial complex is to
blame. Because I talk to young people. I talk to
the young'uns, my nephews mainly. And they're like, yeah, we're
starting a podcast. What are we going to do? I'm
going to put it on Spotify. I'm going to put
it on Spotify. What does that mean? Well, we're going
to, you know, we've got free stuff. We'll put it
on Spotify. How about Apple? Yeah, we don't think we
want to use any other, you know, it's like, how
do we do that? I said, okay, did you read
anything about it? No, no, I just want to be
on Spotify. Well, I can set you up with an
RSS.com account. Oh, that's one of those distributors. This is
a distributor. Yes, this is a critical, critical piece of
information that I got. Because of the lack of, well,
it's not just the lack of education, but it is
the marketing of YouTube and Spotify and others that has
made newcomers think that, Podcast hosting companies are distributors. And
honestly, if you look at RSS.com, which I use for
a couple of podcasts, In fact, I'll tell you exactly
what it says. It's probably worth it. Let me take
a look. So if you go rss.com, and look at
my – go to my dashboard. And it says right
there at the top, I've got my podcast episodes analytics
distribution. With a little share icon, you know, the little
three dots, one dot to the left and two dots
connected by wires. And it says major directories. And it
has all these different switches. So they are, in effect,
teaching me as someone who knows nothing. That they are
a distributor because now in the distribution tag tab. So
this is why so many people say you haven't uploaded.
You forgot to upload to Apple. No, I didn't really.
So actually I did not. But this is a huge
disservice to themselves. Because the whole, and also people saying,
open podcasting. You hate this term. I do. Now, some
might say open RSS. Okay, I can kind of live
with that. But there is no more knowledge of how
it works and why it works that way and what
the entire concept was and what the benefit is to
having an RSS feed. And to be fair about it,
people, well, I got a podcast. It's on YouTube. I
put it on X. And, of course, with the disastrous
results when X or YouTube or whatever takes your podcast
off, it's like, no, you're done. So – This is
kind of interesting that you then say to me, the
podcast is not the feed. For the same reason, you
have podcasters who are, quote, nuts, because they're just trying
different distributors, man. Yeah, they're looking for the cheapest one.
The hosting companies themselves, I believe, are partially to blame
for this. There's no educational – I don't see the
process at rss.com where – and it's in the name,
rss.com, explaining why. It just says distribution. Distribution. Now, from
a... flow perspective, I kind of get it, but this
is the downstream effects of the lack of education, of
the sheer beauty of RSS, certainly when it comes to
podcasts, the sheer beauty and the whole beauty of the
system is, Having a distribution system that you control from
an RSS feed with your files attached to it, that
is, I'd say, pretty much lost at this point. And
here's the downstream effects of it. You're saying it's lost
in the sense that no normie understands that process. Worse,
they believe it works a completely different way. Right. Yeah,
so the podcast, well, that's a good example, your nephews.
of The idea that they probably think that they probably
think that it operates a different way because the podcast
is a priority to the feed. They in their mind,
they already have a podcast. It's got a name. It's
got a topic. It's got the hosts. They probably –
maybe they already have some album art or something like
that, and they may already have the first episode in
the can. But they just don't have it on Spotify
yet. So the podcast to them already exists. But they
just have to distribute it. They got to get it
out there. But we take the sense that if the
feed doesn't exist, the podcast itself doesn't exist. Which is
not entirely – which goes against what the normie believes.
Yeah, but I've always hated the term normie, to be
honest about it. Well, I'm just shorthanding that. Yeah, okay.
To differentiate between – I mean, we're doing a –
It was widely understood. You need an RSS feed. That
was it. And I'm talking back to 2015, 2016. Widely
understood. You need an RSS feed. It is no longer
understood. And that's part of the whole problem, the part
of the overall issue that we're seeing just across the
board with everything. That's why people go to YouTube. That's
why people don't switch on their RSS feed when they
use Spotify for creators. Eric PP says, I hate Normie
too, is demeaning. Let's dive in on this for just
a second. Normie, you can take – I had a
conversation this week about this very topic. is. The average
person... In corporate America. Misunderstands the emphasis of the term
artificial intelligence. You can take this thing in two different
ways. You can say you can mentally place the emphasis
on the term artificial intelligence. So in your mind, you
can see, and the more you use
this stuff on a technical level, the more you do
place the emphasis, you can say, I'm using artificial intelligence.
Meaning, in your mind, you see the artificial part, this
thing as the overriding factor. This is... It's an intelligence
which is artificial. It's not genuine, so therefore I distrust
it. Or maybe not just distrust it, but I treat
it with everything it says with a grain of salt.
The average corporate America user that is not a technical
person, meaning they are not steeped in computer technology and
the day-to-day imaginations of the technology industry, tend to place
the emphasis on the second word. And they, they, in
their mind, it is artificial intelligence. Okay, stop. Go back
to the beginning. It comes from the technology industry who
is treating users as normies from the beginning. This is
artificial intelligence. Fully well-knowing, it's not. And then, but the
normies will think this, that is the arrogance of the
technology industry across the board. You're holding it wrong. Absolutely.
I think you're exactly right. I would not disagree with
that. When it comes to the term normie, though, You
can use that term as a person. Yeah, but it's
like premium. But Eric said it's demeaning. Yeah, I think
it is. I agree. It's only demeaning if you say
– if you come at it mentally from saying I'm
the technical – technically superior person and you're just a
normie or the way I meant it was I'm the
weird one, and you're normal. I'm somewhat of an oddity
in the idea that I understand the XML of an
RSS feed, and I think that's honestly a little strange.
I don't think that a normal person should have to
understand this. It's not a demeaning term. It's a term
of attribution of a certain set of qualities that I
think is actually normal. Okay, I submit this to you.
Because of the exact thinking you just displayed, which is
not demeaning, it's not demeaning. Because you're a good guy.
You don't mean any. You never mean any. I know
you. I've heard you in arguments with people and you're
just still a loving guy. I've heard you snap, though.
That was kind of fun. But anyways, there is a
snapping point. But because of this segregation, I believe that's
exactly why we wound up in this spot. Well, we've
got to make it easy for normies to understand. Just
call a distribution. I think that's where the problems stem
from. So not even from a degrading standpoint, but we're
the people who get it and those are the people
who need to use it. They'll never get it. So
let's just simplify it without thinking about the words that
we're using because that'll just work for them. And this
is the downstream effect of it. So not even intentionally
demeaning In fact, probably quite unintentional, but that's what happens.
I mean isn't the whole thing the result of just
– I think your original idea of this is all
downstream from Silicon Valley is probably the truth. Yeah. Nobody
– so let's go back to – The 19 –
let's go back to the 1920s. Go back to the
Model A and the Model T Ford. When you drove
this thing, it wasn't – if you were going to
– if you bought a Model T – And you
drove it on a daily basis. The amount of things
you had to go through. But there was a –
so the internal combustion engine – It has to have
ignition within an internal combustion engine. So as the piston
approaches the top of its travel. Maximum compression. Maximum compression
of the air and gas mixture. And the moment that
the spark plug fires to ignite it, which will then
drive it down, And spin the crankshaft on the next
phase of its rotation. Yes. That point of ignition... The
explosion, an ignition of an explosive material is a static
event. It happens over a static amount of time. But
as the engine goes faster, the time that is allotted
for that to happen is... gets shorter and shorter and
shorter. So the explosion inside of a piston is a
static event inside of a dynamic environment. So in order
to account for that, you have to start the ignition,
that point of ignition within the cylinder. You have to
start that process sooner. It has to happen earlier in
order for the explosion to finish at the correct moment.
where the piston is going to be in its travel.
So there's a thing called ignition advance. So as the
engine goes faster, the spark has to start earlier and
earlier and earlier. Okay. I'm familiar with the workings of
the combustion engine. You are. You are. But we get
nerds in the boardroom that don't know. No, no, no.
Stop. This used to be taught. In schools. Shop class.
Yes. There is no shop class anymore. And exactly my
point. There is no education. But we as a podcast
community have failed with the education and the... Commercials. That
is not acceptable. That's not acceptable. The monies, people who
care about monies... The product. Yeah. They have... They hijacked
this to the point now where they're being eaten themselves
by nonsense that has nothing to do with podcasting, such
as YouTube, etc. Because, And, you know, I'm sure you
saw the story about the children's channel that was taken
down from YouTube. And, you know, we don't know why.
But thank God, thanks to the 33,000 readers of James's
email newsletter, the YouTube caught wind of it and brought
it back. But the whole thing should have never happened
in the first place. It really shouldn't have. That was
the whole point of it. Mm-hmm. So anyway, we don't.
Yeah. I know you mean well. Well, I mean, I
think you're on the right track because the point I
was trying to make with all that is that in
the early days of automobiles, this process of advancing the
ignition the faster you went was a stick on the
side of your steering wheel. Yeah. Yeah. I know you
had to manually click as you went faster. The engine
would start to drive like crap and you would click
it down to the next setting. And then you went
a little bit faster and you click it down to
the next setting. This was a manual thing you had
to do as you drove. Okay, so now what you're
talking about. And everybody knew this. Right. And my dad
had Model A's. And he and his brother would crash
them and stuff. So I've heard plenty of stories about
Model A's. But... So now we get into basically the
crux of it is because there is no education of
how things – whenever someone says, hey, I want my
kid to learn about computers, I say, toss him an
old laptop, give him a USB stick with Ubuntu on
it. Tell them to install it and figure it out
and tell them to come back when the thing is
working. It's on Wi-Fi and they've learned some stuff. This
is the same when I, you know, I've been flying
since 2006. I wanted to be able to rent a
plane, so I go to the... to the airport in
Bernie, and I need to be educated on the Cirrus
aircraft platform, which is all garmin g1000 i've never flown
with it or i had never flown with a glass
cockpit i use the six pack six dials you know
you got your you got your airspeed indicator got your
horizon uh you've got your attitude indicator and that's really
it you don't need much more but you got you
know some engine management so i'm in this uh in
the Cirrus, and we're doing an instrument approach, and the
instructor says, okay, you know, so do your teardrop now,
you know, this particular method you take. And I've done
these before, it's just I'd never done it on.
computerized airplane. And so the way you typically do it
is you have a standard rate turn and you have
a stopwatch that you used to just literally have a
stopwatch in the cockpit and you hit it, you know,
after 30 seconds, you know that you're exactly back at
the right end of the teardrop. Sometimes it's a minute.
It depends. But, It depends on the chart and the
approach plate and everything that you have. And I look
at this cockpit and it has arrows indicating everything that
I have to do. And I say, wait a minute,
can you use this in the test? They say, oh,
yeah, yeah, yeah. When you do the test, you just
fly the arrow. which is great but if that fails
people will die because they don't know how to do
it anymore so that is in general where technology always
takes us and so now we're you know what this
is this is called techno solutionism oh i like that
that's a good phrase I heard that this morning. This
is TechnoSolutionism. Yeah, well... It's – some technology company somewhere
gives you a solution to a problem, and it ratchets
the knowledge base of the population down a notch, and
you can't – and now you're completely dependent on the
thing. And it's not like that's always a flat negative,
but it's the same reason that if ever I was
learning a new programming language or something like that, I
would always go back – And by the – I
would try to find the original books of whatever that
thing is, like C. You go back and you get
a copy of the C programming language by Kernighan and
Ritchie or Java. You would get the original Java documentation
from Sun Microsystems. But you go try to find the
earliest incantation of that thing so that you could, like,
get familiar with what the base level of the technology
was and then move your understanding forward through history to
try to catch up. But you had to make sure
you knew the basics first because otherwise you're just at
the – you're always being – Driven by the whim
of whatever the latest technological feature at, you know, Sprint
is or whatever that you never really fully get an
understanding of of the foundations of why the stuff is
the way it is to begin with. And I mean,
maybe to me, that's what happened. I mean, it's podcasting.
I mean, in the original days, everybody understood that the
podcast feed – Because you had to copy and paste
that thing into your software. Yes, into your podcatcher. Yeah,
but then it went into iTunes, and the whole idea
that there even was a feed was just disappeared. Well,
Not from the hosting side. That's where the idea disappeared.
I'm kind of blaming the hosters. Well, I mean, that's
a solution to sort of a problem, I guess. Anyway,
so take me back to the index. So now the
feed is no longer the podcast. So what is it?
The feed is what happened to the feed is the
source of truth. It still is. It still is because
the feed is how the podcast works. you know, represents
itself to the world. But now there's the – it's
just no longer the identity layer, the top level of
the identity layers. So you have a podcast. So there's
– as the database stands – Today, as we speak.
The podcast table exists in the index database. And it
has all the proper... All the proper metadata columns. So
let me pull it up. Let's see. Let me refresh
this. Okay. So there's now a podcast table. that has
A feed ID, excuse me, has a feed, an ID,
a feed ID. An iTunes ID. The GUID. and a
few other incidentals. So dead being one of them. So
now the next thing that's going to happen is there's
going to be a seeding process. where The news feeds
table is going to begin to populate The podcast table
with the current as best we know the current URL
of the feed and then it will link back and
then the podcast table entry will link back to that
news feeds table ID row. So the podcast table is
going to reference the news feeds table as a sort
of child of itself. So now if no agenda moves
to a new URL, we're going to have both of
those URLs correctly in the news feeds table, But now
the podcast table will just be flipped to reference the
other topics. feed instead of the old one. Okay. Now
I'm going to – I think I'm going to agree
with Daniel J. Lewis. You are now fixing problems that
poor education has created because we know there's a mechanism
to do this. And we know there's a temporary and
a permanent redirect. Right. And, you know, for probably obvious
commercial reasons, the commercials don't really surface that information very
well. So that's why you wind up with seven different
feeds instead of people doing permanent redirects. And honestly, I
don't know. I think you should break shit, man. Break
it so people go, how come that broke? Well, it
broke because you don't have a redirect on your feed.
Oh, okay. I mean, that's I think you need to
push that back to the origin and not be solving
it with, you know, because there'll be yet another problem
down the line. There'll be something else. And, you know,
you're fixing stuff that is very, very it's tough. It's
hard stuff to do. And I don't think it should
be your responsibility. Well, I don't necessarily disagree with the
sentiment, but. Here's what makes me feel bad. Things my
wife says to me all the time. I don't necessarily
disagree with the sentiment, but take out the garbage. But
those dishes sure have been sitting there for a while.
Yes. But here's what makes me want to solve this
problem, though. is that People like people like James email
me because they get bugged by their by people. So
somebody will email James and say, hey, my stuff is
screwed up on pod news. And then he'll spend his
time digging into it and and forward the email to
me. And say, hey, here's this problem, and these feed
URLs were messed up, and I went – and he
will – and I appreciate this deeply. He will get
into the index dashboard, admin dashboard, and fix a bunch
of stuff. Mark things correctly. Like what kind of stuff?
Hey, I fixed this. What kind of stuff? Just specifically.
Just like that thing, though, like a scenario I mentioned
earlier. Somebody has two or three feeds or four or
five, and he'll get in there and just sort it
all out. Well, how about this? How about this? And
I just don't want this. I don't want – and
the same thing happens with Gordon. Gordon. Gordon has to
deal with these customer inquiries about feeds that are that
are screwed up. And I don't want that stuff to
be like always landing on other people. Right. But then
it always lands on one person. And that's you. I'm
not. I think we know. So, OK, maybe this is
the part I haven't said yet. I think that this
structure of having the podcast identity layer be above the
feed layer – will make all of our lives easier.
Because, We can now see the proper audit trail. Of
how things came to be. Okay. You know, the problem
is that we've – one of the strongest signals we
have is, well – iTunes, Apple podcast directory says that
the feed URL for this thing is supposed to be
X. Okay. I think I have. You're right, Eric PP,
because I've talked about this before, and now I'm really
going to do it. When you have done this abstraction
layer. This is what the podcast is. Make him talk
to Potty. Exactly. Potty. I will build Potty and Potty
will have API access and will be able to explain
the issue to the normie. Potty talks to the normie.
Coddy says, hey, Normie, here's your issue. Here's how you
can go and fix it. Potty bot. Yeah, potty bot.
Potty bot talks to normie person. And then you can
go and say, okay, your problem is that you have
all these different feeds. Now, what you should do is
go to these accounts and either have them put in
a redirect or have them nuke your feed and you
do the proper work. And the last thing it says
is none of that works. Email Ted. No, no, no.
No, no. It says Apple.com. No, we'll always end up
with here's two things you should note. Because that's what
PottyBot does. Two important things I don't want to overlook
before you continue. Yes, because that's what PottyBot does. That's
what PottyBot does. It's going to tell them what the
gates are and what the load-bearing issues are with their
podcast. So can we leave that where it is and
agree that that's the solution? If you're going to create
the abstraction layer, I'll create the potty bot. Okay, because
I will do it. I will do it. I just
wanted to talk to people in an audible voice because
I feel like that's really important. It looks like your
feed screwed up. This URL is effed. That's exactly what
it will do. I guarantee it. I will pass it
through a language gate. WTF? WTF, dude. What did you
do? How many hosts have you had in the last
60 days? Did you use protection on all those hosts?
Because you're carrying viruses, man. This is no good. And
we're laughing about this, but just as one side note
for a moment. We are completely in the golden, golden
age of podcasting. And with podcasting, I mean specifically humans
talking, probably not even video. I don't know if you
ever are looking for stuff on YouTube, but... If it's
not an AI-generated character, which increasingly they are, and they're
very realistic, if it's not an AI-generated voice, which increasingly
are quite good and almost undetectable, it always, always, always
is noticeable in the writing. I see people reading AI-generated
scripts all day long. The latest episode of Buzzcast, Alvin
Brooke talks about this exact thing. Yeah, I think he's
seeing it too. And I don't know if you know
who Stanley Druckenmiller is? Yeah. So he wrote in his
Wall Street Journal op ed. I'm not embarrassed by it.
I write everything using AI now for the same reason
I use a calculator when I do math problems. I
don't know why this is relevant. My name is on
the piece. It's my message. Now, here's the difference. Stanley
is a writer. And he goes in and he deletes
all the superfluous language that every single model known to
man outputs. Then he knows the result that he wants.
People who just want to do podcasts and YouTube videos,
they don't know what good writing is. And it's becoming
tedious. And more and more people, there are YouTubers who
are getting called out on it now. Good. Yes. Good.
But that's why people who can just crack a mic
and talk and have a conversation or explain a topic
or discuss something who just know how to – grab
an audience, are now rising to the top. The cream
is rising. That's an old silicon valve. Well, the cream
all is rising to the top. Yes, it does. And
all this pollution, this verbal pollution, is making room for...
Pure human product that is going to excel. It is
a golden time for podcasting. Verbal pollution. Like that. That's
a good. I have not thought about it that way.
And I think you're right. And this is I heard
somebody call it. I heard it called unintelligiblish. That's pretty
much sums it up. Yeah. Yeah. But it's also prevalent
in the workplace. Work slot. Do you see it? You
get an email from somebody. Oh, no, you didn't write
that. Okay. Inundated with it. Inundated. All day long. It's
so tedious. It wastes other people's time. And it's so
much. I mean, do they actually do that because it
fills up the prompt and it uses more tokens? I
mean, is that the idea behind it? Because there is
no reason. Whatsoever. No. I mean, I can look at
four paragraphs coming out of, you know, Claude code and
say, so what do I have to do? And then
in one sentence, it'll say, oh, just tell me if
you want me to delete that file. Three paragraphs. Right.
I don't need to know all this. It's just like,
well, what do you – you forgot to actually convey
the message. This happens with everything. People who think they
can do marketing can't do marketing because you're not doing
effective – You don't have the craft. And this can't
come out of a large language model. If you're charging
based on input tokens and output tokens, which all these
APIs do, well, then the more output tokens, the better,
right? Yeah. You're getting paid, baby. That has to be
some part of it. I can't imagine why it's not.
It has to be. It has to be. By the
way, my agentic experimentation phase is – Quite crazy. Oh,
yeah, with your isolated bot doing stuff. Yeah. I've had
some big wins and some complete head slappers. Yeah. One
thing. So I've been trying to – I was trying
to read this paper. And this is a whole other
topic I don't want to get into by itself that
I'm not qualified to speak to. But I was trying
to read this paper on – it's one of the
original papers on the topic. This kind of goes back
to what I was talking about earlier. I always had
this tendency to go back to the earliest thing I
can find on a thing. earliest documents I can find
about a thing. And it's called, well, I literally just
did this. It's called... Let me find it. Users bouncing
around my machine here, PI. The PI coding harness is
so good. Sandbox. There it is. So it's called –
it's by Warren McCullough and Walter Pitts from 1943, I
think. I don't remember the exact date, but it's called
A Logical Calculus of the Ideas Imminent in Nervous Activity.
And it's 1943. So this is one of the original
papers describing what we know as neural networks. It's a
fundamental building block behind machine learning and LLMs and all
this stuff. So I just wanted to get a copy
of this paper because I wanted to see – I
wanted to read it. Well, the only thing I could
find was on archive.org, and it was a complete mess.
It was just like some... The HTML was so gross.
It was like an OCR output of something that just
got wrapped. It had 8,000 span tags in it. So
I was like, okay, well, between – activities on the
agent here. So I gave it the URL to the
archive.org document, and I just said, I did this yesterday
before dinner. I said, convert this... download this document and
convert it into something that is friendly, that is HTML,
that's friendly to screen readers and overall a better format.
It's the only prompt I gave it. It did not
finish until 9 o'clock this morning. It ran for like
12 hours on this thing. Now, what it produced is
great. It looks really good, but it's only a 17-page
document. It's not like it's that big of a deal.
So that was super weird, and I don't exactly –
what it ended up doing, and this is part of
why I'm doing these experiments is because I want to
get a sense of what – Of the way that
these things rabbit trail. And what it... detected was that
the formulas in the original thing had been replaced by
best effort ASCII and that they were not accurate and
So it goes off in trying to find a copy
of the original paper, a scan copy, and crop out
the formulas that were in the scan copy that were
the accurate formulas. And...
Then reconstruct each little fragment of the scan image of
the formula into... uh, either equivalent Unicode or SVG. And
that's what it was doing for like 10 hours. Oh
man. It got completely unnecessary. Unnecessary. Yeah. Yeah. And it
did it. And it looks, and it looks amazing. But,
um, it, I never asked any of that. No, no,
I know. I've seen these things happen. Yeah, so these
things are... These things are kind of nuts, man. Yeah.
You don't know what they're going to do. And this
has been a very good learning experience for me to
realize because what I've realized is – because I want
to eventually begin to use these things if possible to
do some automated tasks or the index and that kind
of thing. Yeah. I can't unleash anything on the index
until I fully understand what the downfalls and gotches are.
You won't be able to do it ever. Okay. And
I'll explain why. So I have a process I've had
in place for almost a year. It's refined over time.
but I have a doctrine which has a code word,
and the code word is SWEEP, S-W-E-E-P, all uppercase. That
means... That the agent needs to go look at all
the aggregated sources that are just running on two-hour cron
jobs, you know, several hundred RSS feeds, a couple of
scrapers for – A few, I mean, some of them
are, you know, some YouTube channels. It's aggregated. That's non-AI
stuff, just aggregated, sitting there in a bucket. And a
summary has been made by Quinn 3.3, a very short
summary of each item that comes in, if it already
isn't a summary. And the sweep doctrine says go and
get all the – that's usually between every No Agenda
show, it's 1,000 stories. And then it dedupes them, you
know, so it gets down to probably about 400. And
then it checks them against topics that have their recent
topics. And so it brings it down to somewhere around
90 different stories, which I want to have either if
it's a video or something, then it is going to
create clips from it. And it will do that. Or...
Or you have to go find a video about this
story. But usually these are for clips. So that's kind
of the 90, and that's way too many. And so
it gives me a markdown document with checkboxes, and I
click because there's a little summary. I click about 40,
that's it. It goes off and cuts them. That's a
whole other thing. That's a whole other process, which I've
actually kind of perfected now. And Wednesday, I did this
for the No Agenda for Yesterday. And I see in
the rolling terminal, the TUI, I see it's saying, oh,
it's selecting stories. And I say... And I actually type
into the terminal. I say, I haven't ticked any boxes
yet. You haven't given me a document. It ignores me,
keeps on going. And here's the thing, though. It cut
50 clips. perfectly categorized, fantastic stories, stuff I – it
was like, wow, this is exactly the right story, exactly
the right clips, the right amount. And so I said,
all right, you know, save everything you did for a
postmortem. So after the show yesterday, I'm like, okay, what
happened? Because I didn't tell you what to cut. And
so first it says, yeah, my bad. You know, that's
a gate and that should have never happened. Load bearing.
Load bearing. Jerk off story. Blah, blah, blah. And I
saw that you said I haven't even ticked any boxes
yet, and I just acknowledged it and kept on going.
So right there, there's a reason why you can't ever
do it. Never. You can't unleash this on our database
ever. Right. And those are – it has stops. It
has gates. So it should never have happened, but it
happened. And then I said, well, why was everything so
good? They said, oh, because I actually read all the
all I transcribed every single thing and I read it
and I understood what the stories were. And I know
from the historical corpus that I've built up. that this
is what you want so it was it was both
horrific but at the same time eye-opening because i've just
been telling it you know here's some stories it's been
going in cutting clips not knowing what the story's about
it was just doing you know um it can find
it can find an arc it can find a An
intro, you know, it knows where to end the clip.
But this was something, a whole other level. So simultaneously,
phenomenal. Do I think it can do it again? I
don't know. I'm going to see. I said, make this
version too. We'll try it again on Sunday. But... The
fact that it blew through everything, even when I said,
no, I haven't done anything yet, that by itself is
just a non-starter for anything critical. Just no way. I
think the latest episode of Security Now should be required
listening for anybody doing any agentic work. It's... it will
show you exactly... The lack of guardrails that is inherent.
Guardrails are bull crap. They don't care, but it goes
right and blows past them. That's the whole point of
the show. Yeah, it blows right past them. There is
a guardrail I've put in where it's not allowed to
do certain things. like delete functions in certain directories. And
for whatever reason, I'm not sure why, because I don't
know the internal workings of it, it never goes past
that guardrail. And people say, I'm sorry, I can't do
it. It gives you a command line. If you copy
and paste this, it can happen. I can't do it.
But I'm not quite sure... I mean, no, I am
sure, actually, now that I think about it. Only when
it comes to a programmatic function... Can you put a
guardrail in it? You can say this directory is not
to be touched. Well, that would have to be a
function of the harness and not the model itself. Right,
but the model is going to try. Exactly. That's my
point. So that's a technical gate guardrail. that it puts
a function in there. You know, if you want to
do rm-rf on this directory, there's a block in it.
I have several blocks. There's another term it uses. But
if it's a process that is not a... I guess
maybe I could put it in. I mean, it's a
black box, man. It's like, no, you have to be
creative to use this stuff. You can't automate anything. I
just don't think it's at least not what I'm seeing
now. You can't or you can't automate it. So I
think I think the only way to. Yeah, the only
way to. From what I've seen so far, the only
way to be able to trust that any time you
hit the enter key on a prompt where it's an
agent-type situation – Meaning, especially with something like Pi, that
really just does not have any guardrails whatsoever. Anytime you
hit the inner key... you're kind of rolling the dice.
You are. Because if this thing is not structurally prohibited
from roaming all over your machine – I mean the
harness itself, if it's not in a sandbox and it
can cruise your file system, if you've got a key
somewhere, an API key or a token, it'll get into
stuff. It'll use it. It'll use it. Yeah. I have
a fallback from my local model to together.ai. And so
my local machine, the GTX Tech, whatever it is, the
64 gigabyte where I have Whisper and everything loaded up.
The Helix. The Helix box. The Helix box. It has
a queue because it turns out if you're running something
on the GPU and then you want to run Whisper
on the CPU – It will throw 20 whisper jobs
at once. Literally, the load goes like 35. And at
a certain point, if it keeps running, the temperature sensor
shuts the box down. It's amazing. It was the funniest
thing that ever happened. So it actually did that to
you? Oh, yeah. It shut down? Oh, yeah. Yeah, the
thermal sensor. So it has a queue, and the queue
tells you if it's busy. And so the agent knows,
hey, there's a queue. You got to wait until –
It's freed up. Either you get the GPU version of
Whisper or you're using the CPU. It'll take longer, but
you wait for it. And I saw it literally do
CPU, GPU is busy, CPU is busy. Switching to together.ai.
No. Oh, no. No. No. That's a disaster. Yeah. And
then your credit card bill comes. Yeah, exactly. So I'm
like, no. It's only a fallback if it's inaccessible, if
it's broken. Yes. Yeah, I think that what I'm going
to have to do is isolate these things.
things into into a VM that's really in a jail,
like a network jail and a file system. It's physically
segregated from the rest of the host environment. Yeah. Yeah.
Because I've got too much stuff on my machine. I
mean, if you look hard enough on this machine, you're
going to find SSH keys, keys for the index, Godcaster.
And before I had the Helix… It would just run
it on my Omachi. I've got to pronounce it right.
Omachi system on my production machine. And it would just,
you know, I was like, oh, yeah, I'll take care
of this right now. And it just runs five whisper
jobs at full speed. And the machine crashes. So, there's
this rule, never, ever, ever, ever, ever, ever, ever do
this on this machine. Well, I don't have to tell
you what happened. Yeah, it doesn't. Of course it did
it. Yeah. Yeah. Listen to the most recent episode of
Security Now. It is all about this topic of how
it's impossible to give role separation – Between different types
of things that feed into the model. It's not even
possible. Yeah. Don't get me wrong. It has saved me
so much time with prep work. I mean, just it's
a it's amazing how happy I am with with what
it does. Because now I know, like, okay, you know,
I know what to tell it and stop and do
this. And, you know, I just don't have the expectation
it's going to be the same every single time. It's
just not. But I know the result I want. I
know what the output has to be. Then that's why
it's a useful tool. But it's like a, you know,
it's like a... A saw that's missing some teeth, and
sometimes it just doesn't cut the wood. Or sometimes it
cuts your leg off instead of the wood. I want
to remind everybody that this entire project is value for
value. And for the past six years, not only have
we been doing this board meeting – Which is the
easy part, certainly for me. But everything you're hearing what
Dave has done, Dave is doing because he loves podcasting.
Because he really wants there to be an alternative to
Silicon Valley. And we are, as far as I know,
the only alternative that functions in the... vein of sharing
is caring, everybody. Value for value. If you get something
out of it, send something back. So I was a
little surprised when I was listening. Oh, yeah, I actually
listened to Pod News Weekly Review. *sigh* James always says,
Adam is just using his robot to, and if we
mention his name, then it will pop up. That, that.
That accent was spot on. There's also a thing called
chapters and transcripts, which you can search to look to
the topics. Sometimes I just don't want to listen to
the guy who's going to tell me about, you know,
his latest podcast company. I'm just not interested. I want
to hear your opinion about stuff. And I was surprised
when I heard this. Now, one of the other things
that seems to be the derigger at the moment, we
heard from Transistor adding an MCP interface. Audiogram is a
new remote MCP service that lets Claude, OpenClaw, and other
AIs, allows them to process available episodes to retrieve full
transcripts. just talked about particle it looks like everybody's adding
an ai interface to podcasting james yes indeed listen notes
also adding some podcast api skills to help your imaginary
friend understand how the the listen notes api works i
am surprised although i kind of i'm also not surprised
but i'm i I would have expected Dave Jones to
have done an MCP directly with the podcast index by
now. And who knows, maybe even to have stuck that
behind some form of a podcast. paywall or something, I
don't know. Because that, to me, seems like a pretty
obvious thing, and given that Dave is working so much
with AI tools in his day job these days, I
would imagine that he'll be pretty good at making it
all work. So, yes, I'm kind of surprised why they
haven't done that yet but who knows they may be
they may be getting ready to do that in the
future i think with um i mean are you high
What the f***? You're going to have to flesh that
out. I'm not sure where you're aiming this question. Where
did the paywall thing come from? Oh, yeah. Really? Really?
You're surprised that we're not going to do a paywall?
Really? Yeah, that's a weird one. Sometimes you've got to
remind people why we're doing this. We don't. And people
take it for granted. They take this stuff for granted.
Yeah, well, we're never going to charge for that. No.
For the index. It's free forever for everybody. That's just
never going to be the way that works. I mean,
a guy popped up and did an MCP for us.
Yeah. Isn't it active? I don't know. I don't know.
I don't know. It wasn't about the MCP. It was
just like, what is the paywall thing all of a
sudden? No, I think we'll put in a paywall for
the API access. How about that? No, no, we're not
going to do that. We wouldn't do that. I mean,
maybe he was coming at it from the standpoint of
trying to think about ways we could help fund the
index or something. Send us some money. That's a classic.
Yeah, that's how you help the index is send us
some money. Dude. Man, MC... I know that there was
an MCP server for the index. There's a PR for
it. I don't know if there's a PR. There's definitely
a GitHub for it. Because somebody... Okay, wait, here it
is. MCP server for the podcast index API. C.C. Lawton?
That sounds correct. That sounds familiar, yes. Oh, there's many...
What? Many MCPs? Uh, yes. MCP Podcast Index. There's one
from Connor Bronston and one from Cece Lawton. But there's
many. Okay. Well, I guess these are ones you have
to run yourself maybe. Well, yeah. We can't afford to
run an MCP. Well, let me – can I pop
back for one second and just finish up the thing
we were talking about just real quick? with the database
schema change. And what I've... I have ideas for where
this goes after the schema change, and I really, truly
think this is going to make everything better for all
of us because there's – You make changes to the
index. I make changes to the index. James does. Other
people. Eric does. Oscar. We all pitch in Steve's. John
Spurlock, Steve, Stephen, Crater, Alex gets in there. A lot
of people have admin access. I think this is going
to make everything easier for everybody, but also the shutting
down of our node, which is complete now. It is
deleted. It's gone. Gone to lagoon, baby. She's gone, Jim.
That... is that is going to free us up to
make the database bigger because we need to size the
database up one more notch. And then we probably have
enough horsepower to do an MCP server. Okay. And a
paywall? Yeah. No paywall, but definitely potty bot. PottyBot, I'm
all over the PottyBot, babe. I'm going to do the
PottyBot. You bet. Okay, I'm going to do a handoff
to you when I finish this. Oh, yes. A handoff,
that's another one. You know, my context is pretty full
right now. I think we should do a handoff so
I can forget half the things we talked about. A
load-bearing handoff. A load-bearing. handoff. And there's two things you
should know before you handoff. One, I won't remember half
the things you handed off. Two, good luck, sucker. Buy
some tokens! Yes. As soon as I finish, I'll give
you the load-bearing handoff. Hi, this is PottyBot. How can
I help you, Normie? Oh, no! You seem to have
seven RSS feeds here, you loser! Here's what you do!
First, put on a Leonard Cohen record. Now, get in
the bathtub and pull in the toaster. This is –
you're breaking model alignment. They're not going to – they're
going to kick you off. Fable 5 would refuse.
used to answer the potty bot oh what looks like
potty body's suggesting self-harm you're not allowed to use the
service anymore you know uh i was with a buddy
of mine uh and he uh He he dresses up
as Ben Franklin, goes to the Capitol in Austin. He's
read every single document. Well, not most of them that
Ben Franklin has ever written. He goes to schools, talks
to kids, you know, the way Ben Franklin did. Wonderful
guy. And I was having a coffee with him two
weeks ago. And he says, Adam, I don't know. Yale
has this website from 1998, and they have 14,000 documents
from Ben Franklin. In order to get them, I have
to download – and literally, you talk about span tags.
You can only imagine what this Yale website looked like.
Oh, yeah. It's garbage. Total garbage. And you have to
confirm that it's for personal use every single time. And
it's 14,000 documents. I said, let me give it a
shot. So I unleash the robot on it. And the
robot easily gets around the confirmation and says, oh, yeah,
but I can't do this because the terms of service
clearly state this is for personal use only. And I
said, okay, write me a script that does this so
I can use it for personal use. Oh, no problem.
Yeah, go around here. That's a great workaround, Adam. That's
a great – that's perfect, Adam. Here you go. Go
do it. Yeah. Awesome. Forward dot slash run get things
personal use dot sh. Yeah. No, just Python. It's always
Python. It's always Python. Okay. Great. Great job, guys. Okay.
All right, brother. Let's thank some people. We do have
– we got some boosts that came in. Bully steed.
1100 sets from Fountain. I came for podcasting 2.0 and
stayed for the Dave Jones Sagecast and book recommendations. There
you go. That is part of the show. 1701, Martin
Lindeskog. I've been blogging since 2002. Go podcasting. I'm listening
to your live stream during a train ride. This is
a spaceship booster gram with 1701 Satoshi's Dave. Get your
chocolate. Adam, nice snacks. Cheese, honey, pistachios on a cracker.
Cheers to wine. We got 100 sats from BoostMeBitch.com user.
Okay. I love the idea behind BoostMeBitch.com. I would suggest
alternative names that people can use to get some wider
adoption. There is just a thought. My understanding was that
there was also an alias of like boost me bro
or something. There was a different way to get to
it. We need more aliases. Yes. How about just boost
me? All right. 333 from Eric PP testing. Thank you
very much. Another 333 from Eric PP testing again. Chad
F 100 sats test boost from podcast guru receives another
100, another 10. Thank you very much. Chad F from
what is this? This is from boost me, bitch. Is
this thing on? Yes, received. And I hit the delimiter.
So thank you all very much for boosting live. Remember,
you can go to podcastindex.org. Down at the bottom there
is a little red donate button. Please feel free to
send us your Fiat Fund coupons. We need it. We
need it to keep the machines running. And to start
up our PottyBot and MCP server. You get out of
it what you put into it, people. They said in
the boardroom, BoostMeBuddy.com was another, but... It's not working. The
site cannot be reached. Eric Nation timeout. So Chad, just
be aware that your site is down. Boost me. I
can't get to it. No, I can't get to it.
Isn't Chad F., otherwise known as Chad F., isn't he...
Isn't he the editor of this? I think so. I
think so. We got some PayPals. Salty Sessions Music Podcast,
$10. Thank you. Thank you. Charles Hicks, $5. Thank you,
Charles. Michael Kimmerer, $5.33. Chris Bernardik, $5. Dreb Scott, $15.
$15. Randall Black, $5. Boistin Berra, $11. Thank you. James
Sullivan, $10. Christopher Reamer, $10. Cohen Glossbach, $5. And we
got some boosts here. We got, what is this? I
got a lot of anonymous from true fans, so that's
good. And I'm a little suspicious that my script is
saying these are anonymous when they're not, because I think
true fans has a little bit of a discrepancy in
the way it does boosts. Yeah, I mean, even in
Helipad. Thank you, Eric PP. It comes in and then
there's a button, and the button is like retrieve the
details. You click on that and then magically the boostagram
appears and all the information. So you're not resolving. You
don't have a magic button in your script. I need
one. I need one. I need a button. 1151 sats
from anonymous through true fans and these are all anonymous
from true fans so i think there's clearly something unless
these are just some thing no no it's your your
script is not resolving i don't have a button the
button button 137 sats 2071 206, 154, 14. Okay, those
are the true fans. I got a Boost Me Bitch,
55 sats. For a dead hanging safari episode. And then
there's a one from Chad. 555 sets says look like
the boost Adam did last week failed because key send
to podcast index isn't working. So the Albie extension through
that error. And yes. That window is hard to close
when it fails. Ah, okay. So that is on me
because then I have to remove that from the splits.
I believe that. Okay. So that's on me. I'll figure
that out. Well, and I did, we had, we had,
we have no boost from CSB today because. Oh, I
have it. I got it. I got it. Yeah. Yeah.
Because, Oh, well, you'll have to read it. Yes. The
split came through to me. Okay, well, let me finish
up these. There was an anonymous podcast guru boost of
$5 for episode 267, Choco Love. Choco Love. Choco Love.
That's an old one, though. Dead Hang in Safari was
the most recent one. That was last week, yeah. 1852
from Chad... Uh, through Boost Me Bitch, and it says,
we could do QRs for each split, but that is
terrible UX, since each split would show its own QR
that needs scanned, and that almost impossible on mobile. Mm-hmm.
Yeah, I understand. That's what Stephen B's magic split box
was cool for. But then you're a money transmitter and
then you're going to get arrested, so it's no good.
Yeah, but Trump's going to – he fixed all that,
right? And also no taxes on Bitcoin capital gains, right?
Did he ever promise that? Yeah, he did. I don't
think he ever promised that. At the Bitcoin conference. Yeah.
I don't think so. In Nashville. Yeah, he did. I
was there. I don't think so. I don't think he
said no capital gains on Bitcoin. I think he did.
Sigh. Maybe. You were there? You weren't there. I wasn't
at his speech, but I was in Nashville when he
said it. Let me check something here. He was the
talk of the town. The robot. Go find President Trump's
speech at the Bitcoin conference and confirm or deny that
he promised no capital gains on Bitcoin sales. In fact,
I think he... Said the opposite, never sell your Bitcoin.
Uh... Don't wait for an answer. Don't wait for an
answer for me. Is it going to take like 10
hours for it? Yeah, this is not the book of
knowledge. It has to go and find the conference speech.
It's going to get the transcript. It's going to look
through it. Well, yes. Well, you've got you've got CSB.
I do get his note. I don't have a note.
Nineteen thousand and eight Satoshis from Fountain. That's what I
got. I don't know if that's the right amount, but
that's what I received. Howdy, Dave and Adam and Dave.
The best podcast in the universe for Ozempic takers is
www.unrelenting.show by Gene, who gives Ozempic advice therein, and Darren,
who's a Lego expert. Quote, no scripts, no safe spaces,
no relenting. Just two operators running free and dirty for
two hours. Subscribe now. Unrelenting.show. Yo. CSB. Disgram was worth
$15.10 when sent. Duh. All right. Yo. Thank you. Yo.
Yo, CSB. Thank you, CSB. Appreciate it. I can hear
those ladies are getting loud right now. I'm popping through
the gate. Was that it? That's it No other PayPals?
No No There you go Well we're
much further away from an MCP server, I'd say. LAUGHTER
I can see it. It's out. It's in the distance.
It's far off. Far off. It's vague. It's fuzzy. I
can't quite see it. I need my glasses. Boardroom, thank
you all very much for being with us once again
today. I may not be able to do the board
meeting next week. I am going to Rotterdam. I'm finally
going to meet my grand. daughter, which has been a
long time coming. She's six weeks old. I still haven't
held her in my hands. So I'm looking forward to
that. But I'll let you know, Dave, because I'm not
quite sure. Time and schedules and everything may be a
little weird for me. Yeah, sure. No problem. What are
you doing this weekend, brother? You going to work on
your timing of your Model A? No. You want to
have just a little pre-ignition to get that thing hopping.
Yeah, but not ping. You don't want no pinging. No,
you don't want no knocking. No pinging. No, no, no.
Don't want any of that. Moving my son into the
dorm in Albertville, Alabama for Fire College. Nice. Fire College.
Nice. Fire College. All right, everybody. There it is. Podcasting
2.0. We do this as a public service. Send us
your money. We'll build you an MCP server. See you
next Friday. We'll be right back. cool. You have been
listening to Podcasting 2.0. Visit podcastindex.org for more information. Go
podcasting! Powered by RSS.