Perform versioncheck periodically in background

Torbutton should perform an async XMLHTTPRequest TBB version check periodically, so that new windows show an updated Tor check status message.

changed milestone to %TorBrowserBundle 2.2.x-stable

added MikePerry201205 actualpoints::3.5 component::torbrowserbutton milestone::TorBrowserBundle 2.2.x-stable owner::mikeperry points::3 priority::high resolution::fixed status::closed type::enhancement labels

Trac:
Keywords: N/A deleted, MikePerry201205 added

This is done. We check every 12 hours. I also made the initial check async as part of this.

Will appear in 1.4.6.

Trac:
Status: new to closed
Resolution: N/A to fixed
Actualpoints: N/A to 3
Points: N/A to 3

Uh oh. This behavior will undermine Tor's "go dormant if the user isn't doing anything over Tor" behavior, yes?

How about we export whether Tor is dormant via the control port (#5954 (moved)), and then you can change the "if (++this.update_counter > 720)" section to check the getinfo (if available) before proceeding?

Trac:
Status: closed to reopened
Resolution: fixed to N/A

arma: Firefox has been torpedoing us for a while now and no one seems to have noticed. It already performs addon update checks every 24 hours, and safebrowsing updates at some similar frequency. Would you like me to change it from 12 to 24 in Torbutton, too?

Alternatively (or in addition?), I can launch an async request every time the user does New Identity or opens a new window. Check.tp.o is already loaded in these circumstances.

I wonder if that accounts for the growth in https://metrics.torproject.org/network.html?graph=dirbytes&start=2011-02-24&end=2012-05-24&dpi=72#dirbytes

Ok, I've gone ahead and moved the async check to each New Identity and New Window invocation instead.

You might want to open another ticket for the addon updater. Not sure how we want to handle that.

Trac:
Actualpoints: 3 to 3.5
Status: reopened to closed
Resolution: N/A to fixed

closed

changed time estimate to 24h

added 28h of time spent

mentioned in issue #5954 (moved)

mentioned in issue tpo/core/tor#5954 (closed)