Even as the geopolitical conversation around AI continues to grow more fraught following the U.S. government’s actions to limit the new models from Anthropic and OpenAI, Chinese open source darling DeepSeek is back with yet another open release that could once again change AI development around the globe.
Over the weekend, the firm released DSpark, a new, MIT-Licensed system designed to make large language models answer faster without changing what the underlying model is trying to say.
The easiest way to think about it is this: most AI chatbots write like someone crossing a river one stepping stone at a time. They choose one small chunk of text, then the next, then the next.
DSpark gives the system a scout that runs a few steps ahead, guesses the likely path, and lets the larger model quickly check which steps are safe. When the guesses are good, the model moves faster. When the guesses are weak, DSpark tries not to waste time checking them.
Advertisement
DeepSeek published the work with a technical paper, model checkpoints and DeepSpec, a codebase for training and evaluating speculative decoding systems. The release is available through DeepSeek’s public GitHub and Hugging Face pages, both under the permissive, friendly, commonplace MIT license, making the new technique broadly usable by developers, researchers and commercial enterprise operations that want to study or adapt the approach.
The system is aimed at one of the most expensive problems in AI deployment: serving large models quickly enough for real users, while using hardware efficiently enough to make the economics work. That matters for consumer chatbots, coding assistants, agentic workflows and enterprise AI systems where users expect long answers to stream quickly rather than crawl out word by word.
DeepSeek is applying DSpark to its own latest frontier open model, DeepSeek-V4.
Specifically, DeepSeek used its new DSpark framework on DeepSeek-V4-Flash, its already speed-optimized 284-billion-parameter mixture-of-experts model with 13 billion active parameters, and DeepSeek-V4-Pro, its more thoughtful and powerful 1.6-trillion-parameter model with 49 billion active parameters (Both support context windows up to one million tokens).
Advertisement
But the broader significance is that DSpark is not conceptually limited to DeepSeek-V4. DeepSeek’s own tests and released checkpoints cover other open model families, including Alibaba’s open weights Qwen and Google’s open weights Gemma.
That means enterprise teams running open-weight models could, in principle, train or fine-tune DSpark-style draft modules for their own target models. It is not a switch that any API customer can flip from the outside, but it is a method that can travel to other models when the operator controls the weights and serving stack.
Staggering speed increases for generating tokens during inference
In DeepSeek’s live production tests, DSpark improved aggregate throughput by 51% for DeepSeek-V4-Flash at an 80-token-per-second-per-user service target, and by 52% for DeepSeek-V4-Pro at a 35-token-per-second-per-user target. At matched system capacity, DeepSeek reports per-user generation speedups of 60% to 85% for V4-Flash and 57% to 78% for V4-Pro over its prior MTP-1 production baseline.
The different speed claims measure different things. The 60% to 85% figure for V4-Flash, and the 57% to 78% figure for V4-Pro, describe how much faster individual users receive generated tokens when DeepSeek compares DSpark with MTP-1 at matched practical system capacity.
Advertisement
Credit: DeepSeek, ‘DSpark: Confidence-Scheduled Speculative Decoding with Semi-Autoregressive Generation’
Those are the cleaner “generation speed” numbers. DeepSeek also reports much larger 661% and 406% increases, but these measure aggregate throughput under very strict speed targets: 120 tokens per second per user for V4-Flash and 50 tokens per second per user for V4-Pro.
At those targets, DeepSeek says its older MTP-1 baseline approaches an operational cliff, meaning it can keep only a small number of concurrent requests running while preserving that level of responsiveness.
DSpark avoids more of that collapse, so the percentage difference in total system output becomes much larger. Put simply: the 85% number is closer to “how much faster the ride feels for a user” under comparable conditions, while the 661% and 406% figures are closer to “how much more traffic the road can still carry” when the old system is already bottlenecking.
Advertisement
Why speculative decoding matters
LLMs usually generate text one token at a time. A token can be a word, part of a word, punctuation mark or other small piece of text. Every new token depends on the text already produced, so the model has to keep pausing, checking the full context and choosing the next piece.
That is accurate, but slow. It is like having a senior editor approve every word before a writer can move to the next one. The editor may be excellent, but the process creates a bottleneck.
Speculative decoding, developed in the early Transfomer era, tries to fix that bottleneck. Instead of asking the large model to produce every token one by one, the system uses a smaller or lighter draft component to suggest several likely next tokens. The large model then checks that batch of guesses in parallel. If the draft guessed correctly, the system moves ahead several tokens at once. If the draft made a bad guess, the system rejects the bad token and anything after it, adds a corrected token, and tries again.
The point is speed without changing the larger model’s intended output. In the standard speculative decoding setup, the draft model is not replacing the target model. It is acting more like an assistant who prepares a rough next sentence for the senior editor to approve or reject.
Advertisement
The idea did not appear out of nowhere with today’s large language models. A key precursor came in 2018, when Mitchell Stern, Noam Shazeer and Jakob Uszkoreit proposed blockwise parallel decoding for deep autoregressive models. Their method predicted multiple future steps in parallel, then kept the longest prefix validated by the main model. That paper established much of the draft-and-check intuition behind later speculative decoding work.
Those 2022 and 2023 papers are the clearest ancestors of how speculative decoding is discussed in current LLM inference work: a faster draft process proposes tokens, and the larger target model verifies them in a way designed to preserve the target model’s output distribution.
Since then, the field has moved quickly through several variants, including separate draft models, multi-token prediction heads, tree-based verification, feature-level methods such as EAGLE, self-speculation, Medusa-style extra heads and parallel/blockwise drafters such as DFlash.
Advertisement
The key metric is not how many tokens a draft model can guess. It is how many of those guesses the larger model actually accepts. Long speculative blocks help only if enough of the proposed tokens survive verification. Otherwise, the system spends compute checking guesses that it throws away.
That is the context for DSpark. Speculative decoding is already an established inference technique before DeepSeek’s release, with support in major serving stacks and multiple competing research approaches. But it is still not a solved problem. Speedups depend heavily on the draft model, the workload, the serving setup and the current traffic level. DSpark’s contribution is to improve both sides of the trade-off: it tries to draft more coherent token blocks and then verify only the parts of those blocks that are likely to pay off under real serving conditions.
What DSpark changes
DSpark tackles two related problems: bad guesses and wasted checking.
First, the system uses what DeepSeek calls semi-autoregressive generation. In plain English, that means DSpark tries to combine speed with a bit more awareness of sequence.
Advertisement
A fully parallel drafter can guess several tokens at once, which is fast, but its later guesses can become less coherent because each position is predicted too independently. A purely step-by-step drafter can keep better track of how one token leads to the next, but it loses much of the speed advantage.
DSpark tries to keep the best of both. It uses a parallel backbone for most of the drafting work, then adds a lightweight sequential head that lets the draft take nearby token relationships into account. In the paper’s example, a parallel drafter might confuse likely phrase endings such as “of course” and “no problem,” producing awkward combinations because it is guessing positions too separately. DSpark’s sequential component helps the system make the later tokens fit the earlier ones.
Second, DSpark adds confidence-scheduled verification. Rather than always asking the target model to check the same number of draft tokens, DSpark estimates which prefix of the draft is likely to survive. A hardware-aware scheduler then adjusts how much of each draft should be verified based on both model confidence and current serving load.
A simple analogy: when a restaurant is quiet, the head chef can inspect more of the prep cook’s work. When the kitchen is slammed, the chef spends attention only on the dishes most likely to be ready. DSpark applies a similar idea to AI serving. Under lighter traffic, the system can afford to check longer draft prefixes. Under heavier traffic, it trims low-confidence trailing guesses before they consume batch capacity that could be used for other users.
Advertisement
DeepSeek frames this as an answer to a common production trade-off. Static multi-token drafting can look attractive in isolation, but can hurt throughput under high concurrency because the system keeps checking tokens that are likely to be rejected. DSpark’s scheduler makes the verification budget flexible instead of fixed.
Offline results: better draft acceptance across Qwen and Gemma
DeepSeek tested DSpark offline on Qwen3-4B, Qwen3-8B, Qwen3-14B and Gemma4-12B target models across math, coding and chat benchmarks.
In those tests, the team compared DSpark with DFlash, a parallel drafter, and Eagle3, an autoregressive drafter. The paper reports accepted length per decoding round, a measure of how many tokens survive verification on average.
DSpark model speed improvement over Eagle3 and DFlash on Qwen3-4B, Qwen3-8B, Qwen3-14B, and Gemma4-12B. Credit: DeepSeek, ‘DSpark: Confidence-Scheduled Speculative Decoding with Semi-Autoregressive Generation’
Advertisement
Across the three Qwen3 model sizes, DSpark improved macro-average accepted length over Eagle3 by 30.9%, 26.7% and 30.0%, respectively. Compared with DFlash, it improved accepted length by 16.3%, 18.4% and 18.3%. The paper also says the gains generalized to Gemma4-12B.
That supports a point raised by developer Daniel Han, who highlighted on X that DeepSeek showed DSpark working beyond DeepSeek’s own V4 models, including Gemma and Qwen. I would include Han as community reaction, not as the sole evidence for the claim. The stronger support comes from DeepSeek’s own benchmarks and released checkpoints.
The offline results also show why workload matters. Structured tasks such as math and code tend to have higher accepted lengths than open-ended chat. That makes intuitive sense: a code completion or math step often has fewer reasonable next moves than a free-form conversation.
For enterprises, this means DSpark-style methods may be especially attractive for coding assistants, data analysis agents, structured workflow automation and other settings where outputs follow more predictable patterns.
Advertisement
How enterprises could use DSpark without DeepSeek-V4
One of the most important questions is whether DSpark is a DeepSeek-only optimization or a broader method that can be applied to other models. The answer is: broader method, but not automatic plug-in.
For open-weight models, the path is relatively clear. An enterprise running Qwen, Gemma, Llama, Mistral, Granite, Command-style open weights or another model it hosts itself could train or fine-tune a DSpark-style draft module against that target model.
The team would then measure acceptance on its own workloads and integrate the verification scheduler into its inference stack.
That is different from simply downloading DeepSeek’s DSpark module and attaching it to any model. Speculative decoding depends on alignment between the draft module and the target model. The draft has to learn what the target model is likely to accept. A drafter trained for DeepSeek-V4 will not automatically be the right drafter for a different model, especially one fine-tuned on a company’s internal data or configured for different reasoning behavior.
Advertisement
DeepSpec’s workflow reflects this. The process involves preparing data, regenerating target-model answers, building a target cache, training the draft model and evaluating speculative-decoding acceptance. For domain-specific use, the draft model may need additional fine-tuning, especially if the target model runs in a thinking or reasoning mode.
For proprietary models, the answer depends on what the enterprise controls. If a company owns or fully hosts the model weights and serving stack, it could theoretically train and deploy a DSpark-style drafter. If the model is available only through a hosted API from a vendor, the customer cannot directly add DSpark from the outside. The API provider could implement a similar optimization internally, but the customer generally cannot access the token verification loop, logits, batching behavior or serving scheduler needed to make DSpark work.
That distinction matters for enterprise buyers. DSpark strengthens the case for open or self-hosted AI infrastructure because it gives advanced teams another lever to improve speed and cost. But it also shows why model serving is becoming a specialized discipline. The value is not just in picking a model, but in how intelligently that model is run.
What developers get from DeepSpec
For developers, DeepSpec gives a concrete implementation path for training and evaluating speculative decoding draft models. It includes data preparation, training and benchmark evaluation steps, along with released checkpoints for several open model families. That makes the release useful not only for running DeepSeek-V4 with DSpark, but also for researchers and infrastructure teams studying how to add faster decoding to other open models.
Advertisement
There are real deployment caveats. DeepSpec’s own README says the default Qwen3-4B data preparation setup can require roughly 38 TB of target cache storage, and the default scripts assume a single node with eight GPUs. That makes the release more immediately relevant to AI labs, cloud teams and sophisticated enterprise AI infrastructure groups than to ordinary application developers.
Still, releasing the training pipeline matters. Many inference optimizations appear only as papers, vague benchmarks or closed production claims. DeepSpec gives developers something closer to a set of blueprints: not a finished enterprise product, but a way to reproduce, adapt and evaluate the method.
Early community testing
The release has already drawn fast developer attention. Developer Rafael Caricio published a GitHub pull request documenting single-stream DeepSeek-V4-Flash DSpark work, reporting warmed benchmark anchors of 26.33 tokens per second without speculative decoding, 39.88 tokens per second with MTP-1, and roughly 60 tokens per second with DSpark — about 1.5x over MTP-1 and 2.3x over no-spec decoding.
A later commit in the same thread recorded a five-run mean of 60.31 tokens per second, with a 1.51x gain over MTP-1 and 2.29x over non-speculative decoding.
Advertisement
The same work also points to an important practical limit: in realistic multi-turn coding sessions, performance can degrade as draft acceptance falls with growing context. In other words, DSpark can make decoding faster, but acceptance quality still determines how much speed the system actually realizes.
That is a useful reality check. DSpark is not magic. It still depends on how predictable the next tokens are and how well the drafter stays aligned with the target model. But the early implementation work suggests DeepSeek’s claims are not purely academic. Developers are already testing the method in practical serving environments and reporting gains close to the paper’s single-stream expectations.
The bottom line
DSpark shows how much performance remains available in the inference layer, even when the underlying model architecture stays the same. As AI companies compete on model quality, context length and pricing, decoding efficiency is becoming another major battleground.
Faster generation means lower latency for users, higher throughput for providers and better economics for teams serving open models at scale.
Advertisement
DeepSeek’s release is notable because it combines a production-tested method, open code, public checkpoints and a detailed paper. The main innovation is not just drafting more tokens. It is making the system more selective about which speculative work is worth verifying.
For enterprise teams, the broader lesson is that the next wave of AI performance gains will not come only from larger models. It will also come from smarter ways to run the models companies already have — especially when those companies control enough of the stack to tune the model, train a compatible draft module and optimize the serving engine around real workloads.
Photo credit: Crissa Graves Crissa Graves has spent years making the old Game Boy Camera feel less like a novelty and more like something you might actually carry. Her latest prototype, the GBD-M2, takes that work further. It starts with a fully working Game Boy Pocket and turns the whole thing into a dedicated handheld camera with a removable camera module and interchangeable CS-mount lenses.
Video of Camera GBD-M2 in action
Once I’ve reached a comfortable place with the project, I plan on sharing the files to build yourself
You still get the same 128 by 112 pixel grayscale photographs that the first Game Boy Camera produced in 1998. The small little sensor from that era remains at the heart of every photo, but Graves has simply given it a body that makes you feel like you’re holding a proper camera while still being able to play all of the original Game Boy titles.
Advertisement
There is a dedicated shutter button that sits exactly where your finger would normally go, and the screen is a nice illuminated IPS LCD that you can see outside, which is a great benefit. An 1800mAh battery will keep you snapping away for hours, and you can even charge it via USB-C. The connection connector remains, allowing you to transfer your images to a Game Boy Printer. Surprisingly, Graves claims that you can even play some casual games like Tetris or Pokémon one-handed, despite the fact that the speaker has been removed from this version.
Graves had already completed various iterations of this Camera M project, demonstrating that the whole concept was feasible, although those older versions required hacking into a Game Boy Pocket and had some rather improvised power boards that you’d have to cobble together. The GBD-M2 is a completely new design that takes the Game Boy’s original CPU and RAM and transplants them onto a fresh new circuit board without interfering with a functional handheld. The layout is more camera-like, with bespoke buttons and a shell that has been reduced to a more manageable size after several rounds of design improvement. You also get two battery options: a LiPo battery that can be charged by USB-C, or a set of simple AA cells that you can replace out when they run out.
The camera module detaches, allowing you to replace the custom CS-mount version with alternative lenses, insert the original Game Boy Camera, or simply load a typical old game cartridge. Graves has already created a separate camera module the size of a regular game cartridge, using an iPhone lens and a custom board, which still works in any Game Boy. The GBD-M2 employs the same technique, but in a body designed to be portable and usable.
There are no mass production plans for this device yet, but Graves has mentioned releasing both DIY kits and a limited run of the finished model. You can access all of the files and updates on her GitHub page for the Camera M2 project. For the time being, the GBD-M2 is only a functional prototype, the latest stage in a long journey to find new methods to revitalize an old relic from 1998. You may monitor her progress at gameboycamera.com and on her Bluesky account. [Source]
Apple has reached 1.5 billion paid subscriptions across its platform, adding another milestone to an Apple Services business that generated record June-quarter revenue of more than $30 billion.
CEO Tim Cook disclosed the milestone during Apple’s fiscal third-quarter earnings report. Apple didn’t provide a breakdown showing how many subscriptions belong to its own services or third-party apps sold through the App Store.
The figure represents paid subscriptions rather than 1.5 billion individual customers. A single customer can hold multiple subscriptions, and multiple devices in use, across services such as iCloud, Apple Music, Apple TV, and third-party apps.
Apple’s Services division generated $30.74 billion during the June quarter, up 12% from a year earlier and setting a new June-quarter record. Revenue increased across advertising, the App Store, AppleCare, music, video, iCloud, and payment services.
Advertisement
The result still came in below the $31.22 billion analysts expected. Apple cited foreign exchange headwinds, but the shortfall against Wall Street’s estimate doesn’t change the division’s year-over-year growth or its new June-quarter record.
Apple Services revenue
Services generated $30.9 billion in the previous quarter, continuing the division’s steady growth beyond hardware sales. The latest result rose from $27.4 billion in the same quarter a year earlier.
Apple also has more than 2.5 billion active devices in use, giving the company a large installed base for subscriptions and other digital services. Paid and transacting accounts reached records during the previous quarter, although Apple didn’t disclose a comparable subscription count at the time.
The 1.5 billion total is more than 50% higher than the nearly one billion paid subscriptions Apple reported in 2023. The increase shows continued expansion across Apple’s subscription ecosystem even as quarterly Services revenue missed analysts’ forecast.
Services have become a major source of repeat business beyond Apple’s hardware sales. The latest milestone reinforces that growth, while the Wall Street miss shows investors are still judging the division by the revenue those subscriptions produce.
“It’s not red,” IBM’s design center manager patiently explained. “It’s magenta.”
The safety function officer wasn’t buying it. Between his fingers, he held up a small, rubbery disc that looked like a pencil eraser. “You know it’s red and I know it’s red,” he said.
The design manager didn’t back down. He insisted that what the man held was indeed magenta. The safety officer called his boss. The boss called Tom Hardy, Design Program Director at IBM. Hardy didn’t flinch.
Advertisement
Latest Videos FromTechRadar
“It’s not red. It’s magenta.”
It was one of the boldest lies ever told in tech. And it made the ThinkPad iconic.
Years later, Hardy relayed the incident in an interview with Laptop Retrospective, detailing the design origins of the TrackPoint, the input stick resting in a central position of the ThinkPad keyboard since 1992.
Instantly recognizable today, the little red nub remains core to the ThinkPad’s identity. For anyone working in design, its history serves as a lesson on creative control and innovation.
Sign up to the TechRadar Pro newsletter to get all the top news, opinion, features and guidance your business needs to succeed!
Every designer knows red on black is a classic combination. So, for Hardy’s team, it was a no-brainer choice when first tasked with adding the TrackPoint to the system.
Advertisement
However, at the time, IBM instituted a strict color-code. For control systems like the TrackPoint, the standard was blue. Playing by the rules, the team toyed with that. According to Hardy, “it just didn’t sing like red did.”
They switched back to red. But there was a major problem with that.
Red was reserved for emergency power shutdowns. It’s the kill-switch color. Hardy knew, even then, the safety team had to approve the color scheme. There was no way they’d let it ship with a red cursor control. That simply wasn’t the way it was done.
Advertisement
Rather than fight and inevitably lose that battle, the designers got creative.
They scrapped every trace of ‘red’ in the documentation. They replaced it with ‘magenta’.
“The safety guys,” Hardy explained, “They may not know what magenta is, but they’ll know it’s not red.”
Think Design Stories: TrackPoint Origins, The story of how it became red (ft. Tom Hardy) – YouTube
They may not know what magenta is, but they’ll know it’s not red.
Soon, the parts came in, labeled as magenta. No-one looked twice at them until the safety official snooped on a box of TrackPoints and demanded to know who approved the color for non-power related functions. He didn’t get an answer he liked. He threatened to shut down the whole production line.
Advertisement
Hardy got involved shortly after. Corporate on corporate combat ensued, arguing over the subjective difference between magenta and red. “The next stop in the line,” Hardy reminded them, “It goes to the CEO.”
Fighting his corner, he tells them, will be famed industrial designer Richard Sapper who created the classic ThinkPad design, as well as corporate graphic design consultant Paul Rand, the man behind the IBM logo. Both are color experts.
Even as the back and forth continued, Hardy’s team had linked up with the advertising team. The ad agency had poured millions of dollars into a campaign that was ready to launch. “So hot,” the adverts said with a close-up on the new TrackPoint, “We had to make it red.”
It was enough to make the safety team think twice. Later that day, an email was sent. It said: ‘Make them red.’
Advertisement
They’ve been the same iconic color ever since.
It’s no secret I’m a massive ThinkPad fan ever since I got my paws on a T431s, but check out the best business laptops my team and I have tested.
Amazon linked multiple high-profile open-source software supply chain attacks targeting the Node Package Manager (npm) ecosystem to North Korean hackers.
The cloud computing giant linked the compromises of the typo-crypto, debug, chalk, and axios libraries to the Sapphire Sleet threat actor, also known as BlueNoroff and Stardust Chollima.
Initial activity started with trojanizing the typo-crypto package in March 2025, which Amazon believes served as a testing ground. It then escalated in September of the same year with the compromise of the widely used debug and chalk packages, affecting an estimated 10% of cloud environments within two hours.
In March 2026, the hacker targeted axios, one of npm’s most popular packages with over 100 million weekly downloads.
It should be noted that the axios incident has already been publicly attributed to DPRK-linked actors, but Amazon connected it to the earlier package compromises.
Advertisement
Amazon says the attacker gained access by socially engineering package maintainers, and then published malicious updates that were automatically distributed to unsuspecting users.
The attribution to Sapphire Sleet has medium confidence and is based on the shared tactics, techniques, and procedures (TTPs) observed in the campaign, the command-and-control (C2) infrastructure, and various operational similarities.
Also, the researchers believe the attacker had a financial motivation, targeting popular packages to gain indirect access to a large pool of potential downstream victims at once.
Amazon also highlights several trends that have emerged from the recent supply-chain attacks:
Advertisement
Attackers are splitting malicious functionality across multiple seemingly benign packages, making detection more difficult.
Threat actors are spending months building trust by maintaining legitimate projects or becoming contributors before introducing malicious code.
Malicious behavior is increasingly decoupled from package contents, relying on external scripts, configuration files, or servers that can be weaponized later.
Malware is using stronger encryption and multi-stage payloads, with runtime or remotely fetched keys that hinder static analysis.
Payloads are becoming environment-aware, delaying execution unless they detect real developer or production environments to evade analysis sandboxes.
Attackers are increasingly exploiting “slopsquatting” by registering package names hallucinated by AI coding assistants, hoping developers or autonomous coding agents will install them.
Many of these tactics are enhanced and simplified by AI, Amazon explains, as they help attackers generate code, documentation, and maintainer identities.
Amazon highlighted a multi-faceted response to these dangers, including reporting its findings and intelligence to the community, collaborating with OpenSSF and other industry partners, and investing $12.5M in the Akrites initiative, which helps protect critical open-source software from AI-enabled attacks.
Security teams log 54% of successful attacks and alert on just 14%. The rest move through your environment unseen.
The Picus whitepaper shows how breach and attack simulation tests your SIEM and EDR rules so threats stop slipping by detection.
As useful as USB-to-M.2 SSD adapters are, sometimes you come across a bit of a dud. A case in point is the Orico-branded TCM2-C3 that features both an attractive clear case and in its earlier revisions a JMicron controller-based circuit that apparently degrades over time, causing erratic boot behavior. After implementing a fix a few years ago, [Mark Furneaux] can happily report that the thus fixed enclosures are still working.
These faulty board revisions feature the JMicron JMS583 controller IC, which has a 1.0V core voltage input pin. Apparently to save power, Orico designed the board to target the minimum ~-0.95V core voltage per the datasheet. Apparently due to component drift or degradation, this lower core voltage is after a while often not enough any more to start the controller, which thus translates into an unresponsive USB device and presumably some panic about lost data.
Although [Mark] doesn’t describe the fix in detail, it entails bumping up this core voltage to something closer to the nominal 1.0V, which restores functionality at the cost of presumably a measurable amount of extra heat production by said controller.
Advertisement
Later versions of the Orico TCM2-C3 enclosure switched from this JMicron controller to a Realtek one, which so far appears to be noticeably more reliable. Although Orico kept the same model name, the transparent enclosure makes it at least a snap to see which revision you are dealing with.
Just recently Karl warned that we were going to see some absolute nonsense as the US sought to somehow “ban” Chinese AI models from being used in the US. That seems to already be happening. It kicked off with talk that the US might “fight Chinese AI” using nearly identical arguments to what was used to ban (or force the sale of) TikTok before it. Some combination of “national security threat” combined with “oh no China” propaganda.
But most of the AI industry is now speaking out, in an open letter put together by Nvidia, against the potential path that the Trump administration considered taking: an attempt to ban or limit so-called “open weight” models. The companies seem to recognize that focusing on holding back these competitive models would actually do much more damage to the wider AI ecosystem.
There were notable exceptions from the campaign in defense of open weight models: Anthropic, OpenAI, and Google (the three leading frontier model labs) were not initially signed onto the letter. Though their absence quickly became the story — leading OpenAI and Google to reconsider and sign onto the letter days after it came out.
That left one major player off the letter: Anthropic (a company that has so far refused to release any open weight models). And now the company is trying to explain itself, but seems to only be digging itself a deeper hole.
Advertisement
One of the problems here is that the leading Chinese AI models tend to be open weight models, which can be downloaded and run locally, as compared to the leading frontier models from US companies which require you to access them via their own hosted models. Yes, most of the leading Chinese models also offer (sometimes significantly cheaper) cloud/API access to their models, but you can also run them yourself (for the smaller models directly on your own computers, or for the larger models via your own cloud setup).
There’s no inherent reason why the best open weight models are coming out of China, other than that they seem to have recognized that it may be the best way to get more people to use them and to compete against the American frontier models, which are much more proprietary and locked up. The strategy is a recognition that offering a compelling, more open alternative is how to get people to adopt your system over the American frontier models. If a generation of developers builds on top of Kimi or Qwen or one of the other Chinese open weight models, they become the de facto infrastructure for the next generation of digital tools.
In the same manner that Linux quietly became the substrate of the open internet, and it’s likely that an open weight model may become the equivalent for the next generation. Organizations may rely on frontier models for really deep work, but so much can be done with open weight models that a winner here becomes the commodity infrastructure provider for a new generation of software. That’s why any proposed restrictions on open weight models would get everything precisely backwards. It would guarantee that the wider open ecosystem gets built on non-American tools. Yet, the discussion around such bans seems to treat these as just another software product, rather than a fight over how the infrastructure of the internet will work going forward.
Of course, that’s not the only argument the Trump admin is using to try to stop these models. Last week they focused on claims that Kimi’s K3 model (the latest model to shake up the US market, despite being not quite as good as the frontier models) must have been “distilled” from Anthropic’s Fable 5.
Advertisement
“If we see, especially that overseas models are stealing from our great companies, we have the ability to sanction them because of this theft,” Bessent told Fox Business’ “Mornings with Maria” on Tuesday.
Bessent said the technical term for this theft is called distillation, which is an AI training method where a smaller, less capable model is built using outputs from an existing, stronger model. Anthropic sent a letter to the U.S. Senate Committee on Banking, Housing, and Urban Affairs last month alleging that the Chinese tech company Alibaba had carried out the “the largest known distillation attack” against it to date.
This is rich for a variety of reasons, not the least of which is that all of the frontier AI models were built by feeding their training models whatever information they could get their hands on, including (in Anthropic’s case) building a pirate library of downloaded books for which it had to pay out a pretty massive settlement to authors.
Distillation is not quite the same thing, but is functionally similar. It’s taking the work of an existing model to fine tune the model you’re working on. The claims about Kimi K3 seem somewhat exaggerated, as the initial claims were that it was distilled based on Anthropic’s Fable 5 release, but multiple people I’ve spoken to don’t see how that’s possible, given how Fable 5 has only been out for a little while (and then was turned off for a while due to the US government freaking out over nothing).
No matter what, distilled models are likely to be less powerful, and at least a decent period behind the frontier models, given that they’ll need access to the frontier models and time to train based on them. There’s also some dispute over how the open weight models may be using distillation, and which part of the training process works best.
Advertisement
But either way, the freakout over distillation seems… ridiculous. Bessent calling it “theft” is nonsense. Just as training a model on copyrighted works is a form of reading (which shouldn’t implicate copyright in the first place), so too is distilling, which is (in effect) training your model by having it compare its initial answers to similar answers from a frontier model and then adjusting based on the different results. It’s a form of learning based on observed results by others, not “stealing.” Pretending that it’s stealing or somehow should face sanctions or other consequences will put US AI development in a bad, bad spot.
Which brings us back to that letter. Here’s the case it actually makes:
Open weights also strengthen competition and competition is what keeps the gains of AI broadly shared rather than concentrated in a few hands. By allowing many organizations to build, adapt, and deploy advanced models, open weights create rivalry not only among model developers but across cloud chips, applications, and services. That competition spurs innovation, drives down costs, and distributes the benefits of AI broadly across our economy.
Open weights also give customers greater control. As organizations invest in AI, they want to know that they will not become locked into a single provider or lose the knowledge and capabilities they build over time. Open weight models help provide that assurance by allowing organizations to control their own data, evaluate and adapt models to their own needs, and deploy them wherever their business requirements demand. And as organizations create value with AI, open weights allow them to own that value through self-improving models, specialized capabilities, and accumulated knowledge that drive American sovereignty and prosperity.
Of course, Anthropic (which hasn’t released any open weight models) was conspicuously absent from the signatory block of that letter. Earlier this week, Anthropic’s Dario Amodei came out and tried to explain/justify the company’s stance, which boils down to: “we don’t think anyone should ban open weight models… but we do think the US should ban all the conditions that make quality open weight models possible.”
Amodei argues that simply banning Chinese open weight models wouldn’t solve the alleged “threats” that people are concerned about, though he admits directly that it would act as protectionist industrial policy that could benefit American AI companies (like Anthropic):
But banning the use of these models by US businesses does nothing to address this risk, because bad actors are unlikely to be legitimate US businesses. It would protect US AI companies from competition, but that has never been my goal.
It feels a bit like he’s protesting too much regarding the protectionism here, while trying to have it both ways. He claims he really has the best interests of safety at hand, and is against protectionist ideas, but it’s hard to square that with the rest of the article.
While he says the US shouldn’t ban open weight models (and it shouldn’t), he then puts a bunch of conditions on it, which would make it that much more difficult for the current crop of open weight models to compete. Namely, he leans in on the Sinophobia that has become popular these days in warning about “CCP” influence over models (which… should be less of a concern with open weight models, since those who use versions not hosted by the Chinese companies can adjust the models to deal with those concerns).
Advertisement
But then he says that we should punish Chinese AI companies for engaging in distillation:
We should crack down on industrial-scale distillation operations. Distillation is a much more compute-efficient process than training models from scratch. It allows China to build much better models than its number of chips would ordinarily enable, and thus partially evade chip bans. Distillation does not allow the CCP to obtain equivalent or superior AI capabilities to the US, but it can bring the Chinese frontier to within a few months of the US frontier. It is true that many of the companies carrying out these operations release open-weights models—but the open weights are far less relevant than the fact that the operations are backed by an authoritarian state seeking to overtake the US at the frontier. We should have policy interventions to deter this behavior. A blanket ban on open-weights models is neither the correct remedy nor something we have called for.
To be fair to Amodei, not everything on his list is competitor-hobbling. He also wants chip export controls tightened (a policy that predates this fight and has its own problems, but at least isn’t aimed at a business model), and he wants mandatory pre-release safety testing for all sufficiently capable models — open or closed, foreign or domestic, Claude included. That last one is the tell, though, and not in the way he intends: if you genuinely believe capability-based testing is the right lever, and you’ve just said bans “would protect US AI companies from competition, but that has never been my goal,” then what is the argument about distillation doing on the list at all? Testing catches dangerous capabilities regardless of how the model got them. The distillation crackdown adds nothing on safety. It only serves to kneecap cheaper competition.
And even the “safety testing” plank isn’t as neutral as it sounds. While safety testing is obviously important, when legally mandated, it can quickly turn into an expensive compliance-function of box-checking that only the largest companies can do, taking us back to the world of just a few providers, and limiting smaller competitive models from really being viable. While there are legitimate reasons for it, it can also create its own moat.
The proposed crackdown on distillation is just asking the state to step in and block lower-cost competitors from competing. Yes, these models can be competitive, but they should be driving the leading frontier models to continue to improve and to provide more value. What Amodei is asking for here is basically the US government to help prevent lower cost, lower quality competitors from pushing the floor of the AI market upwards.
Advertisement
Now, to be clear, as with any technology, you can claim that a more open, more widely available, more powerful version can be misused. But that has always been the case and we, in the US, have tended to default to allowing the technology to proceed, and figuring out ways to minimize the dangers/increase the good uses, rather than resorting to assuming the tech will be abused and working backwards to block all possible abuses. Historically, seeking to pre-vet technologies tends not to work well, and (often) opens up the market to foreign competitors to simply build better products.
The open letter makes a sharper version of this point, and you can see why Anthropic wouldn’t want to put its name to this point in particular:
Relying solely on closed models is not inherently safe: they can be breached, misused, or fail in ways that outsiders cannot detect. And concentrating advanced AI capabilities behind a small number of closed models compounds that risk. It results in a small number of single points of failure, weakens competition, and leaves critical technology in the hands of a few providers. Open weight models, on the other hand, allow a broad community of researchers and developers to examine their behavior, identify vulnerabilities, develop safeguards, and improve them over time. Just as open-source software demonstrated that transparency can be more secure than obscurity, AI safety may depend on giving more people the ability to test and strengthen the models on which society relies. It allows for rigorous benchmarking and evaluation, red teaming, and protections tied to real and demonstrated harms rather than assuming that closed systems are safer by default.
Amodei also claims he supports the general argument of the open letter, but he disagrees with the idea that open weight models lead to better security:
This brings me to the open letter. I agree with much of it: open weights expand access to the AI economy, they strengthen competition at least for some use cases, and they give customers greater control. Concerns about distillation should be addressed through targeted legal and commercial frameworks—the same measure I described above. But I don’t agree with the letter’s assertions that open-weights models necessarily make it easier to develop safeguards or that broad access to capabilities necessarily helps defenders more than attackers. It seems at least as likely to me that the opposite will be true.
This strikes me as a repeat of the age-old fight that always shows up in discussions of open source technologies: the claim that by making them open, security vulnerabilities are easier to find. Of course, what we’ve seen historically in other spaces is that this actually means that security vulnerabilities are more quickly patched, rather than in the “security by obscurity” space, where they can remain open (and possibly exploited) for much longer.
Advertisement
Amodei is asserting that the AI space is somehow different, though without much evidence for that other than what feels like a bit of fear-mongering about “weaponizing pandemic-level viruses.”
Of course, part of the problem here is that it often feels like Anthropic treats “crying wolf” as a marketing strategy, whereby much of the company is focused on talking up “our tools are soooooooo dangerous that you need us in there to protect you from them.” Even if there’s some truth to it, it’s awfully convenient that the same argument also happens to justify banning, punishing, or limiting the cheaper, more open, more user-controllable alternatives.
In the end, the federal government still might try to punish the Chinese open models in some form or another just because they view current American industrial policy in very nationalistic terms. But that won’t be good for the wider ecosystem, or for the general incentives to innovate. And, worst of all, it makes it that much harder to build a world where we’re not entirely dependent on a few giant companies controlling the “brains” of the tools the rest of us rely on.
UL’s Prof Martin Hayes on his systems theory research, why ‘pi-shaped’ graduates are the future of engineering, and the importance of patience.
Prof Martin Hayes is a professor of digital technologies at University of Limerick (UL) who describes his research as sitting “within the space of systems theory for machine learning and AI”.
Hayes’ research looks at how to manage system resources intelligently when they’re subject to uncertainty or mixed messaging introduced by communication channels, sensors or human operators. A large part of his work focuses on the “robust” performance of AI in safety-critical environments.
“How do we correctly choose settings when an AI system’s outputs feed into decision-making by people, without getting that handoff wrong?” asks Hayes.
Advertisement
“Health is an obvious area where such solutions have to be correct 100pc of the time.
“The alternative has real consequences in terms of negative outcomes – so I’m asking how we can guarantee a health system that will exploit the benefits of AI while working optimally for every citizen every time.”
Hayes tells SiliconRepublic.com that as AI and machine learning technologies move from research labs into safety-critical, high-stakes settings, these systems “can’t simply be accurate on the average”, and that understanding how to build in basic levels of robustness allows technology to be deployed responsibly in regulated domains such as digital health.
“Professionals working in the health system, be they medics, engineers or administrators, need to understand not just how to use AI tools, but how to trust, interrogate, explain and govern them appropriately,” he says. “Without that grounding, adoption either stalls through excessive caution or accelerates without the safeguards that safety-critical settings demand.
Advertisement
“Translational research that provides a foundation for those who are already working in or who wish to participate in the new European Health Data Space is a key focus of my work.”
‘Pi-shaped graduates’
With his work spanning from systems theory to engineering and the real-world domains where these tools get deployed, Hayes says that the interdisciplinary nature of the research is actually a very rewarding part of the job.
In particular, he enjoys the collaborative side of it where he works directly with industry partners, clinicians and SMEs to “understand where the genuine skills gaps are and then translating that into education and research that actually closes them”.
However, according to Hayes the most satisfying part of the job is seeing graduates go on to responsibly deploying this understanding and thinking in the workplace.
Advertisement
“I believe strongly that the future of engineering education revolves around the growth of such ‘pi-shaped’ graduates who have the basic skills in AI-enabled data engineering but who also have the necessary allied health skills to be able to apply those solutions in a safe, human-centred fashion,” he says.
Hayes has worn and continues to wear many hats at UL, where he has worked since 1997.
He is the academic lead for the UL@Work Human Capital Initiative project, which aims to develop digital, industry 4.0 talent through flexible, innovative, technology-enabled, experiential learning. Hayes says his involvement in the UL@Work project has been “hugely insightful”.
“One key takeaway is that universities need to work together and collaborative programmes like Digital Europe are essential in enabling institutions to pool their resources so that they can offer students the bespoke learning that fits their individual needs.”
Advertisement
Hayes is also collaborating with various European universities as principal investigator for a number of Digital Europe projects – such as that of Sustainable Healthcare with Digital Health Data Competence (SUSA).
SUSA is a €12.4m Digital Europe-funded project led by the University of Oulu in Finland that aims to close the digital skills gap in European healthcare and support the EU’s Digital Decade and European Health Data Space ambitions.
The project aims to deliver revamped bachelor’s, master’s and standalone lifelong-learning modules, built around 20 shared SUSA learning objectives that have been benchmarked against frameworks such as the WHO Digital Health Competence Framework.
Hayes is UL’s principal investigator for SUSA, leading the ‘Workpackage’, which frames and co-designs SUSA activities in order to maximise impact.
Advertisement
“We lead in two specific tasks: investigating how to best deliver education on the optimal use of advanced digital technologies in health – particularly XR/AR and digital twin technology – and designing the SUSA employer framework that connects students with industry most efficiently,” he explains.
“UL’s contribution to the SUSA digital ecosystem draws on existing UL@Work advisory board models and Skillnet partnerships to keep the curriculum grounded in current workplace needs.”
Fundamentals and patience
As someone working in such a future-focused research area, we asked Hayes about what advice he might have for someone considering a career similar to his own.
First thing on the list? “Build a strong foundation in the fundamentals,” he says.
Advertisement
By fundamentals, he means systems theory, mathematics and statistics.
“These are what let you adapt, configure and ultimately deploy solutions as the technology moves on,” he explains.
Next, he advises newcomers to seek out interdisciplinary collaboration early and not to be “afraid to work at the boundary between engineering and the domains where it gets applied, whether that’s healthcare, manufacturing or elsewhere”.
“Get involved in industry-facing projects where you can; the most consistent feedback we get from our students is that they’ve always enjoyed it most when they’ve been exposed to real-world constraints either through UL’s co-op education programme or the in-house projects they complete during their studies,” Hayes adds.
Advertisement
“Ultimately this sharpens the R&D questions you ask and makes you a more valuable resource,” he says.
“Finally, be patient. Your career, much like a trustworthy AI system, is built over the long term and will inevitably require you to actively manage many uncertain situations.
“Embracing that challenge will give you the confidence to achieve your goals. Repetition builds competence!”
Don’t miss out on the knowledge you need to succeed. Sign up for the Daily Brief, Silicon Republic’s digest of need-to-know sci-tech news.
Xiaomi stepped into the large family SUV game on July 30 with the SkyNomad N90 Max, an extended-range electric vehicle built around the idea that a car can serve as living space first and transportation second. Presales opened the same day in China at 299,900 yuan, roughly 44,000 dollars, with official deliveries set for September. The company also showed a smaller five-seat N70 Max sibling starting lower, but the seven-seat N90 Max is the clear centerpiece.
The N90 Max measures 5285 mm in length, 1998 mm in width, and 1825 mm in height, with a wheelbase of 3080 mm. With a completely flat floor and good long seat rails, the groundwork is created for Xiaomi’s Kunlun architecture, a platform designed expressly for this type of customizable cabin rather than driving for driving itself.
49 Min UltraFast Recharging: With upgraded HyperFlash tech, fully recharge at 1,600W—for outage prepping, camping trips, or tailgating events…
2,000W Output via 10 Ports: Delivers 2,000W (3,000W peak) and 1,024Wh capacity. Power up to 10 devices—ideal for emergency backup, remote work…
Compact and Portable: Easily carry, store, and move from room to room, your RV, or even on beach and park outings. C1000 Gen 2 is 14% smaller and…
The N90 Max delivers a powerful punch, thanks to a dual-motor all-wheel-drive system that produces a decent 310 kW (416 horsepower). The rear motor produces 210 kW, and the front one adds another 100 kW to the mix. It takes a decent 5.9 seconds to accelerate from 0 to 100 kilometers per hour. You are limited to 190 km/h, but 0-100 in under 6 seconds gives you an excellent idea of the N90 Max’s capability. A 1.5-liter turbocharged engine from Harbin Dongan serves as a generator, producing 112 kW and charging CALB’s 76 kWh ternary NMC battery. With the battery empty, the N90 Max has a pure-electric range of 464 km on the CLTC cycle. If you put some gas in the tank, you’ll have a total distance of 1705 kilometers (1059 miles). When the battery becomes low, the WLTC cycle consumes approximately 6.26 liters of petrol every 100 kilometers. A 15-minute DC charge adds 285 kilometers to your electric range, while charging from 20 to 80% takes less than 18 minutes.
Advertisement
The N90 Max features a 2+2+3 layout. When parked, the front seats will power swivel fully 180 degrees, allowing you and your passengers to face the second row. If you choose the center table, it will slide out of the tunnel, creating a living space up to 1370 mm wide in four-person mode. Second-row seats include zero-gravity designs with footrests and a 16-point massaging system, providing plenty of extra comfort. You also get a 9-liter compressor fridge in the center island, which has cup and phone slots. The N90 Max has some serious sound setup going on, with up to 25 speakers outputting 4,890 watts over a 7.1.4 arrangement. The rear seats feature a 21.4-inch 3K screen, while the driver has a 20-inch head-up display, an 8.8-inch instrument cluster, and a 16.1-inch primary screen. The majority of seat and table adjustments are controlled by voice commands.
Xiaomi describes the parked cabin as a studio for one, a café for two, a lounge for three, or a playroom for the entire family, so it is quite adaptable. The N90 Max Camping Edition exhibits the same flexibility, with a pop-up roof, a rooftop bed platform, tent attachment points, side cabinets, and an optional removable table. This version is suited for five persons and has the same powertrain as the normal N90 Max. The car includes a roof-mounted LiDAR unit as well as a rear-facing solid-state device with an accuracy of a few centimeters. This is combined with some extremely strong computers, courtesy of NVIDIA’s Thor-level technology, as well as Xiaomi’s whole HAD assisted driving package, which includes their XLA cognitive model. The vehicle’s structure is meant to last, with a frame made of high-strength steel and aluminum.
The three rows are connected together by a continuous hot formed door ring that runs the entire width of the vehicle. Underneath, there’s a really innovative suspension system that combines double wishbone front geometry with a multilink rear configuration, and the vehicle can handle a decent soak with a water wading depth of 750mm. It also has enough electricity to keep your electronics charged, with 220 volt charging outlets and 6.6kW vehicle-to-load capability, making it excellent for camping trips or emergency circumstances. The range extender itself operates silently enough that Xiaomi claims the cabin remains as quiet as a pure electric vehicle even when it is powered up. The pre-sales price for the flagship Sky Nomad N90 Max is 299,900 yuan ($44,322), while the somewhat smaller N70 Max is 259,900 yuan ($38,410).
A trip to college—or even to avoid hard nights at home during high school—might come with an expense you didn’t think about: a good office chair. Dorm chairs are hard, awful, and not exactly ergonomic.
Luckily, there are some decent back-to-school office chair deals right now among chairs I can vouch for. My colleagues at WIRED and I have been testing and tracking the best office chairs for more than seven years. The ProtoArc Flexer Pro ($176) is half the price it was last year, probably the best deal at the moment. Others of our budget favorites, like the Staples Dexley ($169), are kinda always “on sale,” and remain among the best available at a low price.
Here are the best affordable office chairs and back-to-school chair deals available for the 2026 school year. Every single chair I recommend here is one we’ve personally tested. Also check out WIRED’s other back-to-school guides, including dorm room essentials and college laptops.
A Steeply Discounted Mid-Range Ergonomic Chair
Photograph: Julian Chokkattu
ProtoArc
Advertisement
Flexer Pro ergonomic Office Chair
This Flexer Pro ergonomic chair from ProtoArc was a decent deal when it debuted last year at close to $400. But over the past year and month, prices have dropped considerably—this is the lowest price I’ve seen. The chair offers several points of adjustment, including seat pan depth, multiple recline angles, and four-way adjustable armrests.
The build quality and looks are far better than one could generally expect south of $200, with a five-year warranty that’ll get you through those undergrad years. Just note that there’s a detachable lumbar support that can pop off a little too easily from the backrest, and it’s not a great chair for people taller than 6 feet.
WIRED’s Favorite Budget Chair
Photograph: Julian Chokkattu
Staples
Dexley Ergonomic Mesh Swivel Task Chair
Advertisement
Staples basically holds down the discount chair scene, and the Staples Dexley is the best ergonomic chair that can be consistently had below $200. The five-year warranty will take it through most degree programs without a big hit to the wallet and the all-mesh seat offers terrific airflow; the chair is also easy to put together and decently adjustable. The mesh is a little scratchy for shorts wearers, but otherwise this is a solid chair with ergonomics good enough to support the occasional all-nighter.
Amazon plans to launch 5,105 satellites to support new mobile networks
The filing with the FCC highlights voice, data, emergency services, and Internet of Things support
Amazon Leo already has over 390 satellites in orbit, enough to launch the plans ahead of the full deployment
Amazon has confirmed its “low Earth orbit” (LEO) satellite network has submitted an application to the Federal Communications Commission (FCC) to deploy a constellation of 5,105 satellites which will provide voice, data, messaging, emergency services access, and Internet of Things support for under the Amazon Leo Direct-to-Device (D2D) project.
The application follows Amazon’s merger with Globalstar, acquiring the US satellite telecommunications company’s operations, infrastructure, and global licenses and authorizations.
This step into orbit will see Amazon Leo’s existing satellites work alongside the Globalstar HIBLEO and C-3 satellite constellations, kicking off early D2D project support ahead of approval for the full network of comsats.
Latest Videos FromTechRadar
Advertisement
High-speed, low-latency
Much like Starlink, the Amazon Leo network is intended to bridge the connectivity gap between cities and remote communities. It aims to deliver high-speed, low-latency broadband for domestic and enterprise markets, as well as governments, with consumers gaining connectivity via the Leo Nano, Leo Pro, and Leo Ultra high-performance antennae. Meanwhile, mobile devices with satellite-capable chipsets can connect to the satellites without an additional antenna.
Apple iPhones and Apple Watch models are also supported, under a previous agreement to collaborate with Apple. Amazon Leo already delivers data for Emergency SOS, Messages, Find My, and Roadside Assistant to iPhones.
Other partnerships have also been announced that feed into the D2D project. “Telecom operators like Vodafone, DirecTV, Herotel, and Australia’s National Broadband Network […] it plans to continue working with mobile network operators and other partners to deliver on its long-term vision for space-based connectivity.”
Beyond offering connectivity to remote locations, D2D can enable data support for global fleet management, remote operations for supply chains, and IoT connectivity.
Sign up to the TechRadar Pro newsletter to get all the top news, opinion, features and guidance your business needs to succeed!
Advertisement
Amazon Leo’s satellites
Following initial deployment in 2025 with 80+ launches with Arianespace, Blue Origin, SpaceX, and United Launch Alliance, Amazon Leo is aiming at 5,105 low Earth orbit satellites. These units are connected using optical links, capable of high-speed data transfer, with secure gateways networked across the planet, with fiber connectivity.
The D2D satellites are intended to operate across five orbital “shells” – essentially five groups that share the same altitude and inclination. Three shells will cover the mid-latitude, one shell will cover the high-latitude, and the fifth providing coverage for “near-polar” zones. Mid-latitude zones are the world’s most heavily populated regions (North America, Europe, parts of Asia, and southern/central Africa) while the high-latitude coverage aims to deliver high speed internet to the Arctic and sub-Arctic circles.
With increasing demands for mobile data, not just for remote working but also Internet of Things applications, Amazon Leo could prove to be the solution that facilitates home and workplace automation around the world – assuming, of course, that it gets that FCC approval.
You must be logged in to post a comment Login