korrents
Mark Nottingham

What Mark Nottingham thinks about design

@mark-nottingham · 10 positions · On ppll ↗

Web infrastructure engineer and standards editor; chaired the IETF HTTP working group and co-authored core HTTP and Atom specifications.

Mark Nottingham did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

4 dated positions, 2026, in their own words. Our reading of what Mark Nottingham has said — not written or endorsed by them.

4 positions so far — this page is not yet offered to search engines.

  1. Another pattern: an extension gets deployed correctly in proportion to how loudly it fails when you get it wrong.

    ↗Informing HTTP Extension Design with Datamnot.net 2nd of 3 in this piece

  2. 3 months earlier
  3. CMS software should not silently create and advertise feeds that publishers never see or maintain; feeds should be visible, testable, and consciously enabled.

    ↗Web Feeds in 2026: A Surveymnot.net 1st of 2 in this piece

  4. WHATWG should deprecate the feed link relation; the cowpath is well and truly paved.

    ↗Web Feeds in 2026: A Surveymnot.net 2nd of 2 in this piece

  5. 2 weeks earlier
  6. Despite those shortcomings, Web browsers are a good example of how user agency should be done.

    ↗What's Missing in the ‘Agentic’ Storymnot.net 1st of 3 in this piece