Recent searches
Search options
Edit: This post is based on outdated information which is no longer relevant. I apologize for the confusion.
NVDA Remote was merged into NVDA for the upcoming 2025.1 release.
This sounds like something to be happy about, but read on.
Now every new feature and change has to go through NV Access to get approved, which is a lot more work than adding your feature to an addon.
Why not create a separate addon? As said in #17703, they plan to remove the ability for addons to run on secure screens in the future. If this happens, nothing like Remote can ever be created again without the blessing and cooperation of NV Access.
Instead of empowering developers and users by allowing them to choose which addons are usable on secure screens, NV Access plans on disabling them.
Merging this just gives NV Access more leverage to meeting this goal. Their reason might be something like now that Remote is merged, we don't need addons there anymore because the interaction time is so short.
You might say that NVDA is open source, so someone can just modify the features they don't like. That's true, but it has to be signed for UI Access to work correctly, so someone would have to pay quite a bit to fork it and do their own thing. You then also have the problem of a fragmented community between NVDA and the new one.
The advantage with Remote merged in is that the users will be able to use Remote without an extra download, but we're going to be stuck with whatever NV Access gives us. I guess we'll see what they turn it into.
@tspivey I wanted to mention @NVAccess on this so we can discuss this as I'm not in favor of completely disabling add-ons on secure screens at all and I will not update my NVDA if this happens. Apart from Remote, we need to think about people who prefer a certain speech synthesizer due to, for instance, hearing loss, or cases where the built-in synthesizers do not have very good language support for a given language (for instance, I heard that eSpeak has some foreign languages that are not good at all and there are some OneCore voices that also do not have high quality support for certain languages). Please consider these points before enforcing the inability to use add-ons on the secure screens. The correct approach is to either allow the add-on developer to indicate in the manifest whether the add-on is allowed to run on a secure screen, or to allow a user to individually select which add-ons to copy to the secure screen. The fact that the plan is to just completely disable all add-ons on the secure screen, instead of allowing users to selectively copy add-ons over to the secure screen, when users express that they want this, is not good and it is not in the user's best interest. I am hoping that this thread can start a dialogue about this so that this can be discussed further, as opposed to completely disabling add-ons on the secure screens without considering the possible ramifications.
@gocu54 @tspivey @NVAccess @BTyson I think we need to know the underlying reason behind this move. Have they been ghreatened with legal action? Are they hoping more IT departments will allow employees to use NVDA? NVDA has beenquite quiet as of late. If there's a problem, they at least deserve the opportunity to explain it to us without us immediately jumping down their throats.
@alexchapman @tspivey @x0 @Bruce @gocu54 @NVAccess @BTyson I think this issue is exacerbated by the fact that many of the synths users use are still technically illegal/legally ambiguous, and so even if addons will eventually be signable to run on secure screens, the synths that will benefit from that are Vocalizer, Acapela, etc. and Eloquence/Dectalk/Bestspeech will be left out.
@jackf723 @alexchapman @tspivey @x0 @Bruce @gocu54 @NVAccess @BTyson Signable/unsignable doesn't solve the problem. It's *my* computer. I will run *whatever* code *I* want on *my* computer on *whatever* parts of the systems *I* want. It's already not possible to run addons on most secure screens in companies with correctly configured policies because it requires admin approval to make that change.
@fireborn @jackf723 @alexchapman @tspivey @x0 @Bruce @gocu54 @BTyson We aren't disabling add-ons on secure screens, and certainly not for users who don't want it. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: https://fosstodon.org/@NVAccess/114187262027039287 Please follow us for OFFICIAL information, and remember you can now also sign up to updates like our blog via email: https://eepurl.com/iuVyjo
@Aryan @fireborn @jackf723 @alexchapman @tspivey @x0 @Bruce @gocu54 @BTyson That is the FIRST link to something at all relavent to this whole discussion, thank you!
Ok, I can clarify again, we are NOT removing the ability to run add-ons on secure screens. It was a thought awhile ago, we have moved on from this considering how it would impact users. The 2025.1 milestone was a false automated tag when the issue was closed. It was closed as a duplicate of #6305 & #12879 which are both still open.
@NVAccess @Aryan @fireborn @jackf723 @alexchapman @x0 @Bruce @gocu54 @BTyson I had a few reservations, said my bit and let the thread end. Not all of it was even about addons and secure screens. People took more out of it than I intended. I thought my original post was pretty clear that it was in the future, not a something to panic over right now thing, and I even included my source. Maybe it would've been better to wait until that actually showed up as a PR to comment.
@tspivey @Aryan @fireborn @jackf723 @alexchapman @x0 @Bruce @gocu54 @BTyson You deliberately pulled a month old comment from an issue which was closed as a duplicate, ignored the referenced open issues & did not ask in the appropriate channels - ideally on the issue where the comment was made, or at least by email to us, or even tagging us. So no, I don't buy for a minute that you legitimately expressed a concern and let it be. You deliberately lit a fuse and waited for the fireworks. - Quentin