https://chromewebstore.google.com/detail/adios-alexa-for-sho...

Turnstile everywhere + device attestation required is the direction this all seems to be headed. Because of all the AI bots of course (it is an excellent scapegoat).

On this point in particular (that we’re broadcasting these signals), in one of the AoA courses I took there’s an exercise where you and a partner take turns guessing at the emotion the other person is feeling. You’re just staring into each others’ eyes on zoom, and one person is going “angry. sad. joyful. fear. Angry again.”

When I was the guesser I had no idea if I was even in the ballpark.

But when the other person was guessing my emotions, they were probably 70% accurate with what I was feeling. We discussed afterward and they had the same experience (I had apparently gotten most of them right). It was wild.

At first (and for admittedly way too long), I used this as a way to try out fun new frameworks - Node+Express for one thing, Phoenix for another, SvelteKit for a third.

I noticed it was a huge pain to dive into these things once every 6 months. I’d forgotten how it worked, and for some of them at least, I could look up docs and examples.

My Node+Express thing was the worst because it was all homegrown. There’s very little convention in that world, and you have to make your own. No docs were coming to save me, and this was in the Before Times, like 3 years ago pre-LLM.

Anyway I ported everything to Rails and it’s wonderful. I know how it works, there’s almost 30 years of examples online and they even mostly still work, and LLMs are great at it too.

Lots of power in a good framework, in a situation that’s a good fit for it!

You mention the emotional neglect and the connection to childhood, and I get the sense you’re interested in figuring it out. It made me think you might like Joe Hudson’s work on YouTube.

(Must say I'm not a fan of how, increasingly, taking any steps to preserve privacy is seen as deviant, or justified because bots)

Comments URL: https://news.ycombinator.com/item?id=47526242

Points: 2

# Comments: 0

You can! While you’re alive and everything! I’ve had this experience of few times of it being very quiet, and overall my brain is a lot quieter since then (and I see reports from people who’ve gone further/deeper; I get the sense the path is never-ending).

There’s a ton of resources and people out there that basically point to the same thing in different ways. Meditation is one of the ways but it’s not the only one. Some keyword soup if you want to go searching: jhana states, Jhourney, Art of Accomplishment, Joe Hudson, Zen, Buddhism, awakening, Michael Singer, Loch Kelly

There are varying levels of “woo” in this, and if you’re on the woo-averse side, Joe Hudson’s stuff is a good way in.

More or less what it says in the README:

    fence -t code -- claude --dangerously-skip-permissions

    # cat prompt.md | ralph
    function ralph() {
      fence -t code -- \
        claude --verbose --dangerously-skip-permissions --output-format stream-json -p "$@" \
        | jq -r 'select(.type == "assistant") | .message.content[]? | select(.type? == "text") | .text'
    }

And apparently it's violating the terms of service. Is it fair and above board for them to ban people? idk, it feels pretty blatantly like control for the sake of control, or control for the sake of lock-in, or those analytics/telemetry contain something awfully juicy, because they're already getting the entire prompt. It's their service to run as they wish, but it's not a pro-customer move and I think it's priming people to jump ship if another model takes the lead.

0: https://github.com/Use-Tusk/fence

Thankfully the official Agent SDK Quickstart guide says that you can: https://platform.claude.com/docs/en/agent-sdk/quickstart

In particular, this bit:

"After installing Claude Code onto your machine, run claude in your terminal and follow the prompts to authenticate. The SDK will use this authentication automatically."

I can imagine some ideas (ask it for more detail, ask it to make a smaller plan and add detail to that) but I’m curious if you have any experience improving those plans.

One thing that stands out in your steps and that I’ve noticed myself- yeah, by prompt 10, it starts to suck. If it ever hits “compaction” then that’s beyond the point of return.

I still find myself slipping into this trap sometimes because I’m just in the flow of getting good results (until it nosedives), but the better strategy is to do a small unit of work per session. It keeps the context small and that keeps the model smarter.

“Ralph” is one way to do this. (decent intro here: https://www.aihero.dev/getting-started-with-ralph)

Another way is “Write out what we did to PROGRESS.md” - then start new session - then “Read @PROGRESS.md and do X”

Just playing around with ways to split up the work into smaller tasks basically, and crucially, not doing all of those small tasks in one long chat.