<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: mrmattyboy</title><link>https://news.ycombinator.com/user?id=mrmattyboy</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 18 Apr 2026 05:14:35 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=mrmattyboy" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[System Engineering an agent thanks to Golang]]></title><description><![CDATA[
<p>Article URL: <a href="https://blog.mattsbit.co.uk/2026/04/06/systems-engineering-an-agent-thanks-to-the-world-of-golang/">https://blog.mattsbit.co.uk/2026/04/06/systems-engineering-an-agent-thanks-to-the-world-of-golang/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47661632">https://news.ycombinator.com/item?id=47661632</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Mon, 06 Apr 2026 14:46:44 +0000</pubDate><link>https://blog.mattsbit.co.uk/2026/04/06/systems-engineering-an-agent-thanks-to-the-world-of-golang/</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=47661632</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47661632</guid></item><item><title><![CDATA[New comment by mrmattyboy in "Show HN: Artifact Keeper – Open-Source Artifactory/Nexus Alternative in Rust"]]></title><description><![CDATA[
<p>Honestly, this is just awesome.<p>I've spent quite a long time looking at artifact storage, both for work and for personal use and this project literally scratches that itch.
So featureful (assuming they're not placeholders ;) ) and yes, Claude Code, but still - the proof will be in whether it works (and how clean the codebase feels - you're making it sound promising :D ).<p>Very excited to try this - well done :)</p>
]]></description><pubDate>Fri, 06 Feb 2026 14:47:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=46913461</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=46913461</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46913461</guid></item><item><title><![CDATA[New comment by mrmattyboy in "What came first: the CNAME or the A record?"]]></title><description><![CDATA[
<p>I agree this doens't seem too ambiguous - it's "you may do this.." and they said "or we may do the reverse". If I say you're could prefix something.. the alternative isn't that you can suffix it.<p>But also.. the programmers working on the software running one of the most important (end-user) DNS servers in the world:<p>1. Changes logic in how CNAME responses are formed<p>2. I assume some tests at least broke that meant they needed to be "fixed up" (y'know - "when a CNAME is queried, I expect this response")<p>3. No one saw these changes in test behavoir and thought "I wonder if this order is important". Or "We should research more into this", Or "Are other DNS servers changing order", Or "This should be flagged for a very gradual release".<p>4. Ends up in test environment for, what, a month.. nothing using getaddrinfo from glibc is being used to test this environment or anyone noticed that it was broken<p>Cloudflare seem to be getting into thr swing of breaking things and then being transparent. But this really reads as a fun "did you know", not a "we broke things again - please still use us".<p>There's no real RCA except to blame an RFC - but honestly, for a large-scale operation like there's this seems very big to slip through the cracks.<p>I would make a joke about South Park's oil "I'm sorry".. but they don't even seem to be</p>
]]></description><pubDate>Mon, 19 Jan 2026 20:15:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=46683916</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=46683916</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46683916</guid></item><item><title><![CDATA[Profiling Golang Terraform Provider]]></title><description><![CDATA[
<p>Article URL: <a href="https://blog.mattsbit.co.uk/2025/10/04/profiling-golang/">https://blog.mattsbit.co.uk/2025/10/04/profiling-golang/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=45488577">https://news.ycombinator.com/item?id=45488577</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Mon, 06 Oct 2025 07:27:54 +0000</pubDate><link>https://blog.mattsbit.co.uk/2025/10/04/profiling-golang/</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=45488577</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45488577</guid></item><item><title><![CDATA[New comment by mrmattyboy in "Git for Music – Using Version Control for Music Production (2023)"]]></title><description><![CDATA[
<p>It's interesting seeing parts of life overlap.<p>I did music production at the same time as heavily using SVN and starting to use Git - I didn't cross this over at the time. All (in my case) Cubebase files were just -1, -2 suffixes and it worked. I had continuous backups, sure and it just kinda worked at the time.<p>Given I now use Git heavily in my work/hobby life, when doing other projects (3D models for printing (questionable at best) and artwork (very very very questionable at best)) I definitely wanted to use some sort of SCM.
I opted for these for Perforce - mostly to experiment, but also the idea of having binaries in a distributed SCM. Yes, I know Git-LFS _exists_, but also, to me it breaks the idea of what Git is.. relying on a server for binaries in a situations where everything should be distributed.<p>If I now went back to audio-production, I would probably consider either Perforce or SVN. Perforce only if it were for a single user (because of licensing). The ability to clone/checkout a single directory of a repo at a given point in time natively and make modifications and push them back is almost quite necessary when dealing with very large files.<p>And I still use SVN for _some_ situations - particularly those where Perforce is overkill and all I want to _always_ HEAD and the rest is history (for manual preservation history) and no such need for merging and branching (thinking Wiki and other plain-text tooling).<p>In the case of any sort of any binary-merging - I _heavily_ assume this isn't expected in the poster's situation!</p>
]]></description><pubDate>Mon, 01 Sep 2025 17:11:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=45094557</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=45094557</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45094557</guid></item><item><title><![CDATA[New comment by mrmattyboy in "Farewell to my Dad"]]></title><description><![CDATA[
<p>I originally wrote the speach in my blog repo, just for writing purposes.<p>My dad's funeral was yesterday and wondered, maybe, someone might appreciate it - either because they've lost their dad or it makes them appreciate their dad a little more.</p>
]]></description><pubDate>Sat, 26 Jul 2025 18:13:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=44695950</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=44695950</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44695950</guid></item><item><title><![CDATA[Farewell to my Dad]]></title><description><![CDATA[
<p>Article URL: <a href="https://blog.mattsbit.co.uk/2025/07/23/dad/">https://blog.mattsbit.co.uk/2025/07/23/dad/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44695940">https://news.ycombinator.com/item?id=44695940</a></p>
<p>Points: 6</p>
<p># Comments: 2</p>
]]></description><pubDate>Sat, 26 Jul 2025 18:11:39 +0000</pubDate><link>https://blog.mattsbit.co.uk/2025/07/23/dad/</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=44695940</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44695940</guid></item><item><title><![CDATA[Proxying with HashiCorp Boundary]]></title><description><![CDATA[
<p>Article URL: <a href="https://blog.mattsbit.co.uk/2025/06/11/proxying-with-hashicorp-boundary/">https://blog.mattsbit.co.uk/2025/06/11/proxying-with-hashicorp-boundary/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44303315">https://news.ycombinator.com/item?id=44303315</a></p>
<p>Points: 4</p>
<p># Comments: 0</p>
]]></description><pubDate>Tue, 17 Jun 2025 20:02:16 +0000</pubDate><link>https://blog.mattsbit.co.uk/2025/06/11/proxying-with-hashicorp-boundary/</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=44303315</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44303315</guid></item><item><title><![CDATA[New comment by mrmattyboy in "How a 20 year old bug in GTA San Andreas surfaced in Windows 11 24H2"]]></title><description><![CDATA[
<p>I remember reading this and having a mini-midlife-crisis after every read<p>I documented it this time :sigh: <a href="https://github.com/MatthewJohn/terrareg/commit/2231ba733a7f593e263a9006c6ea2796a8059c47">https://github.com/MatthewJohn/terrareg/commit/2231ba733a7f5...</a></p>
]]></description><pubDate>Thu, 24 Apr 2025 08:11:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=43780329</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=43780329</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43780329</guid></item><item><title><![CDATA[New comment by mrmattyboy in "New Vulnerability in GitHub Copilot, Cursor: Hackers Can Weaponize Code Agents"]]></title><description><![CDATA[
<p>Are you talking about my comment or the article? :eyes:</p>
]]></description><pubDate>Mon, 14 Apr 2025 14:05:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=43681441</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=43681441</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43681441</guid></item><item><title><![CDATA[New comment by mrmattyboy in "New Vulnerability in GitHub Copilot, Cursor: Hackers Can Weaponize Code Agents"]]></title><description><![CDATA[
<p>> effectively turning the developer's most trusted assistant into an unwitting accomplice<p>"Most trusted assistant" - that made me chuckle. The assistant that hallucinates packages, avoides null-pointer checks and forgets details that I've asked it.. yes, my most trusted assistant :D :D</p>
]]></description><pubDate>Mon, 14 Apr 2025 06:09:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=43678514</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=43678514</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43678514</guid></item><item><title><![CDATA[New comment by mrmattyboy in "Ignoring unwanted Terraform attribute changes"]]></title><description><![CDATA[
<p>Sure, you're right in most cases. In the use-case I had, it's a private registry with "immutable" tags (at least enough to stop accidental overwrites - and it is a homelab, so if someone else did it, I'd have worse problems ;))<p>The point was more about using null_triggers (or `terraform_data` I see) and using the trigger replacement, with the docker resources as purely an illustration.</p>
]]></description><pubDate>Thu, 27 Mar 2025 20:11:06 +0000</pubDate><link>https://news.ycombinator.com/item?id=43497625</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=43497625</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43497625</guid></item><item><title><![CDATA[New comment by mrmattyboy in "Ignoring unwanted Terraform attribute changes"]]></title><description><![CDATA[
<p>Absolutely, needs-and-musts, it's certainly not a nice thing..  but again, Terraform isn't a scripting language, so sometimes bits of hack are needed!</p>
]]></description><pubDate>Thu, 27 Mar 2025 20:06:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=43497594</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=43497594</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43497594</guid></item><item><title><![CDATA[New comment by mrmattyboy in "Ignoring unwanted Terraform attribute changes"]]></title><description><![CDATA[
<p>Good point - I hadn't actually looked massively hard into solving it with this provider - I had to do it again for another use-case recently and decided to blog about it (and also try my hand at a short post).. but used this example from a while ago because it seemed much more relatable than the latest encounter :D<p>I guess, assuming you're not building the image, whether you use the data source of image probably isn't too important (assuming the data source is able to lookup images that aren't present on the local machine :thinking:).<p>Edit: and now I've seen that in the docker image resource, they reference using the data source to be able to track remote image SHA changes, in order to trigger an image re-pull :doh:<p>Feels like we've gone full-circle with this :D</p>
]]></description><pubDate>Thu, 27 Mar 2025 19:43:39 +0000</pubDate><link>https://news.ycombinator.com/item?id=43497326</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=43497326</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43497326</guid></item><item><title><![CDATA[Ignoring unwanted Terraform attribute changes]]></title><description><![CDATA[
<p>Article URL: <a href="https://blog.mattsbit.co.uk/2025/03/23/ignoring-unwanted-terraform-provider-attribute-changes/">https://blog.mattsbit.co.uk/2025/03/23/ignoring-unwanted-terraform-provider-attribute-changes/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=43454642">https://news.ycombinator.com/item?id=43454642</a></p>
<p>Points: 36</p>
<p># Comments: 11</p>
]]></description><pubDate>Sun, 23 Mar 2025 18:09:46 +0000</pubDate><link>https://blog.mattsbit.co.uk/2025/03/23/ignoring-unwanted-terraform-provider-attribute-changes/</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=43454642</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43454642</guid></item><item><title><![CDATA[New comment by mrmattyboy in "Show HN: A personal YouTube frontend based on yt-dlp"]]></title><description><![CDATA[
<p>I would say yes and no (leaning on the no)...<p>I think saying you don't have a right is fine... they are providing a service and dictating it's usage and you are using it.<p>So on the "closing your eyes". On one side, yes, allowing your browser to play the video and YT then being able to treat as a advert view means that youtube gets paid and the creator gets paid.<p>However... I would personally view this as can a person do this and how it works  as a generalisation and I would say "no", because if everyone did this (why does just one person have the right to close their eyes), then (at least I'd imagine) the companies paying for advertising would see a drop in click-throughs and (I don't know what you call it.. but let's just say) more money. They'd then stop paying for adverts. Then no companies would want to pay for adverts and YT is no longer profitable (to YT or the creators).</p>
]]></description><pubDate>Sun, 16 Mar 2025 08:22:28 +0000</pubDate><link>https://news.ycombinator.com/item?id=43377588</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=43377588</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43377588</guid></item><item><title><![CDATA[New comment by mrmattyboy in "Windows 11 Insider Preview Build"]]></title><description><![CDATA[
<p>I see what you mean..  but if you take a look at vista vs 7..<p>Microsoft shoved glass panels, widgets and such down the user's throat in Vista. It was a new look and they wanted to make you realise it.
Without spinning a fresh 7 machine now, I'm certain it was very toned down.<p>But, I could be very wrong about this :D Last time I used Windows was XP (I mean, granted last week) because nostalgia is a real thing :D<p>Edit: I can't reply (not sure why, thread too deep?) but @cogman10, you're right! My memory is bad :(</p>
]]></description><pubDate>Fri, 07 Mar 2025 16:50:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=43291732</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=43291732</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43291732</guid></item><item><title><![CDATA[Thesun.co.uk: "Pay to reject personalised ads cookies"]]></title><description><![CDATA[
<p>Article URL: <a href="https://www.thesun.co.uk/news/">https://www.thesun.co.uk/news/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=41130666">https://news.ycombinator.com/item?id=41130666</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Thu, 01 Aug 2024 16:07:59 +0000</pubDate><link>https://www.thesun.co.uk/news/</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=41130666</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41130666</guid></item><item><title><![CDATA[Automating SSL CA/Certificate in CI/CD using EasyRSA]]></title><description><![CDATA[
<p>Article URL: <a href="https://blog.mattsbit.co.uk/2024/07/26/automating-ssl-ca-and-certificates-for-ci/cd-using-easyrsa/">https://blog.mattsbit.co.uk/2024/07/26/automating-ssl-ca-and-certificates-for-ci/cd-using-easyrsa/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=41076417">https://news.ycombinator.com/item?id=41076417</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Fri, 26 Jul 2024 07:01:56 +0000</pubDate><link>https://blog.mattsbit.co.uk/2024/07/26/automating-ssl-ca-and-certificates-for-ci/cd-using-easyrsa/</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=41076417</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41076417</guid></item><item><title><![CDATA[New comment by mrmattyboy in "Ask HN: How do you handle LICENSE notices in published Docker images?"]]></title><description><![CDATA[
<p>I can see that they're adding their own license, which contains their license for the code within the repo. But nothing around licenses for packages that they're installing within the Docker images (unless I'm missing something?)</p>
]]></description><pubDate>Sat, 25 May 2024 09:45:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=40473896</link><dc:creator>mrmattyboy</dc:creator><comments>https://news.ycombinator.com/item?id=40473896</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40473896</guid></item></channel></rss>