Elon's rhetoric doesn't really match the model's behavior. It is willing to criticize Elon and argues against many of the insane right way points he tries to make.
The gulf is bridgeable. The problem is that a lot of people are building agents without strong enough judgment layers around them. Work that can be verified with reasonable accuracy are the sweet spot right now.
No need to be defensive. If you ask an epidemiologist, they would almost certainly agree that it is essentially a marker of sexual activity at this point. It is transmissible even with condoms, it has many strains, it is widely prevalent, and the WHO states that basically everyone is sexual active will get one strain. Guardrail prevents against 9 - the ones we were able to create vaccines for and we know have negative effects.
There's also not really great tests for it, so you do not know if you have it or not.
You realize that the companies listed employ many of the core open source maintainers for large projects? It is project-specific, but 80% of Linux kernel development is from paid corporate employees. Similar for kubernetes. All the load bearing infrastructure is already handled by these companies... literally no one else is going to have the resources or experience to redirect large efforts on securing F/OSS.
For some reason not really talked about in mainstream medicine for straight men. It makes no sense. Very safe vaccine and you're eligible into your 40's to get it. Everyone sexually active probably has some strains but not all.
How can an agent use these tokens then? If it sources the file can't it just read the env?
It also sounds like it is missing the important step of keeping the LLM credentials from the agents themselves. For example my GCP creds have access to far more than Vertex. This is solved by OneCLI and OpenShell via MITM proxies which seems more elegant to me. The tools live in containers and can't see anything but can use everything.
It also allows finer grained access controls, rating limiting, and there's talk of scanning for destructive actions.
"Review" them how? Read every single line of code before installing something? If it's a binary package, how do you do that? Make reproducible builds for everything you install? Move to from source distro? Putting this on users is not a tenable solution. There's room for common sense, but blaming the users for this is ridiculous
The fallback doesn't seem to be working for me, I haven't scanned a project in it immediately booted me when it found a security bug even though I didn't ask for it
It hasn't changed, and I don't know why people are saying that most books don't have DRM. It is only a small minority.
Tor books is the largest publisher without it (owned by Macmillan). Otherwise everything is truly hard DRM either ACSM with epub or Kindle's. They are both more or less easily defeated though.
I am not sure anyone knows what a harness is at this point. I've heard 17 different definitions of it at this point. It's almost like a buzzword in search of a problem.