At this point, I’ve switched to Kate Editor. It’s much simpler than VS Code/Codium and similar programs, and I like that. There are ways to customize it to your liking that I’m still exploring, but one I’ve already done is add Typograf.

The description is in Russian, so the gist of it is this: Typograf (which can be a CLI application, an extension to your browser, etc.) formats the selected text, changing quotes, dashes, elipses, and stuff like that to it’s fancier form. So "Huh..." would become “Huh…”. It also puts non-breaking spaces where they belong. Pretty useful.

To be fair, Hugo already does the fancy thing with every Markdown file, but I prefer to have more control over it.

And we can use it in Kate! First, let’s install typograf-cli with npm (which is a package manager for things written in JavaScript):

npm install typograf-cli -g

With -g installation flag, it should be in our $PATH for easy of use.

In Kate, we go Tools → External Tools → Configure → Add → Add Tool. Then fill in the text boxes as follows:

-c is for a settings file if we want to change the default behavior. It really wants a full path for some reason, so no ~/. Mine is -c /home/­andrew/­.config/­typograf/­typograf.json

At the end, it should look like this:

We can customize these to process the entire document, for example. But I just add a keyboard shortcut (Settings → Configure Keyboard Shortcuts…), and it does the magic on a selected text.

Bonus, in Micro we can add

"Alt-y": "command:textfilter typograf --stdin -c /path/­to/config"

to .config/micro/bindings.json for the same result. Alt-y is a keyboard shortcut that we can pick.

Crow Country is a good modern take on survival horror. It goes for the things that inspire it, but doesn’t forget to put its own spin on it, from aesthetics (kind of PS1 with a dash of Ečstatica) to puzzles (a pinch of Metroidvania thrown in).

Paratopic and The Sirena Expedition are nice, short, PlayStation One-looking, slightly creepy games.

Speaking of survival horrors, I finally finished Silent Hill 3. Obligatory: fuck Konami. Has it aged? Sure, but it still holds up pretty well. To be clear, I think the graphics still look amazing. But the animation, the camera, the acting, things like that, they don’t let you forget that you’re playing a PlayStation 2 game. But at this point, it’s all part of the charm, more than anything. It’s also a sequel to the first Silent Hill, which is the only other one I’ve ever played, and that’s probably going to remain the case with this important but problematic series.

Dot’s Home is a good story about a black family, community and gentrification. It’s point-and-click only in presentation, no puzzles to speak of, almost a walking simulator, really. And it’s free!

I was also pleasantly surprised by ObsCure. Don’t get me wrong, it’s not flawless (there are at least a couple of instances of sexist stuff that come to mind, for example), but overall it wasn’t as bad as I feared. It also goes for a very specific thing, a subgenre of horror that was popular at the time (The Faculty, anyone?), to the point that the characters look like 30 years old actors playing high school kids, which is brilliant! And even with the gameplay, it does some interesting things, from the light mechanic to the ability to just break glass doors.

I also tried the sequel, and that didn’t go so well. From awkward free camera to immediate sleaze through the roof, I decided not to finish it.

While Nimona is great, Wolfwalkers also has a few tricks up its sleeve. For example, the way it uses the art style to tell the story. It divides the world into a square, orderly human part and a squiggly, wild forest part. It also draws some things in that tapestry kind of way, where everything is seen from a birth-eye view, but facing the viewer. Not a bad story, nice characters, all in all a good movie.

There are many ways to organize your content in Hugo, including custom taxonomies. But I wanted something simpler: a page that lists all the “things” I have written about, with links to the corresponding posts. Here is how I figured it out.

• Content
• Dictionary
• List
• Conclusion

Maybe not the best or most elegant way, but it works and since Hugo is a static site generator, no one will ever know! :)

“Index” is a bit confusing in the web world, but I mean it as “an alphabetical listing of items and their location”.

Content

So on the content side, we need to add this to front mater of each post:

items:
- Name of a thing
- Name of another thing
- Etc.

If there are some pesky characters like colon, the name should be enclosed in quotes: - "Thing: Not the other thing!"

Dictionary

Then we need a list.html in layouts/map/ folder. map can be whatever we want. I won’t cover how to deal with layouts. Here is the main thing, I will go through the details after that:

{{ $mapItems := dict }}

{{ range .Site.RegularPages }}
    {{ $mapDate := .Date | time.Format "060102150405" }}
    {{ $mapLink := .Permalink }}
    {{ $mapTitle := .Title }}
    {{ with .Params.items }}
        {{ range . }}
            {{ $mapItem := . }}
            {{ $mapUnique := printf "%s%s" $mapItem $mapDate }}
            {{ $mapUnique := replaceRE "^The |^An |^A " "" $mapUnique }}
            {{ $mapItems = merge $mapItems (
                dict $mapUnique (
                    slice $mapLink $mapItem $mapTitle
                )
            ) }}
        {{ end }}
    {{ end }}
{{ end }}

{{ $mapItems := dict }} creates a dictionary named $mapItems. Dictionary is a list of things where you have a key with attached value (one or many things).

I use $mapSomething for names because I decided to call the whole thing a site map. Can be named anything.

With {{ range .Site.RegularPages }} we want to look through all the pages we have. It’s a loop that goes through them. Maybe that’s too much, there are ways to narrow it down. But if a page doesn’t have items: in its front matter, it won’t show up anyway.

Then we create three variables $mapDate, $mapLink, and $mapTitle that we are going to work with. With $mapLink and $mapTitle we are just assigning them to be (:=) link and title of our pages.

With $mapDate, we also pipe it (|) into time.Format to look like a string of numbers, with two for each year, month, day, hours, minutes, and seconds. We will use it to make our keys look unique, so if we have two posts that share the same item, they will not override each other.

{{ with .Params.items }} limits our pages to only those that have items: in the front matter.

Then we create another loop {{ range . }}. . (dot) represents the thing we just worked with from the previous command. So, the items:.

{{ $mapItem := . }} creates another variable. These are the items.

Then, for simplicity and readability, we create our unique key with two commands. First, we join the name of the item with the date of the post:

{{ $mapUnique := printf "%s%s" $mapItem $mapDate }}

Second, we remove articles (“A”, “An”, “The”) if the names of the items begins with them. This is obviously unnecessary, but why not!

{{ $mapUnique := replaceRE "^The |^An |^A " "" $mapUnique }}

Finally, we merge our dictionary (which is empty at the beginning) with the new entries we’ve created with our variables:

{{ $mapItems = merge $mapItems (
    dict $mapUnique (
        slice $mapLink $mapItem $mapTitle
    )
) }}

A bit of translation: $mapItems will now be equal to previous $mapItems plus new ( dict … ), where the first thing $mapUnique is a key and a second thing ( slice … ) is a value. The fact that it is a slice just means that there are multiple things in it and we can get them out individually.

To summarize, what we do is two loops. The first one goes through our posts and gets their date, link and title. Within it, so for each post, the second loop goes through our items: and adds them to our dictionary of things, with unique key and some stuff value that we will use to render our list.

List

Speaking of which, this is how we will render it:

{{ range $key, $value := $mapItems }}
    <li><a
        title="From {{ index $value 2 }}"
        href="{{ index $value 0 }}">
        {{ index $value 1 }}
    </a></li>
{{ end }}

We again use a loop, this time for the dictionary we created. It’s going to sort by key, that’s why we removed those articles so the list can be sorted in a nicer way.

In this loop, we use index to get the specific $value. They start from 0 and go as we set them with slice, post link, item, post title. Title is also unnecessary, but it will show up on hover and will be helpful if there are multiple items.

Conclusion

On my site map, I decided to split all items into multiple categories. I did it very simply, but in a way that is easy for me to work with. Instead of having just items: in front matter, I have three different things: iGames:, iCinema: and iMisc:. Then in the list.html, I repeated the second loop three times, for each of these three things ({{ with .Params.iGames }}, etc.), and each of them adds items to the corresponding dictionary ({{ $mapItemsGames := dict }}, etc.). Then I render every dictionary as its own list.

I am more than sure that there are other ways to accomplish the same thing. There are always different ways to manipulate data. Dictionary just made the most sense to me, with a key that can be used to sort things nicely and then pull things up from value to display in a way I want.

It’s easy to see why the Resident Evil formula has survived to this day (hello, Signalis). It works! Even if the game, like Resident Evil 0, isn’t particularly inspiring and mostly repeats things we’ve already done with just a handful of innovations, it’s still enjoyable.

Anopek is a small metroidvania shooter. Nothing special, just nice.

1000xRESIST is inspired by recent history, often directly: expect a global pandemic, immigrant life, high school shenanigans, and other things I won’t spoil. And it’s very cool to see underrepresented people both on and behind the screen, so to speak. But ultimately it is a sci-fi story, and a good one. Maybe slightly garish visuals. A bit. :)

It’s hard to talk about Demon’s Souls, or any Soulslike game for that matter, without, you know, talking about it. I won’t go into too much detail, but let’s do it.

I think the discussion about difficulty in games should instead be about accessibility. And in this case I mean accessibility in the broadest sense. I believe that games can and should be accessible to many more people than they are now. And the fact that we often talk about “easy mode” instead is very annoying.

It’s especially annoying because these games, at least the FromSoftware games that I’ve played – played Dark Souls 1; finished 2 and 3, and now finished Demon’s Souls – actually give you a lot of tools to lower or raise the difficulty (if you can play them at all, that is), and they do it well.

And of course it is even more annoying that we have to have this discussion instead of having one about the games themselves. Because they are pretty good, you know! Even if they just threw out the whole combat system that gives way to this annoying and misdirected discussion, there would still be a lot to like. The world, the exploration, the story, the atmosphere, the feeling of progress. Even muddy and dark in the way games were at the time, but still beautiful visuals. Good, good I tell ya!

Wendell & Wild is funny, macabre, and progressive. Not perfect (the deadnaming bit comes to mind), but still pretty enjoyable.

There is almost a whole genre of speculative evolution, of which After Man is probably the most famous. Scavengers Reign took that – mushed a bit with art by Mœbius, – as the setting for a story about people stranded on an alien planet. People from Nostromo, not Enterprise. And it’s also, like Alien, a kind of horror. I was a little disappointed that the story was not bad, but, for lack of a better word, pretty classic for such an innovative setting. But it’s very beautiful to look at, in that unsettling kind of way.

There are two ways to look at Yokohama Kaidashi Kikō (I mentioned it before). On the one hand, it’s a gentle look at the death of the world. Post-apocalyptic doesn’t have to be violent, cruel, or even unpleasant. We will all die, our cities, our world. So why can’t it be peaceful and beautiful?

You can get the most out of it by watching just 4 short episodes of an animation. The books expand on this and introduce more characters and their stories.

On the other hand, somehow optimistically, it can be seen as a transformation that our world can take – be forced to take – and still be fine. People, even if some of them are robots, will still be doing people things. There would be communities, celebrations, daily work. And maybe it’s better that way.

There seems to be no consensus on how well mental health is portrayed in Hellblade games, and since I’m not an expert, I won’t say more.

What I can say is that it leans a little too much towards punishing the protagonist for my taste. It makes the comebacks more powerful, but I don’t know if it justifies the whole thing. To put it another way, I was curious about the first game when it was released, and felt compelled to follow the story in the second, but wouldn’t be upset if I never played both.

For me to consider something problematic, both the good and the bad should be on a comparable level. It’s not perfect, but Doctor Who seems to have been pushing diversity for a while now. I even started watching it after they announced that there would be a female Doctor.

At this point I have watched everything with the Ninth, Tenth, Thirteenth, Fourteenth and now Fifteenth Doctors. Yes, I skipped the Moffat era.

On the other hand, the BBC seems to be pretty bad in many areas. Is it worth it? Well, I don’t give money to BBC, so sure.

The show has a somewhat weird and unique tone, where it tries to be for as much of an audience as it can, so sometimes it can be too silly or simplistic. But the premise means that almost every episode would lead main characters on a pretty unique adventure, and if you like those characters, then at least it would be fun, if not provocative, gut-wrenching or awe-inspiring, which occasionally happens too.