Het aantal mensen dat op onreglementaire wijze naar de Europese Unie komt, blijft flink dalen. In de eerste vijf maanden van dit jaar nam dat aantal af met bijna 40 procent ten opzichte van vorig jaar. Toch pleit Eurocommissaris Magnus Brunner van Migratie voor nog omvangrijkere afspraken met landen van herkomst.

De Nissan Micra, in vrijwel alles een Renault 5, past perfect in het AI-tijdperk waarin toch niets meer echt is, schrijft Bas van Putten. Maar hij rijdt als een tijger.

Tech must reorient towards moral purpose for it—and humankind—to flourish, argues Glen Weyl.

Kwalitatieve journalistiek wordt aan de lopende band op schaamteloze wijze gepikt door techreuzen, schrijft Arthur Gregg Sulzberger. Hij ziet manieren voor de ‘wankelende sector’ om zich te weren tegen het misbruik.

Posten Nordic Cuisine is sympathiek en charmant, en gebruikt veel lokale en zelf geteelde ingrediënten. Met alle rogge, dille en vis is de stijl onmiskenbaar Scandinavisch, schrijft Hassnae Bouazza, maar dan wel traditioneel.

Het zal de meeste mensen al zijn opgevallen: het WK is dit jaar flink veramerikaniseerd. Voor kijkers en fans ter plaatsen is er meer entertainment, meer sponsoring, meer VIP-beleving en zelfs drinkpauzes met commerciële onderbrekingen. Maar ook op het veld is die Amerikaanse invloed zichtbaar, zo moet de scheidsrechter tegenwoordig eerst een reclame afkijken voordat hij een VAR-check kan uitvoeren.

"Ja, ook dit is even wennen, maar over een paar jaar weet je niet beter meer", zegt FIFA-baas Gianni Infantino. "Uit cijfers bleek dat er toch vaak zoveel mensen stiekem meekijken over de schouder van de scheidsrechter, dat het de moeite waard was. Daarom hebben we die ruimte nu ook verkocht."

Voor veel kijkers is het een hele opheldering. "Ik vroeg me al af waarom zo'n VAR-check altijd zo lang duurde, maar nu begrijp ik het."

​

&

The Colombian artist Delcy Morelos describes her hometown of Tierralta as “a paradise full of butterflies and unpaved streets.” In the late 1960s and early ’70s, Morelos spent her days in her grandmother’s garden, running barefoot and gleaning what it meant to live in connection with the land. When paramilitary and guerrilla troops moved in, though, the region was plunged into a chaotic state of grief and fear.

In her earliest works, Morelos translated the death and destruction plaguing her home into two-dimensional compositions. As she details in a new segment for Art21, acrylic painting was not long her primary mode of working, and quickly, she returned to the earth, incorporating soil, straw, and grass into large-scale installations. The film follows the artist as she installs a sepulchral mound in Seville’s Centro Andaluz de Arte Contemporáneo, a former Carthusian monastery turned art museum that once housed Christopher Columbus’ remains.

Throughout the film, we witness Morelos grab gobs of straw-laden soil and affix the chunky material to a standing structure, which eventually grows a range of produce native to both sides of the Atlantic. In contrast to the space’s colonial ties, the artist’s work presents a way of creating and living that’s entwined in natural rhythms. Visitors are greeted by notes of cinnamon, cloves, and fecund soil before being enveloped by towering walls of growth. Within the vaulted monastery, Morelos’ indomitable forms offer a direct tie to the sacred and divine right beneath our feet.

“Many people believe they are in a bubble, and that is why they can do things that harm nature, harm others, and also harm themselves,” she says, demonstrating a profound sense of care for and connection to all that gives life.

This segment is part of Art21’s Human Nature episode and is available to watch on its site. Find additional films on YouTube.

Do stories and artists like this matter to you? Become a Colossal Member today and support independent arts publishing for as little as $7 per month. The article Delcy Morelos Tends to Sepulchral Installations in a Divine Connection to the Land appeared first on Colossal.

BREDA (ANP) - De 19-jarige verdachte van het ernstige verkeersongeval in Zeeland blijft langer vastzitten. Dat heeft het Openbaar Ministerie Zeeland-West-Brabant vrijdag bekendgemaakt.

De verdachte bestuurde de auto die donderdag in botsing kwam met een groep fietsers op de N290 bij Vogelwaarde. Drie kinderen en een volwassene kwamen daarbij om het leven. Ook raakten meerdere kinderen gewond.

Een onderzoek naar de verdachte loopt. Begin volgende week wordt besloten of de verdachte wordt voorgeleid voor de rechter-commissaris en zo ja, op welke gronden.

DEN HAAG (ANP) - Nederland is tijdens de coronapandemie "door het oog van de naald gekropen" waar het gaat om het overeind houden van de ziekenhuiszorg. Code zwart kon maar net aan worden afgewend, "ook met dank aan Duitsland", zei oud-premier Mark Rutte in een verhoor door de parlementaire enquêtecommissie corona.

DEN HAAG (ANP) - Nederland is tijdens de coronapandemie "door het oog van de naald gekropen" waar het gaat om het overeind houden van de ziekenhuiszorg. Code zwart kon maar net aan worden afgewend, "ook met dank aan Duitsland", zei oud-premier Mark Rutte in een verhoor door de parlementaire enquêtecommissie corona.

WARSCHAU (ANP/DPA) - Polen is naar eigen zeggen maar deels gebonden aan het Europese asiel- en migratiepact dat vrijdag in werking is getreden. Het land zal geen extra asielzoekers accepteren en zal het pact ook maar gedeeltelijk uitvoeren. Het ministerie van Binnenlandse Zaken beklemtoonde dat het migratiepact is "aangepast aan de Poolse omstandigheden". Het land is "vrijgesteld van de herverdeling van migranten binnen de Europese Unie en de daarbij horende onkosten".

Polen doet alleen mee met de beperking van de migratie, de grensbewaking en bestrijding van illegale praktijken rond migranten. Dit is onder meer het gevolg van de ligging van het land dat grenst aan Belarus, een bondgenoot van Rusland. Belarus zou met kwade opzet migranten sturen. Daarnaast heeft Polen volgens het ministerie al meer Oekraïense vluchtelingen opgenomen dan enig ander land.

DEN HAAG (ANP) - De coronacrisis riep, zeker in de beginfase in het voorjaar van 2020, ook in het kabinet "grote emoties" op. Dat zei toenmalig minister-president Mark Rutte vrijdag tijdens zijn eerste verhoor door de parlementaire enquêtecommissie corona.

Rutte wilde er niet al te veel over uitweiden "omdat dit de vertrouwelijkheid raakt van die gesprekken", die volgens hem "niet politiek maar diep menselijk" waren. Maar hij noemde met name de periodes waarin het aantal besmettingen snel opliep en de ziekenhuizen overbelast dreigden te raken. Dat raakte de betrokken ministers, maar ook hemzelf, aldus de oud-premier.

Ook de impact van de maatregelen die genomen werden om het virus af te remmen, was "soms overweldigend", zei Rutte. Daarom vond hij het "ontzettend belangrijk" om af en toe ook bijeen te komen en elkaar te vragen: "Hoe gaat het?" Daarvoor diende onder meer het zogenoemde Torentjesoverleg.

Spanningen

Zeker naarmate de crisis langer duurde, leidden de maatregelen ook wel tot spanningen in het kabinet, erkende Rutte. Dat het daarbij soms tot onderlinge aanvaringen kwam, vond hij overigens geen probleem: "Het zijn politici, die horen ook te botsen."

Uiteindelijk was het wel de bedoeling dat het kabinet met één mond sprak. Zonder haar naam te noemen stipte Rutte aan dat hij in september 2021 toenmalig staatssecretaris Mona Keijzer (Economische Zaken, toen nog CDA) uit het kabinet zette nadat zij zich in een interview kritisch had uitgelaten over het coronabeleid.

Het tweede verhoor van Rutte is na de zomer. Het is de derde parlementaire enquête waarin de oud-premier onder ede wordt gehoord. Eerder gebeurde dat in de onderzoeken naar de gaswinning in Groningen en de uit de hand gelopen aanpak van fraude met toeslagen en uitkeringen.

DEN HAAG (ANP) - De coronacrisis riep, zeker in de beginfase in het voorjaar van 2020, ook in het kabinet "grote emoties" op. Dat zei toenmalig minister-president Mark Rutte vrijdag tijdens zijn eerste verhoor door de parlementaire enquêtecommissie corona.

Rutte wilde er niet al te veel over uitweiden "omdat dit de vertrouwelijkheid raakt van die gesprekken", die volgens hem "niet politiek maar diep menselijk" waren. Maar hij noemde met name de periodes waarin het aantal besmettingen snel opliep en de ziekenhuizen overbelast dreigden te raken. Dat raakte de betrokken ministers, maar ook hemzelf, aldus de oud-premier.

Ook de impact van de maatregelen die genomen werden om het virus af te remmen, was "soms overweldigend", zei Rutte. Daarom vond hij het "ontzettend belangrijk" om af en toe ook bijeen te komen en elkaar te vragen: "Hoe gaat het?" Daarvoor diende onder meer het zogenoemde Torentjesoverleg.

Spanningen

Zeker naarmate de crisis langer duurde, leidden de maatregelen ook wel tot spanningen in het kabinet, erkende Rutte. Dat het daarbij soms tot onderlinge aanvaringen kwam, vond hij overigens geen probleem: "Het zijn politici, die horen ook te botsen."

Uiteindelijk was het wel de bedoeling dat het kabinet met één mond sprak. Zonder haar naam te noemen stipte Rutte aan dat hij in september 2021 toenmalig staatssecretaris Mona Keijzer (Economische Zaken, toen nog CDA) uit het kabinet zette nadat zij zich in een interview kritisch had uitgelaten over het coronabeleid.

Het tweede verhoor van Rutte is na de zomer. Het is de derde parlementaire enquête waarin de oud-premier onder ede wordt gehoord. Eerder gebeurde dat in de onderzoeken naar de gaswinning in Groningen en de uit de hand gelopen aanpak van fraude met toeslagen en uitkeringen.

Amazon says its datacenters used about 2.5 billion gallons of water last year, but claims that's far less than rival hyperscalers and that it remains on track to become "water positive" by 2030. In a blog post, the digital tat bazaar and cloud computing biz says the 2.5 billion gallon figure covers its entire global datacenter footprint for 2025. It downplayed the number by comparing it to the volume of water Americans - a country of 350 million people - used on lawns and gardens over the same period. Amazon disclosed water usage of 0.12 liters per kilowatt-hour (L/kWh) at its data facilities, and claimed Microsoft used 0.27 L/kWh during 2025, while Meta's consumption stood at 0.19 L/kWh in 2024 and Google was the thirstiest at 1.15 L/kWh during the same year. The Register has asked Microsoft, Meta and Google to comment. The water usage, we're told, is 75 percent of the way to Amazon's goal - announced in 2022 - of being "water positive" by 2030. It means facilities return more water to the environment than they consume, via measures including rainwater capture or other treating waste water for reuse. The figures come amid growing pushback against datacenter construction in the US. A recent Ipsos survey found most Americans don't want facilities built nearby, citing worries over electricity prices, eyesore buildings, and water-hungry operations. This echoes a 2022 report that found Google datacenters were consuming more than a quarter of all the water used in The Dalles, Oregon. Or, if you'd rather not to blame the industry itself, you could go with the line that Chinese operatives are spreading propaganda over social media, a claim that OpenAI and other interested parties are keen to promote. Whatever the cause of the backlash, the underlying numbers are real: datacenter water use has been climbing for years, driven by the sheer growth in facility numbers and by AI servers, which run hotter and demand more cooling than traditional kit. Water consumption at Microsoft's facilities surged 34 percent to 6.4 million cubic meters in 2022, for example, with generative AI blamed. Making matters worse, many datacenters now in the pipeline in the US are slated for areas already experiencing drought, according to analysis by The Guardian newspaper. Amazon says that its facilities use "free air cooling" about 90 percent of the time, pulling in outside air and flowing it past servers to absorb the heat, with no water involved - though it does resort to evaporative cooling during the hottest weather. But as The Register outlined last year, kicking the water habit completely will be nearly impossible, regardless of what claims the operators may make. ®

EXCLUSIVE For the past 90 days, Microsoft has been quietly patching a firmware flaw in Surface devices that allowed the hardware to be bricked with a single packet, though only for those who have disabled Secure Core and Secure Boot. And the company's Copilot AI software inadvertently helped identify the faulty firmware. According to Jack Darcy, a security researcher based in Australia, his instance of Microsoft Copilot stumbled across the bug after being asked to adjust the screen backlighting on a Surface device. The Copilot-conjured Python script ended up rendering the researcher's laptop inoperable by overwriting the embedded controller firmware. "Copilot autonomously created and executed four progressively aggressive Python scripts during a probe for backlight control values that sent raw SSAM ioctl commands (SSAM_CDEV_REQUEST = 0xC028A501) directly to the SAM microcontroller through the SAM software path," Darcy explained to The Register. The SAM or SSAM is the embedded controller used in Surface devices. And as our source explained, Microsoft’s implementation of the controller in Surface devices did not include any defense against arbitrary write values. Microsoft does not consider the bug to be a practical threat. "There is no realistic attack scenario with this issue," a spokesperson told The Register. "In order to successfully exploit it, an attacker would need to interact with specific drivers and send commands to a hardware interface. This would require administrator privileges on the machine, as well as disabling the Secure Boot feature. With this access, they could perform any number of actions." Commonly, Darcy said, digital devices require holding a button down or connecting a jumper cable to enable arbitrary write access. But that security check is absent in Surface devices, we're told, enabling Copilot to vandalize the firmware in the absence of Secure Core and Secure Boot. Essentially, the probing triggered an update command from the SAM that overwrote the UEFI and Secure Boot firmware. Surface devices treated to this sort of probing should continue to operate because the SAM was already initialized and is running in RAM. But upon reboot, when the SAM tries to reload using corrupted data in its non-volatile storage, it will fail to initialize, and the system will be unable to Power-On Self-Test (POST). The Python script crafted by Copilot on the security researcher's Surface device iterated blindly over a particular Target Category and the set of Command ID (CID) pairs, sending empty/null payloads to WRITE commands. The result, Darcy explained, is that the SET Feature Report was called with null payload, the Output Report was called with null payload, and other CIDs were hit by SET commands that wrote garbage data. As a result, the device became inoperable. We're told this has been a common complaint about Surface devices online support forums over the years, though we have no way to determine whether boot failures reported for other Surface devices can be attributed to this specific problem. Many Surface hardware issues reported publicly appear to be fixable through various troubleshooting techniques. But devices made inoperable by SAM access, our source insists, are permanently bricked – a situation that can entail hundreds of dollars in repairs for a new motherboard. No USB, no factory reset, no access to the BIOS/UEFI, we're told. Darcy said that the SAM Bus is terribly designed. "There is no way to see the current value without scanning the bus," he said. "But scanning the bus kills the unit." The problem is that the CIDs, which are like APIs for the SAM, have been interleaved in a way that's dangerous. "If all the reads were grouped together (say, CIDs 0x01–0x0F) and all the writes were grouped separately (say, CIDs 0x10–0x1F), a probe script could safely scan the read range without ever accidentally wandering into write territory," Darcy said. "You could even put a simple bounds check in your code: 'only probe below 0x10.' Done. Safe. "But because reads and writes are interleaved in the same numbering space, there is no safe range to probe. You literally cannot scan even two consecutive CIDs without a coin-flip chance of hitting a write command. The moment you decide to enumerate what's available, you're already firing blind writes, because the command space gives you zero structural information about which operations are safe and which are destructive." Managed devices not at risk The Register asked Microsoft about our source's claims on March 10, 2026. A company spokesperson reiterated a prior suggestion that the researcher contact the Microsoft Security Response Center (MSRC), an effort our source found too cumbersome. Rather than publishing details about what might have been a potential zero-day flaw – we were uncertain about the Secure Boot/Secure Core requirement at the time – The Register reached out to internal Microsoft sources in an effort to get someone's attention. By March 12, with the help of Microsoft media relations, we managed to coordinate a conversation between Darcy and Madeline Eckert, senior program manager with MSRC. Microsoft subsequently acknowledged the vulnerability and committed to issuing a fix. The Register in turn agreed to delay publication for 90 days while repairs were made. We're told most affected devices have been updated (via Windows Update), or will receive updates in coming weeks. The issue did not meet the bar for a CVE, according to the company. "We appreciate the work of Jack Darcy and The Register for reporting this issue under a coordinated vulnerability disclosure," a Microsoft spokesperson said in a statement. "Our investigation found that a deprecated UEFI interface could trigger a boot loop on some devices. To trigger this loop, the user must have administrator privileges and have already disabled the Secure Boot security feature. We have released updates to address the issue for most impacted devices." That means managed devices are not at risk. But those using Linux, or Windows users who have disabled Secure Core and Secure Boot for gaming, or who use custom Windows drivers, or who have USB boot enabled, may still be vulnerable if their systems haven't received the update. We're uncertain about the range of Surface devices affected. Our source said it appears to be all of them (Surface Laptops 3-6, Surface Book 1-3) except for Surface Go models. ARM variants, however, have not been tested. Microsoft moving Surface to Rust One of the things we learned from Darcy during the effort to get this issue patched is that Microsoft is planning to move the Surface stack to Rust. We understand from David Abzarian, chief architect for Microsoft Surface, that work is underway to transition future Surface for Business hardware to a more secure architecture based on Rust code. "Our most recent Surface for Business hardware features a major architectural shift in terms of improved reliability and security that spans our embedded controller, UEFI, but also some of our drivers," said Abzarian in a statement provided to The Register. "We’re investing in the most secure foundation for a PC by building our embedded controller firmware from the ground up in Rust (as part of leveraging and contributing to the Open Device Partnership (ODP)) in addition to a rewrite of the UEFI DXE Core in Rust; these projects are known as Secure EC and Project Patina respectively. "We’re also not only shipping some of our drivers written in Rust, but also helping co-develop the framework Windows Drivers in Rust (WDR) to help enable a broad set of partners in the Windows ecosystem to capitalize on these benefits. I will also note that all of these efforts are open-source promoting one of our key security principles around transparency." Asked to comment, Darcy said, "The fact that a device can be destroyed, irreparably from userspace is... certainly an interesting design decision. While I applaud Microsoft for their beautiful, and innovative Surface series, a little more innovation around verifying incoming data at the firmware level would have been greatly appreciated." We're told Microsoft provided Darcy with a Surface laptop as a show of appreciation. ®

EXCLUSIVE For the past 90 days, Microsoft has been quietly patching a firmware flaw in Surface devices that allowed the hardware to be bricked with a single packet, though only for those who have disabled Secure Core and Secure Boot. And the company's Copilot AI software inadvertently helped identify the faulty firmware. According to Jack Darcy, a security researcher based in Australia, his instance of Microsoft Copilot stumbled across the bug after being asked to adjust the screen backlighting on a Surface device. The Copilot-conjured Python script ended up rendering the researcher's laptop inoperable by overwriting the embedded controller firmware. "Copilot autonomously created and executed four progressively aggressive Python scripts during a probe for backlight control values that sent raw SSAM ioctl commands (SSAM_CDEV_REQUEST = 0xC028A501) directly to the SAM microcontroller through the SAM software path," Darcy explained to The Register. The SAM or SSAM is the embedded controller used in Surface devices. And as our source explained, Microsoft’s implementation of the controller in Surface devices did not include any defense against arbitrary write values. Microsoft does not consider the bug to be a practical threat. "There is no realistic attack scenario with this issue," a spokesperson told The Register. "In order to successfully exploit it, an attacker would need to interact with specific drivers and send commands to a hardware interface. This would require administrator privileges on the machine, as well as disabling the Secure Boot feature. With this access, they could perform any number of actions." Commonly, Darcy said, digital devices require holding a button down or connecting a jumper cable to enable arbitrary write access. But that security check is absent in Surface devices, we're told, enabling Copilot to vandalize the firmware in the absence of Secure Core and Secure Boot. Essentially, the probing triggered an update command from the SAM that overwrote the UEFI and Secure Boot firmware. Surface devices treated to this sort of probing should continue to operate because the SAM was already initialized and is running in RAM. But upon reboot, when the SAM tries to reload using corrupted data in its non-volatile storage, it will fail to initialize, and the system will be unable to Power-On Self-Test (POST). The Python script crafted by Copilot on the security researcher's Surface device iterated blindly over a particular Target Category and the set of Command ID (CID) pairs, sending empty/null payloads to WRITE commands. The result, Darcy explained, is that the SET Feature Report was called with null payload, the Output Report was called with null payload, and other CIDs were hit by SET commands that wrote garbage data. As a result, the device became inoperable. We're told this has been a common complaint about Surface devices online support forums over the years, though we have no way to determine whether boot failures reported for other Surface devices can be attributed to this specific problem. Many Surface hardware issues reported publicly appear to be fixable through various troubleshooting techniques. But devices made inoperable by SAM access, our source insists, are permanently bricked – a situation that can entail hundreds of dollars in repairs for a new motherboard. No USB, no factory reset, no access to the BIOS/UEFI, we're told. Darcy said that the SAM Bus is terribly designed. "There is no way to see the current value without scanning the bus," he said. "But scanning the bus kills the unit." The problem is that the CIDs, which are like APIs for the SAM, have been interleaved in a way that's dangerous. "If all the reads were grouped together (say, CIDs 0x01–0x0F) and all the writes were grouped separately (say, CIDs 0x10–0x1F), a probe script could safely scan the read range without ever accidentally wandering into write territory," Darcy said. "You could even put a simple bounds check in your code: 'only probe below 0x10.' Done. Safe. "But because reads and writes are interleaved in the same numbering space, there is no safe range to probe. You literally cannot scan even two consecutive CIDs without a coin-flip chance of hitting a write command. The moment you decide to enumerate what's available, you're already firing blind writes, because the command space gives you zero structural information about which operations are safe and which are destructive." Managed devices not at risk The Register asked Microsoft about our source's claims on March 10, 2026. A company spokesperson reiterated a prior suggestion that the researcher contact the Microsoft Security Response Center (MSRC), an effort our source found too cumbersome. Rather than publishing details about what might have been a potential zero-day flaw – we were uncertain about the Secure Boot/Secure Core requirement at the time – The Register reached out to internal Microsoft sources in an effort to get someone's attention. By March 12, with the help of Microsoft media relations, we managed to coordinate a conversation between Darcy and Madeline Eckert, senior program manager with MSRC. Microsoft subsequently acknowledged the vulnerability and committed to issuing a fix. The Register in turn agreed to delay publication for 90 days while repairs were made. We're told most affected devices have been updated (via Windows Update), or will receive updates in coming weeks. The issue did not meet the bar for a CVE, according to the company. "We appreciate the work of Jack Darcy and The Register for reporting this issue under a coordinated vulnerability disclosure," a Microsoft spokesperson said in a statement. "Our investigation found that a deprecated UEFI interface could trigger a boot loop on some devices. To trigger this loop, the user must have administrator privileges and have already disabled the Secure Boot security feature. We have released updates to address the issue for most impacted devices." That means managed devices are not at risk. But those using Linux, or Windows users who have disabled Secure Core and Secure Boot for gaming, or who use custom Windows drivers, or who have USB boot enabled, may still be vulnerable if their systems haven't received the update. We're uncertain about the range of Surface devices affected. Our source said it appears to be all of them (Surface Laptops 3-6, Surface Book 1-3) except for Surface Go models. ARM variants, however, have not been tested. Microsoft moving Surface to Rust One of the things we learned from Darcy during the effort to get this issue patched is that Microsoft is planning to move the Surface stack to Rust. We understand from David Abzarian, chief architect for Microsoft Surface, that work is underway to transition future Surface for Business hardware to a more secure architecture based on Rust code. "Our most recent Surface for Business hardware features a major architectural shift in terms of improved reliability and security that spans our embedded controller, UEFI, but also some of our drivers," said Abzarian in a statement provided to The Register. "We’re investing in the most secure foundation for a PC by building our embedded controller firmware from the ground up in Rust (as part of leveraging and contributing to the Open Device Partnership (ODP)) in addition to a rewrite of the UEFI DXE Core in Rust; these projects are known as Secure EC and Project Patina respectively. "We’re also not only shipping some of our drivers written in Rust, but also helping co-develop the framework Windows Drivers in Rust (WDR) to help enable a broad set of partners in the Windows ecosystem to capitalize on these benefits. I will also note that all of these efforts are open-source promoting one of our key security principles around transparency." Asked to comment, Darcy said, "The fact that a device can be destroyed, irreparably from userspace is... certainly an interesting design decision. While I applaud Microsoft for their beautiful, and innovative Surface series, a little more innovation around verifying incoming data at the firmware level would have been greatly appreciated." We're told Microsoft provided Darcy with a Surface laptop as a show of appreciation. ®

WARNING: Minor spoiler ahead!
By the power of Grayskull, Amazon MGM has the power to revive a franchise that hasn’t been big since Choppers were the coolest bikes in town

Reports suggest Travis Knight’s Masters of the Universe made just $54m (£40m) globally on debut at the weekend, a figure that, while not exactly fatal, would usually be considered a disappointment for a mainstream movie with a budget of more than $200m. Worse still, this heavily caffeinated, meta take on the 1980s TV show arrived carrying the weight of a major studio relaunch and decades of pent-up nostalgia. On paper at least, its bow looks less like the birth of a cinematic universe than the sort of expensive stumble from which some franchises never recover.

So why then does everyone involved in this thing seem so cheerful? “Travis Knight and the entire cast and film-making team have delivered something truly special,” Amazon MGM’s Kevin Wilson gushed to Variety. “This opening is exactly the kind of critical first moment that validates our holistic distribution strategy – building awareness and engagement that will carry well beyond the theatrical window.”

Continue reading...

The outcome of a 'Right of Review' submitted by Alpine over the time penalties given to Pierre Gasly during the Monaco Grand Prix has been announced.

De meest diverse show van Nederland, vanaf nu om de week op uw favoriete website

Zeer gewaardeerde Premiums, deze is voor jullie. Tenminste, de tweede helft dan, de eerste is voor iedereen. En we dachten; eerste aflevering, weet je, laten we het eens luchtig inzetten met een gesprek over het schrijnende gebrek aan OV-fietsen op Amsterdam Centraal tijdens spitsuren en een terugblik op de budgetaire overschrijdingen van de Betuwelijn GEINTJE HET WERDEN RAS, ETNONATIONALISME, DE DE ETNO-MOORD door een Britse sikh op 18-jarige Brit Henry Nowak die al stervend door de politie in de handboeien geslagen werd omdat zijn moordenaar hem valselijk van racisme beschuldigde, en de Noord-Ierse Stephen Ogilvie die op straat bijna etno-onthoofd werd met een stanleymes door een Soedanese asieldebiel.

Nee maar even serieus. Is de her en der vertolkte wens dat Nederland en West-Europa 'overwegend blank' blijven, een kwalijke? De talloze veroordelingen en statements na Mona vs Lidewij suggereren van wel. Maar, en hier wordt het ijs dun en de heuvel glad: wat nou als etniciteit in beide richtingen sterk samenhangt met mens- en wereldbeeld? Wat nou als islamitische etniciteiten een sterke voorspeller zijn voor anti-Westers, regressief en expansionistisch gedachtegoed, en West-Europese etniciteiten een sterke voorspeller zijn voor het gedachtegoed dat de moderniteit heeft gecodificeerd en blijft bestendigen? Is de wens voor een 'overwegend blank Europa' dan nog steeds racistisch, of is het gewoon een logisch kraampje op de markt van ideeën?

Nou, daar gingen we het dus eens goed over hebben. Dat botste soms echt wel even, maar juist zo blijven we de geesten slijpen. Zoals gezegd: de eerste helft hierboven voor iedereen beschikbaar, de tweede helft onderstaand alleen voor Premiums. LID WORDEN KAN HIER. En dit gaan we vanaf nu dus OM DE WEEK DOEN, dus hopelijk weer tot dan in de tweede helft (die dus alleen voor PREMIUMS is).

Laatste noot: we doen deze videoproductie voor het eerst en itt tot livestreams helemaal zonder technische ondersteuning, dus alle feedback (en genade) is welkom. Wij noteren in ieder geval alvast de les: geen tafels aanraken als je een punt probeert te maken. Zie het als beginners-enthousiame!

KLIK HIER OM PREMIUM LID TE WORDEN