Lysita vs. Community Notes

What Community Notes does well

Community Notes (formerly Birdwatch) is a genuinely clever piece of design, not just a feature bolted onto a feed:

• The bridging algorithm — a note only ships when it earns agreement from contributors who usually disagree with each other, not a simple majority vote; a well-studied, deliberate defense against a note becoming another front in the same tribal fight it's trying to correct, and the single best idea in the whole design
• Scale — Community Notes operates across one of the largest social platforms in the world, and a note on a viral post can be seen by millions of people within hours
• It attaches to the thing being corrected, in the place the audience already is — no separate site to visit, no context switch; the correction shows up directly under the post, to the same people who saw the original claim
• It's free and open — the algorithm and a large volume of rating data are public, which has let outside researchers actually study how well it works instead of taking the company's word for it

If your goal is correcting something that's already gone viral, in front of the audience that's already looking at it, Community Notes is a better fit than Lysita, and we'll say so plainly — Lysita has no answer to "millions of people are already looking at this one post right now."

What Lysita does differently

The claim is the unit, not the post

A Community Note is permanently attached to someone else's post, on their platform, in their feed. Lysita makes the claim itself the first-class object — it isn't an annotation on something else, it's the thing with its own debate, its own corrections, and its own history.

The corrector gets durable credit, not just a rating

Note authors on Community Notes get almost no durable, portable credit — visibility mostly comes from a helpfulness rating in an interface most users never see. Lysita's depreciating authorship credit shifts a claim's credit toward whoever actually improved it: merged corrections and winning rebuttals earn a real, visible share of the claim's authorship, not a backend score.

Built for correction, not bolted onto a feed optimized for something else

Community Notes has to work against the grain of a feed whose core optimization is engagement, not accuracy — that's a real structural tension the design has to keep fighting. Lysita's entire substrate — the claim/take gate, debate structure, correction markets — is built for this from the ground up. There's no competing feed algorithm to work against.

A falsifiability gate before the claim exists

Community Notes corrects a post after the fact; there's no requirement that the original claim ever stated what would prove it false. Lysita's falsifiability structural test requires that up front — before a Claim can be published, its author has to state what evidence would disprove it.

Structured for/against, not a single note

Community Notes ships one (sometimes competing) note per post. Lysita's debate structure gives a claim nested for/against entries that can themselves be rebutted, so the correction process isn't limited to a single annotation winning out.

Corrector identity and expertise are visible

A Community Notes contributor is functionally anonymous — you can't tell if the person correcting a medical claim is a doctor or a random account with a high rating. Lysita's segmented identity layer lets a correction carry a verified professional identity (pseudonymous, but verified within its segment), so "who is telling me I'm wrong, and why should I trust them" has an actual answer.

Same anti-collusion problem, solved the same way

Community Notes' bridging requirement exists specifically to stop coordinated groups from gaming ratings by agreeing with each other. Lysita's candor score is weighted by counterparty diversity for exactly the same reason — to resist candor-farming via coordinated reciprocal "wins" between colluding accounts. We built our own version of Community Notes' best idea rather than pretend the problem doesn't apply to us too.

Side by side

Which should you use?

Use Community Notes if you want to correct something at the scale it was seen — a viral post, a trending claim, an audience of millions who aren't going anywhere else to see the correction.

Use Lysita if you want the claim itself to have a durable, structured record — sourced corrections, a real for/against debate, and credit that follows the person who actually got it right over time.

Use both if you're trying to correct the record broadly. Community Notes reaches the audience where the false claim already is; Lysita gives that correction a permanent, structured home that doesn't disappear when the post scrolls out of anyone's feed.