> The CPU power point is well taken, believe me. I have considered having > the spec (or maybe this belongs in our Best Practices document) > encourage implementers to support and to prefer the computationally > lighter ciphers in TLS (e.g. the ChaCha stream cipher). This would be awesome. This would be really nice for people like me who dream of one day implementing all the protocols for Gemini from scratch. TLS 1.3's Salsa20 & Poly1305 are much easier to implement than other protocols (yes, yes, "don't write your own crypto," but my goal here is novelty, not security of my specific client). > There is an `application/pgp-encrypted` MIME type that Gemini can serve > content with, and people can write clients that to handle this, so > Gemininaut cypherpunks can do this if they want to! Please no. PGP is a bit of a mess already. It's tough to install/maintain (because it has a daemon), and it's really easy to mess up. I think using something like NaCl could be much more difficult to mess up than automated PGP. --- Thanks again, everyone, for the thoughtful discussion. While I disagree on this topic, I'm very optimistic about and excited by the future of Gemini of a whole. Cheers! Aaron Janse
---
Previous in thread (7 of 17): 🗣️ solderpunk (solderpunk (a) SDF.ORG)
Next in thread (9 of 17): 🗣️ Sean Conner (sean (a) conman.org)