RealFloridaMan
There’s nothing indicating Anthropic was not keeping their end of the contract. If they had, there would have been other recourse.
This is like the change order from hell.
Nothing was stopping the DOD from just entering into a new contract with OpenAI…
Let me ask you this, if Anthropic did allow them to use it for surveillance… do you think it would stop at the Pentagon?
They could’ve just negotiate a new contract with OpenAI, without banning it from every government agency. But I’m sure that would’ve triggered some kind of extra clause and cost money…
Your entire statement lacks any type of fact.
The analogy would be: “A customer agreed to a contract, and after running into a clause of the contract they no longer wanted to follow…canceled the contract unilaterally…which also violated the contract.”
To answer your question, you build your datacenters where there is capacity or you plan with the utility in the area you want to build. This process takes years.
They are not doing that. They are building them as fast and as cheaply as possible.
As a result they are cutting corners and are leading to all of the complaints.
They are as a result stealing from the future to make a profit today.
The grid does not have gigawatts of extra base load capacity available as that has always been looked upon as wasteful.
Lemonade is really just a management plane/proxy. It translates ollama/anthropic APIs to OpenAI format for llama.cpp. It runs different backends for sst/tts and image generation. Lets you manage it all in one place.
Under the hood they are both running llama.cpp, but this has specific builds for different GPUs. Not sure if the 9070 is one, I am running it on a 370 and 395 APU.
It also has endpoints that are compatible with OpenAI, Ollama, and Anthropic so you can throw any tool that is compatible with those and it will just run.
It’s portable in the sense it will install on any of the supported OS using CPU or vulkan backends. But it only supports out of the box ROCM builds and AMD NPUs. There is a way to override which llama.cpp version it uses if you want to run it on CUDA, but that adds more overhead to manage.
If you have an AMD machine and want to run local models with minimal headache…it’s really the easiest method.
This runs on my NAS, handles my home assistant setup.
I have a strix halo and another server running various CUDA cards I manage manually by updating to bleeding edge versions of llama.cpp or vllm.
When you are infected with anything, you do not always develop anti-bodies. If you do develop anti-bodies, they might not be effective at actually stopping you from being re-infected.
Everything about the virus can mutate, but the virus will always target the ACE2 binding site. The spike protein can mutate to bind to it differently, but it will always require a spike protein. (Biology is Analog, not digital)
Thus targeting the spike protein is more efficient as it will be highly conserved.
There is a video series that does a nice job of breaking down how your immune response works: https://youtu.be/lXfEK8G8CUI
The vaccine is more effective at developing anti-bodies for the spike protein as it is the only protein exposed during the process.
An analogy that has helped some of my family: The virus is like a missile, and your immune system is a anti-missile system. Regardless of what the missile looks like, it has to have a warhead, and that warhead is what really defines what the entire thing does. So, if your defense systems targets the fuel of the missile, the enemy can change what fuel it runs on and evade your defense system. They can change the material it is made of, the shape of the overall device, change the propulsion and navigation systems…but the warhead can only have minor changes as it has because it it makes too many, it becomes ineffective and is no longer a threat.
Thus, if your defense system targets the warhead none of the other changes matter.