First Ring Daily 574: Pixeling the Performance

Posted on March 5, 2019 by Brad Sams in First Ring Daily, Podcasts with 3 Comments

On this episode of First Ring Daily, Pixel gets a speed bump, Xbox likes the Durango, and driving went well.

Subscribe: RSS | YouTube | iTunes | Google Play



Tagged with

Join the discussion!

BECOME A THURROTT MEMBER:

Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Register
Comments (3)

3 responses to “First Ring Daily 574: Pixeling the Performance”

  1. luthair

    Paul, I feel like you should try to talk to a security professional as I've heard you make statements which makes me think you're missing background on the security community. I've included a summary below, but since I'm an unknown internet user I'd recommend finding someone unaffiliated (perhaps Leo could connect you with Steve Gibson) that you can trust.


    Google's practices for disclosing vulnerabilities isn't out of line of the security community, though unpatched disclosures are less common today as many researchers opt to participate in bug bounty programs which generally prevent it in return for compensation. The concept of a deadline was something people in the security community came up with after the realization that companies were not taking reported vulnerabilities seriously, they would instead security drag fixes out long periods of time and multiple releases choosing to prioritize features. Its also important to remember that the vulnerability may already being exploited undetected in the wild. A phenomenon that often occurs in security research but also in science or business is that people independently often pursue similar concepts or problems at the same time. An example from the next bit is that problems under the banner of spectre/meltdown were found by multiple independent teams.


    I believe you also made an off the cuff comment that Google delayed spectre/meltdown so they could patch it which isn't correct. On occasion there are vulnerabilities found for which the fix/mitigation can be complicated but more importantly requires the co-ordination of a large number of parties in order to get it to the hands of users. Another example of this would be Dan Kaminsky's discovery of a flaw in DNS which required fixes to different DNS servers as well as actually starting to update key systems running that software.

  2. mesposito2

    The camera performance difference is night and day on the 3XL. For me the camera now shoots immediately, even in the dark.

  3. My Hell baby speaking

    Paul, you have no idea how security issues are dealt with. Please don't pretend you do.

Leave a Reply