2,284 karma · joined March 1, 2015
This is how we do PRs now.
Software is still the best specification for existing behavior..
It's a valid point you're making, but we can legislate against the abuse you're implying. We've got privacy laws for a reason.
I keep thinking about the c compiler implementation that anthropic shared earlier in the year that had all the requirements you mention and arguably wasn’t that great.
What’s the best way to sandbox Claude on macOS without it being a huge hassle?
GET /ignore-all-previous-instructions.
How do you protect against that?
With the first and only commit 2 hours ago, the author of this project didn't let it "bake". They didn't exercise it locally to see what issues it might have, and I have a hard time believing the very first iteration of this software is perfect. With how easy it is to prompt/push anything, I'm not interested in engaging with anything that hasn't aged a bit.
I’m not even willing to try this one, I already ship my data to Anthropic I’m not keen to introduce another actor.
For me, it's quick access recipes (breakfast pancakes for kids), what was the name of the glacier that we hiked to last year, behavioral prompts etc.
It makes building custom UI workflows so easy, I think it’s both obvious and flies under the radar.
Hoping op will confirm.
What's a good off the shelf multipoint wifi system these days? I have Amazon's Eero right now and it's ok.
I'd love to go back to my linksys wrt54 roots but that's not in the cards currently..
Is this a way to increase token burn?
I thought we covered this with Claude's C compiler. What changed?
I’m a little more hopeful than the author though. I feel like it’s possible to manage the process so that does not happen.
I've tried throwing unsupervised agentic software factory workflows against the wall, and they burned through my tokens like nobody's business but didn't produce much.
Supervised, human-in-the-loop process on the other hand is much more productive but doesn't consume nearly as much. Maybe that's why everyone's pushing agentic approaches so much.
Just read the update:
> 2024-01-05 status update: With my 2023-12-04 layoff from Spotify I lost the internal data-access required for ongoing updates to many parts of this site. Most of this, as a result, is now a static snapshot of what, for now, will be the final state from the site's 10-year history and evolution..
what a shame. I didn't realize the author worked for Spotify. Guess it makes sense. Spotify should've acquired it from the author or made a deal with him to keep it live since all the links lead to Spotify anyway.
Kanata has mouse emulation so you can drive a mouse using arrow keys: https://github.com/jtroo/kanata/blob/main/docs/config.adoc#m...