>>19802

Yes, you're right that they would all be funky. It's obviously not showing GMT-11

But, for whatever reason, twatter is not preserving the settings at GMT.

So, is an adjustment being made?

Why it's not sticking?

The ttarchives do export at 23:15, correct.

HOWEVER, the time in the ttarchive is showing 6:15pm or 22:15

It is one hour behind EST linked tweet.

The more current archived tweets since bouncing out of DST are on par with EST tweets.

So, let's explain these discrepancies.

Because they are critical to the CLOCK and all archived material, anonfile xls, pastebin, etc

This is not an easy shut case, and the implications for future research and correlations are big if wrong.

Let's not be so eagerly dismissive, but let's continue to crosscheck each other.

It's ok to make a mistake.

That's why WE are here.

>>19771

attacking the source is not a logical argument

explain where the conversions I did are wrong.

Can’t dismiss based off of “muh source”

Too much riding on it.

The [0] graphic may need to be adjusted to 22:15 GMT UTC/10:15 GMT – IF time conversions are correct.

And we may need to revisit anonfile, how we handle ttarchive export, etc. for timestamp comparisons.

>>19918

Note, it may be that my original mistake was not a mistake, I first got EDT by looking at the source code for archive4plebs which was data original -4:00

and it is likely that the Q OP was indeed 22:15 GMT-UTC/10:15 GMT-UTC

As two anons have very graciously contributed using Tor.

The problem now is the twitter discrepancies.

>>19942

Yes, that is what is being accounted for. It was done at 6:15 EDT, which is why it is one hour behind the EST linked tweet.

JUST LIKE

The Q post is 22:15 UTC (verified)

So is the twatter at 6:15 EDT (why it's one hour behind EST)

WHICH IS 22:15 UTC

Search the archive at

trumptwitterarchive.com for tweets "JFK"

See the date.

Then click the link to tweet. It explains the hour time difference.

I believe it's likely the ttarchive export is maladjusted.

>>20002

good idea. thank you.

>>20027

After you changed the settings and hit save, did it default to GMT-11, the first selection in the option tree?

When you change it to EST and save, does it default?

Why is GMT option not sticking?

Because it's not showing true UTC, and instead doing a conversion?

Possible?

Or is it just that a 10 Billion dollar company is unable to get their option trees and settings to stick?

Hrm.

>>20002

I think Anon is right Zulu, no conversion.

But twitter might be doing a GMT localtime conversion.

>>20127

>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)

Did you read the ttarchive timestamp disclaimers?

FROM: www.trumptwitterarchive.com/about

What's the deal with the timestamps? Are you sure they're accurate?

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, and the website translates that to Eastern Standard Time, which is 5 hours behind. Unfortunately, not all his tweets come with location data, so I'm unable to further translate a tweet 3 more hours behind if he tweeted from California (PST). It's an imperfect system, but likely the most accurate.

But when I look at a tweet timestamp on Twitter.com, it seems like it doesn't match with your site…

That might be true. Twitter displays tweet times to me in PST even though I live on the east coast.

So it's not a particularly accurate gauge, since it also attempts to do some time zone adjustment itself.

>>20127

>>20147

>>20159

>>19918

>>20080

Still looking for a definitive answer to this, fwiw.

Twitter user GMT-UTC time setting save unresolved — since 2016.

Describes the issue exactly, confirmed here.

webapps.stackexchange.com/questions/83005/why-cant-i-set-my-time-zone-to-utc

>>20356

Oh, I totally get the how.

just not the why.

why a 10 billion dollar co

1) removed UNIX timestamps

2) can't seem to get their db right.

>>20410

>>20410

Agreed. it’s precisely because the twatter GUI is both incompetent and unreliable, that I have questions.

“All the raw data is stored with a GMT timestamp, and the website translates that to Eastern Standard Time, which is 5 hours behind.”

www.trumptwitterarchive.com/about

The raw data from their site on CSV export, is agreeably 23:15 or 11:15 GMT. Twatter shows the same with GMT-UTC settings.

If the website translates ALL data to EST, then we should expect to see 6:15 PM EST on their website.

Which we do… well we see 6:15

But, that time is wrong for the date, which should be in EDT.

One problem is, I think, ttarchive changing all times to EST and not EDT where applicable on their site, for example.

Otherwise, their site would correctly read (23:15 -4) 7:15PM —EDT.

Which ODDLY, is actually what twatter is showing for the tweet with user settings at EST.

Can any anons explain this?

I mean, I know I’m dyslexic, but didn’t think I was retarded.

Tell me it’s not weird, and pls. Spell it out to me like a child.

www.timebie.com/timezone/utcedt.php

>>20522

So there is not only the question of why the ttarchive site is all whacky (and maybe also their API calls, dunno)

But, also, what is wrong with this time conversion if twitter is showing 7:15 EST.

Has not been answered.

>>19679 pics here

POTUS tweet in twitter pic settings EST.

7:15pm EST is 6:15pm EDT

6:15pm EDT is 10:15pm GMT

10:15pm GMT is 22:15 GMT

Which MATCHES Tor confirmed Q post at 22:15 GMT