GitHub - tinode/chat: Instant messaging platform. Backend in Go. Clients: Swift iOS, Java Android, JS webapp, scriptable command line; chatbots
github.com
Instant messaging platform. Backend in Go. Clients: Swift iOS, Java Android, JS webapp, scriptable command line; chatbots - tinode/chat
  • Pasta Dental@sh.itjust.works
    0·
    6 months ago

    If only all the efforts of making a better xmpp went to matrix or… to ‘fixing’ xmpp, the world would be a better place

  • simple@lemm.eeEnglish
    0·
    6 months ago

    Someone bring up that one xkcd strip.

    This looks pretty polished though.

    • Curdie@lemmy.world
      0·
      6 months ago

      My issue with XMPP was the lack of synchronization between clients. If my mobile was offline while I was chatting on desktop, mobile client would never have the same chat history as desktop and my conversation history would be fragmented. When I asked about it on some developer forum, they basically just said that was out of scope for XMPP and should be implemented in client. Which sort of makes sense if the client is a web client hosted somewhere but I wanted a thin desktop client like pidgin.im

  • wildbus8979@sh.itjust.works
    0·
    6 months ago

    Unfortunately, XMPP never delivered on this promise

    Huh that entirely false though.

    The fact that iMessage, GTalk, Messenger, WhatsApp, Zoom, and others closed off federation is no fault of XMPP, and a new protocol isn’t going to change that.

    • amigan@lemmy.dynatron.meEnglish
      0·
      6 months ago

      Honestly if even half of the effort that goes into every XMPP replacement du jour instead went into improving existing XMPP clients, we wouldn’t even be talking about this.

      • wildbus8979@sh.itjust.works
        0·
        6 months ago

        There’s a slew of decent xmpp clients too. Conversation on Android, Dino for Gtk is.nice (simple but polished), wouldn’t take much.

        • amigan@lemmy.dynatron.meEnglish
          0·
          6 months ago

          Yeah, Conversations is probably the most fleshed out. Dino is missing lots of features, as is Monal for osx. Gajim is very nice, but it’s written in Python. Psi used to be my favorite 10 years ago but it’s unmaintained.

          I just want something more on feature parity with all the Slack clones, but not actually Slack. Or mattermost. Or matrix. Goddamn, there are so many messaging apps

  • chebra@mstdn.io
    0·
    6 months ago

    @MasterPain We don’t need another instant messaging protocol. We need to fix the interoperability bugs in the existing clients and servers. “Modern replacements” are just making the problem worse.

      • chebra@mstdn.io
        0·
        6 months ago

        @wildbus8979 Have you ever tried sending files without knowing which client app is the other person using? How about multi-user-chats? Or just adding people in your roster. Blocking them? Encrypted chats? Seriously take a mix of 5 XMPP clients and try these actions, they will probably only work if both sides are using the same client app. And don’t even get me started on server support of carbon-copy XEP etc. Being signed up on multiple devices with the same account is a pain.

        • poVoq@slrpnk.net
          0·
          6 months ago

          When did you last use XMPP? With the exception of clients like Pidgin that haven’t been updated in 10+ years all of this works fine these days.

        • BearOfaTime@lemm.ee
          0·
          6 months ago

          What?

          I’ve tested multiple apps and servers over the last couple years, on Android, iOS, Windows, and Linux. The only challenges I’ve found are encryption and message history/sync between different clients/devices.

          The second test I do (after a quick “hello”) is send a large file, and time it. It always works.

          Then I send a gif, then a real video, something like 50mb.

          I’ve never had any consistent failure to send, no matter which clients are used.