I'm stating the obvious, which is that if a feature does not provide quantifiable privacy or security benefits it isn't actually a real privacy or security improvement. Breaking very specific legacy code is a much different thing than fundamentally improving privacy or security.
Conversation
hey, don't call it obvious if the village idiot (that's me!) doesn't understand it ;)
And I still don't see how "it breaks a class of malicious sites" isn't quantifiable. That's simply a false statement, if you ask me.
1
It was trivial to detect Incognito mode, and it's at least as trivial to do it as it was before. The browser project has more attack surface and maintenance burden along with the opportunity cost from taking this approach rather than making real improvements with those resources.
2
As software, Chromium is not more private or more secure. It's slightly more complex and harder to maintain. It's not better positioned than it was before to address this, if they deem it to be something worth properly addressing in a meaningful way.
1
It doesn't break a class of malicious sites. That's a misrepresentation of it. The only thing that it accomplished is a one time adjustment by the adversaries. It only addressed one way this was being detected, and they had the time they needed to adjust. Code is still there.
1
Metric that breaking things for one evil agent for a limited amount of time is worse than letting that actor do what it's doing, including the cost of implementing that mitigation, please.
You're beating around the bush.
1
Incognito is no harder to detect than before. There is no way to present the software as having improved privacy. The adversaries weren't prevented from doing it for any period of time. They weren't even inconvenienced in any substantial way but rather had to update a library.
1
yes, so they had to update a library, and that means the attack didn't work for a period of time. That's quantifiable, and you're acting like it isn't.
You're a proponent of setting goals and measuring success in metrics of goal achievement, but if your declared goal was privacy
2
There was never a point in time where it was prevented. You can't even claim what you're trying to claim because the feature wasn't developed in secret and then launched as a surprise way to temporarily disrupt privacy-invasive code. That would be quite silly, and didn't happen.
1
Then I might have fundamentally misunderstood the point of the mitigation. I thought it was addressing a approach done by a set of websites in the wild, which then couldn't use that approach for a limited duration of time, and hence didn't work. Not "generally", not "forever".1/2
2
There was no period of time where sites could not detect Incognito mode and this change was not a surprise that disrupted anything for anyone paying attention at all. It wasn't something developed behind an embargo and disclosed as part of a release. Not what happened at all.