 2017 is the present, but soon no longer for 2018 as upon us. And our future. The future. Well, soon it'll be the present. That's the weird thing about time, is it keeps just coming at you. But I wanted to think about some of the things that are going to be landing on the web in 2018. And I wanted to try and describe one of them to you for you asking questions in two minutes. I want to talk about the Fetch Observer. The Fetch Observer doesn't have to do with actual Fetch. Yes, it does. Does it observe Fetch's? Yes, it does. How? Magic. Through web specs that we have yet to write, which is right now it's just an API kind of sketch of what this will look like. But which problem does it solve? The problem of I want to observe Fetch's. How can I do that? But what do you want to observe? Because you can usually already know when it's done, right? Right. So it's mostly about all of the stuff that happens in between. OK. So what happens in between? Well, things like it's connecting to the server. It's connected. It's waiting for headers. It has headers. And then things like there'll be upload progress. OK. Download progress. Oh, that's good. And those two things can happen at the same time, which I didn't know. You can be uploading while you're downloading. This will give you that piece of information. And it'll be like a separate object so you can sort of pass that to another piece of code so they can observe the Fetch without having any control over it. So could I? I do a Fetch on my server server. Like let's say download for a bigger file, bigger asset. Can I take out the observer, pass it to the main thread, and have UI updates? Kind of like, that's one of the things that probably are going to happen. You want to download something in the server server in the background, but have a UI that updates in real time with the progress? That's exciting. That will probably be v2. But it might be v2 that actually happens because it's a good use case. But you will also, if you're sending that to the page, then you'll definitely be able to get it from the Fetch observer from the page side. And it's also where we can start adding extra bits of observation, such as observing push, like H2 push. Oh, that's interesting because so far you don't know when something gets pushed. Nope. So the idea is we could have on this Fetch observer an event that says, like, yeah, you've been given this. Do you want it? And it'll be, you know, you'll have a way to sort of consume it and bring that through the network into a promise. I'm really excited about that. Cool. It's an import function. OK. It's a function. Well, technically, no. But that's a difference. What? You've already lied to me in one of the words you just said. I know.