Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.infosystems.gemini > #164

Re: In the news

Show all headers | View raw

David <david@arch.invalid> wrote:
> Indeed! Suppose Gemini built on HTTP(S) instead of the current TOFU 
> approach, and used AsciiDoc, MarkDown or whatever as a default text 
> format ...
> - Would http(s):plain/markdown have a catchy name, say Mercury?
> - Would such beautiful clients exist like Amfora and Lagrange?
> - Would there be concerns about privacy that do not exist with Gemini?
> - Would there be a tangible community around it, a Wikipedia page?
>    This newsgroup?

I suppose it is possible. It does not need its own URI scheme; the existing
"http" and "https" schemes will work. It can still be given its own name,
instead of "WWW", but does not need its own URI scheme.

However, the existing Gemini is good enough, instead of adding many things
that are not needed. Better is to just design better protocols/formats
but other ways can be work, too.

Near the end of article <1643573802.bystand@zzo38computer.org>, I mentioned
a way in which t could be implemented without too much difficulty even in
future versions of existing web browsers (hopefully), but would also be
possible to make the simpler client implementing only a subset of the
features and still have better user customization, etc; in this way, the
protocol becomes interoperable.

Interoperable protocol is not the only way to do, but it is one way. I
still think that the separate protocol/format (like Gemini is, although
there are some things I would have done a bit differently) would be better,
but that will not always be compatible.

(Of course there are still many problems with the commonly used protocols
and formats, but it is possible to make data/services available with multiple
protocols and/or file formats, if wanted, too, just as well as programs can
be available for multiple kind of computers, etc.)

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

Back to comp.infosystems.gemini | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

In the news David <david@arch.invalid> - 2022-01-29 19:07 +0100
  Re: In the news rtr <rtr@haraya.invalid> - 2022-01-30 08:22 +0800
    Re: In the news David <david@arch.invalid> - 2022-01-30 11:02 +0100
      Re: In the news news@zzo38computer.org.invalid - 2022-01-30 18:51 -0800
      Re: In the news rtr <rtr@haraya.invalid> - 2022-01-31 07:43 +0800
        Re: In the news Dan Purgert <dan@djph.net> - 2022-01-31 10:16 +0000
          Re: In the news Jeremy Brubaker <jbrubake.362@orionarts.invalid> - 2022-01-31 14:01 +0000
            Re: In the news Dan Purgert <dan@djph.net> - 2022-01-31 15:56 +0000
            Re: In the news rtr <rtr@haraya.invalid> - 2022-02-01 10:12 +0800
          Re: In the news rtr <rtr@haraya.invalid> - 2022-02-01 10:10 +0800
            Re: In the news Dan Purgert <dan@djph.net> - 2022-02-01 09:42 +0000
    Re: In the news oldernow <oldernow@dev.null> - 2023-12-18 19:55 +0000
      Re: In the news Kestral Gaian <kes@kesgai.com> - 2023-12-22 00:23 +0000
        Re: In the news Denez Van Dyck <denez@vandyck.invalid> - 2023-12-22 08:28 +0000
        Re: In the news oldernow <oldernow@dev.null> - 2023-12-26 20:28 +0000
          Re: In the news John <john@building-m.simplistic-anti-spam-measure.net> - 2024-01-09 16:27 +0000
            Re: In the news SugarBug <3883@sugar.bug> - 2024-01-09 12:18 -0600
            Re: In the news oldernow <oldernow@dev.null> - 2024-01-26 14:01 +0000
              Re: In the news John <john@building-m.simplistic-anti-spam-measure.net> - 2024-01-26 18:09 +0000
                Re: In the news oldernow <oldernow@dev.null> - 2024-01-27 19:31 +0000
                Re: In the news news@zzo38computer.org.invalid - 2024-01-28 10:53 -0800
          Re: In the news news@zzo38computer.org.invalid - 2024-01-09 14:23 -0800
  Re: In the news Ben <benk@tilde.team> - 2022-01-30 14:43 +0330
  Re: In the news bunburya <bunburya@tilde.club> - 2022-01-30 12:53 +0000
    Re: In the news rtr <rtr@haraya.invalid> - 2022-01-31 07:43 +0800
      Re: In the news bunburya <bunburya@tilde.club> - 2022-01-31 11:13 +0000
        Re: In the news Jason McBrayer <jmcbray@carcosa.net> - 2022-01-31 09:42 -0500
          Re: In the news !nv4l1d <invalid@invalid.com> - 2022-02-01 03:06 +0000
        Re: In the news rtr <rtr@haraya.invalid> - 2022-02-04 15:26 +0800
    Re: In the news Christian Seibold <krixano@mailbox.org> - 2022-01-31 16:06 -0600

csiph-web