So, I created a new FEED called @carsten_de@yarn.zn80.net which will hold the German-speaking content. I don’t know if I will be posting content double.
I was thinking about it the other day.
Twtxt spec requires the Z (Zulu) Timezone. But what about posting the local time, and the server/client makes the conversions.
That’s even better if you travel around and your local Timezone changes often.
Then you can show the Timezone based on the last Twt. Is not as specific as having a ICANN Timezone, but I think is precise and dynamic enough.
@prologic@twtxt.net no worries, my point goes on saving the Timezone on the Twtxt file, instead of adding a Metadata (which is going to be outdated if you travel to another Timezone)
That way, the CLI tool or Yarn could take the current Timezone convert it to your local time and say “this user has this Timezone, is X hours behind you, it’s 4am for them”
I’m reading in a twtxt spec that the time offset is allowed and I remember somewhere else asks to use the Z timezone (UTC). I’m confused now.
https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html#format-specification