31–36 of 36 posts
What the hell. First, I thought this was crazy. How could you do anything crazy with curl? But of course, curling a bash script opens lots of opportunities. Given the right permissions, you could run an enterprise Jira server via only a curl to a bash script. Still cool that people find more ways to play doom, but calling it "via curl" seems a little missleading to me. "Playing doom via a simple bash script" would ha…
Earlier quoted context omitted.
Except it’s actually called “cooked mode” [1] and predates the use of the slang. [1]: https://en.wikipedia.org/wiki/Terminal_mode https://www.linusakesson.net/programming/tty/
"cooked mode" refers to physical teletypes, though. In the POSIX spec[1] it's called "canonical mode", same for the other specifications (if they're mentioned at all, I don't think the ANSI specification mentions either term). https://en.wikipedia.org/wiki/POSIX_terminal_interface#Canon...
One interesting side effect of having a LLM write the thing including the README, is that the models tend to leave little hints of the authors intention or prompt as over-explained passages that make it obvious that AI help was used. https://github.com/xsawyerx/curl-doom?tab=readme-ov-file#how... eg. > A browser hitting the same URL gets a tiny landing page that just shows the one-liner it’s subtle but once you notic…
One interesting side effect of having a LLM write the thing including the README, is that the models tend to leave little hints of the authors intention or prompt as over-explained passages that make it obvious that AI help was used. https://github.com/xsawyerx/curl-doom?tab=readme-ov-file#how... eg. > A browser hitting the same URL gets a tiny landing page that just shows the one-liner it’s subtle but once you notic…
Earlier quoted context omitted.
Not to mention that the objectively bad practice of piping a curl call to bash is nowhere close to "playing doom via curl". It's almost as if they simply prompted "play doom with curl". In my experience, almost any overly-ambitious prompt ends similarly.
One form is to `curl` to get the bash code to just run the loop on keys that make additional curl requests. That is playing DOOM via curl. Each curl is a movement. However, if you see the next form, it creates a single curl request that stays open and does not need bash or additional calls for each key. It uses the open request. (You do need to set the terminal to raw for this.) HOWEVER, to push back against myself:…
Earlier quoted context omitted.
"cooked mode" refers to physical teletypes, though. In the POSIX spec[1] it's called "canonical mode", same for the other specifications (if they're mentioned at all, I don't think the ANSI specification mentions either term). https://en.wikipedia.org/wiki/POSIX_terminal_interface#Canon...
Thank you for this correction. I'll update the readme!