Sam: They shut it all down, said 'it's over'... and then one lawyer's opinion was enough to bring it all back.
Kai: I'm Kai.
Sam: And I'm Sam.
Kai: And this is Open Source on the Record. It's Monday, September 7th, 2026.
Sam: [beat] We've got stories that run the gamut from legally shaky to fortress-level secure.
Kai: First up: after a dramatic shutdown, a beloved open-source alternative to X is back from the dead.
Sam: Then, we'll look at the mobile security project GrapheneOS, which just made its ultra-secure platform even safer with a feature every phone should have.
Kai: And finally, a developer does the seemingly impossible: squeezing a Python interpreter into just one kilobyte.
Kai: Alright, let's get into that resurrection. Nitter, the privacy-respecting frontend for X, is back online!
Sam: Just days after developer Zedrus archived the project with the message 'It's over,' a new commit appeared with a three-word explanation: 'Resume after legal advice.'
Kai: And the community went wild. The commit thread blew up—over 600 points. People are thrilled, calling it a huge win for the open internet.
Sam: Hold on. Is it a win, or is it one developer taking a massive, undefined risk? 'Legal advice' isn't a magic shield. It could mean anything from 'you have a strong case' to 'you have a 5% chance, but here's how you'd argue it.'
Kai: But the advice was clearly good enough to flip the switch back on. Maybe they found that scraping public, unauthenticated data for a non-commercial frontend is protected under fair use.
Sam: Maybe. Or maybe the advice was that X Corp's legal threats are just that—threats. And they're banking on the company not actually suing a single open-source dev. That's a high-stakes gamble.
Kai: So what does this mean for people who just want to read posts without logging in?
Sam: It means Nitter and its sibling project, XCancel, are working again... for now. But the ground beneath them feels incredibly shaky. If you rely on it, enjoy it while it lasts. The next chapter could be a court filing.
Sam: So, moving from that shaky legal ground to something solid as a rock: GrapheneOS just announced a major overhaul of its default apps and a brand new security feature.
Kai: Yeah, this is fantastic. GrapheneOS already replaces Google's apps for privacy, but now they're hardening their own replacements. They forked Android's document viewer to make a secure PDF reader, plus updated their camera, gallery, and more.
Sam: The app suite is a nice touch, for sure. But the real headline here is the new Secure Clipboard.
Kai: Right, what's the threat here? I mean, it's my clipboard on my phone.
Sam: On standard Android, any app can ask for permission to read the clipboard... in the background. So if you copy a password, a bank account number, or a two-factor auth code...
Kai: Whoa—so a malicious app could just be sitting there, silently scraping everything I copy.
Sam: Exactly. GrapheneOS now lets you set an automatic clipboard timeout—from a few seconds up to two minutes. After that, the clipboard is wiped clean. Nothing there for a snooping app to steal.
Kai: That seems so obvious. Why isn't this a default feature on every single phone?
Sam: That's the multi-billion dollar question. For now, if you want that peace of mind, GrapheneOS is where you get it. For everyone else, it's a stark reminder to be very careful what you copy and paste.
Kai: And finally, a story from the 'because I can' school of engineering, which is my favorite school. A developer named Austin Henley managed to create a Python interpreter in just 1024 bytes.
Sam: You're kidding. A full programming language interpreter in the size of a couple of tweets?
Kai: One kilobyte! It's an x86-64 assembly program for Linux, and it's a work of art. It can handle integer math, variables, print statements, and even if/else branches.
Sam: [laughs] Okay, that's genuinely impressive. I assume it's not PEP 8 compliant.
Kai: It's a very, very limited subset of Python, of course. But the blog post where he breaks down how he did it is a masterclass in system calls, parsing, and extreme optimization.
Sam: So it's a pure technical flex. A brilliant one, but a flex. What's the takeaway for the average developer here, besides awe?
Kai: It just reminds you what's happening under all the layers of abstraction we use every day. We're so used to our multi-megabyte runtimes, but at the core, it's just raw instructions.
Sam: Fair enough. It's an inspiring piece of work. Just... don't try to run your company's microservices on it. The entire program is smaller than a typical buffer overflow exploit.
Kai: Alright, let's run it back: Nitter is back from the dead, though possibly on borrowed time.
Sam: GrapheneOS is making our phones more secure by fixing things the manufacturers won't, like a leaky clipboard.
Kai: And a Python interpreter can, in fact, fit into 1024 bytes, blowing minds everywhere.
Kai: Before we go, a quick fun fact about that last story. That 1024 byte number... it's technically not a kilobyte.
Sam: [sighs] Oh no. Kai, don't.
Kai: [excited] It's a kibibyte! The 'ki' for kilo-binary. A true 'kilo' is a thousand. The computer world just adopted 1024 and we've been confusing people ever since!
Sam: [dry] I can hear the flame war starting already. Thank you for that.
Kai: And that's our show for Monday, September 7th. You can find links to everything we discussed today in the show notes.
Sam: We'll be back tomorrow with more open source news. And if you get this podcast running on the 1k Python interpreter... you win.
This show is made with AI: the hosts’ voices are synthetic and the scripts are AI-assisted. Every story links to its original source.