6 ms·
your GitHub account is not yours but GitHub's property, they just do not claim that before they ban your account. All cloud services do the similar things.
by elia_is_me 5y ago
your GitHub account is not yours but GitHub's property, they just do not claim that before they ban your account.
All cloud services do the similar things.
- scrollaway 5y agoThis isn’t how it works at all. It’s not how copyright law works, it’s not how property law works, and it’s certainly not how cloud services work. What isn’t yours is your “right” to use the service.
- feupan 5y agoHave you read the project’s license? That is literally how it works. It’s not even an original project by Marak, as it’s clearly shown in there. The only fault here is cutting the owner out of the repo, but given the security breach it’s strange that he isn’t permanently banned at all. And yeah, adding an infinite loop is a DoS attack. > not how cloud services work. Try placing a virus on S3 and let me know how that works out.
- fault1 5y agonot to mention that in the case of colors.js he actually owned less copyright than other contributors. they had actually changed more of the code.
- scrollaway 5y agoI’m not defending the author. GitHub is in their right to do what they did. But certainly not because of the nonsense GP claims. And yes you can host viruses on S3. What you can’t do is use Amazon’s network to do illegal shit (such as distribute viruses without consent).
- feupan 5y agoObviously I mean to distribute viruses via S3, which is what’s happening here. Your account is guaranteed to be flagged as soon as they find out. The update here was distributed to every subscriber.
- scrollaway 5y agoWhat's your point? That doing illegal shit will strip you of your rights? You know, I hear that if you go around stabbing people, you lose the right to not spend a bunch of time in prison, too.