>>5607664

>But that doesn’t account for Twitter server pass-thru time delay, now does it?!?

If Twitter assigns time upon receipt, rather than after process and output, then it's no problemo.

>>5608246

>Still nothing explained

landed in china as initially reported…

>>5608264

>Thats one version of many

it was the first, and everything else since was a cover up