Google DeepMind and partners announce a $10M funding call for multi-agent safety research.
Referees for the 2026 World Cup will be wearing cameras positioned at their temples, allowing TV audiences to see a live view of the pitch from a vantage point they never have before.
According to new research, Trionda would show less unpredictable movements in actions such as corner kicks or free kicks. However, in powerful and long-distance clearances it would lose range.
The 48-team World Cup is not the only historic soccer event this year. Four titans are vying for control of video game soccer in the fiercest battle the industry has ever seen.
The organization claims that the FIFA tournament could have impacts on the rights of local people and visiting soccer fans in all three host countries.
The games start June 11 and end with a grand finale in New Jersey on July 19. There are 104 of them. Here’s how to watch ’em all.
Maybe it wasn't a great idea to let 14-year-olds post videos to Spotlight in the first place.
Findings from an exploratory user research study highlighting the unique insights and practical UX recommendations shared by participants with cognitive disabilities.
From anti-drone tech to face recognition, 2026 World Cup stadiums in the US, Canada, and Mexico are subjecting fans to an array of surveillance tech. Here’s what you need to know.
Most US World Cup stadiums are surrounded by surveillance cameras. Want to know if you’re being watched on your way to a match? These maps will help you.
The Argentine national team will be Google’s test bench and technological showcase during the World Cup.
Over the last few weeks, while learning LangGraph and agentic systems, I ended up building Co-Founder Memory . It's a stateful AI assistant with: • long-term memory • planning loops • self-correcting RAG • web search fallback • automated timeline summaries • project and preference tracking Nothing revolutionary — many ideas already exist. The goal wasn't to reinvent memory, but to understand how these systems work by actually building one. A lot of concepts only started making sense once I had to connect them together: graph-based workflows with LangGraph memory extraction and storage retrieval and validation loops routing and planning nodes maintaining context across sessions Building it taught me far more than watching tutorials ever did. Repo: https://github.com/Somay-kousis/Co-Founder-Memory I'm currently entering my 3rd year at IIITM Gwalior and looking for ML / GenAI internships . If you're building interesting things around LLMs, agents, RAG, or AI products, I'd love to connect. Always happy to chat with fellow builders as well 🚀 AI #GenerativeAI #LangGraph #RAG #LLM #MachineLearning #Internship
Azure API Management shipped a Unified Model API that lets clients speak one format while APIM transforms requests to Anthropic, Vertex AI, and other backends. Content safety policies now cover MCP tool calls and Agent-to-Agent payloads alongside LLM traffic. Token metrics expanded to track reasoning, cached, and audio tokens across providers. By Steef-Jan Wiggers
When a Shopify product CSV imports but product photos fail, the problem is often not the CSV syntax. It is usually that Shopify cannot fetch one or more image URLs during import. Here is the preflight I use before retrying a large product upload: Check that every Image Src or Variant Image value starts with http or https. Local paths like C:\images\shirt.jpg will not work. Open a few image URLs in a private browser window. If the image requires a login, expires, redirects to a file-sharing preview page, or blocks hotlinking, Shopify may not be able to download it. Keep image rows grouped with the correct product handle. Sorting a CSV by image column or price can separate continuation image rows from their product. Watch for URLs that do not end in a normal image extension. They can work, but they are worth checking manually before a full import. Test one small batch first, then verify the product admin after Shopify finishes downloading the images. For a larger file, I also like to extract the image columns into a review worksheet before touching product data. I built a small browser-side checker for that workflow here: https://shopify-csv.aivismonitor.com/shopify-csv-image-url-reachability-checker The important part is to fix image reachability before changing product titles, variants, or prices. Otherwise you can spend time debugging the wrong part of the import.
Text based, I don't want any cheesy porn AIs please 😅 submitted by /u/holupIgotthis [link] [留言]
If you have been writing PHP for a year or two, you have almost certainly written something like this: $items = getFilteredOrders (); $first = reset ( $items ); $last = end ( $items ); It works. It runs. It looks fine in code review. And it contains a subtle bug waiting to happen. The problem with reset() and end() Both functions move PHP's internal array pointer as a side effect. PHP arrays have a hidden cursor that tracks "the current position" in the array. Functions like current() , next() , prev() , and each() depend on where that cursor sits. reset() moves it to the first element. end() moves it to the last. This is harmless in an isolated script. But in a real application, the same array often passes through multiple functions — and any function that relies on the cursor position after your call will get unexpected results. Here is a concrete example: function getFirstActiveOrder ( array $orders ): ?array { // Moves the pointer to the first element $first = reset ( $orders ); foreach ( $orders as $order ) { if ( $order [ 'status' ] === 'active' ) { return $order ; } } return null ; } At first glance this looks fine. But foreach in PHP actually resets the pointer to the beginning before iterating — so in this simple case you get lucky. The bug shows up in less obvious situations: when you call reset() inside a function that the caller is already iterating with current() / next() , or when you use end() to peek at the last item while a foreach is in progress on the same array reference. The deeper issue: reset() and end() return false on an empty array. But false might also be a legitimate value stored in your array: $flags = [ true , false , true ]; $last = end ( $flags ); // returns false — but is this "empty array" or "the value false"? You have to write: if ( $flags === [] || end ( $flags ) === false ) { ... } Which is already awkward. And it still mutates the pointer. The modern solution: array_key_first() and array_key_last() PHP 7.3 introduced two functi
AI is already deciding who gets loans, who gets job interviews, who gets flagged for benefits fraud. Not assisting humans in making those decisions. Making them. And in most countries there is no law requiring anyone to tell you AI was involved, explain why it decided what it did, or give you any way to challenge it. That needs to change. We need laws that say if an AI makes a decision about you, you have the right to know, the right to understand why, and the right to challenge it. A human must always be accountable for the outcome. That’s not anti-innovation. That’s just basic protection for people living in a world already being shaped by these systems. Most governments don’t understand it well enough to even write those laws yet. Most politicians making AI policy genuinely cannot explain how these systems work, who owns them, or what accountability looks like when they go wrong. Voluntary frameworks have failed every single time. Social media companies voluntarily committed to reducing harm. They didn’t. Financial firms voluntarily committed to responsible lending. They didn’t. Voluntary always means the least responsible actor sets the standard. Hard law is the only mechanism that has ever reliably produced accountability at scale. We need it for AI before the damage is done — not after. The window to get this right is still open. But it won’t stay open forever. submitted by /u/United-Actuator-3527 [link] [留言]