SYNK Music Discord RPC

This is a simple tool that connects SYNK Music to your Discord profile, so your friends can see what you're listening to in real-time.

Status

WIP - honestly it's pretty new, so there are probably some bugs. If it breaks, it breaks. Make a issue on here if you feel like it's a serious issue, or make a PR if you think you can fix it.

How do I get the SYNK Music RPC?

At the moment there's 2 ways of getting the SYNK Music RPC.

1: Build it from source (recommended)

1. Get Rust

You need Rust on your machine to run this. Just run this in your terminal:

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

(If you're on Windows, just grab the installer from rustup.rs). Restart your terminal after you're done.

2. Run it

Download the project, open the folder in your terminal, and run:

cargo run --release

Then just open SYNK Music in your browser, and it should connect automatically.

2: Download the pre-compiled version from the releases.

Head over to the Releases page and grab the latest .exe. No Rust required, just download it, run it, and you're good to go.

Usage

1. Make sure Discord is open and running.
2. Open SYNK Music in your browser and start playing something.
3. Run the RPC tool (however you installed it).
4. That's it, your Discord status should update automatically.

Custom port

If port 19836 is already in use, you can change it:

synkmusic-rpc -p 19837

If you change the port here, you'll also need to change the default websocket port on the website. Go to Profile Picture > Settings > Privacy and Social > RPC Websocket Port and set it to the same port.

FAQ

Is this a virus?

No. If you don't believe us then you can check the source code for yourselves, it's all right here. You can also build it yourself on your own computer if you want to be 100% sure. See the build from source section above.

Why isn't my status showing on Discord?

Make sure you've got Activity Status enabled in Discord. Go to Settings > Activity Privacy and turn on "Share your activity status". Also make sure Discord is actually running before you start the RPC, it can't update your status if there's nothing to connect to.

Update: If you are using a chrome based browser it might ask for permissions to "see other devices on your nework". If you do not allow this, the RPC will fail to connect to the RPC running locally. You can read more about this at the official Chrome Developer Blog.

Contributing

PRs are welcome! The codebase is pretty small so it shouldn't be too hard to find your way around.

Before you start:

• Small fixes (typos, minor bugs, etc.) - just open a PR, no need to ask first.
• Bigger changes (new features, refactors, etc.) - open an issue first so we can have a chat about it before you sink time into it.

AI-generated code

We follow a similar rule to what the Linux kernel does. You're welcome to use AI tools (Copilot, ChatGPT, Claude, whatever) to help you write code, the same way you'd use any other tool. However:

• You are fully responsible for everything you submit. If it's buggy, breaks something, or has licensing issues, that's on you, not the AI.
• You must have actually reviewed and understood the code. Don't just paste AI output into a PR without reading it.
• Do not credit AI as a co-author. AI is a tool, not a contributor. No AI co-author tags, no AI sign-offs.
• Low-effort AI-generated PRs will be rejected. If it looks like you've just dumped a prompt into ChatGPT and submitted the output without any thought, it's getting closed.

In short: use AI if it helps, but own your code.

License

MIT, do whatever you want with it.