-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Additional redirs #50
Comments
BTW related but not related, I have a list of ~ 30 domain shorteners plus 3,200 "bit.ly custom shortners" -- these are often used to add tracking cgi args to links that look like they don't have any, but it's hard to do anything useful with them in the context of your extension; you are already just following them and then stripping the args off of the redirect... |
Regarding your comment above: yeah, unless there's a way to expand or figure out what the ultimate target is from the shortened link itself, I'm not sure there's anything we can really do without following it first. Are you aware of any way? Regarding this example
|
I'm pretty sure the integer is a customer number.
Instapage is a small business -- 615 hosts in the top 15 million, I probably should have left them off the list. Now that I look more carefully, more than half of instapage sites only have a single page. And you are correct, for the real shorteners there's no easy way to find out the link without asking the shortener. I'm thinking of providing a service to disintermediate, just because I (and every other search engine person) hate them with a passion... |
@newhouse there're also many more redirects in https://github.com/nokeya/direct-links-out. Should I convert them to a PR? |
The text was updated successfully, but these errors were encountered: