51–60 of 102 posts
Any chance you can copy some of this for aesthetics? https://www.chronoflotimeline.com/timeline/shared/3118/Home-...
Hopefully without the latency, it's slow to respond on a 2022 M2 Macbook Air (tried Firefox and Safari)
Be careful. Gruber (who has trademark in “Markdown”), appears to not like people using his trademark name. https://blog.codinghorror.com/standard-markdown-is-now-commo...
Not only is this a different name, but that was an attempt to essentially expropriate Markdown. This is nothing even close to that.
Earlier quoted context omitted.
Not only is this a different name, but that was an attempt to essentially expropriate Markdown. This is nothing even close to that.
It’s plausible that it could be a trademark issue, were “markdown” strongly enforced. “When” isn’t the furthest from “down”. However, the reason behind Gruber’s issue with it has been misinterpreted and the Markdown name is very widely used without any arrangement with its creator, and a trademark for Markdown is not registered with the USPTO by its creator AFAICT.
Correct. Not to get too in the weeds on a 10 year old controversy, but Gruber has gone on the record to say he is cool with things like GitHub-flavored Markdown but from what I gathered back then and since then whenever he spoke on the subject (which has not been a lot), his issue with the CommonMark project (as it would eventually be called) using any name that included “Markdown” in the name wasn’t cool with him since they went ahead with an ask forgiveness instead of receiving permission approach on attempting to basically expropriate Markdown. GitHub-flavored Markdown and things like it don’t do that, they just claim to be a different kind of Markdown.
Also never understood why he didn’t just go ahead and trademark it, but at this point would it even be enforceable? It’s kind of generic now, but I don’t know if it’s generic enough to not be enforceable either, and maybe he doesn’t want the obligation of having to enforce it.
EDIT: anyway, point is, this is so far from being Markdown or claiming to be that I don’t think there is a single issue with Markwhen as presented that would ruffle any feathers in Philly. The creator shouldn’t have to worry and nobody should be telling him to worry. Like, seriously, none of this is relevant. Markwhen is just a cool looking thing that exists now and I like timelines.
This is neat! It reminded me of this project by cheeaun that enables one to create a visual timeline based on a simple texted based format. The purpose was to plot one's life events in a visual way. https://github.com/cheeaun/life Sample file (from the repository): @USERNAME's life =============== - 24/02/1955 Born - ~1968 Summer job - 03/1976 Built a computer - 01/04/1976 Started a company - 04/1976-2011 Whole bunch…
Right now I'm using YAML for the file format, as I wanted something that would be reasonably readable for both humans and machines. Markwhen would also fit the bill nicely, so that's something to consider, at least as an export format. My entries have a lot of properties, though (stuff like wind speed, vessel coordinates, barometer, etc). Traditional ship's logbooks were done in a tabular manner to record all this. So I'm not sure if that would end up looking quite messy. Here is an example of a day of log entries in the current format: https://github.com/meri-imperiumi/log/blob/main/_data/logboo...
I'm using these also for some data analysis, like watermaker membrane health, or sailed miles per crew member.
Earlier quoted context omitted.
Hopefully without the latency, it's slow to respond on a 2022 M2 Macbook Air (tried Firefox and Safari)
That's weird. It works perfectly for men much older computers and also on my M2 Mac Pro. What version of OSX are you using? I created that product, btw.
Why 2025-01-22 / 2026-10-24?
Why not 2025/01/22 - 2026/10/24?
This is neat! It reminded me of this project by cheeaun that enables one to create a visual timeline based on a simple texted based format. The purpose was to plot one's life events in a visual way. https://github.com/cheeaun/life Sample file (from the repository): @USERNAME's life =============== - 24/02/1955 Born - ~1968 Summer job - 03/1976 Built a computer - 01/04/1976 Started a company - 04/1976-2011 Whole bunch…
That is a great project! I wonder if anyone has created a visualization that uses a "life in weeks" format (like https://waitbutwhy.com/2014/05/life-weeks.html ) rather than a linear horizontal timeline.
Things like Markdown work because they are intuitive, but the date range syntax in Markwhen is anything but intuitive. Why 2025-01-22 / 2026-10-24? Why not 2025/01/22 - 2026/10/24?
(that's why it uses dashes for dates, as for why it uses / for interval I have no idea)