Live data from Hacker News

NPM won't publish packages containing the word keygen

mamot.fr

261–269 of 269 posts

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

#261
post #244

Earlier quoted context omitted.

Just learned "keygen" is the term the script-kiddies use to describe the act of generating fake activation keys. Never let it be said HN is not educational. But I feel the same way I felt when I noticed idiots using "crypto" to refer to cryptocurrency instead of cryptography.

Keygen has been around for for at least 30 years, whereas people misusing the term “crypto” has only been around for five years or so.

"Crypto" has been around for much longer than 5 years. I remember someone using it in reference to a Motorola DES chip in the late 70s. And the IACR Crypto conference has been going on since the early 80s.

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

#262

Earlier quoted context omitted.

Yes, and your definition is by far the exception, not the rule. Maybe don't claim a definitive meaning when you're wrong to begin with. One is much more likely to set off censors. Why do you feel the need to ask ridiculous questions? The word you use had already been said, censoring it would be meaningless -- whereas you ascertained the word I meant easily ;)

I’m not actually the first person you were talking to, so I didn’t give you any definition. In fact, if you note, I’ve never actually used either word. I just refer to them obliquely.

"You yourself imply there are different degrees to how acceptable the two terms are."

I never claimed either were acceptable or unacceptable.

Interesting how you completely gloss over your needless language policing, especially when you - by your own admission -- haven't even used the terms in question (and presumably lack the nuance necessary to weigh in, despite jumping in anyway) shrug

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

#264

Earlier quoted context omitted.

I’m not actually the first person you were talking to, so I didn’t give you any definition. In fact, if you note, I’ve never actually used either word. I just refer to them obliquely.

"You yourself imply there are different degrees to how acceptable the two terms are." I never claimed either were acceptable or unacceptable. Interesting how you completely gloss over your needless language policing, especially when you - by your own admission -- haven't even used the terms in question (and presumably lack the nuance necessary to weigh in, despite jumping in anyway) shrug

> I never claimed either were acceptable or unacceptable

and

> Love how you're trying to justify degrees of acceptable misogynist terms

So you are not saying either are unacceptable, and you endorse 'acceptable' misogyny. So you are a misogynist, but an ok one.

Very well.

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

#265
post #244

Earlier quoted context omitted.

Just learned "keygen" is the term the script-kiddies use to describe the act of generating fake activation keys. Never let it be said HN is not educational. But I feel the same way I felt when I noticed idiots using "crypto" to refer to cryptocurrency instead of cryptography.

Keygen has been around for for at least 30 years, whereas people misusing the term “crypto” has only been around for five years or so.

Greetings! I am here to derail the thread with a remark about "organic chemistry" versus "organic foods".

Sometimes being there first doesn't mean you get to use the simplification forever. Cryptography is an older thing than cryptocurrency, but both are unwieldy to pronounce and have been simplified to "crypto". Since cryptography is math and cryptocurrencies (in the "popular" sphere) is a get rich quick scheme, the abbreviation that works for both generally became applied to the latter.

I am sure organic chemists are a little weirded out when people tell them "oh yeah I love those new strawberries we got". This is that.

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

#266

Earlier quoted context omitted.

"You yourself imply there are different degrees to how acceptable the two terms are." I never claimed either were acceptable or unacceptable. Interesting how you completely gloss over your needless language policing, especially when you - by your own admission -- haven't even used the terms in question (and presumably lack the nuance necessary to weigh in, despite jumping in anyway) shrug

> I never claimed either were acceptable or unacceptable and > Love how you're trying to justify degrees of acceptable misogynist terms So you are not saying either are unacceptable, and you endorse 'acceptable' misogyny. So you are a misogynist, but an ok one. Very well.

What the ever-loving fuck? I don't endorse ANY misogyny you utter melon, which was why I called you out on your "Really isn't, it's about the same as calling a woman a cow." nonsense.

The only one "endorsing" misogyny here is you. Stop projecting, pillock.

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

#268

So,... has anyone with this issue actually contacted the NPM team and asked what is is about?

Official response from NPM (a week later):

> You are correct, keygen is a stopword. We blocked users from using this word for security purposes.

> Apologize for the inconvenience and we highly suggest you choose a different word for your package going forward.

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

#269
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

The Scunthorpe problem all over again. https://en.wikipedia.org/wiki/Scunthorpe_problem

I call systems that attempt to filter out bad words and fall prey to the Scunthorpe problem as "failing the Scunthorpe test".

There are people that fail the test, too - such as people who think that the terms "whitelist" and "blacklist" are offensive.

Post reply on HN