notesutils VS markwhen

I should write this stuff up, but I haven't.

I do have some brief notes on the "Notes.app" format here:

https://github.com/dunhamsteve/notesutils/blob/master/notes....

But I didn't discuss my methodology -- Generic decoding of protobuf, building up a schema as you go -- the tricky part there is that a byte array and a substructure look the same, so you have to try to decode it, and if successful, try that schema on the next example.

Here is another fun technique - scanning through a disassembly of an Apple framework looking for assembly patterns that match the protobuf compiler output (this was dependent on which language was targeted by protobuf):

https://gist.github.com/dunhamsteve/224e26a7f56689c33cea4f0f...

So you find the serializer / deserializer code and figure out what the original protbuf spec looked like.

The creator of this (Chee Aun) is quite prolific and creative with their work (https://cheeaun.com/projects/).

They created https://cheeaun.life, a timeline of their life, more than 10 years ago (which looks to be kept up to date), which was my inspiration for markwhen (https://markwhen.com).

Markwhen

Looks like markwhen[0]. When making it, which initially started out as a strictly timeline-making tool, I realized it is essentially a log or journal language - write a date, any date, and add some stuff to it. Good for notes, blogging, a calendar, etc etc.

[0] https://markwhen.com

https://markwhen.com

I’ve had a lot of these thoughts when working on markwhen. It’s basically turning into a calendar and planning IDE, pretty excited about where it’s heading.

https://markwhen.com - very cool. however, If I could share with you, I would see the value in following case: if I could connect my calendar(s) to it and see what is going on and overlay it with the data here in comment. Use case is both - for retrospective and for planning (for example if you're preparing the meeting and don't want to share content just yet, or jotting something for time in-between meeting what to do, etc)

I realized just over the weekend that the side project I'm working on is in fact a kind of journaling language. It has passed through a number of iterations, started out as a timeline maker (and still does that best), but at the end of the day is a spec for writing what happened when. Or indeed what you hope will happen in the future - I find it's a good planning tool too.

I find myself actually journaling now that I don't have to think about where I'm going to do it, or in the case of most note-taking apps, which note I should put my current thought in. Journal it first, and if it deserves to be somewhere else, move it later.

The project is https://markwhen.com

https://markwhen.com

Timelines in markdown (gantt, calendar, map, other views)

It's open source (https://github.com/mark-when/markwhen) and there are some paid options for storing markwhen documents in the cloud.

Straddling paid SAAS and open source is a bit tricky and I still haven't figured it out completely yet. I have some sponsors as well as some paid saas clients but it's not quite paying the bills yet... I like working on it though, hopefully I can find the right balance or a different revenue model that works better.

Are you familiar with markdown? If so, try markwhen.