dansup (@dansup@mastodon.social)
mastodon.social
Attached: 1 image sup. is an open source encrypted fediverse instant messenger, similar to whatsapp, made by pixelfed. The beta will be launching later this month, and btw most fediverse accounts will work, not just Pixelfed 😉

It will be open source, end to end encrypted using Signal’s double ratchet encryption protocol, and he plans to make it easy for fediverse platforms to integrate it. The beta will release later this month.

He’s also the creator of https://fedidb.org btw

  • Jackthelad@lemmy.worldEnglish
    2·
    1 year ago

    I just saw this on Mastodon and was about to post it here. 😄

    Pretty cool idea. Though I’m not looking forward to trying to convince my friends to switch to yet another new platform. 😂

  • ren (a they/them)@lemmy.worldEnglish
    2·
    1 year ago

    While I doubt I could get my friends and family on yet ANOTHER messaging app in the year of our lord 2023.

    Sup. Is a fucking brilliant name.

      • Magiwarriorx@lemmy.worldEnglish
        1·
        1 year ago

        I remember idly wondering how DMs worked in Lemmy, and I was kinda shocked when I realized they aren’t secure.

        • Aloso@programming.devEnglish
          1·
          1 year ago

          “secure” is relative. They may not be e2e encrypted, but they are still encrypted via TLS, like any HTTPS traffic. It’s the same encryption used for online banking. If you care about your instance admin being able to read your messages, you should use Signal or a Matrix client though.

          But remember that only a few years ago, almost nobody used e2e encryption, and it wasn’t much of an issue.

    • garretble@lemmy.worldEnglish
      2·
      1 year ago

      I personally hate the name, but only because I had a roommate in college who would start every conversation with “sup.”

      On text messages, IMs, in person, you name it. It really started to get under my skin.

      But I hope the software is good.

  • PineapplePartisan@lemmy.worldEnglish
    1·
    1 year ago

    I’m not leaving Signal until someone implements keeping data at rest encrypted on both ends and requires multi factor unlock (bio+pin is my choice).

    So sick of E2E clients that leave the data in plaintext on the devices and then back it up in plaintext to the cloud.

    • outdated_belated@lemmy.sdf.orgEnglish
      0·
      1 year ago

      Does Signal back up in plaintext in the cloud? (If so that doesn’t sound like E2E encryption… unless the ‘ends’ are uh… also constituted as the cloud itself which is… defeating the purpose).

      Where do the pub/ private keys live, exactly, tbh. (Assuming it is asymmetric encryption that they use?)

      Edit: ah, misread. I thought you said that you were not joining it due to it storing plain text in the cloud.

        • XaeroDegreaz@lemmy.worldEnglish
          1·
          1 year ago

          Hm… If they’re not being stored on the cloud, that means offline users would never receive messages, unless Signal is purely P2P. I haven’t looked at the project, or the source, but I find it hard to believe – you can’t really do user lookups without some sort of middleware in the cloud.

          • dinckel@lemmy.worldEnglish
            1·
            1 year ago

            All the data they have on any specific user is the account creation date, and the last online timestamp. They’ve already done loops around this topic in the DOJ.

            And I thought it should be obvious that an online service doesn’t work if you’re offline

            • XaeroDegreaz@lemmy.worldEnglish
              1·
              1 year ago

              Yeah, but messengers, such as WhatsApp for instance, will send you missed messages once you’re back online. That’s what I was referring to.

          • ᗪᗩᗰᑎ@lemmy.mlEnglish
            1·
            1 year ago

            You’re right, Signal is not P2P. The way Signals messaging pipeline works is like this - note I’m oversimplifying it for accessibility.

            Sending a message to Bob

            1. You press Send.
            2. The message is encrypted on your device with a key that can only be unlocked by Bob.
            3. The message is then “sealed” so that there’s only a “deliver to” field visible (not a “from”).
            4. The “deliver to” field is addressed with a hashed/salted label for Bob - this means Signal’s server can see its a unique user, but not what their name is.
            5. The message is finally sent to Signal’s servers.
            6. Your message sits on Signals servers until it can be delivered to the intended recipient.

            you can’t really do user lookups without some sort of middleware in the cloud.

            See their blog post about Private Contact Discovery, they’ve spent a long time figuring out how to engineer a method to know as little as possible about you.

  • vacuumflower@lemmy.sdf.orgEnglish
    1·
    1 year ago

    Desktop fscking client, please. Not electron based would be nice, yes? QT is good.

    ICQ-style or old Skype-style user directory would be wonderful too. VoIP is not something I’d care about, file transfers are.

    This is cool.

    • tate@lemmy.sdf.orgEnglish
      01·
      1 year ago

      Not blank for me. I see a bunch of graphs and statistics about the fediverse.

  • randint@lemm.eeEnglish
    0·
    1 year ago

    Your link, https://mastodon.social/@dansup/110836811082599292%20sup.%20is%20an%20open%20source%20encrypted%20fediverse%20instant%20messenger,%20similar%20to%20whatsapp,%20made%20by%20pixelfed.%20%20The%20beta%20will%20be%20launching%20later%20this%20month,%20and%20btw%20most%20fediverse%20accounts%20will%20work,%20not%20just%20Pixelfed%20%F0%9F%98%89 is broken. I think you accidentally copied the body text as well. Cleaning up the link results in https://mastodon.social/@dansup/110836811082599292, which works fine.