Latest UK & Global AI News

Your Source for the Latest Artificial Intelligence News & Updates

Discover Global AI News with AI Business Help UK, your go-to source for Artificial Intelligence updates spanning the planet. Dive into the latest global AI innovations, industry trends, and technological advancements driving change across continents. From London to Silicon Valley, get the full picture of AI’s global impact right here.

Who Needs Automatic Driving? You Love to Drive! However, for Many Handicapped, Tesla’s Full Self Driving Is the Only Option. It’s Use It, or Don’t Drive!
Who Needs Automatic Driving? You Love to Drive! However, for Many Handicapped, Tesla’s Full Self Driving Is the Only Option. It’s Use It, or Don’t Drive!

Source: Clean Technica

Authors: arthur frederick (fritz) hasler

View Full Article

Editor’s note: In my opinion, a person should not be using Tesla FSD to drive somewhere if they aren’t capable of driving the trip fully themselves. Fritz makes the argument here that it is easier to supervise FSD and that is why someone with a handicap can use it when ... [continued] The post Who Needs Automatic Driving? You Love to Drive! However, for Many Handicapped, Tesla’s Full Self Driving Is the Only Option. It’s Use It, or Don’t Drive! appeared first on CleanTechnica.

View Full Article

Published On: 2026-11-21

AI drives rapid patching as cyberattacks exploit new vulnerabilities
AI drives rapid patching as cyberattacks exploit new vulnerabilities

Source: Indiavision India News & Information

Authors: news editor

View Full Article

AI is forcing companies to patch their systems faster as attackers race to exploit newly discovered vulnerabilities. Welcome to internet outage hell. AI drives rapid patching as cyberattacks exploit new vulnerabilities

View Full Article

Published On: 2026-11-21

New Report Claims Jensen Huang Regularly Threatened Nvidia Staff With Over-The-Top Violence
New Report Claims Jensen Huang Regularly Threatened Nvidia Staff With Over-The-Top Violence

Source: Kotaku

Authors: zack kotzer

View Full Article

As the investigation into the exiting Nvidia CEO deepens, employees say Huang maintained a habit of outlandish threats, from dismembering limbs to brain urination

View Full Article

Published On: 2026-11-21

Japan’s FamilyMart to deploy AI robots to restock drinks
Japan’s FamilyMart to deploy AI robots to restock drinks

Source: Qatar Tribune

Authors: qatar tribune

View Full Article

AgenciesEven as AI is still in its early stages, many eager start-ups are looking at the next big thing, which they have dubbed “physical AI.” That really just means robots control...

View Full Article

Published On: 2026-11-21

US financial watchdog probing Nvidia accounting – Reuters
US financial watchdog probing Nvidia accounting – Reuters

Source: Rt

Authors: rt

View Full Article

Reuters reports that the US securities watchdog is probing Nvidia’s accounting amid scrutiny of its Singapore revenue disclosures Read Full Article at RT.com

View Full Article

Published On: 2026-11-21

Structuring Your Commerce Backend So an AI Agent Can Actually Check Out
Structuring Your Commerce Backend So an AI Agent Can Actually Check Out

Source: Dev Community

Authors: andrii b.

View Full Article

Here's a checkout endpoint that works fine for your own storefront: place-order.ts It passes every test you have. Now put an AI agent in front of it. The agent sends the request, your PSP takes four seconds, the agent's HTTP client gives up at three and retries. You now have two orders and two charges. The agent reads the second response, tells the buyer "done," and never mentions the first one. Nobody did anything wrong from their own point of view. The endpoint just assumed its caller was a browser tab with a human watching a spinner. That's the whole problem in miniature. An agent is a client that retries aggressively, holds no session cookie, can't see your page, reads every field you return literally, and acts on behalf of someone who isn't there. The protocols that have appeared for agent checkout, OpenAI and Stripe's Agentic Commerce Protocol (ACP) and Google and Shopify's Universal Commerce Protocol (UCP), look different on the surface. Underneath, they're asking your backend for the same five things. This article is about building those five things once, in your own domain, so that the protocols become thin adapters instead of rewrites. If you want the protocol history (who released what and when, how MCP, ACP and UCP stack), I covered that in Adobe Commerce Added an MCP Layer, along with stale prices and prompt injection through product copy. I won't repeat it. This one stays below the protocol line. First, a reality check on "agents now buy things" The pitch you'll hear is that autonomous shopping agents already discover, compare and purchase, and the backend that "wins" is the one they can use. Parts of that are true. The part that's overstated is how finished the ground under it is. Look at the status labels in the ACP repository itself. The README marks the protocol as beta. The Agentic Checkout RFC is labelled Draft. The Product Feeds RFC is a Proposal with version "unreleased." The spec has shipped dated versions (2025-09-29, 2025-12-12, 2026-01-16, 2026-01-30, 2026-04-17), and some of those carried breaking changes: the 2025-12-12 release renamed fulfillment_address to fulfillment_details and replaced a single fulfillment_option_id with a selected_fulfillment_options[] array. UCP, meanwhile, uses a different status vocabulary for the same lifecycle. So I'd put it differently from the hype. The protocol details will keep moving for a while. What's already stable is the shape they all require from the merchant, and that shape is good backend design anyway. If you build it into your domain model, adopting ACP this quarter and UCP next quarter is adapter work. If you bolt ACP straight onto your existing cart controller, you'll rewrite it the next time the spec renames a field. Here's the shape: A stable, purchasable item ID that discovery and checkout both agree on. A checkout session resource that returns the full authoritative state on every call. Strict idempotency on every write, with defined replay and conflict behaviour. Payment by scoped token, never by raw card or stored-card reference passed through the model. Explicit identities for the platform, the agent and the buyer, each authenticated differently. Let's go through them in the order an agent hits them. Product data: the variant ID is the whole game Everyone talks about "machine-readable product data" as if the hard part is the richness of descriptions. It isn't. The hard part is that the ID an agent finds during discovery must be exactly the ID your checkout accepts. The ACP Product Feeds proposal says this plainly. It splits a Product (the grouping concept) from a Variant (the thing you can actually buy), and requires that "Variant IDs SHOULD be stable across feed updates." If your catalog ID and checkout item ID differ, the merchant "MUST provide a deterministic mapping outside this RFC or ensure the feed Variant.id is accepted as an ACP checkout item ID." Think about what that means for a typical platform. Magento has a configurable parent SKU and child simple SKUs. Shopify has products and variant GIDs. Plenty of custom backends use a product ID plus a bag of selected options that only become a concrete stock unit inside the cart service. That last design is the one that hurts: an agent can't pass "product 812 with color=red and size=M" to a checkout that expects a line item ID, unless you give it one. A feed entry in the ACP proposal's shape looks like this. Note that prices are integers in minor units, and the variant ID is the checkout key: feed-product.json Two things about feeds catch people off guard. The feed is push, not pull. In the ACP proposal, the Feed API is hosted by the agent platform and the merchant calls it: POST /feeds, PATCH /feeds/{id}/products for partial upserts, or a full-replacement file drop of metadata.json plus a products.jsonl. The spec is explicit that "Agents MUST NOT call Product Feed API endpoints on merchants." So "exposing" your catalog is really an outbound sync job with its own retry, backoff and change-detection, not an endpoint you open. Plan it like you'd plan a search-index sync, because that's what it is. The feed is never authoritative. The same proposal lists "authoritative checkout pricing" as a non-goal: feed prices are "discovery-time signals," and agents "MUST NOT represent feed price or availability as guaranteed." Availability in a feed doesn't reserve inventory either. That's a relief, honestly. It means the feed can lag a bit, as long as your checkout tells the truth and says so loudly when the truth differs. OpenAI's own product feed spec for ChatGPT names nine required fields: item_id, title, description, url, brand, seller_name, image_url, availability and price, and it accepts JSONL, TSV/CSV and gzipped variants. It also has per-row switches, is_eligible_search and is_eligible_checkout, so you can let an item be found without letting it be bought through the agent. Use that switch. Made-to-order items, age-restricted products and anything with a configurator probably belong in "searchable, not agent-checkoutable" on day one. Don't forget the page itself Not every agent uses a feed. Some read your product page like a crawler does, which is why schema.org markup still matters. Google's merchant listing docs require only name, image and offers on the Product, and price (greater than zero) plus priceCurrency on the Offer. The useful stuff for an agent sits in the recommended set: gtin, availability, itemCondition, shippingDetails, hasMerchantReturnPolicy. product-jsonld.json Put the same variant ID in sku that your feed and checkout use. One ID, three surfaces. Warning Google's docs note that dynamically generated markup "can make Shopping crawls less frequent and less reliable, which can be an issue for fast-changing content like product availability and price." If your JSON-LD is injected client-side by a headless storefront, render it on the server. The same logic applies to any agent that fetches HTML without running your JavaScript. The checkout session is a state machine, not an endpoint The single biggest structural change is this: agents don't "place an order." They drive a checkout session through a lifecycle, and every call returns the whole current state. ACP defines five operations: POST /checkout_sessions to create (returns 201) POST /checkout_sessions/{id} to update items, fulfillment details or selected shipping GET /checkout_sessions/{id} to retrieve POST /checkout_sessions/{id}/complete to pay, which "MUST create an order" POST /checkout_sessions/{id}/cancel, which returns 405 if the session is already completed or canceled UCP's checkout capability (dev.ucp.shopping.checkout) has the same five logical operations with different status names. Put them side by side and you can see the common model: Meaning ACP status UCP status Missing info or unresolved issues not_ready_for_payment incomplete Needs the human, outside the API (messages with requires_buyer_input / requires_buyer_review) requires_escalation + continue_url Can be paid ready_for_payment ready_for_complete Payment/issuer step in flight authentication_required complete_in_progress Done completed Dead canceled My strong opinion: model this table in your domain, with your own status names, and map to each protocol at the edge. Don't store ready_for_payment in your database because ACP happens to say it. The next protocol will say something else. A few rules fall out of the specs that are worth baking in from the start. Every response is the full, authoritative state. ACP's first stated goal is that the agent "renders an authoritative cart state on every response." Line items carry base_amount, discount, subtotal, tax and total; the session carries totals[], fulfillment_options[], messages[] and policy links[]. There's no "OK, call GET to see what happened." That rules out the common pattern where an update endpoint returns 204 and the frontend refetches. Money is integers in minor units. ACP: "Amounts MUST be integers in minor units." $19.99 is 1999. If any part of your pricing pipeline still does float math and rounds at the end, the agent will see the result of that rounding in a field it treats as exact. Errors tell the agent who can fix them. Since the 2026-02-04 change, ACP messages can carry a resolution of recoverable (the agent can fix it via the API), requires_buyer_input or requires_buyer_review. That field is small and does a lot of work. An out-of-stock line is recoverable if you offer a substitute variant. A missing age confirmation is requires_buyer_review, and the agent should stop and ask instead of guessing. UCP makes the same split with a status: requires_escalation, where the business "MUST provide continue_url" so the human can finish in your UI. Sessions expire. UCP's expires_at defaults to six hours from creation if the platform doesn't send one. Pick your own TTL deliberately, and tie any soft inventory hold to it. Remember the feed never reserved anything; if you reserve at all, the session is where it happens. Update semantics: the protocols disagree, so your domain shouldn't care Here's a gotcha that will bite anyone who writes one update handler for both protocols. ACP's checkout update is a partial update with a precise rule about null: in its idempotency section, "null value vs absent key" are "Different: null means 'clear this field'; absent means 'do not modify'." The spec even tells SDK authors to make sure their serializers preserve that distinction. UCP's Update Checkout is a full replacement: the platform must "send the entire checkout resource," and it "will replace the existing checkout session state on the business side." And ACP's newer cart capability (POST /carts, PUT /carts/{id}) is full replacement too: "The agent MUST send the complete desired cart state." Cart totals there are explicitly estimates, and carts have no payment data at all. So you have three write semantics for what is conceptually one basket. The fix is boring: your domain exposes intent-level commands (setLines, setAddress, selectShipping, clearAddress), and each adapter translates its protocol's semantics into those commands. A JSON merge in the controller layer is how you end up with an agent that accidentally wipes an address by sending null, or wipes a line item by omitting it. The ACP cart RFC is candid about the next problem: full replacement without concurrency control means two writers can race. It says "future protocol versions MAY introduce optimistic concurrency (e.g., If-Match / ETag)." You don't have to wait. Keep a version column on the session and reject stale writes internally, even if the protocol doesn't carry the version yet. Idempotency is the product, not a middleware afterthought Back to the opener: the duplicate order. For a long time this was "recommended." In ACP's 2026-04-17 release it became mandatory. The changelog entry changed the Idempotency-Key parameter "from required: false to required: true on both Agentic Checkout and Delegate Payment APIs." The rules it now spells out are worth reading line by line, because each one maps to a design decision. Every POST needs a key. Missing key: 400 with code idempotency_key_required. Keys are opaque strings up to 255 characters, UUID v4 recommended. Scope is identity plus path. Servers "MUST scope keys to the authenticated identity + endpoint path." The same key on /complete and on /cancel are different keys. Equivalence is semantic JSON equality of the body. Key order doesn't matter, 1.0 equals 1, but array order does, and null differs from absent. Headers are excluded. The spec suggests RFC 8785 (JSON Canonicalization Scheme) plus SHA-256 as an implementation. Same key, same body: replay. Return "the original response with the same HTTP status code," ideally with Idempotent-Replayed: true, and never re-run side effects like payment capture or inventory reservation. Same key, different body: 422 with idempotency_conflict. Permanent, don't retry. Same key, still running: 409 with idempotency_in_flight and a Retry-After header. 5xx responses are never cached. A retry after a 5xx "MUST be processed as a fresh request." Keep keys at least 24 hours. The 400/422/409 split tracks the IETF Idempotency-Key header draft, which recommends the same three codes. That draft never became an RFC (its last revision, -07, is from October 2025), so the ACP text is currently the more complete normative source. Now the surprising part. Compare that 5xx rule with Stripe, the company that co-maintains ACP. Stripe's API docs say its idempotency layer saves "the resulting status code and body of the first request made for any given idempotency key, regardless of whether it succeeds or fails. Subsequent requests with the same key return the same result, including 500 errors." Opposite behaviour, same header name. Neither is wrong. Stripe is protecting a single money movement where "the first attempt failed" is itself a durable fact; ACP is protecting an agent that needs a retry to actually retry. The lesson for you is that "we support Idempotency-Key" means nothing until you've written down which of these you do, and your checkout sits between both: ACP semantics on the way in, Stripe semantics on the way out. I walked through the general version of this store in Idempotency Keys: The One-Line Fix That Saves You From Duplicate Side Effects. Here it is again with ACP's rules on Postgres. The key design choice is committing the idempotency record and the business write in the same transaction, which ACP's implementation guidance recommends to avoid "ghost keys (key stored, operation failed) or lost keys (operation succeeded, key not stored)." idempotency_keys.sql CREATE TABLE idempotency_keys ( caller_id text NOT NULL, -- authenticated platform identity path text NOT NULL, -- e.g. /checkout_sessions/{id}/complete key text NOT NULL CHECK (length(key) <= 255), request_hash bytea NOT NULL, -- sha256 of RFC 8785 canonical body status text NOT NULL DEFAULT 'in_flight', -- in_flight | done http_status int, response_body jsonb, created_at timestamptz NOT NULL DEFAULT now(), PRIMARY KEY (caller_id, path, key) ); -- Retention floor is 24h; sweep anything older. CREATE INDEX idempotency_keys_created_at ON idempotency_keys (created_at); idempotent.ts import { createHash } from "node:crypto"; import canonicalize from "canonicalize"; import type { Pool, PoolClient } from "pg"; type Result = { status: number; body: unknown; replayed?: boolean }; export async function idempotent( pool: Pool, scope: { callerId: string; path: string; key: string | undefined }, body: unknown, handler: (tx: PoolClient) => Promise, ): Promise { catch (err) { await tx.query("ROLLBACK"); await pool.query(`DELETE FROM idempotency_keys WHERE caller_id=$1 AND path=$2 AND key=$3`, [scope.callerId, scope.path, scope.key]); throw err; } finally { } The caller adds the Idempotency-Key echo, Idempotent-Replayed: true on replays and a Retry-After on 409. Why RFC 8785 instead of JSON.stringify? Because JSON.stringify preserves key insertion order, so two semantically identical bodies from different agent SDKs would hash differently and you'd throw a 422 at an honest retry. JCS sorts keys and normalizes numbers, which is exactly the equivalence ACP asks for, while keeping null and absent keys distinct. The part this code doesn't solve: your PSP call Look at handler(tx). If it calls your payment provider, that call is outside your database transaction. Rolling back the SQL doesn't roll back an authorization at the PSP. ACP names this directly: when an operation "triggers foreign state mutations (e.g., PSP authorization), servers SHOULD implement recovery-point semantics," recording intermediate state so retries "can resume rather than restart." In practice: persist "payment attempt started, PSP idempotency key = X" and commit it before calling the PSP, then call the PSP with that derived key. A retry that finds the recovery point reuses the same PSP key, and the PSP's own idempotency (the Stripe behaviour above, which caches even failures) guarantees you don't charge twice. Two idempotency layers with different semantics, stacked on purpose. Note One inconsistency to watch: ACP's MCP transport binding (docs/mcp-binding.md in the spec repo) still lists meta.idempotency_key as not required, "Recommended for create and complete," and still lists the request_not_idempotent error type that the REST spec removed. If you expose checkout over MCP (tools named create_checkout_session, complete_checkout_session and so on), enforce the REST rules anyway. Your database doesn't care which transport the retry came through. Payment: accept a scoped token, and freeze the total before it's issued The agent never hands you a card number through the model. In ACP, the buyer's payment credential goes to a delegated-payment endpoint (POST /agentic_commerce/delegate_payment, implemented by the PSP), which returns a token usable only within an Allowance: reason must be one_time, plus a max_amount in minor units, a currency, the checkout_session_id, the merchant_id and an expires_at. The token "MUST become invalid at or after allowance.expires_at." Your /complete call receives it in payment_data.instrument.credential, for example as { "type": "spt", "token": "spt_123" }. On Stripe the concrete version is a Shared Payment Token. Stripe's seller docs say the agent grants it with usage_limits (currency, max_amount, expires_at), and, importantly, "the agent sets the maximum amount to match the total amount of the transaction." Read that sentence again with your tax engine in mind. The token's ceiling is whatever total your session showed the buyer. If your /complete handler recalculates tax, re-rates shipping or re-applies a promotion and lands one cent higher, the charge exceeds the grant. The buyer approved one number; you're trying to charge another. That isn't a bug in the protocol. It's the protocol working as designed, and it forces a rule on your backend: the total is frozen at ready_for_payment and /complete charges exactly that frozen total or refuses. If something genuinely changed (a price moved, stock ran out), send the session back to a not-payable state with a message, and let the agent get a new approval. Here's what a complete handler looks like against Stripe's documented REST endpoints, using plain fetch so nothing depends on a preview SDK type: complete-checkout.ts export async CheckoutSession and mapPaymentIntentToSession are yours; everything under STRIPE is from Stripe's docs. Two details worth calling out. The PSP idempotency key is derived from the session, not from the agent's Idempotency-Key, because the agent can legitimately send a new key for a new attempt after a decline, and you want the PSP to see a new attempt too. So in a real system the derived key includes an attempt counter from your recovery point: complete:${session.id}:${attempt}. And subscribe to shared_payment.granted_token.deactivated, which Stripe sends when the token is consumed, expired or revoked, so a session whose grant died can move back to not-payable instead of failing at the next call. 3-D Secure adds one more state. When the issuer wants authentication, ACP says the server "MUST set session.status to authentication_required" and include authentication_metadata; the agent then retries /complete with an authentication_result. Call /complete without it and the spec requires a 4XX with code: "requires_3ds" and param: "$.authentication_result". If your current checkout handles 3DS with a browser redirect, that redirect has nowhere to go. It has to become a state in the session. Auth: three identities, three mechanisms "Auth for agents" gets discussed as one problem. It's three, and mixing them up is how you end up with a bearer token in a place a model can read. The platform. Who is calling your API: ChatGPT, a Google surface, a partner's agent. ACP requires Authorization: Bearer on every request and recommends a Signature over canonical JSON with a Timestamp, verified "with a bounded clock-skew window." This identity is what you scope idempotency keys to, and what you rate-limit. The MCP binding makes a sharp point here: the Authorization header is "intentionally excluded" from tool arguments because "including bearer tokens in tool arguments would expose them in tool schemas visible to LLMs." Auth lives at the connection, never in the payload. The agent traffic. When an agent browses your site instead of calling your API, you need to tell it apart from a scraper. The emerging answer is signed HTTP requests on top of RFC 9421 (HTTP Message Signatures). Cloudflare's Web Bot Auth uses Signature-Input (with tag set to web-bot-auth), Signature and a Signature-Agent header pointing at a key directory at /.well-known/http-message-signatures-directory, with Ed25519 keys. Visa's Trusted Agent Protocol reference implementation also generates RFC 9421 signatures, bound to your domain and to the operation (browsing or payment), with timestamps and a unique session identifier against replay. If you run a WAF that blocks "bots," this is the layer where you'll need an allowlist by verified signature rather than by user agent string. The buyer. The person the agent is acting for. For guest checkout, the scoped payment token plus the buyer details in the session is the identity, and that's fine. The hard case is anything that needs an account: loyalty pricing, B2B contract prices, saved addresses. ACP has a requires_sign_in error code for exactly this, and UCP routes it through requires_escalation with a continue_url. My opinion: resist the urge to let agents log in with stored credentials. Make account-bound checkout an escalation that the human completes on your site, and only flatten it into the API once the protocols carry a proper delegated-consent mechanism for it. Discovery is the one piece that should be static Both protocols expect a well-known document. ACP's is /.well-known/acp.json, public, no auth, describing protocol versions, transports (rest, mcp) and services (like carts). The RFC says to serve it with at least Cache-Control: public, max-age=3600 and not to change it more than once an hour. UCP publishes a business profile at /.well-known/ucp, which is where payment handlers are discovered. Note what ACP deliberately keeps out of discovery: payment methods, because they're merchant-, flag- and context-dependent. Those come back per session in capabilities on POST /checkout_sessions. Serve the discovery file from your CDN as a static asset generated at deploy time, and keep all per-session decisions in the session. What to build first If I were starting this on an existing store tomorrow, the order would be: Give every purchasable unit a stable ID and make checkout accept it directly. This is the one change that helps every protocol, every feed, and your own schema.org markup at once. Extract a checkout session aggregate out of your cart and order code, with your own status machine, integer money, a version column, an expiry, and a messages list with "who can fix this" semantics. Put the idempotency store in front of every write, in the same transaction as the business change, with recovery points before any PSP call. Freeze totals at the payable state and treat any change after that as a transition back, not a silent recalculation. Then write the ACP adapter, and later the UCP one. Each should be a translation layer: headers to scope, protocol statuses to your statuses, partial-update or full-replace to intent commands. None of this is exotic. It's the same discipline a good public payments API has always needed. The difference is that until now your only client was a frontend you wrote, so you could get away without it. The new client retries on every timeout, reads every field literally, and can't see the spinner. Build the backend for that client, and the choice between ACP and UCP stops being an architecture decision and becomes a sprint. Originally published at andriiboyko.com.

View Full Article

Published On: 2026-11-21

Trump seeks to curb foreign data centre investments by US tech firms
Trump seeks to curb foreign data centre investments by US tech firms

Source: Qatar Tribune

Authors: qatar tribune

View Full Article

AgenciesPresident Donald Trump on Friday threatened “a tremendous tax” on U.S. companies that build artificial intelligence data centers abroad, highlighting a divide between a pre...

View Full Article

Published On: 2026-11-21

Bitcoin Proof-of-Work Can Help Stop AI Cyberattacks: Ex-Space Force Director
Bitcoin Proof-of-Work Can Help Stop AI Cyberattacks: Ex-Space Force Director

Source: Bitcoin News

Authors: sergio goschenko

View Full Article

Major Jason Lowery, author of the Softwar thesis, has proposed using the proof-of-work consensus mechanism that secures bitcoin to defend key U.S. digital property against artificial intelligence-led threats, which are already affecting financial institutions and government agencies. Jason Lowery Proposes Using Proof of Work to Defend Against AI Bitcoin’s proof-of-work (PoW) consensus mechanism, which has […]

View Full Article

Published On: 2026-11-21

Teachers are quietly given official permission to use AI chatbots when marking exam coursework in scandalous move, critics say
Teachers are 'quietly' given official permission to use AI chatbots when marking exam coursework in 'scandalous' move, critics say

Source: Mail Online

Authors: elizabeth ivens

View Full Article

While students are warned they face strict penalties for using AI to create coursework, guidance has 'quietly' ruled teachers can use AI to mark it.

View Full Article

Published On: 2026-11-21

They built cyborg cockroaches with built-in AI…
They built cyborg cockroaches with built-in AI…

Source: Whatfinger News

Authors: michael

View Full Article

Sharing the latest news and advancements in AI Discover More: 🛠️ Explore AI Tools & News: https://futuretools.io/ 📰 Weekly Newsletter: https://futuretools.io/newsletter Socials: ❌ Twiter/X: https://x.com/mreflow 🖼️ Instagram: https://instagram.com/mr.eflow 🧵 Threads: https://www.threads.net/@mr.eflow 🟦 LinkedIn: https://www.linkedin.com/in/matt-wolfe-30841712/ 👍 Facebook: https://www.facebook.com/mattrwolfe Let’s work together! – Brand, sponsorship & business inquiries: business@mattwolfe.com #AINews #AITools #ArtificialIntelligence

View Full Article

Published On: 2026-11-21

JasonTheWeen completes GTA 6 after losing 11 hours of progress as streamer praises games love story
JasonTheWeen completes GTA 6 after losing 11 hours of progress as streamer praises game's love story

Source: The Times Of India

Authors: global sports desk

View Full Article

Streamer JasonTheWeen has finally completed Grand Theft Auto 6 after losing over 11 hours of gameplay progress due to a PS5 error. After reaching out to Rockstar Games and PlayStation for help, he continued his gameplay unhindered. He praised the game's immersive heists and meaningful love story between the main characters, Jason Duval and Lucia Caminos. His positive review indicates he enjoyed the overall gaming experience immensely.

View Full Article

Published On: 2026-11-21

US signed off on sales of nearly 900,000 AI chips to China in six months
US signed off on sales of nearly 900,000 AI chips to China in six months

Source: Business Recorder

Authors: reuters

View Full Article

WASHINGTON: The Trump administration approved shipments of nearly 900,000 advanced AI chips made by Nvidia and AMD...

View Full Article

Published On: 2026-11-21

9/9 Is Not a Security Score. Its Something Developers Should Care About.
9/9 Is Not a Security Score. It's Something Developers Should Care About.

Source: Dev Community

Authors: jackymencz (jackymencz)

View Full Article

https://protocolprobe.com/mcp/servers/io.github.jakcmencz/sentinel-ir-mcp#reactions The 30-second version I recently noticed something interesting on ProtocolProbe. Sentinel-IR-MCP now meets all 9 of 9 applicable record checks. Nice number, isn't it? But here's the interesting part: this isn't a security certificate, a penetration test, or a declaration that an AI agent is suddenly invincible. It's something more practical. It means that important parts of a project's public identity and supply chain can actually be checked. And for developers building AI agent systems, that matters more than another shiny badge. Why should developers care? Think about how we build agent systems today. We connect models to MCP servers, packages, APIs, repositories and external tools. Each connection introduces another piece of software that we are trusting. And sometimes we connect things faster than we check what is behind them. It's a little like giving someone keys to your office because they have a nice business card. The card might be genuine, but perhaps we should check who issued it first. This is where transparent records become valuable. ProtocolProbe checks nine public signals, including: Is the registry entry active, and does it explain how to run the server? Is the source repository public and maintained? Is there a published security policy? Is the licence clearly identified? Is the listed package version available and current? Does the npm package have signed build provenance? Are there known critical or high-severity security advisories? These are not glamorous features. Nobody will put a movie trailer together for an SPDX licence identifier. But they help answer a much more important question: Can another developer independently verify the basic health and origin of the software they are about to connect to an agent? For Sentinel-IR-MCP, the current result is 9/9. It also appears at #121 among 1,275 packages meeting all nine checks, ranked by monthly downloads. That's useful external visibility. Not because a ranking magically makes software better, but because verifiable information makes it easier for developers to compare projects and make informed decisions. Verdict Sponsor Sentinel IR development here: https://github.com/sponsors/jakcmencz?o=syg&sc=r Source (GitLab, Apache-2.0): https://gitlab.com/jakubrojicek11/sentinel-ir npm: https://www.npmjs.com/package/sentinel-ir Playground (runs in your browser): https://sentinel-ir-playground-dc30c8.gitlab.io/ MCP Server on npm: npmjs.com https://glama.ai/mcp/servers/jakcmencz/sentinel-ir-mcp By "jackymenCZ" .(https://dev.to/jackymencz) What does this mean for Sentinel-IR-MCP? For me, the important part isn't the number itself. It's that the project has publicly verifiable foundations: an accessible source repository, an active release, a security policy, a declared licence and signed build provenance. These details are part of the infrastructure of trust. Sentinel-IR itself focuses on giving AI agents structured information about code: risk signals and useful context instead of simply handing over raw source. ProtocolProbe looks at a different layer: the public records surrounding the MCP server and its package. Those two perspectives complement each other. One helps an agent understand the code it is inspecting. The other helps developers understand the software they are considering connecting. And there is an important limitation worth mentioning: ProtocolProbe did not start Sentinel-IR-MCP or call its tools because a required configuration setting was missing. So the 9/9 result is not a runtime security assessment. That's a distinction I want to keep clear. A good checklist is not a force field. But a project that makes its foundations visible gives developers something real to inspect. The bigger picture As AI agents become more capable, choosing their tools will become just as important as choosing their models. Developers should not have to rely entirely on descriptions written by the people publishing those tools. They should be able to inspect the evidence. And perhaps that's the real value of a result like 9/9. Not a promise that nothing can go wrong. Just nine fewer questions left unanswered. I'll take that over another AI-generated badge saying "100% secure" any day. Project: "Sentinel-IR-MCP" (https://protocolprobe.com/mcp/servers/io.github.jakcmencz/sentinel-ir-mcp) ProtocolProbe record: "9/9 record checks" (https://protocolprobe.com/mcp/servers/io.github.jakcmencz/sentinel-ir-mcp) Checked November 2026. Record checks reflect public information, not a security guarantee or runtime test. Copyright © 2026 jackymenCZ. All rights reserved. Written for the community.

View Full Article

Published On: 2026-11-21

Great Deals on Ear buds from Amazon

The Real Winners of the Jensen Huang Affair
The Real Winners of the Jensen Huang Affair

Source: Hotair

Authors: beege welborn

View Full Article

On 29 October, a New York Times exclusive revealed how Chinese businesswoman Alice Huang had developed a ‘close relationship’ with...

View Full Article

Published On: 2026-11-21

US IPO Weekly Recap: Anthropic Seesaws In Record Debut
US IPO Weekly Recap: Anthropic Seesaws In Record Debut

Source: Seeking Alpha

Authors: renaissance capital ipo research

View Full Article

One IPO debuted this week, and one IPO submitted initial filings. AI model developer Anthropic priced its upsized IPO above the range to raise $81.3B at a $1.4T market cap.

View Full Article

Published On: 2026-11-21

Roundhill Generative AI & Technology ETF (NYSEARCA:CHAT) Stock Price Up 1.5% – Here’s What Happened
Roundhill Generative AI & Technology ETF (NYSEARCA:CHAT) Stock Price Up 1.5% – Here’s What Happened

Source: Watch List News

Authors: mark dietrich

View Full Article

Roundhill Generative AI & Technology ETF (NYSEARCA:CHAT – Get Free Report) shares shot up 1.5% on Wednesday. The stock traded as high as $68.90 and last traded at $68.46. 508,103 shares changed hands during mid-day trading, an increase of 8% from the average session volume of 472,011 shares. The stock had previously closed at $67.42. […]

View Full Article

Published On: 2026-11-21

Smart feted for AI voice enhancement service
Smart feted for AI voice enhancement service

Source: Philstar.com

Authors: philstar.com

View Full Article

Mobile services provider Smart Communications, Inc. (Smart), the wireless subsidiary of PLDT Inc. has bagged the Best 5G-A Service Innovation at the Global Core Summit Awards in Bangkok, Thailand, for PureVoice.

View Full Article

Published On: 2026-11-21

Anthropics IPO attracts $120 billion in retail demand, surpassing SpaceX
Anthropic's IPO attracts $120 billion in retail demand, surpassing SpaceX

Source: Business Standard

Authors: bloomberg

View Full Article

The AI firm's share sale attracted $115-120 billion in retail demand and more than $500 billion from institutional investors, even as its stock fell nearly 15 per cent on Friday

View Full Article

Published On: 2026-11-21

Good Man Who Made Bad Decisions: Trump Says Jensen Huang Deserves Second Chance At Nvidia
'Good Man Who Made Bad Decisions': Trump Says Jensen Huang Deserves Second Chance At Nvidia

Source: News 18

Authors: news18

View Full Article

Trump said he would like to see the former Nvidia CEO apologise and return to the company.

View Full Article

Published On: 2026-11-21

WhatsApp Android Flaws Could Let Hackers Delete Users’ Files and Expose IP Addresses
WhatsApp Android Flaws Could Let Hackers Delete Users’ Files and Expose IP Addresses

Source: Cybersecuritynews

Authors: guru baran

View Full Article

WhatsApp’s November 2026 security update describes three flaws that could let attackers delete files stored by WhatsApp on Android, expose a user’s IP address, or bypass a security check for Meta AI’s Private Processing service. Of the three, only the IP exposure flaw was flagged for possible abuse. The advisory says it may have been […] The post WhatsApp Android Flaws Could Let Hackers Delete Users’ Files and Expose IP Addresses appeared first on Cyber Security News.

View Full Article

Published On: 2026-11-21

Three young AI founders tell First Round they’re moving fast—and struggling to log off
Three young AI founders tell First Round they’re moving fast—and struggling to log off

Source: Digg

Authors: digg

View Full Article

Applied Compute, Reducto and Gumloop founders tell First Round why youth helps sell AI to big companies.

View Full Article

Published On: 2026-11-21

SpaceX-owned Cursor weighs phasing out Chinese AI models
SpaceX-owned Cursor weighs phasing out Chinese AI models

Source: Tech In Asia

Authors: grace priscilla teo

View Full Article

Airbnb and DoorDash were also examined in the probe over their use of Chinese AI models.

View Full Article

Published On: 2026-11-21

He left high school at 16 with no degree; by 27, his nuclear reactor powered an Nvidia AI chip and hit a $6 billion valuation
He left high school at 16 with no degree; by 27, his nuclear reactor powered an Nvidia AI chip and hit a $6 billion valuation

Source: The Times Of India

Authors: sanjay sharma

View Full Article

Isaiah Taylor, who left high school at 16 without completing his education, has built nuclear energy startup Valar Atomics into a company reportedly valued at $6 billion at age 27. Backed by a $1 billion investment led by Sequoia Capital, the California-based company is developing small modular nuclear reactors to power AI data centres. Its Ward 250 reactor has also demonstrated its ability to generate electricity for an Nvidia AI processor, highlighting nuclear energy's growing role in AI infrastructure.

View Full Article

Published On: 2026-11-21

Jensen Huang Set for Public Senate Banking Hearing As SEC Scrutinizes Nvidia Accounting: Report
Jensen Huang Set for Public Senate Banking Hearing As SEC Scrutinizes Nvidia Accounting: Report

Source: Benzinga

Authors: mohd haider

View Full Article

Former Nvidia CEO Jensen Huang will testify before senators in a public hearing, as the company faces multiple investigations.

View Full Article

Published On: 2026-11-21

Silicon Motion showcases Next-Generation Enterprise Storage Solutions to power Agentic AI Infrastructure at SC26
Silicon Motion showcases Next-Generation Enterprise Storage Solutions to power Agentic AI Infrastructure at SC26

Source: Cyprus Shipping News

Authors: a.violaris

View Full Article

Enabling AI Infrastructure with High-Performance PCIe Gen5 and Gen6 SSD Controllers with Predictable QoS and Reliable Enterprise Boot Storage Silicon […]

View Full Article

Published On: 2026-11-20

Ladies watches on Amazon

Explore exclusive UK AI News crafted by AIBusinessHelp, your trusted source for Artificial Intelligence insights. Our team delivers in-depth articles highlighting the latest AI trends, innovations, and developments tailored for businesses and enthusiasts alike. Dive into original AIBusinessHelp content to stay ahead in the fast-evolving world of AI.

Weekly AI News Roundup for the UK November 1-8, 2025
Weekly AI News Roundup for the UK November 1-8, 2025

Weekly AI News Roundup for the UK (November 1-8, 2025) Week of November 1-8, 2025 This week, the UK AI landscape highlighted regulatory debates, educational integrations, and economic concerns amid global market jitters. Here's a curated summary of the top developments: AI Joins School Curriculum Amid Education Overhaul: The UK government announced plans to incorporate AI into the national curriculum for English schools, including GCSE-level modules on ethical AI use and basic programming. This move aims to prepare students for an AI-driven workforce but has sparked debates on teacher.....

View Full Article

Published On: 8th November 2025

Why Small Businesses Are the Biggest Cybersecurity Risk in 2025
Why Small Businesses Are the Biggest Cybersecurity Risk in 2025

Why the Biggest Threat to Cybersecurity Comes from Small Businesses, and How AI Is Making It Both Worse and Better It does not take a recession to destroy a business. Poor IT security can do it overnight! While the headlines are dominated by billion-dollar data breaches at household-name corporations, an even larger and less visible cyber-security crisis is unfolding quietly: the one driven by small businesses. These “mom-and-pop” enterprises, local hotels, travel agents, accounting offices, retailers, are often overlooked targets, yet they hold customer data, operate older or.....

View Full Article

Published On: 8th November 2025

AI Weekly Roundup Oct 26 - Nov 1 2025
AI Weekly Roundup Oct 26 - Nov 1 2025

AI Weekly Roundup: UK's Regulatory Push Meets Global Innovation Surge (Oct 26 - Nov 1, 2025) Week of Oct 26 - Nov 1, 2025 London, November 2, 2025 – As artificial intelligence continues to reshape industries and societies, the past week has been a whirlwind of developments. In the UK, policymakers sharpened their focus on ethical AI governance amid growing calls for balanced innovation. Across the globe, breakthroughs in multimodal models and hardware advancements signaled an accelerating race toward practical AI ubiquity. Here's a curated look back at the key stories. UK Spotlight:.....

View Full Article

Published On: 2nd November 2025

Appreciating The AI Revolution
Appreciating The AI Revolution

A Front Row Seat to the Future: Reflecting on the Rise of AI Sometimes you just have to take the time to appricaite what we have The drive toward singularity is on, and with it, the ambition to create machines that can think, reason, and perhaps even dream like us. Every day brings a new headline: some warn of apocalypse, others promise utopia. But before we get lost in speculation about what AI might become, maybe we should pause to appreciate what has already been achieved. In just a few short years, we’ve gone from stilted, robotic responses to complex, thoughtful discussions that.....

View Full Article

Published On: 29th October 2025

The Death of the Internet as We Know It
The Death of the Internet as We Know It

The Death of the Internet as We Know It The AI Bubble, Limited Choice, and the Race to Monetize Before It Bursts Could AI spell the death of the Internet as we know it? In 1999, The Matrix imagined a world where humans were unknowingly trapped in a virtual reality, their bodies used as energy for intelligent machines. At the time, mobile phones could barely send text messages, and connecting to the internet meant using WAP, a slow, text-only service. Computers were primitive by today’s standards, and Facebook was still four years away. The film felt like distant science fiction. AI was a.....

View Full Article

Published On: 24th October 2025

Great Deals on AI books from Amazon


Global AI news in Video Format

View More Video AI News from YouTube

Check out great deals on everything AI from Amazon


Latest Published AI Articles

The Parasitoid Effect: How Democracy Can Be Undermined From Within
The Parasitoid Effect: How Democracy Can Be Undermined From Within

Can democracy be undermined without a single law being broken? The Parasitoid Effect explores how voter apathy, organised...

The AI Inventors' Renaissance
The AI Inventors' Renaissance

While headlines warn of AI's dangers, another revolution is beginning. Artificial intelligence, 3D printing and affordable...

The AI Advertising Paradox
The AI Advertising Paradox

AI search gives us answers without requiring us to visit the websites that created them. That's convenient for users, but...

Don't Shoot the Messenger!
Don't Shoot the Messenger!

AI agents are beginning to uncover vulnerabilities in real-world systems. That's alarming—but perhaps we're asking the wrong...


Submit Your AI News Press Release

Submitting your company’s AI press releases to AIBusinessHelp offers a powerful opportunity to amplify your Artificial Intelligence innovations to a targeted, engaged audience of business leaders, tech enthusiasts, and industry professionals—all at no cost. By sharing your latest AI developments with us, you gain free exposure on a platform dedicated to delivering high-quality AI News, boosting your brand’s visibility and credibility in the fast-growing AI landscape. Simply email us with the Press Release details, and your story could be featured alongside exclusive AIBusinessHelp content. This not only positions your company as a thought leader in Artificial Intelligence but also enhances your SEO through backlinks and increased online presence, driving traffic to your site. Whether it’s a groundbreaking AI tool, a new industry trend, or a transformative project, AIBusinessHelp provides a no-hassle, cost-free way to connect with a global audience eager for the latest AI insights—making it a win-win for your business and our readers.

Are you ready for AI News? Share your company’s latest AI developments with our audience. Submit your press release below or email us at info@aibusinesshelp.co.uk.