Zambia has started connecting 751 health facilities across all 10 provinces with Starlink, and the first 90 kits went to Western Province.
There's something poetic about where they started. Every year at the end of the rainy season the upper Zambezi floods the Barotse plain, and for centuries the Lozi king has left his compound at Lealui by royal barge and moved to higher ground at Limulunga. The ceremony is called Kuomboka. In Lozi it means "to get out of water."
Now picture running fiber or building towers across land that turns into a lake for part of every year. A Starlink dish only needs a clear view of the sky, so the water below stops being the problem.
In March 2020, months before Starlink had its first beta users, Elon Musk said it would serve the 3 or 4 percent hardest-to-reach customers, people with no connectivity or really bad connectivity. Six years later, with funding from the Global Fund through Zambia's Ministry of Health, clinics on one of Africa's great floodplains are being brought into the country's electronic health systems from orbit.
“Jensen has been incredibly good at retaining talent. There are very few high-profile departures from the NVIDIA executive team.”
“This is probably when the sharks are in the water. The VCs are going to come in and offer people billions of dollars to start their own chip companies, their own neolabs.”
“If a year from now we’ve seen a bunch of departures from NVIDIA, I’m going to be really concerned about their future.”
“Steve Jobs is a pure visionary, and Jensen is negotiating every supply chain contract.”
“If there’s any manufacturing issues with Rubin, people are distracted and Jensen’s not there. Things get solved slower, things get solved by committees.”
129 people on board and the ship taking on water rapidly is honestly terrifying. A fuel tanker called Atlantic Asphalt hit the American Heritage cruise ship while it was moored on the Mississippi River. Was a power loss on the tanker the real cause? 🚢 👇
Anthropic just published an engineering guide on how to build always-on agents.
The biggest misconception: an always-on agent does NOT run 24/7. It sleeps almost all day, wakes up for short runs, saves state, and goes back to sleep.
The 5 core pieces I distilled:
1. Event Inbox
Put a database table between webhooks and your agent. Acknowledge webhooks fast, run only one active worker per user so runs never collide, and batch rapid messages together.
2. Timers
Keep timers in a separate table from the inbox. Split them into one-off follow-ups and recurring schedules. A background poller drops due timers into the inbox.
3. Lean Memory + Dreaming
Only store what cannot be looked up again: user instructions, user notes, past messages, and task progress. Load a small index at wakeup, not every file. Run periodic dreaming passes to clean out stale facts.
4. Unattended Permissions
Never put raw API keys inside the agent sandbox — inject them through an outside proxy. Use Deferred Tool Calls to pause risky actions for approval without blocking the worker.
5. Outbox
Queue outgoing replies so your agent paces notifications instead of spamming users at 3 AM.
Get a first look at the ideas and conversations coming to #BinanceBlockchainWeek# 2026.
Hear it first from the people building it. Yi He, Eowyn Chen & Jessica Walker go live for the 'Road to Binance Blockchain Week' session.
Set your reminder →