429 Too Many Requests
wedistribute.org

A new messaging app is in development, and the project is described as “an open source WhatsApp for the Fediverse.”

  • Terevos@lemm.ee
    22·
    10 months ago

    I just learned about Matrix recently. Seems like something that’d be good. What sucks about it?

    • timbuck2themoon@sh.itjust.worksEnglish
      13·
      10 months ago

      Besides the main implementation synapse being slow, the new implementation dendrite is unfinished but progressing.

      But technical standards aside, the hassle of managing encryption keys is too buggy and confusing IMO. That’ll deter most people I feel.

      I want it to be great but it just isn’t there yet.

    • Sean Tilley@lemmy.mlOPMEnglish
      7·
      10 months ago

      I personally really like Matrix, but there are a few outstanding complaints about it. The biggest one is that the reference implementation everyone uses by default is known to be bloated and slow, and poor at scaling. Server admins have had a huge challenge of supporting a large amount of data for things like room history, which in the past required propagation to every server hosting every participant. The protocol itself has been described by some developers as overtly complex.

      Some of this seems to be improving, particularly with development of a Go-based backend implementation, Dendrite.

      • Samsy@lemmy.ml
        5·
        10 months ago

        And if dendrite fail, we wait for the rust-based backend implementation. :)

        • Strypey@mastodon.nzoss.nz
          2·
          10 months ago

          @deadsuperhero
          > development of a Go-based backend implementation, Dendrite

          Also Rust-based homeserver implementations like Construct and Conduit. Both of which are usable, although missing a few nice-to-have added features. Eg Conduit is still working on;

          “E2EE emoji comparison over federation (E2EE chat works)… Outgoing read receipts, typing, presence over federation”

          @Terevos @Samsy

      • Terevos@lemm.ee
        31·
        10 months ago

        Good to know. I signed up for beeper.com which seems cool. I am a bit concerned about data collection and privacy, so I’m trying to set up my own instance.

    • AngryDemonoid@lemmy.lylapol.comEnglish
      22·
      10 months ago

      I’m not even close to an expert, but from what I have heard, matrix collects quite a bit of metadata depending on the server you are using/federating with.

      • smileyhead@discuss.tchncs.de
        3·
        10 months ago

        Yes, it does not protect metadata great. It is visible that you and your interlocutor are talking together and when.

        But noone figured out how to prevent that in federated systems. You rather have less metadata in centralized place for everyone or more metadata but only for small subset of people.

        • Strypey@mastodon.nzoss.nz
          1·
          10 months ago

          @smileyhead
          > But noone figured out how to prevent that in federated systems

          You’ve basically got a choice been a centralised service where metadata can be limited but E2EE is mostly pointless (you have to trust the service operators’ E2EE deployment), or a decentralised network where E2EE is reliable, but it’s harder to limit metadata.

          Which one is best depends on the situation/ threat model.

          @AngryDemonoid

      • Terevos@lemm.ee
        21·
        10 months ago

        Yeah, I have been concerned about that. Looking into self-hosting matrix.