Vote with your vote for politicians for common sense regulations that favor the consumer at the expense of everything else.
1,403 karma · joined August 29, 2023
Vote with your vote for politicians for common sense regulations that favor the consumer at the expense of everything else.
Are you even reading the thread?
I didn't read that comment. I don't care about that comment at all. I am someone that complains about sloppy duplicate question and it's only in fringe cases that I gave a example of. Branton is saying that almost all duplication is wrong, that's a lie, because if he had any concern by the truth he would not have made that assertion
No, Bratmon does exactly the same assertion
Either way, it's more efficient to give whatever money to bail out individuals/consumers than to bail out rent seeking organizations
The top answer is still up to date
There's zero reward for closing a question. I know that because I casted 2 thousands of those, no reward ever came my way.
> The honeypots in the review queue trained you to err on the side of closing questions
That's also false, there were as many for either side in the audit queue. There's a whole list of post about people complaining[1]. Most of the time, the answer is the same: if you are not sure, hit skip.
For most the negatives audits, SO famously used spam rather than bad posts (which also taught the wrong lesson)
https://meta.stackoverflow.com/search?q=%5Bdisputed-review-a...
Doesn't have to be yours, just anyone that you've seen.
It got grossly misapplied because it became "look at any answer, if one of the answers it the same, then they are duplicate". Note how likeness became overlap and likelyhood became certainty. Two questions where restart might solve the problem became duplicates under that absurd policy. Your example on the other hand I didn't find. I didn't find anyone claiming that two questions are duplicate of one another in different programming languages unless the language is not relevant.
Also, the linux kernel assigns CVE for anything that can be though as a vulnerability:
> Note, due to the layer at which the Linux kernel is in a system, almost any bug might be exploitable to compromise the security of the kernel, but the possibility of exploitation is often not evident when the bug is fixed. Because of this, the CVE assignment team is overly cautious and assign CVE numbers to any bugfix that they identify. This explains the seemingly large number of CVEs that are issued by the Linux kernel team
In other words, the number is fake