Problem
Currently RPC and Activity is in the
roadmap and also discussed
here.
However, I haven’t seen clarification on whether server‑side or serverless‑originated activity updates are intended to be supported.
My use case is: a web app (
HTMLPlayer (beta)) sends some state to a backend (or serverless function), and that updates my Fluxer activity.
Will this be supported?
I’m mainly asking because Discord explicitly forbids RPC from external servers unless you have special permission, and I would love it if Fluxer supported it via server.
Proposed solution
Clarify whether server/serverless‑originated activity updates are permitted, and if so, what constraints or auth model they should follow.
If this
is intended to be supported, having a documented pattern or recommended approach (maybe a token‑scoped endpoint, app‑level credentials, etc.).
Comments
No comments yet.