3 ms·
"This requirement seems poorly thought out, especially considering the Gemini protocol doesn't even support forms (other than a single text box on a search form
by 1vuio0pswjnm7 6y ago
"This requirement seems poorly thought out, especially considering the Gemini protocol doesn't even support forms (other than a single text box on a search form) so there's no chance of users submitting private data, and there's no mechanism for client-server sessions so clients can't be authenticated, meaning everything served pretty much has to be public anyway."
No chance? Everything has to be public? WTF? How does he arrive at this conclusion?
In Appendix 1 of the Gemini protocol one of the status codes is "SENSITIVE INPUT". It specifically gives the example of passwords.
One of the error codes in the Appendix is "CGI ERROR". This would seem to contemplate generating content dynamically, e.g., a user submitting ad-hoc queries to a database.
I would love it if all websites did not force the use of TLS and provided a plain HTTP option, but there are easier solutions for older computers than trying to get the web to change. (Good luck with that.)
One solution to to use a gateway the user controls, sitting between the vintage computer and the internet.
One can run a proxy on the gateway and have control over changing/deleting request and response headers like Upgrade-Insecure-Requests, Upgrade and Strict-Transport-Security, and TLS offloading/termination.
It works for me. Both for older software and older hardware.