Making Your Own URL Shortener
blog.skywelch.io
Making Your Own URL Shortener
1–7 of 7 posts
Re: Making Your Own URL Shortener
#2Don't use or create a URL shortener. They are only ever useful to spammers, they're a security risk, and they break the web[1].
1. https://t37.net/why-link-shorteners-harm-your-readers-and-de...
Re: Making Your Own URL Shortener
#3Don't use or create a URL shortener. They are only ever useful to spammers, they're a security risk, and they break the web[1]. 1. https://t37.net/why-link-shorteners-harm-your-readers-and-de...
I'm inclined to agree that the use of large URL shorteners obfuscates things too much and can contribute to spam.
However, this is a personal domain for my use only. And I don't think you can simply dismiss the usefulness of being able to track link usage and referrers without using nasty client-side JS stuff.
I'm also using "shortcodes" rather than random IDs for most stuff so the intent isn't lost.
Re: Making Your Own URL Shortener
#4Don't use or create a URL shortener. They are only ever useful to spammers, they're a security risk, and they break the web[1]. 1. https://t37.net/why-link-shorteners-harm-your-readers-and-de...
I'm inclined to agree that the use of large URL shorteners obfuscates things too much and can contribute to spam. However, this is a personal domain for my use only. And I don't think you can simply dismiss the usefulness of being able to track link usage and referrers without using nasty client-side JS stuff. I'm also using "shortcodes" rather than random IDs for most stuff so the intent isn't lost.
Using it yourself isn't the same as instructing other people how to do it.
Using it for a personal domain is likely going to hurt your SEO. You can track behavior on the server side without JS just as easily without short URLs.
Re: Making Your Own URL Shortener
#5Don't use or create a URL shortener. They are only ever useful to spammers, they're a security risk, and they break the web[1]. 1. https://t37.net/why-link-shorteners-harm-your-readers-and-de...
I'm inclined to agree that the use of large URL shorteners obfuscates things too much and can contribute to spam. However, this is a personal domain for my use only. And I don't think you can simply dismiss the usefulness of being able to track link usage and referrers without using nasty client-side JS stuff. I'm also using "shortcodes" rather than random IDs for most stuff so the intent isn't lost.
The only thing that really bothers me personally about shorteners is not knowing where I'm going to end up, and not being able to identify articles I've read before. A shortener with a dedicated domain and user-chosen ids should cover that just fine. The only outstanding issue in the article is a single extra DNS lookup, which is pretty minor compared to the massive chains which were causing the problem.
Re: Making Your Own URL Shortener
#6Earlier quoted context omitted.
I'm inclined to agree that the use of large URL shorteners obfuscates things too much and can contribute to spam. However, this is a personal domain for my use only. And I don't think you can simply dismiss the usefulness of being able to track link usage and referrers without using nasty client-side JS stuff. I'm also using "shortcodes" rather than random IDs for most stuff so the intent isn't lost.
The only thing that really bothers me personally about shorteners is not knowing where I'm going to end up, and not being able to identify articles I've read before. A shortener with a dedicated domain and user-chosen ids should cover that just fine. The only outstanding issue in the article is a single extra DNS lookup, which is pretty minor compared to the massive chains which were causing the problem.
There's an additional security issue when a URL shortener is abandoned and malware groups pick up the domain.
Re: Making Your Own URL Shortener
#7Earlier quoted context omitted.
The only thing that really bothers me personally about shorteners is not knowing where I'm going to end up, and not being able to identify articles I've read before. A shortener with a dedicated domain and user-chosen ids should cover that just fine. The only outstanding issue in the article is a single extra DNS lookup, which is pretty minor compared to the massive chains which were causing the problem.
There's an additional security issue when a URL shortener is abandoned and malware groups pick up the domain.
If the shortener is tied to a site than why is that risk any greater than the risk of the site itself being abandoned?