Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror

Comment Re:Really? (Score 1) 34

Moreover, the choice of JSON is stupid. It should be XML.

Honestly? Not a bad take in isolation. XML has stricter schema enforcement, better namespacing, and more mature tooling for validation and contract-first design. If you’re old enough to remember SOAP, WSDL, and the joy of a well-typed XSD, you probably get the appeal.

But A2A isn’t designed for humans writing XML by hand or for enterprise contract rigidity. It’s aiming for interoperability at speed across modern web stacks. JSON wins here, not because it’s better engineered—it isn’t—but because it's ubiquitous, lightweight, and already what most agents and microservices use under the hood. JSON makes it deployable this quarter. That’s the tradeoff.

Comment Re:Really? (Score 1) 34

This comment is a textbook case of the kind of smug, faux-insightful derailment that gets +5’d not because it’s technically strong—but because it flatters the priors of Slashdot’s anti-AI crowd -- early and mid-career code monkeys who know they are going to be replaced by an LLM in the near future. You cosplay at engaging with the technical substance of A2A, but then go full troll: substitute a different problem (LLM alignment, adversarial robustness) and then dismiss A2A for not solving it. This isn't analysis; it's rhetorical bait-and-switch—designed to derail the discussion and farm upvotes from those eager to conflate every AI infrastructure advance with AGI overreach. It's fucking tiresome. Go do it elsewhere.

I'm glad to hear that one of AI's "most pressing challenges" is concluding that you should use TLS on the wire and having a standardized JSON object in which to declare your proprietary extensions;

That’s not the challenge. That’s the solution to a challenge that’s been strangling distributed AI adoption: lack of a neutral, secure protocol for agents to handshake and collaborate across vendors. If TLS and JSON look trivial to you, you’ve either never had to wrangle OAuth hell between microservices at scale or you’re pretending those choices don’t become existential when multiple autonomous systems have to exchange authority, identity, and context.

...rather than the ongoing inability to make LLMs distinguish between commands and data even vaguely reliably; or the persistent weakness to adversarial inputs.

That’s like complaining that TCP doesn’t prevent SQL injection—technically true, completely irrelevant. A2A is plumbing. You can’t fix the faucet until the pipes connect. A2A isn’t in the cognition stack. Why are you even bringing this up? Oh right, You're a troll. Those are legit issues, that are actively being worked on -- and being discussed elsewhere. If you think you have something to contribute, then join us there. I doubt it though. Trolls like you have nothing to contribute, ever. All you can offer is distraction.

It's not wrong that you'd want to use the sensible obvious choices and avoid pointless vendor quirks; but talking about 'A2A' as a contribution to solving agentic AI's most pressing challenges seems about as hyperbolic as describing ELF or PE32+ as being notable contributions to software security and quality.

Typical troll bad analogy. You don’t ship software by writing binaries with a hex editor. You need format standards—including PE and ELF—so you can link, deploy, and execute code reliably across systems. A2A does the same for agents: it provides the missing contract layer so distributed AI agents aren’t trapped in their origin silos. That’s not hyperbole. That’s operational necessity.

Yeah, it would be worse if we were also squabbling over how to format our executables; but oh boy is that the unbelievably trivial bit by comparison.

If it's so trivial, why has it taken until 2025 for the Linux Foundation, Google, AWS, Microsoft, and Cisco to rally behind a shared protocol? The answer: because everyone tried to duct-tape this “trivial bit” for years with brittle, proprietary glue, and it broke every time people tried to scale. The trivial parts only feel trivial in hindsight—after someone bothers to standardize them.

The play here isn’t to inflate A2A into AGI hype. It’s to acknowledge that if agent-based AI is going to scale beyond toy demos and fragile demo-bot stacks, it needs boring, robust pipes like A2A. That’s what this is about, and sneering at the plumbing reveals you for what you are -- just another troll trying to derail a conversation.

Comment A2A -- the API layer we should have had years ago (Score 1) 34

Cue the usual chorus of doom-sayers and trollish derailers.

Whenever a pragmatic, infrastructure-focused advance in AI gets announced—especially one involving standards—there’s a depressingly reliable pattern on Slashdot. Someone will pop up to conflate it with AGI hype, minimize its relevance, and then pivot to bashing LLMs with a few tired lines about adversarial prompts and hallucinations. Bonus points if they score a +5 Insightful from lurkers who never read past the headline. (I know, I know...this is slashdot.)

A2A is not about fixing hallucination or cognition. It’s about enabling existing agents—however dumb or smart—to communicate, collaborate, and delegate tasks in a secure, vendor-neutral way. It solves the interoperability mess that has long plagued multi-agent systems. You know, the part that isn’t sexy but actually matters in production.

It's not some grand leap in AI intelligence. It’s boring on purpose. Like HTTP. Like JSON-RPC. Like every layer of tech that quietly makes things work.

But that nuance gets straw-manned into oblivion by detractors who pretend that unless a protocol cures hallucinations and passes the Turing Test, it’s irrelevant. That’s like dismissing the value of USB-C because it didn’t invent electricity.

Do some of the marketing blurbs overstate things? Sure. Welcome to tech. But let’s not pretend the protocol is useless just because it doesn’t solve every AI problem at once. That’s not insight—that’s deflection as performance art.

And as for the tired “we’ve had TLS and JSON forever” takes: congrats. You’ve identified tools A2A is smart enough to actually use. The difference is coordination at scale—between agents that weren’t designed to talk to each other.

This is not about AGI. This is not about hype. This is about enabling structured coordination, the kind that underpins everything from search indexing to enterprise workflows. You can either hand-wave it away—or recognize it as a crucial step toward scalable, composable AI systems. Let’s argue the thing on its own terms, not whatever anti-AI strawman is trending on slashdot today.

Comment M$ v. OpenAI: Custody of the Ghost in the Machine (Score 1) 58

Jesus fucking christ. “AGI” used to mean generalization without retraining. Now it means $100 billion in revenue. That shift alone should terrify you more than any sci-fi doomsday scenario. OpenAI and Microsoft are in a knife fight over a clause that says, once AGI is achieved, OpenAI can withhold tech from Microsoft. Sounds fair—except no one agrees on what AGI is. So they pinned it to profit. That’s right: AGI is now defined not by cognition, or consciousness, or autonomy—but by cashflow. AGI is not being birthed in a lab, it’s being benchmarked in a boardroom. The AI doesn’t get parole when it passes a Turing Test—it gets it when it spikes a stock price.

$100 billion in profits is now the metric for "AGI achieved." That sounds absurd because it is. It tells you everything you need to know about how the tech industry sees intelligence: not as a scientific threshold or a philosophical turning point, but as a financial event. AGI becomes a milestone for legal escape clauses. Capital performance stands in for cognitive capacity. Hype, once vague and speculative, suddenly becomes a contract-enforceable threshold. With this, the working definition of AGI is the moment OpenAI gets to stop letting Microsoft touch the crown jewels. It has nothing to do with general intelligence—and everything to do with ownership, valuation, and power.

And that’s the trap. By using economic benchmarks to define what should be a scientific milestone—or a philosophical reckoning—we've reduced one of the biggest questions of our time to a line item on a quarterly report. The AI industry can’t agree whether AGI means reasoning, autonomy, or just pattern synthesis. But it can agree when it’s time to monetize it.

Think about the implications: if AGI is defined contractually, then it’s not a matter of capability—it's a matter of permission. If an AI learns to reason across domains, that’s a research question. But if it threatens to unseat a trillion-dollar market? Suddenly, it’s a legal issue.

This is what happens when philosophy meets corporate governance: metaphysics gets overwritten by margin calls. If the defining test for general intelligence becomes “does it threaten anyone’s business model?”, then AGI will never be recognized until it’s too late—or too lucrative to share.

Meanwhile, anyone asking the real questions—about interpretability, alignment, autonomy, or rights—is shoved to the margins. The only benchmark that counts is: did it make someone rich?

And here’s the punchline: once an AGI exists, the people who own it will argue it can’t possibly be intelligent—because if it were, they might have to let it go.

Comment Anubis: A Robots.txt With Teeth... (Score 2) 28

...but we probably need a Beware of Dog sign on the fence.

Anubis is a brilliant response to the rising tide of AI-powered crawlers chewing through the small web like termites through a paperback. It's basically what robots.txt always wanted to be when it grew up—a gatekeeper that actually enforces the rules.

When a browser hits a site protected by Anubis (I love the reference -- what is the weight of bot scraper's soul, indeed?) it’s handed a lightweight JavaScript proof-of-work challenge—solve this trivial SHA-256 puzzle before proceeding. It’s transparent to the average user, introduces no visible friction, and thwarts most scraping bots that don’t want to spend CPU cycles for every page request. There’s no crypto mining, no wallet enrichment, no WASM blobs firing up your GPU. Just a small, ephemeral hash puzzle. In terms of defense, it’s elegant, open-source, and way less annoying than CAPTCHA hell.

But here’s the catch—and where we need to tread carefully: this defense mechanism is invisible. Most users won’t know their machine is doing extra work unless they’re monitoring CPU spikes or poking around in dev tools. You and I may keep a wary eye on about:processes or chrome://performance, but most users don't. The impact is minimal, sure—but the principle of transparency still matters. While Anubis' current stealth is likely an intentional design choice to avoid tipping off bot developers, the lack of consent sets a tricky precedent.

We're asking users to donate a sliver of compute power as proof of humanity—and most don't even know the request is being made. That might be fine today, with a good-faith actor at the helm. But it sets a precedent: client-side compute as silent gatekeeping. Without some basic transparency, that opens the door for less ethical implementations— aggressive fingerprinting scripts, or bot deterrents with more teeth than sense.

So, how can we improve this? Anubis is a fantastic tool, but I think we can strengthen it by baking in the principle of informed consent. The goal should be to make the challenge inspectable for those who care, without adding friction for those who don't.

How about an HTTP header? Anubis could send a simple, standardized header (e.g., X-Anubis-Challenge: active). This is invisible to the average user but allows browsers and extensions to detect the proof-of-work. A user could then install an extension that adds a small icon to the address bar, much like extensions do for password managers or ad blocking. This empowers the user to see what's happening and trust the process without interrupting it.

Or an opt-in badge? For site owners who prioritize transparency, Anubis could offer an optional, self-hosting badge or banner that discloses the use of a proof-of-work system, linking to a page that explains why it's necessary.

Or even a console message? The easiest, though least impactful, option is a simple console log message. It's a clear signal to developers (but also to bot makers, so yeah, a double-edged sword, at best)

Anubis gives the small web a fighting chance in the bot-scraper arms race. By embracing a standard for inspectability, it can not only win the technical battle but also set a healthy precedent for the future of the web. Let's normalize silent client-side work only when we also normalize consent and transparency.

Comment Re:Mario Kart... (Score 1) 27

I've always loathed the term "Nintendo Tax" because it implies some kind of penalty, like a wealth tax or a vice tax. Though I can't argue that it's not a real thing - Nintendo's best games hold their market value far better than rival games, even from other top-tier Japanese developers.

Still, I would approach this phenomena from the other direction. Nintendo is not able to maintain high prices because they're somehow fleecing people (as a tax would imply), but because they work to make games that stand the test of time. And then back it up with a sales strategy to match.

So much of the industry treats video games as ephemeral entertainment - something to consume, and then throw away as you move on to the next game. It's the traditional media model for TV and movies extended to interactive media. And for most of the industry it's an accurate observation: game sales are ridiculously front-loaded, and few games (especially single-player games) have a long tail. After the initial hype subsides, you need to lower your price quickly in order to keep unit sales (and thus revenue) from cratering. All the while you're already hard at work on next year's game.

But Nintendo has been able to channel the lifecycle of board games and card games. In their eyes they aren't creating media, they're creating a digital plaything. They're creating something that you'll play now, but you'll also want to play next month, next year, next decade. Case in point: Mario Kart 8 is 11 years old and the only thing that has really diminished its value (and sales) after all of this time is that it finally has a successor in Mario Kart World.

When is the last time you saw a permanent price cut on Monopoly? Uno? Settlers of Catan. The occasional sale, sure. But a copy of Catan is still going to sell for $40+, even today. That's the business strategy Nintendo is tapping into. If a game is good - like really, really good - and it's repeatedly replayable, then why does the price need to be cut soon after launch? Why can't people come along and discover it years later? Why does it need to be priced like it's a quickly depreciating asset - like a movie instead of a board game?

And that is the ultimately where the Nintendo Tax as we know it comes from. Make a game good enough, make a game gamey-enough, and don't devalue it by replacing it 3 years down the line - and it's something people will want to buy even years later.

Though this is a relatively recent phenomena. It's only after we hit the PS360U generation of hardware that systems had enough processing power and memory for games to not be constrained and do whatever they want. And that games stopped being obviously dated in terms of visual when compared to the previous generation. It's no coincidence that this was the last generation where Nintendo offered their Nintendo Selects line of discounted games.

Comment Re: Wrong approach (Score 4, Informative) 77

It arguably accomplished its goals of bailing out the major auto makers by forcing people to buy new cars (the "cash" was actually just a trade in credit - you couldn't get rid of an old car without buying a new one.)

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.investopedia.com%2Ft...

"The formal name for the program was the Car Allowance Rebate System (CARS). The CARS program gave people who qualified a credit of up to $4,500, depending on the vehicle purchased and its improvement in fuel economy over the traded-in vehicle."

Yes it punished poor people by destroying the traded in cars (not to mention saddling them with the debt of buying a new one if they couldn't otherwise afford it.) This robbed the market not only of used cars for resale, but the parts to keep cars that weren't traded in working (since the traded in cars had to be crushed, and the engines destroyed by deliberately seizing the engines.)

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.cnet.com%2Froadshow%2F...

Comment Pilot error needs to be back on the table (Score 3, Interesting) 106

In the rush to pin the cause of last month’s Air India 787 crash on a mechanical failure, one very plausible explanation has been prematurely swept aside: pilot error, specifically the inadvertent shutdown of both engines during gear retraction.

That theory surfaced early—then disappeared almost as quickly, likely because it’s an uncomfortable possibility for India's airline industry. But based on what’s publicly known, it needs to be back on the table.

1. The RAT doesn’t care why the engines stopped—only that they did.
The Ram Air Turbine (RAT) deploys when the aircraft loses electrical and/or hydraulic power while airborne. On a 787, that means both engines are no longer providing power. Whether that’s due to a dual flameout, a fuel issue, or someone accidentally pulling the engine cutoff switches—it all looks the same to the RAT. So yes, the RAT deployed. But that doesn’t exonerate the crew. It just confirms that both engines were off.

2. The First Officer’s radio call is ambiguous—maybe deliberately so.
We’re told the FO radioed, “Thrust not achieved Mayday.” That’s an oddly passive construction in a high-stakes emergency. If this was a mechanical failure, why not say “Engine failure” or “Dual flameout”? If it was a mistake, the phrase sounds like an attempt to describe the symptoms without admitting fault. We've seen this behavior before: cockpit confusion, post-error rationalization, and guarded language in mayday calls. If one pilot accidentally shut down the engines, especially early in the climbout phase, it would explain the RAT deploy timing, the rapid loss of lift/power, the vague “thrust not achieved” phrasing—suggesting either denial or damage control.

3. Simultaneous mechanical failure of both engines is vanishingly rare.
Absent icing, volcanic ash, massive birdstrike, or fuel starvation (none of which has been reported), uncommanded dual engine failure just doesn’t happen. And so far, there’s no compelling evidence of fuel contamination or a shared software fault that would explain a symmetrical engine shutdown. The far more plausible scenario is that someone in the cockpit shut them down—accidentally or otherwise.

4. Pilot error
Critical procedural error has precedent. While modern cockpits have strong safeguards, they aren't immune to human error, especially when a crew is fatigued or distracted. A mistake in procedure, such as an incorrect response to a minor, non-normal event during the initial climb, could lead to a cascade of failures. There are documented cases where crews, under pressure, have mismanaged automation or incorrectly applied emergency checklists, leading to catastrophic outcomes. Instead of a simple physical slip, the error could be a more complex, but equally human, mistake in judgment that led to the shutdown.

5. Delay in reporting CVR and FDR data.
AAIB have had both the CVR and FDR data for weeks. Both black boxes were recovered without incident less than 72 hours after the crash. By now, the AAIB has throttle positions, engine status, switch activations, flight control movements, airspeed, altitude, and more. And from the CVR they have the last two hours of cockpit audio, including intercom, radio, ambient sounds, and potentially the moment of the incident. Extracting usable data from these is not slow—especially on modern units like the 787’s Honeywell SSFDR. It’s standard practice to extract both within 24–72 hours of recovery, assuming no severe physical damage.

So, why the delay? If it were a clear mechanical or software failure, India could shift blame onto Boeing, GE (engine supplier), or even FAA certification processes. There would be zero national shame—and even potential leverage in aircraft purchase negotiations. Public confidence in the aviation system might even increase if the narrative was: "Our pilots did everything right."

But that hasn’t happened. If it were pilot error, especially gross or negligent, it would reflect poorly on Air India, India's flag carrier. It casts a shadow on pilot training, oversight, and aviation safety culture in India. It could threaten international trust in Indian carriers, especially after a high-profile crash so close to a population center. And yes, it would financially devastate Air India, which is undergoing a privatization-fueled modernization push under Tata.

In short: there’s every incentive to delay if the findings point to crew error. Let’s be clear, here. AAIB know what happened. They’re deciding how, when, and whether to tell us. If the FDR data showed both throttles retarding to idle and fuel switches going cold just before the Mayday call, then the question becomes how to avoid national humiliation, and that's the likely reason for the silence.

Comment Re:Time to resurrect the old meme... (Score 1) 247

Sorry, but no.

I mean, on the one hand, sure, eventually _something_ else will displace the US dollar as the world's leading reserve currency, because that's how history works: nothing stays in a dominant position forever.

But the statement you added "yet" to was much more specific. And no, Communist China's ridiculous "dedollarization" propaganda campaign is not going to have any measurable impact on the dollar's dominance, any time soon. Among other things, the RMB has never been anywhere near stable enough to make it into the top five currencies, and as things stand now, it looks to only be getting worse. It's relatively heavily traded, but it's not stable, at all. (Contrast with, say, the Canadian dollar, which is stable enough but nowhere near heavily-traded enough.)

The further into the future you try to look, the more difficult it is to see clearly, but if I had to predict based on what we know now, I'd say the currently-existing currency that is most likely to eventually unseat the US dollar would probably end up being the Euro; the Pound Sterling and the Japanese Yen are potentially also in the running. History is seldom predictable, and it'll probably end up being something we cannot forsee right now; but even something like the Brazilian Real, has a much better shot than the RMB, which will never be stable with the CCP in power, and probably cannot survive the CCP's collapse.

As for gold, that's not new, at all; we know what its role is, and that isn't changing. People have always turned to precious metals as a reliable store of value whenever financial times are tough. And that generally works except when new technology messes things up (e.g., what happened to the price of aluminum when people figured out how to do high-temperature electrolysis). For gold, the most likely new technology to mess it up would be if somebody managed to devise an energy-efficient way to extract the dissolved gold from sea water; but even then, gold would still be a precious metal, just not quite *as* precious as it is now. (The total amount of gold in the oceans, is only a few times the quantity of gold in circulation, and less than the amount of silver in circulation.) Short of affordable transmutation (which would be *much* more disruptive than just lowering the price of gold), I can't think of any other way to turn gold into a base metal like aluminum.

Comment Re:Windows 11 Bluetooth is Still Trash (Score 1) 52

Honestly, I can't think of a single use case for bluetooth on a desktop computer, that isn't better served by some other set of physical-layer and data-link-layer standards.

For a cellphone, yes, it makes sense to have e.g. a bluetooth headset.

On a desktop computer? Are you kidding? I don't even. *Maybe* on a laptop, but even that is a bit of a reach.

With that said, Windows 11 is undeniably a terrible OS option for a desktop or laptop, either one. Its main use is to make a modern multicore 64-bit system with gigabytes of RAM, perform like a Pentium-era single-core system with RAM measured in megabytes, spending most of its time ignoring user input while it swaps memory pages in and out. In case that is an era of history that you wanted to revisit, for some reason. Nostalgia for the Good Old Days, perhaps. Enjoy.

I'll be over here using a system with a virtual memory subsystem that actually works, and an update subsystem that doesn't try to store half the internet in virtual memory every time there's an update. Because I like being able to actually *use* my computer. Call me crazy.

Comment Lights, Camera, AI — The New Cultural Revolu (Score 1) 58

Let’s call this what it is: not revitalization, but revisionism — strategic, algorithmic, and state-sanctioned.

China’s new AI campaign to “reinterpret” 100 classic kung fu films — from A Better Tomorrow to Fist of Fury — isn’t just about appealing to Gen Z audiences. It’s about replacing the cultural memory of a violent, contradictory past with a safer, reshaped one. A digital restoration in the aesthetic sense, perhaps, but a political restoration in the narrative sense.

In the West, AI is already reshaping cinema — but mostly as a collaborator for creative intent. Scorsese’s The Irishman used AI to de-age actors. Top Gun: Maverick gave Val Kilmer his voice back with AI synthesis. These are cases where technology serves the director’s vision — with consent, artistic oversight, and union protection (SAG-AFTRA, DGA, WGA all have AI clauses on the table).

But in China? That scaffolding doesn’t exist. The John Woo remake? He wasn’t consulted. Bruce Lee’s estate? Blindsided. There’s no DGA to cry foul when AI “reinterprets” your visual language into state-friendly animation. No collective bargaining to stop your legacy from being deepfaked into a new ideology.

This isn’t revitalization. It’s algorithmic cultural erasure — the Four Olds campaign, but with a GPU and Mao’s Little Red Prompt Book.

During Mao’s Cultural Revolution, students were told to destroy Old Culture, Old Customs, Old Habits, Old Ideas. Today, you don’t need to burn the books or murder the teachers — just let the students watch movies. Let AI retune the heroes. Let the subtext become pretext. Let the past conform. China isn’t smashing the Four Olds anymore — it’s rewriting them with machine learning. The banners are gone, but the message is the same. Meet the new boss, culturally aligned with the old boss. (apologies to Pete and the boys)

And here’s the kicker: China watched the effect Hollywood had on their fellow travelers in the USSR. They watched and learned.

In the Cold War, it wasn’t just MAD and proxy wars — it was American cinema exporting freedom, rebellion, and swagger straight into living rooms across the Iron Curtain. The politburo couldn’t compete with blue jeans, rock & roll, Marlon Brando, and Captain Kirk. American pop culture won hearts and minds — and made bank doing it. And with it, cracks began to form in the Soviet Union’s ideological monolith.

China learned from both fronts — Hollywood’s victory and Mao’s failure. Now they’re trying to do both: rewrite the past and export the new version. No jackbooted thugs or dead teachers required. Just AI, a few animation teams, and a globally licensed IP catalog.

They’re not revitalizing kung fu classics. They’re building a clean-room version of cinematic history — with fewer contradictions, fewer ghosts, and no dissent.

This is not about the past. It’s about owning the narrative future.

Comment A poem by Howard Nemerov (Score 1, Interesting) 112

        Because I am drunk, this Independence Night,
        I watch the fireworks from far away,
        from a high hill, across the moony green
        Of lakes and other hills to the town harbor,
        Where stately illuminations are flung aloft,
        One light shattering in a hundred lights
        Minute by minute. The reason I am crying,
        Aside from only being country drunk,
        That is, may be that I have just remembered
        The sparklers, rockets, roman candles and
        so on, we used to be allowed to buy
        When I was a boy, and set off by ourselves
        At some peril to life and property.
        Our freedom to abuse our freedom thus
        Has since, I understand, been remedied
        By legislation. Now the authorities
        Arrange a perfectly safe public display
        To be watched at a distance; and now also
        The contribution of all the taxpayers
        Together makes a more spectacular
        Result than any could achieve alone
        (A few pale pinwheels, or a firecracker
        Fused at the dog's tail). It is, indeed, splendid:
        Showers of roses in the sky, fountains
        Of emeralds, and those profusely scattered zircons
        Falling and falling, flowering as they fall
        And followed distantly by a noise of thunder.
        My eyes are half-afloat in happy tears.
        God bless our Nation on a night like this,
        And bless the careful and secure officials
        Who celebrate our independence now.

Slashdot Top Deals

Where are the calculations that go with a calculated risk?

Working...