Earlier quoted context omitted.
European here. When I state my date of birth I state it as “7th of October 1990”. 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 w…
YYYY-DD-MM as a folder / filename does not sort correctly. Not a fan. I much prefer YYYY-MM-DD for its sorting behavior.
Show HN: Markwhen: Markdown for Timelines
41–50 of 93 posts
Re: Show HN: Markwhen: Markdown for Timelines
#42Earlier quoted context omitted.
> It’s pretty convenient as the time periods uses the format YYYY-MM-DD/YYYY-MM-DD and I think is easier to mentally parse than MM/DD/YYYY-MM/DD/YYYY Especially for those outside the USA!
As someone who grew up in the US, it's still bizarre as a programmer to have a mixed-significance ordering (MM-DD-YYYY) instead of any consistently-endian ordering (DD-MM-YYYY or YYYY-MM-DD). Out of curiosity, in what order do Europeans verbally say full dates with month names? Or does it vary by language?
Re: Show HN: Markwhen: Markdown for Timelines
#43If 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?
Re: Show HN: Markwhen: Markdown for Timelines
#44This would enable a much appreciated Obsidian plugin, it seems a natural fit
Re: Show HN: Markwhen: Markdown for Timelines
#45I'm working on an MIT-licensed time-tracking tool in my spare time and I'm hoping somebody (in a "this is not legal advice"-capacity at least) can enlighten me on licensing here: 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?
Re: Show HN: Markwhen: Markdown for Timelines
#46Re: Show HN: Markwhen: Markdown for Timelines
#47And diffing to know what changed on git etc.
Re: Show HN: Markwhen: Markdown for Timelines
#48I'm working on an MIT-licensed time-tracking tool in my spare time and I'm hoping somebody (in a "this is not legal advice"-capacity at least) can enlighten me on licensing here: 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?
No, nobody can copyright a file format
Re: Show HN: Markwhen: Markdown for Timelines
#49If only this were a vertical timeline with a print-friendly format. Its great, but a guy can dream....