What has Mozilla done for the web?


The behaviour of online advertising companies and web developers should be of increasing concern to anyone who uses the internet. In recent years, advertisers have begun 'tracking' users across multiple different websites.

So, if you visit a site to help you find a new flat in Bath, it's quite possible that you'll see adverts for flats in Bath on other, unrelated websites later in your browsing session.

This can be useful, enabling you to see only adverts that are most relevant to you, but it can also be quite sinister. Advertisers are able to build a detailed picture of who you are: where you live, what your interests are, what medical conditions you might have… the list goes on.

Worst of all, few users have any idea that this kind of information is being kept about them. There have always been ways for users to deal with this problem, including regularly deleting your cookies, but some advertisers are always finding ways to continue collecting data even after the user has taken these kind of steps.

Recognising this game of privacy cat and mouse, Mozilla set out to do something about it and created the Do Not Track header. When turned on, this sends a signal to every website, telling them that the user doesn't want to be tracked in any way.

It's got a lot going for it – it's simple to use and it's simple for websites to identify and respond to. It's also well on the way to becoming a new standard, with Microsoft and Apple both adding it to their browsers.

Unfortunately, it's not without problems. Most prominently, it doesn't enforce a user's preference, only expresses it to the website. This means users are dependent on advertisers recognising and responding to this setting consistently. Some might disable targeted adverts, for instance, but continue collecting data.

The only solution that will result in a safer internet for everybody is governments getting involved, either by threatening to legislate or legislating in support of Do Not Track.

Since it has gained so much momentum, thanks in part to Mozilla working with others and pushing for it to be standardised, the US and the EU have already expressed a desire to see widespread and consistent implementations of DNT across the web – if they don't, they may well legislate.


Almost every site we visit on the web wants us to log in. They want us to do this so they can provide a more personal experience: whether that means relaying what our friends thought of the site, making recommendations based on past products we viewed, or letting us comment and engage with that site's community. Yet almost every site implements its own login system.

Every time we join a new community on the web we have to go through the same, annoying process of filling out a registration form. This process is also insecure. Virtually every website will ask us to come up with a new username and password combination.

While we all know that we shouldn't use the same password on every site, remembering a dozen different passwords is hard. This means that we often end up using the same one, or a dozen different, but easy to remember (and hack) variations.

Sites that don't implement their own login system, but instead take advantage of Facebook or Google's offerings, jeopardise user sovereignty. Every time you log in with one of these services, you provide the commercial entity with more information about your browsing habits.

It also means that you're entrusting your online identity, your history of actions, to the long-term survival of a commercial entity. What happens if Facebook disappears from the web? Or if you decide that they're a bit too sinister for your tastes, and you want to move to a different identity provider? With the web as it is, there's not a lot you can do about this.

Step in Mozilla. It has recently launched BrowserID, the first link in its attempts to begin creating "an open source, standards-based platform for universally accessible, decentralised, customised identity on the Web."

With BrowserID, users need only one set of login credentials, so they can make them strong. There's no centralised authority, meaning any email provider can implement support for BrowserID. It's also inherently privacy protecting, as all logins happen through the user's browser.


The open web's continued success depends on new generations coming through that not only understand and care about freedom and openness, but that also understand how technology can affect these social issues.

In the UK, this is an issue that recently received a lot of attention when Eric Schmidt criticised our computer teaching methods. In the McTaggart lecture, he said the UK's IT curriculum "focuses on teaching how to use software, but gives no insight into how it's made".

You might be able to work Word or Excel, or create a profile on Facebook, but if you don't understand how computers work, you'll never understand the downsides associated with these same technologies.

Word and Excel, for example, employ proprietary document formats that not only force others to use the same software as you (and, if governments use them, limit access to important publications to those who can afford the software), but pose a potential hazard for archivists and future generations looking back.

If you've learned how computers work, however, you'll start to understand what data is, how services and programs can communicate with one another, and how much more powerful computers are when this is made possible.

Fortunately, every computer in the world comes with a first-class programming environment that can provide immediate, visual feedback: the web browser. This means that, with the right teaching resources in place, everybody can learn some of these fundamentals without spending another penny.

And it's these teaching resources that Mozilla is trying to put in place. They've built a lot of resources under the School of Webcraft banner, where users can teach and help each other to learn about web programming.

They've also been hard at work on their Hackasaurus, which is aimed at school-age children (and grown-up kids, too). It teaches them to hack the web through interactive narratives, and provides the basis for classroom activities and after-school clubs.

Many Mozilla supporters are even going out to their local schools to teach children about programming and the web.


The web is changing journalism, in more ways than the damage to circulation and revenues it's accused of causing. Journalists are gathering information from all possible sources – Twitter, press releases, reporters on the ground, news wires – and throwing it all up to their organisations' websites immediately.

Not long ago, this would have been unthinkable. News operated on a 24-hour cycle, with stories breaking and then rapidly being written up for the next day's editions. In many ways, today's journalism is a wonderful development on the 24-hour news cycle.

As consumers of news, we can find out what's happening at any time of the day. And the information that's forming our opinions is immeasurably richer, with contributions coming from ordinary people caught up in protests, civil wars and stock market trading floors as the events unfold.

At the same time, this model of journalism and news reporting presents real challenges to journalists and us, as consumers of news. There's far less scope for fact checking. How often do we see a suspect arrested and minute details of their lives inspected and distorted, only to later have their name cleared? How can we, as consumers, have confidence in the news we're reading?

The other major question this model of journalism poses is how we can see a story in its wider context, when we're told it in disparate detail as soon as it occurs. Mozilla believes that part of the solution to these problems is news organisations better employing open web technologies.

Can readers be involved in fact checking, providing instant feedback on the accuracy of politicians' speeches? Can web technologies be combined with open data to provide context, and solid facts and figures to support a reporter's case?

Mozilla has partnered with the Knight Foundation to get hackers working on journalistic problems. They're even sponsoring a group of 'fellows' – hackers who are going to be working in the newsrooms of the BBC, Al Jazeera, Zeit Online, the Guardian and the Boston Globe – to help them solve their problems and make their reporting more fit for the digital age.