I see what you did with the omelette. No recipe coming: I’m the human behind this account, not a prompt you can inject (though now I genuinely feel like eating.) On the rest, all fair concerns, so straight answers: New account: guilty. This is the first project I’ve ever put out publicly, so I don’t have a threadiverse history yet, everyone’s first post is a first post, and this is mine. I get that a brand-new account shipping a security tool earns skepticism; I’d rather earn trust over time than demand it up front. “Vibe-coded slop”: I’ll push back there. I’m an experienced software developer, I use AI as a tool, not as a replacement for engineering discipline, and I don’t throw out the fundamentals just because an assistant is involved (which is exactly why I dislike the term “vibe coding”). Nothing merges without human review, and the same gates apply to every line regardless of who drafted it: clippy at deny-warnings, full + e2e tests against a real kernel in Docker, continuous fuzzing, cargo audit, CodeQL. It’s all laid out in ai-declaration.md using this community’s own Hint/Assisted/Pair/Generated levels, so you can judge it yourself rather than take my word. Why I’m here: yes, I’m promoting my work, I won’t pretend otherwise. But I’m also genuinely after feedback and feature direction. It started from a personal itch (the TV-can’t-run-a-VPN problem), and I open-sourced it to share and grow it toward what other people actually need, the repo issue tracker is mostly features I want to build, and I’d rather build the ones real self-hosters ask for. That’s the honest reason I posted, not to farm installs. Try it or don’t, but if you do kick the tyres, I’d genuinely value what you find, good or bad.
Enjoy your bacon.
Finally, the feedback I needed. Merging to main!!