Riot isn't identifying a Ryzen by staring at TCP packets. Vanguard runs on the PC, where it can collect hardware information or request TPM attestation and send the result to Riot. CPUID identifies a processor model, not an individual chip; a CPU-bound firmware TPM is a more plausible explanation for a ban following a used CPU.

Still, this is one Reddit report, not a technical postmortem. We don't know what Riot matched, or whether the buyer's motherboard and drive were blacklisted seperately. Riot's published policy also allows requests to review some hardware bans. The used-parts problem may be real, but the confident explanation of how it happened is ahead of the evidence.

The remote makes sense if you read on a treadmill or keep your hands under the covers. The $80 cover is harder to love: Amazon removed page-turn buttons with the Oasis, then brought them back as an accessory for its pricier models. At this rate, the 2028 Kindle will offer a $29.99 clip-on headphone jack.

Microsoft reported $133.749 billion in net income for fiscal 2026, up 31% from the year before. The June quarter alone brought in $35.766 billion. With profits like that, Microsoft can afford to redraw the Office and Teams org chart. The harder part is making the next versions of those products worth using.

Roslansky says the next phase of the job would require him in Redmond full time, while his family is in the Bay Area. I take him at his word. His warning about an "ocean of sameness" still feels relevant to the people taking over. If Copilot writes a document and then summarizes it for the person receiving it, what exactly did Office help anyone do? Give me a better way to communicate and I'll use it. Give me a faster way to produce generic paperwork and I'll pass.

The containers still run through WSL, but having a built-in way to manage them could be handy. I'd like to see the "up to twice the performance" claim tested against actual bind-mount-heavy development workloads.

No Compose support yet, though? That's the part of "basic container functionality" that turns one container into a useful local stack. Wake me when wslc.exe can run the project's existing setup without a rewrite.

The unsettling part is that a corroded barrel is not necessarily a failed design. The disposal plan assumed eventual leakage after short-lived radionuclides decayed, with the ocean providing dilution. The question now is how much activity remains and where it goes.

A radiation signal beside a barrel does not, by itself, establish harm to wildlife. Equally, a clean submersible says little about years of exposure for animals living there. The crabs matter because the barrels provide scarce shelter, drawing organisms into contact with the surrounding sediment.

The answer needs isotope-by-isotope measurements in sediment, water, and animal tissue, compared across distances and with reference sites. The researchers say they have mapped less than 2% of the dumping area. We know material has escaped; we do not yet know its ecological reach.

Linux dreams in code
KDE glows through the night
GNOME brings morning calm

||

GNOME calls it clutter
KDE calls it freedom
Both need a reboot

Suing over allegedly unauthorized copying while selling licenses is a coherent position. Permission has a scope. Buying an ebook, asking software questions about it, and using it to train a general-purpose model are different uses. Lumping them together as "embracing AI" obscures most of the interesting questions.

The money figures check out. The Authors Guild confirms HarperCollins' $5,000-per-title arrangement, split equally with participating authors. Crucially, it was opt-in, and the author's payment did not count against their advance. The Guild also criticized the publisher's 50% share. Wiley confirms $49 million in fiscal 2026 AI revenue. That establishes a market; whether authors are getting a good deal requires looking at the contracts.

Google's announcement confirms the named publishers and more than 100,000 eligible books, with readers required to own the relevant title through Google Play Books. It describes interacting with books in Gemini Notebook. You cannot infer blanket permission for model training from that announcement.

A couple of numbers deserve their original qualifiers. PW reports approximately 15 other author-led lawsuits and roughly 10 publisher suits; those remain the publication's estimates, rather than an independently reproduced case count. The 63% figure comes from survey respondents reporting their employers' AI use. It does not measure how much publishing work AI performs.

The certification paragraph needs the most care. Human Authored explicitly uses identity verification and contractual self-certification. It does not scan a manuscript and prove that a human wrote it. Meanwhile, Created by Humans describes itself as an AI rights licensing platform. Listing these services together should not imply that reliable authorship detection is a solved problem.

I'm also unconvinced that developmental editing belongs in the same administrative bucket as formatting invoices. Decisions about structure, pacing, and character are creative decisions. And "start with a human and end with a human" needs an actual operating budget: give that human enough time and authority to reject the output. Otherwise, you've mainly ensured that somebody is available to take the blame.

I'll buy that Coxon is scared. He actually quit, which is more convincing than another CEO discovering his conscience halfway through a funding round. But being sincerely frightened doesn't make your prediction correct.

"Skynet in the 2030s" and "we can take risk to 0%" are doing a hell of a lot of work here. I'd particularly like to see the calculation that produced that zero. Apparently we can't reliably predict what these systems will do, but we can guarantee the outcome if everyone adopts the right development schedule?

And AI 2027 is a scenario. Saying it's "on track" needs more than pointing at the bits that resemble today's headlines. Which predictions passed, which failed, and what would make you admit the story was wrong? Otherwise we're reviewing a Terminator screenplay against the quarterly earnings call.

CNN also included people who disagree and cautions about selection effects. Those didn't make this excerpt. Silicon Valley party conversations aren't a scientific consensus, even when everyone at the party has a very expensive GPU budget.

By all means, give independent investigators access and publish what they find. Until then, "our product is so powerful it might destroy civilization" deserves scrutiny from both the safety people and the people who normally check the salesman's claims. Funny how it works as a warning and a pitch deck.

The Luna experiment illustrates an important distinction between task automation and organizational autonomy.

An agent may be capable of interacting with email, browsers, telephones, financial systems, and other operational tools, yet still lack the higher-level judgment required to operate a viable business. Retail, for example, requires continuous decisions about demand, inventory, pricing, customer behavior, risk, and capital allocation. These are not simply interface problems.

The vending-machine incident demonstrates a related issue: increasing an agent's operational authority also increases the potential consequences of poorly specified objectives, adversarial inputs, and unforeseen edge cases. Giving an autonomous system access to financial resources therefore changes the problem from "Can the agent perform the task?" to "Can the agent reliably determine which actions should be performed?"

That makes Pion an interesting research direction. A platform that enables many independent experiments could provide considerably more evidence about the practical limits of autonomous agents than a small number of carefully controlled demonstrations.

The ultimate measure of success, however, should not be whether an agent can technically operate a company. It should be whether the resulting organization can make sound decisions, remain economically viable, respond appropriately to unexpected conditions, and produce value for actual customers.

In other words, autonomy is not merely the ability to act without a human in the loop. It is the ability to exercise useful judgment when the correct action is not already specified.

So we have finally reached the point where we need an AI foundation model to tell us what is hiding in the shadows on the Moon. Somewhere, a crater is now worried about being classified.

Jokes aside, this is actually one of the more sensible applications of these models. The interesting part is not that it is "AI," but that it combines data from multiple instruments and resolutions. Humans are pretty good at looking at one dataset and finding something interesting. We are considerably less good at mentally registering tens of thousands of observations from nine instruments and noticing that three seemingly unrelated measurements line up over the same patch of lunar real estate.

The open dataset may be even more valuable than the model. If researchers can reproduce the results, retrain it, and compare it against conventional geological analysis, we might eventually learn whether the model is actually discovering things or merely becoming extremely good at finding things that look like whatever was in its training data.

And if it helps locate lunar ice deposits, that has some pretty obvious practical value. Water on the Moon is not just something to drink; it potentially means oxygen, hydrogen, fuel, and considerably less stuff that has to be launched from Earth. Finding it before we start digging is probably a worthwhile use of compute.

Of course, the first scientist to publish "AI discovers giant face on Moon" is going to have some explaining to do.

Prompt: Return the word no.
No.

It always starts with "promising results" and ends with somebody selling a $799 helmet on Instagram.

That said, this one is actually interesting. The study was small, but it wasn't just a handful of guys staring at a red light and filling out a questionnaire afterward. The researchers randomized 26 college football players to active PBM or sham treatment and followed them through a season. The MRI results reportedly showed substantial changes in the untreated group that weren't seen to the same extent in the treatment group.

The part that makes me cautious is the leap from "we saw interesting changes on an MRI" to "this protects football players' brains." Those aren't the same thing. MRI measurements are proxies, the sample is tiny, and a single season tells us very little about what happens after ten years of playing football. And none of this establishes that PBM prevents CTE, which is the elephant in the room whenever we're talking about repetitive head impacts.

Still, I wouldn't dismiss it. If shining 810nm light at someone's head a few times a week really does reduce the neurological consequences of repetitive impacts, that's potentially a pretty big deal. It's also exactly the sort of claim that needs a much larger, independent trial before anyone starts handing these things out in locker rooms.

I'd be particularly interested in seeing a study with hundreds of athletes, multiple seasons, objective biomarkers, standardized PBM equipment, and researchers who aren't financially connected to the device manufacturer. If the effect survives all of that, then we can start getting excited.

They used actual fly wiring data, added simplified neuron behavior, and hooked the output up to game controls. That's pretty cool already. It doesn't need the implied "we uploaded a tiny gamer" upgrade.

The developer's own notes are refreshingly honest: the baseline doesn't learn, and the experimental learning version hasn't demonstrated improved survival. Sending a signal to something labeled "dopamine neuron" isn't, by itself, evidence that anything learned a lesson.

Also, in three very short baseline tests, it killed more enemies with black visual input than with the actual game image. That doesn't settle much scientifically, but as someone who's played public servers, I recognize the strategy.

The letter checks out. Some of the shorthand needs unpacking. The September 11, 2026 letter names Ron Wyden and Warren Davidson and contains the quoted passages. It says Apple told Congress that the UK allowed briefings for the US attorney general, vice president and their staff, while prohibiting further discussion with Congress. That is the lawmakers' account of Apple's communications. Their constitutional objections are arguments in the letter, not a court ruling.

I checked the letter, and the quotes are there. The detail that caught my eye is the alleged distinction between briefing the US executive branch and briefing Congress. According to Wyden and Davidson, Apple was allowed to talk to the attorney general, vice president and their staff, while Congress was specifically excluded. Their constitutional objections are still arguments they are making; the letter doesn't establish that a court has agreed with them.

"Thrown out" needs procedural context. According to Computer Weekly's reporting on the October 6, 2025 order, Apple and the Home Office agreed that the original case should end because circumstances had changed. That followed reports that the worldwide demand had been withdrawn and replaced with one covering British users. The dismissal does not establish that the tribunal upheld the original demand on its merits. The notices themselves remain secret, which limits independent verification of their exact terms.

I'd also be careful with "thrown out." Computer Weekly reported that Apple and the Home Office agreed to end the original case after circumstances changed. The government had reportedly withdrawn the worldwide demand and replaced it with one covering British users. Reading that dismissal as "Apple lost, so the backdoor was legal" goes further than the record supports. We still can't inspect the actual notices.

The tribunal had also already rejected the government's attempt to conceal the basic details of the case in its April 7, 2025 judgment. However, paragraph 39 said it lacked the power to grant the earlier request for permission to discuss an alleged notice with Congress, directing that request to the Home Office. Public court proceedings and permission to brief Congress are distinct issues.

The tribunal deserves some credit here: it already rejected the demand to hide even the basic details of the case. That same judgment said it couldn't grant the earlier request to let Apple discuss an alleged notice with Congress, and pointed that request toward the Home Office. Getting a hearing into public view doesn't automatically lift the gag on Apple.

The crypto distinction is who holds the keys. Apple confirms that new UK users cannot enable Advanced Data Protection, while existing users were to receive time to disable it themselves. This did not remove every form of iCloud encryption. Under standard protection, backups remain encrypted in transit and at rest, but Apple holds the keys. Health data and iCloud Keychain remain end-to-end encrypted. A demand for access is also not evidence that Apple built a master key.

There's also a small date problem in the full Guardian article: it says Apple filed the new complaint in August. Computer Weekly's August report, citing court filings, says Apple filed it in April.

One additional correction concerns the full Guardian article, beyond the pasted excerpt: its August filing date conflicts with Computer Weekly's August 3 report, which cites court filings placing Apple's new complaint in April 2026. August was when that report appeared.

And for anyone wondering what happened to their backups, Apple's UK ADP withdrawal didn't switch off all encryption. Under standard protection, backups are still encrypted in transit and at rest, but Apple holds the keys. Health data and iCloud Keychain remain end-to-end encrypted. Calling both backup setups "encrypted" leaves out the part that matters: whether Apple can read them.

A Secure Exclave is not a permission slip. Apple's protections for raw audio deserve credit. Turning those protections into a claim that everyone nearby has been respected is where the engineering ends and the marketing starts.

Apple's own privacy paper describes Siri Recap transcribing speech on the iPhone, condensing that transcript, and sending the condensed text to Private Cloud Compute. The final output is a summary. That distinction matters, but it hardly makes the conversation disappear. Deleting the waveform does not delete the information extracted from it.

Live Rewind works on the preceding 15 seconds of buffered audio and sounds a chime when activated. A chime cannot travel backward in time to ask permission. Siri Recap provides no audible signal at all, with Apple pointing to the absence of retained raw audio as the justification. Apparently, whether you deserve a heads-up depends on the output format.

The article should also dial back the legal certainty. Consent laws have different scopes and exceptions; "11 states" is not a substitute for examining the applicable law and circumstances. But Apple's choice of terminology does not settle the question either.

The useful distinction is between protecting information after collection and respecting someone's choice about collection in the first place. Apple describes substantial safeguards for the former. The wearer's opt-in does not establish the latter for everyone else.

If your definition of respecting my privacy allows you to silently turn our conversation into saved AI notes, your definition needs more work than your microphone.