It seems really cool but I’m a bit wary of it due to the crypto stuff.

    • From two days ago:

      https://lemmy.ml/comment/13108576

      A few SimpleX shortcomings beyond what you noted, in no particular order:

      • No multi-device support.
      • Adding contacts requires sharing somewhat large links (as either text or QR code) which can be inconvenient.
      • Messages are lost if not retrieved soon after they’re sent. (I think it’s 21 days by default. I’ve had vacations longer than that.)
      • No group calls.
      • Group messaging is full-mesh, meaning that as a group grows, the network traffic will balloon faster than it would with any other topology. This is generally bad for high-traffic groups, but it might be okay if they stay small or everyone always has great unmetered connectivity.
      • The claim to not have user IDs is misleading at best, and outright false in group chats.
      • The desktop app uses Java, which will be unappealing to more than a few people. (To be fair, several other messengers use Electron, which is also unappealing to more than a few.)

      It does have some neat design ideas. I don’t consider it ready for general use, but I look forward to seeing how it develops.

      •  jet   ( @jet@hackertalks.com ) 
        link
        fedilink
        English
        427 days ago
        • The claim to not have user IDs is misleading at best, and outright false in group chats.

        I’m in a group chat but I’m unable to send a direct message to a group member, that’s annoying, but would substantiate the claim that they don’t have general user IDs.

        •  mox   ( @mox@lemmy.sdf.org ) 
          link
          fedilink
          6
          edit-2
          27 days ago

          Their queue IDs are user IDs. Each one points to a specific user. You can call it a queue ID, or an account ID, or a user ID, or an elephant, but that doesn’t change what it is.

          They crate a different ID to share with each contact in 1:1 chats, but that doesn’t make them anything less than user IDs. You can do the same thing on any other chat service by creating a different account to reveal to each contact. (This is obviously easier to manage on clients that support multiple accounts, but again, that doesn’t change what the IDs do.)

          And in group chats, they don’t even do that; they reveal the same ID to all group members.

          • Do I understand it correctly that the queue ID is specific to the group chat? How is that a user ID, then? The point is that the user doesn’t have an ID, and so you can’t find them in any other group chats unless they have introduced themselves. It basically only identifies the destination, and you really can’t avoid that, can you? Well, unless all messages are basically broadcasts, and everyone receives them, generating unimaginably larger traffic

        • That does seem like a decent workaround for the multi-device problem, if you only communicate in small groups and each member only has a couple of devices. Directly addressing each other could get unwieldy fast as a group (or the number of devices) grows, but I’m guessing you’re not in that situation. Nice work.

  • Things I didn’t like about Session when I looked at it:

    • Small group size limit
    • Forward secrecy has been removed
    • Isolated, app-specific onion network seems destined to forever be inferior to something like Tor, at least where privacy is concerned
    • Immature codebase (time and dedication could solve this, of course)
  •  retro   ( @retro@infosec.pub ) 
    link
    fedilink
    5
    edit-2
    27 days ago

    My experience is that I tried to use it years ago and it didn’t work, so I continued using Signal. Straight up could not receive messages. That’s probably fixed now but if I wanted to move away, I’d try SimpleX instead.

  • My issue is effective impossibility to selfhost. XMPP, Simplex, even Matrix are very possible to run on your own, while a Session node would be insanely, arbitrarily expensive (requires around $1000 now, IIRC used to be more). A hobbyist like me and you would not want to pour this much into something they provide out of the goodness of their heart.

    Seriously, if you have this much disposable money, you’d be better off running a few Tor nodes in various places).

  • It’s my go to messenger, idc about the crypto stuff, it’s just a way to reward volunteers who use their servers for all the mathematical conversions, and I have been thinking of running a node myself, to make the network more decentralized

    It has some downsides though, you can’t send larger files than 8mb, and if you lose your recovery phrase, you’re compromised, and you can’t edit messages

    I used to tell people to use Signal or Element, but I noticed many can’t even sign up, Session just generates a random ID for you, and voila…

  • It’s nice, reliable and super quick to on board people since no sign up required. Technology seems interesting and novel, and it’s also transparent since it even shows the node path (in addition to being FOSS)

    Do I trust it? No, but I don’t trust technology in general