> even small web utility, you do want a defined subset of HTTP/(X)HTML. Maybe to make a small web HTTP, servers can reject clients that e.g. send user agents, a

> even small web utility, you do want a defined subset of HTTP/(X)HTML. Maybe to make a small web HTTP, servers can reject clients that e.g. send user agents, and clients can refuse to render pages that contain a script tag. For a "small web HTTP", see also: https://news.ycombinator.com/item?id=40980870 https://news.ycombinator.com/item?id=40980870 I think it is not necessary for servers to reject clients that send a User-Agent header. I also think that HTTP and (X)HTML is not good for everything. Although they are excessively complicated, and a defined subset would help, still there are some complexities and other problems, I think. > Spartan and Gemini are so similar they shouldn't need to be different protocols. I also agree, although each has different problems (some are shared with both). (I think it is helpful to allow both TLS and non-TLS, although Gemini is only TLS and Spartan is only non-TLS.)