# dma Published articles for dma. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Selling Digital Goods Outside the App Store: A 2026 Compliance Playbook DevFeed: [Selling Digital Goods Outside the App Store: A 2026 Compliance Playbook]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-05-10T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [iOS](), [App]() Tags: [2026](), [app-store](), [apple](), [apps](), [compliance](), [dma](), [eu](), [guide](), [ios](), [mobile](), [payments](), [us]() ### AI overview A 2026 guide to selling digital goods through iOS apps while accepting payments outside the App Store. It explains regional eligibility in the United States, European Union, and South Korea, relevant integration patterns, categories where in-app purchase may be optional, and compliance risks. The article advises verifying current Apple entitlement terms before shipping. ### Source excerpt Where and how to legally accept payments outside the App Store in 2026: US, EU DMA, South Korea entitlements, and the patterns that keep your iOS app compliant. ## GPU Driver Attacks on Android and Their Mitigation in KasperskyOS DevFeed: [GPU Driver Attacks on Android and Their Mitigation in KasperskyOS]() Original publisher: [Read original article]() Author: denis\_molodyakov ("Лаборатория Касперского") Published: 2026-02-25T15:14:03Z Content type: tutorial Language: ru Sources: ["Лаборатория Касперского" RU]() Topics: [GPU](), [Security](), [SELinux](), [Arm](), [LineageOS]() Tags: [android](), [arm](), [dma](), [gpu](), [iommu](), [kasperskyos](), [security](), [selinux](), [tag-33729a63fe14](), [tag-a6bf72199ce9](), [tag-c87ceb311a81](), [tag-cc2a6346d835]() ### AI overview This article explains attacks against GPU drivers, focusing on Android devices with integrated ARM Mali accelerators. It describes memory-management and use-after-free attack cases, including one that could enable full device access and disable SELinux, and discusses how similar scenarios are mitigated in the microkernel-based KasperskyOS. ### Source excerpt Что вы знаете об атаках на графические процессоры? Наверняка ничего приятного: они крайне распространены на мобильных устройствах, классические "песочницы" от них не защищают, и компрометация лишь одного драйвера может поставить под угрозу все ядро... Меня зовут Денис Молодяков, и я -- лид команды графики в KasperskyOS. Идея этого текста возникла во время одного моего выступления на конференции по системной разработке. Тогда из зала задали вопрос, который касался безопасности работы драйверов GPU. Слушатель ссылался на кейсы с "подламыванием" механизма управления видеопамятью драйверов на Android для интегрированных ускорителей семейства ARM Mali и спросил, как наша ОС сможет этому противостоять. Поэтому в данном материале я подробно расскажу о сути этой коварной атаки, а также рассмотрю и другие типы атак через GPU. В заключение я смоделирую подобные сценарии для нашей микроядерной KasperskyOS и покажу, как мы их митигируем. Читать далее ## How Apple's App Store Model and Browser Restrictions Relate to the EU's DMA DevFeed: [How Apple's App Store Model and Browser Restrictions Relate to the EU's DMA]() Original publisher: [Read original article]() Author: Alex Russell Published: 2025-10-11T00:00:00Z Content type: opinion Language: en Sources: [Alex Russell]() Topics: [interoperability](), [Data Space](), [web applications](), [Web](), [App](), [browser](), [iOS]() Tags: [app](), [apple](), [appstores](), [browser](), [competition](), [dma](), [eu](), [interoperability](), [opensocieties](), [policy](), [right-to-repair](), [web](), [web-applications](), [webdev]() ### AI overview This opinion article argues that Apple's App Store model depends on control over app distribution and browser access. It links Apple's opposition to interoperability and browser engine choice under the EU's Digital Markets Act to the company's ability to collect revenue from developers and users. ### Source excerpt Eric Prouzet And now we see it clear, like a Cupertino sunrise bathing Mt. Bielawski in amber: Apple will censor its App Store at the behest of the Trump administration without putting up a fight. It will twist words into their antipodes to serve the powerful at the expense of the weak. To better serve autocrats, it will talk out both sides of its mouth in ways it had previously reserved for dissembling arguments against threats to profits, like right-to-repair and browser choice. They are, of course, linked. Contents Who's Afraid of the Big Bad Web? Dots Unconnected "Who should rule?" The Price of High Modernism is Dignity Endnote: Let's Talk About Google Apple bent the knee for months, leaving many commentators to ask why. But the reasons are not mysterious: Apple wants things that only the government can provide, things that will defend and extend its power to extract rents, rather than innovate. Namely, selective exemption from tariffs and an end to the spectre of pro-competition regulation that might bring about real browser choice. Over the past few weeks, Tim Apple got a lot what he paid for,1 with the full weight of the US foreign and industrial policy apparatus threatening the EU over DMA enforcement. This has been part of a full-court press from Cupertino. Apple simultaneously threatened the EU while rolling out fresh astroturf for pliant regulators to recline on. This is loud, coordinated, and calculated. But calculated to achieve what? Why is the DMA such a threat to Apple? Interoperability. The DMA holds the power to unlock true, safe, interoperability via the web. Its core terms require that Apple facilitate real browser engine choice, and Apple is all but refusing, playing games to prevent powerful and safe iOS browsers and the powerful web applications they facilitate. Web applications that can challenge the App Store. Unlike tariffs, which present a threat to short-term profits through higher costs and suppression of upgrades in the near term, inter ## Apple's Dispute With the EU Over DMA Compliance and Browser Competition DevFeed: [Apple's Dispute With the EU Over DMA Compliance and Browser Competition]() Original publisher: [Read original article]() Author: Alex Russell Published: 2025-09-25T00:00:00Z Content type: opinion Language: en Sources: [Alex Russell]() Topics: [browser](), [Security](), [iOS](), [PWA](), [push-notification](), [Web]() Tags: [apple](), [browser](), [browsers](), [competition](), [dma](), [eu](), [geofencing](), [ios](), [iphone](), [pdf](), [push-notification](), [pwa](), [sdk](), [security](), [webdev]() ### AI overview The article argues that Apple is misrepresenting the European Union's enforcement of the Digital Markets Act and shifting responsibility for its own compliance decisions onto regulators. It focuses on alleged barriers affecting browser competition on iOS, including geofencing, restricted PWA and Push Notification APIs, SDK bugs, and difficult development entitlements. ### Source excerpt Contents Lies by Any Other Name Great Artists Steal Dear Tech Reporters: Access Is Not A Beat This blog is failing on several levels. First, September 2025 is putting the "frequent" in "infrequently", much to my chagrin. Second, my professional mission is to make a web that's better for everyone, not to tear Apple down. But just when I thought I was out, they pull me back in. Over the past 24 hours, Cupertino has played the hits from its iPhone-era anti-user, anti-business, anti-rule-of-law power trip. To recap: Apple sent a demand that the EU give up on DMA enforcement in a petulant and utterly misleading press release that mostly served to catalogue Apple's own failures to comply. Cupertino's kept astroturf outfit -- ACT | The App Association -- penned unhinged misinformation for consumption by US regulatory types (h/t Damien Geradin). The EC then called Apple's bluff. Make no mistake about what's going on: Apple is claiming that the EU is forcing Apple to adopt interpretations of the DMA that no other party has, which the EC itself has not backed, and which are "forcing" Apple to avoid shipping features in the EU. Or, put another way, Apple wants to launder the consequences of its own anticompetitive, anti-user choices through a credulous tech press. The goal is to frame regulators for Apple's own deeds. Lies by Any Other Name If this smells like bullshit, that's because it is. Apple tried similar ploys last year when it sprung a blatant attempt to kill PWAs on the EU as a price for having the temerity to regulate. The plan, it seemed then, was to adopt an exotic reading of the DMA and frame the EC for killing PWAs. What Apple's attempting now is even more brazen, particularly after 16+ months of serial non-compliance since the DMA came into force (h/t OWA). Remember that: Apple's browser, and by extension every iOS browser, fails on basic security and privacy controls, putting users at risk constantly. Apple serially misrepresents this situation to anyone who will ## Apple's iOS 17.4 Changes Threaten Progressive Web App Features in the EU DevFeed: [Apple's iOS 17.4 Changes Threaten Progressive Web App Features in the EU]() Original publisher: [Read original article]() Author: Alex Russell Published: 2024-02-25T00:00:00Z Content type: opinion Language: en Sources: [Alex Russell]() Topics: [PWA](), [iOS](), [Web](), [Mobile]() Tags: [browsers](), [competition](), [compliance](), [device-apis](), [dma](), [geofencing](), [ios](), [push-notifications](), [pwa](), [shortcuts](), [web](), [webdev]() ### AI overview The article argues that Apple's iOS 17.4 changes in the EU will restrict progressive web app capabilities, including storage, push notifications, app-like interfaces, and device APIs. It contrasts the threatened changes with continued PWA support on Windows and Android and frames them as a response to the EU Digital Markets Act. ### Source excerpt Update: OWA is out with an open letter appealing to Apple to do better. If you care about the future of the web, I encourage you to sign it, particularly if you live in the EU or build products for the common market. After weeks of confusion and chaos, Apple's plan to kneecap the web has crept into view, menacing a PWApocalypse as the March 6th deadline approaches for compliance with the EU's Digital Markets Act (DMA). The view from Cupertino. The DMA requires Apple to open the iPhone to competing app stores, and its lopsided proposal for "enabling" them is getting most of the press. But Apple knows it has native stores right where it wants them. Cupertino's noxious requirements will take years to litigate. Meanwhile, potential competitors are only that. But Cupertino can't delay the DMA's other mandate: real browsers, downloaded from Apple's own app store. Since it can't bar them outright, it's trying to raise costs on competitors and lower their potential to disrupt Apple's cozy monopoly. How? By geofencing browser choice and kneecapping web apps, all while gaslighting users about who is breaking their web apps. The immediate impact of iOS 17.4 in the EU will be broken apps and lost data, affecting schools, governments, startups, gamers, and anyone else with the temerity to look outside the one true app store for even a second. None of this is required by the DMA, as demonstrated by continuing presence of PWAs and the important features they enable on Windows and Android, both of which are in the same regulatory boat. The data loss will be catastrophic for many, as will the removal of foundational features. Here's what the landscape looks like today vs. what Apple is threatening: PWA Capability Windows Android iOS 17.3 iOS 17.4 App-like UI ✅ ✅ ✅ ❌ Settings Integration ✅ ✅ ✅ ❌ Reliable Storage ✅ ✅ ✅ ❌ Push Notifications ✅ ✅ ✅ ❌ Icon Badging ✅ ✅ ✅ ❌ Share-to PWA ✅ ✅ ❌ ❌ App Shortcuts ✅ ✅ ❌ ❌ Device APIs ✅ ✅ ❌ ❌ Apple's support for powerful web apps wasn't stellar, b ## Debugging xHCI scratchpad allocation and port-status handling DevFeed: [Debugging xHCI scratchpad allocation and port-status handling]() Original publisher: [Read original article]() Published: 2017-08-07T00:00:00Z Content type: opinion Language: en Sources: [Front Page on ReactOS Website]() Topics: [Hardware](), [Code](), [dma](), [Operating system]() Tags: [code](), [dma](), [driver](), [free](), [hardware](), [memory-management](), [open-source](), [os](), [react](), [reactos](), [win32](), [winapi](), [windows]() ### AI overview A developer describes implementing xHCI scratchpad buffer allocation while debugging incorrect port-status results. The article explains scratchpad buffers, DMA physical-address handling in Windows drivers, and a VMware xHCI implementation that required zero scratchpad buffers; the underlying port-status issue remained unresolved in the supplied text. ### Source excerpt Recently I've worked on Scratchpad allocation. Scratchpad buffers are PAGESIZE blocks of system memory which the xHCI uses to store its internal state. xHCI can request 0 to 1024 buffers. Number of buffers required is given in the HCSPARAMS1 register. Each buffer is a PAGESIZE block aligned to PAGESIZE boundary. Scratchpad buffer array is an array which contains addresses of the scratchpad buffers. Its size is equal to the number of maximum scratchpad buffers required by the hardware. ## SATA AHCI Driver GSoC - Week 5 Update DevFeed: [SATA AHCI Driver GSoC - Week 5 Update]() Original publisher: [Read original article]() Published: 2016-06-29T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [Programming](), [dma](), [debug](), [Code]() Tags: [debug](), [dma](), [driver](), [free](), [gsoc](), [open-source](), [os](), [programming](), [react](), [reactos](), [update](), [win32](), [winapi]() ### AI overview A GSoC Week 5 update on a SATA AHCI driver describes progress on AHCI port programming and the Interrupt Handler, with port programming still untested. The author has added ATA/ATAPI DMA data transfer support, is focusing on normally queued I/O while NCQ is disabled, and plans to implement Srb functions and add NCQ in later revisions. ### Source excerpt From beginning of week I started reading more stuffs (core) about AHCI and trying to plan a road map which I will follow after making first version of AHCI driver. Throughout the week I made some progress with Interrupt Handler and AHCI port programming. Though I have finished port programming routine and next I will complete Interrupt Handler followed by Srb functions. Port programming is still untested (fingers crossed), because I can't test it without Interrupt Handler routine (I can, but It will not give 100% surety) looking forward to get these two routines tested in this week.