@BRIAN_____ I wish Moz had MSFT engineering strength back then. We did not. We knew about Gazelle then, knew of Chrome by 2006 summer. FWIW.
-
-
Replying to @BrendanEich
@BrendanEich My point is that responsible/coordinated disclosure creates complacency. In Java and Flash & elsewhere too. Not to pick on you!1 reply 0 retweets 0 likes -
Replying to @BRIAN_____
@BRIAN_____ I pick on me all the time, no worries. Your point went further though. Open vuln bugs would have perverse outcomes you left out.2 replies 0 retweets 1 like -
Replying to @BrendanEich
@BrendanEich No doubt there are short-term negative effects. I think, in the end, users would benefit more from full disclosure more.1 reply 0 retweets 0 likes -
Replying to @BRIAN_____
@BRIAN_____ I doubt that knowing how MS bundled fixes & gamed perception system. Besides likely bad hat attacks on Firefox in your scenario.2 replies 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@BRIAN_____ "Gamed perception"? :) For how many years after IE7 shipped did the Firefox download page report IE6 vuln stats?3 replies 0 retweets 0 likes -
Replying to @ericlaw
@ericlaw@BRIAN_____ I don't know, maybe@shaver recalls, but MS bundled fixes to game counts. That I remember. Call the waaaahmbulance! :-P2 replies 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@ericlaw@BRIAN_____ MSFT bundled, and I heard on background from someone at MSFT that the counting aspect was one reason why1 reply 0 retweets 0 likes -
Replying to @shaver
@shaver@BrendanEich@ericlaw Everybody bundles now. Only externally-reported vulns are split out. See https://www.mozilla.org/en-US/security/advisories/mfsa2015-134/ … and Chrome's.2 replies 0 retweets 0 likes -
Replying to @BRIAN_____
@BRIAN_____@shaver@ericlaw Moz didn't bundle *then*, your point actually makes my case: multi-vendor game theory kills open-all-vulns.1 reply 0 retweets 0 likes
@BrendanEich @shaver @ericlaw I wasn't thinking of it from a marketing perspective. More as DoS, as emergency releases are very expensive.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.