 We're going to do another one of our HTTP203 microtask speedruns, right? Yes. Oh, no, it's microtask speedruns. Oh, I don't know. We are not going to branding, mate. I think microtask is a good branding for it, right? Because the idea is you're going to explain a thing in two minutes. Yep. Go. Broadcast channel. Broadcast channel. Yeah. OK. Oh, hang on. Broadcast is a WebRTC. You're going to get in trouble, you know? No, no, no. We're in a different area. It also has been around for quite a time, similar to workers. But it doesn't have as wide support, sadly, because it's not been used a lot, but it's really cool. So you're the type of worker? No, but it has to do with workers in a way. So a broadcast channel is basically a post message channel associated with a name. So I can say new broadcast channel, Soma. And now I get a post message endpoint for the name Soma. And every other site, every other realm from my origin, like my workers, my service worker, all the other tabs that are open from my site can now communicate through this same message channel because they know the same name. So it's like pubs are across tabs across? Yes. And you don't have to worry about knowing which tabs are open. Do I have a service worker? How many workers are there? It just works. And that is brilliant because what it allows you to do is to write little pieces of code, little modules, that just hook up to this broadcast channel and start working. So previously, you would have to use shared workers to be the sort of middleman for all of this. And have some kind of management unit. This module is now here. Do you want to talk to it? And now you just have this central unit in the platform. And whenever a module is finished loading, it just hooks itself up to the thing. And now you can talk to it. And that is absolutely amazing, if I've recently discovered, for code splitting. Because you just load things whenever you need. And they just start working. You don't have to actively, statically import. You just dynamically import. So what kind of messages are you sending through this? So I have a cache manager in there. I have things that do my color scheme adjustments, my animator. All these things are now just like little, tiny, independent JavaScript modules. And they use broadcast channel to talk to a worker, to my main thread. So one page receives an update. And it can just tell all the times, I've got this data. You don't need to go and refetch it. Yeah. It's there. Brilliant. And what, browsers? No. Call my Firefox. Brilliant. There we go. I like that you knew that. How was that for you, mate? Was that right in the ears?