I am sure a certain potential future governor of texas approves. On a serious note though, ideology aside, the internet hardly needs another encryption protoco

I am sure a certain potential future governor of texas approves. On a serious note though, ideology aside, the internet hardly needs another encryption protocol. The problem with these approaches is they try to solve everything. Unix and interner philosophy of layered piping (compartmentalization) exists for a reason. How do you establish trust? TOFU? Your app is broke from the start! How do people on the internet establish the other anonymous person is really their anonymous person? Censorship resistance? Hah! How do you dynamically find network access nodes or peers without getting blocked? HTTPS? Well they decrypt that and you shouldn't rely on non-E2EE stuff for such reasons? Does the network rely on domains? Does your app rely on domain names to be found and installed+working? They can block domains and block you in app stores. Domain front? Russia was blocking entire /8's of google and aws because of apps like Signal. This is why you solve problems one layer at a time. All of the problems are listed (and more) require a unique standardized protocol solution that interoperates with other layers. I said ideology aside earlier so let me bring it back and say this: it is a mistake to create any communication system that is censorship resistant but also lacks practical ways to moderate harmful content. This was something I was very passionate about then I decided I don't want to help build something that can be abused and things that censor are not going to be used by most people anyways so no point.