For one of my open-source investigations, I need to demonstrate user profile creation date and time for a wide audience.
It is a common knowledge that Twitter legacy design shows timestamp as a hover JS tooltip. However, now as legacy design is only available with Googlebot user agent, the timezone seem to vary from profile to profile between GMT-7 and GMT-9. See screenshots below (I’m always in GMT+3, which is relevant for twarc | jq output).
Is there a determinate, end-user friendly way to understand what timezone is used for a given user profile?
Or is there a way to get a fixed-timezone result?
Sorry for being offtopic a bit; I failed to find a more relevant place for this question.
As far as i can tell, on the web, this is formatted as whatever timezone the browser reports (usually this is OS locale settings).
The definitive data is in the API, in created_at property in the user object and is always in UTC. All dates on twitter API are always UTC.
eg, for jack:
In v1.1 API it’s "created_at": "Tue Mar 21 20:50:14 +0000 2006" (+0000 means UTC)
In v2 API "created_at": "2006-03-21T20:50:14.000Z" (Z is UTC)
So when you run your script, you’re getting the output in your time zone, not in UTC. (I don’t get the point of mktime in your script, but you end up with your local time instead of UTC)
