Ok, thanks, I get the idea. So you wil have 24 hrs and get full credit for the previous protein, and up until 48hrs you will get half credit (just in case). This will be effective AFTER the next protein update (so the current protein will still be invalid as soon as we changeover).

I would like to try to address the problem of people with lots of computers but that only run the software nightly. If you start it up on all your machines with a cron script or something all at the same time, they will all download at the same time and wastefully clog the network. Having an intermediate local server to put the update on would be an interesting idea but can anyone propose exactly how this might work with minimum hassle?