All posts by Davi Ottenheimer

Player Ruin as Record Revenue: Catastrophe is the EVE Online Product

EVE is just a 19th-century speculative colonial venture.

Investors pour capital into territorial claims that evaporate, while brokers profit regardless. They hired a central bank economist because it is not a game in any classical sense. It’s an extraction economy with a UX that undermines human resistance to being defrauded.

Go resets. Chess resets. Risk resets.

EVE is a dopamine attachment to manufacture performance from feelings of permanent loss and longing (social engineering), and thus by design never resets.

Assets persist under enforced scarcity where destruction carries forward, so every battle means sunk cost, forever. It captures players’ sense of purpose/home and monetizes illness. Tribal destruction is turned into Lord of the Flies as a recurring revenue business model, instead of a warning of how not to be and what to prevent. The catastrophe is reported as profit.

The overall destruction, paired with the collapse of a major alliance, made 2025 a defining year for the game. Fenris Creations reports that November and December of that year were the two highest-revenue months in the game’s 23-year history. James says the fall of Pandemic Horde, which cost him his virtual job and home, still hurts.

Berlin Museum Island Website Full of Nazi Sympathy

People sometimes ask me “can you believe the AfD is getting votes in the suburbs of Berlin?” Yes, I can believe the Nazi party is getting votes again. And here’s just one reason why.

The Staatliche Museen zu Berlin (State Museums of Berlin) marked the 75th anniversary of the war’s end with a piece about the fighting on the Museumsinsel (Museum Island). It is written from the perspective of the Nazi. The way they tell it, the museums under Hitler’s thumb are the victim of Soviet forces. The war gets depicted like it’s weather, until the Reich falls and then the war’s end becomes something to complain about. The Soviets, surrounding the Germans hoarding their stolen loot, are framed as invaders and thieves.

The words and framing of this museum is the unbelievable part for me. The Germans voting for AfD after reading this Nazi-fluffery and disinformation is the believable part.

Start with the headline they use.

Invasion auf der Insel

It’s almost English. Invasion! Their island of museums is being invaded! By who? The liberators coming to force the Nazis out of the museums.

Did the Nazis consider surrendering the museums so there wouldn’t be any harm to them? What if they had welcomed liberation instead of willfully destroying their own country? The Nazis, despite knowing their “success” in war was over by 1943, were blowing up German churches at the last minute to prevent them being liberated. Some villages around Berlin have memorials that say their seven centuries old church once stood there undisturbed until the Nazis came to destroy it in April 1945.

Are the Nazis not primarily responsible for using Museum Island as their base of violence, which required violence to stop them?

The army that entered Berlin, having already opened the death camps to the east, gets described as the one aggressor? That is the invasion? The same week in 1945 that Hitler’s regime fell, the museum 75 years later deployed claims that the Nazis were victims of aggression. Anyone else? They don’t seem to care enough to say it.

Then look at how twelve years mysteriously disappear into a passive voice. Museums don’t typically disappear time like this by accident. It reads to me as a purposeful omission.

waren die Museen geschlossen und ihre Objekte zum Schutz ausgelagert worden

They just say museums were closed. The objects were evacuated for protection. By whom, against what, the sentence declines to say. The war simply begins in 1939, on its own like a spring breeze.

The post carries the tags Nationalsozialismus and Provenienzforschung, then it delivers neither of them. Nothing is said about the dismissed Jewish staff. Nothing is said about the looted Jewish collections absorbed into the holdings. Nothing is said about the Entartete Kunst purge. The labels do the moral work as a wind up and then… nothing. The silence is deafening.

Now let’s talk about the German history of appropriation and theft from foreign states, which gets completely left out of a claim that someone arrived in Germany to commit appropriation and theft.

beispiellose Beschlagnahmeaktion der sowjetischen Trophäenbrigaden

Unprecedented, they say. They call out the Soviet trophy brigades because they commit Beutekunst, looted art.

Let me just put this in perspective, again. German museums already were the definition of looted art. Then the Reich turned on an industrial-scale looting machine across Europe. The idea that Nazi Germany would call anyone else arriving on their doorstep the one who is doing the looting, is as tone-deaf as it gets. It would be like Germans, notorious for stealing bicycles, accusing the Soviets of stealing bicycles.

To be specific, it’s well known that the Pergamon frieze, the Ishtar Gate, the Market Gate of Miletus, and the Mschatta facade were taken to Germany. That gets called the act of collection. But then someone taking them from Germany is accused of plunder.

Let me be even more precise about the harm this Berlin state website does to history.

The Pergamon frieze the post mourns as carried off by the Soviets was returned by the Soviets. In 1958 the USSR sent roughly 1.5 million objects back to the GDR, the altar among them, and it has been the museum’s centerpiece ever since. The institution that is propagating a public lament is standing on the object whose loss it is lamenting, restored by the people it casts as thieves. Their grievance works only by acting like all the clocks stopped working after Hitler committed suicide.

The particular seizure that the piece calls beispiellose, unprecedented, was the reverse of unprecedented. The Soviet trophy commissions operated under an explicit doctrine of compensatory restitution for what Germany had done to Soviet heritage: Peterhof and Tsarskoye Selo gutted, the Amber Room gone, Novgorod and Pskov burned, libraries and churches stripped across the occupied territory, with twenty-seven million Soviet dead.

When you hear a German say unprecedented after that, hopefully you see the problem immediately.

The piece is thus eyeballs deep already in Nazi fandom when it proposes a hero to the reader.

ganz der preußische Beamte

A loyal official is lauded for suffering a two and a half hour commute, serving straight through the Reich without a “break”. Millions of Jews are sent on locked railroad cars with no food, water or toilets to die. If they survive days of hell, they are murdered on arrival or soon after in death camps. But this guy is offered to the reader with human warmth in terms of his “struggle”. Every inch measured for this dutiful Prussian civil servant. His “hardship” described with affection.

But who is this guy really? Oh, Krickeberg ran the Völkerkundemuseum, the ethnology collection, which is to say he was the custodian of one of the largest hauls of colonial loot in Europe, the Benin bronzes among it. The warmth-figure literally is a face of mass scale plunder.

And then, there’s the street address. It pretends as though this is just any street with a name.

in der Prinz-Albrecht-Straße (heute Niederkirchnerstraße)

This was the specific street of the Gestapo and the SS leadership. It is the Topography of Terror today. The post hands you the old name, hands you the new name, and walks away dogwhistling for those who know the detail.

The sourcing is solid.

The author knows the archive cold enough to whistle.

The problem is the imbalance, the one side of history being told.

A museum sitting on the world’s quarried and shipped antiquities, on the anniversary of the Nazi regime’s collapse, found a way to spin up a story about itself as the only one who was wronged in WWII.

  • Inside Museum Island buildings: stone tablets carved by ancient civilizations. Why are the markings there? How did they get there?
  • Outside Museum Island buildings: stone columns carved by Soviet 7.62×54mm. Why are the markings there? How did they get there?

Berlin residents, especially the staff working at the museums, to this day still call their own work an acquisition yet call the Soviet work an invasion. Here’s the truth, the hardest part for Germans to face: the institution does rigorous perpetrator-history in its scholarship on the “official” record yet happily floats reflexive victim-history in its commemorations.

See also: the Berlin Deutsches Technikmuseum used a particularly irrelevant “birthday” celebration to falsely pump Hitler’s Reich to social media as the birth of computing, while claiming the real history is back at the office.

So yeah, the AfD (Nazi) party rises again in and around Berlin thanks to the curation of memory through “commemorations” that fail to maintain a record of who really suffered and why.

NJ Tesla Kills One With Phantom Brake: 91 Year Old Army Vet

Recently, a New Jersey owner of a Tesla documented phantom braking on the Garden State Parkway.

I live in New Jersey and periodically travel the Garden State Parkway to visit relatives. Phantom braking reliably occurs twice in response to specific overhanging signage (not overpasses). This occurs regardless of weather conditions and is readily reproducible. […] Why Tesla has chosen not to address the problem (particularly in light of their ambitious RoboTaxi rollout) is a mystery. My wife owns a 2025 Kia Sportage Hybrid … phantom braking has not occurred over 10K of driving….

The signs triggering the braking are generic, the kind that also would be found on Route 22, for example. Hold that thought.

Tesla has had these safety issues since the 2016 Model S and X, which is another way of saying their engineering put the defect into the “autopilot” capabilities almost from the very start, and their management apparently has only made things worse. After 2021 the phantom braking reports increased and became more severe, which many would argue was a result of removing radar sensors to replace them with cheap consumer-grade webcams.

Phantom braking therefore has been a subject of many prior blog posts here. It was a very notable defect in the first place, requiring attention, but Tesla uniquely seems to be getting only worse over time requiring some kind of logic to allow them to be on the road at all. The U.S. Office of Defects Investigation received 354 complaints alleging unexpected brake activation in 2021-2022 Model 3 and Model Y vehicles when it opened PE22-002 in February 2022, covering 416,000 vehicles. By June 2022 the count had climbed to 758. Recent litigation filings put the running total at more than 2,000 NHTSA complaints.

The most severe form of the Tesla defect is their deadly “complete stop” event. NHTSA describes this behavior as vehicles that unexpectedly apply the brakes at highway speeds, with such rapid deceleration occurring without warning (even repeatedly during a trip) that it’s a hazard to anyone around. Many owners complain they feared causing a rear-end crash, and many dead motorcyclists have proven that fear, not to mention the ones being run over by Tesla.

Now back to Route 22 in New Jersey.

A Tesla stopped dead in the middle of traffic flow and killed a 91 year old Army veteran. We should call it homicide. Stopping dead in a fast-moving lane is the signature failure NHTSA has logged for years, and Tesla shipped the system that produces it. Is it to blame?

Authorities have identified the 91-year-old man killed in a three-vehicle crash on Route 22 in Bridgewater last week. The collision occurred after a Tesla driver stopped in the middle of the road.

Hugh F. Johnson Jr., of Bridgewater, was driving a passenger car that struck an SUV that had stopped behind the Tesla, Bridgewater police said.

Johnson’s car then veered into the right lane before sliding left into the center median, where it struck a tree before coming to rest at 4:05 p.m. on May 31.

Johnson died of his injuries at an area hospital. His passenger, a 93-year-old woman, was hospitalized with minor injuries.

The sequence of events began when a Tesla headed east near Grove Street came to a “complete stop” in the center lane, Bridgewater police said.

The report says no charges have been filed yet against Tesla. Meanwhile, Tesla has been flagged again for multiple recent low-visibility crashes, after the company acknowledged data and labeling limitations that NHTSA believes led to under-reporting of crashes, on top of a separate probe into Tesla filing crash reports months past the deadline.

Tesla told regulators that limitations in company data and labeling may have led to under-reporting of additional incidents.

Limited visibility, limited reasoning, limited data. Tesla is so incapable of safety, it shouldn’t be legal.

Apple WWDC Announces Privacy Leap Off a Cliff

Step one: Apple took its private cloud compute (PCC), a privacy story that it built on its own silicon, and moved its most capable model onto NVIDIA GPUs in Google’s cloud.

Step two: Apple repeated the identical privacy promise, as if step one didn’t happen.

The trust stack that Apple is talking about now is based on non-Apple nodes, which come from NVIDIA Confidential Computing, Intel TDX, and Google’s Titan. In other words Apple’s own Secure Enclave is not in it. Apple still keeps the signing key and an append-only ledger of hardware it doesn’t build. Fine. But there’s no reproducible build, so nobody outside Apple can confirm the published source is what’s actually running on the node.

That’s a problem. Not a new one either.

Trail of Bits (TOB) audited the same stack on WhatsApp and rated eight findings HIGH, every one a way to pass attestation while the measurement was incomplete. Apple’s reproducible-build gap sits on top of that: with no reproducible build, no outside party can confirm the published source is the binary that runs.

Apple put this on stage as innovation. Apple’s own words for PCC are a generational leap over traditional cloud security.

Leap off a cliff?

Apple launched an architecture with the same reproducible-build gap reported on Meta as TOB-WAPI-18, on the same TEE stack where TOB rated eight other findings HIGH. (August 2025: PDF)

External researchers need to reproduce and examine the CVM images to verify the system. TOB admit this isn’t a TEE flaw, it’s an implementation and deployment issue. And on top of that, Apple’s own admission is their Google nodes don’t have the full protections yet, because “ramping throughout the summer.”

Great, a ramp before the cliff.

Apple is on the big stage pushing a future promise on top of a past vulnerability. Two things to watch. Whether the summer ramp ever reaches the protections Apple already promised. And whether anyone outside Apple can verify the build once it does. Until both land, the privacy promise is the marketing, not the architecture.

Clap.

Clap.