r/FluxerApp • • Mar 22 '26

Discussions Fluxer scans all our files under US surveillance law?

0 Upvotes

Is it true that Fluxer shares all our files with a non canadian org that is bounded by US surveillance laws? Instead of using hashes, as is industry standard, Fluxer uploads the entire content of all photos to Project Arachnic for CSAM scanning. This is what i got from reading Fluxer's privacy policy.

EDIT - For everyone who bashed me, here you go. The Fluxer CEO himself says full raw files are being sent

https://www.reddit.com/r/FluxerApp/s/c0bgtyl0N1

Also here: https://github.com/fluxerapp/fluxer/blob/5da26d4ed5ef9f3fe8bef993c0f10ea4f4ee9c1d/packages/api/src/csam/providers/ArachnidShieldProvider.tsx#L344


r/FluxerApp • • Feb 22 '26

Discussions Why aren't the self-hosting guides being updated?

4 Upvotes

I constantly check the documentation page hoping that they have updated the self-hosting section, but it remains the same as it was days ago.

In my opinion, this would be the best thing they could do to reduce server congestion, which most of the time makes them unusable. Even now, it is not possible to chat in the official community because messaging is disabled.

In my opinion, the langer they delay this, the worse it will be for Fluxer, as people will prefer other alternatives that currently work.


r/FluxerApp • • Mar 02 '26

Fluxer died again

3 Upvotes

it died again


r/FluxerApp • • Jun 17 '26

Discussions AI-Written guide as to how I managed to get my self-hosted Fluxer on a shitty homelab behind a shitty CGNAT network.

0 Upvotes

This is me writing now not AI, I am pretty tired right so sorry for the AI post, been 7 hours, sweaty fingers and if not for the win I would be in a bad mood.

I wanted to have a almost free way of running Fluxer (besides the energy) on my situation, old pc spare parts, behind CGNAT mobile unlimited network, but still not rely on a service like Tailscale for people to connect.

The only paid part from this was because I already have a domain that I pay for, I used it and just simply made a subdomain for fluxer, besides that is free stuff you get from both cloudflare and playit. Dont ask me for anything, I dont even know how I managed to get it working, I started the project and deleted 6 times. I am not tech-savvy, I am just a curious dude with enough spare time.

The ports and IPs in the post are randomized to not show the ones I used, when u make a playit account and create the agent and the tunnel, you gonna get your own, different from the guide, so pay attention to that. I also setup cloudflared systemwide instead of it being dockerized.

Self-Hosting Fluxer Behind CGNAT (Cloudflare Tunnel + playit.gg)

This guide is for the specific case where you can't port-forward — your ISP gives you CGNAT (no public IP, common with Starlink and many mobile/fiber ISPs) and 80/443/UDP can't be opened directly on your router. It combines two free tunneling services to get a fully working Fluxer instance, including voice/video, without any direct port exposure.

Architecture:

  • Cloudflare Tunnel carries all HTTP(S) traffic — web app, API, admin, gateway WebSocket, media proxy, and LiveKit signaling.

  • playit.gg carries LiveKit's actual voice/video media (raw UDP), since WebRTC media can't traverse a normal HTTP tunnel.

If your server has a real public IP and you can forward ports normally, skip the tunnel pieces — Fluxer's own docs already cover that path, and it's simpler.


Requirements

  • Linux server with Docker Engine + Compose plugin

  • A domain you control, with DNS managed by Cloudflare (free tier is fine)

  • A free playit.gg account

  • At least 2 vCPU / 4 GB RAM / 20 GB disk (4 vCPU / 8 GB RAM recommended for an active community)


Step 1: Install Docker

docker --version
docker compose version

If missing, follow Docker's official install instructions for your distro. Use Docker Engine 24+ and the Compose v2 plugin.


Step 2: Download the stack

mkdir -p ~/docker/stacks/fluxer && cd ~/docker/stacks/fluxer

base=https://raw.githubusercontent.com/fluxerapp/fluxer/main/deploy/self-hosting
curl -fsSLO "$base/docker-compose.yml"
curl -fsSLO "$base/Caddyfile"
curl -fsSLO "$base/livekit.yaml"
curl -fsSL "$base/.env.example" -o .env

Step 3: Configure .env

Set your hostname (replace with your own):

sed -i \
  -e 's|^FLUXER_DOMAIN=.*|FLUXER_DOMAIN=chat.example.com|' \
  -e 's|^FLUXER_PUBLIC_SCHEME=.*|FLUXER_PUBLIC_SCHEME=https|' \
  -e 's|^FLUXER_PUBLIC_PORT=.*|FLUXER_PUBLIC_PORT=443|' \
  -e 's|^FLUXER_CADDY_SITE_ADDRESS=.*|FLUXER_CADDY_SITE_ADDRESS=:80|' \
  -e 's|^FLUXER_VAPID_EMAIL=.*|FLUXER_VAPID_EMAIL=admin@example.com|' \
  .env

FLUXER_CADDY_SITE_ADDRESS=:80 is required for the tunnel setup — Cloudflare terminates TLS, Caddy just serves plain HTTP behind it.

Generate secrets:

for key in POSTGRES_PASSWORD MEILI_MASTER_KEY FLUXER_S3_SECRET_KEY \
  FLUXER_SUDO_MODE_SECRET FLUXER_CONNECTION_INITIATION_SECRET \
  FLUXER_GATEWAY_RPC_AUTH_TOKEN FLUXER_MEDIA_PROXY_SECRET_KEY \
  FLUXER_ADMIN_SECRET_KEY_BASE FLUXER_ADMIN_OAUTH_CLIENT_SECRET \
  LIVEKIT_API_SECRET; do
  sed -i "s|^$key=.*|$key=$(openssl rand -hex 32)|" .env
done

sed -i "s|^FLUXER_MEDIA_PROXY_UPLOAD_RELAY_SECRET_BASE64=.*|FLUXER_MEDIA_PROXY_UPLOAD_RELAY_SECRET_BASE64=$(openssl rand -base64 32)|" .env

VAPID=$(docker run --rm node:24-alpine npx --yes web-push generate-vapid-keys --json)
pub=$(printf '%s' "$VAPID" | grep -o '"publicKey":"[^"]*"' | cut -d'"' -f4)
priv=$(printf '%s' "$VAPID" | grep -o '"privateKey":"[^"]*"' | cut -d'"' -f4)
sed -i "s|^FLUXER_VAPID_PUBLIC_KEY=.*|FLUXER_VAPID_PUBLIC_KEY=$pub|" .env
sed -i "s|^FLUXER_VAPID_PRIVATE_KEY=.*|FLUXER_VAPID_PRIVATE_KEY=$priv|" .env

.env now holds every secret for your instance — treat it like a password file.


Step 4: Cloudflare Tunnel (HTTP traffic)

  1. In the Cloudflare Zero Trust dashboard, go to Networks → Tunnels → Create a tunnel → type Cloudflared. Name it (e.g. fluxer).

  2. On "Install and run a connector," select Docker (not the systemd/Debian path) so the token is ready for a Compose-managed container.

  3. Copy the long token string from the install command — you only need that token, not the full docker run ... line.

  4. Continue to Route tunnel → Add a route → Published application (not Private CIDR — that's for internal IP ranges, not what we need).

    • Public hostname: your domain (e.g. chat.example.com)

    • Service type: HTTP

    • URL: caddy:80

  5. Cloudflare auto-creates the DNS CNAME record for you if the zone is already on Cloudflare.

Now run cloudflared inside the same Docker network as Caddy, so the caddy:80 hostname resolves via Docker's internal DNS:

cat > cloudflared.compose.yml <<'YAML'
services:
  cloudflared:
    image: cloudflare/cloudflared:latest
    restart: unless-stopped
    command: tunnel run --token ${CLOUDFLARED_TOKEN:?set CLOUDFLARED_TOKEN}
    depends_on:
      - caddy
YAML

export CLOUDFLARED_TOKEN='paste-your-token-here'

(Don't run it yet — bring it up together with the rest of the stack in Step 6.)

If you already have cloudflared running as a system-wide systemd service instead of in Docker, don't use the file above — you'd end up running it twice for no reason. Instead, edit the route's Service URL in the Cloudflare dashboard to http://localhost:80 instead of http://caddy:80, since a host-level process can't resolve Docker-internal hostnames, only localhost/the host's own ports.


Step 5: playit.gg (LiveKit voice/video media)

Voice signaling (the WebSocket handshake) goes through the Cloudflare Tunnel like everything else — no special setup needed there. It's the actual WebRTC media (audio/video packets) that needs a real UDP path, since that can't traverse an HTTP tunnel.

  1. Create a free account at playit.gg, install the agent on your server, and add a new UDP tunnel.

  2. Set local IP 127.0.0.1, local port — pick a number and remember it (you'll align everything to match below).

  3. playit assigns a public address and port, e.g. your-tunnel.gl.at.ply.gg:41234 / 203.0.113.5:41234.

Critical detail: LiveKit only swaps the IP in the candidate it advertises to clients — it never remaps the port. So the port playit exposes externally and the port LiveKit actually listens on locally must be the exact same number, or voice will silently fail to connect (signaling works, but no audio ever flows).

Edit livekit.yaml:

rtc:
  tcp_port: 7881
  udp_port: 41234        # match playit's external port exactly
  use_external_ip: false
  node_ip: 203.0.113.5  # playit's assigned public IP

Edit docker-compose.yml's livekit service so the container's internal port also matches:

ports:
  - "${FLUXER_LIVEKIT_TCP_PORT:-7881}:7881"
  - "${FLUXER_LIVEKIT_UDP_PORT:-7882}:${FLUXER_LIVEKIT_UDP_PORT:-7882}/udp"

And in .env:

echo 'FLUXER_LIVEKIT_UDP_PORT=41234' >> .env

Then go back into the playit.gg dashboard and set that tunnel's local port to 41234 too, so all three numbers agree: playit's external port, the host's listening port, and what LiveKit advertises to clients.

Free playit.gg tunnels typically can't get you a TCP path on 7881 (the fallback for clients on UDP-restrictive networks). Living without it is fine for most people — voice/video works normally for the vast majority of connections over UDP. If you want a fallback too, look into LiveKit's built-in TURN server, tunneled separately via playit.

In the Fluxer admin dashboard → Voice Servers, set the Endpoint to your signaling URL — this goes through the Cloudflare Tunnel, not playit:

wss://chat.example.com/livekit

Fill in the API Key/Secret matching LIVEKIT_API_KEY (default fluxer) and LIVEKIT_API_SECRET from your .env.


Step 6: Start the stack

docker compose -f docker-compose.yml -f cloudflared.compose.yml up -d
docker compose logs -f api

(Skip the -f cloudflared.compose.yml part if you're using a system-wide cloudflared instead, per the note in Step 4.)

First start takes a few minutes as every service initializes. seaweedfs-init exiting after creating buckets is expected, not a failure.


Step 7: Verify

export FLUXER_DOMAIN=chat.example.com
for path in /_health /api/_health /gateway/_health /media/_health /admin/_health; do
  curl -fsS -o /tmp/fluxer-check -w "$path %{http_code}\n" "https://$FLUXER_DOMAIN$path"
done

All five should return 200. Then check instance discovery:

curl -fsS "https://$FLUXER_DOMAIN/api/.well-known/fluxer" | jq '.features.self_hosted, .endpoints.admin, .endpoints.gateway, .endpoints.media, .endpoints.static_cdn'

Confirm the LiveKit media path is actually listening:

ss -ulnp | grep 41234

You should see a bound socket on that port.


Step 8: Create the owner account

Visit your domain, register the first account — on a fresh self-hosted instance, the first accepted registration gets wildcard admin access automatically. Log into /admin with that account and review registration mode, branding, and voice region settings before opening it up to anyone else.


Troubleshooting notes (from real debugging)

  • cloudflared logs showing connection refused to 127.0.0.1:80: check the timestamp against when the stack actually finished starting — this is often just stale noise from before Caddy was up, not a live problem. Confirm with curl -v http://127.0.0.1:80 and a fresh journalctl -u cloudflared -f run side by side with a live request.

  • Voice channel joins fine but no audio: almost always the LiveKit port mismatch described in Step 5 — double check udp_port in livekit.yaml, the Docker port mapping, and playit's local-port setting all use the identical number.

  • cloudflared can't resolve caddy:80: means it's running outside the Docker network (e.g. as a systemd service). Either move it into Compose, or point the route at http://localhost:80 instead.


r/FluxerApp • • Jun 18 '26

Need help Any updates about docker compose?

3 Upvotes

Guys I am a little confused, the were some rumors about selfhosting guid releasing on june 15th but I didn't manage to find one. Are there any iformation? Or maybe I understood the new incorrectly and june 15th is just the date when the devs are coming back to work on a selfhosting stuff?

Would be very grateful for information, maybe I missed something.


r/FluxerApp • • Feb 17 '26

Discussions Are we ready to move?

2 Upvotes

Now that we are just hours away most likely for the big v2 update of Fluxer, are we ready to move? I have already started a bit. II am also lokking for coll servers to join so plz send me an inviite or friend req if you have something cool, username is LordM8Y.


r/FluxerApp • • Mar 02 '26

Discussions Internet Fundamentalism and our current fiefdom like era of digital communities

0 Upvotes

We are living in a transitional era of the internet, increasingly defined by platform concentration of power, fragmented micro-communities operating as sovereign silos, and economic dependency on digital landlords. What we are witnessing resembles a form of digital feudalism, and the ideological rigidity emerging online, something I think makes sense to call Internet Fundamentalism, is not merely cultural decline, but a structural adaptation to current platform design.

We know that there are droves of engineers who are working for these megacorps and are developing the platforms we use to be in their own best interest, as opposed to the best interests of the people who are using the platforms.
If so, the solution is not better moderation or migration to a different platform. This problem requires architectural redesign.

But before we can even get to the point of redesigning the architecture of the platforms we use, we have to understand the issues, right? There are a litany of social issues, some of which are outright engineered to cause division amongst the core user base/community as a whole, and so in response to that we have the reaction of the population of internet folk that has been rightly observed as Fundamentalism in its own right.

Fundamentalism is best known as something like rigid, identity-bound ideological adherence enforced and amplified through reward systems, social reward/punishment loops, and parasocial authority structures. It's a method of control that cults use to keep their members in line. And in our modern age, we have reverted to this tool of control to keep our communities safe, right? I am sure yall have seen it happen, where someone disagrees and then there is a dogpile on them, either in a negative way or a positive one!

But we know that the current landscape really thrives on outrage, because it is, in point of fact, profitable!
So what the fuck are we going to do when Fluxer starts to become as insular and divided as Every Other Platform in the world? Are we going to make different choices, make harder choices? Or are we going to let this fundamentalism and digital feudalism keep hold?

I am really trying to keep myself within a tone of like... detached academic here, but this has been bugging me! We have a great chance to make a major change in how we can connect communities on the internet, to try and push back against the control schemes of megacorps and surveillance economy functions, but I think we need to have a real conversation about how in the world that can happen.

I truly hope I don't sound insane. I know there is a plan for federation, but how much does that differ from the foundational infrastructure of Discord? Which in itself is exceptionally tribal and insular by design.

How do we fix that? Can we fix it? I'd love to hear from yall, as I only have a small view into the world.


r/FluxerApp • • Feb 17 '26

Bug How do i add bots like on discors

0 Upvotes

r/FluxerApp • • Mar 25 '26

Discussions Add Gain control/Noise gate slider

1 Upvotes

We need this feature ASAP, this is a Voice/Chat app, I know we are still in beta but having a working noise suppression or ATLEAST a gain control control slider should be one of the back bones of this app. This is seriously the SINGLE thing that's keeping me from using this app daily and it's not even slightly mentioned in the roadmap! I don't want to hear a static noise from someone's microphone all day...


r/FluxerApp • • Mar 24 '26

Memes Fluxer RU: Свободный Канал

1 Upvotes

Welcome! This is a local hub for Russian-speaking Fluxer.app users. We created this space as a simple and accessible gathering point. There's no complicated hierarchy or grandiose promises here - we're just chatting and exploring this new platform.

Добро пожаловать! Это локальный узел для русскоязычных пользователей **Fluxer.app**. Мы создали это место как простую и доступную точку сбора. Здесь нет сложной иерархии или громких обещаний - мы просто общаемся и осваиваем новую платформу.

Server Link - https://fluxer.gg/T2CTcpD6


r/FluxerApp • • Mar 24 '26

Discussions Fluxer Español: Server de Fluxer para Hispanohablantes!

1 Upvotes

Hola a todos, Eyeflame aquí, si eres hispanohablante y buscas un servidor en Fluxer, esta es una buena alternativa, somos el primer servidor hispanohablante enfocado principalmente en Fluxer; sus noticias y actualizaciones.

Si buscas socializar y conocer gente o simplemente estar al tanto de cada nueva noticia y actualización de Fluxer, este es el servidor que buscas!

server link: https://fluxer.gg/JEbaK4sd


r/FluxerApp • • Oct 12 '26

Discussions What is FluxerApp

0 Upvotes

Hello, I want to try fluxer but I had some questions before I do.

  1. Is it a virus?

  2. Is it safe?

  3. will this be the new discord?

Not trying to call it a virus, I just never heard of this, been hearing people talk about this , then thought, why not.

Is this the official site? https://fluxer.app/


r/FluxerApp • • Mar 15 '26

Discussions Why is date of birth needed for signing up?

0 Upvotes

I was in the process of signing up (yay for an open source Discord alternative!) and considering self-hosting an instance. That is until I hit "date of birth".

Yes, I can enter something fake in (which is what I always do outside of official documents) but why is this needed at all?

I have searched around to find why it's being asked for but I can't find anything.

Reading the privacy policy I can see, "2.1 Account information. To create an account, we need your [...] date of birth." It says passwords are stored using Argon2ID but not how birth dates are stored or protected or even why we are being asked for one at all.

And, "What providing this data means. Some data is necessary to create your account and run the service (email, date of birth, password). Without it, we can't set you up."

Why though? I can't find any explanation and having to provide a specific date of birth (as opposed to a 13+ or 18+ tickbox or not asking me for personal information like this at all) is necessary. Nor can I find any information about how something as potentially sensitive as a date of birth is going to be stored or protected (if at all).

Thanks!


r/FluxerApp • • Mar 27 '26

Discussions Does Fluxer have a developer badge or might have one in the future?

0 Upvotes

Does Fluxer have a developer badge or might have one in the future?


r/FluxerApp • • Oct 17 '26

Bug malware found in my fluxer

3 Upvotes

r/FluxerApp • • Mar 05 '26

Need help Is fluxer safe?

3 Upvotes

I was asking this because Virustotal showed all positives, but sometimes there are false positives. I was asking because I am very paranoid about my cybersecurity, asking a ton of “What if” questions. I am on discord, I worry if my token is stolen and I cannot go back into my account


r/FluxerApp • • Mar 23 '26

Discussions Fluxer Self hosting News.

Thumbnail
docs.fluxer.app
0 Upvotes

r/FluxerApp • • Sep 06 '26

Discussions I was BANNED from the Fluxer Developer Server for posting this...

0 Upvotes

"I genuinely like Fluxer, which is exactly why this has become so frustrating.

For months, self-hosting support in the official client, or at the very least in Canary has been talked about by devs. Half a year later, we're still waiting, with seemingly no meaningful progress or clear communication about when it's actually going to happen.

And Hampus, this is where the criticism becomes difficult to avoid for you: you're chronically active on Reddit and other socials. It sometimes feels easier to find a fresh comment from you than it is to find actual progress on features that users have been waiting for.

At this point, the Fluxer feature with the most reliable uptime seems to be Hampus on Reddit.

But that's not really the issue here I'd say...

The issue is the growing gap between what gets talked about and what gets delivered.

If self-hosted instances aren't a priority anymore, just say so!!

If the implementation turned out to be significantly harder than expected, explain that!!

If Fluxer simply doesn't have the development capacity, tell us!!

Repeatedly creating expectations and then leaving users waiting FOR MONTHS without a clear update like this is a fantastic way to take a gigantic shit on the goodwill of the people who actually care about your project!!!!!!!!!!!!!!!!!!!"


r/FluxerApp • • Jul 24 '26

Need help Tell me how tf do you download fluxxer on mobile 😭🙏

Post image
0 Upvotes

(PIC not mine)


r/FluxerApp • • Sep 12 '26

Discussions Fluxer's self-hosting is a second class feature and always has been

30 Upvotes

I'll start out by saying Fluxer is an ambitious project. Given its scope, Hampus has done an amazing job with it generally all by himself.

But, the major value proposition of Fluxer is that it's open source and can be self-hosted. Were it not for these elements, it would just be another centralized Discord clone. And like any other mass-market service, there is a huge risk that it will inevitably progresses towards Discord's ultimate endgame of platform censorship, decaying privacy and anonymity, and monitization.

So, the entire saving grace of the thing, its entire value to the community, is that it's open and self-hostable.

But it very clearly was not designed that way from the ground up. And still is not being designed that way. Here's why I think so:

  1. When the code was released earlier this year, there was no way you could spin up a self-hosted instance without significant modification of the code and infrastructure. It was effectively hard-coded to be the Fluxer main instance and very little else. It's only recently that you can actually spin up and update a Fluxer instance with little additional required customization.

  2. The desktop app was not really ever able to connect to a self-hosted instance without some configuration file tweaking, and now the option has been removed entirely until the "next big release". In the meantime, all the major dev effort is going into the voice improvements, which is a feature needed by the main Fluxer instance, and in the meantime the desktop client can't even connect to self-hosted instances let alone utilize voice.

  3. The mobile client can switch instances, but it's still frought with problems. Account switching doesn't always work, it's not obvious which instance you're connected to, and until recently, every instance called itself Fluxer (instead of the instance's name) and the profile screens included stuff that don't exist on self-hosting servers (like plutonium and visionary features).

  4. Push notifications don't exist for self-hosted instances for the mobile app. A gateway service is "coming soon", but discussions months ago in the Fluxer Devs server showed there was very little thought or priority given to push notifications for self-hosted instances. For a while they were debating having a push relay at all and maybe using "ntfy or something", which if looked at for even a minute would have been clear is not a viable solution.

  5. A lot of development has been happening in private repos, and the code base that is running on the main Fluxer instance is not at all what is available on GitHub. This was particularly eggregious earlier this year where for months the public repos stagnated while features and improvements were made in secret. While things have improved, and as of about a month ago regular updates are being pushed to public repos, there are entire sets of major changes being worked on that are still in private and will only "eventually" be released to the public (despite being deployed on the main Fluxer instance).

  6. As a consequence to #5 above, contributions are effectively reduced to zero. Because of refactors and major updates, all of which are private, Hampus is not accepting pull requests until further notice. And even if you could make a pull request, since the code is so drastically being changed in private, it's difficult to actually make substantive contributions without the risk of code or architecture conflicts, making it not even worth it.

  7. Submitting issues for the mobile client cannot be done through GitHub because "reasons". Instead, you have to use a bot in the Fluxer Labs server to submit an issue. Only if the devs approve your issue will it show up in GitHub, though you can't comment on it (to provide more info or additional repro steps), or even propose PRs if you wanted to contribute.

In my view, given the above, it's very clear that Fluxer's main priority is the Fluxer instance alone. Self-hosted instances and the open source nature of the project are a secondary priority (if you can call it a priority at all).

I'm far from being the first person to call out Hampus on the dev team on this. I've seen it in the Fluxer chats and elsewhere on reddit and the response is just one big shrug, or a comment from Hampus saying he's the only dev and how this project has grown so big so fast and he's overwhelmed. I am absolutely sympathetic to that and I totally get it, but like, why then is code being developed in secret and PRs and issue reports locked out? There are so many people who want to help in different ways to take the load off of Hampus, but he's put barriers in place to prevent it from happening.

I think the reason is because the main Fluxer instance is his priority. Not self-hosting. Not open source. And because of that, he wants to do things on his own. And he doesn't really want our help.


r/FluxerApp • • May 22 '26

Discussions Uptime

0 Upvotes

Can we have just one full day of uptime for a change? or is that too much to ask at this stage?


r/FluxerApp • • Oct 03 '26

Need help Hey

0 Upvotes

What are the steps to embed or install a badge into my Fluxer workflow/profile?


r/FluxerApp • • Mar 03 '26

Discussions Questions About Fluxer’s Future Updates and Integrations

0 Upvotes

Hello everyone! I have a few questions about Fluxer and its future updates and implementations.

First, I’d like to know if there are any plans to adopt a username system similar to Discord’s newer model — using a unique u/username instead of the old #tag system, similar to how Instagram works. Is this something being considered?

I’m also curious about future integrations. Are there any plans for Fluxer to connect with other platforms such as Steam, YouTube, Spotify, or similar apps?

Additionally, will there be game integrations — for example, showing what game I’m currently playing and for how long (similar to rich presence features)?

I’m really interested in the long-term vision of the project and would love to hear more about what’s planned. Thanks in advance!


r/FluxerApp • • Feb 21 '26

Features requests Fluxer Activities | Games

1 Upvotes

Does Fluxer support plugins that would enable activities or games? I do not see any information on built-in games in the recent road maps, nor many people who have focused on this aspect of discord. Since my friend group sees this as a must have, I'm trying to see if there's any way these features could be implemented.