Show HN: Markwhen: Markdown for Timelines
markwhen.com
markwhen.com
Of course I didn’t even know what a solidus (“/“) was until using iso8601.
Also, I usually find standards pretty much as overhead, but 8601 seems pretty good as a universal standard.
`2022-08-02T23:00:00.000Z - 2022-08-03T00:00:00.000Z: Event`
but in general I do need to figure out a way to allow more customizable date parsing.[0]
Especially for those outside the USA!
Out of curiosity, in what order do Europeans verbally say full dates with month names? Or does it vary by language?
Same in German.
In Polish, it’s the same, except for official matters since 2002, which now follows ISO8601.
Even in the UK they commonly say the 5th of May, and not May, the 5th (but it does happen).
I can’t talk about other languages.
The only time I see this is in the UK is on movie posters/trailer, e.g. "In cinemas May 5th", which I assume is due to re-using the US material.
PS: 5th of May is a degenerate example, since it's 05/05 regardless of ordering
PPS: 5th of May is also my birthday ;)
When a date is within the current year I state it as for example “27th of June”.
If weekday matters, and specific date is still relevant I’ll say for example “Monday 27th of June”.
I might also simply say “Sunday last week”, “Monday next week”, “Monday at the end of next month”, etc.
Likewise I might say “a couple of weeks ago”, “last week”, “a few days ago”, “in under two weeks”, etc.
Depends on context.
When including a date in a file name I prefer YYYY-MM-DD for date.
When using dates in a directory hierarchy I’ll have years on the top level, with months within them and dates within those.
Sometimes I might use a format like YYYY-mm-ddTHHMMz_s in a file name. For example “something_2022-06-20T1722+0000_1655745728_more_text.tbz”
I much prefer YYYY-MM-DD for its sorting behavior.
And ofc, the mixed order is the inferior option.
US English has several grammatical and pronunciation characteristics that were common in UK English about 300 years ago. Including being largely (but not totally) rhotic.
The numeric month and day of my birthday happen to be the same. For this anecdote lets assume it’s 01/01/1970.
When medical staff ask me for my date of birth, I’ll say “1st Jan 1970”. They’ll reply asking “Sorry, Jan 1st?” And I’ll say “yeah”. This blew my (programmer) mind.
Over the years I’ve rewired my brain to say “Jan 1st 1970” and avoid the extra round trip.
Same for the romance ones: It's just "Quatorze juillet" - 14th of July (Bastille day).
English is the weird one, but not that weird, "7th of october" is not much more complicated to say than "October 7th".
French in France: four twenties seven
French in Switzerland: eighty seven (octante sept)
Japanese uses a neat system akin to YYYY-MM-DD. 2022-06-20 becomes 2021年6月20日 meaning "2021 year 6 month 20 day". Really nice to read. Actual pronunciation is very irregular though, especially days of the month where about half of them are irregular.
I am from India and I say "21st of June 2022"
The "Algorithms to Live By" book has a good name for this: computational kindness. We should strive to reduce cognitive burden. The bigger the audience, the more effort should go into making data digestible. Unfortunately the established date standard goes against it.
The other problem is mixing endianness: the date information uses little endian, while numbers themselves are spelled out in big endian. The American MM-DD-YYYY on the other hand... I don't know what they were thinking.
'June twenty-second' ordering verbally is as distanctly American (not to say you don't hear it, as with many Americanizms) as it is in writing.
I’ve used it personally to help plan and coordinate my own wedding (https://markwhen.com/rob/wedding) and for keeping track of life events, and I’ve seen it used for event planning, project management, and to visualize historical events or periods of time.
I personally like tools that let you immediately start using them, and I set out to do that here with markwhen.
Let me know if you have any questions!
Did you build the timeline UI yourself? Can it be used as a library?
Once nice thing about Mermaid is it's built into [GitHub's markdown](https://github.blog/2022-02-14-include-diagrams-markdown-fil...) and has support in Notion
I'd happily pay for this as an Obsidian plugin.
Missed opportunity not naming it "Markdown for When (feat Lil Jon)
[1]https://upload.wikimedia.org/wikipedia/commons/1/1b/Linux_Di...
If I am understanding the AGPL-3.0 correctly (and assuming that the format is also under the license), I could NOT add an "export to Markwhen" feature to my project without then being forced to convert it to AGPL-3.0. Is this correct?
I'd be interested to see what you're working on!
> Dates: A date can be expressed in a few forms. Human readable dates are supported, like 1665, 03/2222, or 09/11/2001, as well as IO8601 dates, like 2031-11-19T01:35:10Z.
Ideally this would be an emacs package.
Does seem potentially cool and useful though.
https://github.com/kochrt/markwhen/issues/35
Awesome project. Thanks for sharing.
Other than that, you are making amazing progress! And fast also.
https://github.com/kochrt/markwhen/blob/main/LICENSE
> kochrt/markwhen is licensed under the GNU Affero General Public License v3.0
The upstream repo that the live site uses is available to sponsors.
So cheeaun here posted his life timeline project[0] 9 years ago (!) to hacker news[1] and I always thought it was pretty neat. I made a tool to make timelines like that and it has since evolved into markwhen.
[0] https://github.com/cheeaun/life [1] https://news.ycombinator.com/item?id=6833565
And diffing to know what changed on git etc.
Don’t be afraid to distinguish your tool from its inspirations.