Let Tom Hiddleston be your guide to Pompeii's final day
NatGeo's Pompeii: Out of Time fuses historical fact and imagination to bring city's last 24 hours to life.
找到 25 篇相关文章
NatGeo's Pompeii: Out of Time fuses historical fact and imagination to bring city's last 24 hours to life.
The company didn't say how many are in each city and has taken a far more cautious approach to scaling the network than CEO Elon Musk had promised.
The recall comes as the top automotive safety regulator in the U.S. has warned AV companies about their vehicles interfering with first responders.
Originally published on tamiz.pro . Introduction Over-the-air (OTA) updates are a critical component of modern software ecosystems, yet they introduce complexity through network instability, device fragmentation, and rollback challenges. Meanwhile, AI agents are emerging as powerful tools for autonomous workflow orchestration. This article explores how to architect resilient developer workflows by integrating AI-driven decision-making with OTA update management systems. The Chaos of OTA Updates OTA updates face three primary challenges: Unreliable Network Context : Mobile devices frequently lose connectivity during updates Device State Fragmentation : Managing compatibility across 1000+ device configurations Rollback Complexity : Traditional systems lack real-time failure detection Traditional solutions rely on retries and checksum validation, but these fail to address root causes like partial updates on low-memory devices or race conditions during state transitions. AI Agent Innovation Framework AI agents introduce three transformative capabilities: Predictive Update Scheduling # Pseudocode for AI-driven update scheduling agent . observe ( network_quality , battery_level , device_usage ) recommendation = neural_net . predict ( update_success_probability ) if recommendation . confidence > 0.9 : schedule_update () elif recommendation . alternative : queue_deferred_update () Dynamic Rollback Orchestration AI agents can implement context-aware rollback strategies: Immediate rollback for critical OS failures Graceful deferral for non-essential app updates Predictive rollback based on anomaly detection in system metrics Device State Pattern Recognition Machine learning models analyze historical update data to: Predict failure patterns across device models Optimize binary delivery sequencing Automatically generate compatibility matrices Architectural Implementation A resilient workflow combines: graph TD A[OTA Coordinator] --> B[AI Agent Orchestration Layer] B --> C[Updat
In the wake of a massive hours-long gridlock event, San Francisco mayor Daniel Lurie has told state regulators it's time to put more requirements on robotaxi operators like Waymo.
Toyota's everyday small SUV should rarely require trips to the gas station.
By keeping the number of investments to about 25 per fund, Greylock aims to remain what it calls "the most important partner" to its founders.
As the US war on Iran sent gas prices soaring, American car buyers flocked to electric vehicles - and in particular hybrids. After a sluggish winter and fall, EV sales rebounded in the second quarter of 2026, with automakers posting some of their best numbers since the elimination of the federal EV tax credit last […]
Washington D.C. has become a battleground for Uber and Waymo's competing views.
You set up Puppeteer, navigate to a page, call page.screenshot() , and the bottom half of your image is blank placeholder boxes. Welcome to lazy loading. Most modern sites defer images and heavy content until the user scrolls. Your headless browser never scrolls. So those elements never load. Here's how to deal with it. The scroll trick The most common fix is to programmatically scroll down the page before taking the screenshot: async function scrollToBottom ( page ) { await page . evaluate ( async () => { const delay = ms => new Promise ( r => setTimeout ( r , ms )); const distance = 300 ; while ( window . scrollY + window . innerHeight < document . body . scrollHeight ) { window . scrollBy ( 0 , distance ); await delay ( 150 ); } window . scrollTo ( 0 , 0 ); }); } await page . goto ( " https://example.com " , { waitUntil : " networkidle2 " }); await scrollToBottom ( page ); await page . waitForTimeout ( 1000 ); await page . screenshot ({ fullPage : true }); The 150ms delay between scrolls gives IntersectionObserver -based lazy loaders time to trigger. Too fast and you'll scroll past elements before they start loading. That final waitForTimeout after scrolling back to top lets any remaining images finish rendering. Not elegant, but necessary. Why networkidle2 isn't enough You'd think waitUntil: "networkidle2" would handle this. It waits until there are no more than 2 network connections for 500ms. But lazy-loaded images haven't even been requested yet at that point — they're waiting for a scroll event that never happens. networkidle2 only helps with content that loads on page init. For scroll-triggered content, you need the scroll. The loading="eager" override Some sites use the native loading="lazy" attribute. You can override it before images load: await page . evaluateOnNewDocument (() => { Object . defineProperty ( HTMLImageElement . prototype , " loading " , { set : function ( val ) { this . setAttribute ( " loading " , " eager " ); }, get : function () { retu
Anthropic Shipped @claude for Slack. My Team Runs on Telegram. Anthropic just shipped @Claude inside Slack channels. Tag the bot, it reads the thread, does work async, posts back. Nice product. Except roughly 95% of small businesses don't live in Slack — they run on WhatsApp, Telegram, and Gmail. If you're a solopreneur or a 1-to-10-person team, here's the exact four-part recipe I use to run the same pattern in Telegram for under $12/month. What Anthropic actually shipped (and who it's for) Anthropic shipped an enterprise distribution deal wearing a product launch t-shirt. @Claude for Slack lets you tag the bot in a channel or thread, gives it channel memory, connects to your other apps, and returns work asynchronously — but only on Slack Team and Enterprise plans. That's the punchline: it lives where the annual contracts live. Look at the raw user counts. Slack's own reporting puts it around 35–40 million weekly active users globally. WhatsApp is over 2 billion. Telegram is over 900 million. Gmail sits around 1.8 billion. In the 1-to-10-employee segment outside US tech, Slack penetration is single digits. Small teams in Europe, LATAM, and most of Asia coordinate in WhatsApp groups and run pipeline out of Gmail. They are not about to add Slack seats at $15/user/month just to get an @Claude mention. That's a rational call for Anthropic — Slack is where the enterprise procurement motion already exists. It's just not a product for the operator segment. And the pattern they productized is trivially replicable on any messenger with a bot API. Platform Weekly/monthly active users Bot API Cost to run a mention-bot Slack ~35–40M WAU Yes, paid plan $15/user/mo + API Telegram ~900M MAU Yes, free ~$5–12/mo API only WhatsApp Business ~2B MAU Yes, metered $0.005–0.08/conversation + API Gmail ~1.8B MAU Pub/Sub push Free tier + API The four-part recipe (works in any messenger) Every mention-bot is the same four moving parts: a webhook that fires on mention, a context store that ho
The National Highway Traffic Safety Administration said emergency scenes are not "edge cases."
The robotaxi stopped, called 911, and waited for the San Mateo Police to show up.
Early-stage firm Magnify Ventures has raised a $46.6 million Fund II from LPs including Melinda French Gates’ Pivotal Ventures
The company may finally be ready to try to deliver on Elon Musk's years-long promise of launching a robotaxi network of its own.
Aseon Labs, which came out of Y Combinator's 2026 spring cohort, has raised $10 million from Crane Venture Partners and others.
The Department of Transportation wants to remove the brake-pedal requirement for vehicles "designed to be driven exclusively by automated driving systems."
The new Zoox robotaxi has more cushioning, lighter colors, and a better microphone and speaker for communicating with Zoox Support.
Although it's on the smaller side, this electric vehicle is not very chill.
The company has identified at least 13 instances where its robotaxis drove into highway sections closed for construction.