Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Ultimately: It can take some time for community notes to correct misinfo posts; by the time community notes gets to it, the firehose has ten more misinfo posts community notes needs to fix, the people who saw the original post rarely see the community notes correction, and given the algo has a massive temporal bias the original post was probably on the way out of new viewers feeds anyway.

Its a good system that should exist. It could probably be made better by finding any way to help it act faster (e.g. the moment a post is even in the process of community notes voting, attach a temporary banner like "The Community Notes people has suspicions about this post, it might be misinfo, we're doing our research").



I am not sure about that. I see a lot of posts that get CN proposed for bogus reasons that never see the light of day. This is usually done by interest groups who view CNs as another avenue of their strategies. These interest group CNs almost never see the light of day so I would strongly advocate for not putting warnings just because a rando attempted to put a CN on a post.

Imagine every post by Donal Trump getting a CN from a Democratic activist group or vice versa, every post by Kamala getting a CN by a Republican activist group. Every single post will have a warning on them if you get what you are proposing.


Use AI for all posts that have 10k views and do a scan for similar posts with embeddings




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: