1. Forum
  2. Usenet
  3. COMP.INFOSYSTEMS

  • Re: web

    From yeti@21:1/5 to Ben Collver on Sun Jan 19 16:14:36 2025
    XPost: comp.misc

    Ben Collver <bencollver@tilde.pink> wrote:

    In short, gopher is not the web. It does not use the HTTP protocol,
    the HTML format, nor other web standards such as Javascript. Gopher
    is a separate protocol that is not directly viewable in mainstream
    browsers such as Chrome and Mozilla.

    I contradict.

    When browsers appeared, we thought of the web as what was accessible
    by them. FTP, HTTP and Gopher were among this in the early days.

    Gopher is not the web. Yes.

    HTTP is not the web!

    They just are part of the web.

    Today's big$$$-browsers converge to single protocol network file viewers
    and unluckily the smallweb browsers do too.

    Let's prefer multi protocol browsers and return to all goof stuff being
    just a click away from each.

    That was what the web was meant to be and we should make it exactly that
    again.

    First step: Prefer writing plugins for existing browsers over creating
    more single protocol file viewers.

    Writing plugins for Chawan (TUI) and Dillo (GUI) is easy. If you can
    say that about other browsers too, let's start a list/FAQ in
    comp.infosystems (the protocol independent group please) about it.

    --
    I do not bite, I just want to play.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From news@zzo38computer.org.invalid@21:1/5 to yeti on Mon Jan 20 11:23:24 2025
    XPost: comp.misc

    yeti <yeti@tilde.institute> wrote:
    When browsers appeared, we thought of the web as what was accessible
    by them. FTP, HTTP and Gopher were among this in the early days.

    Many browsers can also display local files (which is not internet), and
    many newer ones can display PDF files (whether or not they are accessed
    by the internet), too, though.

    Today's big$$$-browsers converge to single protocol network file viewers
    and unluckily the smallweb browsers do too.

    Some of the small web browsers do support multiple protocols and multiple
    file formats. Unfortunately the major web browsers do not support such
    things very well even if you add extensions, though; and they have many
    other problems too other than just this, anyways.

    Let's prefer multi protocol browsers and return to all goof stuff being
    just a click away from each.

    That was what the web was meant to be and we should make it exactly that again.

    First step: Prefer writing plugins for existing browsers over creating
    more single protocol file viewers.

    I think that it should be done, although you can still make up new browsers that may support such plugins too. I also think that the protocols and the
    file formats should be handled separately, so there will be one plugin for Gemini protocol and one plugin for Gemini file format (although they will probably be a part of the same package, since they are used together), and
    one plugin for Spartan protocol (which also uses Gemini file format so you
    do not need a separate plugin for Spartan file format), etc.

    --
    Don't laugh at the moon when it is day time in France.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)