Twitter adopted a toxic attitude; if the code/browsers don't fully support some changes it implements, it will just block the 'offending' (usually non-proprietary, non-PRISM) browsers and pretend its the 'user's' fault. As if all the JS spyware there wasn't bad enough...