Sorry everyone for the slow reply. The forum was set to never email me and I didn't see any of this until today. That's fixed now.
And I owe you an apology for something else. Ponce-De-Leon is right, I should have said up front that I don't write the code. I'm not a programmer. TuxTalk is written by Claude. I design it, test it on a bunch of distros in VMs and use it for nearly everything I type, but the code is Claude's. Being a beginner doesn't mean I'm sloppy about it, though. I hold it to the standard an experienced developer would expect when they open the code: no leftover dead code, comments that explain why, no copy-pasted duplicates, and every change has to pass over 3,500 automated tests before it goes in. An outside developer reviewed the part that reads the keyboard. I'm still pretty new at putting something out in public and I got the disclosure wrong. The forum won't let me edit my first post anymore, so this reply will have to do, and I'll make sure I say it up front everywhere from now on. The project site is https://tuxtalk.app The speech models (Parakeet and Whisper) are AI speech models too, and they run entirely on your computer.
Forpli, you're right to be careful about the input group. Being in that group lets any program you run read the keyboard, not just TuxTalk. That's how 0.15.1 worked and it's why I changed it. 0.16 came out on the 18th and it doesn't need the group anymore. A small helper service reads the keyboard and only tells TuxTalk about its own hotkeys, and an outside developer reviewed it. It also works without the reboot, which is probably why F8 did nothing in your live session. If 0.15 already put you in the group, 0.16's Preferences offers to take you back out.
JustZorin, you're right that removing it left things behind. apt only takes out the program itself, not what TuxTalk set up when it ran. I'm sorry about that. Here's how to clean up everything 0.15.1 added. Quit TuxTalk from its menu first, then:
sudo apt remove tuxtalk
systemctl --user disable --now ydotoold.service
rm -f ~/.config/systemd/user/ydotoold.service
sudo rm -f /etc/udev/rules.d/99-talktype-uinput.rules
sudo gpasswd -d $USER input
rm -f ~/.config/autostart/tuxtalk.desktop
rm -rf ~/.config/tuxtalk ~/.local/share/TuxTalk
rm -rf ~/.cache/huggingface/hub/models--istupakov--parakeet-tdt-0.6b-v3-onnx ~/.cache/huggingface/hub/models--ggml-org--parakeet-GGUF
gnome-extensions uninstall talktype@ronb1964.github.io
The last line only matters if you installed the GNOME extension. Log out and back in after, so the group change takes. The "already running" message after your reboot was most likely TuxTalk starting itself at login from that autostart file, and the steps above take care of it.
I'm adding a proper uninstall to the next version so it cleans up after itself, and putting these steps on the website.
Thanks for actually trying it and telling me what was wrong. That's worth more to me than anything.