FYI if you use the #NVDA translation addon polyglot: it stores API keys and passwords in nvda.ini in cleartext. If your NVDA log level is anything above info, those values will be written to nvda.log, even if the addon was disabled or removed at the time. I have filed an issue and PR, and am sure this will be fixed shortly. But in the meantime, if you use this addon and have filed any bugs with #nvdasr or with any other addon, and included a copy of nvda.log, you must rotate all API keys and passwords for all of your translation services. github.com/cary-rowen/polyglot/issues/20
An alpha version of my polyglot fork is now available. Note that this is alpha quality software, as of yet. The key changes: * stores credentials in the Windows Credential Manager * adds engines: LibreTranslate, Argos Translate, Naver Papago, and Lara Translate * no longer attempts to download chrome runtimes on secure screens * no longer attempts to download Argos models on secure screens * makes writing the translation cache thread-safe, and batches writes for speed * deletes all API keys and config values when uninstalled * no longer attempts to translate strings that are only numbers, punctuation, or emoji: both for speed, and a tiny boost in privacy * removes all engines that depend on the NVDACN infrastructure * removes shared API keys shipped with the addon * removes someone's private ollama server that was a hardcoded default for some reason
The road to 1.0: * lots and lots of real-world testing to find the bugs that almost certainly exist * get API keys for all of the available services so I can test them locally * build a test harness using GitHub actions that tests all of the services for API changes and ensures they all continue working * set up GitHub secrets, etc, so I have a CI/CD environment that can actually test all 18 API's
