• 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

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

source: https://bsky.app/profile/fluxer.app/post/3mnb6xaanr22h

A mobile app you seek? Well look no further, for I come bearing tidings of our launch information.

Our mobile launch is coming in 3 waves:

• An Alpha launch for our early supporters: Monday May 18th
• A Beta launch for our plutonium users: 3-4 weeks after that
• A public stable release 3-4 weeks after that.

Those final two dates are somewhat in flux (expect them to be pushed back). Timings depend on what bugs are found and how much there is to do.

There has been concern about why we are staggering it like this, so I want to address a few points.

• At the time of the plutonium beta, we plan to open source the code for any user who wants to build it themselves. We are not providing builds because candidly, it wouldn't reach our bar for calling it a "stable" launch.

We feel it's better to not offer an easy first party experience for new users to fluxer besides the PWA, than to give them a half finished one and have newbies bounce off. Most folks in here are techy. Your tolerance for half-finished products is higher than the average person. We need to balance our existing base with a prospective userbase.

• Our visionary launch is nowhere near a complete experience. We expect a lot of bugs and less than 1/3 of "stable" features will be present.

We are super excited to get this into the hands of users. Thank you all for your patience thus far <3 Your support means the world to us.

Full text:

Official self-hosting support lands in 3-4 weeks, by the way!

I replied on a Reddit thread where users voiced concerns that self-hosting was nowhere in sight. This was a very short amount of time after we'd decided on the internal time frame and scope of work needed for "v1.5", so to speak, where we'll be combining the good things that came out of my speculative v2 restructuring of the backend codebase with all the nice things going on in the canary build of Fluxer (https://canary.fluxer.app/download).

Canary includes screensharing with audio, text-in-voice, fixes to DM calling, a revamped and improved system for managing input and output devices and mic processing settings, and bug fixes to hundreds, literally, of bugs, thanks to the help of the people in Fluxer Testers. You too can become a tester by installing the canary desktop client or using the canary web client and joining Fluxer Testers by pressing the in-app banner.

Canary really is streets ahead of stable. We recently crossed build v0.0.200, compared to v0.0.8 of the original stable desktop client. I'm currently finalising the last bug fixes to make sure that screensharing and the other core features all work as they should before promoting canary to stable, and this will happen very soon.

In light of the recent outages, I'm also working on bringing the new backend infrastructure, inspired by the work done on v2, into the existing backend. The goal is to make sure Fluxer always runs silky smooth, without disruptive downtime or performance issues.

So here's what's coming: within 3-4 weeks, official self-hosting support lands. By then I'll have cleaned up and strengthened the codebase, abstracted away sensitive details about our safety system to prevent adversarial misuse, properly documented the entire API, written proper self-hosting guides, published Docker images, built a web-based setup wizard, and created a one-line command for setting up a Fluxer instance from scratch. On top of that, you'll be able to connect to alternative backends and account-switch between them in the desktop app.

That's what you can look forward to!

Source: Fluxer HQ group

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!

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.

That was fast.

cross-posted from: https://piefed.ca/c/privacy/p/592355/rip-discord-self-hosted-discord-alternatives-tested-teamspeak-stoat-fluxer-matrix-more

cross-posted from: https://piefed.ca/c/pcgaming/p/592341/rip-discord-self-hosted-discord-alternatives-tested-teamspeak-stoat-fluxer-matrix-more

• Invidious
• Youtube

I have been in the process of writing some help guides, and one of my friends graciously lent me his Steam Deck so that I could verify that Fluxer would work on it as well. And I'm happy to say it does. Although I did not plan on just posting a Fluxer Help-Article on Lemmy, I figured while waiting on the Fluxer team to start accepting pull requests and me getting done with my guides, someone might be looking for step-by-step instructions for their Steam Deck. So here it is. Feedback and discussion is of course welcome.

In this Help Article we will guide you step-by-step through the process of installing and integrating Fluxer into your application menu on the Steam Deck. Although not required, access to an external physical keyboard is recommended.

The Steam Deck is running a custom version on Linux that is based on Arch, and the CPU architecture is x86-64. This means we could either use the AppImage(x64) option or the tar.gz(x64) option from the download drop-down on https://fluxer.app/downloads

Since integrating the AppImage into the application menu requires additional steps such as manually retrieving the icon .png file this guide will focus on the installation process for the tar.gz.

Before we explain how to install Fluxer from the tar.gz file, let's take a moment and go through what a tar.gz file is. tar.gz are actually two abbreviations put together. "tar" from Tape Archive (sometimes referred to as a tarball) which is an archive file format and the "gz" at the end is short for Gzip(which in of itself is short for Gnu Zip) and it is a compression format. When combined you get an archive that is neatly packed in one file that is now also take up less space.

- Okay, why was that important to start off with?

Well, since it is a compressed archive, that means we can't just double click it and hope it will do much more than perhaps open the preinstalled unarchiver on our system. The fact is, a tar.gz file does not necessarily even have to contain any executable, even if it is an application. In this case with the Fluxer - tar.gz it does contain a executable.

Note: The steps outlined in this help article will primarily be performed using the terminal. The keyboard shortcut to open the terminal is "Ctrl + Alt + T" or you can open it from the application menu under the "system" category and it is referred to as "console".

Installing Fluxer

Let's begin by entering desktop mode on the Steam Deck. Long press the power button on the top of the Steam Deck, this should make a menu appear, from that menu choose "switch to desktop".

Then open the web browser and download the tar.gz(x64) from https://fluxer.app/download.

Once downloaded navigate to your download folder through the terminal by typing the following command:

cd ~/Downloads

Where Downloads is either the default download location, or the folder you chose to save the tar.gz file.

Tip: You can press "tab" on your keyboard to complete the file/directory name. If there are multiple files/directories with the same beginning of the filename it won't auto complete. But if you press tab again, it will show you all possibilities with the same beginning. This is referred to as "Tab Complete".

Now it is time to extract our tar.gz we can do this by using the tar command. Type the following command into the terminal:

tar -xzf fluxer-stable-0.0.8-x64.tar.gz

Tip: The options x, z, f stand for extract, decompress gzip, and specify the file. "Specify the file" might seem a bit cryptic, but remember tar is as old as tape drives. In essence the "f" option just says, what comes next is the filename.

You could run Fluxer here and now, cd into the directory we just extracted and then type the following command in the terminal:

./fluxer

But lets install it properly. Because right now, Fluxer only works if you navigate to its folder and run it manually from the terminal. If we move it to a standard system location and create a desktop entry, we will integrate it with your system. This means Fluxer will appear in your application menu, and you can launch it like any other installed program.

Note: make sure you are located inside the fluxer-stable-0.0.8-x64 folder for the next step. Use the cd command followed by the folder name if needed.

Next we need to create two directories, copy the Fluxer files and make a symbolic link to the executable that can later be used by the application menu to launch Fluxer.

Type the following commands into the terminal:

mkdir -p ~/.local/share/fluxer
cp -r * ~/.local/share/fluxer/
mkdir -p ~/.local/bin
ln -s ~/.local/share/fluxer/fluxer ~/.local/bin/fluxer

Each line followed by return or enter.

Now that the Fluxer has been installed we want to have it appear in our application menu, to achieve this we need to let the system know where to find it. Lets begin by creating a .desktop file with the Nano editor in the terminal.

Type the following command into the terminal:

nano ~/.local/share/applications/fluxer.desktop

Write the following into the file.

[Desktop Entry]
Name=Fluxer
Exec=/home/USERNAME/.local/share/fluxer/fluxer
Icon=/home/USERNAME/.local/share/fluxer/resources/512x512.png
Type=Application
Categories=Network;Chat;

Note: Change "USERNAME" to your username

Once done; press Ctrl + O to write out (functionally the same as Save), then Ctrl + X to exit Nano.

And now lets validate the .desktop file, by typing the following command into the terminal:

desktop-file-validate ~/.local/share/applications/fluxer.desktop

If this returns no errors we can continue and make our .desktop file executable

Type the following command into the terminal:

chmod +x ~/.local/share/applications/fluxer.desktop

And lastly lets update the desktop database. Type the following command into the terminal:

update-desktop-database ~/.local/share/applications/

You will now be able to access Fluxer through your application menu and it will sit in the correct category.

Note: Fluxer will not run properly if added to your steam library as a non steam game on the Steam Deck and launched from within game mode. - This is no longer true

Edit: After some troubleshooting I realized that there seemed to be an issue with the sandboxing and steam wanting to run the app in 32-bit environment.

Solution: All that should be required to solve the situation is to add env -u LD_PRELOAD %command% to the launch option in properties for Fluxer in steam. I did how ever first try and fix the sandboxing issue so if for you the issue persists after adding the launch options. cd into ~/.local/share/fluxer and run the following two commands in the terminal:

sudo chown root:root chrome-sandbox
sudo chmod 4755 chrome-sandbox

When I click on screensharing I do get the options to choose framerate, resolution, and window/monitor. But it just doesn't do anything.

A friend of mine on Arch also tried Fluxer and has the same issue.

Is screen sharing on Linux just broken right now, or are we doing something wrong?

Also of note that Hampus has made his first hire and stated elsewhere on Bluesky that he's looking to further expand the team. Positive news.

Fluxer Status

As pointed out by @[email protected]'s post, the Fluxer app required a CLA in order to receive code contributions. ProdigalFrog's post goes more in-depth to explain why this can be bad for the open source community.

Because of this post, the fluxer developer gave an official response on reddit, stating that the CLA would be removed.

The removal is now in a refactor branch, it should later be added to the main branch of the source code, you can check the commit here.

I'd like to give a special thanks to ProdigalFrog for noticing this issue and informing us about the problems this could cause in the future. Thank you very much, Prodigal!