mark nottingham

Wednesday, 22 June 2022

What willwould a Chromium-only Web look like?

Most of the complexity and nuance of the Web is stuffed into browser engines. Even though they’re a huge burden to develop and maintain, the world is lucky enough to have three major ones, and they’re all Open Source.

this entry’s page

Wednesday, 8 June 2022

Yet More New HTTP Specs

The HTTP “core” documents were published on Monday, including a revision of HTTP semantics, caching, HTTP/1.1, HTTP/2, and the brand-new HTTP/3. However, that’s not all that the HTTP community has been up to.

this entry’s page

Monday, 6 June 2022

A New Definition of HTTP

Seven and a half years ago, I wrote that RFC2616 is dead, replaced by RFCs 7230-5.

this entry’s page

Sunday, 20 February 2022

Server-Sent Events, WebSockets, and HTTP

The orange site is currently discussing an article about Server-Sent Events, especially as compared with WebSockets (and the emerging WebTransport). Both the article and discussion are well-informed, but I think they miss out on one aspect that has fairly deep implications.

this entry’s page

Monday, 21 June 2021

How the Next Layer of the Internet is Going to be Standardised

A big change in how the Internet is defined - and who defines it - is underway.

this entry’s page

Thursday, 18 February 2021

No news is... a sign of a stagnating Internet

Today, Facebook shut off the news in Australia – all of it, and much more besides. For example, when I tried to post a link to this blog entry on Facebook, they responded:

this entry’s page

Friday, 28 August 2020

RFC8890: The Internet is for End Users

The Internet Architecture Board (IAB) has published RFC8890, The Internet is for End Users, arguing that the Internet Engineering Task Force (IETF) should ground its decisions in what’s good for people who use the Internet, and that it should take positive steps to achieve that.

this entry’s page

Monday, 29 June 2020

What limits legal access to cloud data in Australia?

The Telecommunications and Other Legislation Amendment (Assistance and Access) Act 20181 has proven controversial both before and after passage,2 with considerable debate about its industry assistance framework and its potential for systemically weakening encryption on the Internet - a framing emphasised by the explanatory memorandum which introduced the legislation as ‘measures to better deal with the challenges posed by ubiquitous encryption.’3 Telecommunications and Other Legislation Amendment (Assistance and Access) Act 2018 (Cth). ↩ See, eg, Stilgherrian, ‘What’s actually in Australia’s encryption laws? Everything you need to know’ ZDNet (online, 10 December 2018) ↩ Explanatory Memorandum, Telecommunications and Other Legislation Amendment (Assistance and Access) Act 2018 (Cth), 2 [1]. ↩

this entry’s page

Thursday, 5 December 2019

On RFC8674, the safe preference for HTTP

It’s become common for Web sites – particularly those that host third-party or user-generated content – to make a “safe” mode available, where content that might be objectionable is hidden. For example, a parent who wants to steer their child away from the rougher corners of the Internet might go to their search engine and put it in “safe” mode.

this entry’s page

Sunday, 13 October 2019

How Multiplexing Changes Your HTTP APIs

When I first learned about SPDY, I was excited about it for a number of reasons, but near the top of the list was its potential impact on APIs that use HTTP.

this entry’s page