Anonymous ID: d26ba3 Jan. 4, 2018, 10:15 a.m. No.242131   🗄️.is 🔗kun   >>2144 >>2179

>>241779

>>241803

The edited version is right here:

anonfile.com/48n9u4d5bc/q_raw_edit.txt

 

Made all changes from the pastebin – can you do some simple Ruby-comparison between your old version and this one ?

Only thing diff should be 59 + 3 message headers.

Anonymous ID: d26ba3 Jan. 4, 2018, 10:50 a.m. No.242342   🗄️.is 🔗kun   >>2391

>>242298

>>242289

Yes both boards – it's in the nature of setting up a webpage: You define all times as Zulu times (i.e. GMT) and let the user's browser do the conversion by some small piece of code, like "<date local=true>" or such ….

I've checked original HTML from both, 4ch * 8ch, and in both it's coded similarly.

 

The browser should also know when daylight saving starts/ends (one would think) … so I wouldn't think it's much of a problem with the timestamps.

 

You can quickly check it by comparing your timestamps of your messages on 2017-Nov-05 around say 1-3 a.m, because the switch was at 2 am.

So before 2 am all msg should have 4 hrs diff to GMT, at & after 2 am 5 hrs.

Anonymous ID: d26ba3 Jan. 4, 2018, 11 a.m. No.242422   🗄️.is 🔗kun   >>2443

>>242391

Sorry for not making clear, yes it matches up, if SA took q_raw.txt as input for his spreadsheet and the timestamps therein.

 

If SA took independent source (like his own browser/research) he might even not have that problem.

Anonymous ID: d26ba3 Jan. 4, 2018, 11:12 a.m. No.242501   🗄️.is 🔗kun

>>242443

I see … won't be that bad I'd think. Just checked the spreadsheet and the four messages around the DST switch are fine but weren't in the q_raw.txt.