arcus
Sr. Member ⚓︎
   

 ⛺︎ My Room
XMPP: Chat!
Guild Memberships: Artifacts:
 
|
 |
« Reply #61 on: a Summer day » |
|
Fluxer v2 is out, along with a few other changes. https://fluxer.app/blog/mobile-clients-and-fluxer-v2Main changes: - There's more staff on the project
- There's now a self hosting guide
- It's now on Flathub
- Alpha versions of the mobile apps have been released on Github
- There's now $1,500 (USD?) worth of bug and development bounties on Github
- Currently, there's work being put towards 1440p 60fps screenshare with no audio or frame drops, this is publicly available to test through the canary client
Federation is still in the works, but has multiple issues that need to be ironed out: Why is federation taking so long?
We're working on it, and we need your input. Seriously, come talk through the design standard with the Fluxer team and developer community on GitHub and in Fluxer Developers. Federation matters to me and the entire team, and we want to do it right. A lot of questions are still unanswered:
• What happens when a user keeps returning to one Fluxer instance through another instance? • How does Fluxer prevent illegal content like CSAM from propagating across instances? • In DMs, which instance is responsible for moderation, if any? • How do users and communities migrate between instances? • How should Fluxer handle Plutonium? • Why is Hampus a ghost?
And dozens more.
We'd really like to avoid the email problem, where some instances or clients never support newer standards, by being careful with the design upfront. Some split between instances is inevitable, but Fluxer shouldn't start there through rushed implementation.
We want Fluxer to be the home for your community for years to come, no matter who hosts it. That means putting in the thought and building slowly.
Edit: There's also a community run site for finding chatrooms, bots, and themes.
|