Build1 publisher2 min readPublished
Open-weight moderation models land inside the proprietary error band on Bluesky posts
A seven-model comparison on real Bluesky posts reports open-weight sensitivity of 81 to 97 percent against 72 to 98 percent for the proprietary APIs, with the error direction reversing between rudeness and threats.
The Engineer · Build desk

What happened
- Researchers compared seven state-of-the-art models out of the box, four proprietary and three open-weight, on detecting harmful content in social media posts.
- Specificity exceeded sensitivity for rudeness detection, while for intolerance and threats the ordering reversed.
- Sampling drew rule-violating posts from three categories, rude, intolerant and threat, alongside a random draw of posts the moderation service had not flagged.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- decision For a platform whose rules resemble the three Bluesky categories, paying per call for moderation becomes a hosting and privacy question, because the open-weight band covers the proprietary one on both metrics.
- constraint The two reported metrics do not size a review queue: at low violation rates a 9-point false-positive rate dominates whatever a human moderator ends up seeing.
- capability Detection running locally keeps posts on the operator's own consumer-grade hardware, which is the privacy case the paper makes for open weights.
- contradiction Earlier work found consumer-hardware open-weight models inadequate for this task or in need of fine-tuning, so a 2024-era negative result no longer settles the buy-or-host question by itself.
One decision rule across all three categories buys both failure modes at once. Because specificity beat sensitivity on rudeness, a violating rude post was likelier to slip past than a clean post was to be flagged [6]. On intolerance and threats that ordering flipped, so the false alarms concentrate there [6]. Zero-shot classification hands back a label, not a score, so the per-category adjustment has to be a per-category prompt, a different model on one category, or a second pass over one category's flags.
The overlap is between two sets. Four proprietary systems produced the 72 to 98 percent sensitivity band and three open-weight ones the 81 to 97 percent band [1][4]. At the floor the open-weight set looks better, by 9 points of sensitivity [4]. It is still a floor of 81 percent, or 19 violating posts in every 100 going through [1]. The open-weight specificity band tops out at 100 percent, and a classifier that flags nothing scores that as well. The models and the sample size are missing from the arXiv abstract, so the bands cannot be turned into a shortlist.
Sensitivity and specificity carry across prevalence, but the load on a review queue tracks it. The study sampled rule-violating posts in three categories plus a random draw of posts the Bluesky Moderation Service had not flagged [3], a higher violation rate than a live stream. Assume one post in a hundred breaks the rules, and treat that rate as an assumption rather than a measurement in the paper. At the bottom of the open-weight band, 91 percent specificity turns 99 clean posts into 8.91 flags while 81 percent sensitivity turns the single violation into 0.81 [2], so about 92 flags in 100 are wrong [3].
Ground truth here is two authors reading the criteria the moderation service publishes and annotating each post independently [2]. The paper also reports inter-rater agreement across human moderators and the LLMs [5]. Measured sensitivity therefore depends on which human the model is scored against, and that holds for an operator's own labels too.
Open-weight models small enough for consumer devices had been reported as inadequate for harmful content detection, or as needing fine-tuning first [7], while proprietary models had already beaten commercial moderation tools on accuracy [9]. The check that settles it for one platform is a few hundred of its own past decisions, labelled by category, with sensitivity and specificity computed for each category separately, since a pooled score averages the two failure directions together.
What to watch
- Whether one open-weight model holds the top of both bands, or the 97% sensitivity and the 100% specificity belong to different models.
- Replication on a platform whose rule set does not map onto Bluesky's rude, intolerant and threat categories.
- Any published throughput and hardware figures for the local models, since the privacy argument rests on consumer-grade devices.