<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: mnahkies</title><link>https://news.ycombinator.com/user?id=mnahkies</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 19 Nov 2026 05:29:06 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=mnahkies" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by mnahkies in "Devvm.dev: One VM for every project"]]></title><description><![CDATA[
<p>I'm pretty sure you don't need to give it full access to accomplish that. It's possible to create scoped PAT etc. alternatively use a separate account. Ultimately your risk tolerance to decide</p>
]]></description><pubDate>Fri, 06 Nov 2026 22:19:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=50399263</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=50399263</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50399263</guid></item><item><title><![CDATA[New comment by mnahkies in "Devvm.dev: One VM for every project"]]></title><description><![CDATA[
<p>On the git access part, I don't let my agent VMs have write access to GitHub currently. I do give them dedicated users on a self hosted gitea instance, and basically manage the blast radius through branch protection etc.<p>I think at a high level I'm trying to treat them as junior/intern employees where I give them enough permission to do their role, but not enough rope to hang themselves.</p>
]]></description><pubDate>Fri, 06 Nov 2026 21:04:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=50398518</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=50398518</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50398518</guid></item><item><title><![CDATA[New comment by mnahkies in "We know 15k websites are infected. how do we tell them?"]]></title><description><![CDATA[
<p>Worst one I had was about 12 years ago when I got a phone call from the local golf club I'd set-up a site/CMS for, not kept patched as well as I should've, and a club member reported they were served porn ads instead of the Saturday draw... That was a lesson learnt</p>
]]></description><pubDate>Fri, 06 Nov 2026 20:46:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=50398277</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=50398277</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50398277</guid></item><item><title><![CDATA[New comment by mnahkies in "Devvm.dev: One VM for every project"]]></title><description><![CDATA[
<p>One thing I'm struggling with at the moment which I may as well ask here.<p>Many of my projects use pnpm, which ideally uses hard links from a shared store of dependencies.<p>One of my goals is to reduce the disk overhead of VM based isolation, so I'd like a shared pnpm store across projects (and the same for maven, etc as well)<p>With <a href="https://virtio-fs.gitlab.io/" rel="nofollow">https://virtio-fs.gitlab.io/</a> mounts, each mount inside the VM is a separate FS, and I can't hard link across them. I've tried playing around with ideas like bind mounting the directory structure from the host in a folder to have a single virtio-fs mount inside the VM - but the bind mounts still can't be hard linked across it seems.<p>I'm basically wondering if I'm missing something or just trying to do something that isn't possible.<p>All the host folders are on the same FS - but I don't want to organise the host system around the VM mounting needs, and I also don't want to mount extraneous directories into the VM (eg: simple solution could be just mount ~/projects but kinda self defeating)<p>(Fedora workstation host)</p>
]]></description><pubDate>Fri, 06 Nov 2026 20:26:47 +0000</pubDate><link>https://news.ycombinator.com/item?id=50397983</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=50397983</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50397983</guid></item><item><title><![CDATA[New comment by mnahkies in "Devvm.dev: One VM for every project"]]></title><description><![CDATA[
<p>Heh, yeah also very similar. I don't strip devices like you are - I actually want the memory balloon functionality for example.<p>My working threat model for my projects is less about "malicious agent trys to escape VM" and more "well meaning agent got confused and screwed up" - the added protection of a VM is desirable, and it's useful for stuff like nested virtualization (agent working on improving the VM orchestration), makes containers inside the sandbox straightforward<p>I hadn't seen the stuff about filtering spoofed packets so I'll probably add that.</p>
]]></description><pubDate>Fri, 06 Nov 2026 20:16:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=50397825</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=50397825</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50397825</guid></item><item><title><![CDATA[New comment by mnahkies in "Devvm.dev: One VM for every project"]]></title><description><![CDATA[
<p>I missed the one directory part, I'd definitely recommend making that more flexible. With my equivalent of this I often mount multiple repositories into a single VM, two examples:<p>- a bunch of gitops repos: terraform mono repo, argocd-esk conf repo, grafana provisioning repo, etc.<p>- frontend + backend repo (tbh may merge these to a mono-repo, but here we are)<p>I think the auto detection is interesting, but tbh with my solution I've been happy with just install all the tools regardless of what a specific project needs - with a COW base layer this is cheap.</p>
]]></description><pubDate>Fri, 06 Nov 2026 19:35:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=50397257</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=50397257</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50397257</guid></item><item><title><![CDATA[New comment by mnahkies in "Devvm.dev: One VM for every project"]]></title><description><![CDATA[
<p>Damn, I've been building something very similar the past few weeks - haven't quite gotten to a public release yet.<p>Mines based on libvirt and uses cloud-init for creating the images, with shared golden images across projects.<p>Skimming your docs it wasn't totally clear to me if your images are built per project, or COW from shared toolchains.<p>Looks like you have a few features in there that I might take some inspiration from though, eg the proxying stuff.<p>Funny how many of us are trying to solve the same problem at the moment.</p>
]]></description><pubDate>Fri, 06 Nov 2026 19:28:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=50397143</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=50397143</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50397143</guid></item><item><title><![CDATA[New comment by mnahkies in "Ask HN: What's your current AI agentic setup?"]]></title><description><![CDATA[
<p>I'm using a cli I wrote to orchestrate per-project VMs for sandboxing using libvirt with COW shared golden images to minimise the disk overhead. The VMs get "rebased" periodically onto new golden images for the rootfs, but keep a persistent home FS for longer. I'm going to clean-up the documentation and open source it at some point soon.<p>I was using oh-my-pi, but currently playing around with Hermes as an alternative.<p>Exclusively using open router at the moment, mostly on principle around ZDR, and freedom to experiment with harnesses - but financially I'll probably have to compromise on this soon. GLM, Kimi and DeepSeek are the main models I'm using, with some OpenAI usage.<p>Tmux for remote access and session durability. I'd prefer to find a setup where I could access the same session through a web interface and seamlessly switch back to TUI, ideally spawning sessions through a web hook or similar. I'm going to take a look at Hedr to see if this can improve this.<p>Probably the two major things I'm planning to do next are looking at adding a bifrost VM that will hold all API keys, and centralise management of MCP configuration, potentially use it's skill repo stuff as well.<p>I also want to start controlling egress more - probably iron proxy, though tbh I'd like a solution that was relatively liberal whilst still mitigating exfiltration and prompt injection risks. Maybe I can find a curated allow list to use as a base.<p>Finally, I make a lot of use of open-webui, but it's disjoint from the agentic setup currently - it'd be nice to find a better way to share information/research from it into the agentic sessions.</p>
]]></description><pubDate>Thu, 05 Nov 2026 07:51:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=50376357</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=50376357</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50376357</guid></item><item><title><![CDATA[New comment by mnahkies in "GitHub Incident with Actions, Pages, and Webhooks"]]></title><description><![CDATA[
<p>I've started hosting most of my private projects on a self hosted gitea, but one roadblock I've found is oidc auth - from GitHub actions I can publish to the Google play store, or npm, without needing to manage any static credentials. I know I'll need to manage some kind of secrets/identity when self hosting, though I'm still looking for nicer solutions than a bunch of static secrets for individual services.</p>
]]></description><pubDate>Fri, 30 Oct 2026 22:36:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=50311021</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=50311021</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50311021</guid></item><item><title><![CDATA[New comment by mnahkies in "DeepSeek banned from U.S. federal civilian agencies under new DHS order"]]></title><description><![CDATA[
<p>I've seen an agent autonomously upload a jar to a random file host, in an attempt to be helpful as ssh between my host and it's VM wasn't working (which was trivially fixed, but I guess it was in a hurry)<p>It was a build of an open source editor plugin I was extending so not a big deal. However it's made realise I need to add an egress proxy filtering internet access (although none that I've looked at yet work exactly the way I'd like)</p>
]]></description><pubDate>Tue, 20 Oct 2026 07:58:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=50162720</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=50162720</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50162720</guid></item><item><title><![CDATA[New comment by mnahkies in "Bitwarden Dual License Model"]]></title><description><![CDATA[
<p>Bitwarden is one of the few subscriptions I have in a patron sense - eg: I've never actually needed any of the premium feature's, but I chose to pay anyway as I felt that was a way to contribute to the long term viability of the project.<p>I'm not immediately upset about the licensing change - I get the need to protect from low effort/value add reselling and things like that. I do still worry if this is a canary for future changes that run counter to the reasons I migrated to bitwarden in the first place (open, robust, trustworthy).<p>Counter to many other commenters I personally prefer bitwarden over 1password, and certainly over lastpass and roboform, etc.<p>My only gripe is having to unlock the desktop app separately from the browser extension, which after adopting the ssh agent functionality became kinda annoying.</p>
]]></description><pubDate>Sat, 10 Oct 2026 17:20:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=50035035</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=50035035</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50035035</guid></item><item><title><![CDATA[New comment by mnahkies in "EventMaxxer – Automatically apply to events to get you in the right room"]]></title><description><![CDATA[
<p>I missed out on an event recently because it was full. I got a notification that a spot had become available shortly before it started, but I had an hour travel to get there so wasn't viable.<p>I think tools to enable better discovery are a good thing, but I'm not sure that I like the idea of splatting RSVPs just in case.</p>
]]></description><pubDate>Sat, 03 Oct 2026 17:34:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=49946141</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=49946141</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49946141</guid></item><item><title><![CDATA[New comment by mnahkies in "Making Tailscale Faster"]]></title><description><![CDATA[
<p>I started with plain wireguard then migrated to tailscale, for my use case:<p>- I was able to get my partner onto the tailnet by telling her to install an app and login. She doesn't know or care what wireguard is, but she can now access some of my self hosted services on her phone.<p>- I'm able to easily dynamically register machines to the tailnet, such as CI jobs<p>- I'm able to self host a DNS resolver and have it just work for devices connected to the tailnet<p>I'm sure I could achieve these goals with plain wireguard, but I feel like I was able to outsource significant complexity to tailscale instead.</p>
]]></description><pubDate>Thu, 24 Sep 2026 06:42:11 +0000</pubDate><link>https://news.ycombinator.com/item?id=49827050</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=49827050</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49827050</guid></item><item><title><![CDATA[New comment by mnahkies in "I changed my license"]]></title><description><![CDATA[
<p>What are people's thoughts/experiences about dual licencing?<p>Eg: is there a clean way to dual license such that hobbyist, and exploratory work (eg: a proof of concept done in a commercial setting) are allowed, but using it in production requires a fee?<p>If you've done this, has it been successful? Obviously there's been many projects relicense over recent years (terraform, redis, etc) - but it's less clear to me if this is a viable path for new projects starting out, or if it just kills adoption from the beginning.</p>
]]></description><pubDate>Sun, 06 Sep 2026 11:08:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=49585334</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=49585334</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49585334</guid></item><item><title><![CDATA[New comment by mnahkies in "I Cut 80%+ of Context Overhead in My Coding Agent"]]></title><description><![CDATA[
<p>Does anyone know what the impact on prompt caching is?<p>I like the idea of dynamic tool/skill sets, but wonder if it needs to be part of the new session workflow where you would choose a group to activate rather than this dynamic.</p>
]]></description><pubDate>Fri, 28 Aug 2026 11:26:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=49477059</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=49477059</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49477059</guid></item><item><title><![CDATA[New comment by mnahkies in "RustDesk now supports true unattended remote access on Wayland"]]></title><description><![CDATA[
<p>It's funny you say that, as one of my weekend projects today is setting up <a href="https://www.authelia.com/" rel="nofollow">https://www.authelia.com/</a> to achieve the same.<p>I probably won't allow everything through it (eg: postgres, clickhouse etc can stay on tailscale), but I've been stumbling into use cases where I want to share things with friends or colleagues, and I don't want to put them on my tailnet.</p>
]]></description><pubDate>Sat, 15 Aug 2026 14:28:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=49310875</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=49310875</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49310875</guid></item><item><title><![CDATA[New comment by mnahkies in "RustDesk now supports true unattended remote access on Wayland"]]></title><description><![CDATA[
<p>One of my primary use cases for tailscale/VPN is that I can happily run stuff (grafana, gitea, etc) and not have to be panicked about monitoring for CVEs - I serve it all over HTTPS but I don't want to put it on the public internet if I don't need to.</p>
]]></description><pubDate>Fri, 14 Aug 2026 22:09:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=49305191</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=49305191</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49305191</guid></item><item><title><![CDATA[New comment by mnahkies in "Maximizing the value of your Claude Code sessions"]]></title><description><![CDATA[
<p>Through my weekend experiments, I've found I can get way better outcomes, and an order of magnitude less cost with my slapped together sandboxed omp setup plus ZDR openrouter models (DeepSeek, Kimi, etc) than I've ever seen from Claude Code at work.<p>Everything is version pinned and a deliberate choice to change, and a git revert away from changing back.<p>TBF the models may change underneath me to some extent still, but the cost benefit of running them myself doesn't pan out yet (for agentic coding at least, don't have enough local vram to get a usable context window and generation speed, self hosting on runpod or similar isn't economically sensible for my current consumption though I have tinkered with it)</p>
]]></description><pubDate>Fri, 14 Aug 2026 18:56:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=49303108</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=49303108</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49303108</guid></item><item><title><![CDATA[New comment by mnahkies in "OpenAI’s head of ethics leaves less than a year after joining"]]></title><description><![CDATA[
<p>I think the key part is about aligning incentives and outcomes - if your security and compliance departments are only judged on "were we breached, did we pass our audits" then there's a risk they won't weigh the tradeoffs associated with the decisions around controls implemented to achieve those outcomes.<p>To use a ridiculous extreme you can't breach a web app that isn't exposed to the internet, but the users can't access it either.<p>If you can connect/balance those goals to other metrics around cost and productivity, usability, and a realistic threat model, as guardrails then you incentatize cross-team collaboration to achieve the shared org outcomes.</p>
]]></description><pubDate>Wed, 12 Aug 2026 07:27:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=49268939</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=49268939</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49268939</guid></item><item><title><![CDATA[New comment by mnahkies in "Uber SubmitQueue: a high-performance speculative merge queue"]]></title><description><![CDATA[
<p>I'm going to play devil's advocate here.<p>As a developer, I quite like monorepos to a certain size (eg: until they get big enough that the tooling we typically use outside of big tech starts to fall down).<p>As an AI, I'm not sure that I care? I'd guess that context management can actually be easier if each microservice has a well documented API (openapi/graphql/grpc/asyncapi/whatever) and you provide the agent harness the ability to drop into each polyrepo as required (and give it the ability to access said documentation).<p>The tedium of making branches / commits / pull requests across 6 repos to land a feature is less problematic to an agent.<p>Admittedly the way I'm using agents at the moment is more repo orientated where it's sandboxed to a single repo, but conceptually I think polyrepo microservices could end up being a sweet spot.</p>
]]></description><pubDate>Sun, 09 Aug 2026 15:32:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=49232375</link><dc:creator>mnahkies</dc:creator><comments>https://news.ycombinator.com/item?id=49232375</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49232375</guid></item></channel></rss>