Yeah, shouldn’t be too hard to at least keep the existing links working in a read only state.
Comment on Google's goo․gl links will stop working in August 2025
OsrsNeedsF2P@lemmy.ml 4 months ago
The dumbest part is like, why? How much work is it really to keep goo.gl links around?
In 2018, Google wanted developers to move to Firebase Dynamic Links that detect the user’s platform and sends them to either the web or an app. Google ended up also shutting down that service for devs.
lmao
jonne@infosec.pub 4 months ago
jarfil@beehaw.org 4 months ago
A lot.
Goo.gl has a namespace for 10 billion entries, it used to keep tracking/analytics data for each link, with a user interface, and it would happily generate them for links to internal stuff.
Just keeping it running would take some containers of server racks, plus updating the security, accounting for changing web standards, and so on.
Keep in mind this isn’t some self-hosted url shortener with less than a million entries and a peak of 10K users/second, that you can slap onto a random sever and keep it going. It’s a multiple orders of magnitude larger beast, requiring a multi-server architecture just to keep the database, plus more of the same for the analytics, admin interface… and users will expect it to return a result in a fraction of a second, worldwide.
Kissaki@beehaw.org 4 months ago
They could drop all the tracking though and only serve the public redirects. A much simpler product that would retain web links.
jarfil@beehaw.org 3 months ago
I think they’ve dropped the tracking already. Still, where’s the money in that?
They also can’t release the database, not without prior consent of the link creators, or risking exposing some login credentials some very smart people might’ve put in there.
Kissaki@beehaw.org 3 months ago
Why does there have to be money in it when they’re sunsetting the service?
Penguincoder@beehaw.org 4 months ago
Good analysis, I agree and understand.