Comment on [deleted]

Freeman@lemmings.world ⁨5⁩ ⁨months⁩ ago

• skullgiver@popplesburger.hilciferous.nl ⁨5⁩ ⁨months⁩ ago

  [deleted]

  source

  • jherazob@beehaw.org ⁨5⁩ ⁨months⁩ ago

    I recall somebody’s working on actual, E2EE Mastodon DMs, but couldn’t give you details, i guess when it’s ready we’ll know when people start using it

    source

    • Peter1986C@lemmings.world ⁨5⁩ ⁨months⁩ ago

      That would be Sup: github.com/theSupApp By the same person who started Pixelfed.

      source

      • jherazob@beehaw.org ⁨5⁩ ⁨months⁩ ago

        How the hell does he do so much? 😄

        source
  • 4am@lemm.ee ⁨5⁩ ⁨months⁩ ago

    Seems if the messages are sent in an inherently insecure fashion, all one would need to do is set up an instance that purposefully does not filter out all the things it’s supposed to be kind/competent enough to filter out, and boom it has everything.

    source

    • kevincox@lemmy.ml ⁨5⁩ ⁨months⁩ ago

      It’s not “inherently insecure” at least not to that degree. (Once could argue that lack of E2EE is insecure.) If you stand up an unrelated instance you shouldn’t be able to access private messages that don’t relate to an account on your instance. So only bugs in your instance, or your conversation partner’s instance, will be able to leak those messages.

      source