Support Custom Game URIs iOS and Android

[dduleone]

Native apps have the ability to create custom hyperlink protocol schemes, to allow rich linking to their app content.

Some games, such as http://lordsandknights.com/ use custom schemes like l+k://player?1234&1234

Other apps recognize these URLs, enable them to be activated, and then open the associated URL. I am trying to get my alliance to use Discord, but we are unable to get our game links to be recognized as URLs.

Can this feature be added?

[dduleone]

To be clear when trying to use these URLs in embeds, I get errors like this:

(node:71467) UnhandledPromiseRejectionWarning: DiscordAPIError: Invalid Form Body
embed.url: Not a well formed URL.

I'm not sure if this issue is solely with the API or the client. But it would seem the API must change, at least, since it is rejecting the embed outright.

[Lachee]

I variant of this issue has been reported in #450, where they requested access to endpoints other than http and https for oAuth2 redirection. I suppose this can be expanded to also include hyperlinks within text. The desktop client already supports this (probably accidentally tho).

To quote @night :

The only current methods you have for mobile apps is to use the authorization code grant with a server or use the implicit grant without a server (which does not support refreshing). In both of these methods you can use an in-app webview to grab the authorization code or access token off the redirect url.

It's worth noting that this is a "best practices" RFC, which is not an adopted standard nor is something we have to be in compliance with. Support for these new best practices may happen at some point in the future if they become adopted, but as of right now none of the upstream OAuth2 libraries we use support PKCE, which is necessary to move native clients off of using client secrets.

[dduleone]

I don't believe that's the same issue. That has to do with oauth flows. This is just hyperlinks in messages.

[msciotti]

Seems like a valid request 👍

[night]

You can link any URL already with markdown syntax: <l+k://player?1234&1234>. Additionally, this repo is only for requesting API features, not client features.

[LikeLakers2]

@night Pretty sure this is an API feature request, given the way they intend to use the link.

[dduleone]

I just confirmed, the <l+k://player?123&123> syntax does work. But it creates a link to this url: http://l+k//player?123&123.

[lukeeey]

I think this needs to be reopened.

[h1nk]

Additionally I'd like to note the API prevents non-HTTP protocol link handlers in markdown embeds for bots. Valid markdown to a URL such as [link text](steam://connect/...) yields no link in the embed. I see it was requested to allow such hyperlinks in the Discord client but the API does not allow doing so in embeds (as someone commented in the feedback thread here: (original post deleted during migration from old feedback forum) (new re-submission of the same issue on new forum). Also if you try to set the embed url? field to a non-HTTP URL its value is ignored entirely and the embed title is created without the link.

[msciotti]

Hey all. We had some internal confusion with this request, and it was closed invalidly. Our bad. We'll re-open this.

I don't have a good estimate of when we could do this, as there's a lot of edge cases and security questions to handle, and this code has a lot of touch points. But we're tracking it!

[kpontussvensson]

Any news on this?