Google and HTTP (2018)(this.how)
60 points by mpweiher | 103 comments
60 points by mpweiher | 103 comments
64 points by intunderflow | 48 comments
Blog post analyzing how OpenAI agents scanned UNCTAD's statistics API about 16,500 times in 2026 using proxies, obfuscation, and Google's XSS game.
73 points by ziggy42 | 27 comments
521 points by RGBCube | 318 comments
Blog post explaining how Mullvad VPN deterministically assigns exit IPs based on a user's WireGuard key, making them usable as a fingerprinting vector.
444 points by guntars | 138 comments
Blog post describing building an HTTPS web server in Rust using io_uring and kernel TLS to avoid system calls on the request path.
363 points by edent | 461 comments
Ryan Barrett's blog post arguing the Twitter API is effectively unmaintained, citing the decline of Twitter employee posts on the developer forum.
324 points by BerislavLopac | 493 comments
Blog post by Florian Krämer arguing that most APIs called RESTful don't follow Roy Fielding's original REST architectural style as described in his dissertation.
566 points by zkldi | 437 comments
Blog post arguing a newly disclosed PHP vulnerability is hard to exploit and that thousands of LLM-generated GitHub PoC exploits don't work against vanilla PHP.
425 points by nnx | 147 comments
Cloudflare Blog post by James M Snell arguing that JavaScript's Web Streams API is flawed and proposing a better streams API design.
502 points by mpweiher | 413 comments
A personal blog post arguing that developers should manually retype code generated by LLM coding assistants to keep understanding it and avoid cognitive debt.