I support “incorrect”, because unlike you, I consider it more narrow than “debunked”. In many cases you can produce reputable source arguing against something even if it is correct. Debunked and Well-Refuted explained this dynamics well.

I’ve used the spam flag here because it’s the sort of article that relies on taking the meat of other things, running them through some process to distort their original intent, and then repackaging the results as a meat-like substance that is theoretically as filling but clearly less healthy than what it started life as. You know, spam.

Vice, like Hormel, is a brand you can trust to produce spam.

Some time back, it was explained that we can and should use the “troll” downvote in a sense more broad than might be appropriate in other contexts.

I’m trying to apply that reasoning to this proposal , but I’m not sure which of these flag options I see on posts should be applied to the example post. I guess I would pick spam? But the inaccuracy of that option basically discourages me from flagging at all. I guess I support the addition of a new flag.

I favor “incorrect” over “debunked”.

Side note: sorry sanxiyn, I’m not checking out your link just now. Thus still naive, I see “incorrect” as more broad than “debunked”.

How do you down vote stories?

TL;DR: add an Incorrect flag if that makes more people vote; but that won’t be enough, the scoring algorithm needs to be fixed, needs to be made more lobster like.

Incorrect submissions are also spam. Spam is something unsolicited. Incorrect submissions are not explicitly solicited. Therefore they are also spam. That doesn’t require that you can identify a thing that is being promoted.

You mentioned reputable sources but did not say how you define reputable and whether that is independently testable. Reputation can not replace testing an argument, but if done correctly it can help coordination to find things that are worth testing. I consider incorrect thus a more useful concept here.

What is the goal of flagging? Some reason may be a negative score to filter <0 and/or some admin reaction. Anything else?

Many incorrect submissions still keep a positive score, even after that is shown in the comments. A more specific flag than spam will not necessarily make them go negative. That is not a reason to not add an alias or more specific flag if that makes more humans vote at all on a story.

It happens that incorrect information is scored high on this site. One might want to use a better reputation algorithm to make it easier to find scientifically correct submissions and not waste time with things that are incorrect. One that improves quality over time without resorting to authority or majority-rule. It needs to work on something more specific than one score/tally, like if a tag applies (or even a more expressive assertion). It would require calculating the reputation individually for a user based on who they trust to use a tag correctly. Which is a more lobster like approach, as they don’t form a shared hierarchy but each their own view of it. The trust calculation needs to be able to differentiate between trust for different tags. This trust between two humans needs to be calculated based on tags/assertions they put in this system, not directly. It needs to be able to keep by user choice some input private. It needs to take into account if people acknowledge their errors. (To answer if I make an adversarial collaboration with this person.) It needs a way to avoid Sybil attacks. Explicitly tagging things as “correct scientific argument” is needed to make the goal more obvious and to not exclude fiction, jokes, and allow any categorisation goal. It should be able to tag only a part of a submission.

A good collaborative categorisation system makes it possible to take into account when people agree on a specific assertion without requiring agreement on other or a more general assertions. (The current one fails this by requiring agreement on a the very unspecific “up or downvote”.)

Another story this might apply to: Keybase iOS Has A Backdoor

Strongly support