Faker.js is now a community controlled project

Re:Faker.js is now a community controlled project by feupan on Sunday January 16, 2022 @07:27PM (#29961973)

Have 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.

[ Parent | on HN ]

Re:Faker.js is now a community controlled project by scrollaway on Sunday January 16, 2022 @08:08PM (#29962239)

I’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).

[ Parent | on HN ]

Re:Faker.js is now a community controlled project by feupan on Monday January 17, 2022 @08:34PM (#29973839)

Obviously 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.

[ Parent | on HN ]

Re:Faker.js is now a community controlled project by scrollaway on Tuesday January 18, 2022 @08:36AM (#29978797)

What'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.

[ Parent | on HN ]

Re:Faker.js is now a community controlled project by fault1 on Sunday January 16, 2022 @07:55PM (#29962164)

not 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.

[ Parent | on HN ]