NPM won't publish packages containing the word keygen
1–10 of 269 posts
Re: NPM won't publish packages containing the word keygen
#2What if I write a package to provide generic key generation for other software packages, then share it, generous man that I am?
Re: NPM won't publish packages containing the word keygen
#3I have a pet theory that the language police learned their habits from these systems that have no better way than keyword moderation.
Re: NPM won't publish packages containing the word keygen
#4Such rules are so dumb and easy to circumvent, it is like parent filtering all over again!
Re: NPM won't publish packages containing the word keygen
#5NPM 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.
Re: NPM won't publish packages containing the word keygen
#6genkey
Re: NPM won't publish packages containing the word keygen
#7Author here, with some context: the relevant package [1] generates key material to setup an end-to-end encryption SDK [2], based on libsodium and OPAQUE.
Re: NPM won't publish packages containing the word keygen
#8keyword 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.
Re: NPM won't publish packages containing the word keygen
#9What if I write a package to provide generic key generation for other software packages, then share it, generous man that I am?
Name it kee-gin
Re: NPM won't publish packages containing the word keygen
#10What 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.