Space Panda

A few years ago my fascination with hurdy gurdies went as far as ordering one.

There’s a new thing going around in the blogosphere1: human.json.

If you are not humming “Roll the old chariot along” by now, you clearly have some internet-searching to do1.

As was pointed out in abundance, having open source depend entirely on centralised infrastructure (github comes to mind) is not great.

Running any type of computer these days without full disk encryption (FDE1) is a bad idea; but I’m surprised just how that is implemented in many of the installation images of Linux.

Bruno Croci recently wrote about his fantasy book title generator and it reminded me that I had indeed done a similar thing in a generalized form, but never really documented or published it (mainly because it’s so small and quite silly).

Let’s have a look at a few concepts first.

In a previous article I looked at the templating method for reMarkable tablets that was newly introduced with software version 3.17.

When I first encountered a Linux1, I was surprised how an operating system, let alone the software coming along, could be free of charge2.

This is an article describing what my keyboard layout looks like and why.

Apparently Microsoft, famously changing their stance from “Linux is a cancer”1, to actually running a Linux subsystem in Windows (weirdly abbreviated as WSL) yesterday, at the time of writing, now released WSL under the MIT license (to the surprise of pre…

The good thing about infrastructure, that deserves that name, like streets, bridges, and pipes in the ground, is, that it remains usable even when the supplier goes away.

We received a small stack of old laptops in our hackerspace, to do with them as we see fit.

With the release of the reMarkable Paper Pro (rmPP) and at least software version 3.17 on the reMarkable2 (rm2), there is a new way to define page templates in town: Methods.

Every now and then there are screenshots with text scrolling by on the social medias and it might be convenient to copy the text out.

A while back I got my hands on a reMarkable 2 and I guess I might as well write about how I use it.

Hugo appears to be where all the cool kids are going these days; so I decided to move the website over to that, too.

Most desktop environments will not easily accept that users prefer a commandline program for their email.

This is a bit of a rant.

The Steam Deck has in essence an ArchLinux on a read-only btrfs.

Every now and then open source projects are not on any of the popular platforms, but you’d still like to participate by contributing code, report bugs, or ask for new features.

Sometimes it’s quite nice to be able to see where time went.

HTML in emails is a bit of a curse.

This article describes how to select attachments in mutt and neomutt through the command line file manager ranger.

Usually a person has multiple email addresses and when receiving email on one of them, it’s a good idea to have the email program automatically use that address as the sender when replying.

For sending emails you could set up (neo)mutt to do the sending on its own.

I like unicode.

For displaying email (neo)mutt uses the built-in pager (unless you configure an external pager through the pager setting) which is actually quite good, because it allows you to quickly access the attachments directly, or on the spot reply to the email.

By default (neo)mutt will list emails rather bluntly like this: This is what the default view of an inbox looks like.

In order to tell (neo)mutt where to find your local emails, as obtained earlier, let’s first revisit the directory structure.

This is the second article in a series on how to configure (neo)mutt.

In order to run mutt independently from my mail provider I keep my mail synchronised between my machine and the server(s).

As a start why not actually have a look at this website?

On this website I’m mainly going to present my email setup which took me a few years to get to the current state.