> accept I am a somewhat horrible person to even be able to articulate those thoughts.

No, you’re simply thoughtful and a realist. To acknowledge something doesn’t mean you agree with or endorse it.

This is an interesting thread to me and my experience as a total hack programmer has been both awesome and pathetic with regards to AI.

Recently I tried working with both ChatGPT and Gemini (AI Studio) to take a really badly written PHP website and refactor it into MVC components. I've worked strictly through the web UI as this only involved a few files.

While both provided great guidance around how to approach disentangling this monolithic code, GPT failed miserably, generating code that was syntactically incorrect, and then doubling-down on it by insisting that it was correct and that errors were faults lying elsewhere. It literally generated code that lacked closing parenthesis and brackets.

In contrast, Gemini generated a perfectly working MVC version from the start. In both instances I did intentionally keep it on track to only separate the code into MVC and NOT to optimize anything, but it worked the first try. I've then taken it through subsequent refactorings and it's done superbly in that role.

So I can't speak to how well this works for large code bases, much less agentically. (my initial, very focused MVC refactor was about 1300 lines.) But when giving it a very specific task with strict guidance and rules, my results with Gemini were fantastic.

Well the parent did say this:

> Details are extremely thin on the site, so let me know if I'm wrong.

"I don't know any details so I'll make them up" isn't arguing in good faith.

Thanks for the link. Like you, it really helped me understand what's going on with all three of the designs shown.

I don't think source routing is a thing anymore. At least if you're talking about the ability of a source to specify a path to its destination.

The last time I heard about source routing actually being a useful feature or a vulnerability used by hackers was the 1990's.

For mini pcs, Beelink probably has the best support. I've owned a few and had one replaced under warranty.

> pop out a more specific BGP prefix from a backup path or secondary router so you can pull production away from the burning IP.

This won't help against carpet bombing.

The only workable solution for enterprises is a combination of on-prem and cloud mitigation. Cloud to get all the big swaths of mitigation and to keep your pipe flowing, and on-prem to mitigate specific attack vectors like state exhaustion.

I never claimed to be an enterprise, nor did I suggest this was the best option for them. Cheers!

> The firewall on OpenBSD is miles better to configure than iptables.

That's understating the matter by a huge amount.

pf is easier to read and understand, easier to adjust, more dynamic, and works like every other firewall in the world not based on iptables.

Seems a bit subjective. I find iptables much easier to work with.

But then again I've not run iptables for years. nftables has many benefits.

iptables is indeed horrid, but Linux has nftables nowadays, which is much nicer and easier to configure.

Thanks for the summary.

This:

> shutdown has a 50% chance of rebooting.

…gave me a good laugh.

I think most of the hate and resistance is due to the erosion of trust that comes with AI. We’re already at the point where you have to question the authenticity of A/V media you see on social media. Soon we may not be able to trust even news outlets.

Nobody* wants this to happen, yet it’s charging forward.

* yes of course there are some, but they’re already the ones with the power and money.