 It's splitting and. Pardon? Yeah. So this is the place to which you put all the displays. So, yeah, I don't understand. Can you put your stuff on this one? Would you? Yeah, could you? OK, no, the flux shouldn't be affecting it right now. It is? OK. OK. OK. Why do you need a flux for mine? No, no, no. At the night you need it, actually. Doesn't it? That's brightness. That's color. Softness is working. But there is one screen, which is working. No, this one is working, no? Yeah, but it's not. You can put your stuff. Try to put your stuff. Can you set it to higher resolution? No, it seems fine. This one. OK. Anything that's going outside the boundary, so I just had to put it in the screen? Yeah. Oh. No. Actually, this is better. No, it's fine. Oh. It's OK. No, this one is OK. Yeah. OK. OK, so you see two browsers, OK? So think of the two browsers as this is the user. OK, this is you, developer. So now, I mean, what this hack basically is about is, if the user does stuff over at his place, OK, or clicks or whatever, the developer sees it, OK? So if there is some DOM change, OK, it's hidden over here. But yeah, again, the developer can see it, OK? But I mean, so basically, the DOM events are, whatever changes are happening on the DOM will be showed up over here, and the mouse events, and the scroll, and things like that. But the interesting part is, so this is the usual DevTools, OK? The DevTools is connected to this guy, OK? So a developer can basically change stuff on user side. It's like WinRay, right? Yeah, it's Web Inspector remote. Web Inspector remote. It's Web Inspector remote, but Web Inspector remote will run only on the user's system, OK? OK. This can be on any system. I mean, I can show you it on my iPad and all that. OK, so this is running on any system. This is user side. The DevTools is connected to this guy, and whatever changes happen, they are mirrored back to the... So the right one is debug target. The right one is the debugging target, yes. So for example... The server can be anywhere, that's what you're saying. Debugging server, no, this is a developer's browser. OK. There is a server which is trying to intermediate between these two, OK? So, yeah, I mean, I can show this demo of changing the color or background or whatever. You just get what's happening, essentially. So yeah, now you can ask questions. It's tightly coupled to Chrome itself. Yeah, it's tightly coupled to Chrome. I mean, so this DevTools thing, basically Chrome allows it to be run as a server on the... Look, so it's basically for Android phones. So what I was thinking was, if it was not regularly coupled to Chrome, this guy would be in here and he could open different browsers and see how it reacts. No, it is... There is a browser stack and things like that. So, yeah, I mean, this... So we can do this, right? Yeah, it's coupled with WebKit. So... So whatever browser allows this to be run as a remote server, OK, on the local host. You can do that. You can do it, yeah. Do you use Win3 server, Web Inspector, no? No. OK. I think there is a bunch of index calls it's making and there's a script you're downloading there. No. So what's happening is, I mean, so how the user starts this is... So this is user's browser, no? So he has to run this command, basically. OK. So what it's doing is going at a... I mean, a server, which is basically intermediate between these two guys. It's asking for a subdomain that is h.local right now. I mean, that is h right now. And it's basically tunneling... So this Chrome is open with remote debugging option. So DevTools is running as a server in here. So if you go into this guy's PC, user's PC and type localhost colon 9222, you can see the DevTools over there. Now my problem is to basically have access to this server over the internet. OK. So that's where the remote tunneling and things like that. So there is another project that I did called GoTunnel, which basically allows you to make your local server accessible over the internet. OK. I talked on... I mean, I told our friend Ray, right? It's not glued to work it at all. You can use it on any browser. OK. Apart from where it doesn't work with the... Which one? It works with Safari. It works with Safari, but not... Even on Mozilla? No, that's fine, because it doesn't matter if it's just Chrome here, seeing your DevTools. Yeah. So what does it do? By the way, it is going to work on Opera because Opera is an updated WebKit. So why does it do that? They're not moving away from WebKit. They are cloning. They have forced the WebKit as a new engine so that they can make you... Yeah, there's no new prefixes. Thankfully. So instead of using prefixes, they're going to be using an experimental... W-E. I-n-R-E. I-n-R-E. I-n-R-E. You have to connect via USB 4. No, no, no, no. And the script is being injected into... That is local. It runs as a node server, and you need to have nodes installed. So here's the cache. So we need only three things. Devoging server, debugging target and client. One more thing is that the middle, which transfers through Jack's calls. If you have these three things, you can do it anywhere. That's how we were working at Adobe. So if you do it using cable, the way you were saying. So Mac gives automatic support for iPhone and supply and Android if you go and install Chrome and Android, then there's an option called developer tools. Enable developer tools, remote debugging. So if you enable that from Android from cable, you can do that. Otherwise, as long as you're locally connected to your debugging But the main problem with Safari and debugging using USB is that only the later versions are supporting it. The older versions of Safari and WebKit, especially when you're trying to debug on mobile, it's not possible using the demo debugging. That's fine. Who cares about it? That's where Windows actually quite useful. And also more than that, the touch, inspect the touch element and other things. Adobe H2s have built something on this board that is known as as inspect. Shadow. Shadow. That's on WinRid. Shadow runs on WinRid. I haven't tried WinRid, so I can't talk about it. We have to open up. Yeah. It's fun. Shadow is good. We set up a server. What is it? It's simple like end users. It's like you have a client and he is remotely working and you are... Right. So I have to like configure five or four things like that? So my guess is yes. Yes, you would have to... So... Yes. So where is the code? We just install on the client side. That's your code. Yeah, but that listens on some network code, right? So it's not listening. It's connecting too. So if you have outgoing ports, then it's a problem. Yes. Is the code somewhere... Yeah, yeah, yeah. It's open source and... So yeah, it's on GitHub. Actually, I had some slides. So yeah, that's the... The first one is the... Where the whole tool is available. This thing is the one where... I mean, it's basically a tool to allow your local server to be accessible. So you know about... What is it called? Local. Local. Yeah. So it's something like that written in Golang or Golang, whatever. And that is used in DevMirror. Yeah, the fourth link exactly points out to what I said. You have to install Chrome on Android and then... This is the fourth link I think they have. Yes, yes, yes, yes. So this is what it... I mean, the option it uses is in the user end. But you see, the user may be behind the NAT or whatever. So you have to basically make that server accessible over internet. Only DevMirror is the app I have. It's fully for everybody. No, not for everybody. But it allows you to access like... What is happening? I have this... Yeah. And it goes into the spectrum. Okay. I agree with that one. So yeah, that's what I wanted to talk about. Okay, guys. Thank you. That was the last flash talk. So I would like to thank again very much Pradeep and Microsoft Accelerator for asking us today and for the awesome coffee machine. Thanks to the guys from Hasgeek who are filming all the presentations. Thanks to them that will be online soon. And yeah, I'm sorry we ran a little bit late. But I think all of these talks were awesome. So it was worth it. And please, if you have some more time, stay around. Let's network. Let's chat together. I'd love to catch up with all of you. Thank you. Thank you. Thank you for the analysis. Thank you. Thank you.