 So I measured my needs between a community and another one. So many things, especially in Italy. In Italy, so the Italian, find me. But let's start to talk about the station because we are here for that reason. Firefox is famous for extension. I think my memory, the most important feature for Firefox was disruptive. It was the tab dosing, for example. So as we can see, as I said before, Firefox is famous for extensions because extension itself, feature of extension, sometimes became feature of Firefox itself. So this one of the example, one of the example, why an extension platform, ecosystem as you prefer, are important in Firefox. But I said that because it's true. Firefox is the most conservative browser in the market now because there is not only like the other competitors that you can add only a button in that bar or improve the URL bar because you can change many other things like the download manager behind you, teams, as I said, or the features. So actually it's the most... because it's about browser, ever. Which is true. Not because I am on Amazon, but it's true. And another example, are the why addons are important also from, let's say, Mozilla itself. I said we have the faster system of don'ts. As I said, the don'ts maybe will be an addon for Firefox itself. Mozilla try to implement features as addons because that way we can try to disable, we can remove it, we can... we can ship faster feature also as call features as developer tools because not only all the people is a developer. So maybe I don't need it. So the result of a pilot for me is one of the best new project because it's the first time that I see that you can try new features and you can leave a feedback because usually when users accept or rub up something else, you want to join the better program but you cannot have a service sometimes. I cannot say what's going on, what I liked, etc. So these are three examples about Mozilla, why extension, I'm important in Firefox. And there are also a few data that maybe I'm interested because a developer, I want to see that my extension is used because I'm a volunteer. They use me full time. So we have a few data from the M itself, the M is the addon that Mozilla the top website. We have the 40% of Firefox use addons. There are millions of users of Firefox so there are millions of people that can use my addons. Many addons now but there's a number that after web extension is growing every month. There are many extension developers but there's not so many to users on emu. We have a customer of our extension. But this was before. This was a problem. I'm feeling this wrong because there was a problem that the new technology or the technology of Firefox itself pulled with respect to the new technology of today. And XML today is not used anymore. Use JSON. Okay, but the Firefox interface itself is done with XU. It's XML to build interface and we want to do an extension with that framework. We need to act with that kind of things. We use CSS etc. Next, we cannot use the normal to standard we already use. So we have local storage inside in Firefox and many different names, different poverty, blah, blah, blah. So there is another framework. We are not developed. We need to learn new stuff and when new stuff can be cool but sometimes can be very boring and sometimes can be very difficult and I tried so many times to develop an extension. We don't need these kind of things. But actually we have completely changed the actual status of the ecosystem because for developers like us with only HTML, CSS and JavaScript standard, I say standard we can do an extension. And it was animated but okay. As I said, standard technology. We love standards. There are many tracks for them for standards. And next we have technical things because we say it's a new technology with a new documentation. Not something that's circular flow. I cannot do anything. But there are many things about circular flow because web extension is the Chrome API. So we can find with Chrome, K-Want, already ready with code. So we have the poverty with Chrome extension API. But they say for many things. So we find the documentation on Chrome but that's in the end because we want also our documentation. But there is that's another thing that I said we denied. We have electrolysis. With data work code we support electrolysis. With web extension we don't care because I already supported. We next have support for fast forward void. Fast forward void as I know we have a web browser that support extensions. So we can add block on our fast forward void. So only the desktop bus is not enough we can also add mobile. We have also sandboxing that is improving. But the good part for us because there was a time when we have to develop an extension for Chrome. An extension for Firefox. As a time with Windows, with DDL hell and many other bad things. We can add one code that is everywhere. One on Chrome Opera is also working on Edge and that's also working on Kitty Webkit. I already made a list there thinking about it. So for us we can have not only Firefox but also a huge marketplace. But the reason I put it when it appeared to them all because for developers it's amazing because it works. I started with a station for Firefox but it works like a charm on Chrome. So this is practically out of the box you can have all these kind of things you can also try at Chrome extension probably because the party is not complete actually it works on Firefox. So that is the actual status of the party and I want to talk about any VR because I have no time, I'm Italian but I can talk so much but for you it's not good. There are many VRs and I love the first part I am a developer I am like a kid at the Christmas waiting for Santa Claus looking out the door when he's coming because I'm ready for they have tools API because I want to do developer tools too and it's working. They are working on it but this API they are working on some of them are already completed there is native messaging they are amazing, they are already available with the ticket on backzilla so you can track everything as question because the other things are nice people, they are also behind these people they can help with all the problems. So let's talk about the station. It's like with Chrome we have these kind of things and you can tell is not so much different from another web project, we have files a little bit of files but let's work on these kind of things for a web developer remember like a package manager unfortunately we do so many times with package manager we have to work in many languages but the important part of this and I want to talk of the rest is the counter script usually the main extension only changes, they have you in a page on a website this is the main of our extension and that is very simple Gaze Monkey became famous for this kind of things and now we can do it to explain the URL and the fact to read it it's automatic we don't need to code it's already there so try an example to move a Gaze Monkey script as a web station and only to write this file so you can find it's very simple to create a station but there are many other things because counter script is a script they run in a web page there is lots of account scripts because they want to communicate two different pages and I frame in another page what can I do? I can use a script to specify the manifest auto-loaded from Firefox itself to do stuff so these kind of things as I said the results of counter scripts very simple I see I can write an extension an hour now because I can test the benefits of Firefox with the scratchpad and the rest the manifest and plot it on M it is one of the problems as I said Firefox is a most custom it's a browser but in Chrome the only thing you can add is that button and sometimes Chrome is automatic so you cannot specify in the manifest it's automatic added but in Firefox this doesn't happen actually in the interface you can add a button that opens up the pop menu that is on a frame and you can do a menu like as a web developer usually and it's one of the things that I review now these are already available because I was forgetting these kind of things because we love privacy and you can specify what files my extension can access so I have to specify the resources of the JavaScript file as it says specify the manifest itself so cannot access as to strange files security so I want to add this part because we want to plot somewhere extension we need someone that look at the extension and this starts from the HEMO team itself as we can say there is a very good because when you use Chrome the commercial is very ugly you have to fight for the account blah blah blah the extension is released automatically in an hour you can say not so much because you can release a bug and no one decides so much on HEMO you have volunteers they are to review your code they can leave you an email with a suggestion or to improve your code but it's the best thing to do they can say experience is very important because I input myself as a developer but that's the code and we need the reviewers so you cannot apply for these kind of roles and this starts usually in one day it depends from the time the QX set you cannot solve your extension of code with an email you can say thank you for contribution Chrome you don't get anything so we love contributor and the roadmap was also animated is available from Firefox first issue so you cannot already develop and publish on HEMO you have the SDK for every session that I do there is a way to move an old extension in the new way because it's more simple the roadmap is planning to activate only a web extension that will be released in Firefox 53 on HEMO and they are planning for the hand of the year to stop to release on HEMO extension with the old way only web extension there is actually API so you don't want to do many other things so we want participant API they are planning, they are studying etc there is also the side bar new teams done as web extension they are working on it and there is also a project to experiment creating API outside Firefox so you really want an API experimenting without changing Firefox itself and you can do it, it's a project already available and for people that love code you can find a new API there is an example after the 30 example available on the tab so you can open Firefox and try it and then you can find all the files etc for the API available but there is also some of them that are documented as tutorial on MGM so I want to know I can put everything on MGM why I can try extension that is Firefox also the state bar because it was available from the 45 you have only to open about the debugging page and use another program that way we have a watcher of the files so when I change the javascript file CSS blah blah blah they are already loaded without anything that we cannot swap the old button to force sometimes there is JSON it's not a product you can also have the bug to open to the bug in the user for the background skips because they are a little bit advanced but we are developers developers who love the command line so there are lots of tools for us the first one is the most famous from the demo team itself is a command line to do everything without using the interface but also do many other things like simple testing packaging validation many other things it is very well documented on the tab so you can download with a problem etc this is my little skip because I started to develop when there was change the server is a little bit a script that package an extension and check for Chrome etc but now it's not so much required and this one I have done because even developer I want to see static of my users how many people use my extension Chrome web store is ugly again AMO is fantastic the rest API Chrome don't have rest API to access information of my extension to scrap HTML and Python is very good to scratch to scrape HTML so I have done a little scripts that scratch this data and create graphs of the marketplace so I run with the Chrome every day I can see the status between both of the marketplace and one of the last news is this there is the new developer app on AMO you can have an example Chrome extension many other things already on AMO there is a dance for the people that get it but in closing because I think it was very fast probably have time to show a demo there is also the standard in progress I don't know actually the status but finally I can have a standard to develop an extension that already run probably in the future in many ways but we are standard but I wanted to leave resources because we are developer we want to read the documentation don't mind it but read yes and there is a little bit of links as an example there is an extension to download the extension from Google Chrome in Firefox there is one of the last news as an example I will say in Firefox there is a problem of anti-views that create problems in the next version we even have extension that can download library in the system because the new API is native messaging so on in a different way but there are many documentation there is also the roadmap a label of Trello you can see they want to release a new version of Firefox there is a list for people that have a very list there is a list there is also a section on this course I forgot to add the link you can find this course the developer tools that don't section so you can ask here your problem asking the developer question etc it is a forum so for people that don't like many lists you can also have a forum so this is my slide I will try to run an extension now from Firefox itself because it was very fast we have a developer we want to get boring about text stuff this is a page we can see also a few system addons as an example that are already in the system but now we can see these cool things I remember the part where is the examples is I put in a wrong no is the wrong path when you contribute in different projects you don't remember where they are ok this is the folder available MDN with the examples you can see there are many of them there are Marsha client tests so there is nothing messaging nothing message is pretty cool unable to access a program itself in your computer and communicate with Firefox but it is not injected inside Firefox it is another process because it is another executable so you can communicate different applications in the system what we can do is connect the computer ok this is the most simple one I can say the most funny it had a button there was not this button we have a simple page that I have to run in a in a web page because it is not working ok it is very simple but the code is very simple because only change the document right and attach the image is a code script the results are the one that changes the borderline but these are extensions and as you can see you can get fun I started in that way I can want to say my experience I I take the borderify every time a station and I use it from the WordPress polyglots community that support 14 different languages that help all the community workers to translate extensions that have a glossary and there is a valley button Chrome and Firefox I finished the time so I guess the question here speak very loud when you ask a question and Daniela please repeat the question thank you the problem is that Chrome extension developers don't know if they can run the new part is Mozilla trying to engage with Chrome extension developers to show them that they are at most as you say in the developers app there was a section in the application on MDN but the developers have three weeks of life so we started to promotion about it I saw people that suggest to move to try on Firefox people that open ticket improve your code on Firefox I think in the next months we will see many new extensions from Chrome yes the question is do you have a timeline for the W3C standardization I don't remember that I remember the group of study but I don't remember the status sorry no questions I will say very okay I think it is very interesting direction but I was thinking it was a bit illogical in the presentation because you say that extension was made for Firefox for me at least it is but by the end of the year two thirds of the important hardware that I use every day will stop working I understand again very well but I will try to reply the reason the problem of the change of API of time is true but the new extension is the future because I showed now the extension is like a wrapper it is all the CDK then there will be a change inside Firefox whereas we will not have a problem like before with all the CDK that when the new Firefox extension was broken with that extension this problem don't happen because there is like a wrapper to the inside Firefox mechanics so it is working without problem I do have to flow everything I don't know so I can answer that one a little bit better the question was a lot of extensions we will just break and won't work with the new web extensions model that is basically your question you lose a lot of your extensions I am not on the add-ons team but I will give what I think my answer is that we are changing the add-ons system to make Firefox safer for users to make things better for developers and to standardize unfortunately during that transition yes we will do some add-ons we are working very very closely with as many add-ons as possible to port their add-ons and to bring APIs into the new web extensions that will accommodate what they are trying to do so we are really trying our best here but we think this is the future we think this is a way forward it is more secure it is better for users it is better for developers all around Firefox will be more secure we are doing our best as we make the transition yeah you can try why don't we not consider a more young developer for your app for extension because I don't believe when you release at the end of the year you will only release with the scope which is equivalent to Chrome and then it means that I am speaking which API which are needed for specific extension won't be ready at the time so when we do the transition we will stop why do we not consider to have a long time of overlay to allow people to work on this API which are necessary and then do the transition with less impact for the user yeah unfortunately I can't answer that question I am not on the Adams team or the platform team I just give my opinion we put a lot of thought into the length of the transition time the work we are doing with developers the work we are doing with APIs and so on the Adams team are actually in the room here could some Adams team people put their hands up maybe you can talk to them afterwards and get their thoughts on this ask them questions we have time for one more question