4 ms·
Some general notes (I don't have recommendation). Many people see those options as not something to build on, but rather use. I.e. there aren't many p2p encrypt
by kodablah 9y ago
Some general notes (I don't have recommendation). Many people see those options as not something to build on, but rather use. I.e. there aren't many p2p encrypted communication frameworks, and they especially don't solve anonymity + discovery well. Also, I think not enough developers care about making it really easy to self-host (i.e. bust NAT and serve from home) with read mirroring. Myself and I'm sure a gazillion others have side projects trying to tackle these things. You just have to wait until one catches on :-)
- no_identd 9y agoHere's your solution, 181 pages worth of it: https://grothoff.org/christian/habil.pdf https://grothoff.org/christian/habil.pdf Bonus: Briar could run on GNUnet, which would speed up interest in secushare development, which currently occurs at a... well, unexciting rate. Also, I wish Briar would implement double ratcheting WITH metadata encryption. At the moment, it has no double ratcheting, but because the transport layer works differently this seems less concerning as they use good crypto algorithms, but it poses an issue to secure interdevice message sync. I only point the 'WITH metadata encryption' part out because SignalProtocol[!] lacks it. A point against both Briar and Signal: I can't specify my preferred encryption method and parameters.