Comment by 🌆 skyjake
Re: "Could somebody please check this page in Lagrange: [nex…"
@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.
2025-06-27 · 10 months ago
2 Later Comments ↓
🚀 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?