I want to keep a journal, I have two requirements:

1. The data must be stored as plain text and pain images on disk.
2. The entries must have date, time, location and ideally weather information.
3. I want to be able to pick an image, and create a journal entry from it. The entry should use the image’s metadata.

I first started journaling with Day1, but then it got sold, and I have lost faith in its future. Since they use some proprietary database with limited export options, I’m trying to avoid it.

Apple’s Journal looks interesting, but it does not satisfy my conditions 1 and 3.

I looked into self-hosted options:

• Journiv¹ — terrible frontend, database instead of markdown, asinine features like “reflect now” that can not be turned off.
• Obsidian — would be great but does not support 3 and on iOS doesn’t nicely sync outside of their paid sync service.

Diar - iOS shortcuts for authoring journal entries

Squinting at what I wanted I realized that I could probably cook something up. What I need is a Hugo² blog with a login and different syntax + some goodies, and a couple of iOS shortcuts.

First, I’ve decided on the syntax of my entries:

In a file named 2006-01-02T150405.md:

This is an entry inside my journal, as you can observe it just starts as a plain text.

You can use markdown here, but for a journal you should be good with a blockquote here and there.

---
/images/a-nice-illustration.jpg
#rhea #journaling
Home, France
@48.8687162,2.2219584
17°C, Cloudy

All of the footer entries are optional.

Then it was easy to create two shortcuts in iOS to:

1. Grab the current location, weather and address and write a new note with current timestamp as filename with this information. Then open the file immediately with iA Writer.
2. Receive an image, use it’s exif to get the time and location. If the date is today, grab the weather. Copy the image into the desired location, create the note and open it in iA Writer.

The advantage of handling images this way is that iA Writer supports displaying them in preview mode.

Rhea - Go server to render the journal in a nice way

Since I knew Hugo was almost what I wanted, I decided to learn Go language to write my server.

My design goes roughly this way:

1. Fully server-rendered html page.
2. No static rendering, live-running server only.
3. Single user, take credentials as parameters.

The program should do the following.

1. On startup look into the directory that contains the entries.
2. Iterate over the entries.
   1. If the entry contains an image, generate a thumbnail for it if it hasn’t been done and store it in a cache directory.
   2. If the entry contains a location, use MapBox to fetch the map, and store it.
3. Start watching the entries directory and update the in-memory representation if anything is added or changed.
4. Start a webserver that serves:
   1. / - At root show list of all entries, show the location map if the location changed from previous entry by more than 50km. Show images as thumbnails.
   2. /entries/ID - Show a detailed entry with full size images and a more detailed location map.
   3. /images, /thumbails, /tiles - Just serve the images.
   4. /login - Render this page if there is no valid session cookie set.

And that’s about it. Cook this with some nice templates and a bit of CSS and we have a journaling app.

If you would like the source code feel free to ask, I am no longer publishing my repositories publicly.

The other day I have shared the workout tracker I have written for mysef with a friend. Soon enough I have started getting feature requests and suggestions for improvement. I disagree with almost all of them.

The problem is that I use every feature of the tracker, I remove any feature I might not be using anymore, and I implement any feature I want to have.

I have written most of the application by hand, maybe the initial 90%. However, at the end of the line, I have used agents quite heavily and it pushed me trhough the last 90%.

It is okay for something to die.

Here is a little overview of the current most popular fitness influencers, and what you should know about them before listening to anything they say.

The Team

Alexander Bromley

Bro Strongman

My favourite at the moment. Unfortunately the last video contains AI generated animations which I’m not fond of.

Mike Israetel

Science Based Mentally Challenged

Milo Wolf

Science Based Bootlicker

Greg Doucette

Bro Supplement Peddler

Drug dealer with a loud mouth. Has an absolutely insane video editor.

His videos are 90% drama with some workout advice sprinkled on top. His workout advice is extrememly basic and generally good.

Do not listen to him concerning supplements, even if everything he sold worked, he is still very much in the game of peddling turk (which has never shown any efficacy).

Jeff Nippard

Science Based

Lylo

Science Based

Jeff Cavalier

Science Based

Used to be good, but fell down the trap of chasing relevancy. Probably natural at some point, but hard to believe that one can retain 6% body fat year long at 50.

The Conclusion

… because most writing during most ages was terrible, but the only surviving and known pieces from the past are those which stood the test of time.

❦

This was the conclusion I got to. This article is about the journey how I got there.

These are my notes on two videos by the writer Hilary Layne: Modern Heroes are Weak and Boring and Modern Villains are Pitiful and Impotent.

Both issues stem from the lack of objective morality in the worlds created by modern writers.

The concepts of Good and Evil in modern literature are based on how it makes the reader/writer feel. This makes them extremely malleable and ultimately meaningles.

Readers prefer anti-heroes because they are closer to the classical definition of a hero: “The main male protagonist of the piece”. Anti-heroes are closer to objective morality as they can act, whereas modern heroes can’t.