Speaker 1:
Well, hello. It's nice to see you. Does this mean I'm in your pocket? I don't I don't exactly know, but it's a big pocket.

Speaker 2:
I I, you know, I just I shop I shop for the pockets. I optimized for pockets, smart man. You know, I carry around two phones now. So gotta have big pockets. Necessities. Right? You're not a big you're not a big carry. You eat light, so it's fine. No. We wanted to get together and update everybody on a few things that are going on because we have a few new toys to talk about, and as sometimes happens, we broke things too. So there is a few things to update everybody on. So we wanted to get you a pocket office. And if you're hearing this, you've most likely downloaded this using the brand new podcasting two dot o compatible feed, and it more likely than not was delivered to you over the IPFS network. How neat?

Speaker 1:
I think that is so cool. The other thing I love is You don't have to know. Like, it can just work and you don't need to, you know, users and listeners don't need to do anything to be involved. They just kind of -- Yeah. -- works. I love that the IPFS part is,

Speaker 2:
one dot o app compatible as well. That's really nice. And so the way you know you got the new feed is if the office hours podcast name has changed to office hours two point o.

Speaker 1:
Will that make it easier to search for in me? I think it might don't know. I think it might. We'll try.

Speaker 2:
There the that was I mean, I kind of punted on the rename thing because I'm just playing around with, like, this is a whole new set of features in distributing over IPF is IPFS is gonna be so neat, but if all goes as planned, this will also be the first episode that has AI generated chapters.

Speaker 1:
You assume we're smart enough to talk in ways that chapters are appropriate for, and I'm not so, I'm not so confident. I'm not either. Because as as of right now, I haven't generated them. They could be total garbage. Yeah. I know.

Speaker 2:
We'll have to see the, you know, the question is is where does AI play a role in production because you've got AI chapters it can generate, but it's also, seemingly possible now to use different tooling to generate entire episode summaries. Right. So what it's doing is it's string together whisper, which is an open source transcription back end software. Whisper outputs to a format that could then be ingested by Open AIs API, chat GPT then summarizes the whisper trans script and generates a podcast summary.

Speaker 1:
This whole, like, linking of things together. I think that's where the beauty comes in. You know, we were playing with them individually, what, six months ago. Now all of a sudden, everything stringed together, I think.

Speaker 2:
I'm starting to like this. Yeah. And since we're gonna run it through whisper, To generate the chapters, that's also gonna kick us out a transcript for podcasting to a local client. So this should be the first pocket office or office hours with transcripts.

Speaker 1:
And so tell me how much of all of this do you have figured out? Or is this just like,

Speaker 2:
this is oh, this is still an experiment, isn't it? Well, I got the back end tooling figured out. I haven't used it altogether yet, and I haven't seen the out put yet. So the possibility is there. Because I needed an episode to run through it that I could do all this with. So here we are. Right? That's why you brought me here. Don't understand. We'll see if they, I can figure out who the heck you are. Right. About that. But let's talk about what broke. Because whenever you introduce new stuff, Unfortunately, things break.

Speaker 1:
You said you as in me, but it was you. You introduced new stuff. It was the royal. It was the model. Okay. Alright. Alright.

Speaker 2:
So starting with IPFS, IPFS podcasting is working really good. My node seems wonky. And I've had issues where it's had to redownload files a few times that's been solved, but I've also had to reboot it now. About three times. I've had to reboot the box. Thankfully, their network becomes aware of when a node kinda disappears, and they send you an email after a certain amount of time saying, hey. Haven't heard from your note. Is everything okay? And then that tells me, okay, I gotta go reboot it again. And then I reboot it again, and it's fine for a few days. The, like, dreaded email. Do you know What's going on under the hood? Any possibility of solving it? I haven't really dug in too deep. I don't see anything in the logs that I checked. There's like a IPFS podcasting log. Per everything there looks pretty basic. I'm thinking I wanna do a clean install. Try it again. Maybe on a different version of maybe maybe I think I might not be on twenty two zero four. I can't remember if I'm on one LTS backer or the current. But I wanna make sure I get all that squared away and see if I can reproduce a node without problems because ideally, I'd like to probably pop up a few nodes around the world. To help see.

Speaker 1:
Yeah. I'm remembering that this was an Ubuntu base with a script on top of his Mhmm. Mhmm. Yeah. Script. We know it's very handy, usually. Yeah. Yeah. So I'm just not a hundred percent sure on what happened.

Speaker 2:
What ideally would be amazing is if I could run all of this in a docker container. And they provide you a docker composed to get up and get going. That to me would be then it would take it, it would take it away from a bun till you could run on anything, even a container was ubuntu based, you could run it on anything, including for us, Nix, which would be huge for us. Does it seem a bit surprising that these days, projects don't just do that by default? Yeah. I guess I was a little surprised. It's, you know, still you get you get somebody. One person makes this script. They use a Ubuntu. This is how they use a Ubuntu. And if, you know, it does work. So it's a lot of times, that's good enough. Yeah. Just seems like aged methodology, maybe. Maybe. It really probably needs somebody else in the community come forward and contribute. Now we're talking. Yeah. Okay. So, gotta get that note stuff figured out thankfully because the show gets distributed to other IPFS nodes, like my note can go offline, and it it's still fine. It's just I want I want my note to be able to in there too. And build a collect stats and whatnot. But I also broke, and this is a bigger deal. I broke the entire Jupiter Broadcasting website. This doesn't have anything to do with IPFS, but when I was rolling out the fancy new feed for office hours with all the new podcasting two dot o features that we'll be introducing. I was really clever in that I just set up a nice little redirect fireside makes this totally possible built into the fireside platform. And I just set up a little redirect. So when you go to office hours dot hare slash r s s, That now takes you to the two dot o feed I have hosted on linode object storage. Does a redirect to that XML file on Linux object storage. Real easy. Check the podcast apps that I tested in. They all got the updates just fine. I patted myself on the back and said good job, Chris. You've transitioned to a fully two dot o feed, and off into the weekend I went. And it turned out, I broke the web scraper that our community built to scrape new episodes from our various endpoints and auto generate the website. So Can you kind of tell us, give us give us a little idea of what happened there, Brentley. How did I break things?

Speaker 1:
Well, yeah. You did it again. It seems. But what's interesting is Sometimes we don't know what's gonna break. You know, our systems have been automated, which has been for the most part, really amazing. Do you remember how you used to make each episode post

Speaker 2:
manually on the website through WordPress. I can't even I'm getting close to it with Office as again, but Oh. Yeah. No. I can't even it's horrible.

Speaker 1:
So on on the whole, it's been amazing and an amazing transition for us, but occasionally, things break. Know, especially when Chris is in there dabbling with feeds, with the fingers on the, on the pulse. So I think what you ended up doing was making it so that the scraper, which just dives into our fireside feeds, just scrapes everything. And it wasn't It wasn't designed to be extremely robust with error reporting. Like, let's say it ran into an error. Right now, it just fails. And really, the better way is to allow it to fail and continue to scrape everything else. So it was failing on office hours because we had some issues there, which I'll talk about in a sec, but that meant was that no episode was being updated. So Linux unplugged went out and just never appeared on our website as it usually does. What's great is a new listener picked up on that first and, reached out to us and just said, Hey, by the way, I noticed I was really excited for the new episode because this is, like, week two of me being a new listener, and, they didn't find it there, unfortunately. But that said, Our website team is amazing. They, like, dove in and tried to figure it out. West stayed up, of course, late. And got something at least on the website, but I'm seeing now that chance just put in a PR, like a few minutes before we're recording this. And, it looks like there's a fix in the works. So, the team is solving your problems, Chris. What was happening or at least from what West mentioned to me because, I don't know, runs over my head. He mentioned that, this Grapers started failing because the office hours feed is now redirected to the new podcasting two point zero test feed that you made, Chris. But unfortunately, that redirects both the slash RSS and slash JSON routes that we were using previously. So this raper would try to grab them from the JSON route, but it actually ended up with the XML feed that you've made. And so it just broke.

Speaker 2:
Yeah. It just would die. It got XML out of JSON. And I didn't I don't know what to do with it, but I'm just gonna stop. It's not like it's documented at fireside that your, you know, the UI says you're redirecting the slash RSS. URL. It doesn't say anywhere in there about redirecting the slash. I didn't even know it a slash case on the URL. Right? That's nice to know. But I didn't know it was redirecting that one. So I didn't even think to warn anybody or anything like that. Well, the interesting thing is none of us thought of it. So it's not only on you, you know. But it's fixed or it's getting fixed as we record.

Speaker 1:
Yeah. I mean, the the newest episodes are the website now, which is great. And there's a fix in works before another episode goes out, so we shall see what happens on the next scrape. Well, a little extra salt in the wound for that period of time

Speaker 2:
is that around the same time a few a little bit earlier, Google rev the API requirements for publishing to YouTube which broke our ability to publish to YouTube. So we weren't publishing to the main website, and we weren't publishing to YouTube. And it is just a mess. And of course, that requires a little bit of retooling to update for their new API requirements. So that still isn't fully fixed either. Thankfully, the RSS feeds continued to function. And that's really the source of truth for the show. So Oops. Yeah. It's a summer. It's summer and things are hot. Tell you what. But that was both of those are on their way to getting fixed. And, you know, kind of unexpected. But I'm glad. It's sort of nice to have this time that we've been retooling to catch this stuff because it took us a few days to catch all of these things because you only notice when you publish. And if there's a few days between publishing, you don't even know it's broken. Yeah.

Speaker 1:
It's true. Yeah. I feel like it has exposed some ways that we can do, you know, for instance, the scraping better. This scraping is a bit temporary. Let's say long term temporary, and was designed that way because we knew that eventually we want to move to, you know, generating our own feeds and such. So the scraper will then not really be needed at that point. But I think we all thought we would be there by now, but we are So the scraper, you know, maybe there's different ways that we can treat it for now and move on. Yeah. And,

Speaker 2:
now that we've done this, The question I would have is if I redirect the other shows at some point, will it break again? Yeah. Probably.

Speaker 1:
We should we should say yes. Okay. And if it doesn't be surprising rather that way. We'll coordinate that move.

Speaker 2:
So there's that, and those are all things that we should hope I've resolved by the time we produce the next official office hours episode. And before we get there and read all the fantastic booths that helped us get to our milestone, I did have a couple of pocket boosts. I wanted to get two. So let's transition

Speaker 1:
to the pocket boosts. Now it's time for the booster boost to boost boost to gram corner. Booster to gram corner. I don't know if about crypto.

Speaker 2:
So I just wanted to cover a couple of booths that were relevant to the last pocket episode. Cameron boosted in with a row of McDuck twenty two thousand two hundred and twenty two sets. And Cameron is deeply involved with IPFS podcasting. He wrote excellent description of IPFS podcasting The IPFS prefix is our preferred way in your own feed. And so that is where you give a little HTTP redirect put it at the beginning of the URL for the MP three file. And then you can just use your regular old feed and use that redirect He says I can't wait to favorite the show on IPFS and start hosting the content. Cameron also reached out to me when I was having some note issues and helping me resolve those. So Nice. Really helpful. And gave a real nice warm welcoming feeling to the IPFS podcasting community.

Speaker 1:
I think I'm noting, Cameron also boosted in a row of ducks or a grandpa of ducks. So he's he's in on the nose as well. He knows about the Mcducks.

Speaker 2:
Magnolia mayhem came in with ten thousand sets, so I believe he's had some laptop problems raised recently and said, Probably not gonna be able to boost in for a while, so I figure I better make sure this is actually useful. That's, he says that was definitely an excavator in the episode image. Last week. So I was playing around when the things you can do in the podcasting total feeds is you can change album art more often and things like that. So I I put a picture of the cornfield and the excavator that I was using or I wasn't using, but they were using, but I was using to sit at. And, I was like, I don't even know what this piece of equipment is, but I'm using it as my podcasting spot. It turns out it is. And I, you know, looking back, of course, it is because that's what it does. It excavates. There is some seriously cool equipment that I don't have any idea what it does or how to use it. I'm just grateful other people do. Are you tempted to, like, let someone throw you in there and see what happens? Oh, yeah. One day. For sure. Right. Yeah. Yeah. Like, maybe if, like, we're gonna, grind up the cornfield or something like that. I yeah. I can do that. You know? Jump up there and put a podcast on and think I'm supposed to be drinking a beer, although I'm sure you're not supposed to, but every picture I've ever seen guys also got a beer going. I got a podcast going. Maybe like a cigar. You know, I could I could see it working pretty good. Excivating in style. Yeah. Yeah. Alright. Well, so that's kind of the little update we have for everybody. We just wanted to, I guess keep you in the loop on what we're working on for the show and what's broke and what's working and where things are at. So it shouldn't be too long now until we're back with the official office hours, which I was thinking, Brent. The pocket additions don't count as an official episode. Yeah. Sure. So we'll be back with thirty four. Okay. I think I don't I don't unless something else really goes crazy, then we'll sit down and do their pocket pocket office and let everybody know what's going on. Otherwise, We'll be back soon. Thanks for joining us. Now, get out of here. We all gotta go back to work.