In elaborate terms: you have the ability to change any one of the protocols, specifications, designs or standards of the above at their proposal stage or before their mass adoption. You may choose to modify or reject an existing one or create one by yourself.
Some users and I would have common ideas in mind, however I would love to see some esoteric ideas as well.
Make it so that security is a priority when developing a standard, protocol, or specification. Even at present, new stuff is developed for functionality first, with security coming in later. IMO they should be developed in tandem, secure by design.
Definitely. Insecure protocols linger on for ages even after we have better options. The internet used to run on unsecured HTTP, FTP, and Telnet, and it took decades for their encrypted successors to make headway and become the default.
I think email is the last major old protocol that’s still blatantly terrible, but it’s too deeply entrenched/too decentralized to do anything about.