n4jm4's comments

On: The FCC wants to criminalize AI robocall spam

[n4jm4]

See "Computer Fraud and Abuse Act."

On: Forging signed commits on GitHub

[n4jm4]

Relying on regexes instead of thoroughly tested parser AST's encourages vulnerabilities.

Are they really scraping logs for credentials instead of using an API?

On: The NSA Furby Documents

[n4jm4]

Analysis is fun, but any device with a microphone or camera represents a security risk for sensitive environments... Fropies.

On: Lichen: The Sed Build System

[n4jm4]

Can't sleep, must publish build systems for more fringe programming languages.

[tempodox → n4jm4]

Calling sed(1) a programming language is quite a stretch (although I guess you could say it's Turing-complete), as is calling a core Unix tool “fringe”.

Maybe we need a tongue-in-cheek emoji to mark submissions like this. Or would that ruin half the fun?

[jalk → n4jm4]

Brainfuck anyone?

On: Sourcehut will blacklist the Go module mirror

[n4jm4]

Vendoring in go mod should be mandatory.

On: We're wasting money by only supporting gzip for ra...

[n4jm4]

Rewrite our DNA from quadature to base64. Much more efficient.

On: Tell HN: IPv6-only still pretty much unusable

[n4jm4]

Sounds like IPv6 isn't broken, GitHub and Ubuntu and BitBucket are broken.

On: In Solidarity with Library Genesis and Sci-Hub (20...

[n4jm4]

Publicly funded research should generally be available at no cost and bother to the public.

On: Extism: Make all software programmable with WebAss...

[n4jm4]

Why not continue using long-standing C FFI?

This is not so clear.

On: The pool of talented C++ developers is running dry

[n4jm4]

So hire Rust and FPGA devs.