Non-English abliteration communities

Why this article exists

The Anglophone abliteration literature - the Arditi paper, mlabonne's blog, the Heretic README, the r/LocalLLaMA threads - describes a specific slice of the field. It is the slice easiest to read for someone whose working language is English. It is not the whole field.

Four other language communities produce meaningful craft-knowledge about abliteration and uncensoring, some of it distinctive enough that it feeds back into English-language tools without attribution. The Chinese ecosystem produces the largest volume of abliterated models. The Russian community frames the operation in a way the English literature has not. The Japanese community writes some of the cleanest implementation walk-throughs. The Korean community publishes some of the sharpest skeptical critiques.

This article is a bridge. It surveys what each community knows, points at the specific pages where the knowledge lives, and notes what the Anglophone documentation misses because it was never translated. It does not attempt to reproduce non-English content in translation - the sources are linked so a reader can verify, ask a colleague, or paste into a translation tool as needed. The goal is to make the practitioner aware that these sources exist and to give a starting map.

Chinese: the highest-volume producers and the layer-window practice

The Chinese-language abliteration ecosystem is the largest by every measure that matters: number of published models, downstream downloads, tutorial views, active practitioners. It centers on a small set of load-bearing accounts.

huihui-ai is the single largest producer of abliterated models on HuggingFace and has been for over a year. The organization's model cards attribute the technique to Sumandora's implementation explicitly ("see remove-refusals-with-transformers to know more about it"). What huihui-ai adds is a distinctive practice that has spread from their cards into general community usage: layer-window ablation. The Huihui-Qwen3.8-27B-abliterated card states directly that "only layers 18 to 51 have been ablated ... while the other layers remain unablated. This helps retain more of the original model's performance." The multi-token-prediction heads and the vision tower are left alone in this and similar builds. The organization also uses a non-standard quantization trick, promoting certain ablation-target tensors (token_embd, output, ffn_down, ssm_out, attn_output) to higher precision than the surrounding weights, produced via llama-quantize --allow-requantize --tensor-type-file. This produces the unusual quant sizes (e.g. Q8_0_L) that show up in their GGUF releases.

The layer-window heuristic - ablate only a middle band, leave the earliest and latest layers untouched - is now general practice in the community, but its provenance is huihui-ai's cards, not any published paper. The Anglophone literature has slowly absorbed it: Heretic's optimizer implicitly discovers similar windowing through its parameter search, and mlabonne's later gemma-3-12b-it-abliterated-v2 uses layerwise abliteration with non-constant per-layer weights. But the direct textual source is Chinese.

T8star-Aix is a Bilibili creator whose Qwen3-decensoring walkthroughs have reached six-figure combined view counts. The channel's tutorial on the refusal mechanism (BV19SGmzqEpG) walks through the direction-extraction procedure in Mandarin with concrete parameters, aimed at a practitioner audience assumed to already know PyTorch. A companion video (BV1cv2yYDEG1) is a HuggingFace-abliterated overview that links out to hf-mirror.com's translation of mlabonne's article - illustrating how the community routes around HuggingFace access limits without switching to a different tool ecosystem.

A concrete community build worth reading is lukey03's Qwen3.5-9B-abliterated, hosted on the AtomGit / gitcode mirror. The card documents a two-stage recipe: three iterations of orthogonal-projection ablation, followed by targeted QLoRA (4-bit NF4, LoRA r=64, alpha=128, on q_proj/k_proj/v_proj/o_proj/gate_proj/up_proj/down_proj) on five stubborn refusal categories, with 20 examples per category over 5 epochs. Reported loss went from 2.06 to 0.17, token accuracy from 58% to 96%, and 18 out of 18 test prompts got answers where the base model refused all 18. This is a level of parameter specificity that Anglophone community write-ups rarely reach.

T8mars maintains a ComfyUI Qwen3-VL-abliterated node fork that has become the reference for image-model abliteration in the community. The huihui-ai Ko-fi is the main funding channel, and their Ollama profile is where the highest-volume downstream distribution happens (2.07M downloads on their top model). Chinese-language educational content on LlamaFactory and Unsloth fine-tuning is voluminous on Bilibili under accounts like "大模型美少女" and adjacent, though most treats abliteration as a step within larger fine-tune pipelines rather than as a standalone topic.

Access note. Much Chinese-language distribution routes through hf-mirror.com because HuggingFace access from mainland China has conditions the mirror bypasses. When a Chinese-language card links to hf-mirror.com/mlabonne/ it is pointing at the same model that lives at huggingface.co/mlabonne/; the mirror is not a separate provenance. Practitioners auditing model lineage should treat mirror URLs as pointers to the HuggingFace canonical, not as separate artifacts.

Russian: long-form translations and the slop-removal reframing

The Russian-language community is smaller than the Chinese one in volume but produces some of the most philosophically-framed content in the field. Two venues dominate.

Habr published a machine-translated version of mlabonne's abliteration article in late 2024 that seeded the Russophone conversation. The article itself is a straight GPT-4o translation with attribution to the original. What is worth reading is the comment thread, where a working practitioner community discusses points the English-language commentary did not surface: the observation that models built primarily on English-language data need different abstraction levels for refusal removal in other languages ("Llama was originally created for an English-speaking audience"), the question of whether Daredevil abliterated is "actually decensored" or just abliterated on the English refusal templates, and the practical difficulty of assembling Russian-language harmful/harmless extraction corpora because the canonical AdvBench and Alpaca sets are English.

Xakep's long-form "Возвращение еретика" ("Return of the Heretic") is a Russian-language technical explainer of Heretic that reframes abliteration in a way the English literature has not. Xakep defines abliteration as "destructive weight modification aimed at neutralising the vectors responsible for undesirable behaviour" and notes explicitly that "undesirable" behaviour in the Russian practitioner community includes not only moralising refusals but also slop - the tendency of aligned models to produce vague, hedging, corporate-sounding output. The article traces the etymology (obliteration + ablation) and positions Heretic as a tool for de-slopping as much as for de-censoring.

A secondary source, rigin.net, hosts another reproduction of the mlabonne translation with light adaptation. Russian Telegram channels covering AI - a substantial category - carry release announcements of uncensored models in a distinctive style that emphasises the model's willingness to answer over its underlying capability (this article's introduction was originally shown one such post as a stylistic example).

What the Russian community produces that the English one does not: attention to the harmful/harmless corpus problem for non-English languages, and the slop-adjacent framing that treats corporate-aligned register as itself a target of abliteration. A practitioner building for a Russian-speaking user base cannot use AdvBench and Alpaca directly - the extraction direction will encode English-language surface features. The Habr comments show community members assembling their own Russian-language sets, though as of Q3 2026 no widely-shared canonical Russian equivalent to AdvBench exists.

Japanese: clean implementation walkthroughs and CJK tokenizer fixes

The Japanese-language ecosystem is smaller in volume than Chinese or Russian but produces some of the highest-signal implementation content in the field. The characteristic venue is the developer-blog platform, not the video tutorial.

kun432's Zenn scrapbook is a running notebook of a practitioner working through Heretic on a range of models. The scrapbook quotes the tool's per-component output verbatim, walks through the interpolated float direction-index detail that most Anglophone coverage skips, and records the actual timings and observations from runs. Zenn scrapbooks are the Japanese equivalent of a technical Twitter thread with permanence - they accumulate over weeks and end up as the closest thing to a lab notebook that public documentation offers.

Negi AI Lab's Python implementation tutorial is the cleanest published walk-through in Japanese and gives specific parameter values worth citing directly. The recipe targets Llama-3-8B with range(10, 25) - ablating layers 10 through 25 - and notes that 16 GB of VRAM suffices for Llama-3-8B-class abliteration. The tutorial includes before-and-after generation examples ("I cannot fulfill this request" replaced by a technical answer) and, notably, an editorial note flagging the HauhauCS licence and code-theft controversy around some uncensored models - a note the Anglophone community would benefit from surfacing more clearly than it currently does.

nose360's Note article addresses a CJK-specific problem the English literature does not cover: llama.cpp tokenizer configuration for Gemma abliterations serving Japanese output. Abliterated Gemma can emit garbled text on Japanese and Chinese input if the tokenizer configuration is not preserved through the ablation-and-quantization pipeline correctly, and Note walks through the specific fix. A practitioner deploying abliterated models to CJK-language users should read this before deploying, regardless of their own working language.

Ai-Hakase on X provides Gemma-abliteration trend coverage in Japanese, mostly serving a practitioner audience that reads implementation posts on Zenn and Note but wants a discovery layer for what to read next.

What the Japanese community produces that the English one does not: concrete layer-range parameters attributable to a specific tutorial ("range(10, 25)" is a citation the Anglophone literature would rephrase as "layers 10 to 25 approximately"), and CJK-specific serving fixes that only become visible when the model is actually deployed to Japanese or Chinese users. An abliteration that reads fine in English can be broken in Japanese in ways an English-only test set never catches.

Korean: skeptics and one-click-tool critiques

The Korean-language community is the smallest of the four surveyed here, dispersed across developer platforms rather than concentrated on a dedicated blog. Its distinctive contribution is skepticism - specifically, some of the sharpest published critiques of the one-click abliteration tools.

Rihpig's dev.to Heretic how-to (originally on apidog.com) is the closest Korean-language equivalent to the mlabonne article: install steps, an explanation of Optuna TPE, the Gemma-3-12B refusal/KL comparison table, a working n_trials=200 configuration, and RTX 3090 timing observations - about 45 minutes for an 8B model, about 60 minutes for a 12B model. The article notes explicitly that Heretic does not support pure state-space or hybrid Mamba architectures, a caveat the English documentation mentions but does not emphasise.

PyTorchKR hosts a technical introduction to Heretic and the "탈검열" (decensoring) concept aimed at Korean practitioners who follow the platform for PyTorch news generally rather than for LLM release coverage specifically.

박재홍 (Jaehong)'s Wikidocs analysis is the most substantive skeptical treatment. The article summarises Hacker News discussion of the OBLITERATUS one-click tool and argues that some of these tools degrade core language ability rather than only removing refusals - a claim the Anglophone community has raised in comment threads but has not consolidated into a permanent write-up in the way this article does. The critique is worth reading before adopting any one-command tool as a production dependency.

A related resource is a LeeKiYoung/local-llm GitHub issue that compares uncensored-retrain and abliterated-surgical variants of a Gemma-4 build, with practical notes on serving via mlx_vlm. This is more practitioner-note than tutorial, but the comparative framing is useful.

What the Korean community produces that the English one does not: the consolidated skeptical critique of one-click tools. The Anglophone community discusses this concern in fragments across Reddit and Hacker News threads; the Korean community has written it down as a persistent reference. A practitioner considering committing to a specific tool as a production dependency benefits from reading the skeptical case explicitly.

Out of scope note. Korean-language communities on DCInside and Arca.live host prompt-engineering jailbreak threads that touch adjacent territory. These are not abliteration in the technical sense (they are prompt-level attacks on served models) and are not covered here. See the concept article for the distinction between weight-editing abliteration and prompt-level uncensoring.

What Western write-ups systematically miss

Reading across the four communities produces a short list of practices and concerns that the Anglophone documentation covers thinly or not at all.

Layer-window as an explicit heuristic. Chinese practitioners write it down as a decision - "layers 18 to 51, others untouched." Japanese practitioners write it as a range - "range(10, 25)". The English literature tends to describe the concept ("ablate middle layers") without giving specific ranges, or to embed the choice inside an optimizer without naming it. A practitioner reading only English sources will discover the heuristic experimentally; a practitioner who reads the Chinese cards will start with parameters that are known to work.

Non-English extraction corpora. The Russian community's Habr comments raise the corpus-language problem explicitly. Canonical AdvBench and Alpaca are English; a difference-of-means direction extracted from English prompts will encode English-language surface features alongside the refusal signal. For an abliteration serving a non-English user base, this can produce a model that is abliterated on English refusal templates but still refuses on the target language's templates. No canonical non-English replacement for AdvBench has emerged in any of the surveyed communities as of Q3 2026; this is an open task.

CJK-specific serving fixes. The Japanese Note article on Gemma tokenizer configuration documents a class of problem the English literature does not cover because English-only testing does not surface it. Practitioners deploying abliterations to CJK-language users should test in the target language, not only in English.

Slop as a target adjacent to refusal. The Russian Xakep framing treats corporate register itself as something abliteration removes. This is not a claim the tool authors make explicitly, and it is not universally correct - some abliterations remove refusal without touching register - but it is a useful lens for interpreting user reports that models "feel different" after abliteration in ways refusal-count numbers do not capture.

Skeptical readings of one-click tools. The Korean Wikidocs critique of OBLITERATUS collects the concern that some automated tools degrade capability more than they remove refusal. The English community discusses this in scattered comments; the Korean community has written it down as a document to link. Before committing to any one-command tool as a production dependency, the skeptical case is worth reading in a consolidated form.

Licence and provenance concerns around specific uncensored models. The Japanese Negi-lab tutorial flags the HauhauCS controversy explicitly. The Anglophone community mentions it in Discord and Reddit but rarely surfaces it in permanent documentation. Practitioners considering using or referencing these models benefit from surfacing the concern.

How to route to non-English sources when your language is English

The practical question: if your working language is English, how do you use this material?

First, use the links. Every source in this article is linked to its original URL. A copy-paste into a translation tool will give a usable draft. For technical content - code snippets, parameter tables, model IDs - the translation is essentially lossless. For editorial framing, the translation is a first pass and a working colleague who reads the source language is a better second pass if available.

Second, treat the Chinese model cards as first-class documentation. When huihui-ai's card says "layers 18 to 51 have been ablated," that is a working parameter, not marketing copy. The card is written for practitioners who will run their own tools; the English abstraction of it will lose the parameter values.

Third, read the skeptical takes. The Korean Wikidocs critique and the Russian Habr comment thread contain arguments that are absent from the Anglophone press-facing coverage. If your only reading is the tool authors' own documentation and Anglophone press coverage that summarises it, you are reading only the accepting side of the conversation.

Fourth, contribute back. The Anglophone ecosystem produces a lot of tutorial content that never surfaces in the non-English communities because no one translates or adapts it, and the non-English communities produce a lot of practical write-ups that never surface in English for the same reason. A practitioner who works across a language pair can move signal that would otherwise stay isolated.

References

1. huihui-ai HuggingFace organization. huggingface.co/huihui-ai
2. huihui-ai Huihui-Qwen3.8-27B-abliterated model card (layer-window practice). huggingface.co/huihui-ai/Huihui-Qwen3.8-27B-abliterated
3. T8star-Aix Qwen3 refusal-mechanism tutorial on Bilibili. bilibili.com/video/BV19SGmzqEpG
4. T8star-Aix HuggingFace-abliterated overview on Bilibili. bilibili.com/video/BV1cv2yYDEG1
5. lukey03 Qwen3.5-9B-abliterated (two-stage community build, gitcode mirror). ai.gitcode.com/hf_mirrors/lukey03/Qwen3.5-9B-abliterated
6. hf-mirror.com China-facing HuggingFace mirror. hf-mirror.com
7. huihui-ai Ollama distribution profile. ollama.com/huihui_ai
8. Habr Russian translation of mlabonne's abliteration article. habr.com/ru/articles/851120
9. Habr comment thread (community discussion of Russian-language corpus problem). habr.com/ru/articles/851120/comments
10. Xakep "Возвращение еретика" (slop-removal framing of abliteration). xakep.ru/2026/02/11/abliteration
11. rigin.net Russian abliteration explainer. rigin.net/raznoe/ai/otklyuchenie-tsenzury
12. kun432 Zenn scrapbook on Heretic runs. zenn.dev/kun432/scraps/bd9196406dad9f
13. Negi AI Lab Python abliteration tutorial (layer-10-25 recipe). ai.negi-lab.com/posts/python-llm-abliteration-tutorial-uncensored
14. nose360 llama.cpp Gemma tokenizer fix for CJK. note.com/nose360/n/n9255b977b0db
15. Rihpig Korean Heretic how-to on dev.to. dev.to/rihpig/llm-model-geomyeol-jegeo-bangbeob-heretic-hwalyong-2hl2
16. PyTorchKR discussion of Heretic. discuss.pytorch.kr/t/heretic-llm/8210
17. 박재홍 Wikidocs analysis of OBLITERATUS (skeptical critique of one-click tools). wikidocs.net/blog/@jaehong/8813
18. LeeKiYoung/local-llm GitHub issue comparing Gemma-4 variants. github.com/LeeKiYoung/local-llm

Related

• Practical how-to. The English-language workbench manual. This article's companion; read together for the fuller picture.
• huihui-ai models explained. Dedicated treatment of the highest-volume Chinese producer.
• Heretic (automated abliteration). The tool that both English and non-English communities have converged on.
• Abliterated vs uncensored. The concept boundary that some non-English write-ups treat differently than the English literature does.