💾 Archived View for rawtext.club › ~sloum › geminilist › 007202.gmi captured on 2023-11-14 at 08:46:46. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Stephane Bortzmeyer stephane at sources.org
Wed Sep 22 21:23:33 BST 2021
- - - - - - - - - - - - - - - - - - -
On Wed, Sep 22, 2021 at 06:45:57PM +0100, Alice <lia at loveisanalogue.info> wrote a message of 28 lines which said:
Would we want one general message for the domain (so not Gemini specific) or would we want a specific message per protocol ?
I'd go for simplicity (so message per domain, as you've done) but I guess some people might prefer the other way.
Well, port 443 to some.thing.example may go to a different machinethan port 1965, thanks to the various "routers" we have now, so thereis no reason they will share the same fate.
I suggest to get inspiration from the DANE protocol and to prefix thename with the port:
_443._tcp.some.thing.example IN TXT "The Web server works"
_1965._tcp.some.thing.example IN TXT "The Gemini server will be back at 21:00 UTC"