physicsCamera
Member
Seriously, we need it. Will it ever be added?
When will we get Discord RPC?
- Thread starter physicsCamera
- Start date
PencilVoid
Circuit Enthusiast
That's a shame. Rich Presence would have been a neat feature.
Viral licenses are a crock of shit anyway. It puts horrendous restrictions on what you can use in your software. It's fine in the fact that you have to open-source your modifications but having to only use libraries that are also compatible with its incredibly restrictive terms just hinders development - like with the above.
I believe you can sidestep it by writing a GPL shim or something like that, and perhaps shipping with a stub DLL that can be swapped out?
However it's also worth noting that Discord RPC is just not being added to any more, the RPC mechanism is still going to work for the foreseeable future as per the below. So you can still use DiscordRPC as it's MIT.
https://github.com/discord/discord-rpc/issues/290
Last edited:
Hi! Just saw this thread, thought I'd shed some light on it. I made a fully-working implementation of Discord RP for SRB2Kart right a couple months before its release. It showed you the person's character, the level they were on, the game type, even going as far as letting you join the person's server if they were on a public one.
I don't think it's as black & white as anyone here has said. The issue was actually just about how it was a huge grey area, so it's been left in a bit of a limbo. I couldn't figure out if we were allowed to push the Discord Application ID/Client ID to the codebase. Being able to freely provide it and let anyone who compiles use our Client ID would be most ideal, but I couldn't find anything on if that was allowed or not, and I couldn't get an answer from Discord Support on that front. I saw documents saying that you couldn't hand out your Client Secret, another ID that's meant to be handled extremely carefully; however, we weren't using that. There was no solid verdict on the Client ID.
If we weren't allowed to freely give the Client ID in the source code, I also couldn't figure out if not including it would violate the GPL license. Last time I researched it though I was leaning more towards "it's not allowed", though.
If anyone can give me examples of other open-source Discord applications in a similar situation to ours, then I absolutely would resurrect the branch in a heartbeat and put it in the next SRB2Kart patch :)
I don't think it's as black & white as anyone here has said. The issue was actually just about how it was a huge grey area, so it's been left in a bit of a limbo. I couldn't figure out if we were allowed to push the Discord Application ID/Client ID to the codebase. Being able to freely provide it and let anyone who compiles use our Client ID would be most ideal, but I couldn't find anything on if that was allowed or not, and I couldn't get an answer from Discord Support on that front. I saw documents saying that you couldn't hand out your Client Secret, another ID that's meant to be handled extremely carefully; however, we weren't using that. There was no solid verdict on the Client ID.
If we weren't allowed to freely give the Client ID in the source code, I also couldn't figure out if not including it would violate the GPL license. Last time I researched it though I was leaning more towards "it's not allowed", though.
If anyone can give me examples of other open-source Discord applications in a similar situation to ours, then I absolutely would resurrect the branch in a heartbeat and put it in the next SRB2Kart patch :)
Last edited:
FishandChips
When was the last time I logged in?
Minecraft Java uses Java and Open GL and it has the Discord SDK. So I guess it could work?
EDIT: It uses it barely though. It's just a verified game.
Last edited: