Hacker News Daily Digest: The Stories Tech Can't Stop Talking About

California just officially closed the “Montana license plate loophole” for good. That means the trick of using a shell company in a no-sales-tax state to register your supercar and dodge California taxes is finally over. And while last week we were talking about AI forging cartoons, this week the AI story got a whole lot more... formal, but we'll get to that. First, let's talk about why this tax law change is a bigger deal than it sounds. For years, if you were wealthy enough, you could hire a firm in Montana to create a shell LLC for you. That LLC would "own" your Ferrari or your half-million-dollar R.V., and you'd drive it around Los Angeles with a Montana plate, having paid zero California sales tax.

The old law was flimsy — it only required that the company be fifty percent owned by out-of-state residents, a test that was trivial to pass. But the new bill, SB 1406, which passed on September thirtieth, completely rewrites the definition of a shell company. It doesn't matter who owns it anymore. The new rule is simple: if a California resident is a beneficial owner or officer of the company, they are now personally on the hook for all the unpaid taxes, plus interest and penalties. It's a surgical strike against a very specific, very expensive form of tax evasion. Now, for the rest of the week's biggest threads. The top story, generating a massive discussion, is that OpenAI just published a major update on its progress in mathematics.

They released a whole repository of AI-generated mathematical preprints and, crucially, formalized proofs written in a language called Lean. This means the proofs can be verified by a computer, which is a huge step for trusting an AI's output. They're even sharing the compute cost: about three hours of ChatGPT Pro usage per result. It's a surprisingly transparent move. And in a one-two punch, OpenAI also announced the public beta of a new "Decisions API" today, October seventh. This isn't just about generating text; it's designed to help developers build workflows where the AI makes structured choices. Think of it as moving from a creative partner to a logical one. The community is still digging in, but it points to a future where you ask an AI not just to write something, but to decide something.

Then there’s a story that has the gaming and emulation scene buzzing. A project called AnyPS5 just reported a massive milestone. They've now successfully mapped eighty-seven percent of the PlayStation 5's system libraries. Their goal is to run PS5 games natively on a PC, without the performance hit of traditional emulation. This isn't about playing pirated games; it's a monumental reverse-engineering challenge. Getting to eighty-seven percent means they are getting seriously close to making this a reality. It's one of those deeply technical, multi-year projects that you just have to admire. On the flip side of a massive undertaking, we have a story of a single developer's frustration.

The creator of Photopea, that incredibly popular browser-based photo editor, posted that he’s been fighting with GitHub for a month. He filed DMCA takedown notices for cracked, pirated copies of his software being hosted on the platform, and GitHub refused to take them down. Their reason? They couldn't confirm it violated a very specific part of the law. The developer's post is full of raw frustration, and he suspects his reports were never even seen by a human. It's a classic David-and-Goliath story for the platform age. And finally, a new open-source project caught a lot of eyes. It's an email client for Linux called Penguin Mail, written in Rust. It aims to be a modern, all-in-one inbox, pulling in Gmail, Microsoft accounts, and standard IMAP, plus calendar and contact integration.

It also has built-in OpenPGP encryption and an optional AI assistant that can run locally on your machine. In an era where everyone is trying to escape the browser, a slick, native email client is always going to get attention, especially one built with privacy in mind. Okay, let's go deeper on two of these, because they represent two really different, but equally important, struggles happening in tech right now. The first is about creating new knowledge, and the second is about protecting what you've already created. Let's start with OpenAI and the math proofs. This is so much more than just "AI is good at math now." The key is in the details. They aren't just spitting out answers.

They're providing formalized proofs in a language called Lean. So what does that actually mean? Think of a normal mathematical proof written in English. It relies on a shared understanding between mathematicians. It has logical steps, sure, but there's a bit of... interpretive dance. A human has to read it and agree that it makes sense. A formalized proof in Lean is different. It's written in a programming language where every single logical step is so precise, so unambiguous, that a computer program can check it for correctness from the axioms up. There's no room for error. If the Lean proof "compiles," the math is correct. Period. This is where we've seen this pattern before, but with a twist.

The classic example is the Four Color Theorem, which states that any map can be colored with just four colors without any adjacent regions sharing a color. It was first proven in 1976 with the help of a computer, which checked thousands of different cases. It was controversial. Mathematicians complained they couldn't verify it by hand; it was too complex. They had to trust the computer's brute-force checking. But what OpenAI is doing is different. This isn't just a computer checking a human's work. This is an AI generating novel mathematical ideas and then providing the machine-checkable proof itself. It’s like the computer isn't just the calculator; it's the mathematician. And by releasing the proofs in Lean, they're handing the community the ultimate tool for verification.

You don't have to trust OpenAI. You don't have to trust the black box of the neural network. You just have to trust the Lean compiler, which is open source and heavily scrutinized. This feels like a direct response to the credibility crisis in AI. How do you trust the output? Well, in math, you provide a proof. And by also publishing the compute cost — "three hours of ChatGPT Pro" — they're demystifying the process. It's not some unobtainable magic from a trillion-dollar datacenter. It's a quantifiable amount of work. They're saying, "Here is our result, here is the verifiable proof, and here is what it cost us to find it." It's an incredible flex. This also changes the job of a human mathematician.

It doesn't make them obsolete. Instead, it turns them into explorers and guides. The AI can generate hundreds of potential paths or interesting conjectures, and the human's job is to provide the intuition, to ask the right questions, to point the AI in a fruitful direction. It's a collaboration. And the fact that OpenAI is working with the Institute for Advanced Study—where Einstein used to work—shows they understand this. They're not just dropping code; they're trying to build a bridge to the existing world of pure mathematics. This is how you get a deeply conservative field like math to actually engage with AI. You don't just give them answers. You give them tools and proofs.

Now, let's switch gears completely. From the frontier of knowledge to the grim reality of running a business online. Let's talk about Photopea and GitHub. The developer, who goes by IvanK_net, built something amazing. Photopea is a free, powerful photo editor that runs entirely in your browser. It's a lifeline for students, schools, and people who can't afford a Photoshop subscription. He makes money from ads and a premium version. But because it's written in JavaScript, people can just copy the code, re-host it, and sometimes inject their own ads or malware. So Ivan does what you're supposed to do. He files a DMCA takedown notice with GitHub, where these cracked copies are being hosted.

A month later, he gets a rejection. And the reason GitHub gives is incredibly specific and, frankly, infuriating. They said they couldn't confirm a violation of 17 U.S. Code § 1201. So what does that even mean? Section 1201 of the copyright act isn't about copying the work itself. It's about circumventing "technical protection measures." Think cracking the copy protection on a DVD or a video game. GitHub's response implies that because Photopea's code is just plain JavaScript, and there's no complex encryption to "crack," simply copying it doesn't violate that specific part of the law. This is the kind of hyper-literal, legalistic response that makes you want to tear your hair out.

It completely misses the point. The code is still copyrighted. Hosting an unauthorized copy is still infringement. But GitHub seems to be hiding behind this narrow, almost procedural excuse. As the developer said, "I really doubt that a real person ever looked at my report." And he's probably right. Here's the pattern: this is the curse of scale. We've seen this with YouTube's Content ID, with Amazon's counterfeit problem, with social media's content moderation. When you operate a platform with billions of pieces of user-generated content, you can't use humans to review everything. You HAVE to rely on automation. And that automation is optimized to protect the platform from legal liability, not to deliver justice for individual creators.

GitHub's automated system likely saw the report, ran a check against a narrow set of criteria for the most clear-cut, slam-dunk violations, and because this case involved JavaScript code and not a cracked executable, the algorithm just said "nope" and sent the rejection template. The system is designed to say no. A false negative—leaving infringing content up—is safer for the platform than a false positive—taking down legitimate content and getting sued. So the creator is left in an impossible position. He's up against a system that isn't just broken, but is working exactly as its owner designed it to—to minimize its own risk, even at the expense of the users it claims to serve.

The comments on Hacker News were full of sympathy, but also a sense of resignation. Some people suggested porting the app to WebAssembly to make it harder to copy. Others just said, yeah, piracy is a fact of life. But that misses the core issue. This isn't just about piracy. It's about a breakdown of the social contract of platforms. The promise of a platform like GitHub is that it provides tools and infrastructure so you can focus on building. But when that same platform becomes a safe haven for people stealing your work, and its own enforcement mechanism is a black box that spits out nonsensical rejections, the promise is broken. It shows that for all the talk of "community," when push comes to shove, the platform's automated legal defense system will always win against a single human.

So what does it all add up to? On one hand, you have AI pushing the absolute boundaries of what we can know, creating new systems of logic that are verifiable and transparent. And on the other, you have our existing human systems—our legal and platform systems—failing in the most basic ways, becoming opaque and unaccountable. It's a perfect snapshot of the weird moment we're in. We're building these god-like tools for discovering truth, while the everyday systems we rely on for fairness feel like they're falling apart. This week sets up a fascinating tension. We're seeing the birth of AI as a genuine partner in formal science, a tool that doesn't just guess but proves. The next six months aren't going to be about whether AI can do math, but about how human institutions adapt to it.

Will universities create new courses? Will journals accept AI-co-authored papers? That's the real test. At the same time, the struggle of individual creators against massive, automated platforms is only getting more acute. The real story to watch isn't whether GitHub changes its policy for one developer, but whether the growing frustration forces a broader reckoning with platform responsibility. We are simultaneously building systems of breathtaking power and failing to maintain the simple ones we already have. And the friction between those two is where everything important is going to happen next.