Re: "I think when making a nex request, Lagrange (Linux version)…"
In: s/Lagrange
@skyjake : "I don't think there are queries in Nex, just paths...?"
There's no defined mechanism for input, so a ? wouldn't play the same role in nex as it does in Gemini. The specification, such as it is, says that the client sends "a path, which might be empty". Problem is, it doesn't say what a "path" amounts to, formally.
Oh, well. It's not important, just an oddity.
@balloon : "That's the job of Nps"
What's Nps? Sorry if I'm being dim.
🚀 lars_the_bear [OP]
May 20 · 3 days ago
🌆 skyjake [mod...] · May 20 at 07:13:
The Nex spec doesn't really say anything about Nex URIs, but logically, the URI path component is the Nex path being requested.
If Nex is a GET request, then NPS is a POST:
— nex://nightfall.city/nps/info/
🎈 balloon · May 20 at 09:03:
Yes, Nex and Nps are like Gemini and Titan. Nightfall City uses this to receive information from users. You'd better take a closer look at Nightfall City a little more.
Perhaps this is because it is not considered by clients other than Lagrange. What you're trying to do should get an unexpected response.
🖥️ mrrobinhood5 · May 20 at 22:10:
@balloon I made a python next server on github with this same username. It runs nex.inkverse.space
🐙 norayr · May 21 at 07:09:
it doesn't lookup, i think you meant
— nex://inkverse.space
🖥️ mrrobinhood5 · May 21 at 16:16:
@norayr absolutely right 👍🏽 thank you.
Original Post
🌒 s/Lagrange
🚀 lars_the_bear:
I think when making a nex request, Lagrange (Linux version) doesn't seem to send the query string (the bit after "?") of the URL over the wire. Is that intentional? Or am I missing something?
💬 8 comments · May 19 · 3 days ago