We’ve all been in the position when sharing a web link with someone reveals a URL that is several lines long and full of hexadecimal IDs and so on. There are a few ways to make the long URL more acceptable – a simple one being to hot-link the URL under a piece of text.

In most email programs, in Word, and even in the new Yammer experience and some other web forum software, selecting some text and pressing CTRL-K lets you insert a URL under that text – so rather than saying “Flight Simulator – https://www.xbox.com/en-US/games/microsoft-flight-simulator”, you could just write “Flight Simulator”.

When it comes to sharing URLs with other people, though, you might still need the native URL rather than copying the text that has been hyperlinked, so in many apps and websites you could right-click a hyperlink and grab the URL (or in Office apps, again, put your cursor on the text and press CTRL-K to get the edit UI which would also let you put it on the clipboard).

It’s both easier to share and also to remember shorter URLs with simple names, but URLs for linking directly to a web forum discussion or Yammer post (in the new Yammer, click on the 3-dot icon to the side of a post to get the link directly) tend to be cumbersome and with lots of references within.

The first URL Shortening service was launched in 2002, tinyurl.com (and doesn’t the website look like a 2002 site?). The basic idea was that instead of having a 200-character URL, you could generate something that would have the form of the tinyurl domain and a random series of characters, such as https://tinyurl.com/yxtj4gft.

When the user clicks the link, their browser goes to the TinyURL website and is then provided the full link to follow, and redirects to that. The primary benefit was to make it easier to share the URL, even if it’s not so memorable, however the developers later added the ability to provide a custom redirect name and, as long as nobody else has nabbed it first, you can use it – eg https://tinyurl.com/yammerofficespace.

TinyURL has been overtaken by others, notably bit.ly, which Twitter switched to from having previously used TinyURL, and before later launching its own t.co. There are many others too, some connected with existing services – like the onedrive.com shortener (eg https://1drv.ms/u/s!AgMogCiKiWDFraIfifRzFKdjw4F1uQ?e=Yepjwh) which isn’t really very short, and which causes Bit.ly to get its Alans in a twist, as it seems it doesn’t like to shorten another shortener’s link.

There are some downsides to using this kind of service, potentially. What happens if the provider goes bust, or decides to start charging users where it was once free? Sites like Photobucket which started free but began charging users a “ransom” get internet warriors hot under the collar, but so far, sites like TinyURL and it’s progeny are mostly still free to use, with the operators selling aggregate data about the referrals being followed to fund their operations costs.

Some shorteners decide to close down – like goo.gl – meaning there’s a risk that previously-shared short URLs won’t work in future (though in the case of Google’s shortener, they are keeping old links alive, just not allowing any new ones to be created). Similarly, if a shortener has a technical problem or security breach, it could affect the way it works – TinyURL reportedly having problems just this week.

Finally, a web shortener that is unlikely to disappear overnight is operated by Microsoft, called aka.ms. Anyone from Microsoft can create an aka.ms shortlink – subject to some rules – as long as they share responsibility with someone else. Like the other public shortener services, can generate a random series of characters or can provide the “target” part of the link if they like.

All aka.ms links are by definition publicly accessible, but many are used to get access to sites that are for internal use, even though they exist beyond the firewall – Sharepoint sites, for example, or the intranet homepage, aka.ms/msw. Anyone could resolve the destination URL – even en masse as one enterprise developer has done, using Azure functions – but you still need to provide appropriate credentials to access the destination site.