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.

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

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.

Easily readable URLs is something I learned in the 90s and I still try to enforce in everything I create.

Also, when you look at a site and see URLs like /wiki/index.php/MyPage it tells you about the skill level and care of the site administrators.

I could try to imagine these limitations and how the Internet Archive overcomes them, but I'd prefer reading about it.

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.

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.

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.

I learned quickly to avoid Flickr links.

I would be very confused if flickr.com/contact went to a user page.

https://gamicus.fandom.com/wiki/Game_Neverending

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.

?set=2546&pic=8597 is much easier to decipher than /2546/8597

I'm sorry what? URL params are just a thing.

Stopped caring about them when they cancelled their 1TB free storage after 5 years, company which can't be trusted long term with your data. Plus the UI was horrible anyway.