Google Is Shutting Down Its Goo.gl URL Shortening Service (engadget.com)
Google is replacing its URL shortener service, goo.gl, with Firebase Dynamic Links (FDL) as of April 13th. These new smart URLs will let you send people to any location within iOS, Android or web apps. Engadget reports: You won't be able to create new goo.gl short links after the 13th, but existing users can manage them via the goo.gl console for the next year. After that, all the links will still work, but you won't be able to access the console itself after March 30th, 2019. Google suggests creating FDLs from now on, or using other shortening services like Bitly and Ow.ly.
"Drive more installs with social, email, and SMS marketing campaigns"
Doesn't sound fishy at all.
Right up until next year when forever means they are shutting it down in 2 weeks
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
I'm always amazed by the short-term-ness of anything and everything software.
When will we reach maturity with stable, intercompatible software? 100y from now, 1000?
Signed,
AC
I use goo.gl urls to send people map links but the dialog which does that now has lost the shortener option and replaced it with a link which is automatically shortened. Why do this if you are ditching the shortener?
http://michaelsmith.id.au
Two things you shouldn't do on the internet: rely on URL shorteners (because they remove human readability from URLs, add an extra unnecessary lookup, and rely on a service that may randomly disappear), and rely on Google (because anything they make may randomly disappear).
Don't use their office tools. Don't use their programming languages. Don't use their online storage. Don't use their email service. Don't even use their bloody search engine. Sooner or later they get tired of it, and it will disappear without a trace.
Or tinyurl.com. They have been doing this for a long time now, and no log in required.
Two links to Slashdot.org - https://tinyurl.com/87d will take you right to /. and https://preview.tinyurl.com/87... which will allow one to preview or see what link you will be taken to.
"Click here to enable previews." seen when previewing, I assume (I've never used it) will make previewing automatic, or default.
What is the schedule for shutting down FDL?
URL shorteners are of the devil - people should never be asked to click on an obfuscated link.
#DeleteChrome
Nothing is free that lasts forever.
Can't decide if it's a good thing or not because my main exposure to shortened links is when the spamming scammers use them to disguise their drive-by attack websites. Anyone ready to vouch for this new approach (or reproach it)?
By the way, I've never understood the abuse of shortened links. If they wanted to stop the abuse, the solution is quite obvious. When the abuse is reported, they would take over the link and permanently repoint it at the worst website for the spamming scammer. For example, rather than direct the suckers to the scammer's website, the repointed shortened URL could point to a police website warning against the danger of clicking on mysterious links. The more spam the scammer sends, the worse for the scam.
Freedom = (Meaningful - Coerced) Choice != (Speech | Beer^2), and sad sock puppets' bad mods avail them naught.
The problem is that there are people, who made it a job, and linked their livelihood to that job.
Office software has been finished for decades now.
But apart from corporate useless feature creep, it had to adapt to ever-changing OS APIs, because their abstraction was not hardware-independent (and UI-independent) enough. Which was mostly for performance reasons. For which the office software had no actual need.
I'm presently working on something to change most of that.
... I see no big problem here, which, of course, is a positive exception in Google's history of service discontinuations.
Those few parts of Google's own services which produced short goo.gl links themselves when clicked on, which are primarily Google's own problems now, if they even still exist. It's not as if goo.gl would have been the only or just the best URL shortener service. Personally, I like tinyurl.com, because it has been there for such a long time – and because it gives cautious folks the option to look up what's behind a shortened link before they go there.
The Firebase website says "Dynamic Links are free forever,"
IOW, it's free now and even in the future when Google dumps it and discontinues the service it's still free.
HAHA, very funny Google,
J
They are for giving somebody over the telephone on hand-written on a piece of paper and similar situations, where you want to write or memorize as little as possible.
> Google suggests creating FDLs from now on, or using other shortening services like Bitly and Ow.ly.
Even better: Don't use an url shortener service at all. What's the point?
Don't Goatcx that link my friend! Pass the real link over to me!
I, being of sound mind, avoid these like I avoid hoes with stanky twats.
I just logged into this new service and it wanted to me to create a project before seeing the console, so i did and now it says
"Send users to the right place in your app, whether or not it is already installed "
i dont have an "app", i just want to create a short link to a webpage, methinks this is the wrong product for a replacement for goo.gl shortlinks
What's the point?
Like everything else on the web, for tracking people.
I've noticed that the shortened url isn't as short as it used to be.
that is all.
How are you enjoying google-wave, reader and the 50 other popular services they've started and killed?
I don't use shortened links. They can redirect anywhere. Just not worth the risks.
But I don't use goog-book-tweet-gram either.
BTW, self-hosting these things is pretty trivial today.
Why would I want to be marketed to? They didn't explain that in the article.
from the braindead soldiers of the android army.
You can't tell who sold your data off or leaked it if you have a dozen apps all collecting it.
Our email servers enforce a "no shortening" policy. Any emails with a shortened URL is bounced. When we explain to the sender why it bounced, they usually say, "Oh, yeah, that makes sense!"
Email isn't Twitter. There is no reason to not use the full link, which can be examined to discover that it is headed off to a compromised Wordpress site to pick up the latest targeted malware.
Only a few of the shortening services provide an easy way to decode the link prior to clicking on it, and some of those require you to "add a cookie" or modify the link in some way to view the real target.
There are sites that will do the decoding for you, by fetching the shortened URL and reporting back where they were redirected to, but that still tells an attacker that their email reached someone.
So, bouncy bouncy!
At this point anyone defending Google is outed as a small-souled bugman.
I mean email is OK in the beginning but then allow us to switch to proper 2FA (oauth, gauth type stuff).
The advantage of email authentication is that SMTP is federated in a manner that doesn't require a preexisting business relationship between each identity provider (IDP) and each relying party (RP). OAuth-based authentication protocols, such as OpenID Connect, require each RP to register with each IDP to receive a client ID that uniquely identifies the RP to that IDP. Because this client ID cannot be reused with other IDPs, this is an n^2 problem, meaning doubling both the number of RPs and the number of IDPs means quadruple the overall effort to issue and track client IDs. The OAuth 2 specification describes an optional Dynamic Client Registration (dyn-reg) feature that allows an RP to automatically obtain a client ID from the IDP on the RP's first connection to that IDP, but to my knowledge, none of the popular IDPs offer dyn-reg.
Moreover, a lot of IDPs offering OAuth-based authentication expect RPs to keep part of the client ID secret. This is especially true of IDPs that use the HMAC-based OAuth 1.0a, such as Twitter, instead of the bearer token-based OAuth 2. This makes authentication from a desktop application, mobile application, or single-page web application impossible because the client ID cannot be kept secret from someone with a copy of the executable and a debugger. I've explained this before, as has Okta's OAuth guide, but Twitter has threatened to revoke and refuse to reissue client IDs that leak.
Email isn't Twitter. There is no reason to not use the full link
Other than that RFC 2821's definition of "text line" limits SMTP line length to 998 characters. How should someone who needs to send a longer URL to your clients do so?
"When a user shares content from your app, the ultimate goal is to convert their friends into active native app users."
Perhaps the thing I hate most with mobile these days are every simple thing must be APP.
Why use shortened links to begin with? What's wrong with using full links?
In the end, all these shortening services do is break the web. The same goes for third-party image hosting services. I keep finding threads where people have posted projects online but all the photos are broken because of Photobucket's new terms of service.
#DeleteFacebook
Simple. The user should continue to have the choice to stay in a web browser.
But I don't want an app to spy on me? Google - Screw you.