Notices by niconiconi (niconiconi@mk.absturztau.be), page 7

Q: What do you call a California city with an Internet outage after a fiber cut?

A: LOS angeles.

MFW my childhood friend's Intel CPU leak turned out to be 100% real.

The industry's attitude on memory safety is truly strange.

In the early 2000s, enforcing global hardening policies like stack canary, strict W^X, or ASLR was an extreme niche and highly unpopular work, because people think it's invasive and breaks compatibility. It remains so today, "Control Flow Integrity with Forward and Backward Edges", anyone? Then in the 2020s, rewriting entire C codebases in Rust suddenly becomes popular and mainstream in record time - although doing this breaks compatibility in its fullest sense - in contrast to the 15 years of delay on normalizing compiler hardening.

I guess it's because the latter group doesn't need to care much about compatibility at all, unlike the first group who must work with people who do care. So breaking compatibility is paradoxically more popular than preserving partial compatibility.

"Simple Gender Change"
- Engineering Diagrams That Look Like Shitposts

100 meters of optical fiber arrived. If I'm going to wire a room to Ethernet, it's better to add some dark fiber so I don't need to rewire it again for the rest of my life.

Q: Which kind of CPUs is best-suited for running Rust code?

A: Realtek SoC.

5GBASE-T Ethernet adapters are impossible to buy because the search results are full of LTE cellular modems.

Murphy's Duality Law - In engineering, when a system can show both the property "A" and its negation "not A" depending on the specific context, it's always the opposite of what your application needs. Example: Computers are always too deterministic when you want to generate secure random numbers, but they're also always too random for reproducible builds or real-time systems.

Intel CPUs are named after lakes because they're the recommended cooling solution.

@puniko meow

@puniko :blobcatcomfslep:

@lanodan@queer.hacktivis.me I misread the manual. In NetBSD it's actually named LOCAL_PEEREID ("You're in a maze of incompatible Unix derivatives, all alike.")

@lanodan@queer.hacktivis.me even NetBSD has this extension, so it's pretty safe to use. It's only missing in macOS but only under a different name LOCAL_PEERCRED.

#TIL Check SO_PEERCRED of a Unix domain socket to find out the client's identity. No need to do hacky challenge-response via the filesystem.

1950s American car makers
2020s Web developers
🤝 Chromium everywhere

"[Without copyright] GPL could not exist."It's like saying without a global thermonuclear war, we can't spend our Nuka-Cola bottle caps as currency.

#TIL The 1 USD bill has never been updated for almost a century because it's a conspiracy by the Big Vending Machine. https://en.wikipedia.org/wiki/United_States_one-dollar_bill#Redesign_or_replacement_of_the_$1_bill

I was isolating my problem and preparing for a GPU page fault bug report that occurred 9 out of 10 times. In this process, the problem itself disappeared, even using the original setup (according to my best memory) no longer reproduces the bug. How nice! :woozy_baa:

Q: Why does a C programmer look into a crystal ball?

A: pondering the OOB.

Programming? More like enbugging.