<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: naultic</title><link>https://news.ycombinator.com/user?id=naultic</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 15 Jun 2026 05:06:53 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=naultic" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by naultic in "Doom entirely from DNS records"]]></title><description><![CDATA[
<p>lol now I wanna build this. It's like the dark web but without user or in this case, site consent. This could be a fun few weekend project</p>
]]></description><pubDate>Thu, 26 Mar 2026 21:03:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=47535680</link><dc:creator>naultic</dc:creator><comments>https://news.ycombinator.com/item?id=47535680</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47535680</guid></item><item><title><![CDATA[New comment by naultic in "Show HN: Optio – Orchestrate AI coding agents in K8s to go from ticket to PR"]]></title><description><![CDATA[
<p>I'm working on something a little similar but mines more a dev tool vs process automation but I love where yours is headed. The biggest issue I've run into is handling retries with agents. My current solution is I have them set checkpoints so they can revert easily and when they can't make an edit or they can't get a test passing, they just restart from earlier state. Problem is this uses up lots of tokens on retries  how did you handle this issue in your app?</p>
]]></description><pubDate>Thu, 26 Mar 2026 02:01:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=47525855</link><dc:creator>naultic</dc:creator><comments>https://news.ycombinator.com/item?id=47525855</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47525855</guid></item></channel></rss>