Agreguesi i feed

Gom is a very old object mapper I wrote to bridge GObject to SQLite. It made a lot of assumptions about the world based on when it was prototyped.

The past couple years had me using it again for the documentation search in Manuals. Typically, I would have just built Manuals to parse all the XML files on disk and hold them in memory. That’s how both Devhelp and Builder always did things. Once we started supporting Flatpak SDKs that was no longer realistic. You could have numerous SDKs all with copies of the overlapping data and it just became easier to have a query model.

One of the more performance critical limitations was the locking model. When gom-1.0 was written, it was not common for distributions to compile SQLite with locking support. So you just created a single thread and did your work over there.

Bolting fulltext search and many other missing features onto the old ABI just wasn’t realistic. Especially when I’ve wanted to make the thing properly async for years. One of my other projects, Libdex is just right over there and perfect for this sort of problem.

The landscape changed and so do our horizons.

A new informed ABI

In the years after Gom was prototyped, I worked at a commercial database company and learned a great deal about implementing the internals of both that database and more traditional RDBMS. That left a certain cringe on my mouth whenever looking at my code predating it. Knowing how things get done inside the database allows for building better APIs to interact with it.

This time everything is async. Queries are modeled like you do with a compiler. Lowered into the back-end specific implementation. There can be an entity map and real transactions which allows you to read back the same instance despite which query inflated it.

The Center

Your early stage objects are the GomRepository, GomDriver, and GomRegistry.

The registry describes the entities that can exist within the repository. This is handy because it allows us to pre-compile information into a model that is both immutable and fast at runtime. Compare that to methods like g_object_class_list_properties() which is a performance bottleneck of its own.

The driver is very obvious. It is our abstraction layer for the database engines. Currently we have support for SQLite and PostgreSQL.

The repository is the center of the center. It is how you query, insert, update, delete, transact, and more. It is likely your application instance owns one of these unless of course you use Gom as your file format in which case you’ll have one per “document”.

Two Access Models

This new version of Gom can support either the entity mapping you’re used to or; optionally, raw access to relations/projections via the GomCursor.

As the cursor moves through the resulting rows you will have access to all the projections requested in the query. Though it holds enough information to allow you to gom_cursor_materialize() the row into an GomEntity subclass.

If you want a snapshot of that cursor row without materializing, you can use GomRecord which can also conveniently be used in GListModel for integration into GTK applications.

Most of the time, you’ll use materialization. And even then it is likely to happen through automated collections rather than with a cursor directly. More on that later.

Sessions

As I mentioned, there was no concept of transactions previously.

In this iteration we have GomSession. It is your standard identity-map layer with transaction-scoping. If you perform multiple queries for the same record, the session will ensure you get the same instance back. hat is essential when you do local mutations on an instance and what to see that reflected in followup queries.

Additionally, it makes it nice to have multiple views of an object with an editor or listview and needing them to stay in sync.

Relationship Modeling

Support for relationships was adhoc previously. We had some functions named in ways that made you think you could, but I assure you, they were not well tested.

This time around you can model your GomEntity with 1:1, 1:M, M:M, inverse, self-referencing, all while handling proper delete rules. Combing this with the session support mentioned previously is crucial.

So now you should be able to show related models easily in GtkListView while keeping the paginated-and-lazy model beneath it transactional.

Migrations

In the previous version migrations were dynamic, but largely controlled by Gom itself. Very inflexible.

This time around we have things broken down into Migrator and Migration.

You can use built-in implementations like the EntityMigrator or implement your own. CustomMigrator makes that easy. Especially since you can inject your own migrations at just the right point.

Internally, libgom-2 can snapshot your GomRegistry at specific versions based on the provided metadata. Then it performs a diff between two versions of the registry to determine what migration work must be done.

You can just as easily use a SqlMigration with custom SQL scripts. This stuff is all highly composable now to get exactly what you need.

Live List Models

I’ve written many ways to get live SQLite results into GTK over the past two decades. I think one of the first was a GtkTreeModel implementation for GTK 2 which could do it. With that in mind, it was still rather annoying when making Manuals so I set off to make that convenient.

We have GomRecordListModel, GomEntityListModel, GomRelatedListModel, GomQueryModel all of which have practical uses based on application needs.

But in short, most of those are lazy and support transaction-backed stable identities for entities. Very useful when you have a list of items and an editor loaded in another frame, both of which must reflect the same data.

Expression Trees

This time around I implemented proper expression trees. They model the query, relations, and projections in a manner that allows the driver to lower into a query much more accurately.

You can model things like function-calls cleanly all of which required writing manual SQL before. If you did anything outside of what gom could generate previously, it became madness to maintain.

Vectors

This version of libgom embeds the vec1 extension for SQLite. That means we can store vectors in your records and query them. GomVector makes that easier to manage as a property within your application entity.

I can think of a few things this will be useful for, maybe you can too.

Profiling

This version of libgom has profiling support with another project of mine, Sysprof. The whole library emits profiler marks about what is going on so that it is easy for you to figure out why something might be slow in your application.

Since we’ve already done the integration of Sysprof into GLib/GObject, GTK, Pango, Libdex, and GNOME Shell/Mutter you can very quickly get an idea with details of what is going on in your application. Click record, select the problem area, zoom, and it is often pretty clear. You can have flamegraphs, callgraphs, and timing marks all in one place.

Local First with Sync Coordination

One of my personal motivations for this is around building a native sync protocol for applications I’m building. I wrote numerous SQLite-based sync protocols for the now defuct catch.com before they were acquired by apple. That means I know multiple wrong ways to do it.

This time around, I want to put it right in the data-mapper at the point where you have the most insight. So libgom has the right abstractions in place to build that. The GomSyncCoordinator manages the process and GomSyncTransport is the abstraction-point for service integration.

You work with GomDelta at this layer. The application can provide you with a GomMergePolicy to help make decisions which allow for contextually doing the right thing.

This part is still very new. I’m still building the other side of it but landing the shape early allows me to mock and test things comprehensively before committing to the ABI.

My goal is building a practical, robust, and correct implementation for personal local first features.

A small personal note: as I wrote in my recent update from France, I am no longer employed by Red Hat. Work like this is currently self-funded, out of pocket, while my family and I settle into a new chapter. If you find it useful, a note of encouragement or a contribution means a lot right now. It helps make it possible to keep improving the free software infrastructure many of us rely on.

Version:next-20260609 (linux-next) Released:2026-06-09

Meta says it will expand how it uses off-platform activity shared by other businesses to personalize Facebook and Instagram feeds as well as AI responses, not just ads. The change starts in July and can be disabled through the "Activity from other businesses" setting, though Meta says it is not collecting new data as part of the update. The Verge reports: For example, Meta says if you bought a tent online recently, you might see camping-related videos in your Reels feed. "We aren't collecting any new data as part of this update," the blog post says. "This is about using information that businesses already send to us to further improve your experience." Meta spokesperson Emil Vazquez tells The Verge that the company previously only used the activity across its apps, such as likes, views, and follows, to tailor the content you see. The company also started using conversations with its AI assistant to personalize ads last year.

Read more of this story at Slashdot.

An anonymous reader quotes a report from 404 Media: Microsoft has shut down a wave of its own repositories on GitHub, including those related to Azure and AI coding agents, as it investigates a data breach, according to research from cybersecurity researchers and a statement given to 404 Media by Microsoft. Hackers planted malware that would harvest peoples' credentials when they opened it in AI coding tools like Claude Code or Gemini CLI, according to one set of researchers. The exact contours of the breach are unclear, but researchers say Microsoft has disabled more than 70 of its own repositories, and pointed to a particular package that was previously compromised. Last week, cybersecurity website OpenSourceMalware.com, which acts as a clearing house for indicators of supply chain attacks so defenders can secure their own networks, and which also publishes its own write-ups, wrote about the mass disabling of Microsoft GitHub repositories. "GitHub disabled 73 Microsoft repositories across four of its GitHub organizations -- the entire Azure Functions org, the whole Durable Task family, and a row of AI sample apps -- in a 105-second sweep on June 5," the website wrote on Friday. Is it very unusual for any company, let alone Microsoft, to disable so many of its own repositories in one go. They include 49 related to Azure, Microsoft's cloud computing arm, and some concerning AI agents. The shutdown repositories also include ones related to durabletask, a Microsoft development tool. Researchers from StepSecurity wrote on Friday that the GitHub closures came after a malicious commit was pushed to the durabletask repository. That attack planted configuration files that would harvest peoples' credentials when they opened the repository in Claude Code, Gemini CLI, Cursor, or VS Code, StepSecurity wrote. Microsoft said in a statement: "Our priority is to protect customers and the broader ecosystem. We temporarily removed some repositories as we investigated potential malicious content. Some of these repos have been restored after review, while others may remain offline while work continues. As part of our investigation, we notified a small number of customers who may have pulled down content from the affected repositories. We will continue to investigate, and if anything further is identified that requires customer action, we will reach out directly through our established support channels."

Read more of this story at Slashdot.

NHS England plans to roll out Microsoft Copilot to 505,000 clinicians and support staff after a 30,000-person pilot claimed the AI assistant saved users an average of 43 minutes a day on administrative work. The Register reports: The rollout won't happen overnight. NHS England said that each trust will receive a central allocation of licenses based on headcount, typically starting with around 2,000 Copilot seats, and that more than half a million staff are expected to have access by October 2026. The NHS has no shortage of administrative work to throw at the software. The rollout envisions Copilot helping with discharge paperwork, bed management, rota planning, meeting minutes, board papers, briefings, data analysis, and assorted HR, finance, and procurement tasks. NHS organizations will also receive access to Copilot Studio, Microsoft's toolkit for building custom AI agents. NHS England said trusts will be able to develop agents for tasks such as handling Freedom of Information requests, processing complaints, reducing helpdesk workloads, and assisting with financial analysis. A governance framework called Agent 365 will oversee the deployment of those systems.

Read more of this story at Slashdot.

UK Prime Minister Keir Starmer has given Apple, Google, and other tech firms until September to introduce device-level protections that prevent children from taking, sharing, or viewing explicit images. "If businesses do not comply within three months, legislation will be brought forward requiring the protection to be added to all phones and tablets sold in the UK," reports The Guardian. "Tech firms that fail to do so could face fines, and their senior managers could be made criminally liable." From the report: "Today, I am calling on tech companies operating in this country to introduce vice controls that prevent children from sending and receiving sexually explicit images. Because this is not an impossible challenge," he said. "If they choose not, then we will act and we will change the law." [...] Under the changes, sexual predators will be prevented from being able to exploit and abuse victims through their devices, and children stopped from being able to access pornography, the Home Office said. Adults will still be able to take, share or view nude content once they have verified their age. In the Commons, Melanie Ward, the Labour MP for Cowdenbeath and Kirkcaldy, said: "It's time to stop asking social media companies to make their products safe, and instead time to start requiring them to do so through regulation." Clive Efford, the Labour MP for Eltham and Chislehurst, said the "sociopaths" running social media platforms had no concern for the welfare of children. "The only message that they're going to listen to is if there's legislation put before this house that is going to act and send a clear message to them." The proposal is designed to sit alongside the Online Safety Act, which requires companies to have processes for removing material that is illegal or harmful to children.

Read more of this story at Slashdot.

Researchers say mysterious, seconds-long GPS interference bursts detected across Europe appear to come from Russian EKS early-warning satellites, making this "a rare example of human-made GPS interference coming from space," reports Ars Technica. The signals may be tests of space-based jamming capability, short satellite communications, or something else, but experts say they raise troubling questions about whether GPS disruption could eventually be weaponized on a continental scale. From the report: The discovery came from an investigation detailed in a June 2 preprint paper by Todd Humphreys and his student Zach Clements at The University of Texas at Austin, along with Argyris Krizise at Stanford University in California. By sifting through public data from ground-based stations with global navigation satellite system (GNSS) receivers, they identified a pattern of high-powered interference lasting less than 10 seconds each time but simultaneously detectable by ground stations across Europe from Norway to Spain to Poland, and even reaching as far west as Greenland and Canada. By analyzing the ground station data from January 2019 to April 2026, the researchers found 75 days with at least one widespread GNSS interference event overlapping with the GPS L1 frequency band centered on 1575.42 megahertz. That represents the main band used for signal transmission by the US-made GPS satellite constellation and GNSS constellations from other countries. Such interference patterns happened mostly on Tuesdays, Wednesdays, and Thursdays during business hours in Europe, Humphreys told the YouTube channel Veritasium. Because such "continental-scale" interference was simultaneously affecting GPS receivers across Europe and beyond, Humphreys and his colleagues calculated that the source had to be at least 1,200 kilometers above the Earth. [...] In the Veritasium video, Humphreys speculated that the Russians may have been testing the satellites' GPS interference capabilities only briefly on a neighboring frequency adjacent to the typical GPS band. "And then in the eventual future when there is a hot conflict, they go ahead and tune their transmitter down to the GPS band, but it's much more damaging now that it lies right on that band," he said. Incidentally, the raw data also revealed a second interference burst from the Russian satellites in a lower-frequency band used by China's BeiDou navigation system. "I can no longer say this is accidental with confidence," Humphreys told Veritasium. He also described the Russian satellites' quiet demonstration as a "massive escalation in the electronic warfare background conflict that is going on right now." Richard Bowden, division head of assured and resilient PNT at the multinational technology company GMV in Spain, wrote in a LinkedIn comment: "These signals are, without a doubt, intentional and placed on or around GNSS signals, and have the potential to disrupt legitimate use of GNSS services. But from our side at least, we can't be sure they are intentionally malicious or intended as an EW [electronic warfare] weapon."

Read more of this story at Slashdot.

Version:7.0.12 (stable) Released:2026-06-09 Source:linux-7.0.12.tar.xz PGP Signature:linux-7.0.12.tar.sign Patch:full (incremental) ChangeLog:ChangeLog-7.0.12

Version:6.18.35 (longterm) Released:2026-06-09 Source:linux-6.18.35.tar.xz PGP Signature:linux-6.18.35.tar.sign Patch:full (incremental) ChangeLog:ChangeLog-6.18.35

Version:6.12.93 (longterm) Released:2026-06-09 Source:linux-6.12.93.tar.xz PGP Signature:linux-6.12.93.tar.sign Patch:full (incremental) ChangeLog:ChangeLog-6.12.93

A battery researcher's investigation, backed by more than 20 independent experts, claims Donut Lab's much-hyped "solid-state" battery is actually a conventional lithium-ion cell, with voltage curves and expansion data matching high-nickel NCM chemistry rather than the promised sodium-ion solid-state design. Electrek reports the company raised about $25 million from more than 1,300 mostly small investors on claims of 400 Wh/kg energy density, 100,000-cycle life, and 5-minute charging that now appear unsupported. From the report: The investigation consulted over 20 independent battery experts, including Julian Zanau from the Fraunhofer Research Institute, Dr. Yahim San from Justus-Liebig University, Tom Bicha from Leona, and Dr. Yuo Hesca from Seinajoki University of Applied Sciences. Every single one confirmed the tested cell is lithium-ion. There are two key pieces of evidence. First, the voltage curves from VTT testing match high-nickel lithium-ion cells (NCM chemistry). The cell sits at 3.7-3.8 volts at 50% state of charge -- right where lithium-ion cells operate. Sodium-ion cells don't go significantly past 3.5 volts at 50% SOC. The second piece of evidence is even more damning: VTT's cell expansion data. When a battery charges, ions squeeze into the anode material, causing it to expand in a predictable pattern. A graphite anode produces a distinctive "kink" in the expansion curve around 50-70% state of charge, caused by how ions reorder themselves in graphite's layered structure. The Donut Lab cell shows exactly that kink. This is critical because sodium ions are physically too large to fit into graphite layers. The graphite anode signature proves the cell uses lithium ions. The investigation puts it well: "it's like we have a slightly noisy fingerprint and a picture of the suspect's face. And yet again, it's a match." The calculated energy density? About 298 Wh/kg -- what you'd expect from a good lithium-ion cell, not the 400 Wh/kg claimed. The investigation reveals that the battery technology traces back to CT Coatings, a German company with an "eclectic" array of patents -- including inventions for screen-printed paving slabs, menu folders, and warning triangles. CT Coatings promised Nordic Nano and Donut Lab a screen-printed sodium-ion solid-state battery. What it delivered was a lithium-ion pouch cell.

Read more of this story at Slashdot.

An anonymous reader quotes a report from The Guardian: The world's oceans are under "severe and accelerating" pressure from human activities, with the rate of sea-level rise double that of a decade ago, according to a damning assessment from the United Nations. The "intensifying" stressors, which include pollution and large-scale industrial fishing, are cumulative, said the report, resulting in widespread biodiversity loss and putting ocean systems under "severe strain." The UN's third World Ocean Assessment, which reflects the work of nearly 600 scientists from 86 countries, looked at the oceans' health from 2021-25. The previous report, that covered up to 2018, found persistent degradation of the marine environment. Five years on, scientists know more about the cumulative impacts of anthropogenic pressures on the ocean, and the latest report shows just how much of the damage has been done in the past few years. The scientists' key findings include: - Sea levels continue to rise at an increasing rate, from 2mm a year prior to 2015 to 4.3mm a year in 2023. - 16% of the increase in global ocean heat since 1955 occurred after 2018. - The greatest relative warming has been observed in the Atlantic Ocean and the southern parts of the Indian and Pacific Oceans. - Large gaps in knowledge persist -- with only 27% of the ocean floor mapped by 2025, deep-sea ecosystems remain poorly understood. Lukas Meus, Greenpeace's global ocean campaigner, said: "We are calling on governments to create fully protected ocean sanctuaries that will close vast areas of the ocean off from extractive human activities. Governments have promised to protect 30% of the world's ocean by 2030 -- the minimum scientists say we need for the ocean to be able to recover."

Read more of this story at Slashdot.

OpenAI has confidentially filed for an IPO, "setting it up for what may be the most highly anticipated market debut in recent history and a massive payday for early investors," reports CNN. The decision follows recent IPO announcements from Anthropic and SpaceX. From the report: OpenAI said it has not decided on timing yet. And because the filing is confidential, it's not yet clear how many shares the company plans to sell or at what price. "It may be a while because there are things we want to do that are likely easier as a private company," it said in a post on its newsroom page. But the company said the filing "gives us the option to go public sooner if that ends up being best." The transition to a public company will give Wall Street a window into OpenAI's finances as the company pours billions into AI infrastructure and computing resources. Investors dumped tech stocks last week as they questioned whether a recent run-up in those shares had gone too far. OpenAI was last valued at $852 billion after raising $122 billion in March, but it's faced pressure to demonstrate it can generate the cash to match that valuation.

Read more of this story at Slashdot.

Last Thursday, Wired reported that Meta had quietly embedded an unreleased facial recognition system called NameTag into software installed on millions of phones. In a follow-up report, Wired says the tech giant has now removed the face-recognition-related code, while saying "no final decision" has been made about whether the feature will launch. From the report: On Thursday, WIRED reported that Meta had quietly integrated substantial portions of the NameTag system into the Meta AI app. Though never publicly enabled, the feature was designed to convert faces captured by the glasses into unique biometric signatures, commonly known as faceprints, and compare them against a database of faceprints stored on the user's device. WIRED also found that faces the system failed to recognize were cropped, indexed, and stored locally for future processing. NameTag first surfaced in February, when The New York Times, citing internal Meta documents, reported that the company was developing face recognition for its smart glasses and weighing a launch as soon as this year. One memo reportedly described releasing it during a "dynamic political environment," when privacy and civil liberties advocates would be distracted. Last week, WIRED reported that much of NameTag's machinery was already built into the Meta AI app, downloaded by millions of users, as early as January, even as Meta publicly said it had made no final decision about face recognition. After WIRED's report, Stone dismissed the findings, writing that the company couldn't answer questions about how the system would work because "the feature does not exist." Andrew Bosworth, Meta's chief technology officer, called the reporting "incredibly misleading" and "absolutely dishonest." [...] The newly released version of Meta AI removes nearly all traces of the feature Meta said did not yet exist. Gone is the face-recognition software itself, along with the code that ran the NameTag recognition process and the "Person recognized" alert the app would have shown if someone were identified. The update also strips out a folder where the app would have stored the cropped images and biometric signatures of faces it captured but could not identify. [...] A few fragments of the NameTag system remain in the version of latest Meta AI, including an internal debug menu label and a dormant link meant to open a recognized person's profile. The leftover code points to parts of the system that are no longer there.

Read more of this story at Slashdot.

Many GNOME projects have adopted a policy banning all contributions generated by LLMs. This policy was originally developed by Sophie for Loupe, but is now used in many other notable places:

This project does not allow contributions generated by large languages models (LLMs) and chatbots. This ban includes, but is not limited to, tools like ChatGPT, Claude, Copilot, DeepSeek, and Devin AI. We are taking these steps as precaution due to the potential negative influence of AI generated content on quality, as well as likely copyright violations.

This ban of AI generated content applies to all parts of the projects, including, but not limited to, code, documentation, issues, and artworks. An exception applies for purely translating texts for issues and comments to English.

AI tools can be used to answer questions and find information. However, we encourage contributors to avoid them in favor of using existing documentation and our chats and forums. Since AI generated information is frequently misleading or false, we cannot supply support on anything referencing AI output.

I won’t attempt to argue that you should allow use of AI for writing code. If you wish to ban LLM-generated code, fine. That’s probably inadvisable, but I am not going to object.

But this policy is far stricter than that. Notably, it strictly prohibits AI-generated content in issue reports (except to translate text). Don’t do this! Prohibiting bug reports is stupid and just makes your software worse. Please make sure your project’s AI policy allows for at least AI-generated static analysis results and AI-generated vulnerability reports. Otherwise, you prohibit entirely unobjectionable problem reports.

It’s hard to imagine what could possibly be the value of prohibiting valid bug reports. AI-generated static analysis works well: the AI is able to think about your code, follow execution paths, and automatically discard most false positives to avoid bothering you with them, and the quality of reports is generally pretty high. They are far from perfect, but the same is true of humans.

Here is a typical example of an AI-generated static analysis finding:

2. Resource leak in update_credentials_cb on gnutls_credentials_set failure

File: tls/gnutls/gtlsconnection-gnutls.c:169-172

When gnutls_credentials_set() fails, the function returns without calling g_gnutls_certificate_credentials_unref(credentials). The credentials was either freshly allocated or ref-bumped, so it leaks.

Pasting this into an issue report clearly violates the ban on AI-generated content. And yet, why would you not want to receive a clear and concrete bug report for memory leak?

I understand not all maintainers are fond of AI, but is your dislike really so extreme that you would choose to ignore valid problems and intentionally make your software worse? If not, then your AI policy should thoughtfully consider how to handle AI-generated content in issue reports. Certainly do not adopt a policy that outright bans all AI-generated content in issue reports.

As an issue reporter, you could theoretically take the problem found by the AI and rephrase all the words, then claim that it is no longer AI-generated content because it is rewritten it. This is a waste of time and usually results in a lower-quality, less-detailed result, but you could plausibly do that. Or, if you want to go above and beyond, you could just jump ahead to creating a merge request. But realistically, if your project does not allow any use of AI in issue reports, it’s more likely that either (a) you won’t receive the issue report in the first place, or (b) you won’t receive such issue reports from experienced developers who read and respect your policy, while users who do not read your policy will continue to submit them.

What about security vulnerability reports? Since the start of this year, I have reviewed well over 100 vulnerability reports that I strongly suspect were generated by AI. To reach the “over 100” claim, I sadly only considered vulnerability reports submitted during a particularly heavy four week period, so this is an extremely loose lower bound. Suffice to say, I have seen a lot of them. The quality varies dramatically. Vulnerability reports are now often better or worse than before: better because an experienced human working with a good AI is able to find vulnerabilities that would have surely gone unnoticed without AI, and worse because an inexperienced human with a bad AI might create some pretty terrible issue reports, a significant proportion of which are just outright spam. Low-quality reports remain a problem, but nowadays most AI-generated issue reports are quite good.

Maintainers do not need to tolerate spammy vulnerability reports. If an issue report is bad, of course go ahead and close it. If it’s really bad, then I sometimes don’t even bother replying. But banning good vulnerability reports solely because some portion of the report was generated by AI is unacceptable. AI-assisted vulnerability reports are the new industry standard, and this is not likely to change. Prohibiting issue reports reduces the quality and safety of your software, punishing your users. This is too extreme.

Microsoft executive Matt Booty says future Xbox exclusivity will be decided "case-by-case," with Gears of War: E-Day and Clockwork Revolution remaining Xbox console exclusives while major multiplayer, live-service, and previously promised PlayStation releases stay multiplatform. But IGN's Tom Phillips says Microsoft's announcement still leaves numerous questions unanswered, like "why just Gears and Clockwork Revolution?" and "how will this policy be enforced in future?" From the report: Last night's Xbox Showcase featured the return of games specifically earmarked as exclusives for Xbox consoles (though, of course, they'll still also be coming to PC). But why just Gears and Clockwork Revolution? And how will this policy be enforced in future? Microsoft's announcement left numerous questions unanswered. "We want a reason for people to get on board with Xbox, we want them to have a reason to buy an Xbox, we want them to have a reason to be an Xbox fan," Booty said. "At the same time, we want to reward all our players that have been with us for a long time -- we know that exclusives are important, and that's why we've got Gears coming in 2026 and Clockwork [Revolution] coming in 2027." "We also want to be clear that our big multiplayer games and live-service games are going to continue to be multiplatform," he continued. "If we've promised something to players already, we're going to honor that promise. And then -- I think Asha said it -- we're going to make the right decision and not the fast decision. "We're going to keep thinking about this going forward," Booty continued, "and, I think you guys know already, our principle is when we announce the date, we announce the platforms. So, it's going to be case-by-case, but we're going to be clear, that when it's got a date, it's got a platform and you'll know what the choice is going to be." Beyond those games already confirmed for PlayStation (such as the upcoming Halo: Campaign Evolved, and the PS5 version of Forza Horizon 6 due later this year), last night saw Microsoft make the call that other upcoming titles would still be coming to PS5 as well. While it had been assumed that State of Decay 3 would get a PS5 version, yesterday saw it made official. Hellblade threequel Senua was unveiled, and is getting a PS5 version. And, unsurprisingly, Spyro: A Realm Beyond is coming to Xbox, PS5 and Nintendo Switch 2.

Read more of this story at Slashdot.

An anonymous reader quotes a report from AppleInsider: Apple has unveiled its next Mac operating system, macOS Golden Gate, with Apple promising better performance, the improved Siri, and more. [...] On the surface, macOS Golden Gate is not as significant an upgrade as macOS Big Sur, or even macOS Tahoe with its Liquid Glass redesign. But under the surface, it is much more significant than it seems. Apple has chosen this release to draw a line in the sand. For the first time, the new macOS Golden Gate will not support Macs that have Intel processors. [...] Nonetheless, as of when this is released to the public in September or October, no Intel Macs will ever be supported again. One of the most notable design tweaks in this new release is a refinement of macOS toolbars and sidebars: toolbars are now more distinct, sidebars can stretch all the way to the window edge, and sidebar icons have regained color. Apple is also tightening window corner radii to address complaints about resizing behavior.

Read more of this story at Slashdot.

At WWDC 2026, Apple announced a new "Siri AI," describing it as a more conversational, personalized, and systemwide assistant that can understand on-screen context and interact with apps while relying on on-device processing or Private Cloud Compute. The relaunch comes two years after Apple's original Apple Intelligence promises stumbled and "never fully materialized," reports The Verge. MacRumors reports: Siri is now embedded directly in the Dynamic Island, accessible by swiping down from it, pressing the side button, or saying "Hey Siri." A revamped voice engine makes the assistant sound more expressive, with micro-adjustable voice settings available during initial setup. During Apple's keynote demo, presenters showed Siri handling chained, multi-step requests with apparent ease. In one sequence, a presenter asked about a Suki Waterhouse concert, was told tickets require a lottery entry, and asked Siri to set a reminder when the lottery opens, which it did. In another, the assistant identified a photo's landmark, pulled up navigation to that location, and surfaced photos from a recent family trip, adding a specific image to a shared family album on request. Another demo showcased Siri's ability to synthesize information across apps. A presenter asked about a dessert he had heard about at an event, and Siri located the relevant details from his Messages history. It then compiled the information into a watch-party menu, drafted a message to his contacts with the menu included, and presented send and edit options. In a further demo, a presenter asked about something his son had shared in a message and followed it up by asking Siri to compose an email on the subject. A new dedicated Siri app lets users scroll back through prior conversations and kick off new ones, with conversation history synced via iCloud so sessions carry seamlessly between devices. The app is also coming to watchOS. On the Mac, Siri is now also integrated into Spotlight and available via right-click context menus on any file or window. On visionOS, Siri AI gains a 3D visualization that users can place anywhere in their space.

Read more of this story at Slashdot.

wiredmikey shares a report from SecurityWeek: Meta-owned communications app WhatsApp says it recently detected and disrupted a spear-phishing attempt linked to spyware company NSO Group. The attack is allegedly in defiance of a court order that bars the spyware maker from targeting WhatsApp. WhatsApp filed a lawsuit against NSO in 2019, after it came to light that a zero-day vulnerability had been exploited to deliver spyware to users. [...] NSO has been seeking to overturn the order blocking it from targeting WhatsApp users, arguing that the company will "suffer irreparable harm." According to WhatsApp, the spyware maker has violated the permanent injunction. The messaging app reported on Monday that it had recently learned of a social engineering attack that attempted to trick users into clicking on malicious links. WhatsApp has only shared a few domains as an indicator of compromise (IoC), but says it was able to link the attack to NSO, pointing to similarities to previously reported one-click phishing campaigns tied to the spyware company. WhatsApp says it also caught the attackers creating test accounts and groups. Those accounts and groups have been disabled, but further action is also being taken. WhatsApp says it is asking a federal court to hold NSO in contempt for allegedly violating a permanent injunction barring it from targeting WhatsApp and its users. The company also said it is making a "significant contribution" to the Spyware Accountability Initiative, a fund aimed at exposing and stopping spyware abuse.

Read more of this story at Slashdot.

Firefox has merged initial support for Vulkan Video decoding, giving the browser a more cross-platform path for GPU-accelerated video playback beyond Linux's long-running reliance on VA-API. Phoronix reports: Firefox on Linux has long been focused on the Video Acceleration API (VA-API) that isn't universally supported by Linux graphics drivers. This has left to efforts like NVIDIA-VAAPI-Driver to layer VA-API atop NVIDIA NVDEC interfaces to enjoy GPU-accelerated video playback in Firefox. Smaller Arm/embedded graphics drivers also have been largely left out of the game in the VA-API space. But with Vulkan Video we are beginning to see more adoption and in a cross-platform manner. [...] The Firefox 153 release due out in July will have Vulkan Video decoding support available. The Vulkan Video activity in Firefox Git culminated this week with the work of NVIDIA engineer Tymur Boiko and Red Hat's Martin Stransky. Firefox 153.0 is expected for release on 21 July with this Vulkan Video support assuming no last minute issues.

Read more of this story at Slashdot.