File dates should not be changed when they are moved to the POGO plug for several reasons:

1.  Presently, a file created locally has a date and a time that is commonly displayed and is used by programs (e.g., xcopy, etc.), size is in the equation, too, to determine if the local file is more current than the remote (POGO) file; and, vice-versa.

2.  When a file is moved to a POGO, the local and the remote date appear the same during the "session."  A reload, or a subsequent session, the files longer show the same date.  The local file retains its date; and, the remote file now has the date and time of the upload which could be days later.  This pecular situation happens mostly when using the desktop application.

3.  Local-To-Remote:  The date change makes it almost impossible to determine the status of the remote file because of the date tampering.

4.  Remote-To-Local:  The date change often results in a churn of the local files because the remote file has a newer date.  This wastes time and causes confusion when the same identical file on the remote seems newer only because of the date tampering.

My request is to have the remote (POGO) use the same date as that of the local file.

Another problem is encountered when making a visual inspection that attempts to compare what files on the remote (POGO) are not the same as the files that are local to determine if an update is, or is not, necessary.

Sure would appreciate the uploaded file's date being left unchanged!