With a IDA Pro decompiler license & MCP server, paired with Codex/Claude Code... it would be a fun side quest.
HN user
johncoatesdev
You last-minute cancelled coffee with your friends to work on this? I'm not sure how I would feel if a friend did that to me.
Yes, but the advice shouldn't be "Never scan QR codes", it's more like: "be aware of dodgy QR codes by looking at the context in which it's placed".
And how exactly do you plan to forge the SSL certificates to deliver your filtered contents?
It's funny your warning about QR codes goes onto warn about PDF exploits. Yet you clicked the link to this article, by your own definition opening you up to "a whole different world of possible exploitations via whatever file is being returned". It's the nature of the internet to follow links, but our updated browsers keep us safe from exploits.
When was the last time you saw an un-targeted mass 0-day exploit campaign? There haven't been any for modern browsers. If we're talking about 0-days, you likely known there have been zero-click iMessage/WhatsApp vulnerabilities in the past. There's no protecting against those, but you're not here warning users to disable iMessage and WhatsApp. What's more realistic is making sure users keep their software updated, and trust that QR codes and links aren't going to waste a 0-day worth a million dollars on you.
Updating software is good advice. Do you realize how many CVEs are reported on a daily basis? Once you've got a password manager you're largely protected against phishing, so the biggest target becomes your computer, and the most likely way to compromise that would be through outdated software with public vulnerabilities.
What do you expect your browser security levels to the max to do? Browsers are designed to be secure from default settings.
It's completely the opposite of "use one password for everything". When you do that any single compromise of a website you have an account on means all your accounts are likely compromised. With a password manager you have a long random password for every single website, meaning a compromise is siloed to just that site.
Even if your password vault is stored on the cloud you're likely using a very secure passphrase for it that has 0 reuse anywhere else, so even if your password vault is stolen it's impossible to brute force.
For a hacker to comprise your password vault it would likely involve hacking your computer, which if you're keeping your software updated is a very difficult task these days without the target user's active help.
what do you use as a client? Most open source clients don't seem to support the new endpoint that o3-pro requires.
From the reports it looks like they have to have been private and deleted
Yeah I agree. Tried https://news.ycombinator.com/item?id=39771541 but there's nothing related to this repo. Does GitHub send an email out when you make something public? I don't have any emails related to this repo.
I can't find any reason why I would have made it public. I made the repo in 2014 for internal use and don't like to share projects like that. I'm pretty careful when releasing any code publicly. It's some code that other private projects depend on. I searched for any references in public code and there are none, so there should have been no reason to make it public.
Interestingly my public code with thousands of stars isn't in "The Stack".
How do I check this? I found a repo I'm pretty sure was always private on there that I deleted a while back. https://github.com/johncoates/JCBootstrap
There's no archived version on archive.org at least.
You can get a callback when a frame is going to get drawn and only render then. That way you don't render needless frames.
Your logic loop that controls the game state can be set to an optimal tick rate so it's not just maxing out a core.
The audio buffers I've worked with have also supported callbacks so they can remain optimally filled.
Looks like this is a link to an issue of a newsletter and it's divided into sections.
Has anyone won a game of this?
Check for a gas leak
Sorry about that. I figured most would get it was a lighthearted reference, and not groundbreaking quantum research that would change the world as we know it. Even so I made the first words after the title be “I might have the definition of “quantum entanglement” wrong.“, to try and make that clear. Oh well, I’ll get it right next time. Thanks for the feedback.