This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
ibus-speech-to-text will provide voice dictation capabilities to any application supporting IBus input methods in Fedora Linux 42, using VOSK for local voice recognition.
If you are in favor but have reservations, or are opposed but something could change your mind, please explain in a reply.
We want everyone to be heard, but many posts repeating the same thing actually makes that harder. If you have something new to say, please say it. If, instead, you find someone has already covered what youâd like to express, please simply give that post a instead of reiterating. You can even do this by email, by replying with the heart emoji or just â+1â. This will make long topics easier to follow.
Please note that this is an advisory âstraw pollâ meant to gauge sentiment. It isnât a vote or a scientific survey. See About the Change Proposals category for more about the Change Process and moderation policy.
I see that the documentation for the current version states that this runs entirely offline. Is there any danger that a future update might (accidentally or otherwise) start using online resources? Could the âofflineâ policy be enforced somehow (e.g. SELinux rules)? Maybe âofflineâ should even be part of the package name to make that explicit and, if anyone later wants to use some sort of online system, they would have to build a different package?
Hi @kevin , Currently ibus-speech-to-text is provided as an option, not installed by default and there is no plan to include it in the default Fedora installation.
I think we can consider this as more of a âTech Previewâ - it is probably not ready nor mature enough for general use, but still it is an interesting open project, which people can try out and hopefully could improve over time.
I donât know how to write such SELinux rules, but Iâve seen them work, so Iâm pretty confident it can be done. For example, someone once tried to add a custom Python script that would send them notifications via the online Pushbullet service, to the smartd service, but they kept getting the below SELinux denial.
SELinux was preventing the service that was running as fsdaemon_t from opening a TCP socket. Thatâs the sort of thing that I would like to happen if this new speech-to-text service were to try to route any data to any online service.
P.S. I personally think locking this service down is quite important and I wouldnât want to see it installed without such security measures. IMO, the potential of having an âopen micâ plugged into the world-wide-web is a pretty serious concern.