News for hackers. Stuff that matters.
Re:Mitigating MIME Confusion Attacks in Firefox by drdaeman on Friday August 26, 2016 @12:41PM (#12367419)
It's all based on idea that users want sites that are broken beyond repair to still magically work - because user experience.

And that's the story how we stuck with a giant pile of hacks the modern web is.

Re:Mitigating MIME Confusion Attacks in Firefox by gsnedders on Friday August 26, 2016 @12:44PM (#12367452)
Every single browser vendor has exit polling showing websites being broken is one of the top reasons for users changing browser. This isn't some idea, we have solid data that breaking stuff just causes users to move to a browser where the site works.
Re:Mitigating MIME Confusion Attacks in Firefox by jhatax on Friday August 26, 2016 @01:12PM (#12367678)
This.

Most users do not think that their favorite website is broken; the believe the browser is at fault. Therefore, they find a browser that renders said website correctly and stick with it. The problems are manifold, and it's the browser that supports both the standard and many non-standard ways of describing content that wins out: Chrome today; IE before the "second coming of web browsers".

Re:Mitigating MIME Confusion Attacks in Firefox by gsnedders on Friday August 26, 2016 @01:26PM (#12367786)
And if every browser breaks it, you find an old browser that it works with and stick to that forever, which is really bad for everyone.
Re:Mitigating MIME Confusion Attacks in Firefox by drdaeman on Saturday August 27, 2016 @06:26PM (#12374439)
Is this also backed by research?

Because I sort of doubt this. An old browsers become a nuisance quite fast, with "sorry, you need a browser that supports $feature and yours doesn't". Well, I mean, I had to stick with 2 years old browser for some time and this certainly wasn't a good UX.

Re:Mitigating MIME Confusion Attacks in Firefox by drdaeman on Saturday August 27, 2016 @09:43AM (#12372311)
Of course, it's true. Yet, I hope, no one would argue this is also exactly how we ended up with a giant pile of hacks. ;)

The only solution I can think of is a cartel-like agreements between all major browser vendors, on issue-per-issue basis, when they decide they want a sane tech and for the sake of it won't compete on certain compatibility points. Which is quite unlikely.