Even if the prospective investors smell a rat, they might decide that it's likely that a greater fool will arrive on the scene later - justifying investing in a known scam
Every layer of the organization tells a more rosy version of the truth up the chain of command. The programmer might tell the PM that they're running Apache software with the serials filed off, but by the time that filters up the chain to the CEO / Board, the product is "fully proprietary and 100% built in-house"
The very first Apollo attempt killed three astronauts. We would need something different now because the cold-war-crazy days are behind us, and we don't push ahead with missions that might end up in casualties.
We do push ahead with missions that might end up in casualties. It's just a matter of risk tolerance.
It's impossible to say a space flight mission has 0% chance of casualty. It might be impossible to say that for virtually any activity involving humans.
That also means sending every user a copy of the model that you spend billions training. The current model (running the models at the vendor side) makes it much easier to protect that investment
I have used 1Blocker for years and it has worked great. There are many others all using the same principle. It also allows me to have a custom rule to disable JS entirely on some sites.
Same, and I can't put my finger on the "why" either. Plus I keep hitting guard rails for the strangest reasons, like telling codex "Add code signing to this build pipeline, use the pipeline at ~/myotherproject as reference" and codex tells me "You should not copy other people's code signing keys, I can't help you with this"
reply