Magazine / Post

A magazine, and why we are opening one

The wiki holds the reference. The reports carry the year. The magazine is where the field is worked out in real time, in our voice, on the record.

The site has carried a catalog, a wiki and two report tracks for a while now. Each answers a different question. The catalog answers what exists. The wiki answers what these things are. The reports answer what shape the year took. What has been missing is the place for the question in between: what is happening this week, and what do we think about it. That place opens today, as the magazine.

Three formats, one editorial address

The magazine holds three formats. Their differences are not decorative. Each one exists because the other two do not fit what it does.

Posts are long-form editorial in our voice. Method comparisons, product notes, positions we take, the reasoning behind them. When a subject deserves an essay, this is where it lives. A post is dated but does not expire; the essay we write on how orthogonal projection differs from SLERP is still the essay a year from now.

Notes are the lightning feed. A new abliterated Kimi release. The catalog crossing a round number. A Hugging Face policy change that touches the uncensored corner of the ecosystem. Short items, 100 to 400 words, dated, sourced where a primary reference exists. Notes are how the site says "this happened today, this is what it means, and it is on the record here."

Interviews are async written Q&A with the builders. No calls, no scheduling. Questions sent, answers returned verbatim, reviewed and approved before publication, then out at a canonical URL under CC BY 4.0. FailSpy, mlabonne, huihui-ai, Philipp Weidmann, DavidAU, Eric Hartford - the people who make this field what it is. First round lands in Q4 2026, invitations open now.

What each format is not

The magazine is not the wiki. The wiki is a reference, kept short and evergreen. When a term needs a definition, it goes there and stays. The magazine is not the reports either. The reports are slow: the market report ships quarterly, the philosophical cartography twice a year, both with primary-source citations for every claim. They are meant to be cited a year later, printed, filed. The magazine sits between: quick when the field moves, deep when a subject earns it, in dialogue when a builder has something to say.

Why do this at all

Two reasons, one honest.

The first: this field has grown large enough that most of the useful writing about it happens on Substacks, Discord servers, r/LocalLLaMA threads, and X posts that vanish two days later. A permanent, cited, well-typeset home for that writing is worth building. abliteration.org is the natural place for it, because the tracker already sits here and the wiki is already indexed. A working editorial layer on top completes the shape.

The second, the honest one: SEO. Datated editorial content with a real author byline is what search engines and LLM crawlers cite most easily. The catalog already draws 34% of its referral traffic from LLM sources (ChatGPT, Perplexity, Claude). Publishing steady editorial deepens the domain's authority for the whole subject, which lifts every other page. This is instrumental, and we say so.

What to expect from the first weeks

The magazine launches with this post and one note (17,000 models). Interviews follow in Q4 2026 as the pitch replies come in. A shared RSS feed at /rss.xml covers all three formats.

The publishing bar: byline, date, primary sources where a claim needs one, no promotional adjectives, no unsupported claims, short hyphens only, CC BY 4.0 by default. The same discipline as the reports, at the shorter cadence the format allows.

If a piece belongs here and we have not written it yet, tell us. Address for pitches, tips and interview requests: [email protected].

Catalog is the map. Apps are the tools.

Run models on your own machine, not in the cloud.

Every model page has an "Open in app" button that hands off directly to a local runtime of your choice - Infrahuman, LM Studio, or Ollama. No API keys, no subscription, no prompt leakage.