 Yep, so we worked on a diagnosis tool with Lindsey for the IPFS stack. So the IPFS stack is quite new and quite complex. So it looks like magic sometimes, right? And when something breaks, it's not really obvious how do you fix it. When you come from WebTube, you are used to have a lot of tools to debug things like PNG, DNS checkers, trace routes, a lot of tooling, and we don't have all these tools in Web3 yet. So the team gets the same question over and over again, like, it works on my machine, it doesn't work on this machine. It's fast on my desktop, it's slow on my laptop, why? So we end up answering this question again and again, and the team also created a lot of tools for diagnosis. For example, Adin created an IPFS check tool that lets you fix issues of why you cannot find data on IPFS, but you might not know that this tool exists. So our goal with PL-Bagnos, with Lindsey, was to create a one-stop shop to figure out how to fix issues with the IPFS and the PL stack. So one task, can you go to the next slide, please? So one task was to list all the tools we could find on a single page so that you know where to look for when you have an error. And also when you create a new tool, you know where you should share it. So that's the tool page you see, the screenshot at the bottom left. The other task was to recreate the IPFS check in a way that makes it easier to explain what is happening when you have an issue and also make it easier to throw more features at it. So what we did is we took the backend from IPFS check that Adin developed and we extracted different steps. So when you have an issue, like, hey, I cannot access my data on IPFS. Why? We give you this tool where you have four steps, where you test the four steps that could break when you try to access data on IPFS. So step one is my content advertised on the DHT. So we check this step. Then is the peer providing the content present on the DHT? You have one small tool that checks this step too. Then is the peer reachable from other peers, which is the most common issues with natural assault, et cetera. And then last step is the peer selling the content. So if any of these steps break, you can see the first two ones at the top, they're green. And one of them, the third one, went yellow. So when there's one of these steps that breaks for retrieving content, we give you tips on how to fix the error. And you get some feedbacks and advices. So on the back end part, it was quite interesting to quite interesting, sorry, to dig into the stack, because IPFS is like a puzzle. And looking at adding score was very interesting, because I figured out like, you can take pieces of IPFS, like pieces of libraries, and build like a very small fmrl IPFS node. So it's a very smart way to pop up a very tiny node for a diagnosis tool. And Lib2P has very fancy connection-gathering mechanism that will let us, we discover new features that were interesting, basically. Lindsey, do you want to go over the front end part? So yeah, I think one big thing, too, is that it's hard to understand what some of these concepts are. Me and Lauren was very patient. He kind of sat with me and explained the difference between like a multi-address that has your location and one that doesn't. And going through that learning process for the first time, I think was really valuable to create a tool for people who are also using it for the first time. From experience, the experience I've had in test automation, we had one tool that people used to diagnose and figure out what was going wrong. And it was the most popular page visited. So I see a ton of value in something like that. And I think it'd be really cool to create one place that has, as Lauren kind of created a little area, like where are other tools? It'd be really cool to have one place to identify what the problems are and do it in language that expresses what I'm trying to do and not necessarily language that is part of the, I'm already part of PLN and I know the vocabulary. So he also taught me how to create a react component. So it was really fun playing around with creating these react components, making them better and serving it up on fleek. One key feature that I think we figured this out and I think it's a key feature of this is that seeing the green results, like the yellow screenshot. So you tried something and you get an error. And so the error is like, I cannot access some data. IP address, nobody does something like that. So we give you tips on how to fix it. And we also give you a link to create a GitHub issues, which means that as a user, if you're looking at the dog that we wrote for you and you cannot solve your problem, you can just click on this and it'll create an issue in our repo with all the details, like what we showed you and the URL and the parameters that you tried, which means that we can then answer your question and fix the tool and we never answer the same question twice, hopefully. So yeah, that's, I really like this feature. It's really simple to just a link, but I think it makes a very useful tool.