💾 Archived View for bbs.geminispace.org › u › clseibold › 6262 captured on 2023-11-14 at 09:50:04. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-11-04)
-=-=-=-=-=-=-
Re: "How does Gemini differ from the Nex protocol? I see Nex..."
Well, the protocol is completely separate from the "simple server executable". Whether a server is just a simple executable is dependent on the server software, not the protocol. Anyways, yes, it is just a "simple server executable", both my server and the ones that are provided by nightfall. You run it and it just serves whatever is in your nex folder.
As for the way nightfall's interface is displayed, that is how all nex sites display. That's why I said the presentation of nex is different from gemini. Gemini is more focused on being a hypertext document format, like a very simplified html, while *nex is not.*
Spartan is very different from nex. Spartan has upload and error status codes, etc. That's why Nex is more like a simplified gopher without all the cruft.
You can find nex's spec here. There is also an http version if you just replace "nex://" with "http://" in the link below.
The hidden file .directory-listing-okay in Gemini does what I need as far as directory listings are concerned.
This is not actually part of Gemini, this is a functionality of your server software. I might be nitpicking here, but it's an important distinction because you won't find this feature in every gemini server software.
Oct 16 · 4 weeks ago
How does Gemini differ from the Nex protocol? I see Nex used for directory listings and serving files. Gemini seems to do this and much more. Is it as simple as that?