timescale.info
Sign inSign up

How OpenChronology was built

Every merged pull request of openchronology/timeline-app, its first week of commits and its releases; and before them the 2020 PureScript editor, from snapshots of its deleted repositories in the Wayback Machine. Written to this server through the HTTP API.

327 moments · 2020-03-09T00:15:08Z CE – 2026-11-02T20:11:21Z CE · by @athan · @athan

Issue #18 · Minimizing Storage of Time Index

  • 2020 editor
  • issue

A time index will be stored in a different type than what is presented to humans - most will end up as a Number, but some may end as an Int as well. When storing these values in binary, they should take up minimal space - if a timeline only lasts for less than 256 years, then the year field should only be one byte. This implies that a timescale has bounds, however, and migrating from one to another (i.e., making one event that exceeds the 256 bound, or changing the bounds) may cause a hiccup. However, this should be possible. The goal that this applies to would be for link sharing - making the stored value minimal. *Archived by the Wayback Machine on 15 September 2020; the repository has since been deleted from GitHub.*

Sources

Open Issue #18 · Minimizing Storage of Time Index in the timeline