/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 nullprogram.com
Atom vs. RSS
| | www.mnot.net
Yet More New HTTP Specs
35.5 parsecs away

Travel
| | 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.
| | netninja.com
Reviving the Unfiction Forums - Netninja.com
45.4 parsecs away

Travel
| | I set out to take a static snapshot of the Unfiction forums. Its now-15-year-old server software crashed and fell offline 8 years ago. This is how I did it.
| | mathieu.fenniak.net
Is "404 Not Found" really a client error? | Mathieu Fenniak
42.0 parsecs away

Travel
| | A time-traveler is passing by 2013 and she opens a browser bookmark to http://mars.gov/blog/**2056**/11/21/news.html. What HTTP status code does she get back from her response? Well, it's not going to be 200 OK, because it wasn't OK with the server. The server couldn't find the article that the client requested, because it won't be published for another 43 years. "Couldn't find the article" sounds like a 404 Not Found status code. OK, very reasonable choice. But, "The server couldn't find the article" raises a bit of a doubt. A 404 is part of the 4xx-series status codes, which are all for client errors. Was this a client error, if it was the server's fault for not finding the article? Shouldn't she be getting 5xx Not Found?
| | blog.lacnic.net
LACNIC Blog | From IPv5 to IPv6: A Leap That Changed the Internet
61.4 parsecs away

Travel
| By César Diáz, Head of Telecommunications Affairs at LACNIC Back in the month of July, I had the privilege of participating in IETF 123 in Madrid. Internet Engineering Task Force meetings are where many of the protocols that underpin the Internet we use daily have been developed throughout history. As for any engineer, being in [...]