dChan
Anonymous ID: cece7a Jan. 11, 2018, 12:36 a.m. No.19942   🗄️.is 🔗kun   >>9984

>>19918

What's getting you guys all confused is the tweet was originally posted while DST was in effect.

It no longer is. Time shown in archive now for EST is 18:15 [UTC -5:00].

 

This is why it's so critical to compare UTC timestamps ONLY when computing detlas (then convert back to a baseline EST) for making graphics.

The only reason we're running into this for this particular alleged marker is that it happened during DST. It isn't an issue for any others because they all happened AFTER reverting back to standard time.

Anonymous ID: cece7a Jan. 11, 2018, 1:16 a.m. No.20127   🗄️.is 🔗kun   >>0147 >>0317

>>20080

The setting takes effect regardless of what Twatter displays in the menubox after you hit save. There are no conversions being performed.

 

And most importantly, it is in agreement with output from TT archive.

 

If you want to know why twitter can't seem to handle displaying the setting correctly after committing changes, get a hold of @dark_15. I hear he likes to talk.

 

Most importantly, the output as an effect of the twitter settings change is in agreement with TTarchive both before and AFTER DST cutoff (11-05)

Anonymous ID: cece7a Jan. 11, 2018, 1:26 a.m. No.20153   🗄️.is 🔗kun   >>0159

>I collect metadata on each tweet via Tweepy and Twitter's official API, which returns a "created_at" date in Greenwich Mean Time (GMT). All the raw data is stored with a GMT timestamp

This is the only part that matters as far as I'm concerned but thank you for pointing out that adjusted timestamps aren't necessarily arbiters of truth. Appreciate it, anon.

Anonymous ID: cece7a Jan. 11, 2018, 2:36 a.m. No.20356   🗄️.is 🔗kun   >>0398

>>20317

Since you seem stuck on this… inspect the source HTML for when you have your account set to EST vs UTC time. You will notice the option in the dropdown menu has the selected attribute set for when you set it to EST (or any other non GMT[UTC]) timezone.

You will also notice NONE of the options (neither [UTC-11], nor [UTC] have the selected attribute set when you change and commit to UTC time. UTC-11 is displayed by default merely because it's the first item in the list.

This is a post-database error. Either in the javascript or CGI. Someone forgot to apply the selected tag to the html on case UTC after the setting is read from the database.

Anonymous ID: cece7a Jan. 11, 2018, 3 a.m. No.20410   🗄️.is 🔗kun   >>0522

>>20398

It has nothing to do with the database. That part functions as expected. Someone is missing the case in the switch statement for when the page html is generated. They're too lazy to fix it because everything works as expected (other than the confusing appearance of a completely different timezone setting displayed). Because how many users even set their accounts to UTC? They can't be bothered with that shit. They've got laundry lists of accounts to creatively censor.