August 1, 2026
Duplicate drama, extra spicy
The First Idempotency Key
Techies went hunting for who first said “don’t do it twice” and the comments stole the show
TLDR: The article digs into the surprisingly murky history of the trick apps use to stop the same action from happening twice, and finds there may be no single clear inventor. In the comments, readers were far more fired up about today’s mess: companies still handle it inconsistently, while everyone else got distracted by Ringo the double-dinner dog and a side quest about the best free bread.
A charming little tech history quest about the first-ever “don’t charge me twice” trick somehow turned into a full-on comment-section variety show. The article starts with a programmer chasing a gloriously nerdy question: who first came up with the idea of attaching a unique label to a request so a computer won’t accidentally process it twice? Along the way, there’s a scene-stealing dog named Ringo gaming the family dinner system, an AI assistant getting publicly corrected, and a surprise detour into old internet documents from decades past. But the real fireworks were in the replies, where readers immediately turned this from trivia into debate club.
The strongest reaction? People are annoyed that companies still can’t agree on how this basic safety trick should work. One commenter pointed out that some services treat a repeat request as the same action no matter what happened the first time, while others only block duplicates if the first try succeeded. Translation for non-tech folks: sometimes a retry protects you, and sometimes it can create a whole new mess. That inconsistency had veterans basically screaming, “It’s been forty years, why is this still chaos?” Another commenter pushed back on the article’s framing entirely, arguing the person making the request shouldn’t always be the one generating the unique label.
And then, because the internet refuses to stay on topic, people also got deeply invested in the free bread rankings and in praising “Ringo, the crafty b@stard” as the article’s true mastermind. So yes: a post about duplicate computer requests became a food fight, a dog fan club, and a mini civil war over who should be in charge of stopping mistakes. Classic internet.
Key Points
- •The article investigates the historical origin of idempotency keys while introducing them as a new feature.
- •Idempotency keys are described as unique identifiers that let API systems detect and ignore duplicate messages.
- •The article states that exactly-once delivery is impossible in distributed systems, making extra mechanisms necessary for exactly-once processing.
- •Claude first attributed the origin of idempotency keys to Stripe around 2011, then withdrew that claim as unsupported.
- •The article identifies Stripe’s Idempotency-Key header, Amazon EC2’s ClientToken behavior, and Mark Nottingham’s 2005 "POST Once Exactly" draft as relevant points in the documented history.