Follow

@enigmatico technically the left one is not web design as it's text/plain and not text/html

@sneak @enigmatico The early web was like that! Not just http/https, but Navigator (and other early browsers) also supported gopher and ftp as protocols. (Do I perhaps remember wais also?) gopher seperated links into separate menu types, so a person would have found that page from a menu (which could have links to other servers).

The web was about coalescing information into a single form. HTML was part of it but not the whole picture!

@jgoerzen @enigmatico i disagree. the defining feature of the web (not http!) is hyperlinks, the connection of any text on any page to any other page. that's where the term "web" comes from. text/plain does not support hyperlinks, therefore text/plain served over HTTP is not "the web".

@sneak
You can't follow any text at any time. You have to craft a link. Not every text on a page is a link.
Gopher just listed all the links as a menu, like a more traditional (and that doesn't mean wrong) Table of Contents or Glossary.
Web has a way to indicate them as a "clickable" or "pushable" text entries withing the text, nothing more. Semantically it is the same.
@jgoerzen @enigmatico

Sign in to participate in the conversation
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!