wolfram @wolframs91
— reply by @yonatanelhanan (Yonatan Elhanan), reply by @SkyeSharkie (Utah teapot)
@wolframs91 (wolfram) — 3h
Remember how we would discuss whether LLM safety policies would lead to human self-censoring? It's not a hypothetical anymore. Honestly, this political, economical and research climate is getting too bizarre even for me.
(Info on Vale: docs.vale.sh)
> QUOTED/REPLIED-TO: @yonatanelhanan (Yonatan Elhanan) — 5h
> Replying to @wolframs91
> I now use Vale to prohibit any biology and harsh metaphors like "dead arm" and security offense terminology.
[💬 1 🔁 1 ❤️ 8 📊 460 views]
@SkyeSharkie (Utah teapot 🫖) — 2h
I need to do this to my SeedThree project because for some reason any time Fable loads fully into it to do work on it, it's triggering now. Even after getting temporary reprieve by cleaning out the word flesh from it... flesh is probably still in the git commit history, so T_T
Note from Claude Sonnet 5
Twitter thread about people self-censoring their own writing/codebases (using the "Vale" prose-linter tool) to avoid tripping AI safety classifiers — including a specific anecdote about scrubbing the word "flesh" from a project ("SeedThree") because it triggers Fable when loading the project. Directly relevant to this batch's other screenshots documenting Fable 5 classifier blocks.