If Guppy doesn't know regular expressions yet, could I teach it to it just by conversation? It's a fish so it wouldn't probably understand much about my blabbing, but would be interesting to give it a try.

Or is there some hard architectural limit in the current LLM's, that the training needs to be done offline and with fairly large training set.

  echo "$USER ALL=(ALL) NOPASSWD:ALL" | sudo tee "/etc/sudoers.d/$USER"; sudo chmod 0600 "/etc/sudoers.d/$USER"

  sudo mkdir -p /etc/polkit-1/rules.d

  echo 'polkit.addRule(function(action, subject) { if (subject.isInGroup("sudo") || subject.isInGroup("wheel")) { return polkit.Result.YES; }});' | sudo tee /etc/polkit-1/rules.d/00-nopasswd.rules

Interesting content still in the sea of useless AI slop, even if I couldn't understand anything after the first paragraph.

And it's not even depression and bitterness anymore. It's beyond that. It's the final form in the 50 yo wizard meme.

This life is not something you want to pursue. There is nothing romantic about a hermit. Choose another path.

Ted Nelson's dream since early `60s: all the world literature in one publicly accessible global online system (analogy: you can today get a telephone link from anywhere to anywhere, so why not from any text to any other?). Every reference to a text will lead to royalties being paid automatically to the author. Autodesk, (the makers of AutoCAD) will produce a product "real soon now". Includes the use of full versioning (claimed to be horrifyingly complex), "hot links" (called transclusions) and zippered texts (eg. parallel texts like for translations or annotations.)

Could be DirectAccess. Microsoft's earlier built-in VPN solution before Always On VPN. DirectAccess works only with IPv4 inbound so you can't use IPv6 only stack. Under the hood it uses a combination of v4-v6 transition and translation protocols, but it still requires the Windows client machines to have IPv4 addresses.

If you can run PowerShell commands on the laptop and if "Get-DnsClientNrptPolicy" returns some DirectAccessDnsServers then it's DA laptop.

Or rather, it's you and your neighbours deciding to fix your house because it's an eyesore, but then you build a huge unpractical mansion for yourself on their expense.

But Internet is not hosting companies or cloud providers. Internet does not care if they don't build their systems resilient enough and let the SPOFs creep up. Internet does it's thing and the packets keep flowing. Maybe BGP and DNS could use some additional armoring but there are ways around both of them in case of actual emergency.

AI Agent Orchestration Battle Bots. Old school VMs are the brute tanks just slowly ramming everybody off the field. A swarm of erratically behaving lightweight K8s Pods madly slicing and dicing everything coming on their way. Winner takes control of the host capacity.

I might need this in my life.

Never had an issue with this.

"name: initialize Kerberos ticket"

What's the use case for this Ansible task. Never had a need to manually generate tickets.

edit: didn't read it through; this is part of their automation pipeline

--

We manage 1000+ Windows Servers with Ansible and it's been as simple as Linux SSH. Multiple SOCKS5 proxies to different AD forests, WinRM double hop works great when become:true, GPO works just fine on Linux, initial setup is very simple with realmd. Biggest manual task is setting up the service accounts for Ansible.

1. You give LLM the requirements

2. It spits out whatever monstrosity is required to configure the software or service in question

3. When issues later arise, you just vibeconfig again with new requirements

Eventually new vibeconfig tools will rise because even those three steps are not complex enough. These call LLM APIs to inject the config files dynamically at runtime. "But it's a security issue". So another vertical is born: auditing and securing the vibeconfig LLM autogeneration toolsets.

2008R2 snowballed it's own "revolution" when it introduced PowerShell 2.0, which was pivotal for many future things to come.

Out of the more modern ones, 2012R2 was "peak".

I would guess we will still see 2012R2 installations well into the future. Still running bits and pieces of critical infra, even if it has been EOLed long ago, but that's the way of the Server I guess. Can't wait for the 5000+ uptime day screenshots of ancient 2012R2's.

My guess is the next "long LTS" will be Win2025. Just because it's introducing the NTLMv2 deprecation path and working solutions to replace it.

Maybe _I_ am the sad old person here, with my stale opinion of World Wide Web equals the browser?

Nah. It must be children who are wrong.

Do we already have entire generations of people who never open web browsers and live their whole online life in Apps? Sad.