Grep the source for "1506" and a priority level. P5 is the highest, most
important stuff. Here's a key:

P0: Toggle mode code. It needs to die.
P1: Feature we could live without/do another way
P2: Mildly useful feature/enhancement
P3: Fingerprinting and linkability defenses; more useful features
P4: Important privacy features, including New Identity
P5: Proxy bypass/state leak issues

These priority levels will also be used to guide us towards a simplified,
toggle-free Torbutton (probably based on Proxy Mobile. See #1506).

We seem to need to keep a copy of the unsigned rdf to add new versions to the
signed one?

Thanks proper, for keeping us proper.

Also, include some language improvements from nickm.

Let's hope I don't lose this thing...

We launch a confirm dialog when they click on the button.

Wow, that was a close one. :/

We'll mimic but slightly deviate from Firefox 10.0.4 ESR's uagent. (Why do
they need a damn minor version in there anyways? Just so people can get owned
easier, or what?)

We were already pinging check in these cases for the update notice. Might as
well actually perform a versioncheck then, too.

Also, Roger didn't like the additional TCP connection and dirfetch overhead at
guards caused by a purely clock-based version check that happened even when
the browser was not in use.

There was an issue with the 5729 fix with windows closing out from under us if
the page load was stopped.

We check every 12 hours.

I also made the update check at startup async as part of this.

We'll leave the UI option to disable this there for one more release..

We should be loading the home page for new identity windows too, why not.
People need to know if they are out of date.

Resizing on new window creation is good enough.

I think we got it this time.

Also remove Scroogle. RIP, Scroogle. You will be missed.

The old toggle code was getting invoked to preserve pref updates, re-rounding
our 200x100 windows to 50px multiples..

It seems to get cleared eventually by nsICacheService.EvictEntries, but this
gets it done immediately.

Helps reduce fingerprinting linkability:
https://www.torproject.org/projects/torbrowser/design/#fingerprinting-linkability

Does not cause regressions for Ubuntu Unity.

Session IDs are disabled in a TBB patch.

20 seconds seems a decent compromise until we can properly isolate
keep-alive connections..

Throw up some alerts.

TBB-only fix.

Want to keep them in the git history, though.

We basically remove all the url-containing drag and drop mime-types from the
drag action. This seems to still allow you to drag stuff within TBB (because
it uses its own internal secret types), but prevents dragging to outside apps.

Both can always be overriden on startup using TOR_SOCKS_* environment
variables.