videah.net

The fresh new videah.net

videah — Thu, 03 Sep 2026 00:00:00 GMT

The fresh new videah.net

Posted on September 3, 2026

It’s an unfortunate fact of life that every tech-savvy person who writes any kind of long-form content is born with an evil curse that compels them to spend more time coming up with increasingly complex byzantine blogging engines than actually writing any blog posts that use them. It’s been well over a year since my last written post, which means it’s time to deploy the latest iteration! The twist this time is it actually ends up replacing two websites.

Yes! My blog and personal site are now one and the same. The old terminal-style site was cool for the time, but I think it’s now a bit overplayed and was very limiting. Who the hell wants to type to navigate a website? Especially on mobile, oh man!

Feel free to look around, if you have any feedback on the new design I’d love to hear it!

For fun silly things I recommend checking out my 3D model display or going to the homepage and clicking on my pixel art nose.

Out with the Markdown

The old blog used Zola to generate HTML from some Markdown. It’s as nice as static Markdown site generators get. But over time I couldn’t escape the feeling that Markdown was leaving something to be desired. I think the simplicity of Markdown ends up getting in its own way a bit. I grew to hate writing Markdown.

I found myself repeatedly trying to work around its limitations using Zola’s shortcode system which lets you inject some custom HTML components. These are just hacky macros at the end of the day though, they’re not very ergonomic and you can’t do anything crazy with them.

This new website on the other hand is written in Typst, a modern markup language intended to replace LaTeX for document writing. I’d used it in the past to write my resume when I was applying for a job so I already had some good experience with it. When I noticed they were adding HTML support as a build target, I got really excited! It’s not fully mature yet but with the help of some plumbing from Rheo I think it’s crossed the threshold as just an all-round better alternative to writing Markdown.

How about some examples?

I think it would help to show off some of the code powering the site to give you a good idea of what it’s capable of. Starting off simple, the fursona callout box further up the page is a reusable component that I can call anywhere in the document like so:

#sticker-callout("poggers", side: "right", flush: true)[
The old site and blog are not completely gone!
]

Which I think is just a really nice and simple syntax for that kind of thing.

Then consider this snippet of code from /elsewhere that takes a list of my social media accounts and renders them as a list of links:

#let accounts = (
("GitHub", ("https://github.com/videah", "@videah")),
("YouTube", ("https://youtube.com/@videah", "@videah")),
("Bluesky", ("https://bsky.app/profile/videah.net", "@videah.net")),
)
#let me-link(url, body) = html.elem("a", attrs:
(href: url, rel: "me")
)[#body]
= Accounts
#list(..accounts
.pairs()
.sorted(key: ((name, _)) => lower(name))
.map(((name, (url, handle))) => [#name: #me-link(url, handle)]))

This lets me easily add new handles and have it automatically render a list in alphabetical order. No need to maintain the order manually. This is all done in-line in the Typst document alongside written content. Cool right?

We can also pull off some more advanced stuff, like this snippet that helps transform all native emoji to the custom Mutant Standard emoji I use on the site:

#let mutant-transform(doc) = {
show raw: it => _untransformed(it)
show _emoji-re: it => context {
let cps = it.text.codepoints().map(c => c.to-unicode())
let key = cps
.filter(c => c != 0xFE0F)
.map(c => str(c, base: 16)).join("-")
if no-emoji-transform.get() or key not in _index.seq {
it
} else {
mutant-emoji(_index.seq.at(key), text: it.text)
}
}
doc
}

This is great because it means we don’t need to do any JavaScript runtime transformations like Twemoji does, this is all done at compile time!

This seems like a lot… is it a lot?

The appeal here is Typst can be as simple or complex as I need it to be. I can just write posts normally and reach further down to the more programmatic stuff when I feel like it and have it all work seamlessly in a single plain-text document file.

This doesn’t even touch on the future potential this unlocks! Like writing once and having it spit out PDFs and EPUBs alongside the HTML output, which I’ll likely be using in the future for my resume.

You can read a little more about the tools powering this site at /colophon.

Plex Might Be Inadvertently Bottlenecking You

videah — Mon, 12 May 2025 00:00:00 GMT

Plex Might Be Inadvertently Bottlenecking You

Posted on May 12, 2025

Plex has this Relay feature that basically pipes your traffic through their servers if direct access isn’t possible for whatever reason, bypassing NAT and presumably cutting down on their support tickets.

For free users the relay is capped at a measly 1 Mbps and the ever-growing expense that is the Plex Pass subscription service only bumps this up to a whopping 2 Mbps.

I can imagine this being useful for a selection of people. But as this feature is turned on by default, it’s very easy for any issues with your server’s network configuration to go unnoticed. It turns out my port-forwarding rule for Plex hadn’t been working for several months (thanks Ubiquiti) and I never noticed because the relay feature was masking the problem.

It doesn’t help that the remote-access configuration UI has been very buggy for 6+ years, making it impossible to tell if the issue is with your server or the broken interface.

So please don’t make the same mistakes as me. Make sure your Plex client is actually connecting to your server directly, and use a Port Forward Checker.

Attacking My Landlord's Boiler

videah — Tue, 22 Apr 2025 00:00:00 GMT

Attacking My Landlord's Boiler

Posted on April 22, 2025

A little while ago I moved into an apartment to live on my own for the first time. This has given me a decent amount of newfound freedom to sculpt my living environment to my liking, but not enough where I could start knocking down walls. I have a landlord (and a deposit!) to think about, after all.

While it isn’t near the level of knocking down walls, I was finding heating my apartment rather frustrating. The boiler’s thermostat installed by my landlord is a single radio-controlled unit that uses a built-in temperature sensor to modulate the heating on and off to meet a target temperature. This presents a few first-world problems:

The temperature sensor can only sample a single room in the apartment, which heats unevenly.
That room is dependent on the physical proximity of the thermostat’s controls, which can be annoying to use if I might be in bed and the controls are in the living room or vice versa.
If I forget to turn the heating off before I leave the apartment, I’m wasting a lot of costly energy.

I automate things around my apartment with Home Assistant, and I wanted to be able to do the same here. There are a lot of off-the-shelf solutions for this, obviously, but to get back to the knocking-down-walls comparison, they would require my landlord’s cooperation and likely a visit from an electrician. I don’t want that!

Instead, here’s how I figured out how to control my apartment’s heating in a way that leaves no trace using the existing thermostat already fitted by my landlord, and maybe learn a bit about radios along the way.

Where Do We Start?

I knew that the thermostat communicated with the boiler through some kind of radio protocol. We could try to reverse-engineer the protocol from scratch, but as I’ll get into later, that turns out to be very involved and way beyond my minimal radio skills.

I eventually decided it was a lot easier to attempt something called a Replay Attack. This involves cloning the signals sent between the boiler and the thermostat, and then pretending we are the thermostat by re-broadcasting the signals. This way we don’t need to understand the protocol, just replay it.

Initial Reconnaissance

The first thing I did was check to see if there was any information online about my specific thermostat. I came across a listing for the exact model I had, along with a datasheet in the attachments section. The section on RF Communication is exactly what I was looking for:

From this, we know the thermostat communicates around the 868Mhz range. The Protocol: Encrypted part was initially a bit concerning, but it turned out to not be a problem.

The first issue I’m running into here is that there are shockingly few resources on cloning a 868Mhz signal online. Most beefy resources were about using LoRa/Meshtastic. I would come across a lot of Reddit posts of people trying to do the same thing as me for things like ceiling fans and garage doors, but nobody seemed to have any answers…

Seeing Signals

So without much to go on, I thought the first thing to do would be to actually see the radio packets and inspect them. I’d read about Software-Defined Radios in the past and guessed it’d be my best bet. Most SDRs are really expensive, so I went with the budget RTL-SDR V4 off of AliExpress. (This actually ended up being somewhat unnecessary for reasons we’ll eventually get to!)

After it arrived, I hooked it up to my laptop with the SDR++ software just to see if it worked and get an initial glimpse of my thermostat yapping. After pressing the thermostat’s buttons a few times, I managed to see the waterfall light up!

The “waterfall” at 868Mhz showing long horizontal blips.

This step isn’t super important, but we can then try to use the rtl_433 tool (it works on other frequencies despite the name) to see if the thermostat is speaking a known protocol. More obscure devices might not work here!

It seems like this thermostat speaks the same protocol as another Honeywell one. The demand attribute sets whether the boiler is on (1) or off (0), and then the boiler responds with an acknowledgement (presumably so the thermostat can determine if it’s out of range).

Trying To Yell Back

Now that we’ve actually seen the back-and-forth communication, we want to be able to send some packets ourselves and puppeteer the boiler as if we were the thermostat.

Using a 868Mhz Challenger Dev Board, first failed attempt…

This was the step I got stuck on for months. I was trying the “smart” route of attempting to reverse-engineer and reconstruct the packets by hand using URH and then broadcasting them with very cheap 868Mhz microcontroller boards. I can safely say this was all wayyy outside of my skill set. None of the boards were really designed to talk to anything other than the exact same board, and going any further than that required poking at radio registers in ways I wasn’t comfortable doing.

The HackRF

The official HackRF One board, going on to spawn many AliExpress clones.

I decided to then go for the sledgehammer approach: use a full-blown SDR to just replay the exact same signal without a care for what the signal actually contains. But the cheap RTL-SDR I got earlier only supports receiving, not broadcasting. SDRs that can broadcast are usually hundreds of dollars.

I say usuallyyy because one of the most common broadcast-capable SDRs, the HackRF One (usually upwards of $400), had numerous clones available on AliExpress for a fraction of the price—just $40.

There are some obvious ethical (and probably a few technical) problems with cheap clones of what is meant to be open-source hardware, but I figured it’d be fine for my small use case. Please support the original hardware project if it’s within your means to!

Actually Yelling Back

With the HackRF in hand, we can use the hackrf_transfer tool to record signals and, most importantly, replay signals. I perform these commands and then press the appropriate controls on the thermostat to write the signals to individual files:

# We set the frequency to 868.3Mhz and the sample rate to 2000000.
hackrf_transfer -r turn_off.raw -f 868300000 -s 2000000
hackrf_transfer -r turn_on.raw -f 868300000 -s 2000000

And then we can try and turn the boiler off and on from CLI like this:

# We use -a to turn on the amplifier and -x to increase the gain a tad.
hackrf_transfer -t turn_off.raw -f 868300000 -s 2000000 -a 1 -x 23
hackrf_transfer -t turn_on.raw -f 868300000 -s 2000000 -a 1 -x 23

After doing this, I could hear the physical relay inside of my boiler turning on and off!

Automating The Whole Thing

My HackRF clone in a 3D printed case, plugged into the server.

I have the HackRF plugged into a powered USB hub connected to my Home Assistant server. I wrote a very basic web server that simply shells out to the transmit commands above in a Docker container.

Then with an Average Sensor Plugin and the config YAML below:

command_line:
- switch:
name: Boiler
command_on: "curl http://docker-vm:1111/api/on"
command_off: "curl http://docker-vm:1111/api/off"
sensor:
- platform: average
name: "Average Temperature"
entities:
- sensor.bedroom_thermostat_temperature
- sensor.kitchen_thermostat_temperature
climate:
- platform: generic_thermostat
name: Boiler Thermostat
heater: switch.boiler
target_sensor: sensor.average_temperature

We have a working controllable thermostat!

At this point I was just happy to have the thing working after so many months, so I’ll be the first to admit this setup with Home Assistant is a bit slapdash and could use some cleanup. It’d be better to write a proper plugin and control the radio directly instead of shelling out to the CLI. Relying on curl to heat my apartment is maybe a bit cursed?

Was It Worth It?

Grafana graph showing the temperatures following the target one.

I’ve been using this setup to control the heating of my apartment since the beginning of December and haven’t had any issues since! It’s super convenient to dial in the temperature from my phone, and the automations I have make me feel like this project was really worth the work.

I have some basic automations like having the temperature go down when I’m sleeping and then up in the morning in time for me waking up, but I also have it so the heating turns off when I go into town and turns back on when I’m just a few train stops away so my place is nice and toasty for me getting home!

The only thing I’m not happy with is needing to use a very powerful and versatile radio like the HackRF for something as simple as a boiler on/off switch. But I’d rather use something overkill and have it work than spend ages trying to force smaller radios to do my bidding.

The important thing is I’m not as cold as I used to be!

My E-Reader Setup

videah — Thu, 10 Aug 2023 00:00:00 GMT

My E-Reader Setup

Posted on August 10, 2023

I bought an e-reader recently, specifically the Kobo Libra 2. I felt like I wasn’t reading books/manga as much as I wanted and I think the convenience of being able to carry my entire library around with me will help with that. I own an iPad Pro but I wanted a device I didn’t need to think about charging that often and wouldn’t give me eye strain.

This post is a bundle of notes about my current reading setup.

The Libra 2

I spent several hours doing research and I think the Libra 2 is the best device on the market at the moment, at least for my needs.

I picked it up in white to try and make an important psychological distiction. I wanted it to differ from every other electronic rectangle I own and treat it more like a nice book rather than a computer that will inevitably make me angry. Which all things considered is quite funny with all the computer nonsense I ended up doing to it.

It’s got a 7-inch screen which is a little shy of the perfect Tankōbon volume size, but close enough that manga is comfortable to read. I remember reading somewhere that the screen has one of the best contrast ratios in an e-reader and it is indeed very good.

The lineart of Junji Ito’s Uzumaki looks very crisp on this display.

Navigation buttons are a dying breed in the e-reader space but I really can’t live without them. Using a touchscreen to navigate is hateful and is really fake skeumorphism. You can pretend all you want but it does not feel like you are flipping a page! Thankfully the Libra 2 has two buttons on the side where you hold it so you can go back and forth with just one hand.

I got the very overpriced official SleepCover case in orange. Matches my iPad case. Stops the plastic from making flexing sounds. It can let your e-reader stand upright for some reason.

Book Management

The only real book management software in town for e-readers is Calibre but it’s stuck in the late 2000′s UNIX school of UI design and I reaaally don’t want to deal with that kind of thing anymore. I want organising my books to feel comfy. I also don’t want it to depend on having my laptop with me, constantly wiring it to my e-reader to sync new books.

Calibre on macOS. It is very noisy.

It’s not perfect but Calibre-Web works better for me. Despite the confusing name it’s a completely distinct project that just happens to be compatible with Calibre’s database format. I have it hosted on my personal VPS so I can access it anywhere and can give friends access if I need to. It’s not quite Plex for books but it is close. The bootstrap UI is a little dated but it works for what I need.

Reader Software

The default reader software the Libra 2 comes with is called Nickel and it’s fine. It looks and runs ok enough and the built in Kobo Sync functionality can be tweaked to work with my Calibre-Web instance by replacing the endpoint in a config file, which I have to give Rakuten props for letting you do.

But sideloaded files can be very broken. I was half way through a book before I realised Nickel was just throwing all of my notes and highlights into the void whenever I closed it, which was very rude. This is apparently a common problem that’s been around for a while and it seems Rakuten have no plan to fix it anytime soon.

I went looking around for some open source alternatives. Most people reach for KOReader. It runs on pretty much everything and is packed with an ungodly amount of features and has a steady community built around it.

Comparing library views for KOReader and Plato.

But if I’m being honest I just can’t find any enjoyment using it. The user interface just isn’t up to snuff. It feels impossible to navigate and there is no real library view, only a file manager. When I’m holding my e-reader I don’t want to be reminded that it is a computer all the time. It’s meant to be a book!

I came across Plato which is made exclusively for Kobo devices and worked on by the guy responsible for bspwm. It’s really fast and responsive, more so than Nickel even. The UI is pretty much exactly what I’m looking for. It’s not nearly as feature complete as KOReader but it’s written in Rust which is a language I feel confident enough in to tweak and implement things to my hearts desire. I’ve already made a small change that got merged upstream too!

Syncing

Originally I was using Kobo Sync with the endpoint changed to point to my Calibre-Web instance to sync my books wirelessly. But it was buggy and slow and could only pull in KEPUB files.

Plato has a built in hook system that lets you run arbitrary binaries when a directory is opened. Using this I wrote a small CLI tool that just pulls every book that hasn’t been downloaded yet from my Calibre-Web instance using the OPDS protocol.

In the future I would like to take advantage of this hook system to also sync reading positions and other metadata Plato stores.

Tailscale VPN

I love plugging as many of my devices into my Tailscale network as I can and I thought it’d be a fun little project to try and get it running on the Libra 2. Someone had already done most of the work by getting it to run on the Kobo Sage.

It turns out it’s a little harder for the Libra, I had to spend a ridiculous amount of time compiling some missing kernel modules in a horrendously slow emulated x86 emulator just to get this thing running. The joys of owning an ARM laptop. I think being able to type ping kobo and have it Just Work makes all the hours spent worthwhile though

Tailscale has a built in AirDrop-esque file transfer feature that I find really useful for quickly sending PDFs to my e-reader that I don’t necessarily want to be a permanent part of my library.

Sending a PDF remotely with one click with TailDrop.

Unfortunately I couldn’t get Tailscale SSH working which was one of the main reasons I attempted this in the first place I’m not sure why but my first guess would be that I need iptable packet filtering but that would require swapping out the whole kernel which I don’t feel comfortable doing at the moment. Maybe some day though.

SSH

The Libra 2 only has telnet support out of the box behind a developer cheat code (typing devmodeon into the search bar) which is fine because I’d be using it over a Tailscale wireguard connection anyway. My threat model doesn’t exactly involve people bruteforcing telnet over public WiFi just to steal my furry books. But for completions sake I stuck the Dropbear SSH server on mine and then disabled telnet.

Storage

The Libra 2 has 32gb of internal storage which is pretty huge for books considering how small EPUBs usually are. But I like reading manga which can be pretty hefty. An average volume is 200mb, with stuff like Uzumaki coming in at 800mb. What if I need to store every uncompressed volume of One Piece for offline reading in the event of the apocalypse?

Most e-readers treat manga as secondary to books and rarely offer higher storage options or mini-SD card slots anymore. Thankfully the Libra 2 has a mini-SD slot… it’s just an internal one not meant to be user accessable 🫠

Libra 2 internals, SD card highlighted in the red circle.
Image taken by MobileRead user ‘supermighty’

This is better than not being able to upgrade the storage at all though and was actually one of the main things that pushed me in the Libra 2′s direction when doing research. Someone on the MobileRead forums replaced the SD card and posted instructions on how to do so.

I haven’t done this for mine yet but I plan on giving it a shot and sticking something utterly ridiculous like 512gb or 1tb in there. It seems like a pretty risky/messy mod to do though, the slot and card are caked in waterproofing glue that you’ll need to reapply afterwards if you’re like me and enjoy reading in the bath.

Even if this seems excessive it does let me sleep easier at night knowing I can replace the internal storage in the event it somehow fries itself.

Dictionary

This is a feature I didn’t know I wanted till I used it. It’s a pretty big leg-up over reading physical books when I can easily hold down on a word I’m not sure about.

I’m using the ebook-reader-dict project which is based on Wiktionary since that’s the one Plato recommends and is designed to work with. Unfortunately it’s a bit hit or miss. I’m not too happy about the quality of the definitions sometimes, I’ll probably look at alternatives at some point.

Font

For reading, I use the font Atkinson Hyperlegible which you might know from Cohost, but it’s also used by the very blog you’re looking at now! I’ve fallen in love with it as it’s really easy to read even when the text is very small. Very pretty and accessible.

Web Push Pitfall

videah — Thu, 30 Mar 2023 00:00:00 GMT

Web Push Pitfall

Posted on March 30, 2023

Whilst implementing Web Push notifications for my toy Q&A service curiouswolf I ran into an issue that led to me being stumped for hours. I was successfully receiving notifications from my server when using Chrome, but no matter what Safari was not playing ball.

Web Push requires the browser maintainers to run a notification endpoint. For example, when you use Google Chrome and you enable notifications on a page, your encrypted notifications get funneled through a server Google controls. In the case of Safari however, their endpoint was returning BadJwtToken for me despite it being considered valid by Google.

The Solution

It turns out that Apple (and Mozilla apparently) require you to include a sub claim in your JWT with a method of contact (such as an email) for them to consider it valid.

If you are providing an email, the sub claim should be prefixed with mailto:

{
"sub": "mailto:admin@example.com", // <-- The important part
"aud": "https://web.push.apple.com",
"exp": "1680135079"
}

The reasoning behind this is to provide the operator of the endpoint with a means of contacting you if there’s an issue. However, this technically goes against the Web Push spec, and it’s frustrating that something like this isn’t spelled out clearly in Apple or Mozilla’s technical documentation.

Notice the emphasis on the word MAY

Apple quite regularly leave important information out of their docs for web APIs like this, but it’s really messed up that the only place Mozilla talk about this is in a blog post from 2016.

Howdy, Is This Thing On?

videah — Mon, 14 Nov 2022 00:00:00 GMT

Howdy, Is This Thing On?

Posted on November 14, 2022 • Banner by @mollowmollow

Since things are uh… collapsing? I thought it’d be a good idea to finally get my blog up and running. Come in, get comfy and take a look around! Cozy right?

Getting Started (Again)

Ok admittedly, this is my 4th attempt at making a blog. This time I’m using Zola which is like Hugo or Jekyll but more Rust-y and less JavaScript-y. I can’t make any comparisons beyond that because I haven’t used either, but my initial impressions of Zola are good! The theme you’re looking at I made from scratch using Tailwind which is the only way I can do frontend web stuff now.

I wanted to move away from what I had been using in the past (Ghost) and have my blog sit in a git repo in plain text instead. How I currently have things set up means when I push any changes to the blog’s GitHub repo an action runner will automatically build my site (in about 17ms!), compile Caddy, embed the site into the binary using caddy-embed (in… a lot more than 17ms!), then finally push it as an image to DockerHub. My server will then see this new image, hot-swap it, and start serving my blog straight from memory!

Little Gremlin

I hope you like my little rantsona in the sidebar! He took the longest to get working out of everything if you can believe it. I can disable him on a per-article basis, you don’t have to worry about him -ing the more serious posts.

You can’t see him unfortunately (try looking at this page on a larger screen) but I hope you like my little rantsona in the sidebar! He took the longest to get working out of everything if you can believe it. I can disable him on a per-article basis, you don’t have to worry about him -ing the more serious posts.