Step one for my audio-only setup is done. I can have audio (and speech-dispatcher) running without a graphical session. Next I'll either keep banging my head trying to get these TTY screen readers to work or make my own one.
@TheQuinbox Haven't tried that yet! So far I've just used espeakup and fenrir. I just couldn't get espeakup to work at all and fenrir kinda worked but then stopped. 😅 Everything is more annoying on an ARM SBC.
@TheQuinbox Wow, this is great actually! I accidentally set the rate to `1` which is causing a sort of denial of service attack on my brain with how slow it is. 😂 Do you have your configs published for this that I could take inspo from?
@mauve Hit alt c, then r, and type a new rate value. My config is honestly pretty much entirely stock, I turn off line pause, alt+c then l, but the most customization I do is with the speech server. I have TDSR running on a beelink mini pc sitting over on my desk, hooked up to tailscale. I ssh in with putty, run tdsr, which is an alias to uv run my tdsr with -s socket.sh, where socket.sh is just: exec -a tdsr-server socat - TCP4:"$(echo "$SSH_CONNECTION" | awk '{print $1}'):10001",nodelay. I have a custom port to deal with Windows weirdness, the default is 64111. Then, I run a little Rust server I and a friend wrote, and TDSR is speaking to NVDA over the tailnet!
@TheQuinbox That's so fancy! Am I understanding correctly that it's using NVDA as a speech dispatcher backend over the tunnel?
@mauve what screen readers have you tried? My personal favorite and the one I use every day is TDSR, https://github.com/tspivey/tdsr