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.

  • artyom@piefed.social
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    1 hour ago

    If your chat app/protocol provides something other chat apps are lacking, absolutely, go for it. If not, no, please don’t.

    At this point it’s hard to imagine something that isn’t being provided by the likes of Delta Chat, Cwtch or SimpleX.

    You know what I would like to see is an app that uses any of these platforms and creates a nice private social network. There was an app a while back called Circles that used Matrix, and was exactly what I was looking for, but unfortunately was archived. But if you’re looking for something to do…

  • Em Adespoton@lemmy.ca
    link
    fedilink
    arrow-up
    5
    ·
    2 hours ago

    It’s something I’ve been reflecting on for a while, and I haven’t figured out an answer yet.

    I feel like we need something that fills the original niche Discord and Telegram filled, while having the flexibility of XMPP and the E2E security of Signal. Most likely it needs to be a single platform that’s simple to stand up and maintain that has plug-in components providing break out features. So, an XMPP driven federated public key system, public rooms, a simple API to integrate with other software, built in web UI with PWA compatibility.

    But whatever is done, it’ll run afoul of the XKCD standards comic.

  • Dave@lemmy.nz
    link
    fedilink
    arrow-up
    4
    ·
    2 hours ago

    My personal view is that we need few, well supported chat ecosystems. I am unlikely to even try to convince my friends and family to move to a chat platform made by one or a few devs, it needs to have a foundation behind it that can give some guarantee of long term support (think Signal or Matrix).

    Anything else is just a play project that could shut down at any time, and that’s not what you need for chat.

    • typhoon@lemmy.worldOP
      link
      fedilink
      arrow-up
      1
      ·
      2 hours ago

      Fair point on Signal and Matrix for 1-on-1 or family messaging, and I agree nobody wants to migrate relatives onto a small project.

      To clarify, the goal here isn’t a WhatsApp or Signal replacement. It’s specifically aimed at the Discord gap: persistent voice rooms, screen sharing with audio, spaces, and community permissions, built on top of existing XMPP infrastructure so it isn’t locked to a single app or server going down.

      • timbyte@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        57 minutes ago

        Instead of focusing on one or more features, why not design something that can be expanded to do anything and then focus on building the features you want and other people can build other features onto it?

        Start with a solid base that provides both anonymity and privacy. I’ve looked at all the chat apps I could find and I think Cwtch or Briar are probably the best bases to start on. Check whether those projects are capable of being expanded to support the features you want. If not, perhaps then build a better base.

        Personally, I’m not interested in federation (eg. email). I would focus on something peer-to-peer without servers and uses onion routing to hide IPs. Cwtch and Briar are like that.

  • ghost_laptop@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    2 hours ago

    simplex model is actually prett good since its design for servers to not host user data. it only a relay that temporarily holds messages.

  • aim4harmony@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    2 hours ago

    Something privacy -respecting to use WhatsApp when your folks won’t make a move to another service, please.