Signal's new(ish) URI Scheme
signal url · 5 comments · 350 words · Viewed ~1,269 times.
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 error message.
The Signal messaging app launched signal.me URls for this purpose back in 2021. It allows you to share a link like https://signal.me/#p/+447700900123 and have your signal client open up a chat with that person.
Then, towards the end of 2022 they added support for their own scheme! sgnl (although it doesn't appear to have been submitted as an IETF draft, and isn't listed on IANA).
It has exactly the same layout as it's https sibling: sgnl://signal.me/#p/+447700900123
Of course, not everyone has (or wants) a phone number. So Signal are adding support for usernames.
Sadly, they've taken the same xenophobic attitude as GitHub and insist that only good ol' American letters and numbers can be used. No fancy accents, right-to-left languages, or Korean Hangul.
Nevertheless, it will be interesting to see if this prompts a surge in Signal take-up. Especially important as Signal are dropping SMS support
web+*. Some example apps that use it: https://developer.chrome.com/fugu-showcase/?api=protocol-handlers. URL protocol handler registration for PWAs - Chrome DevelopersMore comments on Mastodon.