by anarazel on 5/28/25, 4:28 PM with 189 comments
by kccqzy on 5/28/25, 5:10 PM
by mananaysiempre on 5/28/25, 4:54 PM
> url shortening was a fucking awful idea[2]
by s17n on 5/28/25, 5:58 PM
by creatonez on 5/28/25, 6:28 PM
by amiga386 on 5/28/25, 4:48 PM
> Google Go Links (2010–2021)
> Killed about 4 years ago, (also known as Google Short Links) was a URL shortening service. It also supported custom domain for customers of Google Workspace (formerly G Suite (formerly Google Apps)). It was about 11 years old.
by layer8 on 5/28/25, 7:08 PM
by olalonde on 5/28/25, 5:34 PM
This is the second time today I've seen a disclaimer like this. Looks like we're witnessing the start of a new trend.
by wrs on 5/28/25, 6:54 PM
by 2YwaZHXV on 5/28/25, 10:45 PM
by swyx on 5/28/25, 5:45 PM
i also wonder if url death could be a good thing. humanity makes special effort to keep around the good stuff. the rest goes into the garbage collection of history.
by sedatk on 5/28/25, 7:53 PM
by rurban on 5/29/25, 7:55 AM
by jimmyl02 on 5/28/25, 4:39 PM
Someone has to foot the bill somewhere and if there isn't a source of income then the project is bound to be unsupported eventually.
by sebstefan on 5/29/25, 9:03 AM
>Google (using their web search API)
>GitHub (using their API)
>Our own (somewhat limited) web logs
>The archive.org Stack Overflow data dumps
>Archive.org’s own list of archived webpages
You're an angel Matt
by shepmaster on 5/28/25, 4:56 PM
The Rust playground uses GitHub Gists as the primary storage location for shared data. I'm dreading the day that I need to migrate everything away from there to something self-maintained.
by 3cats-in-a-coat on 5/29/25, 12:58 PM
I've pondered that a lot in my system design which bears some resemblance to the principles of REST.
I have split resources in ephemeral (and mutable), and immutable, reference counted (or otherwise GC-ed), which are persistent while referred to, but collected when no one refers to them.
In a distributed system the former is the default, the latter can exist in little islands of isolated context.
You can't track references throughout the entire world. The only thing that works is timeouts. But those are not reliable. Nor you can exist forever, years after no one needs you. A system needs its parts to be useful, or it dies full of useless parts.
by 90s_dev on 5/28/25, 5:41 PM
He advocated for /foo/bar with no extension. He was right about not using /foo/bar.php because the implementation might change.
But he was wrong, it should be /foo/bar.html because the end-result will always be HTML when it's served by a browser, whether it's generated by PHP, Node.js or by hand.
It's pointless to prepare for some hypothetical new browser that uses an alternate language other than HTML and that doesn't use HTML.
Just use .html for your pages and stop worrying about how to correctly convert foo.md to foo/index.html and configure nginx accordingly.
by devrandoom on 5/28/25, 11:34 PM
I'm pretty sure the lore says that a solemn promise from Google carries the exact same value as a prostitute saying she likes you.
by nssnsjsjsjs on 5/29/25, 12:55 AM
Where URLs may last longer is where they are not used for the RL bit. But more like a UUID for namespacing. E.g. in XML, Java or Go.
by devnullbrain on 5/28/25, 5:59 PM
It's become so trite to mention that I'm rolling my eyes at myself just for bringing it up again but... come on! How bad can it be before Google do something about the reputation this behaviour has created?
Was Stadia not an expensive enough failure?
by diggan on 5/28/25, 5:19 PM
URIs however, can be made to last forever! Also comes with the added benefit that if you somehow integrate content-addressing into the identifier, you'll also be able to safely fetch it from any computer, hostile or not.
by Ericson2314 on 5/29/25, 3:20 AM
We should be using more of them.
by mbac32768 on 5/29/25, 2:36 AM
but perhaps I don't appreciate how much traffic godbolt gets
by sdf4j on 5/28/25, 7:13 PM
And yet… that was a very self-destructive decision.