AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Features

Edit history

Earlier versions of RPC/Activity via Servers/Serverless, newest first.

Current version | Edited by Rex
Changes
If this _is_ intended to be supported, having a documented pattern or recommended approach (maybe a token‑scoped endpoint, app‑level credentials, etc.).Removed: ### Notes (optional)Removed: Removed: _No response_Removed: Removed: ### ChecksRemoved: Removed: - ☑ I searched for existing discussions and didn't find a duplicate.Removed:
Show

RPC/Activity via Servers/Serverless

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.).
Edited by Rex
Changes
### ProblemRemoved: Currently RPC and Activity is in the [roadmap](https://blog.fluxer.app/roadmap-2026/) and also discussed [here](https://github.com/orgs/fluxerapp/discussions/319).Added: Currently RPC and Activity is in the [roadmap](https://blog.fluxer.app/roadmap-2026/) and also discussed [here](https://feedback.fluxer.com/p/927).However, I haven’t seen clarification on whether server‑side or serverless‑originated activity updates are intended to be supported.
Show

RPC/Activity via Servers/Serverless

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.).

Notes (optional)

No response

Checks

  • ☑ I searched for existing discussions and didn't find a duplicate.
Original by Rex
Show

RPC/Activity via Servers/Serverless

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.).

Notes (optional)

No response

Checks

  • ☑ I searched for existing discussions and didn't find a duplicate.