[LATE POST] Fluxer has decided against adopting Activity Pub for its federation protocol proposal, before accepting adoption of a custom protocol based on PolyProto (multiple links)
Links to proposal reports (chronological ascending):
https://fluxerparse.fluxer.host/federation_comprehensive_report-20260329
https://fluxerparse.fluxer.host/federation_comprehensive_report-20260620
Post about Fluxer announcing the chosen protocol: https://leminal.space/post/40562232
By OOOP: https://fluxer.app/blog/roadmap-2026
Fluxer Federation Protocol Announced!
From Fluxer's updated roadmap on their website
See the polyproto website they linked here
I hadn't heard of this protocol before, but the possibility of transferring accounts between homeservers sounds exciting!
Here's the text from the screenshot:
Federation lets people on different instances talk to each other as if they were on the same service, the way email works across providers. Fluxer's federation will be based on polyproto-core, a specification from the polyproto project, with our own extensions on top. polyproto is still young, and we hope that building a real implementation of it, and sharing what we learn, helps the specification mature and benefits everyone else who builds on it.
polyproto-core describes an identity that works across servers. Your identity is anchored on your home server and looks like name@domain. Behind it is a certificate that your home server signs over a key created on your device. To prove who you are to another server, your device signs a challenge from that server, so one identity works across servers and you don't need a separate account on each. Messages are signed by the sender, so a server you visit can't forge messages from you without being detected, as long as your home server and your device haven't been compromised. The specification also defines how to move to a new home server.
polyproto-core is an early beta specification maintained by the Polyphony project. As of October 2026 it is at v1.0-beta.13. It focuses on identity and leaves message formats and chat features to extensions. We'll write our own extensions for Fluxer's features and propose changes to the protocol where they would help others too.
We'll publish an experimental draft pull request in 2026 that you can try and give feedback on. The stable release follows in 2027. Until the draft is up, the discussion happens in Fluxer Labs, and you're welcome to join in.
You can already sign in to several instances from one app. You sign in to each instance separately and switch between them. The mobile apps already support several instances and accounts, and the desktop app gets the same in early October 2026 with the update described in #2.
Two links for federation proposals
-
https://github.com/orgs/fluxerapp/discussions/703
- Self note: I was expecting
[email protected]#0000(four zeros represent a discriminator), but it seemed like they are making their own protocol until i read the next link
- Self note: I was expecting
-
https://github.com/orgs/fluxerapp/discussions/663
- This is what they have to choose: ActivityPub, AT Protocol or their own protocol (which I seem the latter will conform more to the
username#[email protected]handle)
- This is what they have to choose: ActivityPub, AT Protocol or their own protocol (which I seem the latter will conform more to the
Fluxer is sooo slooowww on my phone
Android, tried Waterfox/Yandex/Chrome/DDG.
Whenever I try to go from one page to another, it takes forever to load. I've tried clearing the cache, and my internet connection is solid for everything else I do. Is there a way to fix it? It's maddening!
Workaround for streaming audio on Linux (How-to-Guide)
At the time of writing this, Fluxer does not yet support streaming a game, application, or your screen with audio on Linux. This is a workaround that can be used in the meanwhile. At first glance this guide might seem lengthy, but it's actually only about 3 steps required for this workaround, the rest is explanations and sub steps to help guide those unfamiliar with audio interfaces and routing audio.
Note:
This workaround requires installing a tool through the Linux terminal, although this package is available in Debian, Arch and fedora based repositories, this guide will use the Debian command apt for installation.
What we are aiming to achieve is sharing audio from a game or an application along with our mic input with others in a call. We will do this by using an application called qpwgraph. Which is a Graph manager for Pipewire. It will let us "route" inputs and outputs of different audio sources with a graphical interface. While this requires some manual labor whenever we want to stream audio while in a call, it is by far the simplest method I have found to substitute the "Sharing Audio" feature.
Note: If your system is not using Pipewire, QjackCtl is an alternative but it also requires installing the API Jackd.
First we need to install qpwgraph, so lets open up a terminal. Then type the following command into the terminal:
sudo apt install qpwgraph
Once installed we can open the application either through our application menu or typing qpwgraph into the terminal.
What, and how many, audio interfaces you see when you first open up qpwgraph depends entirely on your hardware and system setup. Because of this, I will try and explain how you identify what is an input and what is an output source. I recommend that all software capturing or playing audio is closed when first starting qpwgraph, because then only your hardware interfaces and sources should be listed. Once you start an application that either plays or captures audio it will immediately show up in the graph editor as nodes.
Tip: You can move around the nodes to get a better more manageable view if needed.
There are different types of nodes, we have input nodes, output nodes and nodes that have both input and output. Some interfaces have multiple nodes such as most sound card. If the only sound card on your computer is the integrated speakers, headphone jack and internal mic, which is standard for most laptops, it will most likely be represented by three different nodes with differently named Input/outputs. With Capture FL, FR being the input node for your mic and Playback FL, FR being your speakers, FL and FR being your front Left and Right channels.
Note: These Input/output connection points are color coded, with green being the color for standard audio.
If we now start an application that plays audio such as Spotify, we will get an entirely new node in our graph editor called Spotify. This node will have its Output FL, FR connected to the Playback FL, FR of your "output-interface" node.
Let's say we want to stream the music playing from Spotify while talking and sharing our screen in Fluxer, all we have to do is to also route the output from Spotify to the Input FL, FR of Fluxer. Some apps can't handle multiple sources being routed to the same Input channels, and require setting up virtual audio devices that act as a middle man. Fortunately, Fluxer can handle this.
If you open Fluxer, it will show up in qpwgraph as Chromium, this is expected since its a webapp. All we need to do now is to click the output connections on Spotify and connect them to the input connections on the Chromium node.
If you want to break the connection between two nodes simply select it by left clicking the green line connecting the two and then right click and choose disconnect.
Reference image below using an external sound card connected as default input device, and Spotify connected to both standard output and Fluxer input along with external sound card on the same channels
This same operation can be performed for any app that plays sound, and qpwgraph will remember routes even if apps are closed and then opened again.
Note: Two things to remember; You will need to manually cut connections if you want to stop streaming audio along with your voice, and the other parties in your call will not be able to adjust the volume ratio between your mic and what ever audio you have routed to the Fluxer input. This is because it is now the same audio source in Fluxer so you will have to adjust the levels on your end.
