* Reconstructing `$HOME/git` after an unfortunate `rclone sync` wiped it. It was not fun discovering that my backup was on the wrong `git` directory and also that I'd not committed some stuff for ... years. Lesson learned, etc. * Implementing three new bot ideas. * Trying desperately to stay out of the "we must vibecode!" juggernaut's path at work. * Wasting hours having to manually download Every. Single. Model. from my MyMiniFactory library because they don't provide an API, a bulk download, or a sync to something like Dropbox. (1500 down, about 4000 to go!)

Building wireless (LTE-based) sensors for most major horticultural sensing needs. Measurements include:

- CO2. Side note: I was surprised to find that most (all?) CO2 sensors used in closed plant production setups are not meant to operate below 400 ppm.

- Air temperature, pressure, relative humidity

- Photosynthetically Active Radiation (PAR)

- Addons like: wind speed, wind direction, soil moisture and Electrical Conductivity (EC)

- The coolest and most challenging: pH, EC, and flow rate

The hardest part has been running everything on battery while maintaining accuracy and using LTE (2–4G) and not common LPWAN options like LoRa. I'm primarily a software guy, so the learning curve has been huge.

Working on Fairvisor — a tool for API governance and usage control.

The problem: one buggy integration, scraper, or infinite retry loop can suddenly explode your API costs or overload infrastructure before anyone notices.

Fairvisor acts as a guardrail in front of your API:

per-tenant and per-route rate limits

request budgets and soft/hard caps

anomaly alerts for sudden spikes

The edge component is open source (OpenResty / Nginx + Lua) and the SaaS part provides policy management and audit.

Still early, validating whether teams would use something like this instead of building internal scripts.

https://github.com/fairvisor/edge

I was using Wisper Flow and had a pretty bad experience with their support related to billing and so I started building my own version of a speech to text app, it's very doable with Parakeet and Whisper models available now. I've got the app working on mac and it's been so much easier to make progress on it with AI available now.

I'm not sure I'll be putting it out there because it feels like there's already 100s of these apps out there so I don't feel strongly about it.

I've been working on my local server mocking tool Decoy: https://decoy-app.com/

I've built it earlier and also did a Show HN, now I am going through some of the steps that get recommended to me such as creating Product Hunt launches, etc. But I am struggling a bit with the concept of PH. What is the audience? People into new apps? It all feels a bit desperate to be honest and this app is just a hobby side project, I am not.

So if anyone knows of a good way to get some attention to my useful fun tool, please let me know.

A bunch of ideas that have had domains but never enough engineers. Now there isn't enough time it seems except when I've hit my LLM subscription limits and they need to cool down.

Already launched biz-in-a-box.org and a life-in-a-box.org spinoff as frameworks to replace every entity's QuickBooks. I'm using them myself for every project my agents are spinning up.

Stealth project is related to classpass but for another category of need that won't go away even in the age of AI that really is only possible with critical mass of supply to meet existing demand. Super excited cus there's no better time to build with unlimited agents that scale without people problems.

Lastly, can't wait to run local LLMs so no longer limited by tokens/money.

Mostly art projects:

- VR version of Surface Browser (3d internet browser): https://boxc.net/surfacebrowser.html

- Crowd Strike: faster self-driving: an exhibition where the visitors help autonomous drones target a different visitor each minute with lasers

and also Wingman: a dating app secretary (privacy focus, runs locally on your computer for any dating app that has a web site. It tells you if favourites have messaged you): https://boxc.net/wingman_app.png I'll open source this one if interest.

I built Collider, A wrap-based package and dependency manager for Meson.

I needed a way to use and push my own artifacts in Meson projects. WrapDB is fine for upstream deps, but I wanted to publish my packages and depend on them with proper versioning and a lockfile, without hand-editing wrap files.

Collider builds on Meson’s wrap system: you declare deps in collider.json, run collider lock for reproducible installs, and push your projects as wraps to a local or HTTP repo. It’s compatible with WrapDB, so existing workflows still work: you just get a clear way to use and push your own stuff. Apache-2.0.

https://collider.ee

I’m working on a small deployment tool called push2start[1]. The goal is to make Docker Compose apps easier to deploy from a laptop to a remote server without a lot of custom scripts. Right now, I’m trying to keep Compose as the source of truth and avoid creating another mini orchestrator. You point it at a compose file, it transfers only the images that need to come from local, then deploys and gives status, logs, and restart controls from one CLI.

[1]https://github.com/kwakubiney/push2start

I've been reworking my blog to have a table of contents per article, clean CSS (something that actually looks nice and no longer relies on Bootstrap) and a few other nice things. Also taking the opportunity to fix minor errors in previous posts.

Aside from that, I need to document and properly release one of the pieces that PAPER is relying on (some generic tree-processing code that makes operations on directory trees a lot nicer than with the standard library "walk"s), and work on others (in particular, a "bytecode archive" format for Python that speeds up imports for some projects, mainly by avoiding filesystem work at import time — I want to offer it as an install-time option in PAPER, and later have `bbbb` make wheels with the bytecode precompiled that way).