Tech Radar

Cookie banners are a complete failure. They've become this universal tax on the internet that manages to annoy every single user while providing a false sense of legal security for the companies that implement them. We've all just conditioned ourselves to click "Accept All" without looking, which means the banners aren't actually protecting anyone's privacy. They're just digital noise. Most people assume these pop-ups are a strict requirement of EU privacy law. They aren't. The law is actually pretty clear: online tracking is prohibited by default. The banners are just a clumsy workaround that companies use to try and trick us into opting in. The EU Commission finally proposed a way out of this mess. Instead of playing whack-a-mole with every single website you visit, you'd set your privacy preferences in your browser once. That's it. No more banners, no more fake choices. Whether this actually kills the cookie pop-up for good depends ...

Most "secure" phones are just running software locks that feel sturdy until you actually try to break them. GrapheneOS takes a different approach by relying on hardware-level timers. It makes brute-force attacks mathematically impractical because the clock isn't managed by the OS, which can be tricked, but by the silicon itself. Google has actually been putting secure elements with internal timers into Pixels since the Pixel 2 launched back in 2017. The integration has gotten a lot better since then, but the core idea of rate limiting and insider attack resistance was already there. GrapheneOS just builds on top of those hardware primitives and the standard Android 14 security features to create a much harder target for data extraction. The duress PIN is a small part of this larger architecture. It's a simple trigger, but it does one thing effectively: it wipes the device the moment it's entered into any prompt for the current profile. It's a blunt in...

Ruff just jumped from 59 to 413 default rules. That is a massive leap in a single update, and it fundamentally changes how much noise you can scrub from your codebase in a few milliseconds. I've seen a lot of linting tools try to be "comprehensive," but usually that just means they annoy you with false positives until you eventually turn them off. The real win here isn't actually the volume of rules. It's the new range suppression. You can finally wrap a specific block of code with ruff: disable and ruff: enable without having to pepper your entire file with inline comments. It's a small ergonomic change, but it's the kind of thing that makes a tool actually usable in a large production environment. Most of these new rules are helpful, but adding 350+ checks to your CI pipeline at once is a great way to break every single build in your company. The question is whether you should just flip the switch or spend your weekend manually auditing a thou...

Everyone is obsessing over sustainable aviation fuels. It makes sense. Swapping the liquid in the tank is a lot easier than redesigning a plane. But JetZero thinks we're looking at the wrong variable. They're betting that the actual shape of the aircraft is the biggest lever we have for efficiency, which is a bold move in an industry that hasn't fundamentally changed its silhouette in decades. It's a high stakes gamble. Changing the airframe means fighting through years of certification and rethinking how we build planes from the ground up. Still, the money is starting to move. They just closed a $175 million Series B, and Japan Airlines is now publicly backing the Z4 program. Money and airline partnerships are one thing, but the physics are another. The real question is whether a blended wing body can actually scale without becoming a maintenance nightmare. The Efficiency Gap Tube-and-wing aircraft have hit a physics ceiling. For decades, we've just twe...

Most interview review sites operate on a clumsy trade. You get transparency, but only if you're willing to gamble your privacy or hope the site's "anonymous" tag actually holds up. It's a leaky system. We decided to build something that doesn't rely on trust or a promise to keep secrets. Our platform simply doesn't ask for names. We don't collect them, and we don't publish them. By removing the identity layer entirely, we've cut out the risk of accidental doxing or revenge posts. It's a boringly simple solution to a problem that most sites try to solve with complex terms of service that nobody reads. The real value isn't just in the reviews, though. We've added a public record for ghosting. It's a way to track companies that go silent after the final round, turning a private frustration into a visible data point. Is a public shame list enough to make recruiters actually hit "send" on an email? We're about...

Google might be about to kill the loopback address for ADB commands. If they do, it isn't just a minor tweak to the developer options. It's a move that could break a huge chunk of the power-user ecosystem, specifically everything relying on Shizuku to get root-like permissions without actually rooting the device. I've seen Google tighten the screws on sideloading and system access before, but this feels different. It targets the very tools that let developers and enthusiasts actually manage their own hardware. They'll probably claim it's for security, but it smells like another step toward a more locked-down environment where you only do what the Play Store allows. The timing is suspicious. It aligns too well with their recent shifts in how apps are installed and managed. I'm not convinced this is an accident, but I'm also not sure if they realize how many people will actually be pissed off when their favorite privacy tools suddenly stop working. T...