About Time
What a Unix timestamp is
A count of seconds since 1 January 1970 UTC, which is why it is also called epoch time. It has no timezone and no formatting — it is one number naming one instant, which is exactly why software stores times that way and people find them unreadable.
The common trap is the unit. 1700000000 is seconds and lands in 2023; the same digits read as milliseconds land in 1970. Most languages hand you milliseconds and most APIs want seconds.
Now, or a moment you pick
Now reads the clock, once a second. There is no interval to set here: how often something should happen is a different question from what the time is, and it belongs to its own block.
Fixed takes a moment from the picker or from the box beside it, which reads a Unix timestamp, an ISO 8601 string, an HTTP date or a plain YYYY-MM-DD. Wire something in and that wins over both: the same block reads a JWT expiry or an ID timestamp without any conversion in between.
Fixed is also the mode to use in a bode you intend to share: the person opening it sees the same moment you did, rather than their own clock.
What comes out
Two values: the ISO 8601 string in UTC, and the Unix timestamp in whole seconds. ISO is what the rest of a bode passes around, so this wires into anything expecting a time — including the outputs of the JWT and ID blocks, which are already ISO strings.
A shared bode never carries the live reading. That value belongs to the session, so whoever opens the link reads their own clock rather than a note of when you happened to build it.
Common questions
- How do I stop it changing?
- Switch to Fixed and pick a moment. That is also what you want in a bode you intend to share or keep, since a live reading is never saved — the block would simply read the new reader's clock instead.
- Which timezone is it using?
- Your own, for anything shown on screen, and the card names the zone so there is no guessing. The values it passes on are always UTC, which is the only way two people in different places can agree on what a bode means.
- Does the fixed time include seconds?
- The date field is accurate to the minute, which is what a picker gives you. If you need an exact instant, wire in a timestamp from elsewhere — a JWT expiry, an ID timestamp, or text you paste.
- Is anything sent anywhere?
- No. Reading the clock and formatting a date happen in your browser, and this block makes no network requests at all.