I don't fully get the negativity here. This seems like a middle ground between quick'n'dirty bash script and a well-crafted Ansible playbook.

Half the time if you want to do something quick'n'dirty in Ansible playbooks you need to use shell anyway..

I participated in a hackathon recently where my deployment process was just a bash script doing scp/ssh to a remote server and it feels like Scotty would fit well to that kind of use-case.

Looks similar to sem/weave

https://github.com/ataraxy-labs/sem

https://github.com/ataraxy-labs/weave

Though, despite the claims, I am not sure if these are ready for prime-time yet. I have noticed some rather concerning merge "resolutions".

> yt-dlp is running the entire YouTube JS+DOM environment

IIRC they maintain a minimal execution environment that is able to run just the JS needed to pass a few checks but this breaks too often enough that they're planning to make Node.js or another JS interpreter a hard requirement (possibly already happened).

Pretty much - yt-dlp currently requires Deno to "solve" youtube challenges.

* https://deno.com/

* there may well be other JS interpreters that are accepted, can be used - but solving JS challenges is required for much, if not all, YT content.

PMs can now also ship their half-baked requirements documents even faster thanks to the help of AI.

I noted something similar a few weeks ago. Companies are finally putting APIs in front of things that should have had APIs for years!

Pretty sure I saw this one a couple of weeks back, or something very similar to it..

https://github.com/philschmid/mcp-cli

Edit: Turns out was https://github.com/steipete/mcporter noted elsewhere in the thread, but mcp-cli looks like a very similar thing.

I believe you're thinking of JScript, they're not quite the same thing.

FWIW I think most users here would prefer you reply to their hand-written comments using your own words, even if you had to use a translator.

Thank you for your message. English is not my native language, so I sometimes use translation tools. I will try my best to reply to you in more direct and understandable language. Thank you for your patience.

> An AI agent was used to gain super-user access

No telling if this "hack" wasn't really just prompt engineering followed by hallucinations, particularly if the "hacker" was attempting to exfil data via the agent.

That line also sounds exactly like the pseudo tech BS somebody will come up with to try to make something sound legitimate

I wonder how the AI agent managed to bypass the HTML5 mainframe firewall

It was a secret agent.

> "The key insight is..."

This was either written by Claude or someone who uses Claude too much.

I wish they could be upfront about it.

It's interesting... Different LLM models seem to have a few sentence structures that they seem to vastly overprefer. GPT seems to love "It's not just X, it's Y", Claude loves "The key insight is..." and Gemini, for me, in every second response, uses the phrase "X is the smoking gun". I hear the smoking gun phrase around 5 times a day at this point.