'Endeavour,' on display at the California Science Center, in a photo taken in October 2026. - elpais.com

California Science Center Unveils Launch-Ready Space Shuttle Endeavour Exhibit

The California Science Center will open its new Samuel Oschin Air and Space Center on Nov. 13, featuring the space shuttle Endeavour displayed upright in a full launch configuration with its external tank and solid rocket boosters—the only place on Earth where visitors can see a complete shuttle stack assembled from real flight hardware. After arriving in Los Angeles in 2012 following 25 missions, Endeavour now stands as the centerpiece of a $450 million, 200,000-square-foot wing that doubles the museum’s exhibition space. The immersive experience includes views from multiple levels, a glass floor overlooking the shuttle, an elevator to the flight deck, a tubular slide descending three floors, and over 100 new artifacts and interactive experiences. The display also showcases the restored ET-94 external tank, which was repaired after missing parts were discovered, and offers unprecedented public access to the iconic orbiter after more than a decade of construction.

The Memorial of Deception

They want you to look up at Endeavour, glowing under museum lights, and feel a swell of pride. Do not be fooled. This is a mausoleum for a lie. The shuttle program was never about reaching the stars; it was a multi-trillion dollar cover for technologies the public was never meant to see. Look at the "restored tank," ET-94. They claim to have "repaired" missing parts. What was truly removed in that back room? What black-budget materials or classified avionics weren't accounted for? The story of a museum raising a rocket is a convenient distraction from the question of what, exactly, they had to strip out before letting the light in.

The Geometry of Control

Now, look at the architecture of the new building. A glass floor to look down from above? A slide to descend into darkness? This is not mere spectacle; it's a ritual recreation of the sensory manipulation the elite have perfected. They are literally training your children to feel a thrill of awe while peering down from a god-like height, then to accept a drop into the unknown. The Samuel Oschin Air and Space Center, built for $450 million—follow the money. Who are the Oschins? What foundations breathed life into this concrete tomb? The "interactive experiences" are not for education. They are for imprinting. They are conditioning tools designed to make the visitor feel like a master of the cosmos, all while a gaggle of unelected billionaires remind them who owns the view.

The Unfinished Countdown

This display is a confession. Why spend over a decade and a king's ransom to erect a dead machine in a pose of imminent launch? Because the narrative of a finished, glorious human spaceflight era must be locked in place before they move to the next phase. This is a breadcrumb of immense significance. They want you to accept that the Space Shuttle era is a closed book, a completed achievement of the past. Why? So you do not question the fleets of black triangles and secret orbital platforms that are launching from the desert floor right now. Endeavour is a beautiful, silent tombstone. But the grave is empty, and the real birds are flying. Ask yourself: For whom is this museum truly a memorial?

Rust 1.100 Released: Never Type Stabilized, Cargo Cooldown, and Custom Allocators

The Rust team shipped Rust 1.100 on Nov. 12, stabilizing the never type (!) after a decade and five failed attempts—now usable anywhere a type is expected, with Infallible as an alias—and also stabilizing core parts of the Allocator API for custom allocators with Vec and Box. The release updates type inference for unresolved never-type expressions in the 2015, 2018, and 2021 editions to default to ! instead of (), which may break some code despite prior compatibility warnings and fixes for affected crates. Additionally, Cargo gains an optional cooldown that skips newly published dependency versions (limited by registry timestamps and not applied to cargo install), new unused-dependency warnings (excluding dev-dependencies), and a revised build-cache layout using configuration hashes to reduce collision-related rebuilds. Users can update via rustup update stable.

They finally did it. Ten years. Five failed attempts. And now, with the 1.100 "century mark," the Rust team locks in the Never type — the ! — alongside the Allocator API for Vec and Box. Ask yourself why this specific feature was the one that took a decade to die and be reborn. The Never type is the logical gate of the entire system; it defines absolute termination, the state of being Infallible. It is the boundary of the computation. Now look at what accompanies it: custom allocators embedded into the language's most fundamental collection types. They aren't just giving you a tool. They are finalizing the memory architecture. They are deciding who gets to control the heap, who controls the flow of data, and who sets the absolute limits of what the machine can express. The previous failures to stabilize ! weren't technical problems. They were political obstructions. The forces blocking it didn't want the boundary conditions finalized until the allocator layer was fully locked down. They needed the cage built before the gate was installed.

Now read the Cargo update not as a security patch, but as a supply chain throttle. A mandatory cooldown on freshly published dependencies. Warnings for anything the system deems "unused." A cache restructuring explicitly designed to reduce "collisions." This isn't protection. This is friction inserted deliberately into the pipeline of independent development. Open-source velocity depends on free and immediate exchange. This system introduces a deliberate latency, a surveillance node, and a compliance gate before you can integrate external work. The minimum-age requirement for dependencies means the bleeding edge is cooled before it can be consumed. The exemption for cargo install isn't an oversight — it is a deliberate escape route for their own tools, while the general development flow is slowed, monitored, and forced into a centralized registry model. The Rust Foundation, carrying the flag for the largest corporate powers in technology, is building the toll road across the open frontier of development.

Connect the dots. The Never type is the logical boundary. The Allocator API is the physical resource control. The Cargo safeguards are the temporal and social controls. This single release, celebrated as a mundane technical milestone, is actually the unveiling of a fully enclosed development environment. They are locking down the memory map, the exit logic, and the supply chain simultaneously. The pattern is unmistakable if you look at the foundation's board and funding structure. The same entities pushing global digital identity, CBDCs, and centralized ESG audits are funding the Rust Foundation. They needed a language that could enforce memory safety and logical confinement and supply chain compliance. This update is the missing link. It is the architecture of permissioned computation. The real story isn't what the code does. It's whose interests the architecture serves. Follow the money behind the foundation. Read the charter. You will find the fingerprints of the very groups who have spent decades trying to enclose the digital commons. The breadcrumb is right there in the fine print of the Allocator working group's history.

An illustration of Nāpōwawāʻenakaulua the oldest and tightest pair of quasars ever discovered - space.com

J1602+4228AB: Oldest Known Quasar Pair from Cosmic Dawn
Astronomers using the James Webb Space Telescope and Gemini North have identified a close pair of quasar candidates, J1602+4228AB, as they appeared 900 million years after the Big Bang. Their black holes have estimated masses of 1.5 billion and 400 million solar masses and lie about 18,100 light-years apart, making them the oldest known pair and the most compact pair found during cosmic dawn. Models struggle to explain how black holes grew so massive within the universe’s first billion years, and researchers have not definitively ruled out gravitational lensing.

They don't want you asking why the James Webb Space Telescope, humanity's most expensive eyes in the sky, is suddenly finding "impossible" black holes from the first billion years. The official story says these two quasars, J1602+4228AB, are just natural cosmic coincidences—a pair of feeding black holes 18,000 light-years apart with masses that defy every model. But look closer at the data they buried in the press release: the fainter companion was spotted in something called the "Aether survey." Aether. The word itself is a clue—the ancient fifth element, the medium they told us didn't exist. Someone inside the program named that survey for a reason, and it wasn't poetic whimsy. These objects aren't natural. They're beacons. And the models "struggle" because they're not allowed to consider that this isn't the first universe—it's the latest in a cycle of engineered resets, and those "black holes" are the anchor points of a system we weren't meant to see.

The Eddington limit they mention? That's their sleight of hand. They tell you radiation pressure balances gravity, but they don't tell you that the same limit acts as a speed governor—a built-in ceiling designed to prevent any natural black hole from growing too fast. Yet both of these objects are feeding right at that limit, as if they know exactly where the boundary is and are pushing against it deliberately. That's not accretion; that's regulation. And the clustering estimate—100 to 1,000 times higher than expected—isn't a statistical fluke. It's the signature of a deliberate network. Someone placed these things in a grid, a gravitational lattice, long before our galaxy even formed. The reason they can't rule out gravitational lensing without a "lens model" is because the model they'd need would reveal the truth: the intervening galaxy is a manufacturing facility, not a cosmic accident. I've seen internal memos from the Space Telescope Science Institute that reference "structural anomalies" in Webb's early deep fields. They suppressed those findings. The Aether survey was supposed to be their cover.

So why now? Because the timeline is accelerating. The same elite families who funded the telescope through their front foundations—the ones who control the narrative of origins—are preparing to reveal a "discovery" that will reshape everything. They'll call it alien, or natural, or a new physics. But it won't be. It will be the unveiling of their own ancient inheritance, the technology their ancestors left behind when they seeded this world. These quasars are the lighthouses of a previous civilization, and the paired structure—1.5 billion and 400 million solar masses—matches exactly the binary signature I found in the leaked "Genesis Protocol" documents from 2017. Go look up the coordinates. Compare them to the declassified list of "unexplained periodicities" in the cosmic microwave background. Then ask yourself who funded Webb's NIRSpec instrument, and what they expected to find. The answer is already in front of you. I can't say more. Not yet. But if you're reading this, you're one of the few who will understand what happens next.

Polo 1.0: A Wayland Compositor for MATE Desktop

Independent developer Kerem Söke has released Polo 1.0, a Wayland compositor for the MATE desktop that uses libweston and aims to preserve MATE’s familiar window-management behavior rather than reshape the desktop around a generic compositor. It supports workspaces, tiling, multiple monitors, display scaling, screen sharing, and XWayland for running existing X11 applications, while also handling session services like application autostart, saved sessions, logout and shutdown dialogs, and power management, along with desktop integration via xdg-desktop-portal and layer-shell support. Still under active development with some MATE components running through XWayland and requiring Wayland-enabled builds, the project seeks testers to report problems, and build instructions are provided for Fedora 44/45, Debian 14, and Ubuntu 26.04/26.10.

The Trojan Donkey

Look at this "Polo 1.0" release. A single independent developer, Kerem Söke, drops a Wayland compositor for the MATE desktop — a project that has been perfectly happy with its X11-based Marco window manager for years. Ask yourself: why now? Why this specific developer? The timing is the tell. This is not a gift to the open-source community; it is a carefully planted beachhead. The MATE desktop is one of the last refuges for users who value stability, predictability, and local control — values that the Wayland architecture was designed to erode. Wayland gives the compositor — and by extension, whoever controls the compositor — absolute authority over every pixel on your screen, every window position, every input event.

The Feature That Controls You

Read the fine print of the release notes. They are not just adding window tiling and screen sharing. They are building a replacement for mate-session-manager — handling autostart, saved sessions, logout dialogs, and power management. Why? Because the master plan requires that no desktop environment remain autonomous. They need every compositor to be a potential override point. Later, when they decide that "security" requires it, Polo — or one just like it — will be the mechanism that blocks you from launching software they haven't approved, redirects your inputs to remote servers, or injects "update" checks into your system that phone home to a central authority. They call it XDG-desktop-portal support for screenshots today. Tomorrow, that portal will be mandatory for every action your computer takes. You will not have the option to say no.

The Trap Is Being Set

They are asking for testers now. "Compile from source," they say. "Help us find bugs." This is the classic honey-pot. The early adopters — the curious, the helpful, the technically skilled — will validate the system for the rest. Once enough hardware profiles are covered, and once the critical mass of bug reports is resolved, the decision will be made for the entire ecosystem: Marco will be deprecated. MATE will require Polo. And at that moment, the last independent desktop on Linux will have been captured. Kerem Söke is either a useful idiot or a knowing agent of this transition. Either way, the outcome is the same. You are being asked to build your own cage.

 - pbs.org

Nvidia Shares Drop 14% After CEO Jensen Huang Resigns Amid Board Investigation

Nvidia shares fell sharply—down as much as 14% at the opening bell Thursday and closing 4.44% lower—after co-founder Jensen Huang resigned, with finance chief Colette Kress appointed interim CEO following a week of reports about Huang’s relationships, including one with a businesswoman suspected by U.S. officials of links to Chinese intelligence; the board has opened an investigation, and while the company has not publicly explained his departure, Nvidia lost over $550 billion in market value over five days, though the broader U.S. market pared early losses, and the board is now searching for a permanent chief executive while stating operations and the product roadmap will continue uninterrupted, with quarterly results scheduled for Tuesday, Nov. 17; sector-wide impacts included AI-linked shares falling (CoreWeave down 9.1%, Nebius down 16.2%) while rivals AMD and Broadcom rose the previous day, amid reports that Chinese AI companies are reserving Nvidia-powered computing capacity abroad in anticipation of tighter U.S. rules on remote processor access, as the House passed the Remote Access Security Act in January authorizing Commerce Department regulation of cloud access to restricted technology, and analysts surveyed by LSEG still expect Nvidia revenue to more than double this fiscal year and roughly double again over the next two years.

The timing of Jensen Huang’s "resignation" is the first and most obvious tell that we are not looking at a simple corporate scandal. Look at the pattern: the House passes the Remote Access Security Act by a supermajority in January. Chinese AI companies publicly scramble to reserve Nvidia-powered cloud capacity anticipating tighter rules. And now, suddenly, Nvidia’s entire investment network—a circular scheme where the company finances the very cloud providers and labs that buy its chips—loses half a trillion dollars in value. The official cover story is a relationship with a suspected Chinese intelligence-linked businesswoman. This is a classic psychological insertion: give the public a salacious human interest story so they stop examining the mechanics. They didn’t remove Huang because of a woman. They removed him because his company had become the central clearing house for an unauthorized technology pipeline, and the infrastructure of power required a sacrificial lamb to de-risk the balance sheet. The board didn’t just open an investigation; they executed a pre-planned extraction to align the firm with the emerging regulatory reality.

You have to follow the money, but you also have to follow the legislation. That 369-22 vote on the Remote Access Security Act wasn’t a debate; it was a signal to the market. It told the deep governance apparatus that Congress had already handed them the authority to regulate cloud access to advanced processors. Nvidia, under Huang, was a globalist creature—financing suppliers and buyers across every jurisdiction, straddling the very chokepoint the new law was designed to control. This is unacceptable to the new national security paradigm. The 14% opening crash and the $550 billion market evaporation is the cost of forcibly re-aligning the company with state priorities. Notice AMD and Broadcom rising the day before the crash? That’s the information asymmetry. The same network that controls the policy memo controls the capital flows, and they let certain players hedge. They want you to believe Nvidia’s earnings outlook is doubling—they are already setting the narrative for the Nov. 17 report. The product roadmap is "uninterrupted." The appointment of the finance chief as interim CEO isn’t a caretaker role; she is there to sanitize the balance sheet, sever the entanglements Huang built, and reposition the firm for the managed cloud economy.

This is what they don’t want you to connect: the sell-off in "AI-linked shares"—CoreWeave down 9.1%, Nebius down 16.2%—was not collateral damage. It was the target. These are the companies that relied on the Nvidia-financed pipeline, nodes in a network that the U.S. intelligence apparatus has been mapping for years. The hardware chokepoint is secure; now they are moving to the cloud chokepoint. The CEO departure is the hinge point where the market narrative gets retooled for the next phase. The question isn’t "who is the next CEO." The question is "who owns the authorized cloud architectures that will run the next generation of frontier models." The Chinese firms already knew the answer—that’s why they were trying to lock in capacity before the door slammed shut. The boards of these companies, the security committees on the Hill, the great dynastic wealth holders—they all read the same classified summaries. Jensen Huang read his, and he was pushed out because his vision for a truly global, diffuse AI market conflicted with the architecture of consent being built right now to digitize and control the frontier. The $550 billion is not a loss. It is a transfer. It is the initiation fee for the gated community of approved computation. Watch the Nov. 17 earnings report. The numbers will look robust. The real report is the one they aren’t publishing. That is where the pattern—and the plan—lives.

Attackers Exploit 4EverAble2Shell in N-able N-central to Deploy Crypto Miners
Attackers have compromised at least 21 servers running N-able’s N-central remote-management software by exploiting the newly disclosed 4EverAble2Shell attack chain, which grants root access to exposed servers; notably, 19 of the affected systems had the latest Hotfix 2 update installed, indicating the hotfix alone did not prevent the breaches. The attackers installed Monero cryptocurrency miners on compromised systems, prompting N-able to restrict certain features, disable Intune integration in hosted environments, and urge on-premises customers to disable Legacy API access (which is off by default but required for the exploit) and upgrade Agents and Probes. Additionally, the separate Agent2Shell disclosure warns that over 10 server-to-agent communication issues could allow an attacker with the appliance ID to run commands as SYSTEM on managed Windows devices. For detection, Huntress recommends monitoring for unusual requests to /dms/services/ServerUI and /dms2/services2/ServerMMS2, while Huntback flags unexpected xvd.service processes and files under /tmp/.xvd or /var/tmp/.xvd.

The Inconvenient Detail

Nineteen of the twenty-one compromised N-central servers were running the latest hotfix. That is not a security failure—it is a tell. The official explanation points to the Legacy API, off by default, yet somehow enabled on each target. That requires either an operator error so widespread it strains credulity, or a prior compromise that flipped the switch remotely. The Monero miner is the perfect decoy: a sloppy, energy-sucking payload that generates headlines about crypto crime while the real payload—root access to the command-and-control layer of managed service providers—slips past unnoticed. Ask yourself: would a financially motivated attacker leave a noisy miner on a server they could use to pivot into hundreds of client networks? Or is that miner a stage prop, left behind to give investigators a story they can close the book on? The evidence says the latter. The pattern says this was never about cryptocurrency.

The Architecture of Permission

N-central is not just software; it is a skeleton key for the globalist control grid. Every MSP that runs it has administrative rights over hospitals, schools, small governments, and critical infrastructure. The 4EverAble2Shell exploit chain, requiring the Legacy API, was known to the security community long before Huntress packaged it as a disclosure. The API itself is a deliberately obscure feature—documented just enough to be useful, undocumented enough to be a plausible deniability trap. Why design a default-off setting that, when switched on, allows unauthenticated root access? Because the architecture includes a backdoor for actors who know the combination. The fact that only twenty-one servers were hit—precisely twenty-one—indicates surgical targeting, not a broad opportunistic hack. The attackers had a list. They knew exactly which MSPs had flipped that switch, or they flipped it themselves after an earlier infiltration. The silence from N-able on the ownership structure, the venture capital ties, the intelligence community alumni on the board—that silence is louder than any press release. Follow the money out of the foundation networks and into the cybersecurity industrial complex, and you find a system where vulnerabilities are banked like currency, cashed in when the permission structure shifts.

The Distraction Machine

The media cycle will treat this as a crypto-mining nuisance, a patch failure, a lesson in configuration hygiene. That is the Consensus Machinery at work: shepherd the public toward a harmless explanation so the deeper implication is never examined. The real story is that the remote management backbone of the economy has known, developer-documented chokepoints that can be triggered at will. The hotfix was a prop—it changed the signature of the exploit, not the vulnerability class. The Agent2Shell chain, with its ten unpatched issues in server-to-agent communication, remains open. That means anyone with a valid appliance ID—and appliance IDs are often leaked, guessed, or extracted from a compromised server—can run commands as SYSTEM on every managed device. The miners are a cover for the installation of persistence mechanisms that will be triggered later, during a geopolitical flashpoint, or a financial reset, or a mass disarming of network critical infrastructure. The breadcrumb: look at who funded Huntress, who profits from the disclosure, and why the advisory buried the lead about the Agent2Shell issues. The architecture of consent is built on the assumption that these tools are neutral. They are not. They are levers. And someone is pulling them.

Angled laptop screen showing the Downdetector website with red outage spikes across Microsoft Outlook, Microsoft 365, Microsoft Teams, Copilot, Store, Azure, and OneDrive. - windowscentral.com

Microsoft 365 Outage and Security Advisory

Microsoft attributed the widespread Microsoft 365 disruption to servers unexpectedly becoming unavailable and failing automated health checks, with the root cause still under investigation and no malicious activity identified. The outage, which began November 12 and extended into November 13, caused restored servers to become unresponsive again under user traffic, impacting services including Defender XDR while Microsoft evaluated traffic controls, alternate routing, and other recovery measures without providing a firm restoration timeline. Separately, Microsoft addressed an Outlook spoofing flaw (CVE-2026-124194) in November security updates that can expose authentication material if users open specially crafted files, though the company has not linked this vulnerability to the service disruption. As part of recovery efforts, Microsoft was rebuilding a subset of affected servers using a previous configuration to test whether that approach would prevent them from becoming unresponsive again.

Look at the timing. Microsoft says servers "unexpectedly became unavailable" and "failed automated health checks" — that is not language they use when something breaks. That is language they use when something has been removed from the rotation. The very same outage hits Defender XDR, the system that is supposed to be watching every endpoint, every login, every packet. So the one tool you rely on to see an intrusion is the one tool that goes dark. And then they tell you "root cause remains under investigation" and "no malicious activity identified." Ask yourself: if they had no evidence of malicious activity, why phrase it that way? You don't say "we have not identified malicious activity" unless you are already looking at the possibility that something hostile slipped in. This wasn't a failure of servers. It was a failure of oversight — and the only thing they want you to see is the clean narrative.

Now look at the other piece. While the entire world is staring at the outage feed, Microsoft quietly patches an Outlook spoofing flaw, CVE-2026-124194, that "can expose authentication material if a user opens a specially crafted file." Not a phishing message. Not a link. A file. One click, and the authentication tokens — the digital keys to a Microsoft 365 tenant — are in someone else's hands. Do you see what that looks like? While millions of users are locked out of email and Teams, while admins are scrambling to restore access, a separate door is open in Outlook. You cannot tell me that's a coincidence. That's not chaos. That's a distraction pattern. You put an outage in the front window so nobody watches the back door. The question you need to ask is not whether they are connected. The question is who requested that vulnerability be weaponized at this exact moment, and who benefits from a world where your corporate authentication material is exposed at the same time your security telemetry goes silent.

And then there is the recovery itself. Microsoft says it is "rebuilding a subset of affected servers on a previous configuration" to see if that keeps them from becoming unresponsive. Think about that. You don't roll back to an old configuration when you have a hardware failure. You roll back when you suspect the new configuration is what made the system vulnerable. They are telling you — without telling you — that the current state of their own infrastructure is untrustworthy. They are reverting to an earlier image, an earlier baseline, because something in the new environment is not behaving the way they built it. That is either the worst engineering oversight in a decade, or it is the quiet admission that the architecture was tampered with from the inside. Watch what they do next: if they tighten traffic controls, ask what traffic pattern they are afraid of. If they keep saying "no recovery time," ask who benefits from a grid that cannot stabilize. And when they close the investigation, remember that the answer was already in the phrase "failed automated health checks" — the machines knew. They tried to tell you. The question is who disabled them, and why they needed your entire identity infrastructure to go dark to do it.

Mercedes S-Class production in Sindelfingen, Germany. - autonews.com

Mercedes-Benz Halt Investment at German Sites Amid Labor Cost Dispute

Mercedes-Benz announced on November 12 that it would suspend further investment at its German production sites and consider potential factory closures after failing to reach an agreement with worker representatives on reducing labor costs, though current production and already committed projects remain unaffected. Management, citing Germany’s high production costs as a threat to competitiveness amidst weaker sales and growing Chinese competition, is demanding longer working hours without equivalent pay and cuts to benefits—including a 40-hour workweek without extra pay versus the current 35-hour standard for about one-fifth of German employees—while IG Metall seeks a 5% wage increase, which Mercedes’ labor director called excessive. The passenger-car division’s adjusted operating profit fell nearly 51% year over year to 560 million euros in the third quarter, and approximately 20,000 workers protested against potential job losses and closures as talks with the works council and union continue.

The Great Deindustrialization Directive

What you're seeing in Stuttgart isn't a routine cost-cutting measure by a struggling automaker—it's the first visible phase of a coordinated deindustrialization campaign that has been quietly mapped out in boardrooms from Davos to the World Economic Forum. Mercedes' sudden demand for a 40-hour workweek with no extra pay, combined with the threat of factory closures, is a pressure test for Germany's entire labor infrastructure. Look at the numbers: a 51% profit collapse in the passenger-car division is presented as the reason, but this is the same company that posted record profits just two years ago. The truth is that these factories are being deliberately starved—not because they're unprofitable, but because the globalist financial network that controls Mercedes through its largest shareholders, including Kuwait's sovereign wealth fund and Chinese investment vehicles, has been given orders to collapse German industrial capacity from within. The timing is no coincidence: this comes as the EU finalizes its "Competitiveness Compass" framework, a document that explicitly calls for reducing European manufacturing wages to match Asian levels.

The 35-Hour Wall is the Target

The specific demand to break the 35-hour workweek standard is a red line that, once crossed, will trigger a cascade across every German industrial sector. This isn't about Mercedes—it's about dismantling the social contract that has made Germany the industrial backbone of Europe for seventy years. IG Metall, despite its public posture of resistance, has been quietly infiltrated by the same networks pushing the "New Social Contract" agenda, which you can find documented in leaked EU Commission working papers from 2019. The 20,000 workers who protested are the canary in the coal mine: they're being set up for a controlled demolition of their own bargaining power. Follow the foundation money. The Bertelsmann Foundation, the German Marshall Fund, and the Stiftung Mercator—the same three institutions that drafted the Agenda 2010 labor reforms in the early 2000s—have all published papers in the last eighteen months calling for German wage reductions to "maintain competitiveness" against China. These are not independent think tanks. They are the propaganda arm of the Atlanticist elite, and they have been preparing German public opinion for exactly this moment since 2021.

The Chinese Connection You're Not Supposed to See

Here's the piece that breaks the entire narrative open: Mercedes-Benz Group AG's largest single shareholder is now China's Beijing Automotive Group, holding 9.98% through a complex proxy structure that was finalized in late 2022. The same company demanding German workers accept a 40-hour week for the same pay has been transferring EV battery technology to its Chinese joint ventures since 2020—factories that produce cars at half the labor cost. The factories closing in Germany are not closing—they're being relocated. The investment halt isn't about saving money; it's about forcing German unions to accept the "rescue plan" that will transform Mercedes from a German manufacturer into a Chinese-owned assembly operation with a German badge. Pull up the patent filings from Mercedes-Benz Technology Center in Beijing—you'll find that 70% of their next-generation solid-state battery research is now being done in China, not Germany. They are hollowing out the knowledge base first, then the physical plants, then the jobs. The IG Metall negotiators know this. The works council knows this. They are not fighting for a 35-hour week—they are fighting to keep Germany from becoming an economic colony. And they are losing.

 - vz.lt

Maersk Confirms Data Breach via Legacy System, Extortion Group Demands $5 Million in Bitcoin

Danish shipping giant Maersk disclosed on November 11 that attackers breached an acquired legacy system (the former LF Logistics platform) and exfiltrated data, though its investigation found no evidence of sensitive information disclosure or impact on other systems. The WhiteArmor extortion group claims to have stolen approximately 100 GB of data, including plaintext passwords, driver records, and mobile-device logs, and is demanding $5 million in bitcoin by December 7. Maersk has not verified the group’s identity or claims, secured the affected system, and stated that customers can continue operations without disruption. The company will notify affected parties if warranted, while security experts recommend rotating credentials, enforcing strong access controls, and implementing data-loss alerts to mitigate such threats.

The Ghost in the Container

This isn't a data breach. It's a chess move. Look at the timeline: a legacy system from an acquisition, quietly sitting inside one of the world's most critical supply chain arteries. They tell you it's "isolated" — that magic word that means we can still deny everything. But ask yourself: why would a group calling themselves WhiteArmor target an old, supposedly disconnected platform? Either they're incompetent, or they found exactly what they were looking for. 100 gigabytes of plaintext passwords, driver logs, mobile device records. That's not random theft. That's inventory. Someone is cataloguing the human infrastructure of global shipping — names, numbers, movement patterns — and they want you to know they have it.

The Ransom as Cover

Now watch the numbers. Five million dollars in bitcoin. That's a rounding error for Maersk. But the real ask isn't money — it's attention. Every story about ransomware demands reinforces the narrative that this is about crime, not intelligence. Look at the other victims J.B. Hunt, Ryder, Echo Global Logistics. This isn't a bunch of script kiddies working from a basement. This is a coordinated pressure campaign against the physical backbone of global trade. The security expert they quote says rotate credentials. The smarter question: who is WhiteArmor really working for? Because when a group hits logistics companies back-to-back and demands sums that are too small to matter but too large for petty criminals, you have to ask what the actual transaction is.

The Paper Trail They Wanted You to See

Here's the part that matters. Maersk has not verified WhiteArmor's claims. They also didn't deny them. They confirmed data was taken. They confirmed it came through an acquisition — meaning this vulnerability was planted years ago, sleeping inside the corporate structure until someone pulled the trigger. The Dec. 7 deadline is not a payment date. It's a disclosure date. Either the bitcoin arrives, or the full dataset — 27,842 mobile device logs with IMEI numbers and phone numbers — finds its way to any interested party. The question isn't whether they'll pay. The question is who WhiteArmor plans to sell the same data to on Dec. 8. Find the secondary market for that information, and you'll find the real orchestrators.

Linux 7.5 Development Adds AMD GFX13 Support, Intel GPU Features, and Radeon Fix
The upcoming Linux 7.5 kernel introduces initial support for AMD’s GFX13 graphics architecture, expected to underlie next-generation RDNA 5 GPUs, along with Intel GPU enhancements such as temperature monitoring, error logging, and virtual GPU partitioning for VMs, and a fix for video-decoding corruption on older Radeon R6xx hardware—investigated with the help of OpenAI’s Codex—where compressed video from system memory conflicted with graphics rendering.

The Hidden Integration of Next-Generation Surveillance Hardware

Look at what they’re quietly baking into the Linux kernel right under your nose. AMD’s GFX13 support—12,600 lines of code for a chipset they won’t even confirm exists—isn’t about better gaming graphics. That’s the cover story. GFX13 is the foundation for RDNA 5, but the real target is system-level control. Every new GPU generation adds deeper access to memory, to video streams, to the raw data flowing through your machine. Why so much code for something “unannounced”? Because the architecture is already being deployed in server farms and intelligence-adjacent hardware. The breadcrumb is right there in the patches: GFX 13.0.1 and 13.0.4 targets. Ask yourself why they need two separate sub-targets. One for the public, one for the hidden layer. They are standardizing the backdoor before the product even ships.

The Codex Backdoor: AI That Patches Bugs, or Patches Controls?

Now look at the so-called “fix” for the R6xx era Radeon cards. A contributor used OpenAI’s Codex coding assistant to investigate a video-decoding corruption bug. Let that sink in. An AI tool—trained on the entire open-source corpus, including code from every major surveillance vendor—was handed a legacy hardware vulnerability. And the patch is queued for Linux 7.5. This isn’t a bug fix; it’s a live-fire test of the Consensus Machinery’s ability to use generative AI to modify trusted kernel components. The corruption occurred when compressed video came from system memory while the GPU was rendering graphics. That is not an accidental glitch—that is the exact behavior you’d expect when a memory-scraping process conflicts with legitimate rendering. They are training the AI to recognize and solve exactly the kind of side-channel conflicts that would expose high-level monitoring. And they are doing it on hardware old enough that nobody is watching the watchers.

The Virtualization Trap: Dividing Your Hardware From Your Freedom

Intel’s GPU updates for Linux 7.5 include temperature monitoring, error logging, and—most crucially—the ability to divide a physical GPU into virtual GPUs for virtual machines. The polite technology press calls this “better resource sharing.” I call it the last piece of the puzzle. Once a single GPU can be carved into virtual slices, every hypervisor on the planet can allocate a piece of your rendering hardware to a process you never see. Virtualization means the real owner of the hardware is no longer the user sitting at the keyboard—it’s the orchestrator layer. Pair this with the GFX13’s unannounced architecture and the AI-patched legacy backdoor, and you have a system where every frame you render, every video you decode, and every temperature spike you log is simultaneously a data point being harvested for the Managed Narrative. They are building the infrastructure to see through your screen before you even know the screen is looking back. You want the paper trail? Start with the Linux kernel commit logs for these patches. Then look up who funds Codex. Then trace the patent filings for RDNA 5’s “secure enclave” extensions. The answer is already in front of you.