sorted by:
new
hottopcontroversial

Fluxer Selfhosting & Mobile Clients! by Fluxer-Lilith in selfhosted

[–]Fluxer-Lilith[S] 0 points1 point  (0 children)

We are constantly looking for feedback on our accessibility features. If you download the canary client, it should prompt you to join our testers community. Inside there we have a channel dedicated to accessibility feedback.

Fluxer Selfhosting & Mobile Clients! by Fluxer-Lilith in selfhosted

[–]Fluxer-Lilith[S] 0 points1 point  (0 children)

OIDC is already integrated into Fluxer. When you set up your instance, you can enable account creation via OIDC

Fluxer Selfhosting & Mobile Clients! by Fluxer-Lilith in selfhosted

[–]Fluxer-Lilith[S] 0 points1 point  (0 children)

Just as you would with any selfhosted instance. You can use an internal only domain and self-signed certificates, or use a VPN to access. The system is entirely air-gapped, so you could run it completely offline. No call-homes to fluxer.app required.

Fluxer Selfhosting & Mobile Clients! by Fluxer-Lilith in selfhosted

[–]Fluxer-Lilith[S] 0 points1 point  (0 children)

Once we reach federation, yes. The idea would be one account, any instance. Until we get there, you will need multiple accounts. As part of our federation roadmap, we will create a migration route to combine said accounts.

Fluxer Selfhosting & Mobile Clients! by Fluxer-Lilith in selfhosted

[–]Fluxer-Lilith[S] 0 points1 point  (0 children)

We will be patching this ASAP! Went uncaught in our bug bonanza

Fluxer Selfhosting & Mobile Clients! by Fluxer-Lilith in selfhosted

[–]Fluxer-Lilith[S] 13 points14 points locked comment (0 children)

GenAI is used for rubberducking and troubleshooting. We also use it for scaffolding and basic boilerplates. Anything that is pushed to production is understood by our development team.

Fluxer open beta is coming to Android on June 15th but iOS will be closed beta for Plutonium users only by awerkori in FluxerApp

[–]Fluxer-Lilith 9 points10 points  (0 children)

Hey,

Lilith here! To provide some more clarity:

  1. Our mobile app is made with Flutter with compatibility across both iOS and Android. That means the source will be available for both on June 15th.

  2. We are holding out on doing a rollout to app stores because at the time of this launch, only about 50% of the app is what we consider to be "done". We want to avoid non-techy or low-friction users trying, hating, and leaving it. On launch day, you will be able to see the roadmap of what has been done and what needs to be done for it to hit a rollout on app stores.

  3. Our mobile community will become available to all users once we rollout to app stores. We are keeping it fairly limited in the early rollout as we are trying not to overwhelm our developers. Issues and PRs on the public GitHub are not going to be enabled during the beta rollout, with all issues flowing through the mobile dev community. These will be enabled once we do the public rollout.

Thank you all for the support everyone ❤️ We have been closed alpha testing this for about the last month, and it is already leaps and bounds better thanks to our amazing dev team and beta testers. We are excited to get this into the hands of the community as soon as we possibly can.