1) Several leakers, including Kopite, have made mistakes that can't simply be excused by "the company changed their plans." Things like clock speed adjustments can change as final specifications are dialed in, but getting something like the memory configuration or core count wrong is a different matter. These are foundational aspects of hardware that are typically set well in advance and aren't subject to last-minute changes. So when leaks get these major details wrong, it’s not just about shifting plans—it's about the leak itself being inaccurate.

2) Even if what you’re saying is true—that leaks are "correct" at the time but companies change their plans—that still means leaks are unreliable. People look at leaks because they want to know what to expect, and if the excuse for getting things wrong is always "they changed their minds," then the leak might as well be speculation. Constantly falling back on "plans changed" makes leaks feel more like guesses. It's awfully convenient for leakers who frequently get things wrong to blame it on Nvidia or whoever supposedly changing their minds.

The point is, even if some details in a leak might be accurate at one point in time, that doesn’t make the information trustworthy for consumers or enthusiasts who rely on it to get a clear idea of what’s coming. The fact that these "updates" are often vague or conflicting adds to the unreliability of the leaks themselves.