@Nick86 It's been broken for two and a half years, just not broken enough for you to realise, apparently. It's not getting fixed, it was never going to get fixed, and the new reader is superior and actually worthy of continued development.
The legacy reader puts more load on our site, is incompatible with the API, can't properly use MD
@H, has no way to recover from failed image loads, uses more screen real estate for options, and as of yesterday is literally incompatible with the new site infrastructure. You've had two and a half years to explain what's wrong with the default reader, and many people did, which is why it's been updated constantly over said two and a half years.
Instead you're in this thread complaining about websites not working properly when you nuke all your cookies constantly.