I feel like this will have a short shelf life. OpenAI is going to notice traffic through that Codex endpoint that doesn't match its usage patterns and lock it down.
Readit Newsredgridtactical commented on Show HN: Free OpenAI API Access with ChatGPT Account github.com/EvanZhouDev/op... · Posted by u/EvanZhouDev
redgridtactical commented on Why Canadian engineers wear a ring alvinpane.com/essays/the-... · Posted by u/alvinpane
That's an awesome story and meaning behind that. Thanks for sharing!
redgridtactical commented on My GPS app makes zero HTTP requests redgridtactical.github.io... · Posted by u/redgridtactical
This is cool. Installed.
Thanks! If you get a chance to try it outside, the GPS lock is usually pretty fast. Would love to hear how it works for you — especially if anything feels off or missing. I don't have analytics so user feedback is the only way I know what to improve.
The 100 hours number feels about right for a solo project. What people underestimate is that the last 20% isn't just polish — it's the boring defensive stuff that makes an app not crash on someone else's phone.
I shipped a React Native app recently and probably 30% of the total dev time was wrapping every async call in try/catch with timeouts, handling permission denials gracefully, making sure corrupted AsyncStorage doesn't brick the app, and testing edge cases on old devices. None of that is the fun part. None of it shows up in a demo. But it's the difference between "works on my machine" and "works in production."
Vibecoding gets you to the demo. The gap is everything after that.
This is the natural consequence of building everything around "the agent needs access to everything to be useful." The more capabilities you hand an agent, the larger the attack surface when it encounters a malicious page.
The simplest mitigation is also the least popular one: don't give the agent credentials in the first place. Scope it to read-only where possible, and treat every page it visits as untrusted input. But that limits what agents can do, which is why nobody wants to hear it.
> The gap between consumer electronics and mil-spec capability keeps shrinking
My friend's brother works in munitions and had, in his spare time, designed and prototyped a missile that could be built for about 10k. He pretty much was ignored by the contractor he works for.
Shockingly, as of a couple weeks ago, they are all hot and bothered to talk.
That tracks. The defense primes have zero incentive to make things cheaper — their business model is cost-plus. A guy building something for 10k in his garage is an existential threat to programs billing 500k per unit. Of course they ignored him until the geopolitical situation made it impossible to keep ignoring.
Right, that's a clean way to frame the boundary. Appreciate it.
On ICS integration, I haven't gotten there yet. The system outputs structured incident records, but I don't have real operational experience on that side.
The limited-connectivity point is interesting. If the output is a compact structured record that doesn't need a live connection to be useful, that could change what integration looks like.
If you have a strong opinion on what people actually use there, I'd be interested.
From what I've seen, the teams that are actually on the fireline mostly use paper ICS 214s and radio. The structured digital stuff lives at the ICP/EOC level. So the gap is really between field collection and the management system — if you can get a compact record off a phone with no connectivity requirement, that bridges it without asking anyone to change their workflow.
I think the practical win is SALUTE-style reports that auto-populate grid and DTG, exportable as plain text. No one wants another app to learn at 0200 on a fire.
For different definitions of cheap though.
While the pure gyro/accelerometer stuff does suffer from major problems the improvements in SLAM using just cameras in the last 15 years are insane.
Visual SLAM on a rocket would be wild. The frame rates you'd need at those velocities are brutal though — feature tracking falls apart fast when your entire visual field is changing at hundreds of m/s. Drones are the sweet spot where camera-based nav really shines.
Cheap sensors look impressive in demos but drift and calibration wreck repeatability unless you babysit launches so nobody in defense is sweating this yet.
For a sub-minute flight the drift budget is actually pretty forgiving — a MEMS gyro drifts maybe 1-3 deg/sec, and if you're fusing with accelerometer data you really just need "which way is up" and "am I still pointed at the target." A $5 IMU can hold that for tens of seconds.
Where you're right is repeatability. Mil-spec works the same on launch 1 and launch 500 across temperature extremes. Consumer MEMS you'd need to characterize each unit individually — fine for a demo, impractical at any scale.