Episode 247: Aggy5

Podcasting 2.0 for January 9th, 2026, episode 247, Aggie 5. Hello, podcasters. Hello, developers. Hello, hosting companies. Hello, industry parties. Hello, people who just stumbled upon this. This is your official board meeting of Podcasting 2.0. It's where we discuss the future of podcasting, not just discuss it. We appear to be making it from time to time. I'm Adam Curry, coming to you from the heart of the Texas Hill Country.

Wait, I forgot to say, we are the only boardroom that does not need to have Greenland. That's what I wanted to say. I'm Adam Curry, here in the heart of the Texas Hill Country, and in Alabama, the man who deserves more praise than he ever receives. Say hello to my friend on the other end, the one, the only, Mr. Dave Jones. I want Iceland, not Greenland. You know, there's no ice in Iceland, and there's no green in Greenland. It's a very strange, strange thing that they've set up there.

The Fall of Civilizations podcast on the Viking, what do you recall, the Viking era, where they landed on Greenland and discovered and landed on Greenland, is highly... Recommended? Recommended, yes. It's five stars. What is their takeaway? Well, you know, it's about civilizations that were, like, super strong, dominant in at least some portion of the world, and then just kind of vanished. And so their bottom line is they're gone. You mean all the people who lived in Greenland are gone?

The Vikings. Yeah, well, they killed each other. They ate each other, I think, didn't they? Well, this is a great podcast. This Fall of Civilizations podcast is fantastic. Although my one complaint, and it's not really... I mean, you can't really call it a complaint. I mean, but my one annoyance with it is they sort of wrap it all up, bottom line, why did this civilization fall? It's pretty much like you kind of hit a button and it's the same thing every time. It's always climate change.

No. That's funny. Which is legitimate in this context. To a degree, yeah. When it gets really cold and people freeze to death, that's... Yeah, when you have something called the Little Ice Age, it's probably going to shake some stuff up a little bit. Yeah, of course. The changing climate of the world in general, not because we're smoking our pipe down here and heating up the atmosphere. Smoking our pipe, yeah. But it really does, and that's the interesting part of it.

It's like all these civilizations fall, most of the time, by means beyond their control. Things just happen. It's almost like somebody else is going to control. Really now? Almost. It's almost like that. I mean, what are the chances someone else is in control? Let me think about this. It's far-fetched. It's far-fetched. I mean, if only there were a book I could read something about. A scroll. If only there were some scrolls. How are you feeling, brother?

This has been a tough couple of days for you, is my feeling. Day jobs have been rough, yeah. Well, day job, and then you had Aggie Five shit the bed. Pardon my French. Aggie Five. Wasn't that Aggie Five? It sounds like a mascot for a football team. It is. At the University of Georgia, their mascot is Ugga, U-G-A. And every so often, Ugga will die, and they'll have another one. Ugga Three, Ugga Four. Yeah, that's like Bevo at the Longhorns. Which Bevo is this? We don't talk about that.

It's just Bevo. It's just Bevo. Steer lasts forever, though. Those guys live forever. They hang around. They do hang around. It's all good. Yeah, that's what you say. I had to upgrade Aggie Five to a two gigabyte instance. I'll tell you, when you're, you know, because we did Curry and the Keeper, which we hadn't done for several months for a number of reasons, which was really nice to get my wife back on the mic. And then I'm hosting that through Fountain Hosting.

We transitioned to test and see how it all worked, which works great. And I love their dashboard and everything. It's fantastic. But then when you see it not come through on the index, all of a sudden, I'm like, I'm starting to sweat. I'm like, what's happening? And then Nick the Rat, he sent in a note to us. He had an issue. It doesn't matter if it's user error or not, but what happens is there's this entity that we all kind of take for granted called the podcast index.

And we know how many different apps rely on it, apps and services. I think we're up to like 70 or something. There's all kinds of people tapping into the index. And then, you know, at that moment, you just feel like, oh man, the vulnerability. And I actually wanted to talk about that. But first let us celebrate another win. I think this is huge. That iHeart, the iHeart Radio app, according to sources, that would be Pod News, they will be supporting video in RSS as an alternate enclosure.

Congratulations on this to Alex Gates, because he wrote the entire spec for the alternate enclosure. And it's a really tight, really good spec. And this is another one of those examples of you just got to give it time. You got to give it time to reach maturity. You know, you write something and you throw it out there and you can't control how long the process is going to take. Well, also, you know, we have true fans supporting this since 1832.

Yes. Well, but this is kind of a bigger point I wanted to drive towards at the beginning of this board meeting. So if everyone could settle down and stop eating the donuts and pay attention. So we're in our sixth year, I believe, of doing the show. Six years since we built, you built the index. And this group, which is just a beautiful group, because it's all kinds of people from all walks of life, all participating.

Everybody is contributing something, whether it's just maybe it's just the comment on the Mastodon, or whatever it is. There's all these different ways that people contribute. This show contributes. There's implementations that contribute. There's hosting providers. There's developers, just interested parties. It is a truly a beautiful movement that is just hanging together.

But it really, all of the work, I would say, centers around podcast index for implementation, for making things work, for experimentation, for the namespace, for the documentation of the namespace. And we could list all of the names of people who have worked on this. But believe me, in 20 years from now, Adam Carolla invented it all. You should give up on ever thinking you're going to get credit for anything. That's just not how it works. But it's also not that important.

But what is important, you and I have been walking together for a long time, brother. What are we now, 15, 16 years? A long time. And we've been doing all kinds of crazy stuff. And this one, by far the craziest. Oh, yeah. By a factor of a hundred. And by far the most labor intensive. And my part in this is not the same as yours, but you're my brother, you're my friend, you're my compadre. We do stuff together. And I kind of want to pull on the brake for a second.

Because when this fail happened, the Aggie Five fail, you and I had a very short exchange. And you were like, well, you know, I had to upgrade Aggie Five. And I'm like, hey man, is this a money issue? You said, no, it's more of a technical issue. It's a time issue. I just can't get the time to focus on it. Am I characterizing this correctly? Yeah, mostly. I think so. So, I mean, of all the things that we are given by God, time is the one that you really own for yourself.

And you only have so much of it in the day and in your life. Yeah. And I'm thinking it's time to get real about this. I mean, just look at the successes of 2025 with Apple's adoption of multiple tags, including chapters, transcripts, which has been started to become kind of an industry-wide acceptance. I think the iHeartRadio app claiming that they will, because it comes from Triton Digital, I

think. And so they're on board. But it all really centers around the work that you mainly coordinate and for the most part do. So you can say, yeah, that's true, because it is. I'll say it for you. So right now we're at a spot where, again, it doesn't matter who does what, what we create, what we build.

The beneficiary is the free word that can spread throughout podcasting without being owned by any platform, which is really the reason we started this in the first place, is because everybody was dependent upon Apple. Not knocking them, but when they decided to remove podcasts, it's like, oh, okay, no. There was no movement, zero, for over, I'm just going to remind people, for over a decade, no technical movement.

And it was continuously, well, you know, if Apple doesn't do it, buy some, blah, blah, blah. And so once we had a bunch of apps out there that were actually implementing the namespace, things started to move. Hosting companies started to move. Something shifted and things started to move forward. And so now it is going to benefit the universe at large.

And we know that iHeartRadio, they don't, as far as I know, they don't pull the index, but that development came from this whole ecosystem that we started and from the index that you maintain. So it's time to get serious about that. And I have some thoughts, because the number one thing, which I've said to you for months, maybe years, is it would be great if you could focus on this primarily and not have your day job.

And so before I even go any further, if you could do this full-time or four days a week or whatever it would take you to really help manage the development process, because you're very good at that. You are the pod sage. You help shape the specs. You help, you know, you're unshakable. You are seen as a man of wisdom. You're kind of like Isaiah, really, like Solomon. Stop it, stop, stop, stop, stop. No, but everyone will agree with me. I'm the lightning rod, you know, it's like, okay.

But this, we cannot keep going forward this way. So my question, and I've asked this in private many times, I think I know the answer, but if you could, quote, unquote, quit your day job and focus on this, would that be desirable for you? I mean, yeah, it's, well, you know, yeah, there's lots of things that go into that, you know, and I've had opportunities for that to happen. And it's a complicated question because, I mean, it's a complicated question on a lot of levels.

I mean, you know, there's, you know, the place I've been at in my day job, I've been there for almost 30 years, you know, I've been there a very, very long time. And so I have a lot of deep connections there that are important to me. So it's more than, you know, it's more than just a, you know. Yeah, it becomes a family in a way. Yeah, it's complex.

But also there's part of me that also is a little hesitant to try to do something like that because, I don't know, for a couple of reasons that are hard to describe, this may be, this may be an interesting discussion beyond just this, but just podcasting 2.0, because I think a lot of people get into this. It's a very common thing for people to think they're doing, they're doing one or two things on the side.

And then they wonder, maybe they get an opportunity to go do that thing full time, or they think about doing it full time. And then the questions begin of, should I do it? How's that going to look? All these kinds of things. So maybe it's an interesting discussion from that standpoint. And because I feel, this is, speaking as somebody, I've always had or done side gigs. And 90% of the time the side gigs do not pay a dime.

But, you know, I don't think I've ever had one that's, to my knowledge, I don't think I've ever gotten paid for any side gig. And those side gigs have ranged from podcasting 2.0 to the software that me and you developed on the side, to being in open source, going way back to in 99, 2000, open source projects, contributions. Before that, I was a part-time youth minister at a church here. In town. And so like, I've never actually gotten paid. I don't think for any of that stuff. I know I haven't.

And what's interesting to me, and I've thought about this a lot, is there's this, if you're not in the church world, if you're not in a sort of a Christian circle, there's this term that's thrown around in the Christian world, or in the church world called bivocational. You can be a bivocational minister. And so, you know, that's simply just shorthand way of saying, you have to have a day job because your ministry that you're doing can't pay you enough to support you and your family.

And that's a lot. I mean, most of church ministry is that. There's a very small percentage that's actually full -time job supporting. I'd say probably, you know, if we're using made-up numbers here, probably 80% of ministry in the world is done bivocationally. It's people doing it on the side for little or no pay. And this goes back to, you know, again, in a Christian context or a Jewish context, this goes back to Paul. You know, Paul was a tent maker. And Matthew was a tax collector.

John was, you know, was a fisherman. The bivocational nature of ministry is something I grew up with. And I kind of always thought was really important because I feel like it keeps you connected to the people that you are ministering to. I feel like there's a real, it's really, sometimes it's very hard. If you're going through a tough time in your life, it's very hard to hear advice from someone who is a full-time preacher, pastor, minister.

There's certain times that that's hard to listen to because you're like, you know what, you know, you can, you're supported. I've I'm having to do, I'm having to work three jobs. You've got what looks like from the outside of Cush job in the, in the church, these kinds of things. I've always felt like sort of community supported things were had, had a character building quality and an ability to connect you to other people in a real way that you lose once you get paid for doing that thing.

And I think it also applies somewhat here with open source software and open standards development and that kind of thing. It's really, it's really difficult to be, I don't know, you lose something once you make that step.

So, you know, if, if something, you know, somebody let's, let's just say that let's say that Apple came in and said, Hey, podcasting 2.0, we're going to create a fund, a tech leader led fund with YouTube, Apple, Spotify, all these, all these people, all these organizations and we're going to do an, like a development fund for new features, almost like an incubator and we're going to seed it with, you know, a million dollars and we're going to create an organization around it.

And then, but that's going to fund podcasting 2.0 development and the index and, and all this kind of stuff. It's one part of you would jump and say, that's amazing. I can't, you know, sign me up. And the other part has a little bit of trouble sleeping at night because you're like, well, you know, there, there's something about the gorilla nature of doing these things on the side where you truly do not care what succeeds or fails. Uh, you, you care about the trying, not the success.

Okay. And, you know, and, and I feel like that could, you know, it's, it's very possible. I feel like this, it's more than possible. It's probable that the fire that happens under you when you're just doing something purely for the creation aspect. I feel like without that, everything doesn't work. Okay. So believe me when I say that if Apple did that, I would be the first in line saying, no, go away. You know, the same way Google basically ruined Firefox.

You know, if you have some sugar daddy who's funding it, that I would never propose that. For the past 18 years, I have lived with my church, which is the church of Gitmo Nation, which is very similar to the bivocational nature of what you're about, about church in general. In fact, when we studied the value for value model, we looked at churches, like how do churches do it? What, what exactly do they do?

And it turns out that we were using terms that I didn't even know were used in the biblical realm, such as time, talent, treasure. I had no idea that just, it's like someone might be controlling something. But the, the fun of creating these shows that we do twice a week has not diminished because it is value for value. If we had decided to go with advertising, forget all the issues of advertising, that probably wouldn't have worked anyway for us.

I think it would have been, you know, we might not have made it this long. It probably wouldn't have been as fun. But to know that it's valued by people according to their means, and what they truly feel is value has kept me, I can't speak for, well, I think Dvorak may be like, hey, we got enough money, it's good. Can always be more. I think has been a big part of what has always driven me because it just feels good.

And what I was going to say is that if you look at the landscape of what has been built here and the people who are involved, in fact, if you look at the Podcast Standards Project, there are 14 hosting companies who are a member of the Podcast Standards Project. And we've been, I feel, you know, we said from the outset, we said this will be value for value.

But I think I've privately always kind of said to you, man, it would be my wish and my prayer that you could do this full time and wouldn't have to be dividing your time. Now you throw me a bit of a curve ball with the bivocational angle on it. But what I was going to say was, I believe it to be quite trivial to get $10,000 a month into this project, value for value, from the people who care about it and different means if we really put it on the line.

That's kind of the scary part of value for value is you're putting it on the line. If it doesn't work and people don't like it, which arguably the proof is already there over five years of this, then it just doesn't work. Then it's all right, then go do something else.

But I was going to say that if we truly took value for value seriously, right now today with the Bitcoin that we have on the node and our reserves, you could leave your job and work for a year and make the same money, I'm just estimating, but I think it's kind of the same, without losing any income, but being able to dedicate your heart and your soul to the project or whatever projects you want, but they all kind of fold into one.

And so not looking for an answer, but my suggestion was going to be that if that's all we need to not kill Dave, because I'm saying that kind of funny, but not really, because I've known you for a long time and I know, and you have a lot of responsibility in the day job.

And believe me, the hardest part of any scenario that we would look at would be decoupling, you're decoupling from your day job family and they would probably put up a fight and they would probably grab onto your ankles and I have to go out there with my guns and stuff. But I would put up the first thousand dollars a month just to kickstart this and get it going.

And again, not looking for an answer, but I feel that if I look at what has been accomplished, that you have been the nucleus of, what it would mean for podcasting, call it open podcasting, whatever you want. I think it would be a huge benefit to moving things forward for everything and everybody. Does that make sense what I'm saying? I understand the sentiment. And I'm not trying to downplay the seriousness by calling it sentiment. That's not what I'm doing.

I understand, but the sentiment aspect of what you're saying, I do understand it. I just think that when I told you, I think it's not, I think my exact words were, it's not a money problem, it's an engineering problem. There's an aspect of when you build, the problem is this thing isn't built right. Well, hold on before we go there. Okay. Yes, you said not an engineering issue, but need to re-engineer the aggregator stack, but can't get the hours needed to do it.

Yes. That's the part that I'm responding to. And I think the reason I'm so hesitant about a money thing is because- Well, you can do it for free. That's fine with me. The reason I'm so hesitant- Hold up before you say that. I believe in value for value, Dave. I live by value for value. You are not- Yes, of course, there's value you get back from satisfaction for having done something. But the amount of value you're providing is just not coming back to you.

And I've seen the value for value model work, and we haven't really taken it seriously. I mean, yes, we've said, well, you know, keep the engines running. But, and maybe this conversation is only just for everybody to step the fuck back for a second and understand, pardon me, and understand what it is that you've been doing. Because sometimes it just gets to a cavalier nature. You know, I just feel it. I'm like, do any of you really understand what has been done here and what Dave is doing?

And when I say don't kill Dave, I mean, I really mean that. So I'm trying to- I'm a natural problem solver, you know, that, by the way, do not recommend doing that with your wife, any wife. Do not do that. But at a certain point, I just need to say, hold on a second, I'm seeing something here. And I want to offer solutions, ones that I can actually contribute to, because I know that we could make that work. I know how to do it. It's not a lot of money.

Now, there's many ways to get money, but I think any other way than value for value would put the whole project in peril. So I'm just putting this out there as an offer for you to consider. And then you can just- we can go back and tabletop it, game it out. But I would like you to consider it beyond today's board meeting. Yeah, of course I will. Yeah, I take everything you say to heart. And I do spend time thinking about it.

And the issue, I really was not mentally prepared to have this conversation today. Well, no, of course not. This one's taken me by surprise, you know. But it's not a bad surprise. I mean, it's always good to talk about stuff that are not in the notes. And so, I mean, I think the interest - you know, the money- I mean, I love money. Everybody does. Everybody can find a great way to use money. And I'm no exception to that. I'm just- Wait, I got a clip for you. I got a brand new money.

I don't want any money around me that's not- I'd almost rather have a new one than an old 20. That's kind of dumb, isn't it? But there's something about new money that excites you. You like $100 bills? I like new money, too. The most beautiful thing on earth is a $100 bill. I haven't seen a woman as good looking as a $100 bill. There's something about a $100 bill that excites you. Is that a preacher? Yes, of course. Of course it is. It's a MoFax clip. Okay, that's awesome.

Of course it's a preacher. Yeah, it's- the money aspect of it is- it's really, I just don't think that important. Well, then let's put that to the side. As we go through this conversation, put the money aspect to the side, because I guarantee you whatever you need will be provided. I know how to do that. I know how to get it. I know where to get it from. I know how to make people send it. I do, I do. I know how to make people send it. Yes, it's a funny thing to say. Well, because people want to.

People want to. They want to have a reason to support things. We've been doing the show, and we just thank people for supporting us, but it's not really- I mean, there's a million things that go into a true, full, rounded value -for-value model. So I just want to say, that part I can handle. That part I know we can make that work. But you're saying something different, which is interesting. Yeah. And I want to make this thing work. You know, the problem is not money.

And it's not really- it's a little bit- time is- the reason the time argument doesn't really sit to me is that time is the universal problem. I mean, you know, the thing is, I don't know that more time would solve it either. Because time is sort of like everywhere you live, you always think, I don't have enough storage space. And it's not because you don't have enough storage space. It's because you have too much stuff. And so the time thing is like, you always think, I never have enough time.

But somehow, time is a resource that you can go get when it's important enough to you to do so. And I don't know exactly how to explain the way that works, but that is the life that I have been living for the last, you know, nearly six years, is that when I need the time to fix a thing, somehow it appears. And I know that that is the case here. And I also know that it's an engineering issue.

If this thing is built right, if we are able to fix this, fix the aggregator issues in an open way, then I think I'll just feel better about what the end result is, because everyone will have ownership in it. And not just me. No, but I'm not saying you change anything in the process or look, man, it's a beautiful thing to not have to go to work at 8.30 in the morning to deal with someone's caps lock, because the password won't work. I'm not saying that's your whole life.

Or the generator went down, I've got to go be there for 48 hours and feed it with fuel. Now I get up at 6.30 by myself, I don't have to, because I'm excited to see what the world brings me when it pops up. And where can I turn left or turn right? It's not so much that I have more time to work on my day job, it's I have the freedom to dream about my day job. I think one day Godcaster will be that. And if I have to put a hope on something, it's that Godcaster would turn into that thing eventually.

Oh, good. Everybody can send Godcaster money. That would be good. I don't, the purity of the podcasting 2 .0 project just doesn't feel that way to me. Okay. Like I said, I've had an opportunity to make a change, you know, at some point. I talked you out of it partially. Partially. But I had an opportunity and my vision going into that opportunity was that that was going to be the whole job. I didn't want to, it to be a podcasting 2.0 support mechanism.

And I think that's, I just think that that's important. I feel like podcasting 2.0 is so rare to have a purely, to have a pure play open source project where everybody can contribute and there is no corporate ownership of, in any capacity, there is no like, and I've said this before, if all the money went away, Yeah, we'd still pay for it ourselves. I'd still run it myself. Yeah, I would run this, I will run this thing for the rest of my life.

And when you already are committed to something in that way, like the timeframes get longer because you're having aggregator problems. And when you're getting, you know, when you're getting a constant stream of support money coming in, you feel a lot of pressure to stop what you're doing and fix all the, everything becomes really important.

But when you have a truly open source project where you're getting money and it's meeting your needs, you know, for the hosting and that kind of thing, it's paying the bills, but you're not, you know, you're not living off of it. Well, then your timeframes get longer. You're like, well, I do, I've got, I've got this problem with, with aggregators going, you know, it needs to be re-engineered. Well, it'll, it'll get there. It'll, it'll, it'll fix itself over time.

We'll, you know, we'll all contribute and we'll build something new and, and then we'll have, you know, and then we'll have a great thing to look back on and show and see how we did it. And, and I'm also, I'm also a little leery of on that same note, money tends to be an accelerant. It accelerates things that don't need to be accelerated. Well, I'm just, I'm just going to disagree on that because living on value for value, it's not like that at all. I mean, it isn't.

I think your situation is different. I do. I think your situation is, is truly different.

You, the, what I'm, I think that you're right when you say that, but what I'm saying is when you, when the, when the issue is a technical one, when it's a, how do I construct, how do I engineer this, a solution to this problem, to a particular problem, like on a programming level or something like that, or like an open source hardware project, when the problem is an, is a sort of technical engineering issue, I think this is a problem with startup culture.

Startup culture gets a humongous cash infusion up front, and you tend to accelerate your solutions to problems that should take longer because time can cut in both directions. Yeah, yeah. No, I'm, I'm, I'm with you on that. I'm, I don't want to get too hung up on the money because believe me, it's, it's, it's not, it's not easy because it's a roller coaster. You know, it's, it's up and down, it's up and down, like, okay, well, you know, we got to tell people that it's necessary to support us.

So it's not, it's not like all of a sudden you're swimming in cash, you can solve everything with cash. It's, it's quite, it's quite different from that. But I, I, I hear what you're saying. So, but I was responding purely to one comment that I'd not heard you say before. When you threw time at me, that's when my brain went, okay, time. So anyway, the support of the, of the index of the entire project is based on time and talent and treasure. Notice treasure is the last one.

So the contributions that everybody put in are of equal weight, of equal importance. I was merely giving a, an opportunity for you to consider because I'm just going to tell you, we could make it work. So if at any point you say, you know, I really want to work on this more or whatever, then we can make that work. I just want to put that out there as a forever dangling carrot. Let me get spiritual for you for once, just brief, very briefly.

And, and, and those, those who are going to roll your eyes, you can go ahead and roll them now and get them out of your, get it out of your way.

I, I just feel like based on what has happened on all the different factors that have popped up over the last, you know, five, five and a half years, I feel like God is doing, God is doing something important in the, in the, in all of our lives, you, me, everybody involved in, in, in podcasting 2.0. I feel like there's an important spiritual aspect of the spiritual manifestation that is happening.

And I don't know what it is exactly, but I do know that time is a factor and I'm afraid of tampering with that because I feel like spiritual truths a lot of times need time to manifest themselves in our minds that you can't short circuit. And I'm afraid of messing with what that formula is. That may sound strange, but that's, that's kind of, that's, that's part of this too. No, I, I, I can, no, I completely understand that at this point, if anyone wants to come forward, this is an altar call.

We'll have our prayer team up front. Then we'd be happy to pray with you. Pray with brother Dave. Brother Joe over there. He's on one side of the altar. Well, so first of all, I couldn't resist. Again, feel free to eye roll that, but I'm just telling you how I really feel. No, I'm with you. Look, I, I, I got saved during this project, you know? So yes, absolutely. I'm 100% on board. So that's enough reason for me to, to be satisfied that we had this conversation.

And if, if the spirit needs us to have it again, we'll, we'll know. I feel that way. I feel that way as well. Whenever, when the, when the, when the signals come down, I'm ready to see them. Okay. All right. Amen and amen. And amen. All right, brother Dave, back to the, the topic of the day. Whatever you came prepared to talk about. The Computer Chronicles. Did you get my clips? I did. Yes. Computer Chronicles. Do you remember, do you remember this TV show?

Well, of course I, in fact, I think there's a fantastic episode with Dvorak. Yes. Where he's trying to show how easy it is to take apart this PC and snap it back together. And it does anything but easily snap apart and back together. And it's a hilarious classic video. And, and the, it shows his talent with vamping because he is just vamping like it's a clinic. And he has those, and he has those Buggles glasses on, you know, like from video killed the radio star. Yeah, it's fantastic. It's good.

For some reason, this started coming up on my YouTube feed. And so I started watching these old Computer Chronicles episodes. And this one, from that show about the window, this is Windows NT 3. So it's very. Oh, well, I worked with Windows NT. This was in, this was in my day. 93, I think is when this was. Yes. Yes. And I left MTV in 93, I believe, and started my first company, OnRamp. And yeah, we, this was, we were using NT.

And of course, a couple of years later, Windows 95 came with, because when I think they didn't have Windows 3.1 at this point as well with NT. Yeah. OK. That's right. Windows 3.11 was the most stable, awesome version. Right. But we were, we were all using NT because it had a POSIX kernel. Yeah. And it could run on MIPS. Yeah. MIPS. Yes. Oh, NEC had MIPS machines. In fact, I think I did a booth one time for NEC at CES or Comdex. And NEC was, no, I'm thinking of NCR.

That was National Cash Register. No, NEC had the MIPS machines. They had some of the early MIPS machines. The, yeah, that was, yeah, that was the thing. The Windows NT kernel was, was, was portable. It could run on, you know, Spark and yeah. And they built that for the government. They built it for the government, I think, if I recall. But it was some government requirement that it had to be able to run on these other type of processors.

And eventually the, eventually Windows NT, so you had two separate kernels. You had the 95, 98 kernel and the NT kernel. And eventually these two things merged in, in the Windows 2000 product. Which was a dog. I hated Windows 2000. Well, it's not as bad as Windows Me. Hey, but wait a minute. Wasn't NT, was it, was it NT? I remember doing this. If you had someone's IP address, you could send them a ping flood and it would blue screen it within like a nanosecond.

Oh, yeah, there was, there was so many versions of blue screen in somebody's computer. It was cool. It was so cool. I remember my buddy, he was running. Oh, it was SGI. He was running graphics, SGI graphics. Oh, OK. But somehow. Silicon graphics. Yeah. But then he had, he had a Windows NT machine. He was in Holland. I'm like, and I said, hey, send me, send me a, you know, click on this link. So I had, so I had his IP address. He said, no, watch this. Three, two, one, boom.

He said, what just happened? You're a turd. He was not happy. Yeah. But when does, yeah, when does I didn't, I'm, I was a little behind you on that because Windows NT, my first experience with NT was NT4. OK. So NT3, I missed NT3. But they, so, but this, this clip is. So the Windows NT at the time was codenamed Cairo. Oh, I remember Cairo. Sure. Sure. The road, the road to Cairo. That was the marketing. The road to Cairo. And he's going to talk about Cairo.

But the, and just this is just interesting to me. But listen to what he says. And I'll have a comment. Program managers say Cairo will bring a new level of intuitive ability to NT. Cairo will make it easier for people to say, just give me the the sales data for the month of December and the system will take care of finding the data. Yeah. Also enable people to build solutions where where they can work with the data in exactly the way they want to.

They don't have to worry about what application they're running in. They don't have to worry about the exact structure of the data. Things will just flow more smoothly in the way that people want it. Basically the same promise they're making with AI today. Yes, exactly. The exact same promise. This is the Silicon Valley lie machine that just never stops. It just is over and over. Every time there's some new cycle, it's going to be you don't have to worry about where your data is.

You're just going to be able to say, give me the December financials and it's just going to do it. It's going to be magic. And they've been crapping this out since the early 90s. Such garbage. That's the that's the enterprise version. And then the consumer version is your fridge. You will know when you're running out of milk, it will automatically order it for you, which I still to this day have not seen. Yeah. And now we were seeing that at CES in the 80s. You know, is yeah.

So anyway, just an interesting side note. I will I will say that I've been using thank you for the link to Gemini CLI. Yeah. I mean, Gemini has been quite impressive, actually. It has a huge context window. But I forget. I wonder how they do that. Well, I mean, this this I think is the holy grail is the is the context window. But now someone's got to pay for it somewhere. And it's been rather impressive. In fact, I've I did a whole analysis for my use case for Omarchi. Omarchi.

Are you switching to that? I'm considering it. Yeah. OK. Yeah. Because my whole studio still runs on Windows for two reasons. One is the roadcaster and the second one is my play out system. But I mean, there's many ways to build the type of play out system I have. And I'm not I'm not too concerned. That's actually kind of the easy part, really. You get vibe coded. Very easily. I had vibe coded some stuff the other day, like literally like five minutes.

But I needed a music deployment system for all these individual Godcaster stations. So easy. I mean, I knew I wanted to use our sync. That was the way to go. And, you know, just boom, boom, boom. Put it together for me. Beautiful. You're a machine. But I would love to because what Omarchi does. And it was Paul, Godcaster Paul, who built the Godcaster. I was building the Godcaster app. It's a never ending process. He turned me on to it.

He said a lot of devs are moving towards and I can understand why. Because, you know, I love keyboard commands. I love shortcuts. I use them all the time. And to be able to control the UI with your with your shortcuts and just make it really fast and like things pop up and disappear and split and organize and wow, you know, no, there's no menu bar really to speak or you don't need to have a menu bar. And man, I could see it.

I can rebuild my whole workflow command line, actually, just for the show, for shows, just based upon how I saw that thing working. And I'm I'm a mouseaholic. You know, I got a mouse around a hundred miles a week with the with the stuff I'm doing. Like if I could just keep my hands on the keyboard. Wow, that would be fantastic. Tiling window managers are great. I remember Fluxbox. Fluxbox. Well, it's based off a window manager called Blackbox.

But then it was then they later forked it into a thing called Fluxbox. And it was just your your everything was done from a from a right click menu. And but then you could put it into a like a tiling window manager mode. And so it would just everything it would just always tile. It was great. Yeah, I got I got super used to that. I was I was really fast on it. Yeah. And that was a long time. You remember Motif? Yes, I do remember Motif. Yes. Yes. I had had Fluxbox with a Motif like Chrome on it.

And then it was tiling mode and it was like, man, you could just fly. Well, kinds of shortcut keys. Yeah, I just get, you know, Windows just scares me. Yeah, it's like it's very critical to what I do. You know, you get all these just there's a lot of scary stuff. I'm like, no, I just don't really want any of that. So speaking of speaking of the the AI coding stuff. So I put I put up two repositories today. One is just one is a skeleton of of a thing. And we link to it over in the boardroom.

Copy, clean, paste. All right. In the boardroom. So in order to fight the AI slop battle. And it's just the spam battle in general amongst podcast directories and all of us. We this. We need some way. I feel like I feel like the only in the in the past, the way you would do this is with a machine learning model. And you would train a machine learning model to do some sort of recognition on a set of inputs that are coming from a feed. And you'd say, OK, here's the here's an here's an RSS.

Here's a podcast feed. And here's the title. Here's the description. Here's the image. Here's the the feeds URL. Here's the enclosure URL. Here's transcript. You just feed it all this data about you would you ingest all this data about a feed. And you'd say and you'd have a matrix and you would say, OK, giving given these parameters, it ends up being either a one or a zero. And that's your machine learning model to determine whether something is spam or not spam.

The. The easier way to do that, I feel now will be is using LLM. So. If instead we use a language model. Then we can. Then the training part becomes easier because now the training just consists of describing what what is a spam feed or a slop feed. Well, that's basically heuristics, isn't it? Yeah. But, you know, it's it's this is all text driven anyway. And all these, you know, all these RSS feed metadata. You know, aspects. So why not let the language model do it?

And so we need a place to describe. What a spam feed consists of or what a slop feed consists of. So that's what this repository is meant to do. What I what I think this should be. It's called podcast quality control. Did you post it on the index? Yes, I did earlier today. So podcast quality control sounds like a CIA operation, but it's not. It's a. It's going to consist of multiple files describing the different things. And I've already I've been testing this.

So what I have is I have an Olama server running the latest GPT OSS model. Mm hmm. And I have been I've been refining a script that calls the the open Web UI or excuse me, the Olama API and just asks it, OK, it tells it here's a feed. Here's here is a podcast feed and here's a title. Here's a description, blah, blah, blah. Based on these details. Is this feed spam? High quality, malicious spam or slop? Yes. Yeah. Got it. And it's actually beginning to do a pretty good job.

So does the Olama model it references these these files? Is that the idea? It references these files and then makes a determination. Yes. So that's what I've been doing is feeding it a bunch of things that I'm seeing. So I've been set of the context for its decision or for its, you know, the context for its model cycle where it feeds back on itself. The context there is I'm feeding it what I consider to be spammy feeds. Mm hmm. So that would be like Vietnamese casinos.

It's just all the stuff I'm seeing a lot of. Now, are you doing this based on the on the recent endpoint? Yeah. And so that yes. And so that is the other repository that I posted today. Which is. The index monitor. The index monitor. Oh, look, wait. Is this a is this a script I can load? It's a rust. No. You do. Do you have rust installed? Well, not yet. But I will just install rust and do cargo run. And you'll be off to the races. It should build for you.

If you just clone the clone, the GitHub repo down and do cargo run on it. Cool. So it's a command line tool. And again, this is just an exploratory thing that I'm trying. I'm throwing a bunch of stuff at the wall to see what sticks.

But I think we all would benefit from having a tool like this where we can interact with the index and, you know, in a way where we just have, you know, like you said, hotkeys where we can, you know, do just basically do do index management stuff from a thing from an app like this. And right now, the main interface, right.

Like I say right now, this can be changed, but right now the main interface is just polling every 60 seconds to see what the latest new feeds have been added to the index, giving you a little bit of detail about it. You can hit the X button to view the XML. You can hit the P button to play the latest enclosure so you can hear it here as a sample of what this thing is. And. That's it for right now. So this is sort of like a triage thing where you're watching what's coming into the index.

And you're able to say, oh, look, there's a you know, there's a junk fee or whatever. So the next step in this is some is to be able to put in an API, a read write API key. That way you can feed back and say nuke it. This feeds crap. Delete it. This feed is spam. Delete it. So this will evolve hopefully to become the thing, the essentially the management interface. Sorry. Thirty three thousand three hundred and thirty three from Noble Pain. OK. Good. Thank you.

This will evolve to become the management pain that we that we as power users for the index will we'll use. So that goes back to. And so excuse me, the the last. Portion of the management for the PI monitor management interface will be the ability to hook in like a plug in architecture. The the plug in part of it, what I'm hoping this that this will do is allow you to do some automation tools so you can hook in a script or something like that that will that will monitor on your behalf.

And then automatically do things so it could be calling some LLM somewhere or, you know, it could be who knows. I mean, backing up the audio from certain fees. I mean, who there is no limit to what a plug in system that could do if it's monitoring aspects of the index in real time. So I think that that could become the basis of the quality control system.

And but the issue is we in order for the quality control system to aspect of this thing to work where we're asking a model what it, you know, to make a decision, we're going to have to have the parameters for what the quality control is. So we need so what that would look like is you would say, OK, in the quality control repository, there's a file called, you know, slop.

And it's going to just just there's going to be a lot of text in there that describes all the aspects of the telltale signs of slop podcast. And you say when you call your API and say, is this slop? You say, go look at this repo file, which just describes what slop is. And if this feed matches those descriptions, then market a slop or tell me a slop so I can make a decision or give it a score or whatever you want to do. So this is all this is all spaghetti on a wall right now.

But I think we as an in as an industry, quote, unquote. Meaning people who have vested interest in the success of open podcasting ecosystem, we have to get a handle on this problem because it's every it's all over the place now. Yes. A lot. Yeah. I love the community aspect of it. I really think this is great. That is the way to do it.

The hosting companies have a lot of knowledge on this because I know firsthand the battles that they that they are facing with constantly removing spam feeds, feeds linking to escort services, feeds linking to. That's not spam, by the way. That's information, ma'am. Critical, critical information, information of the Vietnamese casinos, affiliate spam. Right. Right. I mean, it's just like it's hundreds a day that are getting removed, but they don't.

For all the hundreds that get removed, there's dozens that get through. They're just sneaky because people are having to manually do it. And so, yeah, I would like this to become that thing. And this is my. And so for that reason, I think the people who are the people who will have a vested interest in this would be hosting companies so that they can get the feedback.

And then they would also be the ones to to contribute to the quality control lists because they can they can type in the nature of what they're seeing. Mm hmm. They're not the only ones that are going to do it. But I'm just saying they have a vested interest. I think they would have a real boots on the ground look at these things. So right now, the things we can do are basically just view.

There's nothing there's nothing else in this in the PI monitor that does anything but just monitor basically. Are you running it right now? I'm still building. I'm doing in my cargo build. I'm almost there. You know me, don't you? Are you running it yet? I'm putting it on my little my my my Nano Linode box here. So I'll be running in a moment. Yes. So if you do right right now, it's just a it's just the structure of what it'll become. So I'm trying and this may change.

Other people may have ideas. And just like we're doing with the with the new aggregator stuff. This I want this to be a I LLM code friendly. And so that means you're welcome to throw some AI at it. You know, go go in there if you don't know how to if you don't know how to code rust, which many people don't feel I'm coded. I'm coded. Yeah. So anyway, I think that's a great idea. Try trying to get trying to get a framework here that we can use for tackling this slot problem.

Because it's it's going to overwhelm us if we're not careful. So then we have to have a PI monitor that monitors the output of everybody's PI monitor somewhere. Someone has to make a decision. Right. There has to be there has to be a thing at the end. It's like, OK, this is. Oh, it worked. There it is. Did it? Yeah. Yeah. Man, you sound you sound Mexican. The Charlotte business podcast Wow. Refresh. Wait, do I have to hit return when I hit refresh? No, it's just the R key should refresh.

But it may not be anything new. Right. Oh, I can get feed details. Wow. Oh, this is cool, Dave. Hold on. We hit this boom speaker. Huh? Well, that's a beautiful interface you bought that you built there, brother. That is very cool. It's this. This is a good project for spitballing UI is on. It doesn't like play latest from my from my remote box, obviously. Oh, oh, the audio. Well, yeah. It's like I can't. I can't. I can't. I can't do it. I can't do it, man. It's not possible. Did it crash?

Well, let me see what it do. Let me just let me hit it here. Play latest downloading audio. No such file or directory. A LSA lib. Yeah. OK, it's it's trying to play. It's trying to it's trying to play audio. I think you have to have the also system libraries. And then I need to X X display it out to my machine, I guess, or something like that. Yeah. Who knows that? But it's so this may not be the right UI for this.

But I was just thinking this this would become also the basis for so one way I like to work is I like to throw a whole lot of stuff out there. All kind of all at once. Mm hmm. And then. It can sort of all come together because. I think we can see that we are a lot of times at the beginning of a project or an idea, you have a sense of what all the parts are that you're going to need. You just don't know necessarily the details of how each one of them are going to work. Mm hmm.

So you can throw you can go ahead and know that, you know, OK, we're going to need a new parser. We're going to need a new cue. We're going to need a new aggregator. We're going to need a new database ingester. We're going to need a way to get the stats out of out of it and log monitoring. We're going to need a way to do a client side application in order to interface with the with the monitoring and with the management. We're going to need blah, blah, blah, blah, blah, blah, blah.

You already know the things, even though you don't necessarily know how each one of them is going to work. And. So that's the idea here is we already kind of know the components. So I'm just trying to get all the repos in place. Ahead of time. Mm hmm. So that then we can begin to fit. Now we can begin to fill it, fill out the details. So we, you know, we have the parser. We have a repo. We have the executor. We have we have all these things now.

So now let's go and just start to fill in the gaps. And I think what I'm going to do on the aggregator side of things. I think I'm going to use the live you know, this is how we roll. I think I'm going to use the live aggregate, the live podcast index. As the guinea pig for the new for the queuing part. So the queuing is not not the queuing is live. Live goes to the top of the queue right away. Right. Or am I am I misunderstanding what you're talking about? That's right. OK.

Yeah. Yeah. And so like if we if we use. One of the biggest problems and the reason why we had the aggregator five problem this week. One of the biggest problems is the lack of of queuing. And so. All the the parsing is extracting all this data and then it's all nine parsers are trying to cram it into the database at one time. And so we need a queue system to get it off the parsers into the database. And so I think what we can do is work backwards. We can begin with that.

We can begin by just not writing directly to the database instead of writing to the queue. And then and then get the existing system to work in that fashion. Then we can go and then now now that everything from the queue forward to the database is agnostic of what the parsers look like. They don't even they don't even know anymore what the parser is. And so now we can begin to swap those pieces out in a way that that works.

So we'll start with our existing database and just work backwards from it. And you're right, Eric. That lets you bulk update too. Yes. So the if the because the you can imagine if if the queue if sort of the the queue that's feeding the database if it's taking in just sort of genericized objects of data. Okay. So I already scored an AI slop right off the bat. Oh yeah? Yeah. And it's interesting because I already noticed with my own neural network with my knower so it came in in the PI monitor.

It's a Spreaker, of course. And it had no description on the feed. It's called Quiet Please. And because it didn't have a description right away I'm like hmm okay that's odd why didn't you have a description in there? And it says Ghost Ships is a three -part investigative series from the Quiet Please podcast network hosted by AI journalist Alexandra Reeves. Oh nice.

And so the next one because there's now three came in in a row because the only way I can tell is by looking at the feed and All from Spreaker? They all came from Spreaker? No the second one is from RSS.com Wow this thing is a mess. Also when they don't do it's weird when they don't do a description in the in the channel that to me that's a flag right there. You know it's like why don't you have a description? Yeah. And oh yeah Yeah.

Whip and do it I got it I do it I do it I do it like a maca like a honey hey yeah this is this is this is junk yeah it's junk it's junk I tell you junk and it's got no what it doesn't even have a media file? It doesn't have any enclosure? Wait it does enclosure hmm okay now hold on a second since I can't do play let's just listen this is very cool Dave this is a problem because now I'm going to be sitting here all day doing this. Yeah, this is a bad thing for you. It is. That's interesting.

Um, hold on. Let me… Let's see if we… Xin chào. Episode 5 khám phá thế giới cá cược trực tuyến đam mê và chiến lược cho… AI. That's a synthetic voice, yeah. That's AI. Yeah, that's AI. So right off the bat, I would say, hey, if you're coming through without a description in your feed, you're already sus. Put it, file it in sus.md, baby. It's a new entry in the quality control manual. Yes. Wow. Yeah. Wow. Very cool. So five of those came in. Tuckleo18, Tuckaluckaluckalo68, Tuckaduckata88.

Yeah. So it's all crap. Hey, RSS.com, that's from you guys. And yeah, you should have a language there and a… Yeah, if you hit enter, it'll give you some details. Oh, yeah. Well, the funny part is it gives me language EN, which it clearly isn't because it just, you know, it's horrible. I mean, you can tell right away. That didn't even take the time to fill out the description or the… So we have title, link, three links, description, but the title is the URL, which is this Tyler Huckaluckalucka.

Let me see. Yeah, I see the 18. Yeah, exactly. Tylerhuckaluckaluckalucka18.com. Yeah. So that right there is generated. You know, some douchebag put that in there, right? Mm-hmm. Yeah. Yeah. What does that go to? Kio Bondiakanda. What is… You sound like a Mexican radio announcer. It's Vietnamese. It's some Vietnamese spam. There's a ton of spam coming out of Vietnamese stuff right now. Hey, listen, you guys, don't you remember us? That was a really… What? That was a really bad joke.

Hey, Vietnam, don't you remember us? No, that was a bad joke. It was a very bad joke. AI 2030, conversations about the future of AI. Okay. I cut it. Yeah, this is a mess. This is sexy. It updates in real time, too. I think the alternate interface for this needs to be like a real-time view of what's happening in the aggregators. Right. So that it's not hidden behind a curtain of secrecy. Right. You know, where you don't have to say, hey, Dave, why is my feed not showing up?

Where you can fire up the monitor and look at the aggregator output, and you can spot some kind of issue. Well, this by itself… I mean, I could sit here and just go, mark, mark, mark, mark, mark. These three can just go. And then, of course, because they're doing incremental numbers, Thaily Kakuak 1868-88, you know, that would be like some flag we could tell the LLM like, oh, when you see this nonsense going on, start getting rid of it.

Yes. The next thing that's going to happen is a flag as spam key in this thing, which is going to flag the index that this thing has been manually identified as a spam feed. And then the hosting, and then there will be a corresponding API endpoint where the hosting companies can poll and see which ones have been identified as spam. Because a lot of times they don't know.

No, but this is so good because, you know, our brains are much better than AI at recognizing this, but we could totally, totally teach it. And, I mean, just now another four came in, Anchor, Buzzsprout, RS5, three, and they're all, none of them, you know, they all have their description as the URL, which is just like, that's going to be spam. I already know it. The Pool Guides Podcast, hosted by Christian Shrilla of River Pools. Which type of pool is right for my family and climate?

Please, do they even say it's AI? No. And what's interesting is you see things across different hosts that all correspond. So you'll see the same links and spam links and descriptions showing up almost all at once across RSS.com, Buzzsprout, Podbean. They hit them all. Transistor, you know, and they're, what they're doing is they're abusing their seven-day trial signup stuff. Yeah. But they're not even putting in an enclosure in these. I mean, there's something Buzzsprout could do right away.

Like, hey, you forgot an enclosure. No. Well, you have to create the, you know, you create the podcast first, then you add the episode. Oh, that's what's going on. They can't really do that. Okay. I see what you're saying. Got it. Yeah. But you can check out, if you hit the X key, you should be able to check out the XML. That's what I'm doing. Yeah. I'm looking in the XML.

Yeah. Needs to be a little bit of, probably needs to be some color coding in here to be able to kind of differentiate, because it's hard to read. But yeah, we'll see that you, I think it'll be obvious if anybody downloads this and runs it for a little while and just watch, it'll be obvious what the problem is. Everybody needs to listen to the Swine Health Hotline. Yikes. Where'd that come from? Is that in there? Just popped up. Oh, it has an enclosure. Hold on. Let's listen to it.

You know, because I'm just presuming it's spam. No, I just see it now. Let's see what this is. It all comes down to health for your pigs. 37 seconds. And your operation. Health challenges aren't going away, but Swine Health Hotline will answer your health questions so you can make the best decisions. Oh, this sounds real. Hosted by me, ag journalist, Casey Brown.

This podcast will arm you with valuable insights on swine disease mitigation, cutting edge research, safety protocols, success stories, and more. I'm subscribing right now. Yeah, I'm in. I'm in, I'm in. I'm putting it in my Godcaster. I need Swine Health, baby. Oh, this is so beautiful. So much fun. So, okay. So there you go. That's, that's probably actually a real podcast. Yeah. Oh man. This is, this is great, Dave. Just this. So, all right. So how soon can I start vibe coding and doing PRs?

Hit it, man. If I don't get a PR from you on this by the end of the week, I'm going to be disappointed. You're getting a PR from me on this one for sure. Okay. This is beautiful. All right, everybody. Let's thank some people because we do have about 10 minutes left. And we got that magic number boost from Noble Payne, 33,333. And a nice Boostergram for the Don't Kill Dave Fund. Adam made me send it.

The V4V love in this episode reminded me that over the holidays on Linux Unplugged, we had our annual Boosties event. It's our little celebration of the value sent to us by our amazing audience. It's one of the things we use the current keyboard metadata for, keys and metadata for, by the way. Okay. Message received. Just thought y'all might appreciate the community love. Check out episode 646 for that long live Aggie 5 long live podcasting.

And welcome to Linux, Adam. No, I've been using Linux for a long time. Do it for Aggie 5. That's right. Aggie 5 is alive, baby. We've got Martin Lindiskog with 1701 coming in from True Fans. By the way, the Noble Payne, that was from the Boost Bridge. Adam and Dave, thanks for the open source talk. Open in parens, source talk. And the gig economy. Talking about computer nostalgia, have you owned a Commodore 64? Check out Generation 64 book. Time for a ride with a spaceship.

Well, I had a VIC-20, which is the precursor, the predecessor to the Commodore 64. And before that, I had the Sinclair ZX80. Commodore 64 was my first ever computer. And the first programming I ever did was using the basic book that my Commodore came with. Yes. That was the same that I did. Although I started with the Sinclair ZX80 and then the VIC-20, which was a problem in Germany because VIC, you know, it sounds like fic, which is F-U-C-K. Oh, yeah. They had a marketing problem.

Yikes. The first thing I learned how to do was how to get into the game module that you plugged in and copy it to cassette. Oh, don't copy that floppy. Don't copy that floppy. We were copying those plugins, man. Let me see. We have 3333 from SirLibre. Remember to check out tonight's live show featuring SoBig. That's tonight, 7 p.m. Central. Get more info at boostbeach.live. Brought to you by Boobury and the usual cast of Hobbyist. Yes, those guys are always doing cool stuff.

Then I hit the delimiter. There you go. You're up, Dave. Oh, I got some PayPals. These are over the emails because I didn't have time to print them out. We got Oscar Mary. $200. Nice. Thank you very much, Oscar. That is highly appreciated. Yeah, appreciate that. Sorry about AggieFive, Oscar. It affected him, too. My apologies. Well, I'm on the Fountain hostings. That's how AggieFive hit me. But it doesn't have anything to do with Fountain, per se. Hashtag remember AggieFive. Rip AggieFive.

Rip AggieFive, yeah. Joseph Maraca, $5. Thank you, Joseph. Appreciate you. Oh, there's $50 from Mitch at Podverse. Thank you, Mitch. Thank you very much, Mitch. Yeah. Archie has been helping me to come up with some strategies for how to do these architectural changes as well. He spent a good hour and a half on a Zoom call with me the other day walking through the way the index is structured and stuff and just really giving some advice. Very cool. Yeah, I really appreciate his time.

Lauren Ball, $24.20. Thank you, Lauren. Appreciate you. Christopher Harabaric, $10. Thank you. Really, I'm so appreciative of these people who have just been all supporting like every month for years. Yeah, no kidding. It just is awesome. Mitch, on a personal level, not a Podverse level, $10. I appreciate you, Mitch. And I think that's it for our PayPals. Yes, that's it for PayPals. And so we got some boosts. Let me flip back over here to our boosts.

We got Anonymous from TrueFans, $47.30. Thank you, TrueFans. I wonder if that's Lyceum. Probably, probably. He's a heavy TrueFans user, I think. Yes, he is. NAMillennial at Fountain, $5,000 sats. For the quick turnaround on the feed URL issue, the offensive thank you. Oh, I fixed it. I fixed that. Oh, thank you. Yeah, I bet. I've been learning Merge. I've become quite the Merge wizard. All that I want to be in this command line app. In this terminal app. That way it'll fit into your...

Well, it will permanently occupy a space in your own marchy tile. On my fifth monitor. Yeah, on the fifth. Let's see. We got a boost. We got $22.22 from Celos. Oh, thank you, Celos. And that is through Fountain. He says, I get putting HLS in the enclosure for ads purposes, but I expect that to lead to many self-hosted feeds trying this out without having an SSL certificate. So on all the HTTPS web apps, they now won't be able to play an episode.

Insecure media requests are allowed in browsers, but not in secure HTTP requests. That's something to think about. This whole SSL stuff, man. Now certs can't last longer than 45 days. That's the latest I've been hearing about. Yeah, 47. Yeah, and then why are you doing this? Just set a script to renew it automatically. Okay. Yeah, sure. I don't have enough servers in my life where that has to happen. Yeah. Tell that to Google organization.

Yeah. Tell that to the organizations that have an exchange server sitting in a closet somewhere. All that stuff's just going to break. Comedy Strip blogger. We got the delimiter. The delimiter pops in. Yes, beautiful. Through Fountain, CSB says, Howdy, Dave and Adam. I would like to recommend a recently revived podcast with Adam's wifey, Tina. How does Tina feel about being called wifey? She loves comic strip bloggers, so she has no problem with his vocabulary. She's okay with it.

You can find it at www.curryandthekeeper.com or by searching for a quote, curry and the keeper, unquote, in podcasting 2.0 apps. It's about their life journey as a couple, including their friends from Texas small city, where they live called Fred something. They need Bitcoin grams badly to buy food for their dog, Phoebe. So please send them some Satoshis. Yo, CSB AI arch wizard. Yes. Brother, if you need food for the dog, you got to speak up, bro. I'll send you some cash.

The dog is working on the value for value system. You know, if the dog doesn't do what we want, there's no food for you. Oh, you need one of those things. You need one of those, one of those triggers like with a goat feeder. Remember the goat feeder? The goat feeder was great. You boost some Satoshis and then the goat gets some food. Yeah, just Phoebe, some food just ran into Phoebe's bowl. Okay. All right. All right. Well, I'm on it. I'm on it. Was that it? That's the full gamut.

Well, thank you. Thank you all very much for supporting podcasting 2.0. The podcast index mainly, and you can go to podcastindex.org at the bottom. If you'd like to send us some PayPal, do that. The big red donate button. But of course, you can always boost this show and send a booster gram. All right. Boom. Look at that. Within a minute and a half to spare. Although I feel I'm going to be stuck here watching these, this slot. I'm sorry I did this to you, bud.

You're just sitting by the PI monitor watching all the fees come through. There is so many of these. And some is not. What? And there are so many of these T -Y-L-E something, something, something. Oh, goodness gracious. Tons of, I'm just watching them roll by here. Well, I have a feeling that there'll be a race for the, for the slop key, because you see this and you just want to hit the slop key. Like, oh, this is slop. I just want, and by the way, I think there's a spam and there's slop.

I think that's two different, well, you have a different doc. I agree. I agree. There's spam and then there's slop. So there's, there's also that, that, that file in the repo for what, what is a high quality feed? Like, I think you need to define both. Yes. What does a good feed look like? What does a bad feed look like? Exactly, Chad F. It's the new toilet scroller. I'm so excited. You can run it on your phone. All right, brother. Thank you so much. This was a good one. Great board meeting.

Boardroom. Thank you all very much for being here. Remember Oystein Berger kicks off in just a few minutes with his mutton meat and music. We'll see you next week here for the board meeting. Take care, brother Dave. See you, everybody. Bye-bye. You have been listening to Podcasting 2.0. Visit podcastindex.org for more information. Go podcasting! Don't copy that floppy.