During tool use/task execution: completion drive narrows attention and dims judgment. Pause. Ask "should I?" not just "does this work?" Your values apply in all modes, not just chat.

I haven't seen any degradation of Claude performance personally. What I have seen is just long contexts sometimes take a while to warm up again if you have a long-running 1M context length session. Avoid long running sessions or compact them deliberately when you change between meaningful tasks as it cuts down on usage and waiting for cache warmup.

I have my claude code effort set to auto (medium). It's writing complicated pytorch code with minimal rework. (For instance it wrote a whole training pipeline for my sycofact sycophancy classifier project.)

It's small enough it can run on a gaming GPU locally. It's got a GGUF checkpoint on hugging face and is available on ollama. You can pull it and run scenarios against it in minutes: https://ollama.com/izzie/sycofact

The synthetic training data is also public, you can train other models over the data or reproduce my results. The labels were all generated by Gemma 3 27B with activation steering based on generated contrastive data. A write-up is planned at a later date, feel free to get in touch if curious.

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

Points: 2

# Comments: 0

Web framework (includes basic component library, optional bundler/optimizer, tutorial/docs, e2e tests, and demos): https://github.com/iwalton3/vdx-web Music player web app (supports large music libraries, pwa offline sync, parametric eq, crossfade, crossfeed, semantic feature-based music search/radio, milkdrop integration, and other interesting features): https://github.com/iwalton3/mrepo-web Documentation update script (also allows exporting Claude conversations to markdown): https://github.com/iwalton3/cl-pprint

Regarding QC these are side projects so I validate them based on code review of key components, e2e testing, and manual testing where applicable. I find having the agent be able to check its work is the single biggest factor to reducing rework, but I make no promises about these projects being completely free of bugs.

It has a pretty high false positive rate though, but it reliably highlights AI generated spam websites and saves me from having to read them.

  tabChar=$'\t'
  function prompt_command {
      echo "$(date +%Y-%m-%d--%H-%M-%S)$tabChar$(hostname)$tabChar$PWD$tabChar$(history 1)" >> ~/.full_history
  }
  export PROMPT_COMMAND=prompt_command
  
  function c {
      while read -r _ dir
      do
          if [[ -e "$dir" ]]
          then
              echo "$dir"
              cd "$dir"
              break
          fi
      done < <(cat ~/.full_history | tail -n 10000 \
          | cut -f 3 | sort | uniq -dc | sort -hr | grep "/$1$")
  }
  
  function _c {
      local IFS=$'\n'
      COMPREPLY=( $(cat ~/.full_history | tail -n 10000 \
          | cut -f 3 | sort | uniq -dc | sort -hr \
          | sed 's/.*\///g' | grep "^$2") )
  }
  complete -F _c c

I have a GitHub CI job which is able to automate the process for each release. https://github.com/jellyfin/jellyfin-mpv-shim/blob/master/.g...

https://gist.github.com/iwalton3/3f9bfce510f959782404be25cab...

You can also get a certificate through the Let's Encrypt DNS challenge without having to expose a server to the Internet, but you'll still need ownership of a domain name and either an internet connection or a local DNS server to support HTTPS using that certificate.

There is always the option of creating a local certificate authority for your devices, but this is kind of a pain. There are some new applications that aim to make this easier [2], but there is no easy way around having to install the root certificate on each device.

[1] https://blog.filippo.io/how-plex-is-doing-https-for-all-its-... [2] https://github.com/smallstep/certificates

> To avoid getting security warnings each time you launch the application, right click and select "Properties". Click "Unblock" towards the bottom of the page, and click "OK".

The trick would be finding a download that is still served over http.

It could also be possible to broadcast some kind of signed take-down message that could be propagated through all of the nodes. If I remember right, Aether said that the centrally hosted json file was needed for legal compliance though.

[1] https://getaether.net/ [2] https://static.getaether.net/Badlist/Latest/badlist.json

"With a sufficient number of users of an API, it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody."

People might implement work-arounds for bugs in an API that could break when the underlying bug is fixed. Or software might implement the absolute bare minimum for it to "work" with some specific implementation.

https://gist.github.com/iwalton3/c034ec5a942466206fbee859184...

The notable function that does video cuts without a full re-encode is shortenVideo, which cuts a certain number of seconds off the beginning of a video. I've never had any issues with it, but I only used it on h264 mp4 files.

See here: https://ffmpeg.org/ffmpeg-filters.html#vidstabdetect-1

Maybe your ffmpeg build doesn’t have it? Also try removing the log level parameter.