Oooooooh. Look guys, I'm sorry for not keeping up with the discussions. However the technical side, in spite of best efforts, kinda flies over my head. So the fact gemini clients have user-definable EVERYTHING is honestly a huge win in my book. I prefer dark background/light text. Other people with low vision like blue background with white text (personally I don't get it, but eh.) Others like a beige/cream background with dark text. The 'let the end user define what page elements present as' is honestly a step forward, especially with the idea of gemini being a middlepoint between gopher and full blown html. However I was viewing through a traditional browser, so I'm unsure how to square that problem. On 10/21/20, James Tomasino <tomasino at lavabit.com> wrote: > On 10/21/20 2:16 PM, Leo wrote: >> If we are disregarding user agents being able to pick colours as a valid >> thing to do, should we also add styling to the Gemini document format so >> content producers can make sure their text is displayed correctly and is >> accessible? > > It's the lack of styling in the gemini document format working in our favor. > On http browsers pass the buck for styling saying it's the content author's > responsibility. In gemini we can do away with that nonsense and build > clients better. Accessible clients are first-class citizens. > >
---
Previous in thread (15 of 19): 🗣️ James Tomasino (tomasino (a) lavabit.com)
Next in thread (17 of 19): 🗣️ zephryn (zephryn (a) owlsne.st)