Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I would assume continual monitoring by the feds is involved. There's a number of people out there in the world who have been prohibited by federal law from the use of a computer or any such device with capabilities on par with a computer. IIRC, Kevin Mitnick faced a similar situation after serving his prison sentence, but they eased up on the sentence after a year.I wouldn't particularly trust Reddit's take on it. Please explain how any government on earth would enforce "potential permanent ban from use of a computer."
And while theoretically possible, it does come off as... well, absurd, right? You'd practically need the person to be under house arrest in order to monitor them so thoroughly - eyeing up not only purchases on credit (easy) but also cash, and ensuring that they don't somehow just connect with a cash-bought computer to someone else's wifi by monitoring spikes in electricity usage that might suggest their operating a computer? As you concluded, it's all rather excessive for this scenario.There's a number of people out there in the world who have been prohibited by federal law from the use of a computer or any such device with capabilities on par with a computer. IIRC, Kevin Mitnick faced a similar situation after serving his prison sentence, but they eased up on the sentence after a year.
Infecting is the wrong word for what it sounds like he's doing, because killing the process is the exact same use-case. So to say, if he just had an improper call to his functions cause the process to die, people would probably think "oh, it's bugged, doesn't work" and go on with their days. Rebooting the computer would be done through the exact same avenue. I wouldn't be surprised if this is how it changes, either - rather than a computer restart, he'll just have the code brick third-party libraries and software making calls to his copyrighted shit.infecting countless computers of strangers you don't know just for some gotcha on some little girl on the internet is pretty fucking retarded and up there with the cringe fest this game's community seems inclined to endlessly produce.
What a retard. This stupid little stunt of his will probably get him considered a risk and potentially blacklisted from tech companies, at least if they do research on him and look at his portfolio during the hiring process. You shouldn't dictate what people should or shouldn't have installed. Get fucked.I dunno...infecting countless computers of strangers you don't know just for some gotcha on some little girl on the internet is pretty fucking retarded and up there with the cringe fest this game's community seems inclined to endlessly produce.
Edit: The guy who pulled this dumb shit is now in damage control mode and issued an apology, but the damage has been done. You don't secretively put malware into another person's computer just to spite some stranger on the internet, tell everyone that you could do a lot worse to them and then deflect blame from yourself by saying the person who didn't even know the malware was in the program while distributing it is the real one at fault. That shows a lack of accountability and a level of petty maliciousness that is practically par for the course in this community by this point. You don't come back from that and to think people will be stupid enough to give a snake like you a chance after this is exceptionally exceptional.
View attachment 4458276
From my understanding, gshade is open source, I don't believe it's copyrighted by anyone. It's basically supposed to be a "better" version of reshade. The whole reason he put that code in there was because he was assmad that someone made a tool to be used with his program to benefit reshade and he wanted people to exlusively use only his program. Instead of having a chat with this Nite broad, he instead tries to teach her a "lesson" by putting that code in specifically so that her tool would activate it and then point the finger at her that her tool is causing all of this, ignoring that putting codes into a program that tells someone's computer to do certain things without their knowledge and consent is a pretty big yikes. Especially if done for an extremely petty reason. None of this would have happened had he been an adult and talked with Nite about it. He reacted the absolute worst way anyone could in this situation.And while theoretically possible, it does come off as... well, absurd, right? You'd practically need the person to be under house arrest in order to monitor them so thoroughly - eyeing up not only purchases on credit (easy) but also cash, and ensuring that they don't somehow just connect with a cash-bought computer to someone else's wifi by monitoring spikes in electricity usage that might suggest their operating a computer? As you concluded, it's all rather excessive for this scenario.
Infecting is the wrong word for what it sounds like he's doing, because killing the process is the exact same use-case. So to say, if he just had an improper call to his functions cause the process to die, people would probably think "oh, it's bugged, doesn't work" and go on with their days. Rebooting the computer would be done through the exact same avenue. I wouldn't be surprised if this is how it changes, either - rather than a computer restart, he'll just have the code brick third-party libraries and software making calls to his copyrighted shit.
After a little digging - hard to do because the Gshade git seems to be just vamoose? Assuming this was the old depository? Here someone says that Gshade is closed-source, whereas Reshade is open-source and Gshade is itself a fork of Reshade. This checks out, since if Gshade was open source, whoever Nite is could've just forked the version of it she liked when building her tool and incorporated it into the tool (thus, if he tried to update the depository with malicious code, it wouldn't matter because the tool wasn't referencing that version). Being closed-source, the guy's claims of proprietary/copyrighted assets could hold up, in that Nite's tool was accessing these assets in a manner that violated whatever the Gshade license was. Since the git's dead, I can't actually check whatever was in the license.From my understanding, gshade is open source, I don't believe it's copyrighted by anyone.
Yes, they usually only reserve such punishment for particularly extreme individuals that could either compromise major financial institutions/have embezzled a near fortune's worth of money through some manipulation of computer tech, compromise governmental networks and systems, or... just people with child pornography, basically. I'm sure they have their methods to monitor that sort of thing one way or the other, though one can imagine how difficult is to enforce in the modern day given just how much daily living is now dependent on computers and the internet.And while theoretically possible, it does come off as... well, absurd, right? You'd practically need the person to be under house arrest in order to monitor them so thoroughly - eyeing up not only purchases on credit (easy) but also cash, and ensuring that they don't somehow just connect with a cash-bought computer to someone else's wifi by monitoring spikes in electricity usage that might suggest their operating a computer? As you concluded, it's all rather excessive for this scenario.
I don't know much about the law, but I don't think you can just legally declare something closed-source or copyrighted on the basis of a user statement. Like I can't just upload an original character on Deviantart and then claim it's copyrighted and sue people for taking it. I don't know if claiming something as closed-source is legal binding agreement for people, but I don't it would be considered a copyright application as well because I think there's a process where you have to legally register something as copyrighted material through a legal system. I don't think it would hold up to me I think this developer is 100% in the wrong and Nite did not do anything to warrant this.After a little digging - hard to do because the Gshade git seems to be just vamoose? Assuming this was the old depository? Here someone says that Gshade is closed-source, whereas Reshade is open-source and Gshade is itself a fork of Reshade. This checks out, since if Gshade was open source, whoever Nite is could've just forked the version of it she liked when building her tool and incorporated it into the tool (thus, if he tried to update the depository with malicious code, it wouldn't matter because the tool wasn't referencing that version). Being closed-source, the guy's claims of proprietary/copyrighted assets could hold up, in that Nite's tool was accessing these assets in a manner that violated whatever the Gshade license was. Since the git's dead, I can't actually check whatever was in the license.
Since it's closed-source, Nite making the tool to get around certain things in Gshade was playing with fire, and it's something that you really, really, really should not do for exact reasons like this. If the Gshade retard hadn't stated that his code caused the problem, what he could have done was modify Gshade with even more malicious content and quietly let the Nite person distribute it. That could've bricked a bunch of peoples' computers and, with Gshade being closed source, it would've been far easier to pin the blame on Nite's tool than to go digging through process calls in a sequestered environment to figure out that Gshade was returning something sussy. Eventually people would figure out where it was coming from, but the point remains that the same anti-tampering methods used to kill a process can indeed brick a computer.
Apparently Gshade reserved admin access to do its thing? That's pretty skeezy in the first place, honestly. Yeah, people, uh, don't give that out to programs whose sole purpose is to make some colors look a little prettier unless the code's able to be eyeballed all-the-way-through.
You can legally (and just generally) declare something closed-source if I can't see the code, lol. Open-source means that the code's visible to anyone, including the end-user; closed means that it isn't. As to copyrighting code... it's a bit more of a complicated topic, but you absolutely can copyright the stuff - and other things like particular meshes / shaders / etc, with code being arguably easier to do so. But copyright essentially just says "I made this, I have the rights to it (and thus to decide what is done with it)."I don't know much about the law, but I don't think you can just legally declare something closed-source or copyrighted on the basis of a user statement.
I'm unfamiliar with Deviantart's particular EULA, but if you generated a copyright for the art piece, if someone were to attempt to use it for their profit, you absolutely could go after them. Even if they just found the image on deviantart and started printing it on shirts - protip, don't do that.Like I can't just upload an original character on Deviantart and then claim it's copyrighted and sue people for taking it.
Nite almost certainly violated the licensing of Gshade with the third-party tool. Of course, what does that mean legally? Absolutely nothing, lol, because this third-party tool wasn't trying to turn a profit and in no world could you argue that the Gshade guy was somehow suffering financial damages as a result of it. Whereas Chantal could say that, by distributing her... 'content' to other people, you were diminishing her potential sales and income and claim damages.Nite did not do anything to warrant this.
Copyright 2014 Patrick Mours. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
* Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Yes, they usually only reserve such punishment for particularly extreme individuals that could either compromise major financial institutions/have embezzled a near fortune's worth of money through some manipulation of computer tech, compromise governmental networks and systems, or... just people with child pornography, basically. I'm sure they have their methods to monitor that sort of thing one way or the other, though one can imagine how difficult is to enforce in the modern day given just how much daily living is now dependent on computers and the internet.
While there could be, as I don't really know anything at all about their histories, it isn't uncommon for there to be a bunch of different forks of the same principle software. A fork is basically just where you have the original program, someone copies that wholesale, and then begins working on their own version of it from that effective fork in the road. It may just have been that the Gshade guy wanted to focus on certain aspects of the shaders or their optimization or so-on and decided to just build off of the existing Reshade for that purpose, with no bad blood.Is there supposed to be some rivalry going on?
I will say, if she's (well, assuming it's an actual she lel) actually 16, having something like this crop up is... it's not like a beginner's-beginner's mistake, but it's understandable why someone young wouldn't entirely grok why what they were doing was dubious or dangerous. At the surface-level, it looks to me like they just wanted to improve performance by circumventing certain cumbersome quirks of Gshade that make it inefficient to get to its actual improvements over base Reshade, and just assumed the guy wouldn't chimp out about it.the bitch who made the 3rd party tool are both colossal faggots.
As someone who has used Gshade I won't argue with you on legalities or technicalities (because you clearly know more about that than I do considering that I thought closed-source was a legal term that meant code unable to be tampered with), however, I think it's fair to at least empathize with why she wanted to make the addon in the first place. Gshade has a really fucking annoying function where if you do not install their latest update, the program will just brick itself and not work at all. Basically the program ceases to function until you update it. People, rightfully in my opinion, were pissed about this and this lead to Nite making the mod that makes it so Gshade still works even if you don't update it. Setting aside the technicalities, I personally empathize with this and while it might've been playing with fire to tamper with it, I still think Nite at the very least had empathizable intentions. But that's just me.While there could be, as I don't really know anything at all about their histories, it isn't uncommon for there to be a bunch of different forks of the same principle software. A fork is basically just where you have the original program, someone copies that wholesale, and then begins working on their own version of it from that effective fork in the road. It may just have been that the Gshade guy wanted to focus on certain aspects of the shaders or their optimization or so-on and decided to just build off of the existing Reshade for that purpose, with no bad blood.
Since a lot of these things are passion projects and there's no cash involved, it's usually pretty harmonious. Another way to think of it is DOOM - DOOM's source code was made open-source eons ago, and there's a million different versions of DOOM out there today - all (or, at least, most) forks of that original code.
Gshade being copyrighted and closed-source doesn't mean that you're under any obligation to pay for it; you just have to abide by the license. Reshade being open-source is still probably copyrighted and still probably has a license. oh wait, that was the original reshade copyright, which gshade just included
I will say, if she's (well, assuming it's an actual she lel) actually 16, having something like this crop up is... it's not like a beginner's-beginner's mistake, but it's understandable why someone young wouldn't entirely grok why what they were doing was dubious or dangerous. At the surface-level, it looks to me like they just wanted to improve performance by circumventing certain cumbersome quirks of Gshade that make it inefficient to get to its actual improvements over base Reshade, and just assumed the guy wouldn't chimp out about it.
Which is a fine colloquial understanding of it, because most of the time, you can't really tamper with it. You can't make a call to a function you don't know the name of. What allowed it, I'm assuming, to happen here is that the guy probably left most of the Reshade code totally intact; indeed even the copyright is mostly just the thing that's on Reshade itself.considering that I thought closed-source was a legal term that meant code unable to be tampered with
That's why I think the age of Nite matters here. Because calling into functions as they were named in ReShade to gain access to Gshade's unique assets without dealing with Gshade's stupid update requirements (and other runtime bloat) is a clever idea. It's just, yeah, if you aren't really aware of what power that gives to someone who manages the closed-source depository, you wouldn't know why it's both clever and incredibly stupid. If Nite was even just 20, doing something like this is a mark of extreme retardation, but it's more understandable for someone who's still young and learning.Setting aside the technicalities, I personally empathize with this and while it might've been playing with fire to tamper with it, I still think Nite at the very least had empathizable intentions.
UWU Wholesome 100 LGTB+ Friendly FFXIV streamer Zepla getting cancelled for "Going on a TERF rant to justify herself playing/streaming the game and abandoning her LGBT+ community" is todays HL drama.
For months she had been liking/retweeting boycott crap, it is so funny the drama/bullying in the last week is what peaked her.
Also, lol.