Anonymous ID: d22d04 Jan. 10, 2018, 8:44 p.m. No.18619   🗄️.is 🔗kun   >>8720 >>8990

>>18395

Up until Nov 5th, 02:00 (EDT) the shift from GMT was GMT-4. After that GMT-5.

The message 147023341 is from 18:15:48

(EDT) or 22:15:48 (GMT). The tweet is from 23:15:39 (GMT), which makes it 19:15:39 (EDT).

You can see for yourself in your browser by searching the 4chan HTML source code for the GMT/Zulu times.

Anonymous ID: d22d04 Jan. 10, 2018, 9:07 p.m. No.18815   🗄️.is 🔗kun

>>18735

I wouldn't know, but there is some in the src saying data-original-time="4chan Time […]" but only HH:MM format and GMT-5.

Webpage/Browser takes accurate times (HH:MM:SS) from GMT timestamps. (my PC's timezone is GMT).

Anonymous ID: d22d04 Jan. 10, 2018, 9:12 p.m. No.18861   🗄️.is 🔗kun

>>18735

>>18785

Correct. Unix time, which is defined as seconds elapsed ssince 1970-01-01 00:00:00 (so you can do math with it easier). The unix seconds shown are equivalent to the ZuluTime visible.

Anonymous ID: d22d04 Jan. 10, 2018, 9:19 p.m. No.18921   🗄️.is 🔗kun

>>18766

Had been discussed quite a bit. But times show up on your screen depending on which timezone your OS's time is set.

Conversion to EDT is done by the browser automatically.

You can cross check easily with other data sets, such as the meta files from the batter

>anonfiles.cc/file/884cb98b49b4e8da18087c3edc3df21f

Anonymous ID: d22d04 Jan. 10, 2018, 9:24 p.m. No.18965   🗄️.is 🔗kun   >>8990

>>18395

>>18912

TrumpTwitterArchive (GMT):

>Twitter for iPhone,JFK Files are released long ahead of schedule!,10-28-2017 23:15:39,20238,95386,false,924414387343028224

 

Message header (in GMT):

>Anonymous ID:BQ7V3bcW Sat 28 Oct 2017 22:15:48 No.147023341

 

Message header (in EST/EDT):

>Anonymous ID:BQ7V3bcW Sat 28 Oct 2017 18:15:48 No.147023341

 

How can two different times (in GMT) become two identical times (in EST/EDT) ?

Anonymous ID: d22d04 Jan. 10, 2018, 9:33 p.m. No.19020   🗄️.is 🔗kun

>>18990

As far as I unerstand webpages, they are coded in HTML, where the time of posting (and post content) are translated into HTML and the browser interprets these timestamps (which are zulu time).

Conversion does the browser, as he knows that DST switch is always first Sunday in November 02:00:00 (last Sunday in Oct in Europe, I believe).

So thepage doesn't "self-correct", afaik.