Before I put serious time into this, I wanted to get a quick sanity check from people here. Not trying to pitch, start drama, or add another slop project to the ecosystem, and I know contributing to an existing project is often smarter than starting fresh. I would rather find out that something already covers this or that the trade-offs make it impractical before writing code.
What if you took the open federation and mature OMEMO foundation from XMPP, Dino, and Gajim, paired it with the community/space feel and self-hosting ergonomics of things like Movim, Mony (Harmony), or Fluxer, and aimed for the snappy native UX and solid Linux media polish people expect from Discord’s upcoming Rust client?
Right now each piece leaves clear gaps around drop-in voice rooms, screen sharing with system audio on Linux, granular per-channel permissions, and consistent desktop/web parity. Does combining those pieces make architectural sense to you, or does mixing XMPP and E2EE with Discord-style features inevitably create a splintered ecosystem or compromise one side too much? Where do you see the biggest pain points?
Edit: To clarify, the goal isn’t another chat messenger like Signal or WhatsApp or SimpleX or Cwtch, etc. Nor is an attempt to create some Matrix based client like Element. This is specifically aimed at a real, federated alternative to Discord for communities, voice rooms, and screen sharing.


Yes.
If you build it, it might be good.
Eagerly innovate.