marcus.io · Making RSS more visible again with a /feeds page
Personal website owners – what do you think about collecting all of the feeds you are producing in one way or the other on a
/feedspage?
Sounds like a good idea! I’ll get on that.
Tags: urls
112
Wednesday, June 3rd, 2020
Monday, May 4th, 2020
window.location Cheatsheet - DEV Community 👩💻👨💻
Everything you ever wanted to know about window.location in JavaScript, clearly explained.
Wednesday, March 11th, 2020
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.
Friday, February 7th, 2020
IncrementURL
Last month I wrote some musings on default browser behaviours. When it comes to all the tasks that browsers do for us, the most fundamental is taking a URL, fetching its contents and giving us the results. As part of that process, browsers also show us the URL of the page currently loaded in a tab or window.
But even at this fundamental level, there are some differences from browser to browser.
Safari only shows you the domain name—and any subdomain names—by default. It looks like nice and tidy, but it obfuscates what page you’re on (until you click on the domain name). This is bad.
Chrome shows you the full URL, nice and straightforward. This is neutral.
Firefox, like Chrome, shows you the full URL, but with a subtle difference. The important part of the URL—usually the domain name—is subtly highlighted in a darker shade of grey. This is good.
The reason I say that what it highlights is usually the domain name is because what it actually highlights is eTLD+1.
The what now?
Well, if you’re looking at a page on adactio.com, that’s the important bit. But what if you’re looking at a page on adactio.github.io? The domain name is important, but so is the subdomain.
It turns out there’s a list out there of which sites and top level domains allow registrations like this. This is the list that Firefox is using for its shading behaviour in displaying URLs.
Safari, by the way, does not use this list. These URLs are displayed identically in Safari, the phisherman’s friend:
- example.com
- example.github.io
- github.example.com
Whereas Firefox displays them as:
- example.com
- example.github.io
- github.example.com
I learned all this from Jake on a recent edition of HTTP 203. Nicolas Hoizey has writen a nice little summary.
Jake acknowledges that what Apple is doing is shi… suboptimal, what Firefox is doing is good, and then puts forward an idea for what Chrome could do. (But please note that this is Jake’s personal opinion; not an official proposal from the Chrome team.)
There’s some prior art here. It used to be that, if your SSL certificate included extended validation, the name would be shown in green next to the padlock symbol. So while my website—which uses regular SSL from Let’s Encrypt—would just have a padlock, Medium—which uses EV SSL—would have a padlock and the text “A Medium Corporation”.
Extended validation wasn’t quite the bulletproof verification it was cracked up to be. So browsers don’t use that interface pattern any more.
Jake suggests repurposing this pattern for all URLs. Pull out the important bit—eTLD+1—and show it next to the padlock.
I like this. The full URL is still displayed. This proposal is more of an incremental change. An enhancement that is applied progressively, if you will.
I also like that it builds on existing interface patterns—Firefox’s URL treatment and the deprecated treatment of EV certs. In fact, I think the first step for Chrome should be to match Firefox’s current behaviour, and then go further with something like Jake’s proposal.
This kind of gradual change was exactly what Chrome did with displaying https and http domains.
Jake mentions this in the video
We’ve already seen that you have to take small steps here, like we did with the
httpschange.
There’s a fascinating episode of the Freakonomics podcast called In Praise of Incrementalism. I’ve huffduffed it.
I’m a great believer in the HTML design principle, Evolution Not Revolution:
It is better to evolve an existing design rather than throwing it away.
I’d love to see Chrome take the first steps to Jake’s proposal by following Firefox’s lead.
Then again, I’d love it if Chrome followed Firefox’s lead in implementing subgrid.
Thursday, January 23rd, 2020
This Page is Designed to Last | CSS-Tricks
I feel there is something beyond the technological that is the real trick to a site that lasts: you need to have some stake in the game. You don’t let your URLs die because you don’t want them to. They matter to you. You’ll tend to them if you have to. They benefit you in some way, so you’re incentivized to keep them around. That’s what makes a page last.
Tuesday, September 3rd, 2019
WICG/ScrollToTextFragment: Proposal to allow specifying a text snippet in a URL fragment
It looks (a more complex version of) fragmention might be coming to Chrome.
Friday, March 29th, 2019
Slashed URI
This is my kind of URL nerdery. Remy ponders all the permutations of URLs ending with slashes, ending without slashes, ending with with a file extension…
Friday, January 11th, 2019
Four Cool URLs - Alex Pounds’ Blog
A fellow URL fetishest!
I love me a well-designed URL scheme—here’s four interesting approaches.
URLs are consumed by machines, but they should be designed for humans. If your URL thinking stops at “uniquely identifies a page” and “good for SEO”, you’re missing out.
Sunday, September 9th, 2018
“Killing the URL” | CSS-Tricks
URLs are the single greatest feature of the web.
Friday, September 7th, 2018
881410 - Incorrect transforms when stripping subdomains
The latest version of Chrome is removing seams by messing with the display of the URL.
This is a bug.
Thursday, September 6th, 2018
The mysterious case of missing URLs and Google’s AMP | sonniesedge.co.uk
My reaction to that somewhat sensentionalist Wired article was much the same as Charlie’s—seeing it on the same day at the latest AMP sneakiness has me worried.
The hiding of URLs fits perfectly with AMPs preferred method of making sites fast, which is to host them directly on Google’s servers, and to serve them from a Google domain. Hiding the URL from the user then makes a Google AMP site indistinguishable from an ordinary site.
As well as sharing Charlie’s concern, I also share her hope:
I really hope that the people who are part of Google can stop something awful like this from happening.
Wednesday, September 5th, 2018
Google Wants to Kill the URL | WIRED
Change will be controversial whatever form it takes. But it’s important we do something, because everyone is unsatisfied by URLs. They kind of suck.
Citation very fucking needed.
I’m trying very hard to give Google the benefit of the doubt here, but coming as it does on top of all the AMP shit they’re pulling, it sure seems like Google are trying to remake the web in their image.
Oh, and if you want to talk about URLs confusing people, AMP is a great example.
Daring Fireball: Medium Deprecates Custom Domains Service
I know many people love Medium’s editing interface, but I just can’t believe that so many writers and publications have turned toward a single centralized commercial entity as a proposed solution to what ails the publishing industry. There is tremendous strength in independence and decentralization.
Friday, August 3rd, 2018
StyleURL - share CSS tweaks instantly
This is an interesting tool: mess around with styles on any site inside Chrome’s dev tools, and then hit a button to have the updated styles saved to a URL (a Gist on Github).
Friday, June 1st, 2018
Let’s make the grimy architecture of the web visible again by Russell Davies
Beneath the URL shorteners, the web!
It’s increasingly apparent that a more digitally literate citizenry would be good for a thousand different reasons. A great way to start would be to make URLs visible again, to let people see the infrastructure they’re living in.
Tuesday, April 10th, 2018
Think like it’s 1995; code like it’s 2035 - Grayscale
This is such a great write-up of the workshop I did in Hong Kong!
Jeremy, it was a pleasure to work with you and you are always welcome here in Hong Kong!
If you fancy having this one-day workshop at your company, get in touch.
Wednesday, April 4th, 2018
Brendan Dawes - I Heart URLs
When I’m asked to give an example of a beautiful piece of design, perfect in form and function, I often respond with “the URL.”
I love every word of this beautifully-written love letter from Brendan.
Monday, February 12th, 2018
Eventually, every app builds for the web. Here’s why.
Sharing an experience without asking you to install software is something only the web can do.
Thursday, December 21st, 2017
Extended Validation is Broken
How a certificate with extended validation makes it easier to phish. But I think the title could be amended—here’s what’s really broken:
On Safari, the URL is completely hidden! This means the attacker does not even need to register a convincing phishing domain. They can register anything, and Safari will happily cover it with a nice green bar.
Monday, October 9th, 2017
FriendChip Beacons - With support of Eddystone and Physical Web
I quite like the idea of broadcasting my URL from a friendchip bracelet.