A Go CLI often begins with a small main.go, a few flags, and a switch statement. Then it grows. Before long, cmd/ contains argument parsing, configuration loading, filesystem access, database calls, output formatting, and the actual application logic. Adding a command means copying another block of flag handling. Testing a command means pretending to invoke the entire executable. Changing the CLI framework risks touching the whole program. [go-subcommand](https://github.com/arran4/go-subcommand) takes a different approach.

Working with Large Language Models (LLMs) on multi-module projects or complex codebases can sometimes feel like a high-wire act. You give the LLM a large set of instructions, and while it might accomplish the immediate tasks, you often find yourself wondering: Did it actually have all the context it needed? Did it silently skip over something because a dependency wasn’t ready? To prevent the LLM from trying to stubbornly forge ahead when it lacks prerequisites—or worse, hallucinating a solution—I’ve developed a prompting pattern that I use regularly.

This is a practical build-up guide for creating one large ci.yml that is still readable, maintainable, and tailored to real repositories. Note that if this is provided to a repo with a pipeline already in place it’s generally an upgrade request. The resulting pipeline should be bespoke to each repo, but consistently in approach, logic, parts, etc. The target outcome: One workflow file handles push, PR open/update, PR close, tags, release publish, manual dispatch, and monthly/nightly schedules.

One of the most common pitfalls when working with Go’s text/template and html/template packages—and a frequent stumbling block for AI agents—is understanding how whitespace manipulation works. Specifically, the - (minus sign) in {{- and -}} is highly meaningful. It is not just decorative syntax or a continuation of the {{ token; it explicitly clears whitespace. If you aren’t careful with these markers, you can quickly ruin the formatting of output that relies on strict whitespace, such as YAML or cleanly indented HTML.

When instructing LLM agents (like coding assistants) to update dependencies such as golangci-lint, there are often issues with the models defaulting to older, outdated versions based on their training data. If you try to correct them, they may fall back on what they “know” rather than following your instructions, resulting in version downgrades, overly specific version pinning, and regressions. This post establishes strict rules and alternative strategies to ensure compliance and prevent these downgrades.

Over time, I’ve created numerous .goreleaser.yaml files for various projects. While a lot of them are out of date and inconsistent, reviewing them has helped me formulate a standard set of practices for assembling a GoReleaser configuration file. This post outlines these standards to help maintain consistency, maximize distribution, and simplify CI processes across projects. General Principles Naming Packages I believe that the defaults should work for file and package naming, so I avoid using _template for naming (such as renaming things) unless it is strictly required to prevent a name conflict.

When generating code, Large Language Models (LLMs) often default to using Regular Expressions (regex) for string parsing and validation tasks. While regex is a powerful tool for human developers aiming for concise code, it is rarely the optimal choice for LLMs writing production-grade software. Instead of always defaulting to dense regular expressions, LLMs should often expand logic into explicit, step-by-step procedural code and accompany that code with comprehensive, table-driven unit tests.

For “link and article” style pages, as well as data-defined content repositories, generating monthly releases is a powerful way to keep your audience engaged. People often subscribe to “releases” on GitHub repositories, and providing them with a magazine-style “issue” gives them tangible updates without needing to dig through commit logs. This approach helps people remember your project rather than simply starring it and forgetting it exists. While generating a summary of changes automatically can be complex depending on the project structure, creating the release artifact itself is straightforward and highly valuable.

When instructing LLM agents (like coding assistants) to update dependencies such as golangci-lint, there are often issues with the models defaulting to older, outdated versions based on their training data. If you try to correct them, they may fall back on what they “know” rather than following your instructions, resulting in version downgrades, overly specific version pinning, and regressions. This post establishes strict rules and alternative strategies to ensure compliance and prevent these downgrades.

If your Go code calls os.Create, os.Stat, exec.LookPath, or net.Dial directly from business logic, your tests are forced to touch real side effects more often than necessary. The core pattern in this space is simple: Define small interfaces for side effects. Inject real implementations in production. Inject in-memory fakes or standard library memory file systems in tests. This is why I encourage myfs.Stat("file.txt") (or whatever your project names it) over direct os.

I use txtar as a practical test and fixture format across multiple repositories. This post is my updated reference for how I expect agents (and future me) to structure and evolve txtar-based systems. Repositories discussed: arran4/golang-rcs (testdata/txtar) arran4/golang-diff (pkg/diff/testdata) arran4/editorconfig-guesser (testdata) Related pattern: arran4/goa4web templates (core/templates) The core theme is that there is a range of sophistication: Simple input/output data pairs Case metadata + descriptions Full scenario definitions with options and assertions Since then, the approach has evolved, specifically when dealing with larger test suites and complex context mocking (like validating fstab entries against a mock /proc/filesystems).

When encountering the following golangci-lint error in GitHub Actions or locally: 1run golangci-lint 2 Running [/home/runner/golangci-lint-1.64.8-linux-amd64/golangci-lint config path] in [/home/runner/work/fork-mdtohtml/fork-mdtohtml] ... 3 Running [/home/runner/golangci-lint-1.64.8-linux-amd64/golangci-lint run] in [/home/runner/work/fork-mdtohtml/fork-mdtohtml] ... 4 Error: can't load config: the Go language version (go1.24) used to build golangci-lint is lower than the targeted Go version (1.25.0) 5 Failed executing command with error: can't load config: the Go language version (go1.24) used to build golangci-lint is lower than the targeted Go version (1.

Error handling in Go is straightforward, explicit, and forces developers to deal with failure states right at the point of origin. While if err != nil is a running joke in the community, when used correctly, Go’s error handling produces robust, debuggable, and maintainable software. In my Go projects, I adhere to a set of practices that ensure errors are not just checked, but are rich with context and actionable. Let’s dive into how I handle errors effectively.

This post serves as explicit instructions for LLM agents (like Jules) on how to correctly handle and resolve golangci-lint Go version mismatch errors without requiring the user to repeatedly copy-paste the same workflow. If you encounter an error like the following during a build or lint process: 1run golangci-lint 2 Running [/home/runner/golangci-lint-1.64.8-linux-amd64/golangci-lint config path] in [/home/runner/work/fork-mdtohtml/fork-mdtohtml] ... 3 Running [/home/runner/golangci-lint-1.64.8-linux-amd64/golangci-lint run] in [/home/runner/work/fork-mdtohtml/fork-mdtohtml] ... 4 Error: can't load config: the Go language version (go1.

This post acts as explicit instructions and rules for LLMs tasked with upgrading software projects. When applying an upgrade, you must follow these rules meticulously to ensure the project remains stable and up-to-date. Upgrade Rules When upgrading a repository, always target the latest versions of the following technologies: Flutter & Dart: Ensure the project uses the latest stable releases. GitHub Actions: Upgrade all actions to their latest major versions. Go (Golang): Update to the latest stable Go release.

If you have encountered a build failure in your Go project’s GitHub Actions pipeline, you might see an error output similar to this: 1run golangci-lint 2 3 Running [/home/runner/golangci-lint-1.64.8-linux-amd64/golangci-lint config path] in [/home/runner/work/go-pattern/go-pattern] ... 4 5 Running [/home/runner/golangci-lint-1.64.8-linux-amd64/golangci-lint run] in [/home/runner/work/go-pattern/go-pattern] ... 6 7 Error: can't load config: the Go language version (go1.24) used to build golangci-lint is lower than the targeted Go version (1.25.0) 8 9 Failed executing command with error: can't load config: the Go language version (go1.

This is a practical build-up guide for creating one large ci.yml that is still readable, maintainable, and tailored to real repositories. The target outcome: One workflow file handles push, PR open/update, PR close, tags, release publish, manual dispatch, and monthly/nightly schedules. It supports mixed repos: Go, Node, Dart, Flutter, Qt/C++, classic C/Makefile, and Dockerized components. It can run in public mode (broader checks) or private mode (cost-controlled), while keeping default test runners Ubuntu unless cross-OS coverage is explicitly needed.

This is a practical build-up guide for creating one large ci.yml that is still readable, maintainable, and tailored to real repositories. The target outcome: One workflow file handles push, PR open/update, PR close, tags, release publish, manual dispatch, and monthly/nightly schedules. It supports mixed repos: Go, Node, Dart, Flutter, Qt/C++, classic C/Makefile, and Dockerized components. It can run in public mode (broader checks) or private mode (cost-controlled), while keeping default test runners Ubuntu unless cross-OS coverage is explicitly needed.

1. Introduction I recently lost a Firefox window during shutdown, and unfortunately, it was not saved in the session restore. It was a window filled with extensive research, consisting of many tabs meticulously grouped. Losing it meant losing a significant amount of context and work. 2. Initial Attempts (and why they failed) My first instinct was to use standard Firefox features. I checked “Restore Previous Session” and “Recently Closed Windows,” but the window simply was not there.

If your Go code calls os.Create, os.Stat, exec.LookPath, or net.Dial directly from business logic, your tests are forced to touch real side effects more often than necessary. The pattern in this article is simple: Define small interfaces for side effects. Inject real implementations in production. Inject in-memory fakes or standard library memory file systems in tests. This is why I encourage myfs.Stat("file.txt") (or whatever your project names it) over direct os.

If your Go code calls os.Create, os.Stat, exec.LookPath, or net.Dial directly from business logic, your tests are forced to touch real side effects more often than necessary. The pattern in this article is simple: Define small interfaces for side effects. Inject real implementations in production. Inject fakes or in-memory versions in tests. This is why I encourage myfs.Stat("file.txt") (or whatever your project names it) over direct os.Stat("file.txt") in your core application code.

A recent patch series for arran4/git-tag-inc (PR #54) is a good example of how to turn a one-off code change into a repeatable method other projects can use. The technical change was simple: move long CLI help text out of Go code and into an embedded template, keep dynamic values in code, shift conditional rendering into the template, and avoid global flag-output side effects. The process is what matters most, because it is reusable across repos and agent-assisted workflows.

I use txtar as a practical test and fixture format across multiple repositories. This post is my reference for how I expect agents (and future me) to structure and evolve txtar-based systems. Repositories discussed: arran4/golang-rcs (testdata/txtar) arran4/golang-diff (pkg/diff/testdata) arran4/editorconfig-guesser (testdata) Related pattern: arran4/goa4web templates (core/templates) The core theme is that there is a range of sophistication: Simple input/output data pairs Case metadata + descriptions Full scenario definitions with options and assertions Why txtar txtar is great when you want fixtures that are:

If you use this in GitHub Actions: 1- name: golangci-lint 2 uses: golangci/golangci-lint-action@v9 3 with: 4 version: latest you are absolutely right to be cautious: latest can move to a new golangci-lint release that adds support for a new Go minor while your workflow, runner, or repo expectations are still pinned to older assumptions. This guide gives you: a practical version pairing table (Go ↔ golangci-lint ↔ action), safe version ranges you can reuse, and many copy/paste workflow examples.

I keep reaching for the same API shape in Go: a variadic argument list (...any) processed with a type switch. I call it my type-switched variadic system. It is not the only way to configure behavior in Go, but for parser/consumer style libraries it has been one of the most productive patterns I use. If I had to summarize it for future me (or future agents helping me write code), it is this:

Git’s ref system is a tiny language for naming objects and mapping them across repositories. This post is a grammar reference first, and examples second. Grammar reference Ref and refname 1ref := 'refs/' refpath 2refpath := name ('/' name)* 3name := 1+ valid-char 4valid-char := printable ASCII EXCEPT {space, control, '~', '^', ':', '?', '*', '[', '\\'} 5constraints := not (leading '/', trailing '/', '//', '..', '.lock', '@{') Common namespaces (grammar applies equally):

It turns out the biggest challenge with Facebook these days is not the lack of a wall—it is the friends who constantly disappear and reappear. Between account deactivations, privacy panics, experiments with quitting social media, and the looming spectre of real-name or ID laws, profiles blink out of existence for weeks at a time. I am terrible at keeping up with people even when the directory stays stable, so that churn leaves me forgetting who moved, changed jobs or quietly vanished from my digital orbit.

A brain dump exploring what browsers might need in order to deliver the snappy feel of today’s single page apps without any JavaScript. The idea came from asking ChatGPT to outline a true “JS‑free” SPA. The Core Idea New form attributes async to fetch responses without a full reload update="#target" to inject the returned fragment into a selector CSS pseudo-classes :loading to style the in-flight state for spinners and disabled buttons With only HTML and CSS we could get async submission, live loading indicators and partial DOM updates.

Short comparison of how btop renders in a few terminals. For my config checkout https://github.com/arran4/dotfiles Terms xterm UXterm urxvt Putty term on Linux Kitty Alacritty GNOME Terminal xfce4-terminal WezTerm Konsole Qterminal LXTerminal Consible Term Seems I’m missing a couple op code. I will find a reason to get around to this. (Could be I’m on the wrong branch) mate-terminal Sakura st 1erresc: unknown private set/reset mode 2026 2erresc: unknown private set/reset mode 2026 3erresc: unknown private set/reset mode 2026 4erresc: unknown private set/reset mode 2026 5erresc: unknown private set/reset mode 2026 6erresc: unknown private set/reset mode 2026 7erresc: unknown private set/reset mode 2026 8erresc: unknown private set/reset mode 2026 9erresc: unknown private set/reset mode 2026 terminator ptyxis mlterm kterm zutty 1W [vterm.

While testing the multi-runner setup I discovered containers started by the runner user could not invoke Docker. The base image lacked the docker.io package and the user was missing membership of the docker group. The Dockerfile.ubuntu-runner now installs Docker and ensures the runner user belongs to the docker group so each containerised runner can start sibling containers without needing root: 1@@ 2-RUN apt-get update && apt-get install -y \ 3- curl git jq sudo nodejs npm \ 4- libicu70 libssl-dev libcurl4-openssl-dev \ 5+RUN apt-get update && apt-get install -y \ 6+ curl git jq sudo nodejs npm \ 7+ libicu70 libssl-dev libcurl4-openssl-dev \ 8+ docker.

Introduction Running dozens of self-hosted GitHub Actions runners can quickly become a management headache. Maintaining separate Docker images for each runner and rebuilding them when GitHub updates the runner software burns time and storage. By leveraging one privileged Docker-in-Docker (DinD) container as a supervisor we can host many lightweight runner containers inside it. This approach isolates configuration per runner, keeps updates simple and avoids rebuilding the entire image each time a new runner version drops.

In my earlier posts I uploaded Sieve filters straight to the server using GitHub Actions. That worked well until a typo slipped through and broke my inbox. To catch those mistakes before deploying I created a small Rust project that runs my Sieve rules against a set of example messages. The tests run locally and in pull requests so I can fix issues early. Project layout The test harness lives in a new Cargo project.

In the previous post on deploying Sieve filters to Stalwart using JMAP the workflow always created a new script. After some testing I realised it should update the existing script when one already exists. Below is the corrected workflow. 1name: Deploy to Stalwart 2"on": 3 push: 4 paths: 5 - 'stalwart.sieve' 6 branches: 7 - main 8 workflow_dispatch: 9 10jobs: 11 deploy: 12 runs-on: ubuntu-latest 13 steps: 14 - uses: actions/checkout@v3 15 - name: Install tools 16 run: | 17 sudo apt-get update 18 sudo apt-get install -y jq 19 - name: Upload via JMAP 20 env: 21 STALWART_JMAP_URL: ${{ vars.

When running an email server you often want rules that sort incoming mail into folders or handle it automatically. The standard way to do this on the server is with Sieve scripts. Sieve is a simple language defined in RFC 5228 for mail filtering. It lets you match on message headers or other properties and then file, forward or discard mail without needing any user client online. Keeping such a script in version control makes it easy to track changes and to reuse the same rules across servers.

When developing Go applications, we often define interfaces to abstract behavior and decouple components. This promotes testability and clean architecture. However, ensuring that our concrete types actually implement these interfaces can sometimes be a subtle source of errors, especially as codebases evolve. While Go’s interface implementation is implicit, meaning you don’t explicitly declare that a type implements an interface, it’s beneficial to have a mechanism to verify this compliance early on—ideally at compile time.

I ended up setting my own Matrix server on my synology. However, it occurred to me that if Synology were to adopt open standards their provided apps, like Synology Chat would be substantially more useful. Especially since they have built out encryption in a similar way to how it works in Matrix, least at the surface level. Plus they would get a much larger user base. – Even if it was a couple specs behind it would be quite useful as it would effectively be a managed deploy for me.

Lately I have been a bit obsessed with a communications protocol: Matrix. While I haven’t done too much with it directly. I did attempt to read the spec etc. However, it seems a bit … large for what it is. I have been using a couple Matrix clients and a couple matrix servers/services. Namely, Beeper is the primary one. I do enjoy Beeper, and support what Beeper is attempting to accomplish.

A while back I added golangci-lint to the github actions of all my projects. I never got around to insuring that they all have compliance, which means a lot of my projects look like this: Which is fine. It’s about gradual improvement when I have time and I am able. However the thing that bugs me about linters is that they have ego creep. WHere it moves away from being about reducing the chance of errors happening, into a world of insuring there are the correct number of new lines between functions.

Tried to use Kdenlive to install some packages via pip (I didn’t want to but that’s what it offered) finally got a good rejection! 1error: externally-managed-environment 2 3× This environment is externally managed 4╰─> To install Python packages system-wide, try apt install 5 python3-xyz, where xyz is the package you are trying to 6 install. 7 8 If you wish to install a non-Debian-packaged Python package, 9 create a virtual environment using python3 -m venv path/to/venv.

Looks like I have been inspired by this blog on the old web

KDE’s Discover… I find this KDE application really annoying. I understand what it’s trying to do. But it just feels: Too slow in comparison to the CLI It hides too much information Previous errors Packages that are being updated In settings, it doesn’t show the URLs or anything advanced for the repo It requires too much waiting between actions, it does very little async Error messages are showing as UI blocking “notification” then disappear, there doesn’t seem to be a log somewhere.

One of the major improvements over time has been how text in error messages and other “static” components have become more like read only text box / webpage and interactive over the years. Which means when you get an error message you can copy and paste the text to aid you in your search. This also means that links work. A lot of web pages seem to have failed to grasp this, and have made sections of their application “unselectable”, links “unclickable” and more annoyingly but less importantly, have failed to place white space between distinct elements which means when you go to select text (often by double-clicking and dragging in my case) you “over match” and select elements that are unintended:

Synology Active Insight has gone pro! Made me think about my previous comment. If they offered a more “general” service which included value added things like email processing etc. It would definitely make it seem more worth it. I think they should offer domain services and some email services for free still, however they can add more services along that lines. Such as an “email proxy” so you don’t have to directly expose port 25, (and maybe 110) for instance.

Why!? Synology Mail Pro is decent and all. It feels like a management layer on a bunch of open source mail tools. Plus and Android app which is quite nice. However it has a bunch of quirks which make me wonder if people actually use it inside synology. Or at least various configurations. One of the odd components of the synology mail system is the mail component isn’t fully “abstracted” between components.

I use the keyboard shortcuts [ and ] a lot in gmail. However, when I do I establish a “direction” but sometimes, I press e as I want to go back to the thread list. I don’t always navigate the same direction. For a while I turned on the “auto advance”: Option. Today I abandoned it mostly because it doesn’t support the notion of “inertia” IMHO.. Basically I want a 3rd option that is along the lines of:

I am rather fond of synology’s offering however it does leave me with a couple of wishes / desires. Synology itself Sometimes I don’t quite know if a feature is supposed to be for business or personal / private use. They often seem to have both in mind but under serve both a bit. Anyway here are some of my opinions: Software issues I kind of want an easier way of logging software issues.

Since I have setup a Dotfiles repo using the useful Chezmoi I am using a single configuration everywhere. Something else I also do is use one account for all my work regardless of the computer I’m on. However that means you encounter issues with software which wasn’t exactly designed for users who operate under different “aliases” on the same account. Such as, when I’m working for one of my clients, I do all my commits under the email address associated with that organisation.

Not sure why “Drive” gets it’s own icon but all of my cloud sync items don’t especially considering that it has all the icons already setup:

While I don’t miss people using API to change the status bar text, something I can vaguely recall and I don’t think it’s that useful as people don’t look there that often. (Perhaps it was for help text.) I do seem to miss the status bar, as a concept and in browsers specifically. While it was mostly use for things such as the zoom level and SSL level, those things have been migrated to the address bar.

Almost all the other chat clients I have can run in the background showing only a system tray icon… Why can’t Signal? Slack Discord WhatsDesk (WhatsApp) I think: Facebook Messenger – Or it just harasses me. I guess if they did so I would hope that it at least has some marker to show that conversation has happened.

I use a fair number of password managers for various reasons. However something that bugs me with their prompts is they don’t have a button that easily allows me to configure an exemption.. I almost never want to remember a password used on “localhost” on some weird port number because I develop software and test it frequently: But yet it prompts me every time. There is a way I can manually configure this, Never Urls:

SimpleScreenRecorder, the best simple screen recorder on linux that I know of.. I think it might be a wrapper around some shell commands. IDK.. But it would be nice if it were ported to other systems. Until then I use OBS which is overkill for most of what I do.. (Also in Windows Screen2Gif isn’t bad either.) Got it working on a system with nVidia and got this error: I don’t know what this means, what it does, or how to undo it.

Okay having used Windows and Mac OS for a couple years. Mostly due to driver issues. (Which didn’t abate, I had to effectively buy a new computer to solve my issues. Which is rather disappointing but I think I will be moving back to a desktop / laptop hybrid model again. Laptops have disappointed me recently but that’s a conversation for another day. Title bar customization So the move to KDE has been pretty nice in the most part.

This is mostly just a list of things to remind me what to install when I reformat / start using a new PC. But I decided I would share anyway. The prompt for creating this table wss actually discovering ksnip which resolved a lot of my cross platform screen shot pains. Tool Windows Linux Mac OS X Comments Screen shots ksnip ksnip ksnip Picking this up helped a lot as it was a major missing piece, I had tried things like, Shutter which became dependency hell every update as it isn’t a compiled tool and wasn’t cross platform.

So when you use docker with Synology it has a rather nice UI.. However it seems to be lacking things. Such as redownloading the images for any given tag as the SHAs don’t change but the tags do! -_- Saying that; this addition is nice: – Turns out adding itself over itself doesn’t work. And you can’t add the update by a different tag name and switch the tag on an “off” container.

Turns out I could crash ksplashqml quite reliably rendering my kde setup unusable simply by having a bad XDG_DATA_DIRS configured in my .zshenv file. I’m not sure what caused it. But it might be because it was already set, or that it ended with a : – Edit Actually a bit more looking around and it turns out it is if XDG_DATA_DIRS contains the same entry twice it crashes.

Ugh.. I would rather write here that I found this issue than log it myself. Because from what I recall from the bug logging process it can be pretty tedious. Especially with bugzilla. Perhaps Github / Gitlab has spoiled me with the ability to log very simple bugs quickly and easily. Maybe because web based interfaces were so hard to use back in the 90s, it was tedious to go through bug reports so simply reduce them by getting as much info upfront as possible including classification.

For some reason IntelliJ and Windows terminal discover available shells in different ways, but either way is not ideal. (In-fact IntelliJ uses two different means of discovery.) The terminal popup in Intellj seems to be unaware of Gitbash.. Which is in complete contrast to the terminal settings (same plugin) which is unaware of my WSL deployments. (Possibly because it’s using a file path based system) Which means I can’t set Debian WSL as my default terminal in IntelliJ.

Another one from the department of should have been a bug issue: Why doesn’t the GoLand “move” dialogue show you the receiver. When you’re implementing a new interface this can make it a bit hard to use when you start to refactor your code. -_-

So started using linux.. Getting this issue here: 1[ 499.624767] thinkpad_acpi: unhandled HKEY event 0x6031 2[ 499.624771] thinkpad_acpi: please report the conditions when this event happened to ibm-acpi-devel@lists.sourceforge.net 3[ 517.509897] thinkpad_acpi: unhandled HKEY event 0x6031 4[ 517.509905] thinkpad_acpi: please report the conditions when this event happened to ibm-acpi-devel@lists.sourceforge.net I really don’t want to have to mail a mailing list and learn how to engage with the community, how to write a post, and worst yet, having to subscribe to a mailing list to get a single response.

So.. Turns out the control panel mess that exists on Windows is contagious. After 2 years of using Windows (because of driver issues) I have finally been able to switch back to Linux.. However I got used to a couple settings. One was a faster mouse scroll speed… So I go to configure that and this is what I see: A quick google got me here: https://forum.kde.org/viewtopic.php?t=160416 Ugh no difference

Had an issue with getting MOK to install my keys for my Intel Corporation Wi-Fi 6 AX200 (rev 1a) wireless card on my Lenovo X1 Carbon Extreme G2.. Turns out there is a bug in the shell script that installs the self signed keys in to MOX… Which is great. But it turns out I have hit a bug.. Perhaps this is because I use zsh or some other reason but.

Small gripe.. But it seems that with a default install of KDE it the Akregator (RSS feed reader) comes pre configured with the KDE blog which doesn’t render correctly. -_- Not that it matters it seems there isn’t any syncing ability in Akregator meaning I will stick with Miniflux for now.

The login process and decryption/password-protected document workflow with Synology Office is not great. Probably needs to be looked at. I was going to try figure it out and provide a nice diagram of how it works, but I don’t have that much time to dedicate to this issue. But I get stuff like this, when my login as expired, instead of just presenting a login page, it gives me this;

Ugh. So it turns out AWS Glue (the new interface) when you are writing a script using the editor won’t take into account the region when you click the “cloudwatch logs” link section: I have no idea how something like this could pass. But it has. Turns out it will default to us-east-1. It seems to only occur in certain circumstances, however… Once I have selected a region post login (or account switch) it works fine.

So I bought a new speaker… A Logitech G560.. I had been eyeing this speaker for a while. I assure you it wasn’t because of the sound changing aspect. But there wasn’t really a lot to my reasons to pick it. One of the major points to me picking this is, in the absence of a good list of alternatives, brand loyalty. But other than that. I would have to say; Multiple input (Bluetooth, 3.

So I will be writing tech complaints here.. Here is the first one. Turns out Synology defaults the SSH to port 22… Then if you have enabled the security advisor it constantly complains that is set to port 22. Why not just set it to a random (but free) port? If you have to manually configure SSH to turn it on then you would be aware that it’s not running on a “standard” port.

Just creating this blog. It’s 100% a copy of: https://github.com/arran4/githubpages But I will add stuff to it. I intend to use this space to post more technical things. Probably just tech related complaints that are more wordy than Twitter will allow. On the plus side it’s all managed by hugo! Want to submit improvements to the layout.. Yes. But keep them small.