Use Timestamps

Value of visible timestamps

• Strong support for putting clear, human‑readable dates (and often times) on blog posts, docs, courses, and other content.
• Readers rely on dates to judge technical relevance, especially in fast‑moving fields (ML, dev tools, bureaucracy rules, etc.).
• Some commenters refuse to read undated pages or old tech posts without a visible date.
• Timestamps also help in personal notes (health logs, stress patterns) and in research, where many PDFs and preprints lack obvious dates.

Incentives and reasons for omitting or gaming timestamps

• Many sites hide or omit dates intentionally, to avoid looking outdated and losing clicks (SEO and “freshness” bias).
• Some news sites roll “last updated” forward without real changes.
• Example of a misused static timestamp causing conspiracy claims about “predicting” an event.
• A minority view: some texts are “timeless,” so dates are downplayed or placed at the end; others counter that truly timeless pieces are rare.

Precision, formats, and time zones

• Wide agreement: use an unambiguous standard like ISO 8601 / YYYY‑MM‑DD; month‑name abbreviations and MM/DD/YY cause confusion and localization bugs.
• Debate over whether a full timestamp vs. just a date matters for blogs; more important for breaking news, logs, or high‑frequency research.
• Calls to always show time zones, since dates can shift by one day across zones.
• Relative times (“2 hours ago”) are seen as convenient but often inferior for reporting, auditing, and cross‑time‑zone work; tooltips or user settings help.

Continuously updated texts and documentation

• For living documents (wikis, design docs, internal diagrams), people recommend explicit “accurate as of YYYY‑MM‑DD” text plus edit history or changelogs.
• Distinction between “last edited” vs. “last verified” is important; some government sites display both.
• Ownership and regular review of documentation, with timestamps and version numbers, are seen as crucial but often neglected.

URLs and browser UI

• Many tie timestamp transparency to URL transparency: URLs function like citations/identifiers and should be visible.
• Mobile browsers often hide most of the URL, especially on small screens, which some see as inevitable and others as a harmful design choice.
• Arguments for hiding: most users only care about the domain, full paths look like clutter, and people often treat the address bar as a search box anyway.
• Arguments against: hiding URLs (and filesystem structures) reduces user understanding and aids phishing; tools could make URLs more readable instead of hiding them.

Technical issues with timestamps in systems

• Timestamps are not inherently reliable for ordering events: limited resolution (e.g., millisecond granularity), non‑monotonic clocks, and time adjustments can cause duplicates or reordering.
• Recommended patterns: use separate sequence/order fields or IDs alongside timestamps; treat timestamps more as metadata than as a strict ordering mechanism.

Implementation ideas and minor points

• HTML <time> and metadata already carry precise timestamps, but they’re often not exposed to humans.
• Frontends can send UTC timestamps and render localized strings on the client with standard date APIs.
• Extensions and editor plugins can streamline inserting timestamps into docs.
• Some participants advocate consistent timestamping even beyond tech (e.g., “time‑binding” people’s statements over time).