@Wh1t3Rabbit 4 years and *that* performance is not. baby steps implies some level of progress or evolution.
-
-
Replying to @attritionorg
@attritionorg point taken... just trying to see it from a "big company" perspective.1 reply 0 retweets 0 likes -
Replying to @Wh1t3Rabbit
@Wh1t3Rabbit if a company is that "big" and it leads them to something like this, they have "big" problems at the very least2 replies 0 retweets 0 likes -
Replying to @attritionorg
@attritionorg Not defending crApple, but it's cultural; the attorneys prohibit any level of openness for irrational fears, fearing liability1 reply 0 retweets 0 likes -
Replying to @Wh1t3Rabbit
@Wh1t3Rabbit shitty culture then. Microsoft does a *much* better job at dialogue with the security community, w/o liability.2 replies 1 retweet 0 likes -
Replying to @attritionorg
@attritionorg agreed, but MS was publicly beaten up by public, gov until it catalyzed change... Apple is just now getting beaten up2 replies 0 retweets 0 likes -
Replying to @Wh1t3Rabbit
@Wh1t3Rabbit honestly, it seems like you are pre-apologizing for HP or something1 reply 0 retweets 0 likes -
Replying to @attritionorg
@attritionorg Uhm...no? We have a good relationship with the security researchers community. Nothing to apologize for.2 replies 0 retweets 0 likes -
Replying to @Wh1t3Rabbit
@Wh1t3Rabbit i quit trying after HP didn't fix an XSS in *five years*. i will never report another vuln to them.1 reply 2 retweets 1 like -
Replying to @attritionorg
@attritionorg Are we perfect? Hell no. We empower PM's and product owners to make decisions in a company this size... In general it works.1 reply 0 retweets 0 likes
@Wh1t3Rabbit six months for other companies.... five+ years for HP. that does *not* work. not for me
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.