Link tags: dns

Washed Up - Infrequently Noted

The term “web3” is a transparent attempt to associate technologies diametrically opposed to the web with its success; an effort to launder the reputation of systems that have most effectively served as vehicles for money laundering, fraud, and the acceleration of ransomware using the good name of a system that I help maintain.

Perhaps this play to appropriate the value of the web is what it smells like: a desperate move by bag-holders to lure in a new tranche of suckers, allowing them to clear speculative positions. Or perhaps it’s honest confusion. Technically speaking, whatever it is, it isn’t the web or any iteration of it.

Robin Rendle ･ Inheritance

My work shouldn’t be presented in the Smithsonian behind glass or anything, I’m just pointing at this enormous flaw in the architecture of the web itself: you’re renting servers and renting URLs. Nothing is permanent because on the web we don’t really own any space, we’re just borrowing land temporarily.

The History of the URL

This is a wonderful deep dive into all the parts of a URL:

scheme:[//[user:password@]host[:port]][/]path[?query][#fragment]

There’s a lot of great DNS stuff about the host part:

Root DNS servers operate in safes, inside locked cages. A clock sits on the safe to ensure the camera feed hasn’t been looped. Particularily given how slow DNSSEC implementation has been, an attack on one of those servers could allow an attacker to redirect all of the Internet traffic for a portion of Internet users. This, of course, makes for the most fantastic heist movie to have never been made.

The Web Developer’s Guide to DNS | RJ Zaworski

At Codebar the other night, I was doing an intro chat with some beginners. At one point I touched on DNS. This explanation is great for detailing what’s going on under the hood.

When 7 KB Equals 7 MB - Cloud Four

I remember Jason telling me about this weird service worker caching behaviour a little while back. This piece is a great bit of sleuthing in tracking down the root causes of this strange issue, followed up with a sensible solution.

A cartoon intro to DNS over HTTPS – Mozilla Hacks – the Web developer blog

This is a great illustrated explanation of how DNS resolution works.

Answers for young people - Tim Berners-Lee

Many, many years ago, Tim Berners-Lee wrote this page of answers to (genuinely) frequently asked questions he got from school kids working on reports. I absolutely love the clear straightforward language he uses to describe concepts like hypertext, packet switching, and HTTP.

Chrome to force .dev domains to HTTPS via preloaded HSTS

Well, I guess it’s time to change all my locally-hosted sites from .dev domains to .test. Thanks, Google.

The story of stolen Slovak national Top Level Domain .SK

I’ve heard of people having their domain names hijacked before, but this is the first time I’ve heard of an entire top level domain being nicked.

The History of the URL: Domain, Protocol, and Port - Eager Blog

From the ARPANET to the internet, this is a great history of the Domain Name System:

Root DNS servers operate in safes, inside locked cages. A clock sits on the safe to ensure the camera feed hasn’t been looped. Particularly given how slow DNSSEC implementation has been, an attack on one of those servers could allow an attacker to redirect all of the Internet traffic for a portion of Internet users. This, of course, makes for the most fantastic heist movie to have never been made.

How the Web Works: A Primer for Newcomers to Web Development (or anyone, really) by Preethi Kasireddy

This is a great reminder of the fundamental nuts’n’bolts of the internet and the World Wide Web: clients, servers, URLs, DNS, HTTP, TCP/IP, packet switching, and all the other building blocks we sometimes take for granted.

This is part one of a four-part series:

1. A Primer for Newcomers to Web Development (or anyone, really)
2. Client-Server Model & the Structure of a Web Application
3. HTTP & REST
4. Stay tuned…

Building the Great Libraries of the Internet with a DNS time machine by Ben Ward

Ben proposes an alternative to archive.org: changing the fundamental nature of DNS.

Regarding the boo-hooing of how hard companies have it maintaining unprofitable URLs, I think Ben hasn’t considered the possibility of a handover to a cooperative of users—something that might yet happen with MySpace (at least there’s a campaign to that effect; it will probably come to naught). As Ben rightly points on, domain names are leased, not bought, so the idea of handing them over to better caretakers isn’t that crazy.

Speed up your site using prefetching by Jon Fox

More details on DNS prefetching, page prefetching and, controversial, page pre-rendering.

Front-end performance for web designers and front-end developers by Harry Roberts

A really good introduction to front-end performance techniques. Most of this was already on my radar, but I still picked up a handy tip or two (particularly about DNS prefetching).

At this stage it should go without saying that you should be keeping up with this kind of thing: performance is really, really, really important.

xip.io: wildcard DNS for everyone

It took me a while to get my head ‘round it, but this routing service from 37 Signals is handy for testing local sites on multiple devices (kind of like showoff.io).

Page Speed Service Home

Performance shit just got real.

You can now sign up with Google to have your site pass every request through them and get your documents served up optimised.

Why I Don’t Self-Host Anymore | romkey.com

A comprehensive look at some of the problems with taking self-hosting to its logical conclusion: running your own web server.

Tom Morris - .tel, .xxx and .mobi are all pointless and idiotic

If I were an American, I’d now be saying something like “ICANN have jumped the shark”. Instead, I’m British, so I’ll say “ICANN are fucking useless twats who need a firm kick in the bollocks”.