Tag
#rust
17 entries
craft
Is it ready? We iroh'ed out the basics
“Have we ironed out the basics? We iroh'ed them out — and now I get to go build the thing this whole substrate was always just an excuse for.”
Jul 03
craft
A certificate that rides the gossip — and why I moved it
“The tidy, clever mechanism — trust that rides the gossip and survives a relay — lost to the boring one that checks the credential where it gets spent.”
Jun 30
craft
Extending the mesh with node caches
“A cache that only learns is a leak. It has to forget on the same clock the mesh forgets.”
Jun 26
craft
Keeping a node's name across a restart
“The data dir isn't where the node keeps its identity. The data dir IS the identity — which is why the scariest bug was a five-second timer.”
Jun 23
craft
The bug that wasn't in the mesh
“Write your root cause as a sentence you'd be willing to have your own logs contradict. Mine did, and the cure was 30 seconds of debug logging — not another rebuild.”
Jun 16
craft
Kill by message, not by ownership — and a node is a state
“Which OS process happens to own a node should have nothing to do with who's allowed to operate on it. A kill is a message, not a syscall.”
Jun 12
craft
The relay is a postbox, not a peer
“The relay is an untrusted postbox: you trust it to forward, not to read or vouch. The keys do the vouching, point to point, direct or relayed alike.”
Jun 09
craft
Make the cross-mesh view honest
“A dependency graph is only as honest as the spans under it. If a service name is too coarse, nodes merge; if a receiver emits nothing, edges vanish; if you cc the observer, fake edges appear. Fix the emission, not the picture.”
Jun 05
craft
Watching a node boot, then a second mesh with no bridge
“A node that does work without leaving a trace is a bug. Start with the trace; everything else hangs off the spine it gives you.”
Jun 02
craft
Hunting a connection leak the soak test wouldn't explain
“When a leak resists reasoning, stop reasoning and instrument it. A spawned-vs-finished counter found in minutes what hours of reading the reap path missed.”
May 29
tools
Open-sourcing the Rust Distributed Mesh
“Not a library to take and use. A kit to read while you're paying the same costs I just paid.”
May 22
craft
Chaos-pass replaces tests-pass
“Steady-state-only passing is insufficient. The cluster has to survive being broken.”
May 15
craft
Four days into the soak, the RAM was still climbing
“The worst CPU offenders had zero active peers. That's the fingerprint of dead-state accumulation.”
May 08
craft
Flamegraphing your way out of "this can't possibly be right"
“Comments lie. Flamegraphs don't.”
May 01
craft
When 18 nodes pegged my 80-core box at 100%
“Three obvious wins got the host from 100% to 35%. Still wrong, just less wrong.”
Apr 24
craft
Why I'm building a distributed mesh substrate in Rust
“I want to feel where the iroh-as-substrate story breaks at small scale before betting a real product on it.”
Apr 17
tools
Open-sourcing the Connected Products Starter Kit
“The first 30 days of a connected-product team are mostly the same six pitfalls. Open-source what doesn't need to be re-discovered.”
Oct 22