>>1071629
This.
some concepts:
>plain text
Theming is an end-user choice, websites should not force themes upon the user. The only noble goal a website theming by itself could possibly have is to give the user a consistent theme across websites, but that's impossible without having no theme at all and letting the user theme every website themselves, which is the ideal anyway.
html's fancy formatting never solved the problem of making things look good or consistent across screens, in fact, it has actively sabotaged any attempts at achieving this goal.
No other document format has achieved it either. If we're going to bloat things up with some formatting only to shoot ourselves in the foot with it, give up on the concept entirely, and make things text.
>not executable
If a website contains software, then it is malware, no exceptions. Web pages must be parsed only.
>forms
The only time the browser should send data back to the server beyond the bare minimum required for the initial download of the web page is when the user filled in a form manually. This means no headers/trackers/cookies/whatever botnet. Talking to the server behind your back is botnet.
>encryption
No unencrypted connections. No censoring and cianigger certificate authorities. The user chooses if they trust the certificate or not. If someone else is choosing whether you trust a certificate or not then you got pwned. Use gpg for verifying the identity of the website and encrypting the symmetric encryption negotiation with something else. I haven't touched anything SSL-related but if it's good then it can be that.
>modularity
The actual software used to achieve all this should be standardized swappable, but at the very least known botnet should be forbidden. Any software I mentioned is only a suggestion, ideally the only non-swappable program in all of this is a protocol used to negotiate the software used for all this. Monopoly through non-standardization and non-modularity is communism, communists deserve to die, and their behavior halts progress. If a website wants to use sftp, gopher, rsync, or whatever else to send and receive data, then it's their choice and up to the user to deny or allow it. In such an environment every website would support anything in an attempt to lure in more users anyway.
Also I get that you can't have forms in plain text and forms is something only http has, but in that case we serve forms separate of the plain text, and something to talk to a server behind a file transfer protocol should be invented.