@mos_8502 Maybe framing it in terms of permacomputing or technological accessibility is better than focusing solely on retrocomputing.
Top-level
@mos_8502 Maybe framing it in terms of permacomputing or technological accessibility is better than focusing solely on retrocomputing. 9 comments
@msavoritias @csepp Gopher doesn’t specify a text encoding. Accessibility is the operating systems’s job. Retro computers have… somewhat limited options there. Although I imagine a serial braille display could be made to work with most of the text based ones. i was talking about urls too for unicode. Accessibility is not necesserily the systems job. it can be made easier with alt text for example on websites. or captions. @msavoritias @csepp I’d be interested in how you’d apply that to an 80x24 cell character display with a fixed 256 character font. fair. thats the same problems i have with irc btw. Its lightweight sure, but not as accessible as #xmpp is for example. Which as it was pointed out I would like to move from a mentality of old was better or just retrocomputing. To one that is more about bringing the modern #accessibility guidelines into a stack that is lightweight like retrocomputing. @msavoritias @csepp I would wager that those goals are a bit at odds. Accessibility is inherently complex, as different people have very different (perfectly legitimate) needs, and a lightweight approach practically insists on a one size fits all solution. |
@csepp @mos_8502
that was my thinking too.
Does gopher support UTF or accessibility?
If not its very excluding and it should evolve to do so.