[QUOTE=chalsall;588610]Been there for as long as GPU72 has existed. (Not meaning to be mean or anything, but I believe it was actually you who asked it be rendered as UTC rather than AST many years ago...)[/QUOTE]

Not the first time; won't be the last time I've had a senior moment.

[QUOTE=chalsall;588607]I don't really understand the feature request/bug report.
<snip>
With regards to the report being out of sync with Primenet, that will (almost) *always* be the case. GPU72 only "spiders" Primenet twice an hour to get updates wrt factors found and P-1'ing/TF'ing completed.[/QUOTE]

When the report says "Updated: xxxx UTC", I expect all the results reported to primenet by xxxx UTC to be there. If that is not the case can you please give a "Data as of" time as well which represents the last time primenet was spidered?

I don't really care what time report was generated. I only care how recent the data actually is.

[QUOTE=axn;588643]I don't really care what time report was generated. I only care how recent the data actually is.[/QUOTE]

I hear your reasoning for the change request. Having thought about it, I'm going to remain with the current code paths.

There are many clients (read: workers) who interact with GPU72 by way of direct IPC. The Colab TF'ers and P-1'ers for example.

The timestamp on the report at [URL="https://www.gpu72.com/twok/"]https://www.gpu72.com/twok/[/URL] should perhaps be interpreted as the knowledge GPU72 had at that moment in time. One hour resolution is the same as provided by Primenet for many of its reports.

I hope and trust this is acceptable, taking into consideration the computational and bandwidth constraints of the IPC between these two systems.