Signal's new(ish) URI Scheme


A padlock engraved into a circuit board.

A few years ago, I idly wondered "Whatever happened to URI Schemes?". Older communications protocols didn't rely on http. You can use mailto:me@example.com to send email, sms:+447700900123 to send a text message, and skype:terence.eden to use Skype. There are dozens of these sorts of protocols. But modern apps seem to prefer making everything an https: link. That way, if the user doesn't have the app installed on their phone, they get taken to a friendly landing page - rather than seeing an…

Continue reading →

Page numbers aren't the answer


The PDF file icon with a big red line through it.

There's a new pre-print paper called Pinpointing the problem: Providing page numbers for citations as a crucial part of open science by Leon Y. Xiao and Nick Ballou. It's a short, easily understandable paper, and well worth a read. I think I disagree with nearly all of its conclusions! The main point, I agree with. Citing a whole paper is a lossy process. Saying "Smith, J (1963) Practical Time Travel, Gallifrey Press" is basically fine but it doesn't tell you where in the publication the bit…

Continue reading →

Never use a URL shortening service - even if you own it


Screenshot showing a 404 error on the Guardian's website.

The Guardian launched its online adventures back in 1999. At some point, they started using the name "Guardian Unlimited". Hey, the dot com boom made us all do crazy things! As part of that branding, they proudly used the domain GU.com Over time, the branding faded and GU.com became a URL shortening service. Tiny URls like gu.com/abc could be printed in papers, sent via SMS, or posted on Twitter. They made a huge fanfare about how it would help with analytics. You can read some of the history …

Continue reading →

Konami Code Domain Name


Glowing computer text showing dot com dot info etc.

More on my experiments with silly Punycode domain names. http://↑↑↓↓←→←→ba.tk/ Yup, copy and paste that into your browser and it will resolve. (more…) …

Continue reading →

Facebook Mangles Unicode URLs


Facebook rewrite URLs with Unicode in the path - this is not best practice and could be dangerous. It is possible to create a URL like http://bit.ly/😀 - the Unicode characters are valid in the path. The URL Encoded representation is : bit.ly/%F0%9F%98%80 Facebook mangles these URLs in such a way that it might be possible to redirect a user to a malicious site. Here's what's happening. When Facebook sees the "😀" character in text, it rewrites it to the "󾰀" character (󾰀). That's a …

Continue reading →

The Perils of URL Shortners


I'm not a big fan of URL shortners - bit.ly, t.co, goo.gl, ow.ly, etc - I understand the need for them, but they seem to offer a fairly poor service in terms of privacy and usefulness. Take this recent example from Vodafone. Aside from the obvious downsides (user doesn't know where the link will take them, if it's compatible, link looks like gobbledegook, etc) there is a rather more interesting issue. Goo.gl - along with many other URL shortners - give everyone access to your statistics. …

Continue reading →

Expanding URLs in Dabr / Twitter


I hate shortened URLs with a passion.  It makes it hard to see what a link is and whether I've visited it before.  If they fail - like tr.im threatened to do - you lose your links with no way to see where they once went. So, hurrah for LongURLPlease - a service which takes those horrid little links and turns them in to full sized URLs. Here's the basic code in PHP to use the service. function long_url($shortURL) { //Use the LongURLPlease API $url = "…

Continue reading →