> I was fact-checking your (unsolicited) diagnosis, which you had already provided despite my lack of request for any kind of support.

Yes, I posted a general response to the class of problems that your anecdotal story appeared to apply to. In an informal discussion of anecdotal evidence, what sort of fact checking do you seriously think could be performed? It's basically impossible. You are trying to set an impossible bar for anyone to comment on anything you say.

> I said if you wanted to check your facts I would provide you with information to confirm or disprove you

That's... not how any of this could possibly ever work. You want me to perform research so that you can tell me whether I got it right or not? My original response stands regardless of if it effects your system: proprietary code is often a problem for package managers.

But further more, as the one holding the anecdotal (and physical) evidence, the onus is on you to agree or disagree with facts using it. Your request for me to do original research specific to your problem is at it's most charitable a tech support style question (even if phrased along the lines "what technical knowledge do I need to prove you wrong?"). Because if it were a request for evidence in a discussion it would be an unreasonable request positioned to stifle all disagreement with you by placing unnecessarily large (e.g. ridiculous) burdens on anyone who comments (to which my response would be much stronger).

If alternatively you had said "I doubt that because I never installed NVIDIA code on the system." or nothing at all. I wouldn't have cared or responded.

No I said he implied that about other people. When he said they weren't reading what he was saying and were instead talking about some other story. If a person wrote a response exactly about his scenario, then saying what he did in response would imply that he thought that person was delusional. Which is what happened. I quoted it.

That was the point I gave up on him being an honest participant.