Researchers from several institutes worldwide recently developed Quarks, a new, decentralized messaging network based on blockchain technology. Their proposed system could overcome the limitations of most commonly used messaging platforms, allowing users to retain control over their personal data and other information they share online.

    • HubertManne@kbin.social
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      I disagree here. with p2p/federated you have to worry about if your microprovider goes out. I think blockchain would be a useful way to keep a users preferences and to keep usernames distinct.

        • FlowVoid@midwest.social
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          1 year ago

          The blockchain Is not public. It can only be accessed by nodes whose members are in the channel.

          I’m curious whether without a blockchain there is a solution that (a) allows users to access all their encrypted messages even if any individual server goes down, (b) preserves a record of all communications/edits, and © is resistant to record tampering by a malicious server admin.

            • FlowVoid@midwest.social
              link
              fedilink
              English
              arrow-up
              2
              ·
              edit-2
              1 year ago

              Storing client side isn’t good enough, your records could be lost or destroyed. That’s why people use Gmail.

              And it’s not just third parties, what about untrusted recipients? For example, how do you prove you sent someone a message on a decentralized system?

                • FlowVoid@midwest.social
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  ·
                  edit-2
                  1 year ago

                  Even if it’s encrypted, it can be lost or destroyed if it’s stored client side.

                  I know what identity keys are, but they don’t solve the problem. If someone says they didn’t receive your message, the best way to prove you successfully sent it is to use a distributed ledger.

          • I Cast Fist@programming.dev
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            The blockchain Is not public. It can only be accessed by nodes whose members are in the channel.

            So, federation across channel participants, but with blockchain instead of a “shared database”?

            • FlowVoid@midwest.social
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              Yes, that sounds like their goal.

              Blockchain is used to prevent a malicious participant from altering/corrupting records.

        • HubertManne@kbin.social
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          I don’t think you get it. With a distributed ledger your username could be unique. sorta like the digital art pieces. So if your instance goes down you register at another one with your token and it recognizes you and associates you with everything it conceivably can (some stuff may only have been saved on the instance which is gone). So if the new instance has magazines you interacted with it should still be able to see comments as yours and such.

            • HubertManne@kbin.social
              link
              fedilink
              arrow-up
              2
              ·
              1 year ago

              tree burning is bitcoin specific implementation. distributed ledger does not rely on processing power being wasted for no good reason. Believe me I don’t like bitcoin or its ilk but am fine with grid coin for example. pgp keys are for authentication and don’t store information. distributed ledger is not for authentication its for just like it sounds. keeping a ledger.

      • Barry Zuckerkorn@beehaw.org
        link
        fedilink
        arrow-up
        9
        ·
        1 year ago

        I disagree here. with p2p/federated you have to worry about if your microprovider goes out.

        This Quarks protocol still seems to require reliance on “nodes,” which is the same thing as a federated service, with extra steps. It’s more overhead without any of the portability you want.

        • HubertManne@kbin.social
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          oh sorry. I was not saying in general, not that this implementation is good. I could see the distributed ledger being used though to good effect. Unfortunately it rarely is.

      • amki@feddit.de
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Same thing with centralised services only that you have no options to choose from