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.
> 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).
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.
I can't help but feel there is a funny pattern going on.
A lot of companies want to embrace AI, agents, etc. so they make their platforms easier to use by AI, implementing whatever the latest craze is.
I imagine we're going to see a lot more APIs open up (agentic finances?), a lot of granular access controls, etc.
Where was all of this when regular users had been asking for it for _years_?
Empowering users in general is a good thing, so, in a way, it's a good thing that OpenClaw and things of this nature are exposing all the issues with access controls and API interactions that many of our services have.
Now we just need a reason for AI agents to need "dark mode" on websites...
TIL there's a batch API.. This seems like something a lot of AFK coders should be using.
The pattern for those users is typically they would set some kind of token budget, but their agent would still try to burn through those tokens as quickly as possible, rather than a more sensible "do this at your own leisure over the next ~8 hours".
Looking forward to further commodification of LLM usage in the future to make it more affordable. Batch APIs and more freedom over scheduling/priorities/deadlines seems like the more sustainable approach to driving costs down.
I tried teams, good way to burn all your tokens in a matter of minutes.
It seems that the Claude Code team has not properly taught Claude how to use teams effectively.
One of the biggest problems I saw with it is that Claude assumes team members are like a real worker, where once they finish a task they should immediately be given the next task. What should really happen is once they finish a task they should be terminated and a new agent should be spawned for the next task.
> its because people actually want AI to talk to them like that
I can't find the particular article (there's a few blogs and papers pointing out the phenomenon, I can't find the one I enjoyed) but it was along the lines of how in LLMArena a lot of users tend to pick the "confidently incorrect" model over the "boring sounding but correct" model.
The average user probably prefers the sycophantic echo chamber of confirmation bias offered by a lot of large language models.
I can't help but draw parallels to the "You are not immune to propaganda" memes. Turns out most of us are not immune to confirmation bias, either.
Carmack's comments and the comments in the thread entirely surprise me.
256kbit/s was pretty much the standard ADSL speed 20 years ago. I remember thinking it was lucky some of my friends had 512kbit/s and 1500kbit/s was considered extremely fortunate.
Even still calls over Skype worked fine, you could run IRC or MSN Messenger while loading flash games or downloading MP3s. You could definitely play games like Starcraft, Age of Empires, Quake, UT2004, etc. on a 256k ADSL line. Those plans were also about 8x the price of this plan, not even adjusting for inflation.
Not only that, those lines were typically only 64k upload speed. The usefulness of a 500kbit/s up/down line is incredibly high. I think the only reason it might seem less useful now is that web services are not typically optimised to be usable on dial-up speeds like they were 20 years ago.
With the right setup and having feeds/content download asynchronously rather than "on-demand", 500kbit/s is still plenty of internet by today's standards.