NPM won't publish packages containing the word keygen

Re:NPM won't publish packages containing the word keygen by hinkley on Wednesday June 14, 2023 @11:33AM (#36327509)

At the dawn of the search engine age I was in Japan, and so I spent some time not being able to learn about shitake mushrooms, as was a common western spelling at the time (they are not shi-ta-ke mushrooms, they are in fact shi-i-ta-ke mushrooms, hence the spelling change, even though we still pronounce them wrong).

You couldn’t say shit on the internet. I mean what the fuck.

[ Parent | on HN ]

Re:NPM won't publish packages containing the word keygen by jjgreen on Wednesday June 14, 2023 @11:45AM (#36327694)

... the dirty bastards https://www.youtube.com/watch?v=ndcPtU6Imc0

[ Parent | on HN ]

Re:NPM won't publish packages containing the word keygen by Dylan16807 on Wednesday June 14, 2023 @02:27PM (#36330363)

"shi-i-ta-ke" is not very accurate. It's a long vowel, and the word has three syllables.

But english mostly ignores long vowels, hence the alternate spelling.

[ Parent | on HN ]

Re:NPM won't publish packages containing the word keygen by zelse on Wednesday June 14, 2023 @03:52PM (#36331616)

It's funny, because in Old English ('Anglo-Saxon'), vowel and consonant length are both semantically important.

For those of you who want to have a better handle on the distinction, you can think of it as the sound having an extra 'beat', where a beat is the amount of time pronouncing that sound normally occupies.

It's easier if you take advantage of the one place English still distinguishes this: word boundaries.

Listen how you say, for example: Tibetan nitwit (you're holding the 'n' for two beats because your brain treats the distinction as important /when it's at a word boundary). You can do this with vowels too as an exercise, though they're a bit harder because English has a lot of vowels and finding good matches is a bit difficult.

[ Parent | on HN ]