written by an outsider, blame sladen for any errors
Multisearch is an attempt to improve the browser search experience in the default configuration of Firefox on Ubuntu. It may also be identified as firstname.lastname@example.org (Mozilla Experiment v0.0.1).
The experiment was finished when the plugin patch was removed on 2009-08-11, with the upload of firefox-3.0 (3.0.13+nobinonly-0ubuntu3).
It had only been added to the developer (alpha) versions of Ubuntu and had not been released into the main general use version of Ubuntu.
The first step in improving an experience is to observe how it is used, for example usability testing performed by videoing people and their mouse-movements in a laboratory environment. The Ubuntu community is much larger than can all fit in a laboratory at once and are busy people who don't have time to. For a temporary period during July/August 2009, a sample of searching habits (not searching results) has been made.
Don't worry about searching for Microsoft Windows, or Mac OS from Ubuntu---nobody other than Google is going to know exactly what anyone else has searched for, and there is no way that Launchpad cookies will get sent to Google (or anyone else) either.
* Launchpad: Comment #24 ("official reply")
LWN: Ubuntu's multisearch surprise, 2009-08-07
Slashdot: Ubuntu's New Firefox Is Watching You
Launchpad: commit #407 in firefox/ubuntu.me001 showing diff
Multisearch plugin: multisearch.tgz source code (full plugin source, rather than diff)
Blog update: What is this "Multisearch" thing in my Firefox about? ("official annoucement")
There are currently four ways that Firefox browser searches are forwarded to Google;
Ubuntu 9.10 alpha*
New (blank) tab
Mozilla's partner IDs are "firefox" and "firefox-a"; Canonical's is "partner-pub-2070091971271392"... the "random" numbers after the colon (':') allow the source of the query (the "channel")to be attributed to one of the four search inputs.
(*In the case of the experimental/statistics blank tab, the page is loaded locally, but the favicon is still fetched from http://start.ubuntu.com/favicon.ico).
The Multisearch statistics gathering plugin has only been added to the Firefox-3.0 package. Because of the way that plugins are shared between Firefox browser versions, it will also appear in Firefox-3.5, if you also have the Firefox-3.0 browser installed.
Confirmed, I just installed firefox-3.5 package on a clean and up to date Karmic install, and multisearch extension is active, and the expected cse behaviour is observed --AlanPope
The statistics gathering exercise was started at the end of July 2009. The numbers coming in were checked once shorty after deployment (to confirm that it was working), but will not be analysed until the statistics gathering-code has been disabled/removed.
The multisearch plugin will not exist in its current form in the final Ubuntu 9.10 release. What to do next, or for Ubuntu 9.10 itself will be reviewed after the the Alpha 4 milestone has been released.
If the meantime, if helping to testing the Alpha 3+4 (and helping to improve Ubuntu) is getting in the way of your daily workflow, we're sorry. It was not intended; you can disable the temporary plugin by going to:
Firefox->Tools->Add-ons->Extensions->Select 'Multisearch'->Disable. Restart Firefox.
Note: This will disable the extension, so new tabs will no longer have the new search, but will instead be blank. Disabling the extension will not reset the default browser home page. To change the home page go to:-
Edit->Preferences->Main. Specify a URL or use the shortcut buttons to use an existing tab or tabs. Click Close.
A number of bugs were filed that the use of the the Google Custom Search Edition (CSE) page rather than the default Google page had introduced loss of functionality. For the moment, (Paul Sladen) has duped all of these to the same bug report, as they are all caused by the same root cause---the introduction of CSE---and are probably only fixable by avoiding the use of CSE.
Please add the "multisearch" tag to any bugs you find. When the main bug is closed, the dups will be checked individually and any not solved de-duped.
In the case of purely wanting result statistics, CSE is not really the best tool for the job. It is sub-optimal because of various bits of "normal" Google functionality are removed. One reason for Multisearch being an experiment has been to get a detailed list of issues.
An example of a correct use of Google CSE is to restrict search results to a sub-set of pages; for instance this example by Dustin to narrow results down to Ubuntu Developer documentation:
The deployed research experiment is about getting some automated feedback on how people use the various browser functions; this may lead into work that can try to reduce the time spent when searching (eg. going straight from a highlighted address, to map directions).
Mozilla have been working (and funding) initiatives aimed at this:
Rather than aiming duplicate effort, the time and effort spent by Ubuntu users (and developers) should help feed into this process. As it stands, the current Ubuntu multisearch code needs more work:
AwesomeBar does not have I'm feeling lucky support
- chrome changes the Google searchplugin
- New Tab is not configurable
In the process of making usability improvements, there may also be a way to get adverts added...
Ubuntu is free (no money) aswell as Free (to modify), and it takes developers. If a way can be found for Ubuntu users to support Ubuntu via adverts on the default Google results page, then that means more Ubuntu talented developers can be funded to work on Ubuntu and upstream projects.
There are probably three possibilities:
- Arrange "special page" with Google (best outcome, equivalent to upstream Mozilla arrangement)
- Try to make the CSE page look equivalent to the "normal" Google results page.
- Drop CSE all together and work on other stuff.
The first would be ideal. In the case of the second options, there is a trade-off between seeing which options can be mitigated (if possible). The trade-off between that and the third option (walking away) is that less future developer time to make other improvements may be available.
As always, ideas are welcomed, both via the bug tracker, and at #ubuntu-mozillateam on Freenode;