A certain business I own has an openai account for testing and research purposes.
What ID would we provide?
Would we pick some random employee to attach to the account?
What relevance does this have to the notion of “piercing the corporate veil” if a business account is tied to someone’s drivers license?
I place the blame for this situation squarely on the careless and thoughtless user population who have blindly provided their phone numbers and now ID scans to any old random, fly by night, start up who request them.
"If you’d like to turn these features off, open about:config in the Firefox address bar, search for browser.ml.enable, set it to false, and that should disable everything."
This is nice to know but in future versions of Firefox that single config switch (browser.ml.enable) will both change names and split into multiple sub-switches, most likely appearing in different pages of about:config.
These sub-switches will then not remain consistent.
It's already not true. I had browser.ml.enable and browser.ml.chat.enabled set to false but I was still getting an option to ask an AI Chatbot about stuff in my right-click context menu. I had to also set browser.ml.chat.menu to false.
Also pick a lane mozilla. Either use "enable" or "enabled", don't use both.
The SCSI would probably be meant for a CD-ROM drive. I recall my Sound Blaster Pro had a proprietary Panasonic CD-ROM interface, and at the time, soundcards often came bundled with a CD-ROM drive ( or is that vice-versa?).
This may be true, but you will now have a single lobe of your liver instead of the two lobes that most people have. Your ability to survive a liver injury will be diminished for that reason.
Further, unless things have changed I believe you will also lose your gallbladder as a result of donating a liver lobe.
I believe he is referring to femtocells which have (are ?) given freely to end users who need cellular signal boosting, etc.
Many of these femtocells, historically, could be trivially altered or updated to participate as literal peers on SS7.
I haven't looked into this for many years but there was a time when operating a certain femtocell granted the owner an enormous amount of leverage on the global telecom network ...
... it is distressingly common for Amazon sellers to resell used and/or refurbished drives as brand new.
We generally source drives in much larger quantities from specific suppliers we have relationships with.
However, once in a while we are forced to look at what can be quickly or easily sourced from Amazon and it is only with the utmost caution that we do so.
As can be seen in the link above, sometimes our proofing process reveals bad actors.
"If a global pandemic and a global trade war can't stop the market, seems like nothing will."
What will stop the market is the sudden realization (among retirees and near-retirees) that all of this AI bubble talk is relevant to their interests because their equity index exposure is actually 1/3 mag7 exposure.
They will, correctly, decide it is time to reduce equity exposure (possibly to zero, depending on age and situation).
This is, potentially, a recipe for a very abrupt and disorderly rush for the exit.
I envy you having written this, because I've wanted to do the same. I'm the adhoc IT guy / CISO / etc. for a small medical practice. I have to jump through the PCI hoops quarterly because it's an ancient junk relic of a time where Infinite Trust Networking and monthly forced password rotation were en vogue.
And why do I have to do PCI stuff? Because we have a credit card scanner that patients use to pay for things. In any sane world, compliance would be on the manufacturer of the scanner: "hey, make devices that actually, you know, encrypt stuff reliably". But since we don't live in that world, I have to have a separate Ethernet drop to the card scanner, which plugs into its own dedicated port on the firewall, which completely segregates it from the rest of the LAN traffic. That isn't horrible in concept, but why? Our servers which store PHI don't have those stringent requirements, because the servers are secured. They don't have to trust that the network is kind and gentle, because they're designed with the idea that it's not. But not so the credit card scanner!
For extra fun, we also have to pay someone to run a PCI compliance scan against our external IP. Said IP listens on exactly one port: the one that doctors use to VPN into the office so that they can check their schedule from home. We got a failing score one year because the VPN appliance supported — not required, but supported — some less-than-perfect crypto algorithm. None of our clients were configured to use those protocols. I know. I configured them. But because the server supported them, we were temporarily[0] judged to be noncompliant because some attacker could, I don't know, hack in and pivot in to the firewall appliance and from their pivot to attack the poor downtrodden credit card scanner which, of course, can't be expected to defend itself from the hostile environment of doctor's office LAN.
PCI's a joke.
[0]It would be against the scanner's ToS to temporarily block that port in our inbound firewall long enough to get them to shut up about it, so I totally did not do that.
It works everywhere.
reply