• Magitian@fedia.social
    link
    fedilink
    arrow-up
    15
    ·
    10 days ago

    @kde @kde how I wish Neochat had a full implementation of E2EE. I (and probably several others) would happily make the switch from Element.

    • Bro666@lemmy.kde.socialM
      link
      fedilink
      arrow-up
      14
      arrow-down
      2
      ·
      edit-2
      10 days ago

      There are two ways of getting features into KDE apps that work better than wishing 😉 :

      1. contributing to our fundraiser, or donating to the project, or whatever. That is, providing the developers with means to get stuff done, either by buying them time so they can spend it on developing, or hiring help. If you are on this thread it is because you are doing this, or considering doing this, or whatever, so we can assume you already know about this.

      2. contributing with your know-how. Check out our get involved page, as it describes in detail how you can help with the implementation the things NeoChat needs.

    • Strit@lemmy.linuxuserspace.show
      link
      fedilink
      arrow-up
      3
      ·
      10 days ago

      Libquotient just added cross-signing support, which works in Neochat if it’s build against the new version. I’m not sure what else was missing from E2EE support.

    • Bro666@lemmy.kde.socialM
      link
      fedilink
      arrow-up
      5
      arrow-down
      5
      ·
      10 days ago

      There are two ways of getting features into KDE in a speedy fashion :

      1. contributing to our fundraiser, or donating to the project, or whatever. That is, providing the developers with means to get stuff done, either by buying them time so they can spend it on developing, or hiring help. If you are on this thread it is because you are doing this, or considering doing this, or whatever, so we can assume you already know about this.

      2. contributing with your know-how. Check out our get involved page, as it describes in detail how you can help with the implementation the things NeoChat needs.

  • penquin
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    10 days ago

    Does it do regular SMS? If you say yes, then my next question will be, does it do RCS? Or is that monopolized by Google? Because I’d extremely happy to leave Google’s shitty messenger.

    • aronkvh@lemmy.kde.social
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      10 days ago

      @alextecplayz@techhub.social Technically, you could use a Beeper account (or another homeserver with mautrix-gmessages set up) with NeoChat, but that’s not guaranteed to work by either side.

    • BearOfaTime
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      10 days ago

      You’re not getting RCS into any proper messenger.

      RCS is garbage that’s wholly hardware-bound (your phone/IMEI/Sim) which is pretty much antithetical to any modern (i.e. Post 1994) design.

      Why would I want to use a “protocol” that’s not network-agnostic (just like SMS)?

      Protocols like XMPP/Jabber predate RCS by close to 20 years, and already did everything RCS will eventually do, but it did it in 2010. Except be bound to your phone number (and encryption didn’t occur until more recently).

      SMS at least was an honest attempt to utilize the empty space in cell management frames. RCS is nothing more than an attempt to keep people using their phone numbers/IMEI as an ID when far better systems already exist. What possible rational can there be to develop a protocol that’s bound to hardware identifiers in the 21st century?

      A even better question to ask is why these organizations are abandoning Jabber/XMPP when they were using it for their own chat programs since 2000, and it’s had steady development over that time? (Hint: Jabber/XMPP is an open protocol, doesn’t lock you into any system/app/service. Anyone can use it, any client can communicate with any server over any network. RCS can’t. I currently run 4 different clients using the same accounts, on 5 or 6 devices, and they all stay in sync nearly instantly, with encryption).