‹ BackHN Continuity

Thread

Pirate Face Rescues LLM Models from Deletion

569 points · 149 comments · skepticalgenius

  1. wren6991 · · focus · HN ↗
    Speaking to the "uncensored model" angle: there's little reason to distribute abliterated weights anyway. Instead of orthogonalising the weights that write back to the residual stream, you can just orthogonalise the activations themselves. It's equivalent.

    Orthogonalising activations at runtime is computationally cheap. Just distribute the refusal vectors (few thousand floats per layer), then run against the stock weights. Antirez&#x27;s DS4 already supports this: <a href="https:&#x2F;&#x2F;github.com&#x2F;antirez&#x2F;ds4&#x2F;blob&#x2F;8db1d1d155cb0400a86a86b9c62d0defb3a6148b&#x2F;dir-steering&#x2F;README.md" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;antirez&#x2F;ds4&#x2F;blob&#x2F;8db1d1d155cb0400a86a86b9...

    Abliterated weights are just a bad habit we&#x27;ve gotten into. It&#x27;s also deeply suboptimal from a precision point of view to take a model that&#x27;s already been QATed and distributed in pre-quantised form (DeepSeek V4, Kimi K2.5 or K3...), modify its weights, and re-quantise it. Similarly, abliterated models regain some of their refusal behaviour when they&#x27;re re-quantised after abliteration -- avoidable by keeping the two separate.

    1. khalic · · focus · HN ↗
      I didn’t know about that method, thank you. I’ve needed a local model for security research but Qwen 27b abliterated did 30% worse than the stock weights on my internal benchmarks (I just skip the public benches now, it’s honestly useless noise on an operational level).
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.