What if the problem statement (what is something like this trying to solve) is: 1. No tracking beyond what the server gets via standard logging 2. Document sty

What if the problem statement (what is something like this trying to solve) is: 1. No tracking beyond what the server gets via standard logging 2. Document styling control in the hands of the user agent 3. Navigation control in the hands of the user agent 4. Compatibility with existing web browsers would be a bonus Points 2 and 3 imply some kind of semantically-clear markup. Would definitely want to think of forward/backward compatibility (something the web has been fairly good at). Point 1 means no cookies, likely nothing like JS, images need to come from the same server (either packaged in the initial request or forced to come from the same host). Point 4 is a nice to have and may be possible if this is built on a subset of HTML and HTTP. One possibility is that if the server receives a request that looks like it's coming from a standard browser, it can serve up the page with some JS and CSS that fill in the stuff that would normally be done by the user agent. IMHO, something built on a stack that looks like that would be a better fit for 2020 than something based off of Gopher's approach.