clintfred

That was fun. That whole left side has a lot of suspicious lighting, doesn't it?!

Every government wants to ban E2E encryption, but most know that it isn't feasible to do so.

Not OP, but I'm going to guess because it's an added dependency in your client library, and even worse, it includes some code generation in each client's build.

It's not sad. You have identified a problem in your life! That's awesome. No one has a life with no problems, so you're like the rest of us humans. Now you can decide how you are going to change your behavior. You might consider talking to a friend or maybe a counselor to help you identify changes and unhelpful thinking patterns.

Thanks for all the thought you put into this post.

While I think some of your points have value, I'm not sure this is best time/place to have this discussion. Perhaps /r/rust or a blog post might allow you to have the discussion you are hoping for.

We built ironhide https://github.com/IronCoreLabs/ironhide to help developers share secrets with each other and with CI.

I posted elsewhere about https://github.com/IronCoreLabs/ironhide a tool purpose built for sharing developer/CI secrets.

https://github.com/IronCoreLabs/ironhide is a tool we built for managing our own developer secrets. It allows encrypted files to be checked in to git or stored elsewhere. You can think of it similar to gpg, with the upside that ironhide has the ability to change who can decrypt the secret without re-encrypting the data.

Check it out and if you have any questions, feel free to ask here or open an issue in github. We also have a Rust version in the works for those interested in something native.