termpair VS mailvelope

A counter to this would be to let users deploy their open source client [0] themselves to wherever (as one example, this is something that TermPair implements [1]).

[0] https://github.com/ProtonMail/WebClients

[1] https://github.com/cs01/termpair/#static-hosting

TermPair: Terminal sharing with AES-GCM 128 bit end-to-end encryption\ (34 comments)

From a quick skim it looks like the key is base64 encoded into the URL in terminal_id param, so presumably you just share the URL and the collaborator stays on the URL with the key? If the key is ephemeral/regenerated for each session it seems to eliminate most of your concerns.

https://github.com/cs01/termpair/blob/1d273fa306a543fefbf2cf...

This looks pretty similar to the few years old TermPair [0], featuring AES-GCM 128 bit end-to-end encryption and built with FastApi (Python).

[0] https://github.com/cs01/termpair

Mailvelope ( https://github.com/mailvelope/mailvelope) is an open source extension for Chrome and Firefox that allows users to use openpgp encryption with any webmail provider. Unfortunately, I have only one contact who has corresponded with me with pgp. But two others (both activists) use ProtonMail (my only reason for having an account on the service) -- but not Tor (their ProtonMail use predates the latest "explainer"). At least when it comes to email, I'm going to go out on a limb and say people should _never_ trust it for sensitive communications. Message content itself can be protected by pgp encryption (if people would bother to use it), but there's no watertight way to consistently avoid the kind of relationship mapping that nation states and transnational corporations have been doing for the last two decades. That game is already over, and Big Brother won -- no matter who you use for email.