I am working on some Gemini related stuff (the protocol, not Google AI) and would be interested in hearing about how Gemini stacks up from an accessibility perspective. Are there any specific clients or screen readers that work best? Is there any specific Gemini formatting that helps or hinders? Is there any accessible-specific content that you think should be made available via Gemini?
On a related note, am I wrong in thinking that Gemini is well suited to a low/no vision user? And if so, why?
While not applicable in all scenarios, one solution is to leave this whole polluted protocol behind.
Check out #geminiprotocol with gmi.skyjake.fi/lagrange/
The experience is like early web, in a good way.
The Gemini protocol is a lightweight alternative to HTTP positioned as a spiritual successor to Gopher. One drawback is that without reuse of TCP connections, every navigation takes several seconds on geostationary satellite Internet.
Read what curl maintainer Daniel Stenberg (@bagder) thinks of Gemini
daniel.haxx.se/blog/2023/05/28…
#GeminiProtocol #satellite #Gemini #curl
There is again a pull-request submitted to the curl project to bring support for the Gemini protocol. It seems like a worthwhile effort that I support, even if it is also a lot of work involved and it might take some time before it reaches the state …daniel.haxx.se
On Sunday 25 February 2024 I have to change the certificates of my Gemini capsule. You can accept those new certs (despite the red warning popup in your gemini browser), there is nothing suspicious going on. This is because of a server change from gmid to gemserv by int80h.
Here is an article going into more detail:
redterminal.org/gemlog/2024-02…
gemini://redterminal.org/gemlog/2024-02-20-Certificate_change_on_Sunday_25_February_2024_on_redterminal.org.gmi
Boost appreciated!
