1 |
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ |
2 |
On Thursday, September 3, 2020 6:50 PM, John Blinka <john.blinka@×××××.com> wrote: |
3 |
|
4 |
> Hi, Everyone, |
5 |
|
6 |
hello big dawg! |
7 |
|
8 |
quick point: imo the problem of gray texts on |
9 |
white backgrounds, or scrollbars or whatever, that |
10 |
you have, is not related to aging. imo it's |
11 |
rather related to stupid web developers. not even |
12 |
a mutant with infrared vision can use these |
13 |
websites. |
14 |
|
15 |
|
16 |
> 1) How do you cope with this problem? |
17 |
|
18 |
i cope by these: |
19 |
|
20 |
- use pixel-based fonts for everything as much |
21 |
as possible, specially for key apps like: |
22 |
terminal, window manager and browser. |
23 |
|
24 |
they become so much readable. i use |
25 |
"terminus-font" (and previously used "dina") |
26 |
in my urxvt as well as my other apps as much |
27 |
as i can. |
28 |
|
29 |
i notice one of the major problems with |
30 |
fonts is actually not our eyes, but in many |
31 |
cases how fancy fonts blur. i was |
32 |
personally amazed by how i could use much |
33 |
smaller fonts, while maintaining |
34 |
readability, by simply switching to |
35 |
pixel-based fonts, such as terminus. |
36 |
|
37 |
- for my browser, i use custom user css for |
38 |
different modes. i also configured |
39 |
shortcuts for my browser, so that i change |
40 |
these user css files based on which ones |
41 |
work best with the site. generally, i have |
42 |
"night.css" and "wiki.css" that i change by |
43 |
keyboard shortcuts. the "night.css" is very |
44 |
generic and changes background/foreground |
45 |
texts for pretty much 90% of sites properly. |
46 |
|
47 |
this way, i am no longer bound by bad colors |
48 |
chosen by web designers. |
49 |
|
50 |
- i use i3 as window manager, with lots of |
51 |
shortcuts. i also use qutebrowser (a |
52 |
browser with good vim shortcuts). |
53 |
|
54 |
this way, throughout the day, i rarely end |
55 |
up needing to use the mouse to do things. i |
56 |
only use the mouse for ultra quirky websites |
57 |
with fancy javascript links that are not |
58 |
clickable by qutebrowser's shortcuts. |
59 |
|
60 |
so thanks to using keyboard shortcuts, a |
61 |
website can have thin gray scrollbar on a |
62 |
gray background and i don't care. because i |
63 |
scroll by shortcuts, not by bars. in fact, |
64 |
my qutebrowser's interface has scrollbars |
65 |
disabled altogether to use pixels, which i |
66 |
paid dear money for, for real use. |
67 |
|
68 |
|
69 |
> 2) Is there an xfce theme and icon package you |
70 |
> recommend? Or maybe something other than xfce? |
71 |
> I like xfce, and have never been attracted to |
72 |
> integrated desktops like kde and gnome, but if |
73 |
> they’ve got a credible solution, I’m willing to |
74 |
> try. |
75 |
|
76 |
i would suggest try keyboard-based window |
77 |
managers. my 1st suggestion is i3. it's actually |
78 |
perfectly usable for all applications. it's |
79 |
tiling-based, but also has floating functionality, |
80 |
and does a fine job eliminating need of clicking |
81 |
around on tiny things. |
82 |
|
83 |
> 3) Are there lower level ways of tweaking my |
84 |
> current desktop? For example, changing colors |
85 |
> in the 2 examples I gave above from black on |
86 |
> dark gray to black on white? Could that be done |
87 |
> with a little judicious editing of color |
88 |
> settings somewhere, or adjusting colors on an |
89 |
> icon? I don’t know how desktop appearances are |
90 |
> programmed, so I don’t know where on the |
91 |
> spectrum of trivial->apocalyptic this lies. |
92 |
|
93 |
user style sheets. maybe have a look here |
94 |
(i also talked about it above): |
95 |
https://userstyles.org/styles/browse/css |
96 |
|
97 |
or, if you dislike fiddling with these, maybe some |
98 |
use some browser add-ons that offer things like |
99 |
"night mode", or "contrast mode", by which they |
100 |
apply their own custom styling to fix mistakes of |
101 |
web designers. |
102 |
|
103 |
|
104 |
------------------------------------------------- |
105 |
optional/offtopic: extra text if you have coffee |
106 |
------------------------------------------------- |
107 |
i think this problem that we have could've been |
108 |
avoided if the web was originally designed to only |
109 |
deliver content, without any power to dictate |
110 |
appearance, so that appearance is 100% a task that |
111 |
a local client should choose. |
112 |
|
113 |
imo this could've been done easily, because |
114 |
websites in the internet follow a finite number of |
115 |
"document classes" (if we call them so). the vast |
116 |
unique changes that web designers make are just |
117 |
pointless. |
118 |
|
119 |
if the web was designed this way, then today we |
120 |
would've had a much happier time of achieving 100% |
121 |
consistent look for all websites optimized for our |
122 |
readability. but too bad, that is not done, so we |
123 |
have to use custom user style sheets which works |
124 |
for most of the time. |
125 |
|
126 |
for people who really want js and fancy rendering, |
127 |
they could use a separate app for their "instant |
128 |
js games". there is absolutely no reason why the |
129 |
entirety of the web has to be so turing-complete |
130 |
just because someone wants to play games. |