I’m an electrical engineer living in Los Angeles, CA.

  • 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle






  • My head canon is that Tony Stark has a superpower: everything he builds works the first time.

    If it’s really complicated, like an entirely new Iron Man suit, then it might malfunction once in an amusing way. Then he tightens a screw and it’s perfect. It never fails outright or bricks itself.

    In my experience, this is not how hardware or software development goes. I want this power so much.






  • The Google system allegedly shares hashes of a ID-number salted with a rotating timestamp over BLE. But it’s also a closed-source binary. Can you or anyone else actually inspect its implementation? Can you really guarantee it doesn’t have even the smallest design flaws?

    This technology is exceptionally dangerous. There is very little difference between these two scenarios:

    • A doctor has identified a COVID patient. Let’s notify everyone who’s spent time with them recently.
    • Secret police have identified a “dissident”. Let’s round up all their close associates.

    It’s voluntary (for now). It’s allegedly secure (for now). But did anyone actually benefit from this complicated system? All I see are downsides.





  • Google is making a system to verify any given user is running a verified browser on a verified OS on verified hardware (TPM).

    The first problem is that only big tech companies will be able to pass any of these verification steps. Say goodbye to your modifiable, community-driven, open source OS or browser.

    The second problem is that the only software they choose to verify well be increasingly restricted. Say goodbye to your ad-blocker, because Google makes the browser and they’re the one selling the ads.

    You can still an unverified browser, I suppose, but websites decide whether to let you in or not. And Google will reduce their ad revenue if they don’t “verify” their users.