hop 00 entry
Developer · Security enthusiast · Self-hoster
Backend and network work, mostly in Go.
I run self-hosted services, game servers and DDoS protection on my own hardware, and probe the network from five vantage points.
I write Go in my free time: backend services and the networking they run on. That means HTTP APIs, Postgres with sqlc-generated queries, and ClickHouse for anything time-series and heavy.
Further down the stack I reach for nftables, netlink and XDP to push packet handling and load balancing into the kernel, which is also what my DDoS protection runs on. All of it lives on hardware I host and run myself.
Profile
A live read from my own monitoring stack at sp.tumult.dev: ICMP latency to backbone, DNS, CDN and tier-1 networks, probed from five vantage points.
Five concurrent map implementations across eleven core counts on a 48-core EPYC. Reads scale close to linear for all but one, and the ranking reverses once writes are in the mix. Churn throughput drops every time the core count crosses a power of two.
Sixteen hash candidates across every key shape and length I actually use, benchmarked on the box the code deploys to. The length answer was boring. The type answer was not, and neither was the 7x a string-to-bytes cast costs on the way in.
Three things move a Go TLS 1.3 handshake and they are not close in size. Certificate key type is the biggest lever by far, post-quantum key exchange costs a real 25%, and a keygen patch claws back 9 to 15%.
tumult1337