site banner

Quality Contributions Report for January 2023

This is the Quality Contributions Roundup. It showcases interesting and well-written comments and posts from the period covered. If you want to get an idea of what this community is about or how we want you to participate, look no further (except the rules maybe--those might be important too).

As a reminder, you can nominate Quality Contributions by hitting the report button and selecting the "Actually A Quality Contribution!" option. Additionally, links to all of the roundups can be found in the wiki of /r/theThread which can be found here. For a list of other great community content, see here.

This month we have another special AAQC recognition for @drmanhattan16. This readthrough of Helen Joyce’s Trans: When Ideology Meets Reality garnered several AAQC nominations throughout the month:

Part 1 – The History of Transgenderism

Part 2 – The Causes and Rationalization of Transgenderism

Part 3 – How Transgenderism Harms Women And Children

Part 4 – How Transgenderism Took Over Institutions And How Some Women Are Fighting Back

Part 5 – Conclusion and Discussion

Now: on with the show!


Quality Contributions Outside the CW Thread

@gattsuru:

@Rov_Scam:

@OracleOutlook:

@popocatepetl:

@AmrikeeAkbar:

@urquan:

@Chrisprattalpharaptr:

@DaseindustriesLtd:

@erwgv3g34:

@ymeskhout:

@aiislove:

@faul_sname:

@throwaway20230125:

Contributions for the week of December 26, 2022

@FiveHourMarathon:

@dr_analog:

Contributions for the week of January 2, 2023

@FiveHourMarathon:

@Rov_Scam:

@JhanicManifold:

@screye:

@problem_redditor:

@veqq:

@daezor:

@LacklustreFriend:

Contributions for the week of January 9, 2023

@naraburns:

@huadpe:

@Stefferi:

@FCfromSSC:

@DaseindustriesLtd:

@Dean:

Contributions for the week of January 16, 2023

@Dean:

@ControlsFreak:

@Stefferi:

@DuplexFields:

@ymeskhout:

@strappingfrequent:

@doglatine:

Contributions for the week of January 23, 2023

@gattsuru:

@TracingWoodgrains:

@arjin_ferman:

@vorpa-glavo:

@Amadan:

Contributions for the week of January 30, 2023

@gattsuru:

@TracingWoodgrains:

@DaseindustriesLtd:

17
Jump in the discussion.

No email address required.

I have yet to come across a Holocaust "revisionist" who is not also antagonistic towards Jews as a group.

It's ipso-facto antagonistic towards Jews to engage in revisionism on this question. At least that is the framing they have established.

I do not doubt that the Yad Vashem Database is an accurate accounting of people murdered in the Holocaust

You should doubt it, because the methodology by which they determine a person was murdered is extremely flimsy- such as testimony over 50 years after the fact, from some friend or acquaintance who lost contact with so-and-so all those years ago.

It's also based on assumptions surrounding the use of code words in documents. So when a document describes a transport as "leaving the ghetto for work", the Holocaust historians assume that this was coded language for "murdered in gas chambers" and everyone on the transport is assumed as murdered. Revisionists have already shown many cases of duplicated entries, survivors listed as "murdered", and many people changed names after the war and lost contact with friends and even extended family.

There is no investigation whatsoever that these people were actually murdered. It is not a scientific source by any means. Why would a passport application be evidence that a person was murdered?

That is, he believes that mainstream historians are the ones who should be obligated to produce physical (or other equally compelling forms of) evidence in support of the claim that approximately 3,000,000 Jews were murdered in extermination camps.

The reason I'm a denier is because I find it completely unbelievable that anyone would believe this claim without extremely strong physical evidence. It's even harder to believe the antagonism of the mainstream position towards minimum standards of investigation that would be expected for the most cut-and-dry murder case of a single victim.

You won't get a good answer, you will get things like "Look at this name and this passport application", and people will find that compelling- even people here who are otherwise skeptical of highly unlikely claims.

You will notice that the closer they get with specificity, the more they can't justify their claims. @netstack was clearly moved by @faul_sname listing a few names from a database, he probably didn't even notice that @faul_sname never provided any evidence for his claim that 70,000 Lodz Jews were exterminated in Auschwitz in 1944, and never engaged with the Revisionist research that disproved the assertion.

For example, mainstream historiography makes the claim that at least 700,000 people were buried* in a precisely-known area of a small camp of less than 5 acres (or less than 5 football fields!). Why would anybody believe such nonsense without physical evidence? No number of passport applications in the Yad Vashem database is going to convince me of that assertion.

Er. I think I may not have explained clearly enough what I was doing there.

My purpose in listing those 5 names was not "make the account more moving by providing names instead of inhuman numbers". My purpose was to determine whether it was likely that those names corresponded to (1) real people who were (2) from a plausible area to be on that transport and (3) not obviously still alive after WWII.

If those names didn't correspond to anyone I could find details about pre-1940, that would have been evidence against that list of 4.8 million names corresponding to 4.8 million people. Likewise if the names and birth dates were repeated dozens of times, or if the documents looked like forgeries, or if there was an obituary from a 1976 newspaper about one of the 5 people and another two had gone on to have children in the 1950s. Those are ways the world could have looked.

In fact I got the outcome I pretty much expected. Which rules out a whole bunch of the specific ways "those 4.8 million names do not belong to Jews who died in Nazi custody during WWII" could be true.

As a note: you should not just believe me. I could have cherry-picked my random numbers. You should instead choose your own random numbers, and then test whether those random numbers appear to you to be people who did not exist / duplicated records / people who have a suspicious obituary in 1976, by looking at the world with your own eyes, which is a thing you are allowed to do.

Are you an auditor? What you did with the names would be referred to as "vouching": taking a sample from your population and finding the source documents for those in the sample, to verify management's assertion that those transactions actually exist.

I am not. We call it "random sampling" or "spot checking" in the professional context I inhabit (my role is dev / analyst (/ product manager / customer support / designer / qa / etc... can you tell I work at a small company?))

I do, in fact, do some fraud detection as part of my nebulously defined job responsibilities, though. For that my favorite heuristic is actually

  1. Pick a metric. Any metric. The stupider the metric sounds, the better. If you're running a marketplace, "fraction of orders with a positive subsequent review from the customer" is a good metric, but "average time from order to shipping label printed" might actually be better by virtue of not particularly sounding like it points at anything valuable.

  2. Rank all users by that metric.

  3. Take the bottom and top 5 users (with a substantial amount of account activity) by that metric.

  4. Most of those 10 users are probably trying to defraud you.

Ah, very cool. Sampling is a big part of auditing, as is directionality: vouching, for example, goes from final answer back to source documents, while tracing works the other way, from source to final, in order to verify existence and completeness respectively.

General auditing is directed more toward finding error than fraud, but forensic stuff interests me quite a bit.