Never used T-Mobile, yet the last T-Mobile breach, I received a postcard from them offering me credit security services because they leaked my information. Turns out that data was from the early 2000's when cell phone store employee checked to see what services I can apply for... WTF!
"Boudin's Bakery" is this the one where their Sourdough Starter, over 150 years old, is so valuable that it is taken from store to store in a Armored Van?
I am certain AMD like most responsible vendors (Seagate) also worked with Apple to correct the issue. Nvidia's issue was that it told all of the laptop vendors to just deal with it. It's why they are hated by other vendors and AMD/Intel worked hard to keep them from creating x86 cpus.
The issue is that Zoom continues to keep the mic open after you quit the App. They blamed it on a bug and said it was fixed in a new version but it's still happening! This is why doing this in the browser would be better or even adding an App Firewall like OverSight to block access to the external devices.
Objective-See has a utility to do this called OverSight. It's a firewall for your webcams and mics. BUT do not mention this in the Zoom forums as it will be taken down.
MacOS (Certified Unix OS) is bundled with multiple OpenSource projects since it's initial OS X release, just like many other *nix OSes. It's so easy to install your own version and override it that this is not an issue. Simple response... use brew.
PSA: don't use brew to manage your development python, unless you like having the carpet pulled out from under you by brew deciding to change 3.8 to 3.9 on you.
Use brew to install pyenv (or bootstrap it from github). Use pyenv to manage python versions, and then use a virtualenv.
Yes, this is what I do now and since moving to pyenv I haven't had any real issues. The only glitch was that I have to upgrade pyenv from 2.2.3 to 2.2.4 and it just tells me 2.2.4 is already installed when I'm running 2.2.3. I'm guessing that's a homebrew thing?
There's a bunch of places that can still get tripped up:
- scripts with `#!/usr/bin/python` instead of `#!/usr/bin/env python`
- shell scripts which call /usr/bin/python directly instead of the one in your path
- shell scripts which intentionally set a prefix in $PATH to some vendor directory with a custom python, but the vendoring is incomplete and leaky and it implicitly loads packages from your system python anyway
plus a hojillion other things I'm not thinking of...
you should absolutely avoid overriding the default python installation if you're on a distribution that ships python2 by default in particular, because that is a good way to kill a good chunk of your system.
Everyone should depend on “python3” or “python2”, never just “python”. They aren’t really the same language. python3 can’t run python2 scripts, nor vice versa, so no matter what you expected there will be systems on which you won’t get it.
Nothing. NVidia still has it's ARM license and as long as they are kept out of the x86 chip business (thanks to Intel and AMD) they are happy to renew the license with ARM.
