can somebody help me understand how authentication for the rpc api works?
its probably using oath?
The documentation on the build tools is highly outdated
node 10 is recommended and latest npm
There are also local development dependencies for each system that are required, like xcode, msvs, etc
building on windows is probably the worst experience, as I recently discovered
@Nithindanday Are you talking about the playbackApi? its just a generated code
Given the fact that their PR they used of mine is for Discord-RPC.
Discord Rich presences is done locally and is all behind the scenes. Theres nothing you really need to change for it to work.
holy moly. huge shoutout to @jostrander . i had tried the latest node. the node on the documentation and a few random variants and couldn't get anywhere. node 10 was the trick.
hey all, I ran npm run make:deb, and it seems to have succeeded. However, I don't see any built binaries. Where do I find those?
I dont see a dist/ folder
sorry don't understand what does that mean?
@devksingh4 i mean, that yes, if you run make:deb:64, the binaries packages are in /dist/installers
Yeah ik it should go there, but its not. The dist folder is not created or anything
any idea why the ui is so sluggish?
I'm literally waiting 1-3 seconds for the button I clicked to have the action performed(i.e. pause, skip song, show playlist)
I have some problems with the hotkeys, I can't get the in app keyshortcuts to work, well they work partially, and only when that window is focused. Also when I press next song media button, it skips the next song too.