Comment by 🕹️ skyjake

=> Re: "Input indicator" | In: s/Gemini

The extra dashes added into the links in preformatted blocks above have now been fixed.

=> 🕹️ skyjake [mod, sysop]

2023-08-30 · 1 year ago

2 Later Comments ↓

=> 🧇 Acidus · 2023-09-15 at 20:13:

Honestly, this feels best handled by the client:

1. They can have a setting like what @skyjake is suggesting for Lagrange and spellbinding. Basically: "This URL needs input, so always proactively prompt me for it"

2. Support Spartan-style link lines. Kind of like how some capsuel games offer a "ANSI mode" or "plain text mode", they could offer a "Spartan link" mode

=> 🐐 drh3xx · 2023-09-18 at 12:21:

Although adding to the gemini spec would break handling of new content in clients which had not been updated to support it... a 2nd link markup of ?> or =? to signifying a link expecting data from a prompt seems reasonable. Easy to add to content, no scope for Link markup creep or add further checks to URL handling. Adding support would be a minimal patch for existing clients - to support the links with existing behaviour would just be an additional case match with fallthrough to the exiating code in C. Proper support shouldn't be much more work unless I'm missing something. It would also allow advanced clients to add support for inline text entry + 'submit' button should they want to.

Original Post

=> 🌒 s/Gemini

Input indicator — I'm thinking again about something which has come up a few times before, which is how to deal with the annoyance that requesting input on gemini involves two requests -- the first to get a 10 response with a prompt, and the second for the actual input. The first is often not really necessary, and could be eliminated if there were some way to signal to the client that a link will expect user input. That extra request is wasteful and can be genuinely annoying -- I was prompted...

=> 💬 mbays · 15 comments · 2023-08-28 · 1 year ago