

That's tough enough to decipher. But over the past decade link shortening has grown in popularity. This predates micro-blogging sites like twitter, though the 140 character twitter limit drove adoption. Hovering over a shortened link shows only the shortened destination, not the final destination site.

So, what can we do about it? I have 3 methods we can use to help:
- Use features of the url shortener to show the destination link. That definitely works, however each shortener uses a different method including: prepending "preview" or "peek", or appending a character like +, - or ?. Here is a great blog post that covers these in depth.
- Use a browser plug-in or extension that expands shortened urls like Long URL Please or LongURL. These expand shortened URLs either inline or when you hover your mouse pointer over the link.
- Consider the source - twitter vets shortened url's but most sites do not. Here is a, somewhat geeky, post about URL shortener service security.
Do you use shortened links? How? And what else can you do to check the safety of shortened links before clicking?
No comments:
Post a Comment