Oh, podcasting 2.0 for October 9 2020, episode number six name
your space I'd like yelling on a Friday. Makes me feel good.
Ladies and gentlemen, to Dragon Slayer Dave Jones on the
microphone.
Yeah. I just made a mistake of scarfed down some lunch I ate a
sandwich. But then I made the mistake of I ate a butter finger
right after that. Oh. And then and then I realized that had
some more sandwich. And so I ate that. And I was like, you know,
I really, I don't want the taste of roast beef sandwich in my
mouth for the whole show. So I had to eat another butter finger
to compensate for having food
waffling issue real issues, man. We should talk to somebody about
that. Yeah. All right. My favorite is vanilla yogurt and
cheese. No. Cheese. Yeah. So I'll take a bite of cheese. And
then I'll have some vanilla yogurt with.
That's a strange one. Yeah. Preferably. green jello and
carrots.
Oh, yes. There you go. There you go. There's a nice callback
episode number six, which means we've really only been at this
for less than two months. Right. And we've probably had a week of
calls and started and I think we recorded the first episode a
week before we released it, if I recall correctly.
Yeah, it feels longer than that. does.
It does well. So we got some exciting news for today. Because
just before we started, you dropped a namespace and did a
drop down menu namespace dropped on the hub.
Yeah. Yeah. So I mean, do we what do we want to do want to
talk about some donations? Or do we?
No, no, no, no, no, I want to know, don't bury the lead. Let's
get to the namespace first, and then donations definitely
touched posted to ease and other stuff. No, no, no, not.
This is this is the lead you got? We got lots of stuff to
talk about.
All right. Yeah. So I spent a couple of days writing up.
Something is, first of all, the namespace is not meant to be I
mean, this is not a complete thing. This is just something to
get everybody started, maybe
you should back up for a second, I'll just give you my
understanding of what a namespace is for people who are
listening going, Oh, no, no, no, don't just do technical. Debt
for a namespace is a way to take the existing podcast
infrastructure, which is based on RSS mainly, and add
functionality to it. Is that fair?
Yes, it's a way to extend a an XML document, without having to
write a new document. Document definition, right. So which
Google did for their for their podcast, you know, directory
thing, but or whatever they call it, Google did that they wrote a
DTD. And all this jazz, but you can sort of get around that by
just creating a namespace. And it allows you to extend the XML
with new element types. Easily
now when when Google does their own DTD? Is that their version
of capturing the space? Hoping for adoption, hoping for
adoption for to their?
Maybe? I think they I think they do it more from the standpoint
of just that they're, they're just kind of super geeky. Oh,
okay. You know, and they just kind of go off, they go to the
very bottom of everything. Right? Well, this is the right
this is this is how you do
watch us, we got a lot of people to throw at it. Okay. I
understand. That's my
impression. But um, yeah, so this, there's many namespaces,
for RSS that have cropped up over the years. Some of them
specific to podcasting. Some of them not. There's a list of
them. So what I posted in the podcast, index dot social, was a
link to the GitHub repository that contains the write up for
this. And let me just jump over there real quick.
Because this is where you get to put your writing skills to good
use, and get to write some of that Dave Jones poetry.
Yeah, you're setting me up.
I'm digging it. I haven't even I only read the first line. I
didn't know we started the show. So
yeah, we had a debate about whether you could spell holistic
with the nature of who we neither one of us knew actually,
we had to Google.
Can I read this? Can I read this? While you're looking that
up? Can I just read this paragraph? Go for it. Okay.
Podcast index namespace, a holistic RSS net namespace for
podcasting. That is meant to synthesize the fragmented world
of podcast namespaces. The broad goal is to create one namespace
to rule them all. That is easily extensible community controlled
slash authored and addresses the needs of the indie podcast
industry now. And in the future. The largest, the largest podcast
platforms have shown virtually no interest in extending their
namespaces for new functionality in many years. Our hope now,
this will be our mission. Our hope is that Yeah, can you is
not allowed to change that or Dahlia was I'll read it, I'll
read it properly, then. Our mission is that this is our
mission is that this namespace will become the framework for
that in the podcast framework, that a framework that the indie
podcast community needs to deliver new functionality to
apps and aggregators. Do we like the indie podcast moniker?
I don't know. I mean, I tried to set it apart from
unaffiliated and affiliated or is that too political? I don't
know. Yeah. Maybe independent just indie just you know, all of
a sudden, you know, I gotta wear black jeans have long black
hair. I just don't I feel so emo emo. That's what I
put that in there. Okay, Emo cross it up at
the end. I think independent,
independent or unaffiliated?
I think independent independence better. Independent,
independent, because, yeah, because they're in they're
independent of any overlords, they're part of the community.
So the idea here is that this whatever this is indie,
independent, unaffiliated is that this namespace is
targeting, basically the whole world of podcasting outside of
really about three, right? Google apple, and let's just say
Spotify.
Well, then why don't we just say what it is the non corporate
controlled asshole industry,
as maths, a lot of work on many words. Is your book your book
fixing?
Anyway, I love it, I totally understand what it says.
Yes, the idea is that those guys don't even need. I mean, they
don't really need a namespace anyway. They can kind of do
whatever they want in the background. And however they
want to do it. Yeah.
Yeah, they Google has a copy of the entire Internet. So I mean,
like, what, what do they really need? So, I mean, this is really
meant to give people like Todd Cochran at blueberry, like us,
you know, like, fireside and these guys that are trying to
pull in, as well as other podcast app developers who run a
large back end. We're trying, you know, we're trying to solve
some problems and give new functionality to apps. And they
just the big guys just don't seem interested in furthering
this at all
right, because they have zero benefit to them. So, right,
they'll just do some, they'll just do something off on their
own, and they don't really care anymore. So this is meant to get
the ball rolling, and to be a central place where people can
do pull requests can discuss. I'm sure a lot of that will
happen on podcast indexed by social Putin. Basically, this is
just the repository, go ahead and fork it. And, you know,
start playing around with with your ideas. The thing, there's a
couple of things I feel pretty strongly about. And I can go Oh,
yeah, yes, please. And so just so I understand the process. So
you can fork it in your own GitHub, you can make changes,
then you do a pull request, which then means hey, I want
this Incorporated. And then how does that get decided what's
pulled in?
It? There's a couple of things that can happen. It can, it can
have conflicts with the existing now, this is less likely on just
documentation. But a typical pull request can create a
conflict with existing code and other pull requests, and you
have to basically decide who wins or decide how to go about
merging that in if it clobbers, something else, that's
important. But the other option is that everything that the
checks workout in there says okay, this is fine. And then you
just have to decide whether you want to incorporate it or not.
So there's a right you know, a repository moderator or owner
who makes a decision and you
potentially have 1000s of what are the individual items called?
Elements, elements, so this could have thought Dozens of
elements ultimately. Is that not
a bad idea? Yeah. Okay, that'd be a bad idea. Okay. So just to
go over the goals. You want me to do that? Yeah. You want to
read them off?
I'll read them off. I'll read them out. There's a good
proofread at the same time. Have you taken notes on those
important changes? No, I got a pencil. Go one. Eliminate
redundancy. Do you mind if I read it in the broadcast voice?
Because I really
think that would be that would make my day. It would be
wonderful.
I'll do I'll kind of do Attenborough if I can.
Oh, is are there any other creatures? Yes,
there is significant overlap amongst the many existing
podcast namespaces.
That is so pretty good.
Each platform and public publishers created their own
namespace to give their respective system and audience
and audience the metadata they need in the way they want it
delivered.
Yeah, so a good example of this would be fireside what
his fireside, fireside is the podcast host. Yeah. Okay. So
what have they put in? Their stand? Benjamin? Right. Thanks.
Yes. So what what has been put in there that is?
Well, they have a namespace, okay. It's small. All right. And
within this repository, you can look at the existing namespaces
dot txt file, and it shows a list of them. That's, that was
compiled by Christopher I seen in the podcast.
Oh, right. Right, right. Yeah, he did for like the top 10 or
top 20.
I hate I think he had this list is extensive. He sent me a
bigger list. This got a lot of them in there. So for instance,
firesides namespace just has a few extensions to it. We pull
that out.
And that's so that they can run stats for their users and other
things. Like,
let me pull it up at transfer case here. Yeah, well, these are
hosts their extensions, our host name, Gen date, player URL,
player embed code. So I'm thinking that that is most
likely just a way for them to track some of theirs. The
hostname is a way for them to figure out maybe if they have a
server farm, which, which host generated the RSS feed for Boca
blog traffic tracking, and maybe I'm just guessing and then the
player URL that's probably a web based, like player html5 player
app. And then player embed code is probably just a way for you
as an iframe
so so we would likely just take these and put them right into
the namespace.
Yeah, that's. So that's one of the next, let me get back over
there. That's one of the next goals listed. As goal, that's
goal number five, so we'll get there.
All right, goal number two, avoid attributes, attributes,
and XML elements should be used only when absolutely needed the
preferences to create a new element type, rather than reuse
the same element with different attributes. For example, instead
of using podcast index colon, image type equals large, we
would use podcast index colon image large, this makes the
corresponding aggregator code easier and more linear. I
understand why that is. I got that.
And other people may not agree with this. But my personal
preference is always to just have the the element with a
value in it and avoid attributes if at all possible. And the
reason is just because it gets messy, your code just has to dig
in farther, lots of question marks. Yeah, and the attributes
can be, they can be hard to handle like in the node, XML
parser that we're using now. It's, it can be a mess, to try
to dig those attributes out. So I would prefer to avoid them. I
think it makes for easier, easier code.
Okay. All right. Goal number three use RSS native elements.
The RSS version 2.0 specification already has a
robust set of defined elements, we should aim to use those
instead of creating new ones. Instead of creating a podcast
index colon owner element, we can use the already existing
Managing Editor element that can contains both name and email
address in situation like so don't want to reinvent the wheel
in situations like item level images where the RSS spec never
defined that element, it is appropriate to define new ones.
Yeah, and there's a lot of have the RSS namespace or excuse me,
the RSS spec. There's a lot of that that is not used at all or
properly. And one of them is the managing editor is a good
example of a tag that's just not used. Often. Probably
underutilized.
underutilized. That's a better term. Yeah, a better way to say
it there and there's quite a few of those that are that are
underutilized like you know there's one that we use in free
control if Britain controller that shows is the source of
where you where that item came from? Oh, okay. No. And yeah, we
used it for some creative purposes so that rather than
reinventing the wheel here, it makes sense to just use try to
use what's already there as much as possible.
I agree. I mean, I, I kind of vicariously went through RSS 1.0
to 2.0 at a distance with Dave Winer. That's that was quite an
ordeal. That that was not not to. Not pretty to watch,
actually.
Yeah, so a lot of fighting.
Okay, goal number four keep existing conventions. Oh, here
we go. reinventing the wheel helps nobody, when at all
possible existing convention should be maintained. For
example, it would make sense to turn podcast index colon
explicit into it. unary element. What's a unary? Like a single?
Single operator? Oh, not binary. But unary?
Yeah. That may not be the appropriate use of that word.
I mean, I read it almost as urinary so
gotta get the bathroom.
Okay, adjectives are involving a single component or element, a
beautiful, beautiful word. I'm going to use this in regular
language.
Okay, I just sound appropriate. You think that's right. I mean,
basically, what it would mean is like, the element is there for a
while it it goes on to say if you want to keep reading,
okay, so it turns it into a unary element, where its
existence is taken as a yes. And its absence as a no. Yeah,
totally makes sense. You don't have it in there. It's just off.
You put it in there. You can switch it on. Yeah. But that has
never been the standard. Oh, and we need sound effects for this.
Since we're messing around anyway. Okay. Let me reread
that. So for example, it would make sense to turn podcasts
index colon explicit into a unary element where it's existed
is taken its existence is taken as a yes. And its absence as a
no. But that has never been the standard.
Long way to get
to early, given us how this namespace will probably sit
alongside at least one other namespace. It makes sense to
keep existing conventions in place. And I agree.
Yes, we just don't want to. We don't want to have to reach out
to people and expect stuff to work already. Yeah. Basically,
that
we want people to just upgrade for more fun and valuable cash
and prizes.
Yeah, that's, that's there you go. And there's there's a cash
and presence element. Oh, nice.
Oh, number five, the general, there's no way to address every
possible metadata point at each platform would want. That is not
the aim. Instead, we focus on defining the elements that would
be useful to the broadcast set of apps, publishers, platforms
and aggregators. Individual parties can keep their
respective supplemental namespaces small and targeted as
an adjunct to this larger namespace.
Okay, yes. So the example of the fireside
that's kindly do say that small, they don't necessarily have to
put it in. Yeah, we
don't have to try to reinvent what or we don't have to try to
incorporate what fireside is doing in our in this broader
namespace because there's always going to be like this one
fireside colon host name. And element is something that
probably nobody else wants or needs, but then, right, so it
doesn't make any sense to try to stick that in here. And when
they can just their namespaces small, and they can just include
their own route beside it. I mean, you can have 25 namespaces
in an in an XML document if you want. So that's fine. We don't
we don't want I'm trying to say is that we don't have to take
every existing namespace that's out there and take all the tags
and shove them all into this one.
I wouldn't mind doing a podcast called namespace of the week,
and we just read through a namespace,
oh, my God, that would be horrible.
Bear that in mind as we continue reading this one,
never another donation.
So then you have the element list. And I can
go through this if you want me to. Yeah, it might be quicker
that way. So one thing that J. James Crillon has mentioned a
couple of times, is the ability to specify different size images
in the in the RSS. So that's what these these first three are
image, large image, medium image small, and there's some pixel
width definitions in there about what suggested and it's
basically just to give hints to the player or app or whatever of
how to what you want to grab first Should be pretty self
explanatory. Now the categories, but I don't I'll say this
upfront, I don't expect that everybody is going, I would be
naive to think that everybody would ditch the existing
categories that are out there in podcasts and start using
podcasts index categories. That's really not what not what
this is for. It's basically, we're going to be consuming
these, these namespaces. Also, we're already set up to handle
what's out there already. But as far as,
right, we can display everything that's already in a namespace
pretty much, right? We
can, yeah, so this is basically just our category name names, I
like them. I think our category list works well. So this is just
a way for, to I'm just putting in there to be used whatever.
The now Now we'll start to get into some, which I think I feel
pretty strongly about location. Spotify has a country of origin
tag in their namespace. And that when I read through their
namespace, that seems to be the only serious contribution that
they've made, as far as that, that their namespace goes
everything else. I think there's not really much there. But the
look, location tag could be a country code and a locality. So
something like us, Alabama, or Brazil, Rio, like you could have
in a separate about pipe character, since that'll never
really be an existing character in the language. So that's,
that's my idea for that. Again, I think the tag is important.
But how its font had the final implementation of it is very
much open to the community to decide.
Right? You know, what have those really funny? What is it called
the I should know this. I'm a general license. That Maidenhead
grid square locator. What is that? A Maidenhead grid square
locator? So, I'm going to enter my zip code. And I'll enter my
and why they didn't want my callsign I don't think I need
it. But I see. Okay, zip code. We'll just work on that. So my
my Maidenhead grid locator is e m 10 D, F. And it's an area of
not quite sure what how big the area is. But it's big enough to
obfuscate where I live, except the.is. Right in the middle. It
did not. It doesn't. That's not good. That's not disclosing my
address. But you look at the middle of the square like yeah,
that's where I am. So you could also offset it. But what I like
about it is that it's this is well known. There's tons of
API's on the internet is ham radio that invented this. And
I'm sure that Well, I'm sure it's from something what is it?
Maidenhead grid square locator? I'm sure you've never heard of
this. No, no, I
have no idea what this is.
Yeah, it's, it's been used ever since. Then, if there's a wiki
page about it, here we go. Maidenhead locator system is a
geographic coordinate system used by amateur radio operators.
What's its history? I guess it was an amateur radio. came from
the German cure a locator system. And then they had they
had the working group meeting in Maidenhead England. Okay. Okay,
so there you go. But, okay, Maidenhead locator compresses
latitude and longitude into a short string of characters,
which is similar in concept to the world geographic reference
system. Except it's really easy to do, but it uses uppercase
lowercase. I don't know if that's a problem.
Shouldn't be Yeah, anyway, and I know that it's a good idea.
The bottom line is when the apocalypse comes.
Where you're gonna say the world namespace is gonna save the
world.
Where was that? Where was that drop? I had this somewhere. Save
was it save the world? Save the world.
I just sent you clips, by the way. Oh, thank you. Now
here we have ham radio, guys. Ham radio is the public service
network of last resort, when the apocalypse comes where the guys
who are going to save the world.
Right, right. So at least we'll know where the nodes are and
where people are and where the podcasts are.
When you go into a car when you go into a conference in the
keynote starts and that's what the guest sounds like do you
just do you just kind of like hope put your head down and your
hands
I'm all jacked. I'm like, yeah, yeah, we're gonna save the
world, man. Hell yeah, we're all Remember, the ham radio guys are
really frustrated firemen and EMTs basic.
I've got that I had a ham radio license. Got it in high school,
there's a well known High School, it was eighth grade, we
had a class at my junior high called consumer electronics. And
they present it consumer. No, no, I'm sorry. Consumer Science,
I think is what it was called some crazy name that didn't have
anything to do with what we actually did this, the first
like, the first half of the year was aerospace, which was fine.
And the second half of the year was get your podcast and get
your ham radio license. And so we like the whole second half of
the year for like, I think it was like fifth period during the
day, we would just get in there and just be CQ, and and learn
and, you know, learn Morse code and the whole nine yards. And
then at the end of the year, we all our teacher was the proxy,
and he gave us the test. That was fun. All right, very clever
ham radio license it like, I don't know what I was, like 15
or 14, like that
back in the day you had to code back then probably had to be
able to do code. Yeah, it
wasn't real fast that I just did. I was
12 words a minute guy. Yeah, I haven't seen your clips yet. But
maybe it's going through the pipes.
Okay, it's just as the Okay, so the next tag is the one that I
think are the next group is one I think is really important. So
it's, it's the locked tag, yes or no. And I'll just read the
description. This is a channel level element. This tells other
podcast platforms, whether they are allowed to import this feed.
A value of yes means that any attempt to import this feed into
a new platform should be rejected. It is expected that
podcast hosting providers will enable a toggle in their duty to
allow their users to turn feed transfer log on or off. And so I
think this is a way to directly combat feed import fraud. The
same way that pod news exposed this past week with anchor.
Right, right, right. Everybody knew it was going on. But he
just laid it out. Here's it, here's exactly how you do it and
exactly how easy it is. So if we have a lock, element locked
element in the feed,
then it should not be allowed to import and what do you think we
have to make sure Ankur adopts that?
Well, that's that's why I think this is so important is because
if as long as there's nothing out there to actually no formal
spec to stop it, there's no way to really shame them other than
just doing what what the what Panis did, and just publishing,
you know, articles about it. But if if there's a formal spec that
says, This is your, I've chosen not to allow you to import this,
and you do it anyway. You're, you're sending a clear message
to everybody. You're just basically flipping the middle
finger to the whole to the whole industry, and the shame gets you
10x That's my fate. I mean, there's a if everybody says,
Yeah, we agreed to adopt this standard, and you don't, you're
a douche. Yeah, I mean, really, because it's not it's not like
it's a like, debatable thing. If I if I say if I put in my feed,
transfer a lot. Yes. And I that I'm clearly telling you not to
not to clone my feed. Right, if you do it anyway. He be your,
you know, you're just given me the middle finger.
Should we consider naming this? I mean, it's this document
called podcast index namespace. Yeah. Now, should we consider
just calling it podcast namespace?
That's fine. Yeah, that'd be fine with me. Let's do that.
Just change it to podcast. Yes.
We seem more independent that way. We are. We actually, and
the whole thing is independent. That's the point. That I think
that's a lot better. Because if it says Spotify namespace, I'd
be like, nope.
Yeah, me too. I think that's great. Because this this really
is the community's namespaces
Yeah, exactly. Exactly. Okay. And I totally agree on that. So
And moreover, for that very reason, is it's one thing to say
well, the podcast index namespace says nothing to say,
Dude, bro. The podcast namespace says this. So you got to start
rejecting those feeds anchor.
Yeah, that's that's a good that's a good point. Because
it's just from the naming standpoint. That's
also I'm really good at shaming once I have the ammunition.
Yeah, I know where I'm looking. forward to it.
Okay, we got locked. And so there's a couple of tags that
kind of go with that. And this may seem redundant. But I feel
like it's necessary. The next one is, is, let's just call it
podcast colon email. And that is a channel level element, an
email address that can be used to verify ownership of the feed
during a move and import or import operations. This could be
a public email or a virtual email address that the hosting
provider that redirects to the owners true email address. So
this goes along with the transfer lock or the import
lock. Right? Yeah. And you're gonna, you're giving an email
address, this says, If you want to communicate with me, for
tech, about doing something with my feed,
just how you just like domain registration.
Yeah, exactly. Like I can go in, you could say that you can say
that's redundant, because there's there's iTunes owner
email. There's many Yeah, but
but that could be important for a number of reasons. One for
it's just two different roles, I guess. I mean, it's just like
DNS registration, you have administrative financial
general. So yeah, that made those roles are understood, I
think,
I think if there's a new element, specifically targeted
at this, then what's out there already is a mishmash of, of
people's actual, some of them are actual email addresses, like
in the owner email. And some of them are just kind of throw, you
can tell they're just kind of junk. If this if there's
something new going in, like this namespace, you could say,
Okay, this is for this reason. And this is your chance to plant
your flag and put a put an actual contact address in this
this little achieve this goal, right. So I think I think it's
worth having that redundancy in there. And it could even be
change, it doesn't even have to be email can be changed to be
something like podcast colon contact, and that could be
either an email address or a URL to the at the hosting provider
who, you know, who knows that's, we can debate this, which is
fine by me. The next one is previous URL. And I feel like
this is a really good idea to the previous URL tag contains,
there can be as many of these as needed. And every time that a
podcast moves from one URL to the next, it should add a
previous URL tag, an additional previous URL tag to the channel.
That will it operates like an email header, wait email,
does that allow for archives? Or am I just Well, no, it'll
it allows you to associate a pre what, what a previous Feed URL
with its new one, so that you can deduplicate got
it? Ah, okay. Understood.
Yeah. So somebody moves from blueberry to to Lipson, and they
don't, and they don't actually do it, they don't do a 301. And
they don't tell anybody, right, they can just, yeah, you end up
with two feeds. And it takes you a long, it may take you a long
time to figure out that those that the old one is dead now,
right? This, this lets you say, Look, if this podcast were to
happen, were to pop from host to host, maybe five times, adding
all these previous URLs would would let you always deduplicate
and remove those old URLs from your feed.
Great. That's great.
The new feed URL, again, it may seem redundant, because Google's
namespace has a new feed URL tag, and also iTunes has a new
feed URL tag, but they don't match. Don't use the same
format. And so since we're already sort of in this mindset,
it makes sense to me to put a new feed URL into formally into
something called the podcast namespace, right. Okay. Yeah.
And then here's another one that I think some people have wanted.
And I think it's a good idea is the podcast, colon ID. Now, if
you just leave, if you don't put a platform in a platform
attribute, if you just put in podcast that the podcast colon
ID, and then the value is a is a number, it's assumed to be the
podcast index ID, right? If you put in platform equals, then you
can, there's some listed down in the further in the document, you
could put in the slug of whatever your provider is. And
then you can put not just your provider so let's say Now that
you're listed on blueberries directory, us, Google Play, and
iTunes, you could put all your IDs on those respective.
Oh, good, good.
I like that one for each. And that's another way that we can
that aggregators can be signaled to can be given good information
to deduplicate. Now,
will you rename all these elements as well, to podcast
colon location? Does that conflict with other namespaces?
No, it doesn't. Okay, cool. It does. I don't I don't think as
far as I know, I don't think there is a podcast namespace.
Okay. Well, one, just called cod puck. Okay, cool. So those are
the those are the elements that that I felt were good to start
with. And I really feel like the transfer locking in that. And
the tracking ones are, are good will would give good new ammo to
the podcasting world. As well as to aggregators and app
developers. The now there's some that I know that people have
wanted, and I didn't know enough detail about it. So I just kind
of sketched them out real quick. And that's in the element. List
proposal section.
Right? We have captions, transcripts and alternate
enclosure. Yeah. It's also nice. That's so that's where you can
do alternative like IPFS, or some other beat torrent, or
different bit rates? Oh, yeah. Nice. Yeah. Nice. Nice. Nice.
And I think that's one that James one of the captions and
transcripts are one that Todd Everbloom wanted. And there's
been a few other people piping up to do like things like
chapters. There's plenty of ideas out there. And so what I
would say is, let's just, let's start this discussion. Let's
start hammering on this thing and try to get something. Let's
try to get something good put together.
That's a lot of work.
Yeah. Yeah, it's, you know,
I think that how do I help you drive this? How do I help just
by? Yeah, how do I help you drive it get people to
participate? Firearms or can? Poison poisoning? Threat of
poisoning?
Yeah. Yeah. You never know when it's gonna happen. So I mean,
you better get on board. I think just just talking about it. And
if, really, if we can get the podcast, news guys and the in
the podcast platforms, on board, luckily, we already have
connections with quite a few of those guys. Yeah, guys. Good.
Yeah, we could we can just get this out there. Because I think,
what would the feeling that I get is that everybody has wanted
this to happen for a long time. But there's never been a single
entity that's tried to pull it all together. Yeah, everybody
did the same table.
Yeah, that seems to be a lot of consensus about that, which I
love that because that's exactly what we have. We've got to an
actual community, people who care and when people care and
other people show up who care stuff gets done, and I
definitely see stuff getting done.
Podcast index dot social has become as much about general
podcast technology techno technology needs as it has about
the API's. So
absolutely. And there's such a good mix of people. A really
good mix of people have all kinds of ideas. I'm I'm just
blown away by it every single time. And just all these me and
everyone has. I can also see a lot of frustrations from for a
long living frustrations that people are like, Oh, fuck,
someone wants to listen. Just listen to me. I like it. I
really do. It was actually it was quite nice listening to Todd
and Rob on the media show where they I don't think I've ever had
that done where I did an interview and then the same host
went back and analyze the interview.
It was kind of necessary I'm glad they did it.
Yeah, I'm super happy they did it because it also taught me
something that I guess I maybe I come across as a raving lunatic
sometimes to some people when I could Yeah, I'm always in my
head. I'm visualizing everything and and it just comes out of
that little a lot of like diarrhea of the mouth just flows
out for like, why is he talking about?
Did you get the clips? Did you get this close? Second? Because
I've got some good diarrhea of the mouth in there.
Oh, nice. No, I don't have them. Well, they bounced backwards.
You know, I have a limit on my mail server. wouldn't think so.
Yes, pretty small. Anyway, weird wonder why they addressed it to
you again. We just got a big donation by the way. $100
Oh my goodness.
I don't know if this person wants it read
though. So maybe we can use your first name only?
Yeah. And then I'll email them and see if it's okay to mention
on the next show.
Now, are you emailing from your regular account? You know, I
have pretty strict rules demark and all that stuff.
And mail from my podcast index account. I should probably do
that from just do
it from the Gmail, we know that for us. Yeah. Okay, because
there's something with the with the demark records on on the
emails because I'm, I'm getting all kinds of I haven't really
looked at it. I'm getting like errors.
Or you get, like killed on that flood.
Yeah, yeah, I got a serious mail email attack, not a bomb and
attack. And it was just that long was like, couple months
ago. Yes, five months ago. And I've just got 10s of 1000s of
emails a minute, but all subscribing me to stuff and oh
my god, it was a nightmare. Thank God for Mark void zero.
who rescued me. They put the clamps down on that thing, too.
Yeah. Well, he's an email expert that that's actually what he
loves. And he's so proud of his email. He's always been trying
to get me on his on his servers and like, gotta migrate all that
shit. And now it was Do or die. And he said, All right, man. I'm
cool. And he's got it locked. I mean, people were trying to send
me email from their from the Apple Mac dot Mac account or
what I iCloud account, and somewhere so some SMTP server
had showed up on a UBL. And yeah, like, well, Apple should
know this. But all right, I'll put an exception for them.
So do I have the hot pipe? Does it come straight 3d If I get
from my Gmail? Oh, yeah. Yeah, yeah. So you do alright. Yeah.
Okay. I just I just recently got him.
Okay. Yeah, that went through. We got we got to figure that
out. There's some some misconfiguration with where
we're using Mailgun.
on ours, now we're using FastMail. Okay, for podcast
index.org. So that's pretty much the namespace. And I want to I
wanted to just give everybody enough to get them started. And
the, there's a couple of other things in there. There's the
categories, dot json file, likes, that's just a list of our
categories. I'm not concerned about category stuff, just don't
even worry about that. Example. dot XML is just an example feed
that shows our namespace or excuse me, the podcast
namespaces. We're going to rename it shows the podcast
namespace living side by side with the iTunes namespace. It
just gives a good visual example of how this stuff would look in
practice. Excellent. Thank feed an owl, we'll say this. So it's
assumed I needed some some kind of like, fake ish, real world.
Stuff to stick in there. So I'll put in the podcast, podcast
colon email address, I put like a what would be kind of like a
virtual blueberry address. So it's assumed that this podcast
is being hosted on bluebridge Picton Got it. Got it. Anyways,
that's namespace Yeah,
like it was and just dropped out of the blue. But I think it was
time you were talking last night. Like now I'm gonna do
this namespace. See, I think with by changing the podcast,
namespace and changing all the element names, I think that'll
just make it even more clear. What we're trying to do here.
That's, that's a great idea. I think that's that's exactly what
we need to say, well,
these are the things that I went through with the RSS 1.0 to 2.0.
That they you gotta yeah, there's people get. There's no
context in text often, especially not computer code.
Yeah, you know, so every colon every word is, is important.
I've learned a lot of coders take language very literal.
Yeah, you have to.
Yeah, here's a strong, there's a strong Asperger's element to a
lot of programmers. Yeah.
Yes. It's. And I was just thinking about this last night.
I had a company that 700 employees, we had a lot of
coders and the overlap between musicians and people who write
code is very strong. And you and I were talking about our talking
about something last night and we're, you've been doing this
for 22 years. And we're talking about some some kid whose first
project took off as like, now he helped coders truly are like
musicians. You can be working now the gigs haircut for a long
time, you can get a good corporate gig, you know, play
in, in the theater, whatever it is, it's all kind of the same
thing.
Programming is such, you said this before, a dozen times that
programming is as much as much art as it is.
copes. Yeah. Which is why, you know, when I do it, it looks
like I'm finger painting
me to have you got you know, and that's the thing, it's like you,
nobody's going to use your nobody's going to use your
software because the code is so beautiful. Yeah, but that's just
not there. Like, oh my God, look how pretty that code is. I'm
going to use this product. No, you use the product because it
meets your needs. Right. And, and it and it does it in a way
that this satisfying to you. But But the the code itself is a is
an aspect of the it reflects the programmer, it reflects who he
or she is. And you can, you know, you can just you can see a
certain style in a certain person and it just is fairly
consistent. Like a signature, you know, that.
Right, right.
Did you get those clips?
I did? I certainly do.
Which one was it? Okay, so this is funny. I think Ralphie
dropped his new version of cast cover. Yes,
it looks beautiful cast coverage.com That thing is
fantastic. I switched it to Dutch language. Yeah, just going
through hidden through Dutch podcasts, like, you know, I
speak Dutch fluently. And I have no idea what's out there. And
all of a sudden, I'm getting it random is very nice experience.
Is, is there a okay, I'm not bilingual. So when you're
listening to some, let's just say you're listening to
somebody, something in English, and then it flips, like
immediately to, to Dutch. Does your does your brain? Does it
take a second to adjust? Or is it just an automatic?
almost automatic? Now, of course, it depends how recently
I've been using it. But I read that I read a lot of Dutch just
for news flow and people who send me stuff. And I and I
remember when I was a kid, we moved there and it took me a
while I was translating, you know, translate from Dutch to
English in my head. And now it's just that those, you know, it's
just talking straight to the API. It's going right right in
there right to the brainstem? Yeah, it's very, it's very cool
that way, and I will also you know, I will take on that it's
hard to say but like the whole feeling of because, you know,
Dutch is different. The Dutch have different culture. You
know, like, I immediately want to wear my wooden shoes, you
know, it's like that kind of idea. I feel that I really do.
It's very interesting.
Oh, that is interesting. So you so it's, it's as much if it hits
you with a feel as much as it does with the the understanding
Absolutely. And if I if I hear someone speak it on television,
or in a movie, and it's actual Dutch because a lot of it is
really just an actor who kind of learned it phonetically it Yeah,
it's vibe. It's I immediately am transported as I said API
straight to the to the brainstem.
Hit play a cast coverage, I'm not ashamed. And I'm gonna tell
the whole world I'm not ashamed of the gospel.
Nice. I'm not ashamed of the gospel. Wait a minute, is that
Reverend Manning? I don't know who that is. That's all hell
break loose and you're gonna need a Bitcoin.
It sounds a lot like it does. It does. That's
great. I love that one.
Ralphie dropped the link to the new cast coverage in the in the
mastodon and I clicked on it and hit go. And that is the it
started right there at that exact moment.
One more time for the experience. And I'm gonna tell
the whole world I'm not ashamed
of the gospel. Glory, ashamed of the gospel.
Nice. Yeah. That's an experience.
That's I mean, talk about a product launch.
And I tweeted out a link that had been updated. And someone
said, Hey, drop me right in the middle of the podcast. I think I
like it. So yeah, that's, that's by design, man. And it's true.
Because if you're just sampling podcast, you're starting with
ads or you're starting with due to someone's opening music,
you're waiting half an hour. I think that that's, that's a user
who put something together that the user wanted, and it makes
sense for everybody. I think it's great.
I was I got an email this morning about this new podcast
from a quote unquote, podcast, which is really not one from
Audible, some kind of self help podcast, and so the First, like
literally like the first 45 seconds to a minute of it is
just the work is some do some bit a bit of background of like,
you know, non offensive background music. And then it's
like, you know, hey, this is our new podcast, where, during this
podcast, we're going to explore these ideas and this and this
and this. And here's the bubble blah, blah, blah. I mean, he was
like, 30 to 45 seconds. So just, yeah, I already know all this.
That's why I clicked on it like that. That is the quickest way
to get somebody uninterested in your show is to tell them all
about your show. Yeah, before, man before I actually do it
skips all that cast cover just like Yeah, screw that. We're
just gonna straight to the middle. Yeah, anyway, so that
that's kind of where we're at on the namespace. I think it's, I
think we'll see what happens. I like
it. I like it a lot. Now, let's see, we had put my own notes
here. Well, gosh, why don't we Why don't we thank people who
donated and then we'll move on to the next. There's a couple
more things that we should touch on today. Yeah, sure.
Let's see here.
While you're looking at Apple, just say that the entire project
podcast index.org Is, is built around the value for value
concept you get out of it, what you put into it. And we are
always looking for time, talent, treasure. So obviously, we're
putting a lot of that in ourself. But so many people have
understood this and are supporting it. It's really
fantastic. And it's it sets us up as a as a culture in the
community for what's coming, you know, true true value transfer
to everybody involved. And so just to be able to do this to
get it started not to have come out of our own pockets. Although
of course, we were always perfectly willing to. To do that
if necessary, is very, very heartwarming, and every single
person who supports it, not just with finances, but with your
time and your talent and what we're all building here is so
incredibly appreciated. It's I had I have not been this
excited. Since I first used gopher in that, I'm telling you,
that'd be
nice. Yeah, then this side is on first use Gopher,
it is truly that exciting. I mean, there are a number of very
exciting moments but it's the feeling really is coming back
and this kind of unknown and, and you're working with people
who you know from a handle or an icon or, and it's all kind of
the same goal. It's a very good energy very, very appreciative
of what will go I love I love this. I really do. And we love
the people who help us and all you have to do is to support us
is click on the donate button on podcast index.org It's also on
the developer site, and whatever you get out of it, you know just
whatever it's worth to you however you want to support it.
We do of course have our special feature where you can be named
with a recurring donation a server will be named after you
tweeted out the hilarious.
So, you know Benjamin nastic donated $500 Just like 30
minutes ago. Oh, Mike, I'm just gonna say Benjamin. The message
just says, David Adam, you're doing great work. keep on keepin
on. That's the whole message.
Thank you so much Benjamin.
I mean, like, they Benjamin gets like the whole the whole rack
you make whatever decisions you have to when you said that, like
this is such a great idea. And I'm glad you're going to manage
it. Yeah. You're gonna need a spreadsheet brother.
Yeah, I'm gonna manage this by not managing it. All right. Very
good. Just ignore it for now. Benjamin bake. Yes, yes. Okay.
And see get a subscription at $50 a month. Wow. Nice from pod
verse.
Cool. Very cool.
Yeah, that's
that's to servers. Servers.
is Mitch and the guys over there at pod verse nice and says
they don't do they have a website up yet for pod verse?
Yeah. What is their URL?
It's a pod verse.fm I think Oh, that's right. FM. Lisa, here on
verse.
I also saw that we got baked into podcast addict as a choice.
Oh, yeah. I saw that pop up. It kind of came out of the blue.
I think someone Someone did a pull request. I don't know who I
presume someone from the index
is podcast addict. Is that an open source project?
I think so. They have their own. They have their own index. I
know I know that and then Uh, in the past couple of weeks, I've
seen them say, oh, you know, we, we have our own index, but that
someone created the code or did whatever and nice. I haven't
it's now it's pod verse running on entirely on the index or is
it running off of a multiple?
Now it's working on the index? Really?
I haven't. I haven't promoted this.
Well, I'll, I'll read the note. Okay. All right. Let's see. So
pod verse, you're gonna get the, you're gonna get the master API.
Server. Thanks. Nice, nice.
The for the front end, you're gonna get one of the front end
servers. I wanted to assist. Hey, guys want to let you know
that the monthly donation is from pot verse in my team,
Korea, Korea, and I think that you named Kreon, Gary and Kyle.
Dave, thanks for the absurdly fast turnaround on the Recently
Updated podcast and point overnight by integrating this
endpoint with our own feed parsing system, we can now
expand our database from 100,000 to a million podcast at no extra
cost to us. Wow. Yeah, while simultaneously reducing our
servers CPU usage from 80% to 20%. And allowing our system to
detect podcast updates faster as a floor wax
and a dessert topping, ladies and gentlemen.
As a small open source project, savings like these are a game
changer for our ability to scale. And we couldn't do it
without y'all. It's amazing. It's amazing how much value you
in the podcast in this community have created in just over a
month. Thanks again for the incredible work you're doing
Mitch.
Oh, man, he's
so nice. Yeah, he gave me like a graph of their server stats. He
says we switched to the new endpoint two days ago and their
server their server usage went from 80% to like, a cliff.
Oh my god. That's so cool. This is a nice little project that
got here to nice little
player. It's got the clips you can make clips with.
Oh, that's right. Okay. Oh, nice. Oh, contextual menu. like
crap, man. This is nice.
If you go to the clips thing, like there's some pretty good
clips on there. It's pretty neat. I spent some time on there
yesterday.
Ha. And you can just make your own clips.
It looks like it. There's like a there's some controls down there
at the bottom like a scissor. got scissors.
Yeah. Look at this. Holy crap.
Cut it up, man.
This is good. I gotta I gotta share this right away to the
world.
One thing I don't know, Mitch in the guys is, can you when you
make a clip? Can you share that back out as its own as a
defense? Oh, I think so. I'm what I'm tweeting is pod verse
let you make clips and share them. So they better have it in
there. Because I'm just I'm just promoted. Now. All right.
All right. Thanks. Thanks, guys. Cameron rose. See, he did a $25
a month subscription. Cameron. Nice. You are going to get the
you're gonna get the images, the new images server that is not
even 100%. Oh, yeah. Okay. So Cameron sent $25 A month says,
Hi, David. Adam, thanks for taking this project on free
speech is always needed is always in native defenders. And
I think that podcasts are a critical vector for that. I
agree that providing a structure for others to build from is the
right direction rather than trying to dictate and in
product. Totally agree. Adam, as much as you seem to disdain
Scott Adams, some sort of cartoonist. I think he's very
right. And that one should always aim for that one should
always aim for systems, not goals. And this would be a good
display of just that. I'm excited to see what comes out of
it all.
Hey, I love Scott Adams. I have no, we were just joking around
on the show about him. Yeah, I'm sure I'm sure this is tongue in
cheek too.
Yeah. If the subscription is enough for a server naming it is
Please assign it to my company to be Omp tech. Alright. Say
Yeah, sure. Absolutely. We'll do that. I'd also like to support
and rewrites Adams suggestion in the last cast about the critical
importance of owning and using public domain names. I know a
lot of people look down on the expanded list of TLDs available,
but I've come around to them and it greatly expands the
opportunities for the Average Joe Joe to find something they
like. I agree with that
too. What exactly are you saying here?
The TLD like the new TLDs like I like.io.
Oh, the top level domains? Yeah. Oh, yeah. Like, yeah, sure. Did
I say I didn't like those two that make him
think he's just making a comment for I think he's just making
that comment himself.
I totally like it. They're expensive though. Some of them
really thinking you know, because of just how it works.
Doesn't it take like 100 grand out of the gate to start one of
those? A
TLD I looked into it when I didn't pursue it when I should
have, you know, that was around the time that GoDaddy guy
figured it out. And it just wasn't. It wasn't a business I
was interested in. But at the time, you could do it. You had
to have some guarantee. I don't know if 100 grand or not, but it
was not a big hurdle.
Like WordPress to get from WordPress, they started the dot
blog domain.
Yeah, that's right, Matt. Yeah. Yeah.
And I think, I think I want to say it was like, 100 grand. I
don't know. That's,
that's possible. But that's right for him. You know, man, I
would hate to have to run that business. Yeah. Oh, my God.
You're what you're dealing with all day? Yeah. Takedown request,
DMCA? FBI. That's MSLs. National Security Letters.
You bet. Oh, yeah. And you can't even talk about it. No. Kidding
bitch about it. No. Se is no agenda stream. Is no agenda
stream really so much better than no agenda dot stream? I
guess he's talking about TLDs is if there's any way you can
utilize domain names to confirm feed off authenticity, I would
recommend it. No need to reinvent the wheel red
checkmarks here because that's funny. Yes, that'd be that.
Thanks, Kathy. Thank
you so much. Let's see like this paper crumbling sound effect
you're doing? That's that's working for me. And it's a nice
transition between donations.
I'm a I'm a complete Luddite. I print everything. That's cool.
Yeah, I mean, like, I will print it. I will literally print out
an email and then walk over to the printer and grab it and read
it off off the paper. Oh, one paragraph? Oh, that's an
extreme. Sometimes. I mean, not all the time. Looking at the
screen all day just drives my eyes crazy. Yeah. It's just it
just gives me a break. Cold acid from the rare encounter podcasts
is the new subscription for $10 a month. Thank you. Thanks.
Cool. And now you're gonna get aggregator five. All right.
Thank you cold acid. Appreciate it. And Mitch. coming in again,
Mitch. Mitch is out of control. He's just throwing piles of cash
at Mitch from pod verse. I think so. Mitch. Mitch. Mitch down.
Give us 10 bucks.
Right. Nice.
They just, yeah. Yeah, Mitch is out of control.
He's making it rain. Podcast, rain, baby.
See? Okay, and I hope I'm saying this name, right. Clint. Pro PR
o IE,
what do you think? Pro Pro? Pro Pro?
Yeah. Five bucks. Nice. Thank you. Thank you. And a $5 a month
subscription. Also from Jeremy new. Thank you, Jeremy. Yeah,
these are great. I mean, long term subscriptions are extremely
appreciated. That really builds up a base over time. Thank you.
Yeah, it takes the pressure off, you know, you start starting to
spin up servers, and you start looking at the bill and you
start thinking, Well, I really need to do this, but oh my god,
that's gonna be an extra 40 bucks a month. And I love it. I
love how you think Dave Jones? You know, me? Like, I don't
know, I guess like, this is for them. Dave is this right? Like,
no, no, we need to bring that down. Do a different also,
before you continue, I just wanted to say that I'm so happy
that so many people get to see and work with you. Cuz, you
know, we've been doing stuff for 10 years. And I've seen people
go holy crap, you know, I breathed something. And Dave's
got it implemented or has an idea. This is Dave Jones. So I
just want to make that very clear that you know, the dragon
slayer for sure. Because I've thrown I mean, I will talk to
you the way I spoke on the international podcast day with
an idea. And you'll go okay, and you'll usually turn it around
and you'll ask me two questions. And then it's like, oh, test
this. Yeah. So it's a joy to see you're working with all these
other people as well. And I hope they, they appreciate the how
this is all flowing through you.
Yeah, it's been great. It's been it's been a lot of fun. Tina
wants to make sure you're having
fun because Dave must be having fun. Besides, he better be if
he's not then we're in trouble.
Yeah, true. No, no, it's it's great. Yeah, it's been it's been
a it's been a blast because it's
all consuming. I mean, I'm also sitting on the couch, you know,
like, chatting with you or checking the, the mastodon
server or anything, you know, it's like
it gets in your brain
does it does and does.
Well, that's it for donations, I think. Okay,
well, it's very good. This'll definitely keep us power. for a
bit longer, incredibly appreciated, again, value for
value can't say it enough your time, your talent, your
treasure, some people seem to be contributing all three, whatever
you put into, it usually flows out. And that is what we've
learned over the course of many years of the applying the value
for value model. So let's talk about the image server for a
moment, because that we've kind of went through a lot of what it
already does in the namespace. But longer term, it appears to
me that this can be a good resource for a lot of things. A
lot of people seem to need these images. And I'm really happy to
set that up. You set that one up pretty quick, too.
Yeah, this this week was dedicated to me throwing Andy
from the mastodon under the bus, because he's been waiting for me
to refactor the recent episodes in point for like, two weeks,
and I keep saying, Yeah, I'll get that for you. And it's and
then go off and create an image server, right, where I go off
and do a namespace, right? Okay. Um, I've, I've got to get I've
kind of felt some pressure to get back to getting some stuff,
some of these endpoints reengineered. So I'm really
going to try to buckle down and start start focusing on that for
a while. Okay. And because I mean, we don't want to neglect
the core of, of what we're doing here.
Now is the endpoints obviously, do I need to cock block anybody?
So they don't disturb you
know? Yeah. Now I can close my browser.
Oh, okay. Good.
Play. See what you know. We lost Conan O'Brien.
He went off word who did he sign with?
I think it's Amazon.
No fraud. Audible probably. I think I did see a blurb about
that.
Yeah, play. I think that's a good PLAY CLIP three Conan Eisah
Oh, clip three. There's too much comedy. And I think that's why I
started this podcast is to try and stop it here we got to pay
homage to the guys that disappear. But the so the image
server is probably going to be
going on we're not doing it right. Changed. We're not doing
it right. I'll show you how we do it.
Everybody and I think that's why I started this podcast is to try
and stop. tabs as they go on their way out. I forgot what all
right party is was clipped to you.
All right party.
It was a very alright party. Let's throw it.
Oh, he's probably he's probably joking around about the SCOTUS
party in the Rose Garden.
I think that was from his interview with Sarah Silverman.
Okay, yeah, explains that. Yes, the image server will probably
just going to I'm probably going to end up reengineering that
because I don't the ideas sound. But I think the way that it
needs to be filled in right now. It's basically just running.
There's running three image converters in parallel,
each for each one for a different size.
No, it's they're just, they're just taking different sections
of the index. And grabbing them and sticking them in five
different sizes. And his work in the problem is going to be and I
can see it already, which is just a big way. Well, yeah.
Mike, Mike was talking about dupes. There's that and there's
also just you're in you're going to end up doing a lot wasting a
lot of space for podcasts that never get touched. And so I
think a better way to do this is going to be to to respond to
have it monitoring and respond when calls are made that return
podcasts. And then do it on the fly. So basically, just
the first request is is the toughest.
Yeah, no, the first real quick here's, here's my idea. So
Martin had came up with this idea to use an initially very
small size image and blur it. And that seems to
that was the intro very interesting the way that worked.
Yeah, like as a as an effect. I mean, you're masquerading a
problem with conductivity and software, but it worked. I mean,
the the illusion is beautiful. Oh, that is actually kind of
almost like it was a feature.
And in this file size of that thing is tiny. It's, it's 987
bytes, right? So my thought is, what we could do is we could, we
could resize on the fly to the 20 by 20, when somebody
initially when somebody initially asks for it. And
excuse me, let me back that up, we can go ahead and pull down to
20 by 20s. And serve that immediately. And then when
somebody asks for the full, and then when they asked for it, we
go ahead and pull the other images and convert them in the
background. So that there's like a one second delay, right?
Before we deliver the full the other resolution.
So okay, I get it.
What we may find out is we may find out that there's out of a
million and a half feets there's only you know, 400,000 that ever
get requested for images. And
although I, I do hope in the future that people consider
changing their art per episode. I think it's really worth it.
Yeah, it makes everything so much colorful. It makes the
world prettier. The apps better. I don't know. It's attractive.
It's exciting.
I'm always excited when I look do a search. And then one comes
back and all the episodes are different. Yeah, so yes, you
happy?
And you look. Oh, wow, that might be a good episode. Yeah,
that's probably the Ardo. I know, it's, it's hard. It's
hard. But you know, we're lucky. No agenda. We have people who
want we get like 20 submissions a show before the show's even
over.
Yeah, for most people, that would be really difficult.
Right? Yeah, no
kidding. But we also deliver the show 30 minutes after the
stream?
Yeah. That's still incredible. Fast. Yeah. So that's the image
thing. So basically, what I'm saying is, all this, all the
stuff that has happened to this point, I may just throw that
stuff away, like, you know,
shortly and but the way you access, it won't change, right?
No one has to change code necessarily. Right? Yeah.
Well, if we do it this other way, what I think is we will put
in an extra property in the endpoint that returns the URL of
that 20 of that small 20 by 20. Image. And when the endpoint and
when that happens, it will trigger the full resolution
download and conversion on the image on the object. So nice. So
that would be a good way to like, be more efficient with
this whole thing. Yeah, I think that's the new because because
this thing's gonna take like 300 gigs
of disk, it's gonna be it's gonna be pretty hefty.
Yeah. And we may only need half that if we do it this other way.
And then we could check for duplicates, and only serve, only
serve the one the one version of that if we needed to out on the
back end. We can do. Like we, we can just do like a soft link or
something in on the Linux file system. Okay. Cool. We're good.
We got other stuff to talk about. We're going kind of long.
You want to? You want to wrap it up? Are you guys anything else
you want to?
Well, besides the you're intending to work on endpoints,
we'll get the namespace name change. We'll get that up. I
guess I'll do work on promoting that and see if we get some
people to come in and work on it. And what else do you need to
say anything I can get for you? A beer. What happened to hookers
and blow man rent boys Sheraton? A none of that
he's way, way too much. Way too much baggage.
Here. So I will just say and here's your T's. The Dave and I
have been also been we've been working pretty hard on the
second mission, which is retooling podcasting to a
platform of value. It's just way too early to talk about it. But
we found interesting people that have some ideas and we're we're
looking at some some initial tests. But I am quite excited.
Yeah, me too. It's gonna be that that's when things are gonna get
real fun.
Yeah. Yeah, I think you're right. So all all will be
revealed.
Good do a cast coverage. Paul, shoot you
can't wait for this one. Another random shot from cast
coverage.com
and coming in here and putting us all in jail. You have a mask
or no mask we're going. Okay? Or he might not put you in he just
shoot you. Um, well, he probably would shoot you back. There we
go.
I like that mask or no mask we go on beautiful, beautiful.
Yeah, but we didn't even talk about the web. So all that
stuff's working now. Well, let's talk about that next week. That
was like, multiple days of stuff to get that
work. But do you want to just just briefly talk about it? I
mean, it's, it's an important piece.
Yeah, well, I'll just let's talk about next week. Okay. So my
next week will the basically it's working. And I've got some
good stats, too, that we can talk about next week. I'll dig
in a little bit. Excellent. Excellent.
Well, Dave, it's as always, man, it's a it's a real joy working
with you on this project. It's really, really fun. It is fun.
And I'm all I'm all God with it. That's what's going on here.
Alright, everybody, that'll do it for podcasting. 2.0 for
today. We'll be back next week with another episode. Well, I'm
sure we'll have lots of stuff to talk about. Dave. See you then
man.