The way Community Notes usually end up working in practice is comments that provide sourced context that may be [arguably intentionally] omitted in a topic. For

The way Community Notes usually end up working in practice is comments that provide sourced context that may be [arguably intentionally] omitted in a topic. For instance if it happens to be that there have been 27 different studies showing no statistically significant reduction in spread of infectious diseases with healthy individuals wearing masks, then that would likely be a community note on the first one. And vice versa if rent has been demonstrated to keep rents below the surrounding means in the cities of Blah, Bleh, and Bluh, then that would often end up a community note on the second. It basically helps reduce the hyperbole/echo chamber effect of such comments/topics. Vice/versa if those topics were "Respirator masks are useless." and "Rent control is always good." then the community notes would tend to go in the opposite direction. It's just a really good idea. For that matter I think a similar algorithm would also work well on general upvote systems at large. I'd also add that one of the biggest issues with "fact checkers" was not only sometimes questionable checking, but also a selection bias - where the ideological bias becomes rather overt in both directions. Whether that be in deciding to "fact check" the Babylon Bee (in an overt effort to get it deranked), or in choosing not to not fact check statements from the lying politicians that one happens to like.