• @peregus
      link
      118 days ago

      Do you mind sharing with us what’s incorrect? I’m here to learn.

      • chebra
        link
        fedilink
        118 days ago

        @peregus It’s explained in other threads here. The key is in the url but behind # and that part is invisible to the server. protocol://host:port/path?query#fragment, server will only see …?query, so both participants can decrypt, but server can’t => E2EE

        • @peregus
          link
          118 days ago

          But it’s the server that creates the URL in the first place, so it must knows it, right? …or wrong?

            • @peregus
              link
              118 days ago

              Oh, ok, now I get it. So it could be checked by a third party if that code is really created by the browser and if it’s not sent to the server, correct?

                • @peregus
                  link
                  118 days ago

                  @[email protected] but the owner of the server could change it, could it be checked directly on the webpage of the service? Not that I will do it (I can’t, I can’t read that code), I’m just curious.

                  • chebra
                    link
                    fedilink
                    318 days ago

                    @peregus yes, well the javascript on the site is minified, but I found this place even in the minified code. At this level it would be easier to take the source code and compile your own, host your own instance, then you know exactly what code is running there. And their minified code could be directly compared with your minified code… the beauty of open-source software.