I liked this post by rlamacraft:
gemini://gemini.rlamacraft.uk/replies/reframingThePhilosophyOfGemini.gmi
Have to disagree with Drew here. Gemini is decidedly not a read-only distribution protocol. (As evidenced by what we're doing right here.) There is a little more nuance to it: I would call it a balance of 80/20 in favor of reading. Writing is possible, and even secure thanks to client certificates, but not as convenient as reading.
So this means, if in doubt, focus on the read direction, but completely ignoring the write direction unnecessarily excludes a lot of cool potential.
3 years ago · 👍 ttocsneb, krixano, thatsredadcted, gnuserland, mozz, devyl, martin, negepezzannyitfiam, kensanata, moddedbear
gemini://gemini.rlamacraft.uk/replies/reframingThePhilosophyOfGemini.gmi
@mozz Your comment got me thinking about ANSI styling: gemini://skyjake.fi/gemlog/2021-11_ansi-sgr.gmi · 3 years ago
gemini://skyjake.fi/gemlog/2021-11_ansi-sgr.gmi
I use Gemini to monitor some of my servers RAM. Each server sends the total RAM used by programs and the name of the program using the most RAM.
My router (ER Lite so no RTC) use Gemini to syncronize the clock on start (usually after power cut) with a RB pie that have a RTC. In this case the capsule only display the date, but the output is the input for the router. Even if Gemini was a "display only" protocol that information is going to be an input to the reader.
There is a company that sell sensors that use Gemini. I don't know if they send the data to a Gemini server or if the just display the data. You can do a lot with 1024 characters. · 3 years ago
@mozz Honestly I don't know, there are some capsule that accept "raw" input but might be the ones that you already cited. · 3 years ago
@gnuserland So far, the strategy has overwhelmingly been to just use INPUT and accept the 1024 byte limitation. What capsules (besides titan:// and alex's wiki) use complimentary protocols for upload? · 3 years ago
I like that post too! I think the whole “content vs presentation” debate has fallen into the same trap. Gemini doesn’t have colors/stylesheets because adding them would have been too complex, *not* because of some dogmatic return to early web principles. · 3 years ago
The interactivity with content is the major pain of WWW, I understood why has been designed with stricly rules. So far the strategy has been creating a complimentary protocols, which is for certain extents cheating.
I consider Gemini also as a mean to preserve digital documentation in a way that is more resilient than, HTML/HTTP, since GMI can be read as simple text file, and since the moment the protocol will not be extended you already know your documentation will be readable from now to the far future. · 3 years ago
Drew uses a negative connotation for reading, as it was a bad thing. Gemini is, in my vision, a protocol to share a reading contents primarily.
However what other folks were able to get within the boundaries is amazing. Lagrange makes looking Gemini just cool and modern, Station is spectacular. · 3 years ago
I agree, and in fact, I think Solderpunk's earlier articles (like the one on Input and Input Prompts I posted on Station) shows that he intended Inputs to be used for more than just searching - to be interactive. Read-only was never a priority for the Gemini protocol, from what I've seen and read. Of course, this doesn't mean Solderpunk couldn't change his mind now. Solderpunk also had this really good post on Gemini Applications that I've posted before too. · 3 years ago