I don’t see why we shouldn’t require this on discord as well.
Also, as an example, to create a timestamp in discord you put a unix epoch timestamp inside <t: > like this: <t:1670355000>
2 Likes
For the technologically illiterate among us, could you explain what this is and how one is created?
This is a standardized format that computers use to keep time that ignores all time zones and the like. Technically, it’s the number of seconds since the “unix epoch,” which is January 1, 1970, at 00:00:00 UTC. It’s what Discord uses to display times in each person’s timezone.
In a practical sense, there are a number of tools you can use to generate these. I think Discord might have one themselves these days (?) but I usually use https://sesh.fyi/timestamp/.
1 Like
This amendment seems sensible. Full support from me.
I do think it would be a good idea to pin one of these tools somewhere on Discord.
1 Like
This or a coco/other bot tool to generate them in Discord itself.
I believe on desktop, typing @time will also allow you to type in a date/time to create a timestamp rather than needing a unix timestamp.
This seems like a power-user feature that at worst requires understanding what a “Unix epoch timestamp” is and at best requires an outside tool.
Do we really need to legally require this?
Given that this covers only legal deadlines, I think we should be legally requiring it. For the average TSPer it’s going to be helpful, and the number of people publishing legal deadlines is low enough that I don’t have any concerns about them being unable to learn or be taught the knowledge needed to do this. I’d be happy to write out an explanation for the Addendum too for those who would need it.
Before anything, at my knowledge, (2) should be (1b) and (1) as (1a). Also if we have a procedure we should have a timezone, because TSP is international and the fact that in the same office no one is in the same timezone could lead to problematic issue on administrative things.
So I would vote yes if it’s contain a timezone preferably UTC+0.
I recall a time when we simply just posted Eastern (American) Time, Sydney Time, and Greenwich (London) time…
As a central (American) time user, I know to subtract an hour when a specific Eastern time is given… just as Europeans/Africans know to add or subtract an hour and as many Asian nations know to do the math to Sydney or Greenwich time.
I am not strictly against it (and would vote for it), but why are we continuing to make things more complex?
How is adding three different timezones to each post less complex than using a built-in Discord date feature that shows the local timezone for everyone?
It’s literally just @time now.
2 Likes
It’s not. I would argue that people who think it is more complex do not actually understand what it is, how it works or that it doesn’t require an effort. They can’t be blamed for that, take me for an example, I am not the brightest pea in the pod myself, I know what I know of computer science and coding through my brother who is a qualified computer scientist and working in computers in his job, ordinarily, on my own, I haven’t a clue.
1 Like
Unformal hours, some procedure are written like this : you should do this at Noon, but their is 26 timezones in the world so it could be the author POV, or my POV. Putting an official timezones which is UTC+0, would definitely finish the problem.
I motion this to vote
Second.
1 Like
I oppose. I write an another version.
This resolves the timezone problem if it isn’t specified.
1 Like
So.. what’s the point of this? Like I get the vision, but see no benefit. In fact, just adding AB:CD AM/PM UTC+0 would be quite confusing for some people, ESPECIALLY for those who live in a place which practices daylight saving time.
Discord accepts Unix timestamps and displays the local time using the device’s local time, usually UTC but can also be GMT. It is very clearly the more organized solution, and opposing it because it’s “too complicated” or something is ridiculous (considering how easy it is nowadays).
This version completely cuts out the discord timestamp amendment to propose something completely different.
In terms of timezones, those are only necessary when you’re not using timestamps, so are only relevant on site. Failure to include a timezone is a failure to give a time anyways.
Additionally in terms of dictating an official timezone, why UTC specifically? Yes there’s the argument of UTC+0 being a “neutral” time in that it is the arbitrary zero some person decided, but that does not make it equally convenient. It’s a time that favors those who don’t practice daylight savings, and is easier to calculate from for those in Europe. Eastern Time serves a larger section of TSPers, being easy to calculate from for those in the US and for American daylight savings. We also have whatever time zone Sydney is in (or really any Australian time zone), which while it may not serve as large a section, is culturally appropriate in the sense of ‘the South Pacific’. We are also not restricted to naming one time zone. We could require listing times multiple time zones. We could also just specify timezones are required when listing times and leave the specific timezone up to the authority posting the date.
Additionally, this timezone amendment should specify it is only for legal deadlines to stay in line with the current law’s deference to its scope.