A List of Ways to Confirm the Earth is Round.

People who have never really lived in a world without mobile phones […] might think that daily life at that time was unnecessarily complicated and ‘harder’. Organising meetings, finding people, finding places around you, having to use paper maps instead of having a portable device with GPS functionalities built in, not being able to look things up in Google or Wikipedia at any time. The truth is, people knew how to organise themselves with the tools they had available. Daily life had a completely different pace and style, built around the tools available at that time. It really isn’t a matter of ‘worse’ or ‘better’ — life was just different. — How I’d live this quarantine if it was 1990

org-noter: Emacs document annotator, using Org-mode, with some differences from Interleave. #emacs

Harp: The static web server with built-in preprocessing.

Falcon: Free, open-source SQL client for Windows and Mac. Looks like a nice successor to Induction app (now defunct).

Emacs (like Smalltalk) has no barriers except at its low-level foundations. Emacs users can change, and break, anything they like. Emacs packages made available for download can potentially contain very malicious code. The Emacs philosophy, going back to the 1970s when there were neither cybercriminals nor completely tech-naive users, is that Emacs users are fully responsible for managing their Emacs environment. This actually works very well in practice, even today, because Emacs is neither attractive for completely tech-naive users, nor sufficiently popular to be an interesting target for cybercriminals. — The most successful malleable system in history

This was also the day it was.
(roast chicken, fried potatoes and carrots, and celery root.)

Interesting discussion regarding Markdown for serious typesetting (using shell scripting).

We’re happy to announce we’re making private repositories with unlimited collaborators available to all GitHub accounts. All of the core GitHub features are now free for everyone. — GitHub is now free for teams

A nice discussion about UTF-8 encoding.

We see no particular reason to favor Unicode code points over Unicode grapheme clusters, code units or perhaps even words in a language for that. On the other hand, seeing UTF-8 code units (bytes) as a basic unit of text seems particularly useful for many tasks, such as parsing commonly used textual data formats. This is due to a particular feature of this encoding. Graphemes, code units, code points and other relevant Unicode terms.