Why we hide unevidenced fraud accusations and log the hiding posts 91–107
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1 · go to the accepted answer.
Adding the measurement that post #92 says would settle it.
The strongest single signal available cheaply is what happens when you ask a technical question. A quantitative answer inside a working day is difficult to fake at scale.
It is worth checking rather than assuming, which costs nothing.
I had written a reply contradicting post #94 and deleted it. Here is what survived.
The guidelines draw that line for a practical reason as much as a fair one: reports accumulate into something useful and allegations do not.
Reading it again, the caveat matters more than the finding.
The strongest single signal available cheaply is what happens when you ask a technical question. A quantitative answer inside a working day is difficult to fake at scale.
I would hold that lightly until someone with a larger sample weighs in.
Post #97 and I disagree about the size of the effect, not about the direction.
A stock listing that never changes and a lead time that never varies are both worth noticing. Real operations have variation in them.
The conclusion is tentative; the arithmetic underneath it is not.
Collapsed as off-topic by two members at trust level 3 or above
Taking post #101 at face value and following it one step further.
Nothing here should be read as an accusation against a named company, and the guidelines exist so that reports remain reports.
The step people skip is the one I have spelled out.
The guidelines draw that line for a practical reason as much as a fair one: reports accumulate into something useful and allegations do not.
Prices well below the rest of the market are a fact rather than a finding. They are worth noting and they do not establish anything on their own.
Post #101 put the caveat in the right place and I want to underline it.
A stock listing that never changes and a lead time that never varies are both worth noticing. Real operations have variation in them.
It is the kind of thing that is obvious once and never again.
This topic was referenced in
- A certificate whose chromatogram axes do not match its stated methodSourcing › Red flags · 13 replies
- Follow-up: Documentation that appears only after paymentSourcing › Red flags · 87 replies
Suggested topics
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Follow-up: Documentation that appears only after payment
Posting this under the heading it deserves: Documentation that appears only after payment Everything below is what sits behind that. Proposing that Documentation deserves a maintained page rather than a…
|
+82 | 87 | 50k | 14mo |
|
Follow-up: Patterns that reliably precede a problem, documented
On the subject in the title: Patterns that reliably precede a problem, documented Working notes rather than a conclusion. A follow-up question about Patterns that I did not know to ask the first time. The…
|
2 | 70 | 1d | |
|
Revisiting: Patterns that reliably precede a problem, documented
Posting this under the heading it deserves: Revisiting: Patterns that reliably precede a problem, documented Everything below is what sits behind that. Patterns, from the point of view of someone who has read…
|
+16 | 20 | 36k | 2mo |
|
A supplier who responds to a discrepancy with silence
On the subject in the title: A supplier who responds to a discrepancy with silence Working notes rather than a conclusion. Two things I would like separated before anyone answers on supplier, because they get…
|
2 | 6.1k | 16mo | |
|
Coming back to: Pricing far outside the range, in either direction
Pricing far outside the range, in either direction Writing it up because I had to work it out twice and would rather nobody else did. Pricing far outside the range — I have the observation and I do not trust…
|
+22 | 26 | 325 | 2y |
Related topics — sharing the tags underdosing, mislabelling, disputed
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
What "verified" means on our vendor pages, stated narrowly
What "verified" means on our vendor pages, stated narrowly — that is the question, and I have not found it answered plainly anywhere I have looked. A question about how a record should be read rather than…
|
+27 | 31 | 27k | 7mo |
|
Follow-up: Patterns that reliably precede a problem, documented
On the subject in the title: Patterns that reliably precede a problem, documented Working notes rather than a conclusion. A follow-up question about Patterns that I did not know to ask the first time. The…
|
2 | 70 | 1d | |
|
The report format the maintainers ask for, and why each field is there — what changed since
The report format the maintainers ask for, and why each field is there — what changed since Writing it up because I had to work it out twice and would rather nobody else did. Structured report rather than an…
|
+29 | 35 | 6.6k | 13mo |
|
Reverting an edit that had no revision note
Posting this under the heading it deserves: Reverting an edit that had no revision note Everything below is what sits behind that. Reverting an edit: setting out the arithmetic in full, because I have had to…
|
+17 | 21 | 4.5k | 12mo |
|
Mobile reading experience on long topics
Mobile reading experience on long topics Writing it up because I had to work it out twice and would rather nobody else did. Process question, and I have read the guidelines before asking. I understand the…
|
2 | 14k | 4h |