Strange. In the last few years, I’ve abandoned search engines for most programming related queries by chugging along happily with Recoll. If I had the time I’d sit down and hack out a web front–end for its Python API but the desktop interface supplied with HTML from my own web crawlers works beautifully (medoc92/recollwebui also exists).

In the end my blog here ended up as a public note taking system — oh well. It’s kinda prickly though because I’m linking out in most posts and don’t have a workflow for auto–archiving the destinations yet. Chances are that when I return to older posts links inside will be dead. Archive.org isn’t infallible – ya better locally archive anything remotely interesting. Y2Z/monolith is good at creating self–contained web pages.

Writing assistant: Vale. I heard somewhere that writing/speaking at a 6th grade level is a surefire way to be relevant.. whoops.

$ vale extensible-stylesheets.md
1:1     suggestion  Grade Level 11.02.              thedro.Readability         
16:3    error       Use code tag `XML` instead of   technical.CodeSubtitutions 
                   'XML'.                                                     

I had some time to futz about updating my Isso setup and forgot that a while back they added Atom Feeds. It’s also neat that it uses Atom Threading (an example). Installation from source is easier too.

Out of all front–ends for Mastodon/Pleroma the one with the funniest name is Soapbox (repo). Social media is a soapbox. Yes, this blog now has simple text animations :-)

It’s alive again. cbformat looks extremely useful — might just beat my current method of formatting code blocks in Markdown.

Blade CLI is a nice find. I saw a past iteration of this a while back in nsrosenqvist/blade-cli. Basically, it’s a cli for kinda rendering blade templates. Don’t ask why..

name: {{ $name }}
type: {{ $type }}

blade render data.yaml --name="name" --type="type"

The Syncthing developers have added support for synchronizing ownership and extended attributes. If enabled, root might be needed and the bidirectional sensitivity/conditions for file conflicts might increase dramatically. From perusing the commits, versions after 1.22.1 should stabilize these features.

Sometimes the source code is the ultimate documentation. If you’re creating color schemes based on chroma, nothing beats types.go for finding out what each token means.

cgit is good. I’ve added a small note on using git maintenance with cgit.