nulltrace

4 ms·

1.
by nulltrace 6d ago
Soon my phone can cryptographically prove the beauty filter lied at capture time.
2.
by nulltrace 9d ago
Rebuilding strip from clean source doesn't clear it. The copy in the bootstrap seed modifies its replacement, and the replacement carries on from there. The provenance can still look normal.
3.
by nulltrace 17d ago
Rebase an old branch and it suddenly looks recent again. The rewritten tip gets a fresh committer date.
4.
by nulltrace 24d ago
A replacement app could just send the vendor-signed image and leave the signature check to the device. Plenty useful once the official app disappears.
5.
by nulltrace 27d ago
Anything in our stack is modern C++ if we can help it. If Mojo can replace those kernels without the Python runtime sitting underneath, even better.
6.
by nulltrace 2mo ago
I think your concrete treehouse counts too though. Add a shower and suddenly you need plumbing, drainage, the structure has to hold more weight. The overcomplicated part drags the overengineered part along with it. They pretty much collapse
7.
by nulltrace 2mo ago
That loop reads like a bug to anyone who hasn't memorized the wrapping rules. while (i-- > 0) on a signed index does the same thing.
8.
by nulltrace 4mo ago
The SKIP LOCKED pattern is fine until the worker count climbs. Then vacuum can't keep up. Dead tuples pile up, visibility map turns to swiss cheese. Queue table is tiny on disk but the planner thinks it's huge and stops using the
9.
by nulltrace 4mo ago
Compiler mode won't catch the `extern "C"` thing though. Both sides compile happily, link blows up on mangled names. What I do is just keep a throwaway .cpp in tests that #includes the header and calls a few of the public fun
10.
by nulltrace 4mo ago
Being a generalist isn't easy.
11.
by nulltrace 4mo ago
Most IAM policies start as "whatever made the deploy pass." Need rds:CreateDBInstance? Fine, rds:* it is. Ship it. Months later that same role can wipe the cluster and nobody remembers why it ever had that permission. Separate acc
12.
by nulltrace 5mo ago
There's a GitHub issue for the freeze thing. Their security scanner passes the full dep list as CLI arguments, large monorepo on Linux and you blow past ARG_MAX. Spawn silently hangs, no error, --ignore-scripts doesn't help becaus
13.
by nulltrace 5mo ago
designed, but never tested
14.
by nulltrace 5mo ago
We went through the same switch. Half our alerts had been firing for a while and nobody ever acted on them.
15.
by nulltrace 5mo ago
Firefox at least randomizes extension IDs per install. Chrome hands all of that to extension devs, basically a "your problem now".
16.
by nulltrace 5mo ago
Stale training data is part of it. But even a current model can't tell what setup.py is going to run on your box. Nothing actually inspects the package before it executes. You'd want something that pulls the metadata and checks wh
17.
by nulltrace 5mo ago
Common mistake is trusting the repo instead of the workflow. Then any workflow inherits the same cloud access.
18.
by nulltrace 5mo ago
Browsers already treat the same SVG differently depending on how you embed it. <img> strips scripts and external resource loads. <object> and inline don't. People test with img tags, looks fine, then someone switches the em
19.
by nulltrace 5mo ago
We added a preflight curl against registry.npmjs.org before the install step in CI. Not surprising they went down together.
20.
by nulltrace 5mo ago
Downtime is one thing. Silently reverting commits on your default branch is something else entirely.
21.
by nulltrace 5mo ago
Preview deploys are even worse. Every PR spins one up with the same env vars and nobody ever cleans them up. You rotate the key, redeploy prod, and there are still like 200 zombie previews sitting there with the old value.
22.
by nulltrace 5mo ago
Catching accidental drift is still worth a lot. It's basically the same idea as performance regression tests in CI, nobody writes those because they expect sabotage. It's for the boring stuff, like "oops, we bumped a dep and
23.
by nulltrace 5mo ago
Right, metaclass is a ways off. But even without it, just the core reflection is going to save a ton of boilerplate. Half the template tricks I've written for message parsing were basically hand-rolling what `^T` will just give you.
24.
by nulltrace 5mo ago
Rebalancing is what really kills you. A CAS loop on a flat list is pretty straightforward, you get it working and move on. But rotations? You've got threads mid-insert on nodes you're about to move around. It gets ugly fast. Skipl
25.
by nulltrace 5mo ago
Yeah pricing seems okay with batching. The 128MB memory cap per Durable Object is what I'd watch. A repo with a few thousand files and some history could hit that faster than you'd expect, especially during delta resolution on pus
26.
by nulltrace 5mo ago
Fair, but from the user side it still hurts. Setting up an Ed25519 signing context used to be maybe ten lines. Now you're constructing OSSL_PARAM arrays, looking up providers by string name, and hoping you got the key type right becaus
27.
by nulltrace 5mo ago
Lockfiles help more than people realize. If you're pinned and not auto-updating deps, a package getting sold and backdoored won't hit you until you actually update. The scarier case is Dependabot opening a "patch bump" P
28.
by nulltrace 5mo ago
It also doesn't bother checking what's already in your project. Grep around a bit and you'll find three `formatTimestamp` functions all doing almost the same thing.
29.
by nulltrace 5mo ago
This clicks for message parsing too. Had field lookups in a std::map, fine until throughput climbed. Flat sorted array fixed it. Turns out cache prefetch actually kicks in when you give it sequential scans.
30.
by nulltrace 5mo ago
Could be the bundler re-resolving the whole dependency graph on every build, even when nothing changed.

More ›