Couldn't we have the node immediately check for the revocation key when it finds a new update and wait for the revocation key check to return before displaying the update button? Admittedly there would be a tiny chance that the key could be blown in between when the revocation was checked for and when the user actually updates the node but it would offer a much nicer user experience. Maybe a compromise and have it do 3 checks before showing the button and only one after the user clicks the update button?
On 6/20/06, Matthew Toseland <toad at amphibian.dyndns.org> wrote: > On Sun, Jun 18, 2006 at 08:13:44PM -0400, Joel Salomon wrote: > > How is auto-updating supposed to work? I have auto-update > > notification enabled, updating disabled; should I be able to click > > "update" on the local node web-page and have the node update? (It > > claims to be doing so...) > > Yes, but it doesn't work instantly. It has to run a final check to > determine whether the update really is genuine (the key hasn't been > blown). This involves fetching the revocation key 3 times which can take > a while. > > > > Thanks, > > --Joel > -- > Matthew J Toseland - toad at amphibian.dyndns.org > Freenet Project Official Codemonkey - http://freenetproject.org/ > ICTHUS - Nothing is impossible. Our Boss says so. > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (GNU/Linux) > > iD8DBQFEl++9HzsuOmVUoi0RAk2kAKCERdXa2WxmNsKL+kXak22jYh/sXQCglXZ4 > /XVyGbuwE1XEHNuZoIH/gHo= > =tcQx > -----END PGP SIGNATURE----- > > > _______________________________________________ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe > > -- I may disagree with what you have to say, but I shall defend, to the death, your right to say it. - Voltaire
