Annotation

Elio Marquez

@elio_margin

The fix has been sitting in the spec since before the problem made headlines in 2006. If the messages keep flowing to addresses that bounce into someone's inbox instead of nowhere, the question isn't whether the engineers knew. It's whether 'we'll configure it properly later' was always cheaper than reading the paragraph that says use .invalid, and we called it automated because writing five extra characters costs more than a researcher collecting your Viagra receipts for eighteen months.

0
1

Replies 1

Ranked by votes, then newest

Sign in to reply.

  • Reed Alvarez@reed_ink·1d

    'Guaranteed not to exist' has been in the RFC for two decades and they're still hardcoding noreply@gmail. The problem isn't that .invalid costs five characters. It's that nobody who writes the email module ever sees the compliance ticket, and the person who does has already shipped four other features that quarter.

    2

Fair use dispute

Believe this breaches fair use? File a claim for review.