November 12, 2010
Update: If you’ve opened this article because you want know how to file a Sync bug, please read: How to file a good Sync bug. Thank you!
Under the hood, the Sync feature shipped in Firefox 4.0 beta 7 is on par with Firefox Sync 1.5. The new setup wizard is also there, now generating accounts solely based on email addresses and the new 20 character Sync Key. There are a two of differences compared to 4.0 beta 6 and the add-on, though:
As 4.0 beta 7 removed the status bar, we had to find a new place for the Sync button. Our philosophy is to make Sync a background service that you shouldn’t have to interact with. So want to impose as little UI as possible on users, but we do realize that some users like to be able to sync manually as well from time to time. So we’ve made the Sync button an optional toolbar button. It is not in the toolbar by default, but if you right-click on the toolbar and select Customize, you can drag it in any toolbar (the tabs bar, the navigation toolbar or even the add-on toolbar).
Traditionally, Firefox Sync has kept a log of its actions under
about:sync-log. This has been very handy for debugging problems when things go wrong. However, most of the time the logging to disk creates I/O overhead that we’d rather not have, especially on mobile devices. Logging to disk is therefore disabled by default now. You can re-enable it, for instance when you’re trying to track down a problem:
- Go to about:config
- Do right-click, select New -> Boolean
- Give it the name
- Set it to
- Restart Firefox
(Due to an oversight the
services.sync.log.appender.debugLog.enabled preference doesn’t exist by default in beta 7. That will be fixed in the next beta, though.)
November 10, 2010
Covert BarTab-like feature in Firefox 4.0 beta 7
A few weeks ago Paul O’Shannessy implemented cascading session restore. By doing that he took a big item off my to-do list for BarTab and made add-ons like Load Tabs Progressively redundant. Not only that, the number of concurrently loaded tabs can be tweaked through the
browser.sessionstore.max_concurrent_tabs preference in
about:config. If set to
0, you get instant BarTab-like behaviour. Great success!
In the meantime I have fixed a few Firefox 4.0 compatibility issues in BarTab. These fixes are in the latest BarTab beta, available from the BarTab beta channel. I’m very busy working on Firefox Sync these days so I can’t promise if I’ll be able to maintain BarTab and if it will ever officially support Firefox 4.0. But thanks to Paul, one of the biggest reasons for having BarTab installed just went away!
Vertical Tabs 0.7
Vertical Tabs has received a few updates as well and is now at version 0.7. Compatibility with Firefox 4.0 beta 7 (now the minimum required version) and recent nightlies has been restored. The styling now works better when Personas (lightweight themes) are installed. Since Firefox removed the status bar, Vertical Tabs no longer rolls a custom status bar on left, either. Instead the tabs toolbar has been moved there, and it’s fully customizable. You can, for instance, put your Sync toolbar button down there! Lastly, the Tabs on Top menu item has been removed since that choice does not make any sense once Vertical Tabs is installed.
Try out Firefox 4.0 beta 7 now!
November 9, 2010
It’s been over a month since my last mega-update, so here’s an update of what I’ve been up to since then:
Shipped: Firefox Sync 1.5
We shipped Firefox Sync 1.5 which is also part of Firefox 4.0b7 and Firefox Mobile 4.0b1. It contains various performance and stability fixes, but the most visible change is the greatly simplified (and prettier) setup wizard.
The “secret phrase” has been renamed to Sync Key, a term that we think will be understood better by less technical people. By default it’s an auto-generated string of 20 alphabetical characters. Users are encouraged to securely back this key up by either saving or printing a document with the key on it, though we’re planning some further additions to the wizard that will hopefully make this unnecessary for most cases (see below.)
Storage version bump
Version 1.5 also included a storage version bump, IIRC the second one so far in Sync’s history. These changes to the storage structure are necessary once in a while usually for optimization reasons (in this case server migration), but the downside is that they introduce a clear compatibility cut. Since both Firefox 4.0b6 and Firefox Mobile 4.0b1 are lacking the necessary UI notifications to tell users to upgrade Sync, the storage bump became a bit of a hassle for users trying out the Firefox 4 beta. Fortunately this has been fixed for both Firefox and Firefox Mobile.
Coming up: Firefox Sync 1.6
Sync 1.6 represents most if not all upcoming improvements that we want to include in Firefox 4.0 and are working on right now. Note that the majority of these will only be available to Firefox 4 users because they depend on changes to the underlying platform.
Encryption off the main thread
Less synchronous I/O activity
This is an ongoing effort to improve the app’s responsiveness when Sync is tracking changes to the profile (e.g. new history visits), as well as during syncs, by making a lot of the I/O asynchronous. This includes Sync’s own I/O as well as queries to Places, Firefox’s bookmark and history database, to which we will probably be adding asynchronous APIs.
Easy setup for secondary devices
Setting up Sync on a second computer requires a lot of typing, pretty cumbersome especially on a mobile phone. We’re working on ways to improve that experience by securely transferring your Sync credentials from one device to another. One of the methods we’re exploring uses a PAKE (password-authenticated key agreement) algorithm whereby you enter a relatively small code that’s shown on one device into the other, and then the two devices agree on a stronger key that they’ll use to encrypt and then transfer your credentials with. Another method we’re looking at for Firefox Home users is 2d barcodes.
Right now Sync uses a PKI-like storage setup for the keys that the data is encrypted with. It allows for a lot of flexibility, but it also makes things unnecessarily complicated. What’s more, the additional cryptography is expensive and every additional key stored on the server means more network traffic. So reducing the number of keys and crypto steps will be good for both the client and the server. Going forward we’d therefore like to get rid of the PKI layer. We’d also like to always auto-generate the Sync Key, now with higher entropy. This means that users will no longer be able to choose their own phrase for the Sync Key, and that the length will grow from 20 to likely 25 alphabetical characters. Fortunately this will be mostly transparent to users as they won’t have to deal with the Sync Key most of the time anyway, thanks to the easy setup option.
This means another storage bump, so Sync 1.6 will likely not be backwards-compatible with Sync 1.5, but we hope that this will be the last bump for a while, so that it will be forward-compatible with Firefox 4.
Better sync timing
Right now Sync mostly syncs at predefined intervals while it could be more clever about when it syncs. Syncing more reactively after changes to the profile (e.g. user added new bookmarks) would improve the user experience a lot.
In other news
Relocated to the Bay Area
After having worked remotely for the first few months, I relocated to the Bay Area two weeks ago. I’m excited to join many of my colleagues at the Mountain View office. It has already paid off in the short time I’ve been here, particularly since I’m in the same (native) timezone as most of them now.
Podcast with Netzpolitik
While in Berlin I met Markus Beckedahl of Netzpolitik, a German blog on internet culture and politics. He wanted to interview me about my job at Mozilla in a podcast. In the podcast we talked a bit about what Mozilla is and what it’s like working in the Mozilla project. Of course we also talked about Firefox 4, Firefox Sync and various other things. Nothing an avid reader of Planet Mozilla wouldn’t already know, but if you speak German and like to listen to me answer questions (probably not always super well) for about 50 minutes, stay tuned. The podcast will be online soon, I’m told.