If I'm understanding correctly, the post isn't calling TLS broken, it's calling out the bad behavior of browsers. By employing mitigations/workarounds, they en

If I'm understanding correctly, the post isn't calling TLS broken, it's calling out the bad behavior of browsers. By employing mitigations/workarounds, they encourage misconfigured servers, and that in turn produces unexpected or inconsistent behaviors when interacting with those servers through different client types. eg you might see different behavior in FF vs Chrome, or Chrome vs curl/python, etc.