<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Go on Ilya Rusalowski Hub</title><link>https://rivik.dev/tags/go/</link><description>Recent content in Go on Ilya Rusalowski Hub</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 06 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://rivik.dev/tags/go/index.xml" rel="self" type="application/rss+xml"/><item><title>validgo-gen: OpenAPI → Go Validation Done Right</title><link>https://rivik.dev/validgo-gen-openapi-go-validation-done-right/</link><pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate><guid>https://rivik.dev/validgo-gen-openapi-go-validation-done-right/</guid><description>My colleague Yury built validgo-gen — an OpenAPI 3.0 → Go generator that finally distinguishes missing fields from explicit nulls from zero values. Two-layer validation, chi integration, idiomatic output.</description></item><item><title>ykvault: Stop Storing API Tokens as Plaintext</title><link>https://rivik.dev/ykvault-stop-storing-api-tokens-as-plaintext/</link><pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate><guid>https://rivik.dev/ykvault-stop-storing-api-tokens-as-plaintext/</guid><description>Are you still keeping API tokens in ~/.secrets? Any app you install can read them. ykvault encrypts every secret with a YubiKey challenge-response key — each get/set requires a physical touch, and the encrypted files are useless without your key.</description></item><item><title>I was afraid of agents yolo-mode for half a year</title><link>https://rivik.dev/i-was-afraid-of-agents-yolo-mode-for-half-a-year/</link><pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate><guid>https://rivik.dev/i-was-afraid-of-agents-yolo-mode-for-half-a-year/</guid><description>Why I built agent-landlock — a small Go wrapper that uses Linux Landlock LSM to give coding agents YOLO mode without letting them escape the project directory.</description></item><item><title>When TLS 1.3 Silently Dies Inside Your Android Proxy</title><link>https://rivik.dev/when-tls-1.3-silently-dies-inside-your-android-proxy/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://rivik.dev/when-tls-1.3-silently-dies-inside-your-android-proxy/</guid><description>A post-mortem of intermittent HTTPS failures across a mobile proxy fleet: TLS 1.3 handshakes silently dying on memory-starved Android devices — large multi-packet handshake messages, inflated by post-quantum key shares, stressing proxy buffers under memory pressure.</description></item></channel></rss>