• menas@lemmy.wtf
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 months ago

      Decentralized matrix has not the quality level for production. The only matrix user that has no issue have their account on all of their contacts on matrix.org. So, use it as a centralize app.

      • carrylex@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 months ago

        And your source?

        I’m running and am part of a Matrix server for years and experienced near zero problems with them so far.

        • magguzu@midwest.social
          link
          fedilink
          English
          arrow-up
          0
          ·
          3 months ago

          Great. Can you reference an SLA to prove that, and what’s the size of that server?

          Apples and oranges.

            • magguzu@midwest.social
              link
              fedilink
              English
              arrow-up
              1
              ·
              3 months ago
              1. Where do people keep getting this SLA pink promise information? Your SLA has to be presented to potential clients and whether you’ve been successful in maintaining it can make or break them being on board. It’s also audited for things like SOC2 compliance.

              2. That’s a microscopic fraction of what a product the size of Signal is dealing with, and unimaginably small compared to AWS

  • Tiger_Man_@szmer.info
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    There always is another and better choice and it’s called using your own fucking servers

    • PrettyFlyForAFatGuy@feddit.uk
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      3 months ago

      There was a big exodus to signal for a while a couple years ago when meta were fucking with their whatsapp privacy policy, similar to the exodus from reddit to lemmy.

      Having your infrastructure on a cloud provider allows you to keep your costs in line with your current amount of users, if you have a big influx you can immediately scale up to accommodate them, and then when that spike in users dies off as they invariably do you can scale back down instead of being left with a load of hardware you’ve just bought for your new users (that have since fucked off) and now aren’t using