|
|
|
|
|
by nickysielicki
2130 days ago
|
|
I can't stand to see this sort of logical inversion take place. There are exactly two possibilities: A. The timestamps weren't modified at all, and the modification time on the file truly represents the time at which they were written. ie: the timestamps are a roughly accurate indicator of transfer speed. B. The timestamps were modified, but the hackers specifically went through the effort to calculate timestamps that align with 23MB/s, and then set those timestamps on the files. Possibility B is much more contrived, is unfalsifiable, and yet you're defending it as if those that believe Possibility A are the real conspiracy theorists. In reality, you're the conspiracy theorist! You're saying there must have been an explicit effort (say, a conspiration) to set modification times to align with 23MB/s. It's ridiculous. |
|
1. The timestamps reflect some process that occurred before the files were uploaded to the internet.
That's it. That's the plausible explanation.
* Secondary transfer to removable media that changed timestamps
* Transfer to network file server, likewise
* Archival
* Compression/decompression
* Encryption/decryption
* Analysis of files that touched them (set timestamp) to indicate completion
Basically any process that proceeded at an average of 23MB/s would produce that pattern. And note, that it doesn't preclude the possibility that the timestamps changed many times between when they were on the DNC server and when they were made public. So indeed, the 23MB/s could indicate removeable media was involved, but it could have been from one Russian intelligence officer's computer to another's.
Occam's razor: the simplest explanation is the most likely one: The timestamps reflect a process that occurred at a rate of about 23MB/s.
We just can't speculate on what process that is.