Comment by 🚀 clseibold
Re: "Could somebody please check this page in Lagrange: [nex…"
@skyjake Ah, right, yeah. Forgot about that part of the nex specs, lol.
@ps Yeah, slash at the end means its a nex index, no slash means its plain text or a file.
(Sidenote: I really wish nex would have defined a proper mimetype and extension for the nex index format!)
For the links inside the nex index document, a slash at the end means its linking to another nex index document. No slash means its linking to a file via the extension. And typically files without an extension are considered plaintext files.
🚀 clseibold [🛂 Code of Conduct rule 1 violations]
2025-06-26 · 10 months ago
4 Later Comments ↓
🚀 clseibold [🛂] · 2025-06-27 at 04:18:
I believe nex does have one exception: files named "index", and thus URLs ending in `/index`, are nex index documents and *should* render links, afaik.
🌆 skyjake [...] · 2025-06-27 at 05:46:
@clseibold That sounds like server-side behavior that a client would not be privy to. There is no mention of such files in the (admittedly very terse) Nex protocol specification.
🚀 clseibold [🛂] · 2025-06-27 at 06:08:
@skyjake Oh! I'll have to check the nex spec again. I thought it did talk about it.
🚀 clseibold [🛂] · 2025-06-27 at 06:14:
@skyjake Also, to be fair, clients would know about "index" files in the same way that webbrowsers know about "index.html" files and gemini browsers would know about "index.gmi" files. "index.extension" is a pretty widespread standard (even if just de facto) for all three protocols (except nex doesn't use the extension) when you want to create the "index" file of a directory. And you can link to these index files.
It's particularly important for crawlers, where when they happen upon such an index file, they remove that part of the url so that you aren't getting duplicate pages in your database.
Original Post
Could somebody please check this page in Lagrange: [nex link] I can't understand why does it ignores links there, is this a bug or some plain/nex markdown feature?