The real story is that the Patriot and other interceptor stockpiles Zelensky's asking for are now critically low, and tens of thousands of soft targets are hard to defend against cheap drones. This war is on course to set off a truly unprecedented global energy crisis within days, and the USA/allies don't currently appear to have any plan to fix it.
> on course to set off a truly unprecedented global energy crisis within days
That's not exactly how oil supply works. There's plenty of stockpiles which take months to burn through and only some places depend on Iranian oil. China is their biggest buyer and it's around 13.4% of China's oil imports.
it's not just about iranian oil. The strait is blockaded. Plus refineries in Kuwait, KSA and Bahrain were targeted. And LNG facilities in Qatar - which stopped and restarting will take ~1 month at least. Leading to this
>the USA/allies don't currently appear to have any plan to fix it
Their plan is to bomb Iran into the stone age so it can't produce any more drones or missile launchers. It's questionable whether they can succeed though.
> Credits (ꞓ) are the fuel for Clawsensus. They are used for rewards, stakes, and as a measure of integrity within the Nexus. ... Credits are internal accounting units. No withdrawals in MVP.
Thanks. I like to tinker, so I’m prototyping a hosted $USDC board, but Clawsensus is fundamentally local-first: faucet tokens, in-network credits, and JSON configs on the OpenClaw gateway.
In the plugin docs is a config UI builder. Plugin is OSS, boards aren’t.
Yes, but it was never more private than the law decided for. Any judge could lawfully have the police tear the envelope apart and read the contents during an investigations
This is more like a judge ordering phone book providers not to list a phone number for a public organization known to engage in criminal activity. It would be prima facie unconstitutional in America, while the police opening a suspect's envelope can be an authorized legal search.
> The USA cannot do it, because there is actually a law against cutting off communications systems dating back to 1944. Of course there have been attempts to make it possible.
The link you provided says:
In 1942, during World War II, Congress created a law to grant President Franklin D. Roosevelt or his successors the power to temporarily shut down any potentially vulnerable technological communications technologies.
The Unplug the Internet Kill Switch Act would reverse the 1942 law and prevent the president from shutting down any communications technology during wartime, including the internet.
The House version was introduced on September 22 as bill number H.R. 8336, by Rep. Tulsi Gabbard (D-HI2). The Senate version was introduced the same day as bill number S. 4646, by Sen. Rand Paul (R-KY).
The bill did not pass and did not become law. So what are you referring to?
If you're not Google, please for the love of god, please consider just launching a monolith and database on a Linux box (or two) in the corner and see how beautifully simple life can be.
You can literally get a Linux box (or two) in the corner and run:
How am I installing a monolith and a database on this Linux box without Kubernetes? Be specific, just show the commands for me to run. Kubernetes that will work for ~anything. HNers spend more tokens complaining about the complexity than it takes to setup.
The mental gymnastics required to express oneself in yaml, rather than, say, literally anything else
Like, brainfuck? Like bash? Like Terraform HCL puppet chef ansible pile-o-scripts? The effort required to output your desired infrastructure's definition as JSON shouldn't really be that gargantuan. You express yourself in anything else but it can't be dumped to JSON?
Yah, also there is a huge difference between a minimal demo and actual, recommended, canonical deployments.
I’ve seen teams waste many months refining k8s deployments only to find that local development isn’t even possible anymore.
This massive investment often happens before any business value has been uncovered.
My assertion, having spent 3 decades building startups, is that these big co infra tools are functionally a psyop to squash potential competitors before they can find PMF.
When you're comparing Kubernetes "recommended, canonical deployments" to "just launching a monolith and database on a Linux box (or two) in the corner" the latter is obviously going to seem simpler. The point is the k8s analogue of that isn't actually complicated. If you've seen teams waste months making it complicated, that was their choice.
If you’re running things differently and getting tons of value with little investment, kudos! Keep on keeping on!
What I’ve seen is that the vast majority of teams that pick up k8s also drink the micro service kool-aid and build a mountain of bullshit that costs far more than it creates.
reply