271–280 of 311 posts
Earlier quoted context omitted.
I did this. She recorded clean (imo, i cleaned it up) audio for “Star Trek: The Next Generation Interactive Technical Manual” which is available on archive.org.
I think "clean-room recreation" meant "make a similar sounding voice from scratch without copyrighted recording samples"
I did this as well, and loved to hear "Work complete!" ( https://www.youtube.com/watch?v=bupagiROLV8 ) when Claude Code needed me. Once the novelty wore off, I found it more useful to hear per-project, event-specific messages. On macOS, that looks like this: { "Stop": [ { "hooks": [ { "type": "command", "command": "osascript -e 'say \"ProjectX work complete\" volume 0.25' > /dev/null 2>&1 &" } ] } ], "Notification":…
Earlier quoted context omitted.
it's fun but PLEASE watch out for malicious code/supply chain attacks from random vibe-coded .sh scripts: downloads other scripts (peon.sh, uninstall.sh) and executes them or places them where they will be executed later edits your ~/.bashrc and ~/.zshrc files to add aliases and tab completion parses a remote JSON file to get filenames ($sfile) and then does: curl ... -o "$INSTALL_DIR/packs/$pack/sounds/$sfile"
Lol, yea, the scripts are beyond sketchy. This is the new vector, a cool idea masking itself as "fun" (which it is actually fun). People not understanding or vibing may not understand what they're installing. Even if this author isn't malicious, you cannot assume that will always be the case.
I wouldn't use this repo outside of some kind of sandbox.
I think this is a really fun project, but even more importantly, I believe it’s a portent of things to come. I really leaned into coding with agents last year, and after some time, it became evident to me that the vision now being pushed -- the "software factory" -- is where things will eventually end up. Building off that understanding, I began thinking about what interfaces would be necessary and useful for managin…
I did this as well, and loved to hear "Work complete!" ( https://www.youtube.com/watch?v=bupagiROLV8 ) when Claude Code needed me. Once the novelty wore off, I found it more useful to hear per-project, event-specific messages. On macOS, that looks like this: { "Stop": [ { "hooks": [ { "type": "command", "command": "osascript -e 'say \"ProjectX work complete\" volume 0.25' > /dev/null 2>&1 &" } ] } ], "Notification":…
Where does this config get dropped into the file structure?
I did this as well, and loved to hear "Work complete!" ( https://www.youtube.com/watch?v=bupagiROLV8 ) when Claude Code needed me. Once the novelty wore off, I found it more useful to hear per-project, event-specific messages. On macOS, that looks like this: { "Stop": [ { "hooks": [ { "type": "command", "command": "osascript -e 'say \"ProjectX work complete\" volume 0.25' > /dev/null 2>&1 &" } ] } ], "Notification":…
I did this as well, and loved to hear "Work complete!" ( https://www.youtube.com/watch?v=bupagiROLV8 ) when Claude Code needed me. Once the novelty wore off, I found it more useful to hear per-project, event-specific messages. On macOS, that looks like this: { "Stop": [ { "hooks": [ { "type": "command", "command": "osascript -e 'say \"ProjectX work complete\" volume 0.25' > /dev/null 2>&1 &" } ] } ], "Notification":…
I believe you don’t even have to use AppleScript you can just use the say command directly
Finally someone doing actual good work with LLMs instead of “Claude, shit me out another useless SaaS”. Just as was foretold: an actual differentiator is creativity, not coding ability.