 So good afternoon. I'm Tristan Nito. I'm president and founder of a non-profit organization called Mozzarella Europe. You may have heard about our main product called Mozzarella Firefox. And I'm here with Anthony, Anthony Enrico, here on stage, who is a web developer and open source contributor. He has the history of contributing to what's the name of this browser again. It's a fruit company. Can't remember, anyway. So he used to contribute to Safari, but he's seen the light. And he came in contributing to Firefox now. But I like him, anyway. So apologies for this presentation, which is quite a mess. I was told yesterday, I think around 7, that there was a slot available. And it would be nice to have a Firefox presentation. And so I had literally no slides, nothing to show. And I would like to thank Anthony for joining me. We had room service lasagna in my room. And so we created this presentation yesterday evening instead of going to the beer event. And so it's kind of a big sacrifice. So I know, we did have a bottle of wine, anyway. So no beer, but wine instead. But it was not really a party. Well, I'm going to talk to you about mostly three things. The one is the cloud phenomenon and what's going on. How Firefox is changing in this regard with Firefox 4. And we'll also talk about the browser as a platform. And this will include demonstrations by Anthony. I was actually very pleasantly surprised this morning by Eben Moglin's talk. Who in this room has attended Eben Moglin's talk this morning? Raise your hand. Well, not enough people, let me tell you. Well, it's better than nothing. Eben, who's an amazing guy, actually had a very nice words for Firefox. That was cool. But also mostly he had a discussion about privacy and network centralization, which is very close to my heart. And so it was a pleasure to hear Eben discuss these, in my opinion, very important issues. So whether we want or not, the cloud paradigm is taking over information technology. Everything, it's the big trend these decades of moving to the cloud. And I don't think we can stop it. But if we cannot stop it, how can we make sure that we as users, as free software developers and citizens of the internet, how can we ensure that we have the maximum control over what's going on? So this is one thing I want you to keep in mind during this discussion today. The cloud is happening, but Firefox is the product that we, Mozilla, as an organization, are producing in order to remain in control as much as possible with our data and our future. So while the cloud is taking over IT, the browser needs to evolve. Like remember a decade ago, the browser basically was something to display a web page, a static web page like a Wikipedia web page. I'm not dismissing Wikipedia in any way, but it's a very static document that evolves maybe a couple of times a day or a month, but it's a very static document. Now we're talking about web applications. How many of you use a web mail with your hand? All right. So many of you know what a web application is firsthand. So a web application is not a document anymore. I mean, there is a lot of things going on, downloading new emails, writing, composing emails, and stuff like that. The page itself is evolving in real time. The browser has to evolve in this regard. An issue the browser had was it had limited capabilities as a development platform. I mean, it was meant to display static web pages. Now that we're moving to web apps, how does it work? Many things have to be changed. And this is what we're going to see today. Privacy and centralization, how we cope with this. And also as the world is going mobile, as many of us have now things like smartphones, cell phones, we carry around, which in turn fuels the interest for the cloud itself. I mean, I don't want my data to be on my computer or at home or on my cell phone. Basically, I want data to be in the cloud and I can access it from any device I want. This is what fuels the interest for cloud computing. So there is good to with cloud computing, but this means you also need a mobile web browser that you can trust. So I'll start by discussing Firefox 4 in terms of user interface and user-facing features. What we have, what we have done with Firefox 4, things that are new. One thing that we have is a tab on top. So the tabs now are here. These are a screenshot from a Windows version. I'll show you on Linux how we chose. With generally a new theme, new look and feel, the location bar, which makes sense, is now closer to the content because actually it relates to the content. You will see in Windows and soon on Linux, it's disabled by default, but we can fix that. You will see that there is no more menu bar. So overall, the idea is to limit the importance of the Chrome real estate on the screen. Chrome being not only a competing browser, but historically, the Chrome is the name of the user in the face of the browser. Now it's confusing that they took this as a product name, but in the browser vendor jargon, this is what you call the Chrome, and this too, is the piece of the browser that you see, which is not the content. So we wanted to reduce this to the maximum. So no menu bar and shaving a pixel here and there in order to have maximum space on the screen for the content or the web applications. And tabs on top is one way of achieving this. Another thing we have is a feature called Switch to Tab. As you have more and more tabs open, because I don't know if you're like me, but basically the browser is the piece of software that I run like 24-7. It's where my life is. And so I have many, many tabs open. And when I want to look for something, when I want to access some information, because the location bar in Firefox is smart, this is what we call the awesome bar, you start, you open a new tab, start typing what you're looking for. And the suggestions here, if you start typing wiki, it suggests wikipedia.com, which is .com, come on. Well, anyway. Or it could suggest, in this case, which is new in Firefox 4, you already have a Wikipedia tab open. So it suggests that you go to the existing tab, which has Wikipedia instead of opening yet another Wikipedia tab. So it prevents you, in the end, when you start cleaning up the mess in your tabs from closing like 20 Wikipedia tabs that were open at the same time, which doesn't make sense. So this is one nice feature, which is so Switch to Tab. We are suggesting to move to the tab, which is already open instead of reopening a new tab. And the Firefox button you see there on the top left corner is basically a menu, well, a list of options. If you're not displaying the menu, then you have that. Because we've been studying very thoroughly with our user experience people, what are the items that are actually used in the browser? And we've seen that many of them are not used. And so we decided to remove them and put them in this Firefox button so that they are not in the way and they save space for the content. App tabs is pretty neat. And actually, you know what? I'm going to demo it for you. I don't know where I stand. OK, it looks like the network is pretty limited. Anyway, Twitter is something I use pretty often. So what I'm going to do is right-click on it. Oh, it's sorry. That's the French version. Fail. I can click there. No, that's OK. Well, in English, you would read Pina's app tab. And look at my Twitter tab. It's going to switch to the left. There you go. And now it's here. But it's a tiny icon. Doesn't take a lot of space in a tab bar. And if I open new tabs here, you see that my Twitter is still here. So it stays there. So you can do that, for example, this is my blog. Maybe it's a place or maybe it's Gmail or whatever. Your webmail, you want to access it very often. And instead of having it lost in a sea of tabs, you right-click on it and you say Pina's app tab. And there it goes. It's here. So it takes tiny space. And it's very, very efficient to save space for the web apps you use often, as opposed to random tabs. What else did I want to show? Yes. Another one is Panorama. Panorama is a way to manage your tabs. I wish I could show it to you, but because I don't have a good internet connection, it's not going to be very interesting. But basically, Panorama is a button that you click on the top right corner of user interface. And it enables you to put together groups of tabs. So in this case, I was writing an article about Marshall McLuhan, a famous Canadian, on the communication theory. And so I've put all my tabs about him together in a group and all my work tabs on the left. And I can switch from one group to the other. So it makes organizing my tabs much easier. And also because it's visual and it's 2D, I have the notion of where I can find easily my tabs instead of having them listed on the tab bar. So it's pretty powerful and very useful. Something else we've been working on during the Firefox 4 cycle is performance. And performance, believe it or not, is actually extremely complex as a topic, including very different topics like startup time. We've made a lot of effort in streamlining the startup time, reducing the startup time so that the startup process is much faster. It doesn't matter much to advanced users because Firefox is always launched, like 24.7 for them. But for less advanced users that tend to watch one page and then close the program and go back to email and then relaunching Firefox like an hour later or so, this is important to them. So we've been working on this startup time quite a bit. The JavaScript engine, we have a new generation of a JavaScript engine which is called JagerMonkey. I'll detail more about the performance. We've been working on a very difficult topic, which is called hardware acceleration. So I mentioned here that your mileage may vary because hardware acceleration basically is using your GPU, basically your graphical processor on your graphics card, leveraging it so that it helps the browser do complex computation about page layouts, displaying text on the screen, or 3D, or decoding videos, and stuff like that. The GPU is an unused part of your computer that is extremely powerful. On the other hand, it is very complex and between Firefox and the GPU stands a very complex bit of software which is the device driver. So while hardware acceleration works pretty well in Windows and more precisely in recent version of Windows, it's not easy to make it work on the Mac. And it's even harder on Linux because there is such a difference of quality between certain drivers and other drivers on Linux, graphical drivers. I won't get into the mess of the NVIDIA proprietary drivers versus open drivers and stuff like that. But basically, we're dragged into this and it's complicated. So in some cases, if you're lucky enough, if your drivers are high quality, then we can leverage them. And you will see a boost in terms of performance. But if we are not sure that the drivers are bug-free enough, then with disabled hardware acceleration on Linux, and then you'll see a good Firefox 4, but not blazingly fast on the pieces of rendering that are impacted by hardware acceleration. So it's a very complicated topic. Just for the record, Microsoft is using hardware acceleration. We've been fighting on who had the first product to do that. I claim that Mozilla produced prototypes of Firefox builds earlier than Microsoft. We tried to do that on all platforms. And Microsoft say, yeah, we can do that only on Vista and 7. But XP, yeah, it's the last battle. Actually, if I'm right, we're able to do hardware acceleration also on XP. It's just they don't try hard enough. Well, of course there. The bottom line at Microsoft is about selling more version of Vista and mostly 7. So yeah, they don't care much about XP. Tons of optimizations have been going on in terms of performance. I won't get into details, but we call them compartments, retain layers, and many others. Basically, it's aggressive caching and better management of the code base. And one final thing is streamlining the experience. And this is kind of a tricky thing, but I'll save it for later. Let's start about the JavaScript Yagamonki engine. So these are graphs. These are benchmarks. This is the benchmark called V8Bench, produced by Google. So in red here, this is Safari. So basically, we take the Safari JavaScript engine called Nitro, and we run the test regularly. We take their nightly builds, isolate their JavaScript engine, and run test. We run the benchmark. And it gives this line. We do the same with the Google V8 JavaScript engine, which is getting slightly better sometimes, or worse. And we do that with a Firefox Yagamonki JavaScript engine. As we can see, we make a lot of progress. Mid-September, the smaller is better, lower is better. So we've been beating regularly Safari since then, and we're approaching Google's engine on Google's benchmark, which we can assume their benchmark is favorable for their own engine. That's how people build Benchmark. And it's last year. No, it's just December and January, and it's even better now. OK, so we're even better now. This is Yagamonki, our JavaScript engine, now running on SunSpider, which is Apple's benchmark. And so we're better than both Safari and Chrome in terms of JavaScript on Apple's benchmark. And we also have our own benchmark, where we beat everyone, of course, because it's our benchmark. And we pretend, and I think we are right, but yeah, who knows, that our benchmark is better than their benchmark. Right, I wouldn't get into that. So JavaScript, as you can see, we've made huge progress in terms of JavaScript over time. So we're highly competitive, even better than others, we're very close. So we've closed the gap with regards to JavaScript execution. A JavaScript execution is just part of the performance issue. But if you have very complex applications, it makes a difference. We've made already very significant progress between Firefox 3, 5, and 3.6, was it? Do you remember, Anthony, with a better JavaScript engine? And it made a big difference for users that were running Gmail. Like, basically, when you click on the link, it changes immediately as opposed to having to wait like half a second. And half a second for the human being, you feel like you're waiting. But if it's like under a tenth of a second for the software to react, then you have the impression it's instantaneous. And so we went under that tenth of a second threshold. And it really made a difference for using Gmail. Now, in a very, very different topic, I'm going to talk about performance, but mostly the impression of performance. Because let me go back there. When we go from here to there, frankly, users don't see a difference. We've been working really hard to go from here to there, really hard, and it's paying off. But people, they see nothing. It was fast before, and it's even faster after. But so little, and it was so fast before, they just cannot notice it. On the other hand, in the user interface, there are things, when you start making things differently, people see a lot of change. But actually, product is not faster, but it gives the impression to be faster. I've listed a few examples. Let's start for this last one. You add a new add-on in Firefox, and instead of saying you have to restart Firefox, it says that's OK. You can use the add-on now. So you've saved time by not exiting Firefox and re-entering Firefox. You can use it now. So it means a lot of work behind the scenes, but it really changes the way you use Firefox install and then install an add-on. Reloading old tabs, you have the choice of reloading or not the old tabs, and if you reload them, we're basically loading a couple of them that are visible. And all the others, they are ready, but when you hit the tab button, then they start reloading. That means that when you restart Firefox, for some reason, it restarts very, very quickly. And also, when you start it, that's number one item, it is not saying, OK, hold on. I've got to make sure that you have the latest add-ons for this version. So you do not see a pop-up that says, hold on, I'm going to check the add-ons. What we've done is we've checked the add-ons in the background during your last session. And if new add-ons are ready, then we install them then at startup, which is unnoticeable, and then you go. So it's changing the product so that you don't have added boxes, dialog boxes, and things that make you feel like it's painful to use it or it's not responding the way you want. And it's giving you the impression that it's actually much faster. It's actually really more pleasant to use than actually faster. On a very different topic, something we've done is raising the bar on privacy. We're very happy at Mozilla to see that privacy is actually becoming a topic of interest with the European Commission, with the government of the United States, and also browser vendor that start to feel the heat, because they are concerned there will be regulation from authorities. So this, we've been fighting for privacy for a while. There are extensions such as TACO and Better Privacy that have been available for a few years already. That basically puts cookies in Firefox. And these cookies that are set by advertising networks, when an advertising network sees that cookie on your computer, then they are not going to track you. That's their promise. Whether people obey their promises is a different story, and I won't get into that. But because the advertising industry is concerned that they will get regulated, they have put this mechanism into place, and they offer you to put these cookies so you're not tracked. Now, these cookies could actually disappear. And so these extensions make sure these cookies stay in place. So even if they're removed, they're put back into place, and these cookies say, no, I don't want to be tracked. For each and every advertising network, I think there are like 74 of these advertising networks that have that. Other extensions such as Adblock Plus and NoScript for the advanced users are also available for now seeing no advertising, no scripting. Personally, I tend to also use FlashBlock, that blocks Flash, which I highly recommend. Although we have to recognize that these two plus FlashBlock are really extensions that are for the advanced user, because, well, sometimes the website you're visiting doesn't work exactly like it should be because you're basically you've removed stuff from it through these extensions. So unfortunately, I would not recommend them for ordinary users that don't feel like debugging websites that don't work well because of these extensions, although they are very, very efficient. We're seeing companies such as Google and Microsoft have recently announced something similar to the extensions that we have for several years. It's good. In the case of Microsoft, they've built this into the product because their extension mechanism is very crappy. But by default, there is a kind of a blacklist of ad networks. And these blacklists are empty by default. So yeah, they have a do not track feature except that you may not use it. Right. Google has announced they are doing something similar there within Chrome. But they're still at level number one. What's new in Firefox 4 is a very simple feature called the do not track HTTP header. So yeah, I think I'm going to show it to you. It's not going to work. It's not going to be to 10. Oh, it's OK, right. So I'm not going to show it to you because that would mean I need to run another version of Firefox, which is a nightly build. But I've seen it on my other machine. So that's why I thought I would show it to you. It is in Firefox, though it's going to be in the next beta, not in the one that was just released. And one final thing we're doing on the privacy front is it's a service called Firefox Sync. Who has heard what Firefox Sync is? Raise your hand, please. All right, I still have to explain it. Sorry for bothering me with that. 15 minutes left. I need to hurry up because basically it's a service that backs up all your browser history on the server and your bookmarks and your passwords. Now, these are highly sensitive informations. So the way we do it at Mozilla is everything is encrypted by Firefox on the client side with a key that only you have. And it's sent on the Mozilla server. Means that Mozilla cannot decrypt it and read it and understand what is your history and what are your passwords. Other browser vendors offer similar services, although they do not offer encryption. Because for them, tracking where you've been is highly valuable. Data mining, like Eben Moglin explained this morning, is highly valuable for the bottom line of these organizations. But for us, being an on-profit organization, caring about you, we do encryption on the client side. And what we see in our servers is only encrypted and unusual data that we cannot data mine. That's one thing. And the second thing is that our server is open source. It's free software. You can download the source code for it and run it on your own server. So we're also addressing the issue of centralization of this. You can run your own server of sync. And so even if you know it's encrypted, even if we're good people, you may not trust us and you may want to run this on your own server and that will be fine. And we're totally OK with that. We'll still need to run a centralized service because it's more simple for users. And finally, Firefox 4 for mobile, Firefox Sync is very useful in order to synchronize your history so you can reuse it on your smartphone. Just typing a few letters on this because the keyboard is crappy. You will be able to revisit tabs that are open somewhere on your other computer. Firefox 4 on mobile is going to be really soon. It will be running on Memo Amigo and Android. I'm running Android. Yes? That's a small question. How much RAM is required for that? How much RAM is required? I don't have the specs on top of my head. But I run it on a pretty good Android 2.2 phone. It works well. But this is a good machine. So 760 may. How long is it going to take in so long? Yes. And what's important, it's the same engine as Firefox 4. So if you can run it on Firefox 4 desktop, you can run your application on these things. Switching over. He wants the microphone. What else? Hey, is it OK? Yeah. I have to say about Firefox sync. When I joined Mozilla, I was still running Safari. Yeah. I did it for three weeks because I had an iPhone. And I switched when I discovered Firefox Home, which is just a sync client for the iPhone. And when I'm in the subway or in a car, I can check my bookmarks. I can check all pages. And that's when I switch back to Firefox. So really cool. OK. OK, so I'm going to talk about web features available in Firefox 4, but most importantly, in other browsers and in their latest versions. So I guess you've seen the HTML5 logo that the W3C is promoting. So HTML5, it's an umbrella word to put everything that's web inside it. And so I'm not going to go into all the details because I don't have the time. Thank you, Tristan. But it's about new web features and new design features and having powerful JavaScript engines in the browser, having SVG as the first class technology. So SVG is about scalable graphics. So highly important on mobile. It's about having access to the desktop, having access to a web page when it's offline. And so there's really a lot of technology in there. So this little demo, I'm not sure you can see exactly, but there's a gradient, a radial gradient, like it's light orange in the center, and it's going red over there. So that's done with CSS3. There's no image used. On the bottom, all the images are, in fact, videos. So I don't know if I do that, if you can hear the sound. But so it's playing. And when I click that, it's opening with a transition, a rotation. It's scaling up. And so that's really not going to say easy to do, but that's something that's really easier than before to do. And by the way, I don't know if you've noticed, but I'm running a Firefox full screen. So on the Mac, it's really new. And that's cool. Just Tristan was talking about panorama. That's the way you use it. I have all my demos here. And OK, thanks. I have all my demos on the right. And I have some links on the left for FOS demo. And I can access, as you can see, access the app tab on Twitter, on Gmail, or whatever. Again, next one. So let me refresh this. So this one is to showcase how we can store data in the browser and we can store code in the browser. So if you're on a mobile, you want to run an application. If it's native or web, you want access to it if you have access to the network or not. So there's a feature in HTML5 where you can store the code inside the browser. So next time you launch it, it's not going to go on the network. And so you can do a to-do application really quickly and access it everywhere. And you can also store data. So this demo is storing a list of all the cities in the US and the zip code associated to that. And so even if I have a, I don't have a good Wi-Fi here, when I'm going to search for this one, it should work. And it's not. Oh, yeah. I've been in the street. No, I've been in, I've been in early days there and it's in Florida. OK, let me try another one. Yeah. And so as you can see, it listed everything. So you see Florida, FL. So you can store it. There's two kinds of storage, a really quick one and simple one with a key and values. And you get also, in this demo, it's using index DB, a more complex database system where you can do queries and really, really cool on mobile devices. But if you want to do a web mail, I know Gmail is already using some of this stuff to store the emails so that you get a list when you launch it real fast. And OK, this one. Yeah, it's also important to move the browser out of the web and access the desktop and some stuff like that. So if I take this picture over here, you see I can drop it like I don't need to go into a file picker and search for my file. And when I'm going to drop it with a powerful JavaScript engine, I can go into this image, take the data in it, extract the exit data because that's what you get in two images. And with that, I can see where the picture has been taken, what is the camera, what else, the data in time, stuff like that. And so when you're on the web, you can match this with a service called Google Maps. And I just dropped it. I never went to a server. I'm just doing this on my machine, computing the data into the image. And you can see all the exit data in there. And especially the GPS latitude. And then I'm using it to insert a Google Map on the place where the photo was taken. And I don't have a server. I just have a Wi-Fi connection. So that's really cool. This one is really cool also. The story behind it is very cool. I should have configured the screen before. Anyway, so there's an audio tag into HTML5. You just put the file in the markup. You can play it. You get the user interface that you're seeing over there. And it's really easy to insert audio files now. But some people said it's not enough. We want access to the sound that is playing. And we want to play with that. So I'm going to run it. And you don't need to read the music. That's not the point. What you can see here is the data from the sound that is playing in the background. So that's something we couldn't do before. It's not really useful. So this way makes more sense. And you can do a lot of violations. But you can also modify the sound. If I don't know if you ever did, but anyway. So you can modify the sound on real time. You can compute a four-year transformation on top of it. Anything. And you can even do 3D that goes with the sound. So the cool thing about that, and I'm going to switch to another one, because otherwise you're not going to listen to me. The cool story about that is that the guys who did that. So the names are on top of it. They said, we want this. The W3C was not going to put it into a specification. And so they decided to come to Mozilla and said, OK. We have an ID. We want access to the sound. And we're going to produce the patch and put that into Firefox. And so they did the code to make it available. They did the specification that now is going to be a standard. Of course, there's discussion with other groups, et cetera. They did the demo I just showed you. And they also did another one that I'm going to show you in a minute. And the really cool stuff is that except for making sure the code is secure and not performant enough, there was no Mozilla employee involved in the creation of this stuff. So that's something you're not going to find in other open source projects, like the one in the other one in Mountain View. And so this one, oh, you're not going to see anything. Nice. Yeah. That's bad. Do you have control over the? No? The sun. OK. The sun? Yeah, in Belgium. No, no, no, no, no, no, no. OK, anyway, I'm going to run it. Ah, yeah, shit. No, but it's not enough. Anyway, so this is using WebGL. So WebGL is like OpenGL accessed on the web. And so there's an audio file that's running the whole animation you're seeing. It's not a video. It's an animation. It's 3D computed on my laptop in real time. So the way to prove that to you, if the network wants to play with us, OK, OK, so it's going to go into a city. And you'll see in real time some flicker photos with the first dem tag in it. They should appear right now. Yeah, in the background. The Wi-Fi is not good enough to download the images on. Sorry. But trust me, it's really computing on getting the flicker photos. And another thing, about four minutes, 30. Now the, ah, you can't see it. The buildings over there, they are playing at the same, with the music. I don't know if you, it's really good on my screen. Audio API for visualization of the sound? Yeah. So the buildings are, lights are moving at the same pace than the music. And you can also insert videos inside this 3D animation. So this is a big bug bunny, I think. And so again, this was done by people who like music and wanted better audio access. And all this, computed with a really cool JavaScript engine, 3D with WebGL and all that stuff. Is it OK on time? I have a question. Yes? Also, I would like to have the same functionality. Sorry, I can't. I would like to have the same functionality, namely create audio on one time. And I saw something, it was mentioned, in the, it's the, you know, device specification, actually device, they introduce devices. What devices? I don't know, devices, but also audio devices. I know that the Marshella has created a bit of audio API, but it's also mentioned, Marshella is not implemented yet, but it's also mentioned in HTML5. So I'm not sure what you're asking exactly. But HTML5 is at the same time a specification and a bunch of other stuff that. I just have a question here. Marshella has already an audio API. Yes, that's what, this was, yeah. Also, so it has implemented matter. Chrome as an audio API too? It's possible, it would be possible to build the same functionality into the HTML5. How am I wrong? It's a device. But the device API is different. Yeah, there's a device API. There's a lot of work in the W3T and other standards body to get access to audio, like I've just shown, to get access to the webcam, to get access to the microphone, because that's not part of this. So microphone and webcam, this is part of the device API that's worked in the work group or something like that. We should probably take it offline, because we don't have time for many questions. Any other questions? I promise you can grab Anthony on the side. Yes? Yeah, not far from synced. There's been talks about creating add-ons, synced integration of add-ons, because that's the focus. Where is that synced with this guy? The question is, can we sync with Firefox Sync? Can we sync add-ons from one version of Firefox to the other? The answer is not yet right now. Although we're considering we're working on it. Now, what's keeping us busy is shipping Firefox 4. So all the energy right now is on Firefox 4. And we'll see once it's shipped. We'll see what we can do about extensions. And extensions, I think, can already sync their preferences using Sync if they choose to do it. So you still have to install the add-on on your new computer, but it will get the preferences of this extension if the extension is compatible with it. If you had to convince somebody who had left Firefox to use Chrome or Chromium to come back to Firefox, what would be your kind of short-killer argument if you have one? But beyond the ebb and model and its freedom and you're not evil, even in that context? Well, so if I have to, I think both Firefox and Chrome are very good browsers. And I should repeat the question. So yes, why should I use Firefox instead of Chrome? That's the question. And the answer is, well, you should use Firefox because it's made by us. We're a nonprofit organization. And our business is not coming from data mining user data. But what if you're a selfish person and you're a stupid person you don't care about that? Well, you know, I don't know. It's nicer. The logo is nicer. OK, if you're an asshole, that's all the answer. I'm getting you. I'm not technical, but I mean. She's blonde. Thanks. Fank blonde. I work at Mozilla, but I'm non-technical. And the things that I like is a lot of work that they've done into the UI. So the features that were showed like panorama, I actually can visualize my tabs. I have many windows, many tabs open. I know it's clear. I have a clear visualization. I also have an iPhone. I got Firefox home on it. I got to play with an Android. And when I go back to the US next week, I'm switching to Android phone because I was able to play with sync and really get that same experience no matter what type of device I used. So there's a lot of different features. It's faster. It's cleaner. And also you can bring it with you no matter what you use. And just being able to have your Firefox on the go is so important. When I use another computer and it's not my Firefox, I'm really lost. I'm used to organize my tabs. Everything the way I like it. And you can do it now with Firefox 4 and the other options. Thank you. And I'd like to know if you have any limited hardware and serialization systems for future use? So is there any limitation about hardware acceleration, about the brand of the GPU you're all using? So if someone wants to answer that from Modina, so. I'm here with the code media. Yeah. So we're kind of working on this right now. You're asking about Linux, right? The question is exclusively about Linux. All right, so then we are right now, I think we only enabled NVIDIA proprietary driver because this is the only one that doesn't crash. But we are, so this is the sad note, right? Like that's not the story we'd like to hear. But the positive story is that when we started sending dumps of the crashes, we started getting responses from the XORC community much faster than from the vendors. So basically, ATI did not respond at all while the open source ATI driver started sending patches like two days later. So even if we're starting from a really bad position, we believe that pretty soon we'll be able to enable at least a Radeon driver. Probably not sure about Navoo. What's the full name? Navoo. They are also working on this, but they have kind of a complex issue that they're trying to resolve. I think the work is progressing and we'll be enabling things as we go once we see the drivers working. But it'll take some time to upstream to distributions as well, right? So it's not going to happen tomorrow. So that's the status. There's a full test suite coming with a WebGL so that's going to improve the whole situation on Linux, not only for Firefox. All right, time is up. Sorry, we couldn't take all the questions. Thank you very much.