add support for discord:// protocols in buttons

[leElvyn]

Description

currently, if you try to create a button with a url, it has to use http or https as a url scheme.
However, discord implements the discord:// scheme, with urls such as discord://-/users/316860714260234243 or discord://-/settings/advanced. Everything that works with discord.com also works with that protocol, but whereas the discord.com link opens a new discord client in the browser, the protocol actually opens a user profile or a channel in the client.

The idea is to support the discord:// protocol in buttons links
Why This is Needed

It could be really useful if you could make a profile pop out of a button, link to a channel, or guide actions like opening the advanced tab of settings to activate developer mode.

Alternatives Considered

It is possible to use the links with https://discord.com instead of discord://-, but they open a new browser tab, instead of executing the action in the client.

Additional Details

currently, trying to send a button with a discord:// scheme returns 400 : Scheme "discord" is not supported. Scheme must be one of ('http', 'https').

[Antouto]

Also, please add support to the title url and author url in embeds :)

[viral32111]

I'd love this, something similar to Steam's browser protocol.

[c43721]

I plus this. Using this with the browser protocol would be AWESOME.

[nihaals]

Maybe it could also be added to the allowed hyperlink protocols? At the moment only http(s) and steam are automatically turned to links in messages

[AnotherZane]

Maybe it could also be added to the allowed hyperlink protocols? At the moment only http(s) and steam are automatically turned to links in messages

Buttons urls currently only supposed http(s) as the protocol. However, in a normal message content, you can use almost any other protocol by wrapping the uri in < >.

Eg. <steam://install/698780>, <com.epicgames.launcher://store/en-US/p/discord>, <calculator://1>, <ms-settings://notifications>, <dict://discord>.

These work fine on web/desktop and do seem to be intended behaviour by looking at these warnings before opening them:

vs

However, these do have a few limitations that I have found such as:

These uris do not work on phone (at least on android) as seen below.

They cannot seem to be used in markdown links - which I assume is due to security concerns, behaviour on desktop:

vs behaviour on phone (android):

The actual description of the embed sent above is [test](steam://open), this doesn't seem to work on desktop or phone and also breaks the markdown link formatting on phone. Can also confirm that sending a markdown link in the normal message content with a webhook also results in the exact same behaviour.

[sevenc-nanashi]

I love this.
I think discord://-/users/316860714260234243 is good for author in embed, and discord://-/settings/advanced is good for text like this:

How to get id:

1. Go Advanced setting(discord://-/settings/advanced)
2. Enable developer mode
   ...

[laGameTV]

I mean if its an embed you clould use "to turn off streamer mode click (here)[discord://...]"

[nihaals]

However, in a normal message content, you can use almost any other protocol by wrapping the uri in < >.

Thanks, had no idea that worked but it does the trick. I guess it's still a bit of a hack though, and if it was officially supported it probably wouldn't open a pop up and could be handled entirely in the client (it uses a standard URL open so if you don't have the protocol set up e.g. on Linux it doesn't work).

[ckohen]

Another thing to note, if this gets implemented, the client would need to not throw the user to the dms list when clicking any discord:// link that doesn't direct to a channel

[4Kaylum]

Something like this would also be a good shortcut to running certain commands; consider something like discord://commands/<APP_ID>/<COMMAND_ID>/<ARGS> - maybe just to fill in the chat box or maybe to run it directly.

[msciotti]

Support for discord:// in buttons was just merged, and should be deployed to our API shortly.

[typpo]

@Commandtechno - you're describing the old behavior, I'd wait for the change to be deployed anddiscord://-/foo will work just fine. There will be a note in ddevs when this happens :)

[advaith1]

what about discord:///foo? that doesn't work in <> in Discord currently, but it works in run

[ZhenjaMax]

I don't know where should I send answer, so I write it in suggestion and below your answer.

I'm try to create button with Steam URI for lobby link and I can't because

...node_modules\discord.js\src\rest\RequestHandler.js:349
throw new DiscordAPIError(data, res.status, request);
            ^
            
DiscordAPIError: Invalid Form Body
data.components[0].components[0].url: Scheme "steam" is not supported. Scheme must be one of ('http', 'https', 'discord').

What about to add some of these URI (or at least Steam, GitHub and all able to associate with Discord user from user's connections) ?

[erkinalp]

@msciotti Why not allow all URI schemes (with a client-side disclaimer stating URIs other than HTTP and Discord-scheme are not checkable server side)?

[dbauducco]

+1 from my current project. Trying to give the user the option to quick launch a related app by just clicking a button. Sad to see this is the only thing stopping me.

[Underpants-dev]

I think there are more protocols like discord://. I have tested other URLs on my iPhone SE gen 1 phone (iOS 15). They all redirect to a certain application instead of redirecting to a certain URL on a web browser.
For example:-

1. duolingo://- redirects me to the "Duolingo" application
2. While using twitter://- redirects me to the "Twitter" application.

All of them require a prompt of course.

[Underpants-dev]

Also, it only supports URLs having only one character in their app name.

[Chew]

Yes, these are called "Deep Links" and a lot of apps have it. It's rather useful.

[Slowftw]

I believe only ms-cxh and ms-cxh-full are blacklisted because of a windows bug, all others[1][2] are accepted in the msg content between <>

[dutchman-dev]

Why my discord:// button opens Discord developers app and not the main client?

[Susko3]

Your OS decides which app to open when a URI is opened. Check your default app settings, per URI/protocol.

[ssebastianoo]

...You shouldn't be using the Development Client in the first place? (It's unsupported, among many other reasons)

then why does discord let us use canary?

[GoldenAngel2]

...You shouldn't be using the Development Client in the first place? (It's unsupported, among many other reasons)

then why does discord let us use canary?

Discord Clients: Stable, PTB and Canary is officially supported.
Discord Client: Discord Development isn't supported and shouldn't be used.

[TwilightZebby]

...You shouldn't be using the Development Client in the first place? (It's unsupported, among many other reasons)

then why does discord let us use canary?

As GoldenAngel2 said, the Development client (with the black coloured icon) is separate/different from the Canary client (with the more orangey coloured icon)

[ssebastianoo]

...You shouldn't be using the Development Client in the first place? (It's unsupported, among many other reasons)

then why does discord let us use canary?

Discord Clients: Stable, PTB and Canary is officially supported.
Discord Client: Discord Development isn't supported and shouldn't be used.

oh, my bad, sorry

[RSNFreud]

@msciotti

Will this feature come to mobile devices?

[NovaFox161]

Its already in mobile. This was an API change to allow link buttons to use it, which has already been done. The custom discord:// scheme was already supported on mobile platforms.

It might throw you to a browser and then immediately back into the app (there's some bugginess I've seen doing my own app development) but the custom discord:// scheme has been supported on iOS and android well before this.

[RSNFreud]

Hey,

It seems to do nothing at all when you click it...

[Zoddo]

Could it be handled internally by the desktop and mobile apps (like links to messages) instead of relying on the system protocol handler?
This would give a smoother experience.

[InvalidLenni]

:soonTM:

[kavascriptos]

how to use?

[danthe1st]

just create a link button and set the URL to discord://...

[ZhenjaMax]

I'm try to create button with Steam URI for lobby link and I can't because

...node_modules\discord.js\src\rest\RequestHandler.js:349
throw new DiscordAPIError(data, res.status, request);
            ^
            
DiscordAPIError: Invalid Form Body
data.components[0].components[0].url: Scheme "steam" is not supported. Scheme must be one of ('http', 'https', 'discord').

What about to add some of these URI (or at least Steam, GitHub and all able to associate with Discord user from user's connections) ?

[erkinalp]

Even better alternative: Allow using any URI handler scheme in buttons.

[Sixboy17]

java -Dprefix="!" -jar JMusicBot.jar

[benxutech]

Note that users will get the "may open an application on your computer" warning after clicking the link button when using the discord:// protocol. I understand this is for security reasons (there's no way to guarantee discord:// will link to the discord app), but it's a bit unfortunate that the user can see the URL filled with scary numbers unlike in Chrome for example which only opens a prompt.

Also, for others in the future who stumbled upon this question, the URI for linking to a channel is this: discord://-/channels/<guild-id>/<channel-id>

[KevinNovak]

This still does not work in link markdown correct?
Ex: [My Profile](discord://-/users/212572875793234272)