OpenAI built a custom WebRTC architecture to deliver voice AI to 900 million weekly users by splitting packet routing into a stateless relay layer and a stateful transceiver layer, avoiding Kubernetes deployment issues with port exhaustion and state stickiness. The system encodes routing metadata into the ICE ufrag field to route the first packet correctly without database lookups, then uses a geographically distributed relay fleet to minimize latency. The architecture serves one-to-one conversations between users and AI models more efficiently than standard SFU (Selective Forwarding Unit) approaches used for multiparty calls.
The White House accelerated discussions on voluntary standards for frontier AI model releases, with OpenAI, Anthropic, Google, and national-security agencies negotiating benchmarks and gates for advanced models. OpenAI reportedly proposed giving the U.S. government a 5% stake in the company, potentially worth tens of billions of dollars, as a way to share AI's upside and smooth regulatory relations. If formalized, such public ownership could reshape how AI labs balance regulatory compliance, public trust, and capital markets expectations as they approach trillion-dollar valuations.
OpenAI proposed giving the U.S. government a 5% stake in the company as part of discussions with the Trump administration to address political pressure over AI development and security concerns. The stake would be worth approximately $42.6 billion based on OpenAI's $852 billion valuation from its March funding round. The arrangement would potentially extend to other major U.S. AI developers like Anthropic, Google, and Meta ceding similar stakes through a government sovereign wealth fund vehicle, though it remains unclear whether these companies would agree.
Every AI story that matters,
in your inbox by 8am.
TLDRocket reads all relevant sources, removes duplicate coverage, and summarises the
day in two minutes. Follow companies and topics for alerts, or get the
briefing in Slack. Free, no spam, unsubscribe anytime.
Reading TLDRocket needs no cookies, and the readership counts we rely on come from
our own cookieless analytics. Google Analytics is the exception: it sets cookies and
reports to Google, so it stays switched off until you allow it. You can change your
mind any time from “Cookie settings” in the footer.
Strictly necessary
Session security and form protection (tldrocket-session,
XSRF-TOKEN, 2 hours). The site cannot work without them,
so they need no consent.
Always on
Google Analytics 4 (_ga,
_ga_<id>, up to 2 years). Measures which
stories and sections readers use. Google acts as a third-party processor and may
store the data outside the EU. No advertising, no profiling, no data sold.
