I built this browser tool which lets you quickly generate 3D printable boxes in your browser. It's pretty useful when you are rapidly iterating a design and need a box with specific parameters for internal capacity or external size without the effort of opening up CAD software.

It uses Three.js for rendering, and runs entirely in the browser (no server necessary).

It works in inches, mm, and also Gridfinity, which is a standard for making 3D printable storage units which stack nicely and fit along a 42 mm grid. It uses internal units of 10 nm, so that 100,000 are exactly one mm, and 2,540,000 are exactly one inch.

I have validated the numbers against the Gridfinity spec, but I don't have access to a 3D printer right now. I would love to hear what people think of it so far, or if one of you has a 3D printer nearby, I would love to know if it actually works.

Hi HN,

I built rust-gun (v0.1.0): a Rust workspace template + one CLI to standardize environment checks, tooling bootstrap, and running the full pipeline locally before pushing.

Core commands: - gun doctor: diagnose OS/Bash/Rust/Git/tooling issues early - gun ensure: install/verify required tooling - gun ci-local: simulate CI locally

It also wires in “gates” commonly needed in real repos: - quality: fmt/clippy/docs/coverage/bloat (+ optional spell/taplo/prettier) - supply-chain: deny/audit/vet - testing: fuzz/miri/sanitizer

Quickstart: 1) clone repo 2) run install 3) gun ensure → gun doctor → gun ci-local

Repo: https://github.com/codingmstr/rust-gun

I’d love feedback on: - what would make you adopt this in a real project? - which defaults/policies you’d change (deny/vet/audit)? - cross-platform edge cases to prioritize (Linux/macOS/WSL/Git Bash)?

For a while I've been looking for a tool that can monitor network connections down to individual sockets and with the ability to block or throttle traffic. Since the existing tools I found weren't able to do that I gave it a shot and tried to make my own.

Wächter (or waechter) is divided up into a demon using eBPF and tc for monitoring and controlling traffic and client using imgui for a simple GUI to control the demon. The demon can be connected to both via a unix socket or a web socket if you want to run it on a server and control it remotely. Eventually the goal is to also collect and visualize long term traffic statistics.

So far I was able to test it on Arch Linux with 6.18.3 and Ubuntu 24.04 LTS with 6.8.0. Since eBPF is a bit picky about whether or not it'll load a program depending on the kernel version people are welcome to test it on other setups and report bugs or request features.

I started with making a cognitive architecture and wanted to attempt a system that heavily resembles autopoiesis. An A.I that builds itself entirely.

With agents, I have I found myself using worktrees more and more. First manually, then with conductor.build, then with worktrunk.dev.

I prefer using coding CLIs instead of UI wrappers as the terminal tends to be more performant (depending on the agent you choose) and you get access to new features immediately.

Ghostty is a bit challening to automate today— I considered building a complementary app to Ghostty at first. But since I have been building native mac apps on the side lately (as well as tools for agents, consuming their logs etc) I figured I would just modify Ghostty to have native worktree management.

You can download with homebrew via: brew install sidequery/tap/ghostree