Re: "I've been trying to make my Gemini capsule available using…"
In: s/Alhena
@lars_the_bear I got it now! Alhena looks at extension to know how to handle what comes in (obviously). Because I was focused on that and not "/" strictly meaning text, I ended up "cornfused" (as they say in Nebraska). As a result, I put in a fix that breaks/expands the spec!
You see...
In my fix, "about.txt/" opens as text but "song.mp3/" will open the audio player. "video.mp4/" will open embedded video and so on. Thanks to deeper reflection and your post, I get why this is wrong even though it seems like it could be very useful. I should remove it, right? Right?
🛸 bluesman [mod]
May 20 · 2 days ago
🚀 lars_the_bear [OP] · May 20 at 12:41:
@bluesman : It seems to me that "song.mp3/" should be treated as a directory, and rendered as text, even though, as you say, that's hardly useful. But it seems to me that there's no good reason for a server or author to present a file _other than_ text as if it were a directory.
Dealing with issues like this make me realize how well thought-out Gemini is, despite its flaws.
🛸 bluesman [mod] · May 20 at 13:15:
@lars_the_bear Yeah. I pushed the "fix" so things work as intended by the Nex Consortium. Thanks.
Original Post
🌒 s/Alhena
🚀 lars_the_bear:
I've been trying to make my Gemini capsule available using nex, because why not? Trouble is, nex is weird about where you can use link lines -- it's only in directories, i.e., paths ending in '/'. Since I didn't want to rearrange all my content so that it's organized into a directory hierarcy, I hit on the idea of having all filenames end in "/". Here's a example: [nex link] This works fine with Lagrange, but Alhena asks where I want to save the file, rather than displaying it. While I…
💬 10 comments · May 19 · 3 days ago