It's painful, but I've grown distrustful enough of the ecosystem that I disable updates on every IDE plugin not maintained by a company with known-adequate security controls and review the source code of plugin changes before installing updates, typically opting out unless something is broken.
It's unclear to me if the code linked on the plugin's description page is in amy way guaranteed to be the code that the IDE downloads.
The status quo in software distribution is simultaneously convenient, extraordinarily useful, and inescapably fucked.
They exist. Services treat control of the number as equivalent to control of the account, and expect you to maintain that control.
Throwaway phone numbers are not a viable low cost or no cost alternative in most normal user signup scenarios, and they're implemented as a privacy invasive form of spam prevention for that exact reason.
> It’s surprising how something that seems harmless, like a simple recovery page, can actually hide some pretty serious security risks.
This is something you should include in any personal security checkup. Attempt account recovery using every allowed mechanism. The rules for recovery change over time in a way that classical login doesn't.
If the dongle acts as a wifi AP with a DHCP server, it could give the iPhone an ip address but no gateway upon connection. This will cause the iPhone to talk directly to the dongle via the WiFi interface, but talk to the rest of the internet via the cellular connection.
You can determine this by checking the WiFi network's properties after the connection is established. If there's no value in the "Router" field, that's how it works.
Once you load the firmware update page, JavaScript on the page instructs the browser to fetch the firmware payload from a server on the public Internet, then relays that data to the dongle's web server to execute the firmware update process.
As the other reply mentioned, this can be tricky, as CORS likes to prevent this kind of data transfer for security reasons, the right configuration on the web server will make it work.
It's a fairly clever setup.
If you want a low-tech way of confirming this design, try running the firmware update with a device that doesn't have two network connections, like a laptop, instead of a cell phone. If it doesn't work from such a device, the scenario I described above is probably how it works.
To keep with that analogy, customers expect the SaaS company to respond to the HTTP requests for free, but you still have for-profit factories producing servers...
No. I used both of them when migrating from LastPass, and found that Bitwarden only supports four or five types of entries, which ultimately drove me away from the product.
The rich entry types from 1P and LP are nearly all converted to Notes in Bitwarden. Great product otherwise.
Oligarchy. Kleptocracy. Morons cheering because they're deluded enough to believe that the definition of "pork" is when the government transfers money directly to lower and middle class via paychecks.
Congress will authorize contractors to do these jobs instead. We get back privatized versions of the old government services at a higher price, and the money goes into the bank accounts of the rich.
I'd like to read the CBO report on what this shit will actually cost over ten years.
The problem isn't that the owner didn't get the data. The problem is that the method for getting the data is that you must beg Tesla for it, rather than just slurping it out of a USB port inside the car.
If Tesla is going to go to the trouble of uploading all this shit to the cloud anyway, the least they can do is give customers a no-questions-asked download button.
I'd recommend any good sound device that connects digitally, like USB or HDMI/Displayport.
So the answer is that you should get a dedicated sound device, but don't bother looking for an internal card. External devices are easier to connect, won't complicate upgrades, and can be attached to a different machine with less work.
Onboard has always been good enough, it's just that people are usually willing to accept trash.
We've got similar opinions here. I'm just pointing out that the overall experience here feels familiar, and it wasn't until reading this thread that I really put it together.
I agree with you that I'd be surprised if Enshittification works as well here as it does in tech, but maybe since there's an app involved, they just think they can get away with it. Who knows.
They've captured the user base with the money that corporate was pumping into the app deals, and are in the process of enshittifying it by transferring the value to themselves instead of the users.
> The development environment where I'm downloading random libraries is on a completely separate physical machine than my primary computer. I generally spin up a short-lived container for each new coding project, that gets deleted after the resulting code I produce is uploaded somewhere. This is completely separate from the work-supplied machine where I hack on my employer's code.
Something like VS Code remote dev with a container per project? Just plain docker/podman for containers?
> On my primary computer, my web browser runs in an ephemeral container that resets itself each time I shut it down. My password manager runs in a different, isolated, container. Zoom runs in a different, also isolated, container. And so on.
Qubes, or something else? I've been looking at switching to Linux for a while, but Apple Silicon being as good as it is has made making that leap extremely difficult.
It's unclear to me if the code linked on the plugin's description page is in amy way guaranteed to be the code that the IDE downloads.
The status quo in software distribution is simultaneously convenient, extraordinarily useful, and inescapably fucked.