son 😭😭😭😭😭

source: u/Dyenzo on reddit.

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

I noticed that the url https://lemmy.kde.social/ returns the error on the picture. Does anybody know what happened?

I have a bot that fetches news from kde feeds, I used to post things there, I guess I'll start posting them here.

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!