It's the little things.

It's been a few days since I posted. Mostly because I've been head down, partly because the last stretch taught me a couple of things I wanted to sit with before writing them up. Basically:

Rushing a fix

An outside contributor found a real problem in 1.4.1. When you pasted certain private keys and hit Cover it, part of the key could be left behind in your message. For a tool whose whole job is keeping that stuff out of an AI chat, that's promise-breaking, and I treated it that way. I fixed, tested, and shipped it as fast as I reasonably could.

That's where I messed up first. In my haste to get the fix out, I overlooked the kind of attention to detail I usually pride myself on.

Once the release was out and the anxiety passed, my brain naturally started to wander again, and that's when things started to sink in. What if the key's last line is missing? What if it's sitting inside a web address? What about PRIVATE_KEY=0x and a long string of hex in a .env file? I went looking, and between my own digging and a long run of test attempts against the public version, I found and fixed nine shapes where 'Cover it' could leave part of a secret behind.

All nine are fixed in 1.5.0, each with its own test.

The lesson for me is that a fix isn't worth much if it leaves more problems than it solves. Taking my time and paying attention to the details is the actual job. It's the little things (Or so Denzel said).

Dead buttons in Clotr for Windows

On the Windows side I found more than a handful of buttons that didn't do anything. Six of them, to be exact. I most likely broke them while I was working on the export feature, and nothing told me, because nothing was checking lol.

I built a new test that checks every button in the app is actually connected to the thing it's supposed to do.

I also found Clotr for Windows could set up its connection to your browser before you'd agreed to it. Nothing was sent anywhere, but the connection point was registered before you said yes, and that's the wrong order. It now waits for your consent.

What's next

I'm freezing releases for a little bit. This is the culmination of over a year of solo development, and I'm getting some really valuable community input. I want to make sure all my 'i's are dotted and 't's crossed before I do much else. A new term at school is starting, so I'll need to shift focus a bit more.

If you find something that looks wrong, please tell me. The individual that found the issues in 1.4.1 really made my week. A lot of what I'm doing is a product of therapy, so the validation of at least one person seeing the project's worth does more than I could put into words. Your feedback matters.

To reply, open an issue or a discussion on GitHub.