 Gmer4Lfe
|
2ccc93bb14
|
Send a bug report to one place, on purpose, after reading it
The page built its own markdown and nothing could send it; local and upstream
are different people, so neither falls back to the other.
|
2026-08-13 16:32:36 -04:00 |
|
|
Gmer4Lfe
|
e64d26af6c
|
Put each page's settings on that page
A watchdog threshold was reachable only from the bottom of a list of a hundred
and twenty on another tab.
|
2026-08-12 19:55:51 -04:00 |
|
|
Gmer4Lfe
|
8ca52c64b9
|
Give the rest of the conf a place to be changed
A third of the settings had no control anywhere, so the answer to "where do I
change this" was to open a file over SSH.
|
2026-08-12 19:41:01 -04:00 |
|
|
Gmer4Lfe
|
a04368e9fc
|
Notice when the question is about their own machine
The other detector recognises named components, so its complement is unbounded;
this one reads grammar instead, which is not.
|
2026-08-12 18:08:50 -04:00 |
|
|
Gmer4Lfe
|
c33f3c067b
|
Lead with the route, since that is what was asked
Naming the conf file first got answers that sent people to edit host1.conf and
mentioned the tab afterwards.
|
2026-08-12 17:19:07 -04:00 |
|
|
Gmer4Lfe
|
240876e710
|
Tell the assistant where the settings are, not just what they are called
The index reads tracked files and page markup is not one, so it could name a
conf key and never say there was a button for it.
|
2026-08-11 22:07:10 -04:00 |
|