Source post on hold: for reference
The entire post was about hardening Chrome, referencing vulnerabilities, and offering solutions.
He does not believe hardening chrome against the latest TLS_RSA, CBC & QUIC vulnerabilities has to do with security, as noted in the image below.
He said my post looks like a duplicate of an 5 year old security post about RC4 ciphers. The commandline in the post no longer works with chrome. Developers have since changed the code. This was the original reason I posted. Cipher names were no longer working. They removed a zero from some of them, others they left alone. It no longer lines up with the standard on SSL-Labs. Information rectifying this is relatively new and sparse. I received the appropriate answer on wilderssecurity and shared it here... after posting my answer, schroeder mod suggested I delete the post, claiming I had merely misspelled the code. However, its relevant code and not widely available and important for users concerned about their online security, unlike the link he linked which provided outdated inoperable code.
One of the answers includes working with Chrome developers to implement better in-browser cipher selection functionality, the only approach to the roadblock of limited, poorly writ security functionality. He says that is not relevant.
Elsewhere he claims
"You are mixing up "what cipher suites should be disabled?" with "how do I disable cipher suites in a certain product?"
How confusing can you get. Nowhere did I ask what ciphers should be disabled, I asked how to disable them.
For the owners of this site please take appropriate action to ensure moderators do not abuse their power on here.