2,480 karma · joined January 19, 2014
But thank you for one more demonstration that even the HN crowd can’t reliably give or deny informed consent here.
Every NTP session leaks time desync information, which reveals—on modern hardware—relativistic travel, including long airplane trips.
Every software update leaks a fortune about what you run and when you connect.
I don’t think it’s reasonable to ask that people consent to these; I don’t think they can. I absolutely agree that photo metadata is different and at a way higher level of the stack.
This isn’t about punishment: it’s about how we organize ourselves if we want to create together. I write LARPs collaboratively, and I play tabletop RPGs, too—and those are more fun and more productive and creative in person.
Alternately, they did not ever test the ability of their code to accept arbitrary configurations. That totally could have been done, allowing fast config pushes. But it wasn’t. So as a reliability engineer, I’d point at that change: configs were originally expected to be tested, so the parser was only tested to be sure it showed issues on pre-release testing. Later, they started shipping configs faster than their release cycle, but didn’t check to requalify the parser for this new requirement.
Behind that, I’d look at the engineering and product culture that had that happen. Is there a list of what’s been tested for what purpose? Was the expectation that configs get tested like software written down someplace, and do the roles who scheduled that config release read that place? Who is organizationally set up to notice this, and why is it a director-level IC straight out of xkcd 2347?
But this way makes a better story.
Nonuniform physics—call it colliding universes or whatever, but the processes that gave rise to life on Earth may not be possible anywhere in this universe now. Including labs on Earth!
Until that sort of thing is fixed, it’s not helpful for manufacturing trustworthy devices.
It's the ARRL field day for a few more hours; check out http://websdr.ewi.utwente.nl:8901 near 14100 kHz, looking for 2.7 kHz wide voice transmissions (USB), or near 7200 kHz LSB.
The reason is SEO; this is Google’s fault.
Nearly the only law is that you don't impede the mail system, and that you pay a small tax to support the fleet that will hammer you into the ground if you impede the mail.