Parsing RSS feeds is always a pain. Don’t parse feeds inside the template engine kids :-)

The dictionary and thesaurus are among my most used tools. They’re easy to install and use offline on any device — no search engine required. I just also realized that my most used offline tools are not in my blog post about programming without the Internet…

Why blog? One key reason is for framing offline and organic discussions — they’re the best. Online discussions tend to devolve into “peanut gallery” takes for any range of topics. You can’t know it all, but being in the gallery is fun?

It’s painful to realize that a program’s state is name spaced wrongly/scattered. You’ve then got to either accept the complexity or rewrite select portions + migrate to a more correct data hierarchy. Databases exist to make that easier.

Though, imo the simplest form of system administration is when you only have to backup/copy state directories from one computer to the next.

Two interesting indie/micro blog repositories.

1. GoBlog: Simple blogging system written in Go. Example.
2. tally-ho: A micropub speaking blog. Example.

SVG is a solid tactic. No one “inspect elements” every site. Everyone’s a user, even programmers — they won’t know until someone tells them.

I’m actually sleeping…

If the cryptocurrency ecosystem “falls” in on itself, it probably still won’t disappear because it’s almost TBTF. It’s how we westerners do things. ;-) Magic is real, but strangely selective?

I’m very tempted to stick GNU Guix somewhere in my main workflow — Guile Scheme looks interesting. I’m sorta curious as to why people like Lisp languages so much. The plan is to read the reference manual. (yeah… right)

My knowledge of the functional ecosystem is mostly diddly, but maybe there’s a way to speed it up? Ignore all module and package imports and piece together a minimal evaluation perhaps?

{ ... }:

{
  imports = [
    <nixpkgs/nixos/modules/programs/git.nix>
    <nixpkgs/nixos/modules/security/auditd.nix>
    <nixpkgs/nixos/modules/services/databases/postgresql.nix>
  ];

  nixpkgs.overlays = [
    (_: pkgs: {
      cpio = pkgs.callPackage <nixpkgs/pkgs/tools/archivers/cpio/default.nix> { };
    })
  ];
}

If that goes anywhere, maybe that’s an article, but I’m fairly certain someone must have tried something like this already.