an important information about nvda remote

I just want to require you in this thread not to use NVDA remote anymore because I just heard that Taylor built in a function to crash the clients. He just controlled some PCs even if they have disconnected and then he said yeah it's okay it was just yeah it's funny he said or something like this. I don't hear the audio to the end but yeah and so it might be a good idea I should not use NVDA remote anymore. The exact link if you want to hear the audio. Or want to read the thing go to the NV Audio Network to the same two piece page and then it's there an audio called NVDA remote security something like this. If you click on it there is in the description a link where you can read it. Yeah so I will require to not use it anymore or at least not on the default server. Dash for example. But the server you can use it on there I think because I think you can trust him but yeah.

I think we should wait for official security announcements from NVDA devs or someone else. A website where everyone can upload stuff while he is drunk or whatever is not a trusty source for security-related things. And yeah, NVDA remote is open source and everyone can look inside the code with enough understanding what's going on. And I think we will soon get real security information. Any audio is currently down as it seems or it at least has some issues. I can't access it. And yeah, I think, like I said, it's not a trusty source for security-related information.

Strange. Anyway, you work for me, so maybe it depends on your internet or something like this. But I think we can't hope to an answer of those guys because, as I already said, it seems like it don't interest them that much.

yeah perhaps my no script add-on for firefox is blocking some content from any audio that's needed to load the entire site regarding nvda remote it's not the add-on alone it's also the server code the nvda remote add-on is connecting to and if a server owner is deciding to mishandle its users by implementing code that has a negative effect on nvda remote users it's not a problem of the add-on itself and the server code is also open source and anyone can run his own server i'm not using the official nvda remote.com server only as a form callback but not for daily usage yeah i think there are more than one part that takes place when it comes to security for nvda remote

they don't think that that is all faked because yeah sam also wrote in the audio game summit forum that the voice of the developer is included so yeah

That also happened on the default server by the way. So it wasn't on their server. This was on the official server. So yeah. And I don't know if the official server is still active because last time I tried to connect when I didn't know what these guys are doing, this server wasn't reachable but it can only be a short time problem. And also I would trust no one who implements a crash client's code. And as I already said it was on the official server. So it was implemented by the developer guys not by someone else.

Okay, I just found a recording of a team talk session and I think it's that you're referring to. And as I understand, what basically happened is Tyler was testing a special code, I think something keyboard related. And the mistake he made was to test this not on a development server, but on the regular nvdaremote.com server. And the guys in the team talk session totally made a mountain out of a molehill and freaked out. Yeah, very chaotic, but I think it's nothing to really worry about. Yeah, I don't think nvdaremote is completely out of control or something. It was a test and the only mistake Tyler made was to test things on the official server and not on a development server with a closed user group. And yeah, that's not... That's not good, but as I said, it's nothing to worry about, really.

But if you are testing a crash code, then you do that because you want to use it. And Taylor also said that he knew since this thing was created that it's possible. So he doesn't test it, he just did it because of fun or whatever. And he thinks it's funny. No, it's not funny to feed computers and reset their synthesizers.

This was not relevant when this was posted, so it's very much not relevant now.

yeah here's the thing oh yeah it's recording okay here's the thing uh when a video when this post uh was done um from what i know i have some info from you know the people who were involved um they wanted to well ivan had his pc on remote and you know he wanted to see if he posted on twitter saying oh yeah fuck me over with this key uh and gave out his key he wanted to see how long it would take people to connect and what people would try and do um and i think this is probably more of a dead than anything and obviously what happened was uh tyler spivey for whatever reason decided to modify his video add-on option to send a very very long string of text to a video like by long we're probably talking a few million characters and if you haven't tested this before um you might want to make sure that you know you have sighted help or you have you can restart your pc you need data or anything what essentially happens is um if nvda encounters a huge block of text it will pop up an error message and you will not be able to exit because your nvda will not speak what will have to happen is if someone will have to either click the ok button with the mouse and nvda will come back up or you pretty much have to restart your pc since these guys probably were using desktops without mouse mouses mice i don't fucking know without a mouse um and probably didn't know what was really going on anyway that didn't occur to them so you know which led to sam presumably losing whatever work he was doing or at least that's what we know so really this comes down to common sense you know if you post a key somewhere especially you know on twitter where there's like a billion and something users of course people are gonna fuck with it because you know that's what you've asked for really uh was it okay that tyler did what he did honestly no but at the end of the day a this was a long time ago this is like zero percent relevant today b um b anyone could have done this you know you can't really just say oh this is the dev abusing the add-on no anyone uh could have quite easily done this you know the add-ons open source as is the server it really isn't difficult you know it probably would take me about 10 minutes to replicate the same thing in fact i did once a while ago as a test so you know this isn't rocket science guys don't don't don't don't don't don't don't don't don't don't leave your don't give out your keys if you have to leave your pc on remote you know keep your key to yourself if you have to note write it down anyway keep it somewhere secure where it can't be messed with um you know and obviously be careful what you run because something can just get you on any file but most of this really comes down to common sense you pretty much get what you pay for anyways this is me this is like my random contribution so yeah carry on

I love those people that, like, say that a topic is useless, but those people are pushing the topics so more people are seeing them. Then, if you find it useless, that's your thing. I thought it was kind of important to tell you about that. I was never using NvidiaRemote.com in general, but I thought it was important to know about it. That's my opinion. You don't have to share that opinion, but if you don't, why do you push the topic up just to say that you don't share that opinion? The topic was one year old. Like, seriously.

Well, NVDA Remote once again. I'm seeing we have a bit of a rearing of a beast's ugly head once again. Nice going. I try to avoid the NVDA Remote server where I can. In fact, I've usually been using one or two private servers lately. Namely, Gabduin.com or even KN4CRC.com. Because at least the people who run those servers are quite a bit more honest about what they do. They're not necessarily shady about how their traffic is managed. Plus, I'm wondering. The whole 2019 NVDA Remote. There's a 17.3 bit about NVDA Remote when it officially stops working because of the switch to Python 3. Which should be very interesting to say the least.

Okay, let me see. I was, I've been using NVDA remote for a long, long time. And as far as I've seen it, I haven't had any security problems or anything like that. I mean, yeah, it's, I don't know. I think it was kind of false magazine or something like that. Because if there had been any security problem with NVDA remote, something would have been published in NVDA, NV Access or anything like that. Yeah, NV Access, which are the developers of NVDA, they have been, they have been, they have been, they have been, they have been, they have been, they have been, they have been, they have been published in NVDA. I mean, they had announced something in their official website or anything like that. Or perhaps in, in their blog, in NVDA, in NV Access blog, there had been, there had been anything. But there hasn't been any announcement from, from them. So I don't really think there has been any issue with NVDA remote as far as I can see.

I have been using nvda remote too and with the nvda remote server of course and I did not send my key to anyone that I didn't want them seeing and I had no issue so as long as you use common sense and you generate secure enough passwords and of course you don't tell your password to anyone you don't want them to know and you're going to you're not going to have any problems because even when the guys are guys who run this server are shady I mean they're not going to know when you launched your server mostly because they're not obviously looking after this hacking business like you know let me see who is running as nvda remote server today so I can screw with around with their computer and stuff like that so as long as you don't do what this guy what Ivan did and tell your password on Twitter you're not going to have much of an issue I should say

um so the person who was saying it might have been false um it it's not everything sam said um was true everything he said on the forum were true uh you can do some research and you know find that stuff it's not difficult uh everything he said was true the thing uh the issue was as far as like uh actually validity because um he like him and his friend did something really stupid um i mean today it was a bit of fun because it was a huge cc server which you know included sam ivan sayoon carter and uh finn turner and uh a few other people um and they did something a little bit stupid and you know i haven't so what you know i haven't posted a remote key uh and then he waited for people to connect to see what happened uh and today it was probably just a bit of fun you know they weren't planning anything malicious with it um but obviously when tyler connected to and saw all of them connected to ivan uh he assumed that they were trying to hack ivan so he took some action himself he uses a little modified remote with the crash clients option which like i said previously is not difficult at all to replicate given the fact that the remote code is you know out there you can grab it uh he used it to do some sort of uh he used that um to effectively freeze their computers uh everyone else on that server restarted but sam left his computer in the state it was so he could you know get the whole thing recorded in one file but um uh the point i'm trying to make is the the whole incident really was a bit of a misunderstanding um you know every single one of them was trying to do something and everyone thought the other person was doing something much worse than what they actually were um you know i i think people um in general are taking this way too seriously um it doesn't help that someone who you know uh well at the time that this was posted at any rate had kind of developed a reputation for being trustworthy and for being a reliable source of info you know had posted this that i think hasn't helped um because you know generally speaking people trust sam you know people know that if sam posts something somewhere he's not likely to be lying because he hasn't really done that at all as far as i'm aware i might be wrong but he's pretty much always been honest and people know that about him so because of this because the way he portrayed this whole remote thing it painted it in a much worse light and even though a lot of people rightly didn't take everything he posted seriously um you know it's still obviously you know i think this whole thread is proof that it still did make quite the impact um but no i don't think as far as like lack of our security i don't think tyler slash uh q have any issues there i would say you're risking your i'll say you're risking more by connecting to someone like me and i don't think tyler slash q have any issues there i would say you're risking like me and i don't think tyler slash q have any issues there i would say you're risking who has a reputation for kind of spammy drama filled team talk servers mixed with you know vps is full of ultra power clones or red spot clones or clones of clones or whatever um i say you'll put yourself more on the line and then there's kn4crc or joseph lee who has his own set of issues which i'm not even going to get into um but his trustworthiness should definitely be questioned definitely um and yeah i'm not going to go into exactly why because i don't want to incite more drama here but i think a lot of you will know what i'm talking about um um but yeah um i just wanted to say i think i'm not going to go into exactly why because i don't want to incite more drama here but i think i'm not going to go into exactly why because i don't straight a little bit again everything i've said here is verifiable with a little bit of research you know audiogames.net forum there's a whole topic that sam posted any audio the comments will tell you some things twitter if you look back you know really far at sam's and q's timelines on tyler's timeline too if you look back at those far enough you'll see some stuff you know this is all verifiable on ivan as well but you know what i'm trying to say is all this is verifiable you know i'm not talking out my ass here you can very easily verify everything i'm saying um but yeah that said um yeah that's me done um bye

hello people um i have a problem with nvidia remote because my antivirus is marking it as a virus um i don't really know what to think about this um are there more people here having these issues um or is it just my antivirus um giving a false positive if so please let me know i downloaded the add-on from nvaremote.com i believe that is the official website so um i don't really know what what is um causing this so if somebody could uh could tell me if this is if this is real or if you have the same uh please let me know

oh okay NVDA remote is the proper place to get this so it is definitely a false positive I don't know which antivirus you're using but obviously it needs to be shown some way that this is not a virus sadly NVDA remote support will let out when Python 3 comes in because I haven't heard anything about a new update to that but that's another story

so I don't really know why it is marking remote as a virus it's very weird because remote is not written in BGC so it doesn't use a very old compiler or something so if someone could explain that to me in private message because then we're otherwise we're gonna get a little little off topic but actually I'm gonna run a virus total scan and I will see what comes out if it if it's only Norton saying that the virus then I'll still run it and install it and I will enjoy remote for the time it will still be online so um yeah I have a nice day everybody and bye

so um wait oh yeah it's recording yes I think it's recording I don't know um so um I think the problem is it is coded in some thing and I think it has something to do with that so I don't think it's a virus it is a very good program and I don't think it would be virus I don't think it would be a virus

From now, from this update of NVDA 2019.3.1, or I don't know how it calls, I forget what's the version, when I've updated today the NVDA, or it might be NVDA 2019.3 just, but when I updated, it said that most of NVDA, all of my NVDA add-ons were just flew off from the NVDA, turned off, really. And the remote is all... also flew off, I don't know, I know the reason why it flew off, because NVDA is going to be written in Python number 3, version 3, and all the add-ons must be written in Python 3. That's why it is like this. But I think Golden Cursor and emoticons and some updated, some add-ons will be updated soon. NVDA remote also.