this post was submitted on 09 Apr 2024
88 points (100.0% liked)

Technology

37735 readers
51 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] flashgnash@lemm.ee 2 points 7 months ago (1 children)

Does the whole encryption/decryption thing still bother you if you self host?

I tried out the app, the value there is that it's ready to go straight away, though I took it all down again because my messages being unencrypted on someone else's server makes me uneasy. May end up self hosting it for that reason and not using anything closed source

[–] jarfil 3 points 7 months ago

Somewhat. It's kind of a gradation:

  • 3rd party servers, or closed source, no trust.
  • Self-hosting on a hosting provider... it's not my hardware, but maybe some trust.
  • OpenSource with non-reproducible builds, even self-hosted at home, little trust.
  • Local bridges, OpenSource, with reproducible builds, and a 3rd party audit, most trust.

All software can have bugs, and we've seen what cases like xz-util can bring, so I would rather have no decrypting bridges at all, particularly for sensitive information... but for random private chats, "mostly trusted" sounds like enough.

Public conversations (like this one) are fine going through random bridges, but I feel like bridging with E2EE networks, is subverting user expectations.