privacytools.io provides knowledge and tools to protect your privacy against global mass surveillance.

Before iridiumbrowser, we had to decide if we wanted to have cutting edge technologies like sandboxed processes, WebRTC, WebUSB … , or if we wanted to use a browser that respects our privacy. So we decided to use the power of free software and build a browser that can do both. We analysed the code of Chromium and stripped out the functionality which exposes data to others in a way we don‘t like.

Our ambition is to get builds for Debian, Ubuntu, openSUSE, fedora, Windows and OS-X a couple of days after a new release of Chromium.
To achieve this, we need help from individuals and organisations, who have the same intention. Currently there are weeks between a new release of Iridium and Chromium.
Please take this into consideration for your personal usage of the browser as you might be at risk when surfing unknown and potentially dangerous websites!
We feel, that as an application browser or as browser for trusted websites, this is acceptable.

One of the challenges faced most often by those of us in the field of usability is finding good data about user behavior quickly, accurately, and, in most cases, cheaply. In an environment where many stakeholders question the return on investment in usability, some in the industry have developed interesting ideas aimed at gathering user data. One such idea is the analysis of server log files to gather information about user behavior. On the surface, it is easy to understand the gravitation towards server logs: They’re supposedly a data source which portrays what people are doing on a site. Server logs supposedly show what people click on, which pages they view, and how they get from page to page.

Often when I talk to clients, I am asked the following question: “Can we track how many users with disabilities access our site?”. The question itself is always asked with good intentions. The client wants to be able to provide an improved experience for persons with disabilities.

The short answer is that you can’t. At the time of writing there isn’t a way to reliably detect whether someone visiting your site is using a screen reader (or screen magnifier). You might have heard that Flash will do the trick, but that might not be quite the solution you’re expecting.

On February 26, 2014, the webAIM project published the results of their 5th screen reader user survey. Two questions were new in this survey that pertain to a recently growing desire of some web developers to know whether they’re dealing with assistive technologies on the other end or not. The results were rather shocking to me as a representative of a browser vendor and experienced assistive technology user:

We have an advanced webpage (ASP.NET, C#), and a application which needs to be installed on the client computer in order to utilize the webpage to its fullest. The application is a tray app, and has primarily two tasks. Detect when certain events happen on the webserver (for instance invited to a meeting, or notify of an upcoming meeting). The other task the trayapp has is to use a custom protocol (trayapp://) to perform some ajax calls back to the server.

Maqetta is free, open source software (published under the modified BSD license or the Academic Free License version 2.1) that provides WYSIWYG visual authoring of HTML5 user interfaces. The Maqetta application itself is authored in HTML, and therefore runs in the browser without requiring additional plugins or downloads.