Back

@evilcookies98 @tspivey I'm confused, how is switching to JAWS relevant here?

@tspivey @NikJov well, it’s relevant because if this kind of crap is actually going to happen, it’s a good thing. I’ve stopped using NVDA full-time.

@evilcookies98 @tspivey So JAWS lets you run unrestricted Python code on the sign-in screen?

@tspivey @NikJov the point is it leaves your preferences mostly intact. It doesn’t switch back to eloquence on speed slow as a snail just because you pull up the sign in screen.

@evilcookies98 @tspivey The ability to have your preferences intact on the sign-in screen isn't going away, let's not confuse the issue any further.

@NikJov @tspivey if your preference is not using some cruddy built-in voices, yes, it is. I don’t think you’re hearing me here. This isn’t just for fancy functionality.

@evilcookies98 @tspivey My preference is my speech rate. About custom voices, we'll see what happens when it happens. I have no need to switch my screen reader over something that may happen in a year, but maybe it won't even impact me in any way, for instance maybe synth drivers will be an exception. I don't see the need to instantly jump to the worst conclusion possible.

@NikJov @tspivey just because that’s your preference doesn’t mean it’s everybody else’s. Think bigger here. Also, what about our braille display people? They’re getting screwed too.

@evilcookies98 @tspivey Nobody is getting screwed because the change isn't even implemented yet. When it goes to alpha, that's the time to provide feedback if your points aren't already in consideration. So, I can't actually think bigger, because there's nothing to think about. It's only an item on the roadmap.

@NikJov @johann @evilcookies98 @tspivey Can’t believe an open source project is considering something like this

@serrebi @johann @evilcookies98 @tspivey Why?

@NikJov @johann @evilcookies98 @tspivey Because the default is user hostile. At least have it be users choice. The default, allowing these add-ons on secure screens, of course. Businesses that want things to be secure. Can check the box, or enable it on install somehow. This does not need to be the default.

@serrebi @johann @evilcookies98 @tspivey To be honest, I really don't know of many open, or close source apps that provide the ability to run whatever custom Python code on the Windows sign-in screen. To be clear, I fully agree that there needs to be a way for speech synthesizers and Braille display drivers to run, but other than that, almost no add-ons are needed during the minimal amount of time on secure screens.

@NikJov @johann @evilcookies98 @tspivey I agree with that, of course. I think it is interesting timing that remote got put in with an inconvenient shortcut command that I have come around too, and now we are talking about blocking out speech synthesizers some people don’t like us using from the logon screen. Not a good look for MVDA.