Mozilla Looking to Tag Along
Figuring out how your customers use your products — and by extension, how to improve user experience — can be a tricky process to navigate. Focus groups have their flaws, surveys suffer from selective memory, and peeping over shoulders could plant one in the penitentiary. The browser-makers at Mozilla, though, are hoping to put an Open Source spin on the process, expecting to release within the next few weeks a plugin to gather usage data from volunteers.
The plan, which is entirely opt-in and requires installing a plugin to participate, has been dubbed Test Pilot by Mozilla Labs, and hopes to provide volumes of useful information for Mozilla developers and outside researchers. Volunteers will initially be asked to provide a limited amount of information for demographic purposes, then will install Test Pilot and browse as usual. Additional "experiments and tests" will follow, and the participants will have the opportunity to choose whether or not to take part in a given exercise. All information submitted by the plugin will be anonymized and in aggregate, while potentially sensitive information, like individual web addresses, will be tracked with the use of hashes and other anonymizing technology. In this way, usage data — how often a user returned to a previously visited website, for example — can be collected without revealing the website in question.
Mozilla Labs' user experience chief, Aza Raskin, was quick to point out the transparency provided by Mozilla's Open Source approach. "One of the great things about Firefox and Mozilla is that you don't have to take [our word] on faith. There are no secrets with open source. In Test Pilot, the source [code] and the data will be open." Unlike proprietary code, which may hide any manner of surreptitious data collection, users skeptical of Test Pilot will have the ability to see for themselves exactly what the code is doing. How much effect these and other steps to protect user privacy will have on the project's reception remains to be seen.
Mozilla execs are expecting the program to provide information that can be used not only to improve Firefox, but other Mozilla products, browser extensions, and spawn new products as well. Raskin pointed to the enlarged back button included with the Firefox 3 release as an example of feedback-driven change — user experience data showed higher use of the back button than forward, prompting the change. Mozilla hopes 1% of the browser's users can be convinced to take part in Test Pilot, a grand undertaking indeed, considering that estimates exceeded 125 million users over a year ago.
The issue of privacy is one that can get just about anyone's hackles up, and this one is likely to be no different. Whether it be companies hemorrhaging credit card details or covert keylogging as you browse the reasons to worry about where ones data is going are legion. Mozilla is, at least, definitely stepping off with the right foot, being open from the beginning, opting-in rather than out, making strides to balance privacy and progress, and maintaining the transparency and openness that is a cornerstone of Open Source projects.
Justin Ryan is a Contributing Editor for Linux Journal.
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide