Coming from anyone else, this glorious vision might seem far-fetched, but Anne is working to make it a reality.
I agree completely with the sentiment of this article (although the title is perhaps a bit overblown): you shouldn’t need a separate API—that’s what you’re existing URL structure should be.
I’m not entirely sure that content negotiation is the best way to go when it comes to serving up different representations: there’s a real value in being able to paste a URL into a browser window to get back a JSON or XML representation of a resource.
But this is spot-on about the ludicrous over-engineered complexity of most APIs. It’s ridiculous that I can enter a URL into a browser window to get an HTML representation of my latest tweets, but I have to sign up for an API key and jump through OAuth hoops, and agree to display the results in a specific way if I want to get a JSON representation of the same content. Ludicrous!
A heartfelt response from Vitaly to .net magazine’s digital destruction.
This a great proposal: well-researched and explained, it tackles the tricky subject of balancing security and access to native APIs.
Far too many ideas around installable websites focus on imitating native behaviour in a cargo-cult kind of way, whereas this acknowledges addressability (with URLs) as a killer feature of the web …a beautiful baby that we definitely don’t want to throw out with the bathwater.
I gave the opening keynote at the Beyond Tellerand conference a few weeks back. I’m talked about the web from my own perspective, so expect excitement and anger in equal measure.
This was a new talk but it went down well, and I’m quite happy with it.
The web’s walled gardens are threatened by the decentralised power of RSS.
Google is threatened by RSS. Google is closing down Google Reader.
Twitter is threatened by RSS. Twitter has switched off all of its RSS feeds.
It will dip and diminish, but will RSS ever go away? Nah. One of RSS’s weaknesses in its early days—its chaotic decentralized weirdness—has become, in its dotage, a surprising strength. RSS doesn’t route through a single leviathan’s servers. It lacks a kill switch.
My presentation from the Industry conference in Newcastle a little while back, when I stepped in for John Allsopp to deliver the closing talk.
I like the idea of a /purpose page: I should add one to The Session and Huffduffer.
This is a breath of fresh air: a blogging platform that promises to keep its URLs online in perpetuity.
Yes, yes, yes!
I like these design principles for server-side and client-side frameworks. I would say that they’re common sense but looking at many popular frameworks, this sense isn’t as common as it should be.
Luke’s notes from my talk at An Event Apart in Chicago.
Remember when I linked to the story of Twitter’s recent redesign of their mobile site and I said it would be great to see it progressively enhanced up to the desktop version? Well, here’s a case study that does just that.
A cautionary tale from Dave Winer of not considering digital preservation from the outside. We must learn the past. We must.
A really great article from Stephen on how we are mistakenly making assumptions about what users want. He means it, man!
Looks like the scourge of hashbangs is finally being cleansed from Twitter.
The Long Now blog is featuring the bet between myself and Matt on URL longevity. Just being mentioned on that site gives me a warm glow.
Matt has transcribed the notes from his excellent Webstock talk. I highly recommend giving this a read.
I really enjoyed Matt’s talk from Webstock. I know some people thought it might be a bit of a downer but I actually found it very inspiring.
A truly excellent article outlining the difference between share-cropping and self-hosting. It may seem that the convenience of using a third-party service outweighs the hassle of owning your own URLs but this puts everything into perspective.
- Can I bookmark this information? (stable URIs)
- Can I go from here to there with a click? (hyperlinks)
- Can I save the content locally? (open accessible formats)
I really like this proposal to allow for more nuanced linking using CSS selectors in fragment identifiers (though I worry about the overloading of the # symbol in URLs).
I really like the thinking that’s gone into the design of Github, as shown in this presentation. It’s not really about responsive design as we commonly know it, but boy, is it a great deep dive into the importance of URLs and performance.
Here’s one to add to Instapaper or Readability to savour at your leisure: Aaron Straup Cope’s talk at Museums and the Web 2010:
This paper examines the act of association, the art of framing and the participatory nature of robots in creating artifacts and story-telling in projects like Flickr Galleries, the API-based Suggestify project (which provides the ability to suggest locations for other people’s photos) and the increasing number of bespoke (and often paper-based) curatorial productions.
Namespacing fragment identifiers — CSS Wizardry—CSS, Web Standards, Typography, and Grids by Harry Roberts
Well, here’s something I didn’t know: fragment identifiers can use the colon to add another level of addressability.
A superb post by Dan on the bigger picture of what’s wrong with hashbang URLs. Well written and well reasoned.
James follows up on his previous excellent post on hashbangs by diving into the situations where client-side routing is desirable. Watch this space for a follow-up post on performance.
Read it and weep. Here are the articles on Wikipedia that reference URLs that are getting axed as part of the BBC’s upcoming cull.
Tim Bray calmly explains why hash-bang URLs are a very bad idea.
This is what we call “tight coupling” and I thought that anyone with a Computer Science degree ought to have been taught to avoid it.
So why use a hash-bang if it’s an artificial URL, and a URL that needs to be reformatted before it points to a proper URL that actually returns content?
Out of all the reasons, the strongest one is “Because it’s cool”. I said strongest not strong.
It turns out my Boolean URL tag hacking in Huffduffer is answering a real need: Will Myddelton had already put the same functionality together using Yahoo Pipes.
Documenting the use and abuse of fragment identifiers.
An excellent collection of best practices for designing URLs. I found myself nodding vigorously along with each suggestion.
Eleven years old and more relevant than ever.
Blaine is doing his bit to battle the great linkrot apocalypse with an archive of short urls and their corresponding endpoints.
Chris Shiflett gets behind the rev="canonical" movement. This thing is really gaining momentum.
rev="canonical" has a posse.
An aggregator of aggregators... and I'm posting a link to it on one of the aggregators.