So explain how like the engine intersects with the browser and how they work together and what that actually means.

Yeah, so the engine, you can kind of think it is everything that's inside the frame.

And say if you go to a website, you type a URL into your address bar.

And if you go to any site out there, but let's say you go to Google Docs or something, then now within that frame, that is rendering the code that Google Docs has built or Maps or anything like that.

The browser then also encompasses things that are around that frame as well.

So things like the ability to do split tab, vertical tabs, the ability to look at your history, save your passwords, a VPN, which we recently launched.

And the...

So all these experiences kind of in companies, private organizations, and then you come into the Mozilla foundation, the corporation, like what sparked that change?

So how are you playing in this map now?

When there are platform shifts, they're often very disruptive.

And it's not disruptive in a bad way.

It's just that it opens up new expectations and capabilities for users that then want new ways to do things.

So when you look at the internet, say over the last 25 years, there have been platform shifts for the internet as we know it.

And so one big one was mobile 15 years ago.

And when mobile emerged, there were a lot of changes in how people interact with internet applications.

So I'm curious to know how you're thinking about headless or being useful when people still require your product, but they might not be going to your product first.

So do you want to maybe touch on the behind the scenes infrastructure and just explain the differences between Firefox VPN and Mozilla VPN? Because I know that can cause some confusion for people.

Yeah.

So with the terminology, I think there's a lot of debate on like, what is a VPN like mean? And there is like a very like technical understanding of like, this is what a VPN means.

And that's like historical when people were using Arden, like enterprise security use cases and things like that is somewhere started.

But then in other ways, like the term has been a little bit more genericized to say like, I want it from more of like a privacy angle.

And so we have products that serve both needs.

One is Mozilla VPN and one is Firefox VPN.

Are you guys struggling with that behind the scenes? Is it hard to communicate to users the realistic protection that they're being offered while still assuring them that they are getting real protection? How do you walk that line from a marketing