Skip to main content
Toggle menu
Cracking
Walnuts
Interviews
Interview Roadmap
Start here
Pick your level, get your full prep plan
Case Studies
Full systems, worked end to end
HLD Playbooks
A full problem, step by step
Design Drills
One decision at a time, drilled
LLD Problems
Object-oriented design rounds
DSA Templates
Patterns & templates in 5 languages
Cheat Sheets
Quick-ref for interviews
Behavioral
Fresher to Principal
Company Playbooks
MAANG and AI labs, by level
Staff+ Interviews
Staff/principal rounds
Forward Deployed Engineer
The FDE role and its decomposition round
AI
AI Engineering
LLM fundamentals, internals, inference, RAG
Math for AI
The math behind LLMs, with small numbers
Security
Security
AppSec to cloud to architecture, attacker-first
AI Security
LLM, RAG, agent, and MCP security
Engineering
API Design
REST, HTTP semantics, OpenAPI & versioning
Concurrency
Java, Python & Go
Performance Eng
Latency, percentiles, profiling & labs
Networking & Protocols
TCP, HTTP, TLS & more
Linux Internals
Kernel & system internals
Distributed Systems
Consensus & replication
Infrastructure
Production infra & ops
Key Technologies
Core tech deep dives
Database Internals
How every engine works inside
Cryptography
How HTTPS, TLS, passkeys, and PQC work
DevOps Internals
How Kubernetes, Terraform, and the stack work
Blockchain Engineering
Bitcoin, Ethereum, consensus, L2s and ZK
Leadership
Arch Decisions
ADRs & trade-offs
Platform Eng
Internal dev platforms
Incident Patterns
Postmortems & SRE
Metrics & FinOps
DORA, cost & KPIs
Compliance
Security & governance
Leadership
Tech lead & influence
Org Design
Team topologies & orgs
More
Posts
System design deep-dive topics
Visualizers & Calcs
Interactive system design tools
Whitepapers
Academic & industry papers
Books
Beyond-the-code reading picks
Search...
Ctrl+K
Go Premium
Log in
C
r
a
c
k
i
n
g
W
a
l
n
u
t
s
Home
Security
Security
(6 posts)
How Can an Invisible Watermark Live Inside AI-Generated Text?
AI
Security
Deep Dives
Aug 11, 2026 · 15 min
INSIDE THE HTTP TERMINATOR
138 documents in.
30,000 attacks out.
How the AI generated them, and why it was never allowed to say which ones worked.
WHAT THE MACHINE DID
138
documents
15,000
fragments
THE AI
reads each one
30,000
attack ideas
30,000
sites tested
~700
actually broke
WHO DECIDED WHAT
THE AI
invents the odd requests
allowed to be wrong
THE CODE
decides pass or fail
never argues, never guesses
THE PERSON
says which result matters
and why it matters
AI generates the possibilities. Code decides what survives. A person decides what any of it means.
HTTP Terminator · PortSwigger Research, August 2026
How AI Helped Find New HTTP Attacks, and What It Actually Did
AI
Security
Deep Dives
Aug 7, 2026 · 9 min
Proving You Are Over 18 Without Revealing Your Birth Date
Security
Deep Dives
Jul 30, 2026 · 22 min
Passwordless Authentication's Silent Choice: Trust vs Privacy
Security
Deep Dives
Aug 10, 2025 · 8 min
Premium
End-to-End Encryption in Chat Applications
Security
Deep Dives
Jun 19, 2025 · 13 min
Securing Access: The Power of RBAC, ABAC, and ReBAC
Security
Deep Dives
Apr 8, 2025 · 6 min