- Feature Description: When a user signs up to Fuze.tv (and logins with discord) we’d like to offer him to follow his friends (discord friends) who are already on the Fuze.tv platform, for that we need to know who his discord friends are (user id, username, discriminator, email).
- impact for my app: [low, mid, high, show-stopper]. low (this test might have big positive impact on our engagement)
- What is your current pain point? We can’t get this list on our own by using discord’s relationship API without making the end user to login to discord one more time (since he is already logged in with OW’s developer key).
- What do you have in mind to solve it? 2 options: Having Overwolf implementing https://discord.com/developers/docs/game-sdk/relationships OR finding a way in which Overwolf would allow us to access discord api with the same developer api key it uses.
Hi, and thanks for the feedback.
We will discuss the matter internally, and we will update you here.
It might take up to a few days.
We added this feature request to our backlog.
We don’t have an ETA, though, and that can take some time to implement and release. Thank you for your patience.
We will update you here once it is ready.
@eransharv as we are striving to get with this feature to production in a shortest time possible, is there a chance you could expose the discord client object (of the discord SDK) that you are using to make all the corresponding requests to discord API? This way we could communicate with discord ourselves not asking you to make us a facade for any method available in the Discord API.
The con here is clear, developers making calls to discord API with Overwolf’s Discord API key is not optimal, however I’m not sure what is the current level of thresholding or limitation heuristics applied on the existing calls to discord, so maybe it’s not unprecedented if there are little or none.
Another approach that could help us a lot, is for every developer (optionally) pass his own Discord API key when making calls to Discord via Overwolf’s API, this way we could use existing Overwolf’s implementation and on top of that create in our own code an instance of the Discord API client and make additional calls that are not implemented by Overwolf, without asking the user to authenticate again with Discord. That way it’s a win win, since we use Overwolf’s implementation without using Overwolf’s Discord API key as described in the paragraph above.
It would mean the world to us if one of the proposed above can be considered for soon releases.