Mozilla Nederland LogoDe Nederlandse

Gervase Markham: Someone Thought This Was A Good Idea

Mozilla planet - to, 20/10/2016 - 11:55

You know that problem where you want to label a coffee pot, but you just don’t have the right label? Technology to the rescue!


Of course, new technology does come with some disadvantages compared to the old, as well as its many advantages:


And pinch-to-zoom on the picture viewer (because that’s what it uses) does mean you can play some slightly mean tricks on people looking for their caffeine fix:


And how do you define what label the tablet displays? Easy:


Seriously, can any reader give me one single advantage this system has over a paper label?

Categorieën: Mozilla-nl planet

Mozilla rozhodla: zítra přestane věřit CA WoSign a StartCom -

Nieuws verzameld via Google - to, 20/10/2016 - 09:48

Mozilla rozhodla: zítra přestane věřit CA WoSign a StartCom
Mozilla přestane důvěřovat certifikátům s platností začínající po 21. říjnu. Tak zní definitivní rozhodnutí týmu zodpovědného za správu kořenových autorit. Na svém blogu to oznámil vývojář Gervase Markham a šéfka týmu, Kathleen Wilson, už vytvořila ...

en meer »Google Nieuws
Categorieën: Mozilla-nl planet

Mozilla rozhodla: zítra přestane věřit CA WoSign a StartCom -

Nieuws verzameld via Google - to, 20/10/2016 - 09:48

Mozilla rozhodla: zítra přestane věřit CA WoSign a StartCom
Mozilla přestane důvěřovat certifikátům s platností začínající po 21. říjnu. Tak zní definitivní rozhodnutí týmu zodpovědného za správu kořenových autorit. Na svém blogu to oznámil vývojář Gervase Markham a šéfka týmu, Kathleen Wilson, už vytvořila ...

Google Nieuws
Categorieën: Mozilla-nl planet

Daniel Pocock: Choosing smartcards, readers and hardware for the Outreachy project

Mozilla planet - to, 20/10/2016 - 09:25

One of the projects proposed for this round of Outreachy is the PGP / PKI Clean Room live image.

Interns, and anybody who decides to start using the project (it is already functional for command line users) need to decide about purchasing various pieces of hardware, including a smart card, a smart card reader and a suitably secure computer to run the clean room image. It may also be desirable to purchase some additional accessories, such as a hardware random number generator.

If you have any specific suggestions for hardware or can help arrange any donations of hardware for Outreachy interns, please come and join us in the pki-clean-room mailing list or consider adding ideas on the PGP / PKI clean room wiki.

Choice of smart card

For standard PGP use, the OpenPGP card provides a good choice.

For X.509 use cases, such as VPN access, there are a range of choices. I recently obtained one of the SmartCard HSM cards, Card Contact were kind enough to provide me with a free sample. An interesting feature of this card is Elliptic Curve (ECC) support. More potential cards are listed on the OpenSC page here.

Choice of card reader

The technical factors to consider are most easily explained with a table:

On disk Smartcard reader without PIN-pad Smartcard reader with PIN-pad Software Free/open Mostly free/open, Proprietary firmware in reader Key extraction Possible Not generally possible Passphrase compromise attack vectors Hardware or software keyloggers, phishing, user error (unsophisticated attackers) Exploiting firmware bugs over USB (only sophisticated attackers) Other factors No hardware Small, USB key form-factor Largest form factor

Some are shortlisted on the GnuPG wiki and there has been recent discussion of that list on the GnuPG-users mailing list.

Choice of computer to run the clean room environment

There are a wide array of devices to choose from. Here are some principles that come to mind:

  • Prefer devices without any built-in wireless communications interfaces, or where those interfaces can be removed
  • Even better if there is no wired networking either
  • Particularly concerned users may also want to avoid devices with opaque micro-code/firmware
  • Small devices (laptops) that can be stored away easily in a locked cabinet or safe to prevent tampering
  • No hard disks required
  • Having built-in SD card readers or the ability to add them easily
SD cards and SD card readers

The SD cards are used to store the master private key, used to sign the certificates/keys on the smart cards. Multiple copies are kept.

It is a good idea to use SD cards from different vendors, preferably not manufactured in the same batch, to minimize the risk that they all fail at the same time.

For convenience, it would be desirable to use a multi-card reader:

although the software experience will be much the same if lots of individual card readers or USB flash drives are used.

Other devices

One additional idea that comes to mind is a hardware random number generator (TRNG), such as the FST-01.

Can you help with ideas or donations?

If you have any specific suggestions for hardware or can help arrange any donations of hardware for Outreachy interns, please come and join us in the pki-clean-room mailing list or consider adding ideas on the PGP / PKI clean room wiki.

Categorieën: Mozilla-nl planet

Mozilla Open Design Blog: Nearly there

Mozilla planet - to, 20/10/2016 - 07:55

We’ve spent the past two weeks asking people around the world to think about our four refined design directions for the Mozilla brand identity. The results are in and the data may surprise you.

If you’re just joining this process, you can get oriented here and here. Our objective is to refresh our Mozilla logo and related visual assets & design toolkit that support our mission and make it easier for people who don’t know us to get to know us.

A reminder of the factors we’re taking into account in this phase. Data is our friend, but it is only one of several aspects to consider. In addition to the three quantitative surveys—of Mozillians, developers, and our target consumer audience—qualitative and strategic factors play an equal role. These include comments on this blog, constructive conversations with Mozillians, our 5-year strategic plan for Mozilla, and principles of good brand design.

Here is what we showed, along with a motion study, for each direction:






We asked survey respondents to rate these design directions against seven brand attributes. Five of them—Innovative, Activist, Trustworthy, Inclusive/Welcoming, Opinionated—are qualities we’d like Mozilla to be known for in the future. The other two—Unique, Appealing—are qualities required for any new brand identity to be successful.

Mozillians and developers meld minds.

Members of our Mozilla community and the developers surveyed through MDN (the Mozilla Developer Network) overwhelmingly ranked Protocol 2.0 as the best match to our brand attributes. For over 700 developers and 450 Mozillians, Protocol scored highest across 6 of 7 measures. People with a solid understanding of Mozilla feel that a design embedded with the language of the internet reinforces our history and legacy as an Internet pioneer. The link’s role in connecting people to online know-how, opportunity and knowledge is worth preserving and fighting for.


But consumers think differently.

We surveyed people making up our target audience, 400 each in the U.S., U.K., Germany, France, India, Brazil, and Mexico. They are 18- to 34-year-old active citizens who make brand choices based on values, are more tech-savvy than average, and do first-hand research before making decisions (among other factors).

We asked them first to rank order the brand attributes most important for a non-profit organization “focused on empowering people and building technology products to keep the internet healthy, open and accessible for everyone.” They selected Trustworthy and Welcoming as their top attributes. And then we also asked them to evaluate each of the four brand identity design systems against each of the seven brand attributes. For this audience, the design system that best fit these attributes was Burst.


Why would this consumer audience choose Burst? Since this wasn’t a qualitative survey, we don’t know for sure, but we surmise that the colorful design, rounded forms, and suggestion of interconnectedness felt appropriate for an unfamiliar nonprofit. It looks like a logo.


Also of note, Burst’s strategic narrative focused on what an open, healthy Internet feels and acts like, while the strategic narratives for the other design systems led with Mozilla’s role in world. This is a signal that our targeted consumer audience, while they might not be familiar with Mozilla, may share our vision of what the Internet could and should be.

Why didn’t they rank Protocol more highly across the chosen attributes? We can make an educated guess that these consumers found it one dimensional by comparison, and they may have missed the meaning of the :// embedded in the wordmark.


Although Dino 2.0 and Flame had their fans, neither of these design directions sufficiently communicated our desired brand attributes, as proven by the qualitative survey results as well as through conversations with Mozillians and others in the design community. By exploring them, we learned a lot about how to describe and show certain facets of what Mozilla offers to the world. But we will not be pursuing either direction.

Where we go from here.

Both Protocol and Burst have merits and challenges. Protocol is distinctly Mozilla, clearly about the Internet, and it reinforces our mission that the web stay healthy, accessible, and open. But as consumer testing confirmed, it lacks warmth, humor, and humanity. From a design perspective, the visual system surrounding it is too limited.

By comparison, Burst feels fresh, modern, and colorful, and it has great potential in its 3D digital expression. As a result, it represents the Internet as a place of endless, exciting connections and possibilities, an idea reinforced by the strategic narrative. Remove the word “Mozilla,” though, and are there enough cues to suggest that it belongs to us?

Our path forward is to take the strongest aspects of Burst—its greater warmth and dimensionality, its modern feel—and apply them to Protocol. Not to Frankenstein the two together, but to design a new, final direction that builds from both. We believe we can make Protocol more relatable to a non-technical audience, and build out the visual language surrounding it to make it both harder working and more multidimensional.

Long live the link.

What do we say to Protocol’s critics who have voiced concern that Mozilla is hitching itself to an Internet language in decline? We’re doubling down on our belief in the original intent of the Internet—that people should have the ability to explore, discover and connect in an unfiltered, unfettered, unbiased environment. Our mission is dedicated to keeping that possibility alive and well.

For those who are familiar with the Protocol prompt, using the language of the Internet in our brand identity signals our resolve. For the unfamiliar, Protocol will offer an opportunity to start a conversation about who we are and what we believe. The language of the Internet will continue to be as important to building its future as it was in establishing its origin.

We’ll have initial concepts for a new, dare-we-say final design within a few weeks. To move forward, first we’ll be taking a step back. We’ll explore different graphic styles, fonts, colors, motion, and surrounding elements, making use of the design network established by our agency partner johnson banks. In the meantime, tell us what you think.

Categorieën: Mozilla-nl planet

The Rust Programming Language Blog: Announcing Rust 1.12.1

Mozilla planet - to, 20/10/2016 - 02:00

The Rust team is happy to announce the latest version of Rust, 1.12.1. Rust is a systems programming language with a focus on reliability, performance, and concurrency.

As always, you can install Rust 1.12.1 from the appropriate page on our website, or install via rustup with rustup update stable.

What’s in 1.12.1 stable

Wait… one-point-twelve-point… one?

In the release announcement for 1.12 a few weeks ago, we said:

The release of 1.12 might be one of the most significant Rust releases since 1.0.

It was true. One of the biggest changes was turning on a large compiler refactoring, MIR, which re-architects the internals of the compiler. The overall process went like this:

  • Initial MIR support landed in nightlies back in Rust 1.6.
  • While work was being done, a flag, --enable-orbit, was added so that people working on the compiler could try it out.
  • Back in October, we would always attempt to build MIR, even though it was not being used.
  • A flag was added, -Z orbit, to allow users on nightly to try and use MIR rather than the traditional compilation step (‘trans’).
  • After substantial testing over months and months, for Rust 1.12, we enabled MIR by default.
  • In Rust 1.13, MIR will be the only option.

A change of this magnitude is huge, and important. So it’s also important to do it right, and do it carefully. This is why this process took so long; we regularly tested the compiler against every crate on, we asked people to try out -Z orbit on their private code, and after six weeks of beta, no significant problems appeared. So we made the decision to keep it on by default in 1.12.

But large changes still have an element of risk, even though we tried to reduce that risk as much as possible. And so, after release, 1.12 saw a fair number of regressions that we hadn’t detected in our testing. Not all of them are directly MIR related, but when you change the compiler internals so much, it’s bound to ripple outward through everything.

Why make a point release?

Now, given that we have a six-week release cycle, and we’re halfway towards Rust 1.13, you may wonder why we’re choosing to cut a patch version of Rust 1.12 rather than telling users to just wait for the next release. We have previously said something like “point releases should only happen in extreme situations, such as a security vulnerability in the standard library.”

The Rust team cares deeply about the stability of Rust, and about our users’ experience with it. We could have told you all to wait, but we want you to know how seriously we take this stuff. We think it’s worth it to demonstrate our commitment to you by putting in the work of making a point release in this situation.

Furthermore, given that this is not security related, it’s a good time to practice actually cutting a point release. We’ve never done it before, and the release process is semi-automated but still not completely so. Having a point release in the world will also shake out any bugs in dealing with point releases in other tooling as well, like rustup. Making sure that this all goes smoothly and getting some practice going through the motions will be useful if we ever need to cut some sort of emergency point release due to a security advisory or anything else.

This is the first Rust point release since Rust 0.3.1, all the way back in 2012, and marks 72 weeks since Rust 1.0, when we established our six week release cadence along with a commitment to aggressive stability guarantees. While we’re disappointed that 1.12 had these regressions, we’re really proud of Rust’s stability and will to continue expanding our efforts to ensure that it’s a platform you can rely on. We want Rust to be the most reliable programming platform in the world.

A note about testing on beta

One thing that you, as a user of Rust, can do to help us fix these issues sooner: test your code against the beta channel! Every beta release is a release candidate for the next stable release, so for the cost of an extra build in CI, you can help us know if there’s going to be some sort of problem before it hits a stable release! It’s really easy. For example, on Travis, you can use this as your .travis.yml:

language: rust rust: - stable - beta

And you’ll test against both. Furthermore, if you’d like to make it so that any beta failure doesn’t fail your own build, do this:

matrix: allow_failures: - rust: beta

The beta build may go red, but your build will stay green.

Most other CI systems, such as AppVeyor, should support something similar. Check the documentation for your specific continuous integration product for full details.

Full details

There were nine issues fixed in 1.12.1, and all of those fixes have been backported to 1.13 beta as well.

In addition, there were four more regressions that we decided not to include in 1.12.1 for various reasons, but we’ll be working on fixing those as soon as possible as well.

You can see the full diff from 1.12.0 to 1.12.1 here.

Categorieën: Mozilla-nl planet

Support.Mozilla.Org: Firefox 49 Support Release Report

Mozilla planet - to, 20/10/2016 - 01:13

This report is aiming to capture and explain what has happened during and after the launch of Firefox 49on multiple support fronts: Knowledge Base and localization, 1:1 social and forum support, trending issues and reported bugs, as well as to celebrate and recognize the tremendous work the SUMO community is putting in to make sure our users experience a happy release. We have lots of ways to contribute, from Support to Social to PR, the ways you can help shape our communications program and tell the world about Mozilla are endless. For more information: []

Knowledge Base and Localization Article Voted “helpful” (English/US only) Global views Comments from dissatisfied users Desktop (Sept. 20 – Oct. 12) 76-80% 93871 “No explanation of why it was removed.” 61-76% 8625 none 36-71% 11756 “Didn’t address Firefox not playing YouTube tutorials” 70-75% 5147 “Please continue to support Firefox for Pentium III. It is not that hard to do.”

“What about those who can’t afford to upgrade their processors?”

Android (Sept. 20 – Oct. 12) 68% 292 none Localization Article Top 10 locale coverage Top 20 locale coverage Desktop (Sept. 20 – Oct. 12) 100% 86% 100% 81% 100% 81% 100% 81% Android (Sept. 20 – Oct. 12) 100% 71%


Support Forum Threads


Great teamwork between some top contributors


Bugs Created from Forum threads – SUMO Community
  • [Bug 1305436] Firefox 49 won’t start after installation
  • [Bug 1304848] Users report Firefox is no longer launching after the 49 update with a mozglue.dll missing error instead
  • (Contributed to) [Bug 1304360] Firefox49 showing graphics artifacts with HWA enabled
Army Of Awesome

(by Stefan Costen -Costenslayer)

My thanks goes out to all contributors for their help in supporting everyone from crashed (which can be difficult and annoying) to people thanking us. All of your hard work has been noticed and is much appreciated

Along with Amit Roy (twitter: amitroy2779) for helping uses every day

Social Support Highlights

Brought to you by Sprinklr

Total active contributors in program ~16

Top 12 Contributors Name Engagements Noah 103 Magdno 69 Daniela 28 Andrew 25 Geraldo 10 Cynthia 10 Marcelo 4 Jhonatas 2 Thiago 2 Joa Paulo 1

Number of Replies:


Trending issues

Innbound, what people are clicking and asking about:


Outbound top engagement:


Thank yous from users who received SUMO help Support Forums:

Thanks to jscher from determining between how windows and Firefox handles different video file types Thank you post

Thank you for Noah from a user on Social, link here

Tune in next time in three weeks for Firefox 50!

Categorieën: Mozilla-nl planet

Air Mozilla: Singularity University

Mozilla planet - to, 20/10/2016 - 00:11

Singularity University Mozilla Executive Chair Mitchell Baker's address at Singularity University's 2016 Closing Ceremony.

Categorieën: Mozilla-nl planet

Air Mozilla: IEEE Global Connect

Mozilla planet - to, 20/10/2016 - 00:10

IEEE Global Connect Mozilla Executive Chair Mitchell Baker's address at IEEE Global Connect

Categorieën: Mozilla-nl planet

Eric Shepherd: Finding stuff: My favorite Firefox search keywords

Mozilla planet - wo, 19/10/2016 - 23:33

One of the most underappreciated features of Firefox’s URL bar and its bookmark system is its support for custom keyword searches. These let you create special bookmarks that type a keyword followed by other text, and have that text inserted into a URL identified uniquely by the keyword, then that URL gets loaded. This lets you type, for example, “quote aapl” to get a stock quote on Apple Inc.

You can check out the article I linked to previously (and here, as well, for good measure) for details on how to actually create and use keyword searches. I’m not going to go into details on that here. What I am going to do is share a few keyword searches I’ve configured that I find incredibly useful as a programmer and as a writer on MDN.

For web development

Here are the search keywords I use the most as a web developer.

Keyword Description URL if Opens an API reference page on MDN given an interface name. elem Opens an HTML element’s reference page on MDN. css Opens a CSS reference page on MDN. fx Opens the release notes for a given version of Firefox, given its version number. mdn Searches MDN for the given term(s) using the default filters, which generally limit the search to include only pages most useful to Web developers. mdnall Searches MDN for the given term(s) with no filters in place. For documentation work

When I’m writing docs, I actually use the above keywords a lot, too. But I have a few more that I get a lot of use out of, too.

Keyword Description URL bug Opens the specified bug in Mozilla’s Bugzilla instance, given a bug number. bs Searches Bugzilla for the specified term(s). dxr Searches the Mozilla source code on DXR for the given term(s). file Looks for files whose name contains the specified text in the Mozilla source tree on DXR. ident Looks for definitions of the specified identifier (such as a method or class name) in the Mozilla code on DXR. func Searches for the definition of function(s)/method(s) with the specified name, using DXR. t Opens the specified MDN KumaScript macro page, given the template/macro name. wikimo Searches for the specified term(s).

Obviously, DXR is a font of fantastic information, and I suggest click the “Operators” button at the right end of the search bar there to see a list of the available filters; building search keywords for many of these filters can make your life vastly easier, depending on your specific needs and work habits!

Categorieën: Mozilla-nl planet

Mozilla's Rust goes real-time with code feedback - InfoWorld

Nieuws verzameld via Google - wo, 19/10/2016 - 22:00


Mozilla's Rust goes real-time with code feedback
Developers of Mozilla's Rust language, devised for fast and safe system-level programming, have unveiled the first release of the Rust Language Service (RLS), a project that provides IDEs and editors with live, contextual information about Rust code.

Categorieën: Mozilla-nl planet

Mozilla verteilt zwei neue System-Add-ons an Nutzer von Firefox 49 -

Nieuws verzameld via Google - wo, 19/10/2016 - 21:32

Mozilla verteilt zwei neue System-Add-ons an Nutzer von Firefox 49
Kurz vor Veröffentlichung von Firefox 49.0.2 hat Mozilla damit begonnen, zwei neue System-Add-ons an Nutzer von Firefox 49.0 und Firefox 49.0.1 zu verteilen. Damit behebt Mozilla diverse Probleme unabhängig vom nächsten Firefox-Update. Mozilla plant ...

Google Nieuws
Categorieën: Mozilla-nl planet

Air Mozilla: Getting Started with Mozilla Maker Party 2016

Mozilla planet - wo, 19/10/2016 - 20:21

Getting Started with Mozilla Maker Party 2016 Getting Started with Mozilla Maker Party 2016

Categorieën: Mozilla-nl planet

Air Mozilla: MozFest Volunteer Meetup - October 19, 2016

Mozilla planet - wo, 19/10/2016 - 20:00

MozFest Volunteer Meetup - October 19, 2016 Meetup for 2016 MozFest Volunteers

Categorieën: Mozilla-nl planet

Air Mozilla: The Joy of Coding - Episode 76

Mozilla planet - wo, 19/10/2016 - 19:00

The Joy of Coding - Episode 76 mconley livehacks on real Firefox bugs while thinking aloud.

Categorieën: Mozilla-nl planet

Air Mozilla: Weekly SUMO Community Meeting Oct. 19, 2016

Mozilla planet - wo, 19/10/2016 - 18:00

Weekly SUMO Community Meeting Oct. 19, 2016 This is the sumo weekly call

Categorieën: Mozilla-nl planet

'Mozilla heeft zich teveel laten afleiden' - Computable

Nieuws verzameld via Google - wo, 19/10/2016 - 14:01


'Mozilla heeft zich teveel laten afleiden'
De Mozilla Foundation, vooral bekend van webbrowser Firefox, heeft teveel andere projecten opgezet waardoor het de weg kwijt is geraakt. De negen jaar oude mailclient Thunderbird is eerder al losgelaten en die software wordt elders ondergebracht.

en meer »
Categorieën: Mozilla-nl planet

'Mozilla heeft zich teveel laten afleiden' - Computable

Nieuws verzameld via Google - wo, 19/10/2016 - 08:02

'Mozilla heeft zich teveel laten afleiden'
De Mozilla Foundation, vooral bekend van webbrowser Firefox, heeft teveel andere projecten opgezet waardoor het de weg kwijt is geraakt. De negen jaar oude mailclient Thunderbird is eerder al losgelaten en die software wordt elders ondergebracht.

Categorieën: Mozilla-nl planet

Yunier José Sosa Vázquez: Nueva versión de Firefox llega con mejoras en la reproducción de videos y mucho más

Mozilla planet - wo, 19/10/2016 - 00:24

El pasado martes 19 de septiembre Mozilla liberó una nueva versión de su navegador e inmediatamente compartimos con ustedes sus novedades y su descarga. Pedimos disculpa a todas las personas por las molestias que esto pudo causar.

Lo nuevo

El administrador de contraseñas ha sido actualizado para permitir a las páginas HTTPS emplear las credenciales HTTP almacenadas. Esta es una forma más para soportar Let’s Encrypt y ayudar a los usuarios en la transición hacia una web más segura.

El modo de lectura ha recibido varias funcionalidades que mejoran nuestra lectura y escucha mediante la adición de controles para ajustar el ancho y el espacio entre líneas del texto, y la inclusión de narración donde el navegador lee en voz alta el contenido de la página; sin dudas características que mejorarán la experiencia de uso en personas con discapacidad visual.

El modo de lectura ahora incluye controles adicionales y lectura en alta voz

El modo de lectura ahora incluye controles adicionales y lectura en alta voz

El reproductor de audio y video HTML5 ahora posibilita la reproducción de archivos a diferentes velocidades (0.5x, Normal, 1.25x, 1.5x, 2x) y repetirlos indefinidamente. En este sentido, se mejoró el rendimiento al reproducir videos para usuarios con sistemas que soportan instrucciones SSSE3 sin aceleración por hardware.

Firefox Hello, el sistema de comunicación mediante videollamadas y chat ha sido eliminado por su bajo empleo. No obstante, Mozilla seguirá desarrollando y mejorando WebRTC.

Fin del soporte para sistemas OS X 10.6, 10.7 y 10.8, y Windows que soportan procesadores SSE.

Para desarrolladores
  • Añadida la columna Causa al Monitor de Red para mostrar la causa que generó la petición de red.
  • Introducida la API web speech synthesis.
Para Android
  • Adicionado el modo de vista de página sin conexión, con esto podrás ver algunas páginas aunque no tengas acceso a Internet.
  • Añadido un paseo por características fundamentales como el Modo de Lectura y Sync a la página Primera Ejecución.
  • Introducidos las localizaciones Español de Chile (es-CL) y Noruego (nn-NO).
  • El aspecto y comportamiento de las pestañas ha sido actualizado y ahora:
    • Las pestañas antiguas ahora son ocultadas cuando la opción restaurar pestañas está establecida en “Siempre restaurar”.
    • Recuerdo de la posición del scroll y el nivel de zoom para las pestañas abiertas.
    • Los controles multimedia han sido actualizados para evitar sonidos desde múltiples pestañas al mismo tiempo.
    • Mejoras visuales al mostrar los favicons.
Otras novedades
  • Mejoras en la página about:memory para reportar el uso de memoria dedicada a las fuentes.
  • Rehabilitado el valor por defecto para la organización de las fuentes mediante Graphite2.
  • Mejorado el rendimiento en sistemas Windows y OS X que no cuentan con aceleración por hardware.
  • Varias correcciones de seguridad.

Si prefieres ver la lista completa de novedades, puedes llegarte hasta las notas de lanzamiento (en inglés).

Puedes obtener esta versión desde nuestra zona de Descargas en español e inglés para Android, Linux, Mac y Windows. Si te ha gustado, por favor comparte con tus amigos esta noticia en las redes sociales. No dudes en dejarnos un comentario.

Categorieën: Mozilla-nl planet