Live data from Hacker News

NPM won't publish packages containing the word keygen

mamot.fr

21–30 of 269 posts

Re: NPM won't publish packages containing the word keygen

#21

keyword moderation is terrible and only affects the language(s) you know about. It doesn't actually prevent the content (the goal of these types of filters) from being served. It'd be like a virus scanner preventing a program from running because it had the name 'virus' in it ... which would prevent itself from running -- probably.

[deleted]

Re: NPM won't publish packages containing the word keygen

#22
post #19

I run a business called Keygen [^0], and own the @keygen namespace on npm. We’re working on a Node SDK, so this isn’t good to hear. I’ll open up a discussion with them and see what we can do. [^0]: https://keygen.sh

Have you had any publishing issues? My last successful publish on this package was 3 months ago, and I started noticing issues with deploys a few weeks back.

Three fun days of CI/CD pipeline debugging to get to this..

Re: NPM won't publish packages containing the word keygen

#23
post #10
post #2

What if I write a package to provide generic key generation for other software packages, then share it, generous man that I am?

Believe it or not, jail.

For anyone not aware of the reference, this is from an episode of Parks and Recreation:

https://www.youtube.com/watch?v=eiyfwZVAzGw

Re: NPM won't publish packages containing the word keygen

#24
post #10
post #2

What if I write a package to provide generic key generation for other software packages, then share it, generous man that I am?

Believe it or not, jail.

We have the best package repository in the world because of jail.

Re: NPM won't publish packages containing the word keygen

#25

keyword moderation is terrible and only affects the language(s) you know about. It doesn't actually prevent the content (the goal of these types of filters) from being served. It'd be like a virus scanner preventing a program from running because it had the name 'virus' in it ... which would prevent itself from running -- probably.

My favorite is the online name censoring in video games. Dark Souls infamously just does a straight check of any string match within the name against a big list of no-no words. So in this fantasy game where everyone is running around as a knight, anyone who has "knight" in their game will appear as "k***ht" to other players.

There's also a famous image I've seen online from another game where the guy's name was Nasser which appeared for everyone else in-game as "N***er"

Re: NPM won't publish packages containing the word keygen

#26
post #5

NPM is owned by Microsoft, who sell proprietary software, the kind that keygens are made to defeat. Don't expect to see KMS spoofers on GitHub anytime soon for the same reason.

Okay but what about keygen for ssh/git/pgp/certs or really anything in software that relates to security, which fundamentally rely on, at some point, the generation of encryption keys? It’s just such a dumb counterproductive step to take.

Re: NPM won't publish packages containing the word keygen

#27
post #15

I thought buttbuttination taught everyone how incredibly stupid this is 25-30 years or so ago already? But no. Just a few years ago I tried to enter an answer into a Hungarian Q&A site recommending to take the Algeciras-Tangier ferry and the answer was refused. https://en.wiktionary.org/wiki/geci

LOL, that is a great mnemonic! Now I will always remember how to spell assassination.

Re: NPM won't publish packages containing the word keygen

#28
post #19

I run a business called Keygen [^0], and own the @keygen namespace on npm. We’re working on a Node SDK, so this isn’t good to hear. I’ll open up a discussion with them and see what we can do. [^0]: https://keygen.sh

Try using a Russian Cyrillic е or к or у

Sure no one will be able to install the app from the CLI (unless there is a bug in npm’s parsing logic) but you should be fine distributing hyperlinks to skim-readers ;)

Re: NPM won't publish packages containing the word keygen

#29
Keyword moderation feels like an unspirited attempt by developers to satisfy incompetent managers telling them to get other incompetent managers, upset about piracy, off their backs. I don't believe anyone involved actually thinks this will make a difference. It's just to address a complaint.
Post reply on HN