By default, the Discourse forum software only auto-links standard web protocols (like http, https, and mailto) in forum posts. In order to support clickable-link non-standard custom protocol (e.g., unityhub:// or steam://), the forum administrator will need to add it to the allowed scheme (under Admin Path: Admin Settings > Security > allowed rich text schemes).
This is a request for non-standard URLs of the 3 main streaming services supported by dCS platforms to be added to the forum, namely;
qobuzapp://
tidal://
spotify://
This will allow posters on the “What’s Spinning…” threads to directly link to albums, for example: the following URLs will launch the respective Desktop (or Mobile) App directly into the selected Album (in this case Ryuichi Sakamotor’s “Sweet Revenge”)
Once the App is launched, the dCS Connect service can be selected to listen to the albums, all without having to manually launch the App and hunt for the album.
Great idea. My reservation concerns Qobuz where album URLs may relate to the individual services provided to each Qobuz territory. Hence the URL provided for e.g. the French service will not be appropriate for the, say, UK one ( if the album is available in both territories which is not always the case) . Of course you also need to be a subscriber to the correct service.
I wonder if we might see inappropriate link failure complaints?
That’s true Pete. If a certain album is not available in a particular geography, than the link will lead to an error. On the flip side, the user will know straight away, and not have to wonder why a manual search doesn’t show the album.
Note though, when available, a single album will always have the same code everywhere globally. I’ve actually physically verified this across multiple geographies. It’s also the basis for the Streaming service’s “Share” feature.
As for those getting an error when they click on a Streaming services link even when they don’t have a subscription to that particular service, well, we can’t cater to those who do illogical things (to put it politely)
ps:
Anyone can try it by the way, just paste the URL in a browser window and hit return, your Browser will ask for permission to launch the app the first time, but thereafter launch it automatically, give it a try - qobuzapp://album/okgqofkedrzdc
Simon, you have an inadvertent space between the “z” and “a” - another user error Also, if you don’t have Qobuz installed, of course it’s not going to launch.
Actually no, Google inserts the space if it isn’t present, but if I insist on the search as entered it still gives the same result. Interesting that it can find the album. And I do know a little bit about computers (that a program has to be installed to launch). I’ve sat in front of the darn things for about the last 40 years!
Exactly why native support for these custom URLs are useful, prevents copy/paste typos.
In fact, it even works down to individual tracks, not just an album. Again with a globally unique track ID that works across all geographies where the album is available;
For example:
qobuzapp://track/416397342
Is the track “If I Let You” from [the] new The Womack Sisters single.
Good shout Anup. I’ve enabled support for the Qobuz, Spotify and TIDAL URL schemes. These links now work correctly when inserted as hyperlinks.
Note that Discourse does not automatically convert raw custom-protocol URLs into clickable links, so you’ll need to create them as links using Markdown or the editor’s link function.
Also, if you don’t have Qobuz installed, of course it’s not going to launch.
