Can't get Spotify's rich presence to work

[TigercatX]

Acknowledgements

• I have checked that there is no other issue describing the same or
  similar problem that I currently have, regardless if it has been
  closed or open.

• This bug affects Discord website.

• This issue is confirmed to be reproducible when WebCord is packaged
  on at least all three latest supported Electron major releases.

• This issue is reproducible in Chrome, Chromium or any
  Chromium-based browser, e.g Brave or Edge (please write in
  Additional Context which browser you have used if it is neither
  Chrome nor unmodified Chromium).

• There are no fixes done to master which resolves this issue.

• My issue describes one of the unstable and/or not fully implemented
  features.

• I have found a workaround to mitigate or temporarily fix this issue
  in affected releases (please write it in Additional context section
  below).

Operating System / Platform

🐧️ Linux

Operating system architecture

x64 (64-bit Intel/AMD)

Electron version

32.0.1

Application version

4.10.1

Bug description

My spotify's status won't appear when using Webcord. It works only if I start both Discord (from the application or from the web) and Webcord. I have added my spotify account to Discord and enabled "Spotify" in Webcord's privacy options but nothing seems to happen.

Additional context

I'm running Ubuntu 24.04LTS with X11.
I'm using spotify from Brave (but I don't think this can be the cause of the problem since it works in Discord client and web-app)

[SpacingBat3]

There's no yet a Discord presence support; I need more details on whenever DisConnection is implementing it the right way (tests, tests, tests!) and maybe more capture data in the future. There's also a need for implementing Discord-alike errors and handling a few more stuff in IPC implementation, finding out more what does what in clean way (without examining Discord's limited JS code).

Overall, this has to be closed as somewhat invalid report and falls to issue ticket #292. I'll close this and lock conversation, please continue further on this issue ticket if there's any need for any meaningful on-topic conversation.