294 points by onli 9 days ago | 99 comments on HN
| Mild positive Editorial · v3.7· 2026-02-26 03:47:17 0
Summary Digital Access & Usability Acknowledges
This article examines Flickr's URL design scheme as a model of user-centered interface design, celebrating how readable and editable URLs enabled information sharing and navigation. The content implicitly acknowledges the connection between thoughtful technical design and user agency in accessing and sharing information, touching lightly on principles of information freedom and cultural participation.
However, getting rid of the /photos prefix would be a terrible improvement.
Having the /{username} at the root of the routing logic means that every URL should either query the user database for a match or use /{username} as a catch-all fallback if no other patterns match. But this makes resolving real 404 pages much more expensive.
The shift from URLs accessing resources on file systems to more abstract resources (implicitly HTML unless the headers said otherwise) occurred around 1999/2000. Suddenly we were all doing it once we’d figured out the necessary Apache directives. It wasn’t just Flickr, although it and its APIs were a good example of clean URL design
> I would also try to add a human-readable slug at the end, because…
No? Because what would it be based on and if you edited the thing that it's based on then the URL would either change, or get out of sync which woudl suck. You could ignore the suffix meaning flickr.com/mwichary/sets/72177720330077904-<everything-past-the-previous-dash-is-ignored> I'm not sure if that would be a positive, although I guess S.O. does something like that. The issue is other sites really want to know if it's a link to the same resource or a different resource. And while you could redirect to the new one that just makes more work for everyone.
> I would get rid of /photos
I wouldn't because then you'd had have https://flickr.com/settings but that would not be a user named "settings" and the same for every other alternate purpose URL
> Alternatively, I would consider getting rid of numerical ids altogether and relying on name alone. Internet Archive does it at e.g. archive.org/details/leroy-lettering-sets, but that has some serious limitations that are not hard to imagine
They don't rely on title alone, it's a separate identifier. You can set it to anything and you can't change it afterwards but you can change the title.
Flickr deserves a lot of praise for a number of technical advances that I wish had seen wider adoption.
Their API was one of the first and honestly still one of the most enjoyable to actually use as a developer. It's still full of incredibly interesting API calls that you wouldn't expect from it unless you read carefully. Did you know, for example, that flickr API will provide you with the bounding box co-ordinates of different types of places? From a neighbourhood all the way up to a continent?
They implemented the Where On Earth ID (WOEID) which was a super useful way of disambiguating different places that shared latitude and longitude (for example, being able to disambiguate the Sydney Opera House, Circular Quay and Sydney Harbour which all can potentially share the same lat/long co-ords).
They implemented machine tags which are tags in the form of -
namespace:predicate=value
Which, when it was implemented by other sites with machine tags allowed you to get and group all kinds of interesting combinations of content.
Yeah, honestly flickr had some incredible tech the was so much fun to explore and use. That their vision of what the web could be wasn't the one that won is one of the great losses of the web IMO.
> (Alternatively, I would consider getting rid of numerical ids altogether and relying on name alone. Internet Archive does it at e.g. archive.org/details/leroy-lettering-sets, but that has some serious limitations that are not hard to imagine.)
I could try to imagine these limitations and how the Internet Archive overcomes them, but I'd prefer reading about it.
I agree 100% with the author, clean, easily readable and well structured URLs make the web a better place. URL is a hierarchical structure as introduced in the RFC1738 by a guy you might have heard, Tim Berners-Lee, the inventor of the World Wide Web :-)
https://www.rfc-editor.org/rfc/rfc1738
Easily readable URLs is something I learned in the 90s and I still try to enforce in everything I create.
Unfortunately things are going in the opposite direction with media platforms creating an encoded blob impossible to edit by hand so that you (or a tool) cannot strip tracking etc.
Flickr was a hero, then yahoo/smugmug killed it. It's still there, but along the way all changes reduced it to an also-ran. It's still a nice tool, but I just don't see myself using it again. The URL scheme, as neat as it was, I never noticed or cared to hack at. I just wanted to upload photos.
I don't know how much Flickr is used these days, but I remember it was quite popular some 15 years ago. I decided to search around, and discovered that it is a treasure trove of photos from the period 2005 - 2015, and incredibly easy to search / filter.
Internet archeology is something I've always found fascinating, and I don't think people realize how much data has been lost after we moved to the modern "big tech" internet of today. So many data hosting services disappear back in the mid/late 00s, and with that, the data too. After social media exploded, many just stared storing all their photos there.
from the article :
> This might seem silly. The user interface of URLs? Who types in or edits URLs by hand? But keyboards are still the most efficient entry device.
Can someone let Apple know this ? Safari URL bar is a disaster. If I edit a URL say to remove a part and hit enter 9/10 times it searches the internet.
It seems to forget that it's a url it's displaying despite it cutting the front off, even after telling it to use long urls in address bar. It's so annyoing I actually use another browser since I often need to paste in or modify urls for the work I do. Safari sucks hard. Any solutions to disabling 'search' in the address bar ? I want it to be a URL bar only, and anythign typed in it should be resolved and not searched.
The flip side is enumerable IDs. Back when I was scraping a site for a side project, sequential photo IDs were basically a free sitemap. YouTube's random-ish IDs aren't just branding — they at least make bulk harvesting annoying.
I thought Photobucket did it better, with the exception of having to know which server an individual's bucket was on.
It's been a long while, but if I recall, the url schema was something like a00.photobucket.com/albums/username/someimage.jpg
But what was really cool about it was that you could change someimage.jpg to someimage.png and Photobucket would serve a PNG instead. Or you could change someimage.jpg to th_someimage.jpg and Photobucket would serve a thumbnail of the picture. It was very cool.
Strange, because I always remember Flickr having horrible UX. You could never just open an image file directly; if you tried, Flickr would always redirect you to a page which obscured the image behind an invisible layer which obscured pointer events such as right-click.
Can't say enough good things about flickr. Those people nailed it in 2004 (I've been a paying subscriber since their first year) and everyone else has been making bad copies ever since. Tagging, friends (pretty much inventing social media without any of the diabolical dark patterns), full-resolution archival storage, a solid API, all over two decades ago. I'm frankly embarrassed for things like Instagram, it's like they're not even trying.
And a bit about the skill of whoever made the wiki software, they need better documentation and automation to help even less-skilled admins to have clean URLs
> You could ignore the suffix meaning flickr.com/mwichary/sets/72177720330077904-<everything-past-the-previous-dash-is-ignored> I'm not sure if that would be a positive, although I guess S.O. does something like that.
GitHub manage to do it. Most URLs you'd think of are either redirects to other bits of the site, or accounts owned by GitHub themselves. It just takes a bit of planning.
I'm a big fan of writing little bits of code into my URL routers that check for pages and try to correct typos. So if someone types https://some-awesome-site.org/jhon-davisdon it will check and correct it to /john-davidson. What's nice is always delivering the "canonical" link rel when you serve the correct page that way, too. I make the assumption that people still try to type links, sometimes ;)
Flickr is an unsung hero in this. I uploaded photos back in 2011 when I purchased my first DLSR camera, and had forgotten about them until this day, and seems they're still up! Did some other checks for content I uploaded back then, and seemingly only my YouTube and Vimeo videos are still up, everything else I spot checked from the same period seems to be gone by now.
I understand the Yahoo part, but what do you mean with smugmug? My impression was that they bought it and "revived" it but I might misremember the history there.
It still has plenty of active users (myself included) but it feels much smaller than the 2010s. The groups are great if you can find ones that match your taste, and it’s way more fun to do that and share you photos with human-curated communities than with the algorithmic feed.
I'm always surprised that archive.org's URL scheme is still used. To this day uploads will have URLs like `/details/hey` and IIRC the only thing to distinguish them from other submissions with matching names is the auto appending of a digit. It feels like `New Folder (1)` for URLs.
Edit: I misremembered. They append the date to the URL to avoid name conflicts, like `/details/hey_20260122`.
I think Youtube got it right early. Make it short enough but random, so users won't be tempted to manually type it out and make mistakes but if they really do need to manually type it the length is reasonable. It also made sharing via SMS/Twitter limits more feasible.
Don't forget their "interestingness" algorithm that would determine which photos get to the top position in groups and other shares views. Way before ML ranking.
This was a big thing around the time of Flickr and, if my memory is still working, del.icio.us. There was a push for “url is the new command line” which I wish had gotten more traction because there were some fun things happening. I feel like Yahoo Labs was involved in a lot of it, including Pipes and their ahead of its time JavaScript framework. It’s a strange sliding doors moment for me because I turned down a job there right around this time.
The oldest account have a direct URL in the form of youtube.com/username. Newer account had youtube.com/user/username (I think most account have both URLs).
Then YouTube was bought by Google and they introduced "channels", so some channels had youtube.com/channel/username.
Then YouTube wanted to become like TikTok and they forced at-usernames some years ago, so now accounts have a URL like youtube.com/@username
You can absolutely still do this. I'm still a Flickr Pro subscriber since 2015, and I still regularly upload photos to Flickr. I don't think there was a set of changes that reduced Flickr to an also-ran, the entire market shifted. First, there was a shift away from photography being focused on what I will short hand as "quality" towards being focused on what I'll short hand as "moments" with services like Instagram, which had 100m users by the end of 2013 and continued growing exponentially from there, which was deeply interconnected with the introduction of reliable fairly high-quality phone cameras built into smart phones.
Flickr was, and continues to be, a place where people who use actual camera equipment post photos that are taken not just to capture a moment, but to express a scene, using technique and artistry to do so. That type of high quality photography doesn't really get much traction in more contemporary social media, because the photos of moments shared on Instagram weren't about the photo, they were about the moment. It was about proving that you were in a place or experienced a thing, and the place or thing giving you social value. "Pics or it didn't happen."
Instagram has now largely been supplanted by TikTok, because short video is now much more of a common, engaging, and desired format than photography, and thankfully this means Flickr in 2026 is once again a refuge of die-hard photographers sharing their works, and not seeing much attempt to change it into Instagram 2.0. Many (maybe most) of the photos on Flickr are now taken with smartphones, but there is still an expectation from the community to focus on expressing a scene using technique and artistry, and modern smartphones now have good enough cameras to do just that without detracting from what you're trying to express.
I use a couple of JS libraries to serve image galleries, and they conform to the Flickr _[a-z] type of naming to indicate resolution. The library will load the appropriate size based on the available real estate.
The auto serving of the chosen output extension is interesting. Wonder if they were automatically created when making the various image sizes, or only on the first time it was requested. And how many formats were supported? The one that got me was hitting an API and tagging with xml|json to get the response as needed instead of sending it as a dedicated query paramter
I remember signing up for an AI inference provider, noticing my profile page was "/<username>" and changing my name to logout which worked but caused some amusing errors. Oops!
What I typically end up doing is just recalc the slug and see if it matches the provided one. If it doesn't redirect to the most up to date slug matching the id. Though who knows if those old SEO patterns still matter these days...
Maybe it was like that for a while? But flickr allowed image downloads, there was a dropdown in the UI with the available sizes for years. And it had an API (+stable URLs) to download images.
It's possible they did not allow the way you tried to access images directly, to enable control of the downloads for the photographer. But I think you misjudged the behaviour back then, they were pretty open.
You should write all that up! (I've been around for a while and I never used Flickr except as a casual, but I did know about a lot of mashups and even spent time using FlickrLickr for Wikipedia; yet I've never heard of... any of that.)
Content celebrates clear, readable, easily shareable URLs as a design principle. The author frames URL readability and editability as beneficial to users, enabling them to navigate and share information without friction. This implicitly supports accessibility to information.
FW Ratio: 60%
Observable Facts
Page discusses how Flickr's URL design made links easily readable and shareable without modification.
Author explains that well-designed URLs can be edited and navigated efficiently using keyboard shortcuts, reducing dependency on intermediary interfaces.
Content emphasizes that naked URLs were placed in emails, Markdown, blog posts, and sentences without truncation, enabling direct information sharing.
Inferences
The author's celebration of human-readable, editable URLs suggests a value for user agency and direct information access, which aligns with principles of freedom of information.
The discussion of URL design as affecting user ability to navigate and share information implicitly supports the idea that interface design choices enable or restrict freedom of expression and access.
Content discusses the technical design of a cultural platform (Flickr) and how its URL scheme enabled sharing and use. There is an implicit recognition of cultural participation through accessible design.
FW Ratio: 50%
Observable Facts
Author credits Flickr's URL design with educating them about 'URLs as user interface' in the late 2000s, describing it as part of their personal education.
Article emphasizes that Flickr's design choices enabled people to easily share photos and collections without friction.
Inferences
The author's framing of URL design as educational suggests recognition of how digital design shapes users' ability to engage with and understand technology.
The celebration of Flickr's accessibility to sharing implies value for cultural participation and the dissemination of creative work.
The article is freely accessible with no paywall or registration barrier, supporting public access to written discourse about web design. The domain's access model (noted in DCP) adds structural support for information dissemination.
The article's free accessibility allows readers to access discourse about digital design and cultural platforms, supporting participation in shared knowledge about technology.