I am impressed with the solution that has sprung forward, even if it is only a mockup. I already commented on them, we'll have to wait how the final version pans out. I'm wondering how much Canonical had a hand in that mockup. I guess we'll never know :). Either way, it looks like the Mozilla/Canonical collaboration is a succesful one. And I'd like to think that we (the community) did have a hand in the end result.
I'd like to thank you, Mark (and other Ubuntu and Mozilla officials as well) for still attending this bug in spite of the low signal-to-noise ratio.
With regards to the question by lord_alan about shipping Firefox with web services switched off by default: as a system admin you can do this yourself via /etc/firefox-3.0/pref/firefox.js:
pref("browser.safebrowsing.enabled", false);
pref("browser.safebrowsing.malware.enabled", false);
Considering how things are now with the services agreement, I don't think it will be necessary to ship with them turned off.
I am impressed with the solution that has sprung forward, even if it is only a mockup. I already commented on them, we'll have to wait how the final version pans out. I'm wondering how much Canonical had a hand in that mockup. I guess we'll never know :). Either way, it looks like the Mozilla/Canonical collaboration is a succesful one. And I'd like to think that we (the community) did have a hand in the end result.
I'd like to thank you, Mark (and other Ubuntu and Mozilla officials as well) for still attending this bug in spite of the low signal-to-noise ratio.
With regards to the question by lord_alan about shipping Firefox with web services switched off by default: as a system admin you can do this yourself via /etc/firefox- 3.0/pref/ firefox. js: safebrowsing. enabled" , false); safebrowsing. malware. enabled" , false);
pref("browser.
pref("browser.
Considering how things are now with the services agreement, I don't think it will be necessary to ship with them turned off.